HummingBoard Pulse i.MX8M Plus SOM board flash issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HummingBoard Pulse i.MX8M Plus SOM board flash issue

Jump to solution
1,200 Views
krsuresh
Contributor III

Hi Team,

I have the same problem in i.MX8MP board bring up.

Can I get some help on this?

 

Flashing image from ubuntu 

imx-yocto/build-xwayland-imx8mpsolidrun/tmp/deploy/images/imx8mpsolidrun$ sudo uuu -v -d imx-boot-imx8mpsolidrun-sd.bin-flash_evk
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.4.243-0-ged48c51

Build in config:
Pctl Chip Vid Pid BcdVersion

SDPS: MX8QXP 0x1fc9 0x012f [0x0002..0xffff]
SDPS: MX8QM 0x1fc9 0x0129 [0x0002..0xffff]
SDPS: MX8DXL 0x1fc9 0x0147
SDPS: MX28 0x15a2 0x004f
SDPS: MX815 0x1fc9 0x013e
SDPS: MX865 0x1fc9 0x0146
SDPS: MX8ULP 0x1fc9 0x014a
SDPS: MX8ULP 0x1fc9 0x014b
SDPS: MX93 0x1fc9 0x014e
SDP: MX7D 0x15a2 0x0076
SDP: MX6Q 0x15a2 0x0054
SDP: MX6D 0x15a2 0x0061
SDP: MX6SL 0x15a2 0x0063
SDP: MX6SX 0x15a2 0x0071
SDP: MX6UL 0x15a2 0x007d
SDP: MX6ULL 0x15a2 0x0080
SDP: MX6SLL 0x1fc9 0x0128
SDP: MX7ULP 0x1fc9 0x0126
SDP: MXRT106X 0x1fc9 0x0135
SDP: MX8MM 0x1fc9 0x0134
SDP: MX8MQ 0x1fc9 0x012b
SDPU: SPL 0x0525 0xb4a4 [0x0000..0x04ff]
SDPV: SPL1 0x0525 0xb4a4 [0x0500..0x9998]
SDPV: SPL1 0x1fc9 0x0151 [0x0500..0x9998]
SDPU: SPL 0x0525 0xb4a4 [0x9999..0x9999]
SDPU: SPL 0x3016 0x1001 [0x0000..0x04ff]
SDPV: SPL1 0x3016 0x1001 [0x0500..0x9998]
FBK: 0x066f 0x9afe
FBK: 0x066f 0x9bff
FBK: 0x1fc9 0x0153
FB: 0x0525 0xa4a5
FB: 0x18d1 0x0d02
FB: 0x3016 0x0001
FB: 0x1fc9 0x0152
Wait for Known USB Device Appear...
New USB Device Attached at 1:1
1:1>Start Cmd:SDPS: boot -f "imx-boot-imx8mpsolidrun-sd.bin-flash_evk"
100%1:1>Okay (1.797s)
1:1>Start Cmd:SDPS: done
1:1>Okay (0s)
New USB Device Attached at 2:1

 

 

Board Observation


U-Boot 2021.04-lf_v2021.04+g17ff5a3646 (Nov 22 2021 - 01:39:23 +0000)

CPU: i.MX8MP[8] rev1.1 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 29C
Reset cause: POR
Model: NXP i.MX8MPlus LPDDR4 SolidRun board
DRAM: 992 MiB
MMC: FSL_SDHC: 1, FSL_SDHC: 2
[*]-Video Link 0probe video device failed, ret -2

[0] lcd-controller@32e80000, video
[1] mipi_dsi@32e60000, video_bridge
[2] adv7535@39, panel
probe video device failed, ret -2
In: serial
Out: serial
Err: serial

BuildInfo:
- ATF 5782363

switch to partitions #0, OK
mmc1 is current device
Detect USB boot. Will enter fastboot mode!
Net:
Warning: ethernet@30bf0000 (eth1) using random MAC address - be:13:de:0e:92:08
eth1: ethernet@30bf0000 [PRIME]
Fastboot: Normal
Boot from USB for mfgtools
*** Warning - Use default environment for mfgtools
, using default environment

Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot 0; fi;
Hit any key to stop autoboot: 0

## Checking Image at 43800000 ...
Unknown image format!
Run fastboot ...

0 Kudos
Reply
1 Solution
1,142 Views
krsuresh
Contributor III

Hi Sanket Parekh,

Yes, You can close it. Thanks for the response. 

Thanks,

Suresh Kumar R

View solution in original post

0 Kudos
Reply
4 Replies
1,162 Views
Sanket_Parekh
NXP TechSupport
NXP TechSupport
Hi @krsuresh ,
 
I hope you are doing well.
 
Please accept my apologies for delayed answer.
 
Regarding issue i have few queries to ask , which i mentioned below , 
-> Is your image format that you are flashing into the board correct ?
-> Do you only want to load the boot loader ?  because as per what your logs stats , it is looking for Linux image at some location , That you haven't provided.
 
Thanks & Regards
Sanket Parekh
0 Kudos
Reply
1,155 Views
krsuresh
Contributor III

Hi Sanket Parekh,

Thanks for the reply. 

I have fixed the issue, the image was always trying to boot from uSD so I modified the configuration file to fix this.  

Fix details: 

Changed to /dev/mmcblk1p2 from /dev/mmcblk2p2 in file "sources/meta-solidrun-arm-imx8/conf/machine/imx8mpsolidrun.conf"

 

Thanks,

Suresh Kumar R

0 Kudos
Reply
1,147 Views
Sanket_Parekh
NXP TechSupport
NXP TechSupport

Hi @krsuresh 

Thank you for sharing the observations.

Issue is resolved. Can I mark this case to close state?

Thanks & Regards

Sanket Parekh

0 Kudos
Reply
1,143 Views
krsuresh
Contributor III

Hi Sanket Parekh,

Yes, You can close it. Thanks for the response. 

Thanks,

Suresh Kumar R

0 Kudos
Reply