Hello
Since we are working with the RT1060, we often ran into a situation, where we could not access the CPU with the debugger anymore. It was always some kind of software bug during development.
The problem is, that we are developing the software in flash memory. And when such faulty software is in flash, it keeps booting each time after power up and locks out the debugger again, so that it is not possible to erase that software anymore.
The only way to get out of this situation, is to change the boot mode from SPI flash to something else. Then it was again possible to access the cpu with the debugger and erase the flash.
We have now found a way to easily reproduce this situation on a RT1060 dev board. We attached a sample project for this. We reproduce that situation by trying to access the PHY, while the ENET peripheral is not enabled yet.
What is the reason that the debugger can't accesss the CPU anymore in such a situation? We do not experience this with other ARM processors.
Is there any other way to get access again, without need to change the boot mode?
Thanks,
Daniel