• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 83 subscribers
  • Views 433 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.

Compiler/TMS320F280049C: F280049 software reset

Wolfgang Burger
Prodigy 220 points
Part Number: TMS320F280049C


Tool/software: TI C/C++ Compiler

Hi All,

we are using a custom bootloader in our device and we want to be able to reset the running device to the bootloader. I wanted to use a modified ExitBoot method from the Boot ROM which I am already using to enter the application from the bootloader. Then I realized that this method is not feasable since we are using locking of registers which wouldn't be unlocked this way.

In the past we were using the WD to trigger a full reset with the F28069 but I hope there would be an alternative solution to that. Otherwise it wouldn't be able to detect a watchdog which really occured in the last run of the application to handle some error logging. Is there a usual way how to do a software reset?

Best regards

Wolfgang

  • 0
    TI__Guru* 95315 points

    I presume your custom bootloader is in flash. Right now, how do you decide whether to execute your application or your custom bootloader? I didn’t understand what you meant by " Then I realized that this method is not feasible since we are using locking of registers which wouldn't be unlocked this way." Please clarify. 

    The different reset sources are summarized in Table 3-2 in page 89 in SPRUI33C. Is it feasible to write a unique value in a RAM location and then initiate a WD reset (to invoke the custom bootloader) to differentiate between a genuine WD reset and a reset deliberately triggered to run the custom bootloader?

  • 0 in reply to Hareesh Janakiraman
    Prodigy 220 points

    Yes the Bootloader is located in the flash and the Boot ROM is configured to boot to the entry point of the Bootloader. The custom bootloader then starts communication and if no tool halts the bootloader it jumps to the application entry point. During runtime it should then be possible to switch between bootloader and application. By triggering the reset it should also be possible to get out of an error state which also locks some registers to achieve a safe state. Now this would not be possible with the ExitBoot Code taken from the Boot ROM sources.

    For the RAM approach I have to admit I missed that the initialization of the RAM is stated to happen on a POR. Since it seems I did not miss a specific software reset I could trigger I will try the approach using the WD with a specific value in RAM. Thanks for the help.