• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 134 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.

TMS320F28379D: Controller behaving improper in CHIL

Komal Singh
Prodigy 10 points

Part Number: TMS320F28379D

Tool/software:

Dear Sir/ Ma'am,

I am working by connecting controller in loop with the opalrt. When I run some algorithm in the controller in loop with opalrt, it shows correct response for the first time. But when I burn the same code in the controller again it again shows the samd output even without providing any input from the opalrt analog out pins. why is this happening?. The controller should only respond when the input come from opalrt pins but it is providing the previous run output before running the simulink model in Rtlab, Is there any bug in the controller or the controller is storing the previous inputs? . I am definetly reseting the board in the wait boot mode using uniflash as well as the reset buttion also before reburning the code. Please provide solution.

Thanks,

Komal Singh

Phd Scholar 

IIT Delhi

  • 0
    TI__Mastermind 36526 points

    Hi,

    Komal Singh said:
    But when I burn the same code

    Are you writing the FLASH or the RAM? 

    Komal Singh said:
    it again shows the samd output even without providing any input from the opalrt analog out pins. why is this happening?

    If you do not power cycle the microcontroller, the volatile memory (RAM) where your data is probably stored will not be erased. I assume that you are declaring some objects in volatile memory, but are leaving them uninitialized until the control algorithm runs and fills the object with data. 

    If this is causing a problem, there should be two ways to work around this: 

    1. Power cycle the device between runs, this will erase the volatile memory.

    2. For the data that you want to be cleared every time, make sure that your software initializes it to the desired state during start up.

    Best Regards,

    Ben Collier