We're having a problem debugging an example application that was supplied with our install of uVision5 and the ARM KEIL MDK.
The example application that we're building is the Blinky_M4 project. It's based on CMSIS-RTOS, and it's an application created specifically for the iMX7D SABRE Board that we have connected to our Colibri evaluation board. In uVision5 we can build the project successfully, but when attempting to debug the generated Blinky_M4.axf file on the device using our ARM KEIL ULINKpro D the following error message is displayed in a ULINKpro – Cortex-M Error dialog box.
Cannot access Memory (@ 0xe00ffff0, Read, Acc Size: 4 Byte)
The ARM KEIL website supplies a list of possible error messages in the ULINKpro User’s Guide online. The suggestion given to resolve this error is to try lowering the maximum clock rate of the JTAG debugger. The default clock rate is 10 MHz. We've set a number of lower clock rates in the Cortex-M Target Driver Setup dialog box for uVision5, but we still receive this error message.
What can we do to resolve this issue so that we can make this work?
Thank you in advance for any help you may be able to provide.
It's always the case with all dual core or tri core boards with Cortex-Mx + Cortex-Ax processors.
As soon as you power up the boot up starts automatically which you can see via serial interface.
In order to first connect with Cortex-M, you would have to stop the boot process, other wise Cortex-A will be active and you can never connect with Cortex-M, unless you repeat the power up process and stop the boot.