MCUXpresso demo_apps on i.MX8QM EVK

cancel
Showing results for 
Search instead for 
Did you mean: 

MCUXpresso demo_apps on i.MX8QM EVK

350 Views
ravi_kohli
Contributor IV

Hi,

I'm using the 'Getting started with MCUXpresso SDK for i.MX 8QuadMax' instructions with SDK_2.5.2_MEK-MIMX8QM and ARM GCC toolchain (gcc-arm-none-eabi-9-2020-q2-update-x86_64-linux) on a Linux host (Ubuntu 18.04) to build the demo_apps (hello_world). I'l like to run the app on the EVK so I have flashed an SD card (as described) with the new .bin images generated using the targets from imx-mkimage: flash_b0_cm4_0, flash_b0_m4s_tcm, flash_m4_tcm_ddr, flash_m4s_tcm but haven't seen the app boot up or run on the Cortex-M4s on my i.MX8QM EVK. Is there any limitation or can someone clarify the build procedure and SD card image flash ?  I'm seeing the following console message: "Normal Boot Trying to boot from MMC2_2". Thanks.

Tags (2)
4 Replies

209 Views
jamesbone
NXP TechSupport
NXP TechSupport

Hello,

In order to get the SDK examples working, you need to have first Uboot in your SDCard in order to boot the device and then you flash the binary of the SDK example, let share a web page where is the instructions to on how to do it

Enabling Cortex-M4 on i.MX 8QXP MEK - i.MXDev Blog 

0 Kudos

209 Views
ravi_kohli
Contributor IV

Hi James, Thanks for the reply. I used the imx-image-full-imx8qmmek.sdcard (from L5.4.24-2.1.0_images_MX8QMMEK) to boot my i.MX8QM MEK and followed the web page instructions. On the debug console when I TFTP the image M4 image I see the following error message running the examples.

I likely picked the wrong address range for the M4. What are the valid ranges, general info I can read about M4 ?

Thanks

=> setenv serverip 192.168.86.43

=> tftp 0x38FE0000 m4_image.bin (ddr or tcm version)

=> bootaux 0x38FE0000
## Starting auxiliary core at 0x38FE0000 ...
Power on M4 and MU
Copy M4 image from 0x38fe0000 to TCML 0x34fe0000
"Synchronous Abort" handler, esr 0x96000210
elr: 0000000080077208 lr : 00000000800236ec (reloc)
elr: 00000000ffeef208 lr : 00000000ffe9b6ec
x0 : 0000000034fe0000 x1 : 0000000038fe0000
x2 : 0000000000020000 x3 : 0000000000000000
x4 : 0000000000004000 x5 : 0000000000020000
x6 : 00000000ffef8098 x7 : 000000000000000f
x8 : 00000000fd687c30 x9 : 0000000000000008
x10: 00000000ffffffd8 x11: 00000000fd6a6518
x12: 0000000000000004 x13: 0000000000000200
x14: 0000000000000004 x15: 00000000ffffffff
x16: 0000000000002080 x17: 0000000000000000
x18: 00000000fd695db8 x19: 0000000034fe0000
x20: 0000000038fe0000 x21: 0000000000000000
x22: 000000005d1c0000 x23: 0000000000000116
x24: 0000000000000129 x25: 0000000000000000
x26: 0000000000000000 x27: 0000000000000000
x28: 00000000fd6a29b0 x29: 00000000fd687d70

Resetting CPU ...

resetting ...

0 Kudos

209 Views
jamesbone
NXP TechSupport
NXP TechSupport

Hello,

You need to try to put the M4 image into RAM Address,  like

0x88000000
0 Kudos

209 Views
ravi_kohli
Contributor IV

Thanks James, I have been able run M4 demo_app on my EVK.