iMX8MM Custom board PROBLEM [URGENT]

cancel
Showing results for 
Search instead for 
Did you mean: 

iMX8MM Custom board PROBLEM [URGENT]

Jump to solution
404 Views
Contributor II

Hello all,

We've made a new custom PCB based on iMX8Mini

  • 4 x Cortex A-53
  • 1 x Cortex m4

We've tested all voltage and every element got his good power.

Before making the new custom board we were able to get a hand on the iMX8MM EVK board, and when plugging the USB the kernel detects it, and show NXP in dmesg and lsusb and everything was great.

But now we are not able to detect the new custom board.

We tried to debug the Cortex a53 and m4 with JLink EDU (version 10) with openocd, and it detects everything similar like it detects it from the EVK.

NOTE: openocd supports imx8mq.cfg but we have no other way to do it.

Here's the output of some commands :

  • targets on openocd detects the 4 cores of A-53 and the m4 core:

imx8-1.png

  • reg showing registers too:

imx8-3.png

We think that the issue stopping the linux from detecting the USB ports is that the custom board's Cortex A53 has no bootloader.

We have generated an imx-boot with Yocto for iMX8 that contains:

  • ATF (Arm trusted firmware)
  • HDMI
  • DDR3L
  • ...

So we need to flash the imx-boot into the Cortex-A53 flash so that the USB can enumerate with the linux host or any other host.

We tried to load the imx-boot binary with openocd load_image and it fails with this error:

load_error.png

We do not have an idea on what address we should use either, we tried the Cortex A53 Boot ROM addresses from the datasheet too but we got the same error.

aaaa.png

We know that the Cortex-M4 has no flash size, so it has to be into the Cortex-A53, but we need to find out how to install the imx-boot in there so that it can load the firmware and set it up for USB enumeration with any other host so that we can detect it with the toot : UUU (Universal Update Utility) which we use for flashing the eMMC/SD like we're used to do with the EVK board.

We need an urgent help if possible.

0 Kudos
1 Solution
131 Views
Contributor II

Hi,
we found the solution for the custom board :

The USB was connected to USB 2 and we changed the hardware connection to USB 1 then we can detect the NXP board on our USB host machine 

Thank you !

View solution in original post

0 Kudos
1 Reply
132 Views
Contributor II

Hi,
we found the solution for the custom board :

The USB was connected to USB 2 and we changed the hardware connection to USB 1 then we can detect the NXP board on our USB host machine 

Thank you !

View solution in original post

0 Kudos