Timeout on flash programming LinkServer CMSIS-DAP

[jfsimon1981]

Good morning,

If you're more familiar than I am, would please someone let me know what the below errors stand for ?

I just try to program an i.MX RT1020 EVK with the builtin J23 micro usb connected to the IDE ... I can see the "Probe", though it won't get too much further away. Spends a couple seconds and reties, but i got several messages from try flash or just connect GDB to running target.

- The board is connected over USB J23 and properly flashes the green LED.
- The CMSIS-DAP probe is properly discovered
- Next step fails with IO exception "Read timed out":
- When starting a programming sessions through the IDE debug/flash request, i see several attempts
- The red led near USB transceiver illuminates, and it seems to try work with controller and flash during 5 seconds and reset back to green led default program
- After multiple attempts, i get a timeout and reset to pre-installed program
- Serial console (putty) works, i see "Sensor device initialize failed!"

Other infos:
- Board is rev A3 (SCH-29856 REVA3)
- J27 and 28 are on
- Power from USB (J1 is connecting 5-6)

Here are different error messages i saw:

IDE terminal messages:

Executing flash operation 'Program' (Program file into flash: evkmimxrt1020_iled_blinky.axf) - Wed Dec 14 11:58:31 CET 2022
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.6 (Oct 3 2022 08:15:46 - crt_emu_cm_redlink build 9)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in /home/jeanfrancois/got/Documents/MCUXpresso_11.6.1_8255/workspace/evkmimxrt1020_iled_blinky/Release/MIMXRT1021xxxxx.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Connecting to probe 1 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Retrying...
redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Reconnected to existing LinkServer process.
redlink server client - failed to receive response (to op 26) from server after 2000ms - Connection timed out (rc 110)
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
redlink server client - failed to receive response (to op 32) from server after 60000ms - Connection timed out (rc 110)
============= SCRIPT: RT1020_connect.scp =============
============= END SCRIPT =============================
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

Error messages popping up:

Read timed out
at com.nxp.mcuxpresso.core.debug.support.linkserver.redlink.client.RedlinkServerClient.receive(RedlinkServerClient.java:978)
[...].redlink.client.RedlinkServerClient.sendReceive(RedlinkServerClient.java:1068)
[...].redlink.client.RedlinkServerClient.sendReceive(RedlinkServerClient.java:1053)
[...].redlink.client.RedlinkServerClient.sendReceive(RedlinkServerClient.java:1040)
[...].redlink.client.RedlinkServerClient.wireConnect(RedlinkServerClient.java:1189)
[...].emulators.jtag.AbstractJtagDiscovery.ideConnect(AbstractJtagDiscovery.java:232)
[...].emulators.jtag.AbstractJtagDiscovery.connect(AbstractJtagDiscovery.java:196)
[...].emulators.jtag.AbstractJtagDiscovery.discover(AbstractJtagDiscovery.java:155)
[...].emulators.TargetDiscovery.jtagDiscovery(TargetDiscovery.java:454)
[...].launch.LaunchScriptUtils.getEmulatorInfo(LaunchScriptUtils.java:257)
[...].launch.LaunchScriptUtils.init(LaunchScriptUtils.java:497)
[...].launch.LaunchScriptUtils.<init>(LaunchScriptUtils.java:165)
[...].launch.LaunchScriptUtils.<init>(LaunchScriptUtils.java:152)
[...].services.TargetDiscoveryService.getTargetDiscovery(TargetDiscoveryService.java:138)
[...].override.LSFinalLaunchSequence$TargetDiscoveryJob.run(LSFinalLaunchSequence.java:124)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Error messages:
02: Failed on connect
Could not connect to core.
31: No connection to chip's debug port
Debugging context: evkmimxrt1020_iled_blinky LinkServer Release

Error messages:
02: Failed on connect
Could not connect to core.
31: No connection to chip's debug port
Debugging context: evkmimxrt1020_iled_blinky LinkServer Debug

Error in final launch sequence:
Failed to execute MI command:
-target-select extended-remote localhost:10989
Error message from debugger back end:
Remote communication error. Target disconnected.: Connection re-initialized by remote target

Failed to execute MI command:
-target-select extended-remote localhost:10989
Error message from debugger back end:
Remote communication error. Target disconnected.: Connection re-initialized by remote target.

An internal error occurred during: "Opening RedlinkServer telnet session...".
Read timed out.
Cannot connect to the server process: redlinkserv (port:3025,3050,3075)

Thanks,

Jean-François

[jfsimon1981]

Hi,

Oddly enough, the USB flashing through J-Link works perfectly fine after a few MCU flashing with the NXP Mcu-Link Pro.

I haven't modified the board firmware. This particular one is at rev.A and now can be handled through the microUSB, doesn't require the JTAG flasher anymore.

That's gonna be a mystery.

For reference, jumpers J25+26 for UART and J27+28 for SW which apply for this rev board
have moved in a recent wiring diagrams.

Regards

Jean-François

[jfsimon1981]

Pavel,

Ok thanks,

Jean-François

[Pavel_Hernandez]

Hello,

I review the information and seems like the MCU is halt I recommend use the NXP-MCUBootUtility-master for do a mass erase.

Best regards,
Pavel

[jfsimon1981]

Pavel,

Ok thanks,

Jean-François

[Pavel_Hernandez · Accepted solution]

Hello,

I find this thread maybe could help you. First Steps with the NXP i.MX RT1020 EVK Board | MCU on Eclipse.

This is the first time testing the RT1020 or you already test it on the blink-led [or other] project before?

If you have more questions, please let me know.

Best regards,
Pavel

[jfsimon1981]

Hi Pavel,

This is my first time with NXP product, yes, i was not familiar with J-TAG either earlier.

I'm familiar with embedded generally, IDE and programming, flashing micro-controllers.

It's a bit sad i can't find your J-Link product, it's out of stock almost anywhere, the same link shown in the thread you posted ... That seems a very neat tight programmer.

I found a similar one, quantity available was very limited, i'm lucky i can get hand on one.

I'll do flashing next week.

If the rom/boot code issue is found & fixed i'll post it back.

Regards

Jean-François

[jfsimon1981]

Thanks,

I believe there's a firmware compatibility issue probably, but i'll get to flash with an external device that recommended.

If time allows i'll also take time to flash boot code, see if that fixes the USB integrated debug/flasher.
Jean-François