Debugging RT1064 via JLink

cancel
Showing results for 
Search instead for 
Did you mean: 

Debugging RT1064 via JLink

875 Views
nplayle
Contributor I

Hi, 

 

This is kind of a continuation of the previous post (https://community.nxp.com/t5/i-MX-RT/Debug-without-blowing-efuses-setting-efuses-from-J-Link/m-p/126...). 

 

I cannot get reliable debugging via JLink from MCUXpresso. The behaviour is as follows:

  1. On launching the debugger for the first time, it will open up the Jlink programming dialog for a few seconds, then it will close and the program will not run. 
    1. The Jlink output script seems to have some errors in it and then an eventual timeout when erasing sectors

 

 

 

ERROR: Timeout while erasing sectors, RAMCode did not respond in time. (PC = 0x00000000, CPSR = 0x00200300, LR = 0x81000000)!
Failed to erase sectors

 

 

 

  • On launching the debugger for the second time, it does correctly program but does have an error in it too? 

 

 

 

Core did not halt on reset vector. Assuming faulty image.
Resetting and halting core on image verification value read.
Core did not halt after reset step 1

 

 

 

  • When this happens, the debugger does not stop at main and seems to randomly pick a breakpoint it wants to stop at (it does successfully stop at breakpoint 3 that was set. restarting the core via MCUXpresso does stop at the first breakpoint. 

When debugging, I consistently bounce between these 2 states. For example, after a failed load, the next load will always succeed (insofar as you can call that success). However, the next load will fail in one of two ways:

  1. If I do not change anything in the source files, the debugger gets into a weird state where it stops responding altogether and I have to disconnect / reconnect it from USB and close / reopen MCUXpresso. 
  2. If I do change the source files, I get back into state 1 above, where the load fails due to RAMCode timeout, then the next load 'succeeds'. 

 

This is really getting to be annoying, so far it has been 2 days and we don't have a way to reliably hook a debug session to our board. 

The debugger connections are as follows:

Schematic Pin NameJ Link PinPin Name
NXP RT1064 Pin
VDD_3V31VTref 
GND4GND 
NXP_JTAG.TMS7SWDIOGPIO AD B0 06
NXP_JTAG.TCK9SWCLKGPIO AD B0 07
NXP_JTAG.TDO13SWOGPIO AD B0 10
Solder to RST node Rt / C1615RST\POR / M7

I have also tried hooking up the RST pin from the J link to TRSTB / GPIO AD B0 11 on the NXP and that made the debugger unable to connect. 

I have attached a debug launch file that I tried to use, but I have tried various settings in the launch file and they don't seem to have any effect. 

e.g. both checked / unchecked versions of:

nplayle_0-1618352682678.png

nplayle_1-1618352703735.png

 

Is there something I'm missing? Can anyone confirm they have successfully used MCUXpresso and a JLink to program / debug an RT1064's internal SPI flash? 

 

Edit: More info:

I found someone on the segger forums with the exact same issue as me, but I don't see a resultion:

https://forum.segger.com/index.php/Thread/7264-ABANDONED-Timeout-while-erasing-sectors/

I'm using a J-Link base which doesn't support external memory programming - can anyone confirm if the Jlink base works with the RT1064?

Also, for what it's worth, we're developing with the RT1064CVL5B, whereas the SDK only has the option for RT1064CVL5A, though I'm not sure what difference that would make, if any. 

Thanks,

Nick

 

 

Labels (1)
0 Kudos
4 Replies

852 Views
jeremyzhou
NXP TechSupport
NXP TechSupport

Hi,
Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
1) Is there something I'm missing? Can anyone confirm they have successfully used MCUXpresso and a JLink to program/debug an RT1064's internal SPI flash?
-- It's able to debug the RT1064 in the MCUXpresso with Jlink, so I guess the problem may be related to the Jlink debug tool, you can try a Jlink-plus tool.
2) RT1064CVL5B is the later version of the RT1064CVL5A.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

 

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos

847 Views
nplayle
Contributor I

We don't have access to a j link plus, hence the j link base... If anyone can confirm the issue is with the base vs + we'd be happy to update, but u less we can prove its the cause of a problem it seems kind of silly to waste 400$ to update our debuggers when it might not solve anything. 

 

 

I know the B version is the updated A version, but the SDK only lists the A version. Can you confirm the SDK supports both the A and B version?

0 Kudos

843 Views
jeremyzhou
NXP TechSupport
NXP TechSupport

Hi,
Thanks for your reply.
I try to use a J-link base (V8.00) for a test, it can recognize the Cortex-M7 core in the J-link commander.
However, it fails to enter debug mode in the MCUXpresso IDE.
To be prudent, you can contact the Segger to confirming.

The SDK library definitely supports both the A and B versions.

Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

 

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos

839 Views
nplayle
Contributor I

Thanks - I'm waiting for my account to be approved in order to ask there. 

 

You had previously said that the j link works - does the j link plus with version 8.00 work? Or perhaps it's broken in a recent update and an older version works? I did update my j link but I can't remember from which version (and there were other issues in the way at the time). I'll give some older versions a test tomorrow. 

0 Kudos