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.
Hi, I have a Mini54zde chip in an application. I programmed it and everything was well quite a few times. Recently I uploaded a code revision and I think I boot looped the core. It starts and reboots almost immediately causing keil to display no target connected or internal command error.
How can I halt CPU execution immediately at start so that I can flash new code.
Perhaps you can "connect under reset", look at what options your debugging pod provides, or strap the chip so it doesn't run your code??
Is there a link to break connection to external memory? ie CS pin
I've tried connect under reset with hardware reset and vectreset. Also openocd + st link utility. Openocd connects, gets chipid and then loses connection.
I had hoped for a CS type pin to stop execution but its a QFN33 package and I don't see a pin which would do it:
see below, zde is the same
img15.hostingpics.net/.../624907min54zanpinout2.jpg
Doesn't sound very Keil.
I guess you'll need to figure out how to select the boot rom modes, IAP/ISP, etc. Look at what tools Nuvoton offers.
Would suggest you put a trap-door in your code in the future so you can sense a GPIO state early in the reset process and go into a safe mode.