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.
Hi!
I have programmed a CSM password, and everything seemed to work fine (PWM frequency for example) until I've started the debugger and connect to the board, write the password and click unlock. The PWMs are not functional anymore, I mean the frequncy changed from 9KHz to 285Hz.
I've noticed that after I unlock it, PLLCR changes from 0x0010 to 0x0000. And CLKCTL from 0xA505 to 0x0000.
Also if I go in halt, unlock and then run it again I get a reset. The system runs again at the expected frequency, until I unlock it again.
If I change the GEL file and use Unlock_CSM() in OnTargetConnect(), I don't have these problems.
Can somebody explain what does actually the on-chip flash CSM unlock?
Thanks,
Monica
Monica
I'd like to clarify a few things :
- The program from flash works correctly in standalone
- The same program does not work when debugger is connected and device is unlocked
- How is the unlock being done? - via the Onchip flash CCS plug-in or your s/w code or Gel function?
To answer your question, the on-chip flash CSM unlock will only unlock your device. It should not affect any register values.
Hi!
- the program, as much as I can test it without the debugger, runs fine.
- if I just connect and let the device unlocked, it still runs ok.
- I unlock using the on chip flash CCS plug-in.
I found a solution for the moment to unlock it and still have it run correctly after this. I worked on the GEL file.
I've also noticed that if I use the Unlock from Scripts-> CSM-> Unlock, I can unlock the device and it continues to run correctly. But I've tried to lock it back and I got again some error.
Monica