• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 82 subscribers
  • Views 307 views
  • Users 0 members are here
Support feedback
Options
Options

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.

Original question:

TMS320F280025C: Perform watchdog reset

TMS320F280025C: TMS320F280025C watchdog reset

Jarold Gonzalez
Prodigy 70 points
Part Number: TMS320F280025C

Hello,

I’m performing a reset the watchdog, the reset is performed correctly but is starting at the wrong address. I read a recommendation in this forum that I should modify the content of 0xD00 and put the 0xA500_0000 so the board starts correctly. However after performing a reset the the code gets stuck in the startup, please see screenshot below, any thoughts ? 

Thanks,

  • 0
    TI__Guru** 113875 points

    Hi,

    The PC points to RAM location so it must be your application code. You need to step through the code to see what condition is causing CPU to stuck there.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 70 points

    After the reset the breakpoints are not working properly in CCS, I have added  -- ESTOP0; -- to stop the core at the beginning of my main function however the debugger does not stop there, any thoughts ? 

  • 0 in reply to Jarold Gonzalez
    TI__Guru** 113875 points

    Not sure what do you mean by "breakpoint" not working after reset. Are you running the code from RAM or Flash ? If you are loading it in RAM then it'll not work because the value you are writing at 0xD00 is for Flash boot. 

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 70 points

    I'm running from Flash. I was trying to stop the code after the reset so I can debug it, I added an infinite loop to hold the uC at the beginning of my main but it seems that the branching to RAM happens earlier. 

    Do you have time for a call to discuss this issue?

  • 0 in reply to Jarold Gonzalez
    TI__Guru** 113875 points

    We discuss it offline and will provide you update by end of the day today.

  • +1 in reply to Vivek Singh
    TI__Guru** 113875 points

    Hi Jarold,

    I see what is wrong here. You are setting the value at 0xD00 incorrectly. 0xA5000000 is 32bit value at 0xD00 address but you are setting 16bit value hence its not working. In case of 16bit memory view , you need to write 0xA500 at address 0xD01. 

    Please try this and hope that fixes the issue.

    Regards,

    Vivek Singh