2296631_en-US

[#1]

Unable to debug i.MXRT1064 custom board.

Hi,

      I'm getting "Break at address "0x20d102" with no debug information available" message while trying to run my code in debug mode.

      I'm using i.MXRT1064 custom board and programming it using, LinkServer LPC-Link2.

      This board was working earlier without issue but now all of a sudden, this message appears.

       I'm tried Release mode. I can successfully flash my board with the release code but then it seems the program doesn't run. I don't see any output, either from serial terminal or from display.

      I also tried programming this board using Secure Provisioning Tool but it still doesn't work. 

       Can anyone help on where to focus or any leads for this issue?

Re: Unable to debug i.MXRT1064 custom board.

Hi MayLiu,

       Thanks for your response.

        Earlier, I did try that setting as suggested by you, but the IDE prompted an error (Failed to execute MI command: -target-download) when try to debug. I have attached a snapshot of that error for your reference.

        Going back to the previous message, I wish to add that when I checked the address of where the current program is executing, it was showing that the code is in ROM region (address 0x20E35A). So somehow the code is unable to reach/start application code and is struck in ROM. Is my assumption correct? Can there be such a scenario?

Re: Unable to debug i.MXRT1064 custom board.

Hi @nxpsachve ,

Thank you so much for your interest in our products and for using our community.

1: Please try select Link application to RAM, then debug again.

If your application can run successfully from RAM, please set the board as Serial Downloader mode, and then use the Secure Provisioning Tool to program your board by UART1 or USB1.

If your application  fails to run, I suggest you using an oscilloscope to check your board the power‑on sequence.

Wish it helps you.

Best Regards

MayLiu

Re: Unable to debug i.MXRT1064 custom board.

Hi @nxpsachve ,

I do not think MCUXpresso IDE  change BOOT configuration,  Boot behavior on NXP RT is determined by hardware boot config and boot mode pins. 

Since the target can be detected in Serial Downloader mode, this indicates that the ROM is still running correctly. As a next step, you could:

• Perform a full chip erase,
• Switch the board to Internal Boot mode, and
• Try reconnecting with MCUXpresso IDE for debugging.

Alternatively, you may also use the MCUXpresso Secure Provisioning Tool to program the application image.

Best Regards

MayLiu

Re: Unable to debug i.MXRT1064 custom board.Hi MayLiu,

Thanks for your suggestion.
I would like to check if there are any such setting/configuration within MCUXpresso that can alter or impact the BOOT Conf? Just to rule out the IDE.
The link server is able to detect the target when in serial download mode.Re: Unable to debug i.MXRT1064 custom board.

Hi @nxpsachve ,

Thanks for your updated information.

Based on the information you provided, it is possible that the CPU is currently executing code from the Boot ROM rather than your application code.

I would suggest checking the BOOT CFG and BOOT mode pin settings, ensuring that the device is configured to boot from user flash.

You may also try to set your board as serial downloader mode and then connecting via J-Link to confirm whether the debugger can  detect and communicate with the target.

Best Regards

MatLiu