We have custom i.MX8MN board, we've struggled a bit to get it up.
I can see /dev/ttyUSB0, and I can see the NXP OTG device.
I don't know see any output over the USB0 device. Should I? Should U-boot be present on a new device, i.e. from the NXP factory?ha
When I run UUU I get: "Wait for Known USB Device Appear..." and it just hangs there.
I believe we've set the switches correctly (0001) to allow Download and I've tried other switch settings.
I also have a Digi CCIMX8MN board that our design is based on. It has always had u-boot. But for UUU to successfully run against it I first need to enter uboot and then run fastboot N.
Is this the normal behavior from the NXP factory?
Any pointer appreciated.
Should U-boot be present on a new device, i.e. from the NXP factory?
>what do you mean?
I believe we've set the switches correctly (0001) to allow Download and I've tried other switch settings.
> since your design is based on third party company board, you need double confirm this,
I also have a Digi CCIMX8MN board that our design is based on. It has always had u-boot. But for UUU to successfully run against it I first need to enter uboot and then run fastboot N.
>I'm not sure if I understand your question or not, if you download uboot to the board by uuu successfully, the below log is from nxp imx8mn board
U-Boot SPL 2024.04+gde16f4f1722+p0 (Sep 02 2024 - 10:44:35 +0000)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 3200MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
SEC0: RNG instantiated
Normal Boot
Trying to boot from BOOTROM
Boot Stage: Primary boot
image offset 0x0, pagesize 0x200, ivt offset 0x0
NOTICE: Do not release JR0 to NS as it can be used by HAB
NOTICE: BL31: v2.10.0 (release):android-14.0.0_2.2.0-rc2-0-g7c64d4e86
NOTICE: BL31: Built : 10:35:32, Aug 29 2024
U-Boot 2024.04+gde16f4f1722+p0 (Sep 02 2024 - 10:44:35 +0000)
CPU: i.MX8MNano Quad rev1.0 1500 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 33C
Reset cause: POR
Model: NXP i.MX8MNano EVK board
DRAM: 2 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x52]
SNK.Power3.0 on CC1
tcpc_pd_receive_message: Polling ALERT register, TCPC_ALERT_RX_STATUS bit failed, ret = -62
Power supply on USB2
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
Core: 207 devices, 35 uclasses, devicetree: separate
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... OK
[*]-Video Link 0adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
mxs_video lcd-controller@32e00000: failed to get any video link display timings
probe video device failed, ret -22
[0] lcd-controller@32e00000, video
[1] dsi_controller@32e10000, video_bridge
[2] adv7535@3d, panel
adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
mxs_video lcd-controller@32e00000: failed to get any video link display timings
probe video device failed, ret -22
In: serial
Out: serial
Err: serial
SEC0: RNG instantiated
switch to partitions #0, OK
mmc2(part 0) is current device
flash target is MMC:2
Net: eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
u-boot=>