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

RM48 - Safety code/demo

Emanuele Cardani
Prodigy 80 points

Other Parts Discussed in Thread: HALCOGEN

Thanks for your support.

Your project is working and was really like mine.

I've further investigated my issue. The two projects differ only in the system startup generated with HalCoGen.

I've enabled the safe initialization. Firstly I noticed that CPU hangs in CCM Self Test and in the forum I discovered that CCM cannot be run in Debug Mode.

I commented out the call to CCM test and my code seemed to be running fine except that I was not able to make printf over JTAG but only over SCI (and, I noticed only after, to place break points).

I think this may be related to the CPU reset during self tests. Am I right?

Is there a way I can keep safe init on and use the Jtag for debug? Or am I supposed to disable safe initialization during debug session? Is there a paper or an example that describes the CPU behavior in debug mode? I mean which features are badly affected by the debugger..

About the safe feature:

  • The self test example in the demo software cover all cases? Or can you suggest examples/docs?

During my tests I also got stuck in an infinite loop in memoryInit. Only way to get out of this condition apparently was to turn off the evaluation and restart CCS5.

Any Idea?

Thanks for your support and sorry for bothering you but I just the evaluation board and started to work with.

Regards,

Emanuele Cardani

  • 0
    TI__Mastermind 22375 points

    Emanuele,

    I will try to answer to some of your question and will have to ask some colleague for the rest.

    1] CCM R4 cannot be used in debug mode.

    2] For the printf to work under ccs in the console, you have to have checked: "Enable CIO Function use" as following:

    If not the printf does not print to the console.

    3] During debug, I personally disable almost all safety feature if not mandatory. (even the meminit)
        I usually want or need to check the content of RAM to debug a problem. If the RAM is re-initialized each time, I've lost any kind of history)