MCF52233 - Code protection ?

[Max_Arrow]

Hello all, I would like to know if there is any level of the code protection because I can't erase the memory after that I've protected it. Anybody knows where I configure this?

--
Alban Edit: FSL Part Number must figure in Message Subject line.

Message Edited by Alban on 2007-09-03 09:39 PM

[Marcia]

Hi Max_Arrow,

Please help us by telling us what ColdFire device you are using, and on what board. Is it a Freescale EVB, or your own target. What flash - internal or external to the device.

Bye for now,

Marcia

[Max_Arrow]

Hello Marcia,

I'm using the internal Flash of the MCF52233 in my target board. I've used the M52233DEMO as the reference board.

Thank you

[blackjack]

Hello Max_Arrow,

                            Did you fixed your problem. if it is then could share your solution couse i have the same problem as yours.

Thanks

blackjack

[mjbcswitzerland]

Hi

If the security is enabled it can not be reversed using BDM. A chip erase via the EZport is the only way to unsecure the part (if it doesn't run software that can do thsi when commanded) - this needs an EZport module to be used or another system connected via SPI with the approriate commands.

See the following: https://community.freescale.com/message/38162#38162

Regards

Mark

[Marcia]

Hi Max_Arrow,

Thanks for updating the post with the device. That helps a lot.

Your board has the flash secured.

Did the information in the device Reference Manual, Version 4.0, page 17-31 (pdf page 273) not help? A bulk erase followed by a blank check should be sufficient to unsecure your device.

Bye for now,

Marcia

[a_yelm]

Hi Macia,

I'm in the same spot as Max_Arrow (I think), but I would like to be able to erase/unsecure the internal flash of the MCF52233 using the CodeWarrior Flash Program Utility (from Tools->Flash Programmer menu). It's been working fine up to the point where I enabled the chip secure feature. Now the flash is not reachable for me. Perhaps its just a matter of using the correct .cfg file for target initialization(?).

Bye,

a_yelm