I.MX RT 1052 Dev board remote connection issue

[Aveld2]

Hello guys, have some troubles here…

We are trying to apply some NXP dev. boards to our hardware remote access service (all-hw.com), we already made it for lot of STM boards and now start with NXP, and face some strange MCUExpresso IDE  behavior in terms of remote debugging.

Testing environment:

• Server (Windows 10 PC) with running SEGGER J-Link GDB Server V6.96 :

• Client also Windows 10 PC with MCUXpresso IDE v11.3.0 [Build 5222] [2021-01-11]

SDK for I.MX RT 1052 Processors

Build the project(could be any example), and configure the debug is:

Trying that gives us an error - “localhost2331: No connection…”

and that’s strange because we are expecting something like “target-select remote” but not «localhost», so it looks like IDE doesn’t try to connect to the remote at all

To check overall connectivity we tried the direct connection to the debug server via telnet:

And it worked, so question is – how to make that happens from the IDE

• Main instructions come from here: Remote Debugging with USB based JTAG/SWD Debug Probes | MCU on Eclipse
• The physical debugger is: J-Link EDU Mini - SEGGER - The Embedded Experts
• The Target board is:
  • ARM Cortex-M7 VisionSOM-RT (SLS12Rx) - system on module from SoMLabs
  • ARM Cortex-M7 VisionCB-RT-STD - carrier board from SoMLabs

Would be really happy to get some opinions here!

[Aveld2]

Any ideas?...

[FelipeGarcia]

Hi,

Please give me some time to test this myself. I will let you know any progress.

Best regards,

Felipe

[Aveld2]

Hello Felipe!

Any leads so far?

[FelipeGarcia]

Hi,

I have contacted the colleague that wrote the blog you are referring and he mentioned that it should work correctly.

• Please make sure you are not using the ‘blue’ debug button as this will revert to a USB based probe.
• There was a small issue with the blog that asked you to use Host PC IP instead of server PC. This was already fixed so please make sure you are using Server PC IP.
• If you have any extra firewalls, please try disabling them as this could be blocking remote debugging.

Best regards,

Felipe