imx93evk zephyr flashing jlink

[zefox]

Hi everyone, 

I am trying to get my brand spankin' new imx93evk board to work with a basic zephyr example. I am trying to get it to flash by following these two lines from the i.MX93 EVK board webpage (https://docs.zephyrproject.org/latest/boards/nxp/imx93_evk/doc/index.html

# From the root of the zephyr repository
west build -b imx93_evk/mimx9352/a55 samples/synchronization
west flash

((.venv) ) fox@ubuntu2204:~/zephyrproject/zephyr$ west flash
-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner jlink
-- runners.jlink: JLink version: 8.46
-- runners.jlink: Flashing file: /home/timon/zephyrproject/zephyr/build/zephyr/zephyr.bin
FATAL ERROR: command exited with status 1: /opt/SEGGER/JLink_V846/JLinkExe -nogui 1 -if swd -speed auto -device MIMX9352_A55_0 -CommanderScript /tmp/tmp3mpcn6xdjlink/runner.jlink -nogui 1

i am not really sure what i am doing wrong, i have tried the regular emmc boot mode where i stop it in u-boot, then run:

dcache off

 then flash. Also i have tried putting it in the Serial Downloader mode. But i keep getting the same error. 

any help would be greatly appreciated

with kind regards, fox

[zefox]

trying to continue to debug this, i found out when i run it from the emmc. Then try to even connect with my jlink, I get this output:

u-boot=> dcache off
u-boot=>
U-Boot SPL 2024.04+gde16f4f1722+p0 (Sep 02 2024 - 10:44:35 +0000)
SOC: 0xa1009300
LC: 0x2040010
PMIC: PCA9451A
PMIC: Over Drive Voltage Mode
DDR: 3733MTS
M33 prepare ok
Normal Boot
Trying to boot from BOOTROM
Boot Stage: Primary boot
image offset 0x0, pagesize 0x200, ivt offset 0x0
Load image from 0x4f400 by ROM_API
NOTICE: TRDC init done
NOTICE: BL31: v2.10.0 (release):android-14.0.0_2.2.0-rc1-1-g28affcae9
NOTICE: BL31: Built : 10:35:32, Aug 29 2024

U-Boot 2024.04+gde16f4f1722+p0 (Sep 02 2024 - 10:44:35 +0000)

Reset Status: WDOG3

CPU: NXP i.MX93(52) Rev1.1 A55 at 1700 MHz
CPU: Industrial temperature grade (-40C to 105C) at 42C

Model: NXP i.MX93 11X11 EVK board
DRAM: 2 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C2 0x52]
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C2 0x51]
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C2 0x50]
Core: 235 devices, 37 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

[*]-Video Link 0adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c
fail to probe panel device hdmi@3d
fail to get display timings
probe video device failed, ret -19

[0] lcd-controller@4ae30000, video
[1] dsi@4ae10000, video_bridge
[2] hdmi@3d, panel
adv7535_mipi2hdmi hdmi@3d: Can't find cec device id=0x3c
fail to probe panel device hdmi@3d
fail to get display timings
probe video device failed, ret -19
In: serial
Out: serial
Err: serial

BuildInfo:
- ELE firmware version 1.2.0-38f309fe

switch to partitions #0, OK
mmc0(part 0) is current device
UID: a4f9422fa84948c19b3167059fb8438a
flash target is MMC:0
Net: eth0: ethernet@42890000, eth1: ethernet@428a0000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
u-boot=> mw.l 0x42490000 0x0
u-boot=> dcache off
u-boot=>
U-Boot SPL 2024.04+gde16f4f1722+p0 (Sep 02 2024 - 10:44:35 +0000)
SOC: 0xa1009300
LC: 0x2040010
PMIC: PCA9451A
PMIC: Over Drive Voltage Mode
DDR: 3733MTS
M33 prepare ok
Normal Boot
Trying to boot from BOOTROM
Boot Stage: Primary boot
image offset 0x0, pagesize 0x200, ivt offset 0x0
Load image from 0x4f400 by ROM_API
NOTICE: TRDC init done
NOTICE: BL31: v2.10.0 (release):android-14.0.0_2.2.0-rc1-1-g28affcae9
NOTICE: BL31: Built : 10:35:32, Aug 29 2024

so the watchdog might be interfering. I am just not sure how to get this to work?

[Manuel_Salas]

Hello @zefox 

I hope you are doing ver well.

Unfortunately, this support channel does not provide support for Zephyr.

Also, If you have your binary or elf file compiled, you can try to load with remoteproc or in U-boot. 

Best regards,

Salas.

[zefox]

Hi @Manuel_Salas 

thanks for the response! 

that’s unfortunate… is it possible then to debug the application when i have started it from u-boot or remoteproc?

[Manuel_Salas]

Hello @zefox 

It should be possible in U-boot.

Please take a look to the chapter 4 Prepare the board for the debugger of AN14120 Debugging Cortex-M with VS Code on i.MX 8M, i.MX 8ULP, and i.MX 9, there is explained how you can debbug it with VSCode.

Best regards,

Salas.