We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I use CRP3 function in my firmware with MCB2300 demo board. When I download it to MCB2300, then I can't upload another firmware again. How do I solve this problem ?
Thank you !!
I was almost doing the same thing. But I was lucky, I didn't choose CRP3.
I think that, now, you have an USB bootloader on your MCB2300, so you can download a new Application from your PC to your MCB2300 via USB line. Then your new Application should have the ability to do the IAP to erase/write 0x000001FC. After that, your MCB2300 should return to the normal state.
I have download a test app in MCB2300 without any IAP function and it is just a simple LCD demo. So everytime when I boot up MCB2300, it just run this LCD demo.
Hi Edward,
The download function of USB Bootloader should be able to be enabled/triggered many times, unless you erase it.
Do you know what is your "Update Entry Pin"? Do you have a button for your "Update Entry Pin"?
I use the P0.6 for Update Entry Pin. But I pull down this pin before boot up MCB2300. It still go to my LCD demo and it can't stop in Bootloader mode. Because if it go to Bootloader mode and update folder will show, but it is not now.
I am sorry to tell you that;
AN10759 USB secondary ISP bootloader for LPC23xx Rev. 01 â€" 16 October 2008 Application note
Page 7, Table 1. Code Read Protection (CRP)
CRP3 ENABLD
The user flash content cannot be read or updated.
The USB bootloader ignores the Entry Mechanism (Update Entry Pin) and always executes the user application if present. If user application is not present then "Update" mode is entered.
It has been damaged. Both your ARM7 SOC and your software are set to a state that you don't want.
Mmmmm.....
Personally, I think the USB secondary ISP bootloader for LPC23xx example from NXP is danger.
Its behavior of CRP3 destroys the last chance to update the ARM7 SOC.
If you have some time, you should futher check the documents and source codes to see if there is still some way to rescue your MCB2300.
Thanks for your help. I think that I need to change one new 2378 chip for MCB2300.