[SOLVED] IMX8MPlus Cortex-M7 Support

Robster · Feb 4th 2021, 9:56am

Hi,
I'm currently trying to connect to the Cortex-M7 module on the new (fresh out of the owen) IMX8MPlus SoC.
I've been unsuccessful with the more generic approach of using Device "CORTEX-M7", JTAG & SWD interfaces:
RESET (pin 15) high, but should be low. Please check target hardware.
Is there anything I can do to get around this? An early "iMX8M Plus Cortex-M7 J-Link script" laying around somewhere

I've had no problems working/debugging on a MIMX8MQ6_M4 device.

And in the case someone affiliated with SEGGER happens to read this, it would be interesting to know when official M7-support for IMX8MPlus can be available.

Hälsningar
Robert

SEGGER - Fabian · Feb 4th 2021, 11:30am

Hi Robert,

Regarding the issue:
i.MX8 support was implemented by NXP.
I would suggest to contact NXP support regarding this.

Robster wrote:

And in the case someone affiliated with SEGGER happens to read this, it would be interesting to know when official M7-support for IMX(MPlus can be available.

As a SEGGER software engineer I would say I am somewhat affiliated

J-Link has general support for the ARMv8-A/R architecture.
This means Cortex-A53, A55, A72, ... cores are already supported.

However, here is the pitfall:
For most v8-A based devices you need special connect, reset, ...
sequences so just because the core is supported does not mean that
the device is working out-of-the box.
You may need to create a J-Link script file as long as we do not
list a particular device as being supported.

This comes as no surprise.
Most vendors (and NXP is no exception here) design these big
devices with the goal to have a Linux running on it.
The documentation about the debug interface is next to
no-existent, the standard answer is: „the only documentation we
can provide is the source of the Linux port“, ...
Last but not least, as most people are running a Linux on such
devices, they don‘t need a debug probe at all, so there is little
business for SEGGER here.

The bigger i.MX devices with the v8-A 64-bit cores are still on
our list, but do not have priority.
I cannot give you any exact schedule for the extended v8-A support
but most probably not this year. Schedules are already quite
filled with new devices that came out and are coming out this
year.

Does this answer your questions?

Best regards,
Fabian

Robster · Feb 4th 2021, 1:02pm

Thanks for your speedy reply Fabian.
I too fall into the category of people running Linux on the "big" cores and therefore don't expect J-Link support for those.
But we are discussing using 1 (or perhaps 2) AXX-cores in an AMP solution and in that case it would be interesting hooking up the ol' trusty J-Link.

But for now my main/and only J-Link-interest is geared towards the onboard MCU's (Cortex-M4/M7) on these IMX8 SoCs.
From what you are telling me I should be able to get support from NXP, so I'll reach out to them.

Finally, just a thought:
Most of the i.MX8M SoC's have an extra Cortex-M4 onboard, except for i.MX8MN (Nano), like i.MX8Plus also has a Cortex-M7 onboard.
Since MIMX8MN6_M7 is in the current J-Link device list, is this something the could be used in my endeavor to connect with the i.MX8Plus Cortex-M7?

Hälsningar
Robert

SEGGER - Fabian · Feb 12th 2021, 9:05am

Hi Robert,
It might.

NXP implemented the i.MX8 devices via J-Link Script file.
The script files are shipped together with the J-Link Software Pack
under "%JLinkInstDir%\Devices\NXP\".

For further support you would have to contact NXP.

Hope that helps!

Best regards,
Fabian

Share