Hello,
We are developing an application for NXP RT1061 (custom board) and are experiencing some issues when it comes to debugging.
MCU: MIMXRT1061CVL5B
Flash: IS25LP032D
Debuger: JLink Plus (Firmware: J-Link V11 compiled May 2 2022 08:59:57, Hardware: V11.00)
A complete log and flash configuration is attached.
1. The JLink server seems to have problems halting the mcu after reset, when running and debugging from flash, hinting that we have faulty flash settings.
This causes for example breakpoints in the beginning of main not to trigger. And possibly also other issues as described below.
Log from JLinkServer:
Received monitor command: reset
ResetTarget() start
Core did not halt on flash image verification. Assuming faulty flash settings.
Halting target manually.
ResetTarget() end
What causes this, do we have the wrong flash configuration?
2. We have no problem booting from the flash. However once a program is present in the flash the Jlink Debugger is unable to reprogram the flash. Could be related to issue 1 since if we insert a delay in the beginning of main it works. We have some units which we at the moment are unable to recover because of this.
We suspect that configuring the MPU or something similar to this prevent JLink from uploading its "Ram code" but we have not been able to confirm this. We have however tried to disable the MPU using JLink commander but have not been successful. The FlexRam module has default configuration (128k DTC, 128K ITC, 256K OC).
Log from JLinkServer:
Downloading 2964 bytes @ address 0x60025550 - Verified OK
Downloading 84 bytes @ address 0x600260E4 - Verified OK
ERROR: Failed to prepare RAMCode using RAM
Error while determining flash info (Bank @ 0x60000000)
Writing register (PC = 0x60002308)
3. Starting a debug session takes a long time.
The time from when the program has been written to flash/ram and the triggering of the first breakpoint in main is long sometimes more than a minute. This could for some reason be a related to the application size since we do not experience this issue when running nxp's example applications. Our application is around 400k. This happens both if we execute from ram and flash.
We are using McuXpresso.
What could be causing this? Anything we can do to improve the debugging experience.
Thanks
/Björn
We are developing an application for NXP RT1061 (custom board) and are experiencing some issues when it comes to debugging.
MCU: MIMXRT1061CVL5B
Flash: IS25LP032D
Debuger: JLink Plus (Firmware: J-Link V11 compiled May 2 2022 08:59:57, Hardware: V11.00)
A complete log and flash configuration is attached.
1. The JLink server seems to have problems halting the mcu after reset, when running and debugging from flash, hinting that we have faulty flash settings.
This causes for example breakpoints in the beginning of main not to trigger. And possibly also other issues as described below.
Log from JLinkServer:
Received monitor command: reset
ResetTarget() start
Core did not halt on flash image verification. Assuming faulty flash settings.
Halting target manually.
ResetTarget() end
What causes this, do we have the wrong flash configuration?
2. We have no problem booting from the flash. However once a program is present in the flash the Jlink Debugger is unable to reprogram the flash. Could be related to issue 1 since if we insert a delay in the beginning of main it works. We have some units which we at the moment are unable to recover because of this.
We suspect that configuring the MPU or something similar to this prevent JLink from uploading its "Ram code" but we have not been able to confirm this. We have however tried to disable the MPU using JLink commander but have not been successful. The FlexRam module has default configuration (128k DTC, 128K ITC, 256K OC).
Log from JLinkServer:
Downloading 2964 bytes @ address 0x60025550 - Verified OK
Downloading 84 bytes @ address 0x600260E4 - Verified OK
ERROR: Failed to prepare RAMCode using RAM
Error while determining flash info (Bank @ 0x60000000)
Writing register (PC = 0x60002308)
3. Starting a debug session takes a long time.
The time from when the program has been written to flash/ram and the triggering of the first breakpoint in main is long sometimes more than a minute. This could for some reason be a related to the application size since we do not experience this issue when running nxp's example applications. Our application is around 400k. This happens both if we execute from ram and flash.
We are using McuXpresso.
What could be causing this? Anything we can do to improve the debugging experience.
Thanks
/Björn