• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 29 subscribers
  • Views 672 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

HALCoGen & Warning #10068-D

Mathew Maher49
Expert 2115 points
Other Parts Discussed in Thread: HALCOGEN

Hi,

I'm using HALCoGen v3.6 to generate code for a TMS570LS20206PGE using the TMS570LS20216ZWT_FREERTOS wizard. Everything seems to work fine generating from a ZWT project onto a PGE target, except a few warnings are raised in the code:

"../HAL/source/sys_link.cmd", line 47: warning #10068-D: no matching section
"../HAL/source/sys_link.cmd", line 53: warning #10068-D: no matching section
"../HAL/source/sys_link.cmd", line 54: warning #10068-D: no matching section
"../HAL/source/sys_link.cmd", line 55: warning #10068-D: no matching section

Stgruggling to understand these warnings, as they relate specifically to high-level areas of FreeRTOS:

    /* FreeRTOS Kernel in protected region of Flash */    
 .kernelTEXT   : { sys_startup.obj(.const)
           os_tasks.obj (.const:.string) <<WARNING
           -l=rtsv7R4_T_be_v3D16_eabi.lib<auto_init.obj> (.text)
           -l=rtsv7R4_T_be_v3D16_eabi.lib<copy_decompress_rle.obj> (*)
           -l=rtsv7R4_T_be_v3D16_eabi.lib<cpy_tbl.obj> (*)
           -l=rtsv7R4_T_be_v3D16_eabi.lib<copy_zero_init.obj> (*)
           -l=rtsv7R4_T_be_v3D16_eabi.lib<copy_decompress_none.obj> (*)
           -l=rtsv7R4_T_be_v3D16_eabi.lib<icall32.obj> (.text) <<WARNING
           -l=rtsv7R4_T_be_v3D16_eabi.lib<memset32.obj> (.text) <<WARNING
           -l=rtsv7R4_T_be_v3D16_eabi.lib<memcpy32.obj> (.text) <<WARNING

 Has anyone spotted these warnings coming out of HalCoGen before, or is this something specific to building for one target and compiling for another?

Using the latest versions of Code Composer and compile tools.

cheers

Mat

P.S. As a side point, is there any backdoor way to enable HALCoGen to generate FreeRTOS code for the PGE target?

 

  • 0
    Expert 1895 points

    Mat, I have always had those issues with the FreeRTOS builds for my Hercules RM48L950ZWT and 952PGE builds. Somewhere I have a forum post where it was confirmed to be OK and expected, something to do with FreeRTOS's own memcpy routines and other libraries I think.

    As for a back door for a FreeRTOS PGE target build, I would also like to see this as I lost a lot of time trying to port a ZWT HALcogen setup to PGE. It seems to me that Ti could help us all out by integrating the project for their PGE packages too.

    Or - provide a good "diff" tool for HALcogen so that we can more easily identify what changes are required when porting from one MCU package to another.