• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 29 subscribers
  • Views 924 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.

Bootloader TMS570 starts application, FEE TI_Fee_Init() not IDLE after app startup

Thomas Germann
Prodigy 60 points
Other Parts Discussed in Thread: HALCOGEN

Hi

I have a TMS570 bootloader which starts an application which is using the FEE interface. Application works fine when loaded via JTag and run from addr 0x0. When loaded and run via bootloader from addr 0x0002’0000, application starts ok until TI_Fee_Init() is reached. TI_Fee_GetStatus() returns always UNINIT and app is stuck. When removing FEE usage, everything is ok.
Bootloader itself does not use FEE.

Thanks…

  • 0
    Prodigy 60 points

    The reason is the missing FEE_..._SECTIONs in sys_link.cmd file. Which got lost while I was experimenting with my handwritten sys_link.cmd
    Is it possible to tell HalCoGen to generate a linker command file which starts at 0x0002’0000?
    Thanks

  • 0 in reply to Thomas Germann
    TI__Guru 59540 points

    Hello Thomas,

    It is not possible to configure the linker command file from Halcogen. However, the linker command file that is output by Halcogen has user code sections where you can insert any custom configuration information needed. If you place your application specific code within these sections, any additional project code regeneration via Halcogen will not change those areas of you file.