Reply by Peter Scholz June 29, 20072007-06-29
fvds72@gmail.com schrieb:
> Dear All, > > I've made an image, which when no password (0xFFFF's) on CSM are > programmed, boots fine. But when a password is set in the CSM it > doesn't run. And because I can not use the debugger I have no idea > what is happening. Who has a idea what could be causing this? > > Greetings Frank >
From a manual: "Should the device be unsecure to run application code? Yes. The device must be unsecure in order to be able to execute code out of on-chip Flash/ROM memory. Under what conditions is the device unsecure? A device is unsecure when the device comes up in the intended application mode in which code is executed from on-chip flash/ROM, without JTAG connector connected�i.e., the device is brought up in �microcontroller� mode upon reset (with the on-chip ROM bootloader disabled). Note that this is the typical usage of the DSP in an end-product. Should I incorporate routines to �unsecure� the device in my application code? There is no need to incorporate routines to �unsecure� the device in your application code. Recall that the device comes up as �unsecure� when you power it up in �microcontroller� mode (without JTAG connector connected/with the on-chip ROM bootloader disabled). Unsecuring is necessary only when you need visibility to ROM/Flash on a currently secured device."
Reply by June 29, 20072007-06-29
Dear All,

I've made an image, which when no password (0xFFFF's) on CSM are
programmed, boots fine. But when a password is set in the CSM it
doesn't run. And because I can not use the debugger I have no idea
what is happening. Who has a idea what could be causing this?

Greetings Frank