How to configure debug target for i.MX RT that flashes the board?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to configure debug target for i.MX RT that flashes the board?

853 Views
mjbcswitzerland
Specialist V

Hi All

I am making my first attempt to use MCUXpresso to debug a target but presently is fails since it doesn't seems to load any code to the board and also doesn't seem to do behave normally when connected (I can't see what it does since it deletes the console window content)

This is what i have done:
1. Tested an i.MX RT 1015 SDK reference using the debug icon that scans for probes and programs. This is OK.
2. Tried with a custom development project that builds in MCUXpresso and generates a binary file that I can load using the NXP MCU Boot Utility v2.2.0 (this runs)
3. Tried adding a debug target by using the debug icon that scans for probes and programs. This detects the problem and connects but look to actually program and, even when operational code is in the QSPI flash, after connecting it lands here:

pastedImage_1.png

Therefore I tried using the GUI Flash Tool in each of the debug configurations.
The first thing I found was that on evkmimxrt1015 debug configuration used a connect scrip but this was missing in the debug configuration created for the custom project. So I manually added

RT1015_connect.scp

but it didn't seem to change anything.

The next thing I noticed is that when I attempt a blank check with the evkmimxrt1015 debug configuration it starts by opening a flash driver (after which teh blank check is correctly performed)

NXP: MIMXRT1015xxxxx
DAP stride is 1024 bytes (256 words)
Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1015_SFDP_QSPI.cfx  <----------
Image 'iMXRT1015_SFDP_QSPI Dec  2 2019 18:58:55'
Opening flash driver MIMXRT1015_SFDP_QSPI.cfx
Sending VECTRESET to run flash driver
Flash variant 'JEDEC_SFDP_Device' detected (16MB = 256*64K at 0x60000000)
Closing flash driver MIMXRT1015_SFDP_QSPI.cfx
flash area 'flash' set, now --base 0x60000000 and --size 0x1000000

But if I attempt the same using the project's debug configuration which was generated it fails since it doesn't load any flash driver:

NXP: MIMXRT1015xxxxx
DAP stride is 1024 bytes (256 words)
find flash area 'flash' - flash area unknown   <---------------------------
( 65) Chip Setup Complete
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

I haven't been able to find how to configure the debug configuration to work with a flash driver and this may be the basic issue.

Afrerwards I attempted manually creating and configuring debug configurations, as well as duplicating operating ones and changing to the target's elf file, but in each case with unsuccessful results.

Therefore:
A: Why does the generated debug configuration not include a flash driver for the target?
B: If the generated debug configuration is not successful how is it possible to configure it so that it operates?

Thanks for any tips to get MCUXpresso debugging working on a custom project.

Regards

Mark

Labels (1)
0 Kudos
2 Replies

728 Views
lpcxpresso_supp
NXP Employee
NXP Employee

This sounds like an issue with your project's memory configuration. Check the "MCU Settings" in project properties - and compare and contrast with your working project. As Con Verse says, there are more details in the MCUXpresso IDE User Guide.

You might also want to read through the blogs available in this forum on using the IDE with the various RT devices (though we don't currently have one for the RT1010, that still on the todo list).

If you are still having problems, please post details of your project's memory configuration.

Regards,

MCUXpresso IDE Support

0 Kudos

728 Views
converse
Senior Contributor V

This is described in Chapter 15 of the MCUXpresso User Guide.

0 Kudos