• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 29 subscribers
  • Views 203 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TM4C129ENCPDT: Startup_ewarm vector table not consistent with datasheet.

Hairy Lee
Prodigy 200 points
Part Number: TM4C129ENCPDT
Other Parts Discussed in Thread: EK-TM4C129EXL, EK-TM4C123GXL, EK-TM4C1294XL

Hi I have a copy of the TivaWare_C_Series-2.2.0.295 SDK and the example startup_ewarm.c file in \examples\project\ does not match the locations specified in table 2-8 and 2-9 of the June 18, 2014 datasheet.

The startup_ewarm.c file provided in the actual examples C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c129exl\project0 does however.

  • +1
    TI__Guru**** 158815 points

    Hi Hairy,

      The one in \examples\project\ is meant for the TM4C123x device, not TM4C129x device. The C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c129exl\project0 is specific to the TM4C129. Sorry for the confusion. 

  • 0 in reply to Charles Tsai
    Prodigy 200 points

    Hello Charles,

    Thanks for the clarification, it is somewhat confusing as it was the TM4C129 specific SDK (SW-EK-TM4C129EXL-2.2.0.295.exe) that was downloaded so I had assumed that all files would be targetted at the TM4C129 as per the provided examples.

    Could I suggest a comment to this affect makes its way into the next release please either in the startup_ewarm.c itself or the associated readme file.

    Regards,

    HL

  • 0 in reply to Charles Tsai
    Prodigy 200 points

    Sorry Charles, as a side note, is there any documentation explaining why the stack is defined in startup_ewarm.c rather than as a block within the linker file please.

    Thanks

  • +1 in reply to Hairy Lee
    TI__Guru**** 158815 points

    Hi Hairy,

    Hairy Lee said:
    Could I suggest a comment to this affect makes its way into the next release please either in the startup_ewarm.c itself or the associated readme file.

    Yes, we can add that clarification. I will even think to remove the /example/project all together because there is a also a specific project0 for TM4C123 in C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c123gxl\project0.

    Hairy Lee said:
    as a side note, is there any documentation explaining why the stack is defined in startup_ewarm.c rather than as a block within the linker file please.

    Actually, I don't really know. For other toolchains like CCS, we actually define the stack size in the CCS build setting. I think the reason is that IAR is a 3rd parity toolchain and we don't have any TivaWare examples that is ready to run in IAR other than source code. All the examples in C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c1294xl\ are ready to run in CCS without rebuilding them.

    [Edit] Our current team did not put together these examples, and we don’t really understand why the engineers who did took that approach. We will investigate if we can adjust that in future builds now that is has been raised as it does some strange to do it this way. Thanks for bringing this up as we are not IAR experts