• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 381 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.

TM4C1294NCPDT: Different timing behavior: debugging via CCS vs. start-up

Volker Weber
Intellectual 570 points
Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: UNIFLASH

Hi,

coming from here: Post in CCS forum, I put my question now here:

I am facing a different behavior on my own hardware using the TM4C1294NCPDT with an external clock. When I debug the software with CCS and flash it at runtime the program works as expected: the sensor <-> tiva connection output shows the expected result. However, if I power cycle the system or flash it with the UniFlash tool (and power cycle after), I got lots of bit errors while receiving messages. Looking on the bus itself, the messages are still transmitted correctly.

Are there any prerequisites to be met regarding the timing of the tiva when using e.g. the UniFlash tool?

  • 0
    TI__Guru 72500 points
    The one thing that comes to my mind is that CCS sets the program counter to the entry point, while running directly from reset causes the program counter to be loaded with the reset vector from flash location 0x00000004. Using CCS, verify that location 0x00000000 contains the initial stack pointer value and that location 0x00000004 contains the entry point address of the code (plus 1).