Hello,
Earlier I was using imx8ulp-evk9 to flash in that I was using uuu tool and with that I was able to generate flash.bin and can flash with below command
sudo uuu -V -b emmc flash.bin
Than I made custom board in which I am using chip MIMX8UD5D08SC and I am trying to flash with same command but after 29% uuu getting aborted.
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.21-0-g1f42172
Wait for Known USB Device Appear...
Success 0 Failure 1
1:1 1/ 1 [HID(W):LIBUSB_ERROR_NO_DEVICE ] SDPS: boot -f /imx-mkimage/iMX8ULP/flash.bin
Any changes I required to do if I am flashing on new board , I just want to start with flash bootloader first, what is ways for that?
@pengyong_zhang
I followed that only and at last getting below logs while flashing flash.bin, it is getting stuck after 100%
U-Boot SPL 2022.04-dirty (Jan 07 2025 - 14:36:27 +0530)
Normal Boot
ELE firmware version 1.0.0-344acb84
upower_apd_inst_isr: entry
upower_init: soc_id=48
upower_init: version:11.11.13
upower_init: start uPower RAM service
user_upwr_rdy_callb: soc=b
user_upwr_rdy_callb: RAM version:12.17
Turning on switches...
Turn on switches ok
Turning on memories...
Turn on memories ok
Clearing DDR retention...
Clear DDR retention ok
SEC0: RNG instantiated
Trying to boot from BOOTROM
Boot Stage: USB boot
Find img info 0x&88000000, size 288
Download 943104, Total size 944128
NOTICE: BL31: v2.8(release):lf-6.6.3-1.0.0-0-g8dbe28631
NOTICE: BL31: Built : 17:57:56, Jan 22 2024
NOTICE: upower_init: start uPower RAM service
NOTICE: user_upwr_rdy_callb: soc=b
NOTICE: user_upwr_rdy_callb: RAM version:12.17
U-Boot 2022.04-dirty (Jan 07 2025 - 14:36:27 +0530)
M33 Sync: OK
CPU: i.MX8ULP rev1.2 at 960 MHz
CPU current temperature: 46
Reset cause: POR
Boot mode: Single boot
Model: NXP i.MX8ULP 9X9 EVK
DRAM: 2 GiB
Core: 47 devices, 25 uclasses, devicetree: separate
MMC: FSL_SDHC: 0
Loading Environment from nowhere... OK
[*]-Video Link 0 (720 x 1280)
[0] display-controller@2e050000, video
[1] dsi@2db00000, video_bridge
[2] panel@0, panel
In: serial
Out: serial
Err: serial
SEC0: RNG instantiated
switch to partitions #0, OK
mmc0(part 0) is current device
UID 0x3baf2bda,0xb74e39fc,0xc40c9992,0xb364aa92
Detect USB boot. Will enter fastboot mode!
Net: 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 ;
Hit any key to stop autoboot: 0
## Checking Image at 83800000 ...
Unknown image format!
Run fastboot ...
auto usb 0
No USB device found
USB init failed: -19
=>
@pengyong_zhang
One more IMPORTANT thing is in EVK there is typeC for flashing and we are using normal USB 2.0, do we require to change anything in configuration for that?
Please refer our i.MX Linux User's Guide file compile the flaash.bin by yourself. Sorry about it. Because i can not help you compile it each time.
B.R
@pengyong_zhang
That's completely fine zhang, Just share me imx-mkimage folder with all changes that you did I will generate flash.bin by myself.
Hello @pengyong_zhang
Thanks for sharing, In the Custom board we are using same UART port(lpuart5) with different pins, Can you share me updated flash.bin with below change in dts file
pinctrl_lpuart5: lpuart5grp {
fsl,pins = <
MX8ULP_PAD_PTE6__LPUART5_TX 0x3
MX8ULP_PAD_PTE7__LPUART5_RX 0x3
>;
};
please share me yout pass timing.c file i will help you generated the flash.bin, and see if it can pass.
B.R
After changing C12 from 3 to 1 I am able to calibrate my DRAM successfully,
>>>C12?
Is this issue reflects my previous change or it is something else?
>>>What is your next step when you generated the new timing.c file with DDR Stress tool? you should use it to replace the old timing.c file and re-compile the Uboot. then flash it to your board.
B.R
IMPORTANT,
Hello @pengyong_zhang
Here I am attching updated logs, Earlier I was using only 1 bank for LPDDR, now I am using all existing configuration and generated timing file and created flash.bin and enabled debug log in u-boot I am attaching for reference, Can you tell me why log is like this?
@pengyong_zhang
Updated Logs,
Is below issue can happen because of wrong ddr calibration or is this indicating different one?
U-Boot SPL 2022.04-dirty (Jan 02 2025 - 19:23:58 +0530)
Normal Boot
ELE firmware version 1.0.0-344acb84
upower_apd_inst_isr: entry
upower_init: soc_id=48
upower_init: version:11.11.13
upower_init: start uPower RAM service
user_upwr_rdy_callb: soc=b
user_upwr_rdy_callb: RAM version:12.18
Turning on switches...
Turn on switches ok
Turning on memories...
Turn on memories ok
Clearing DDR retention...
Clear DDR retention ok
SEC0: RNG instantiated
Trying to boot from BOOTROM
Boot Stage: USB boot
Can't found uboot image in 640K range
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
@pengyong_zhang
I exactly did same, I updated timing.c file and recompiled u-boot, took u-boot.bin and u-boot-spl.bin updated in imx-mkimage/iMX8ULP, generated flash.bin and flashed on board with uuu.
After that I am getting just below logs in my custom board and than failed,
U-Boot SPL 2023.04-dirty (Jan 02 2025 - 17:24:28 +0530)
Dhruvin
Normal Boot
ELE firmware version 1.0.0-344acb84
upower_apd_inst_isr: entry
upower_init: soc_id=48
upower_init: version:11.11.13
upower_init: start uPower RAM service
user_upwr_rdy_callb: soc=b
user_upwr_rdy_callb: RAM version:12.18
Turning on switches...
Turn on switches ok
Turning on memories...
Turn on memories ok
Clearing DDR retention...
Clear DDR retention ok
SEC0: RNG instantiated
Trying to boot from BOOTROM
Boot Stage: USB boot
Just for reference in the EVK when I flash with it's compaible flash.bin logs were like
U-Boot SPL 2023.04+gf8a2983ec8+p0 (Mar 04 2024 - 07:25:04 +0000)
Normal Boot
ELE firmware version 1.0.0-344acb84
upower_apd_inst_isr: entry
upower_init: soc_id=48
upower_init: version:11.11.13
upower_init: start uPower RAM service
user_upwr_rdy_callb: soc=b
user_upwr_rdy_callb: RAM version:12.18
Turning on switches...
Turn on switches ok
Turning on memories...
Turn on memories ok
Clearing DDR retention...
Clear DDR retention ok
SEC0: RNG instantiated
Trying to boot from BOOTROM
Boot Stage: USB boot
Find img info 0x88000000, size 288
Download 999424, Total size 1000448
NOTICE: BL31: v2.8(release):lf-6.6.3-1.0.0-0-g8dbe28631
NOTICE: BL31: Built : 17:57:56, Jan 22 2024
NOTICE: upower_init: start uPower RAM service
NOTICE: user_upwr_rdy_callb: soc=b
NOTICE: user_upwr_rdy_callb: RAM version:12.18
which is not coming in my custom board.
Hello @pengyong_zhang
After changing C12 from 3 to 1 I am able to calibrate my DRAM successfully,
Than I taken code and added where I am creating image and tried to flash image where I get below logs and than stuck, Is this issue reflects my previous change or it is something else?
U-Boot SPL 2023.04-dirty (Jan 02 2025 - 17:24:28 +0530)
Dhruvin
Normal Boot
ELE firmware version 1.0.0-344acb84
upower_apd_inst_isr: entry
upower_init: soc_id=48
upower_init: version:11.11.13
upower_init: start uPower RAM service
user_upwr_rdy_callb: soc=b
user_upwr_rdy_callb: RAM version:12.18
Turning on switches...
Turn on switches ok
Turning on memories...
Turn on memories ok
Clearing DDR retention...
Clear DDR retention ok
SEC0: RNG instantiated
Trying to boot from BOOTROM
Boot Stage: USB boot
In the EVK after last line logs were like
Find img info 0x88000000, size 288
Download 999424, Total size 1000448
this is not coming in my board what can be issue for this?
We have not test with only one channel on the two channel DRAM. So, I think it's not possible。
B.R
Hello @pengyong_zhang
Can you provide me any document where all supported lpddr4/4x for IMX8ULP/IMX8ULP-EVK9 is listed?
I have checked this parameters about your new LPDDR on the RPA table, It same with the MT53D512M32D2DS. So,I don't think there's any problem with that. No need update about it.
B.R
Hello @pengyong_zhang
One question here, in the logs I observed that registers associated with Channel A has proper value I think some issues with Channel B,
Is there any way we can configure and complete calibration for only channel A, if yes can you share me that XLs and .ds file which only configure and calibrate for channel A