UUU issues on IMX6SX

mabar52 — Tue, 10 Oct 2023 10:59:50 GMT

Trying to build write and boot u-boot with uuu utility.
Our board is based on the sabresd reference with IMX6SX and qspi-flash.

SO-AP-SE-19:uuu root# ./uuu -lsusb uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.125-5-g1a9d927 Connected Known USB Devices Path Chip Pro Vid Pid BcdVersion ================================================== 2:11 MX6SX SDP: 0x15A2 0x0071 0x0001 SO-AP-SE-19:uuu root# ./uuu -s uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.125-5-g1a9d927 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 FB: 0x0483 0x0afb Please input command: U>SDP: dcd -f files/u-boot-smartoptics-dcp.imx-memtest >Start Cmd:SDP: dcd -f files/u-boot-smartoptics-dcp.imx-memtest New USB Device Attached at 2:11 100%2:11>Okay (0.009s) Okay U>SDP: write -f files/u-boot-smartoptics-dcp.imx-memtest 2:11>Start Cmd:SDP: write -f files/u-boot-smartoptics-dcp.imx-memtest New USB Device Attached at 2:11 0%2:11>Fail HID(W):LIBUSB_ERROR_IO(0.004s) HID(W):LIBUSB_ERROR_IO

Is there a way to further debug this to know why the error occurs.
With another build u-boot configutation:

SDP: dcd -f files/u-boot-memtest-DCP-R8.0-r0.imx SDP: write -f files/u-boot-memtest-DCP-R8.0-r0.imx -ivt 0 SDP: jump -f files/u-boot-memtest-DCP-R8.0-r0.imx -ivt 0 SO-AP-SE-19:uuu root# SO-AP-SE-19:uuu root# (reverse-i-search)`-s': cat dcp-start-u-boot.lst.memtest SO-AP-SE-19:uuu root# ./uuu -s uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.125-5-g1a9d927 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 FB: 0x0483 0x0afb Please input command: U>SDP: dcd -f files/u-boot-memtest-DCP-R8.0-r0.imx >Start Cmd:SDP: dcd -f files/u-boot-memtest-DCP-R8.0-r0.imx New USB Device Attached at 2:11 2:11>Okay (0.004s) Okay U>SDP: write -f files/u-boot-memtest-DCP-R8.0-r0.imx -ivt 0 2:11>Start Cmd:SDP: write -f files/u-boot-memtest-DCP-R8.0-r0.imx -ivt 0 New USB Device Attached at 2:11 2:11>Fail HID(W):LIBUSB_ERROR_TIMEOUT(2.157s)

We use several u-boot compilations that serve different purposes and we have recently upgrade our yocto environment from 2.7 to 4. We have several patches and separate defconfigs that are applied depending on what kind of u-boot configuration that is built.

I suspect that I miss some kCONFIG to u-boot, not sure how to check that, though.

This is an old build that works and I can see through the console that u-boot is started:

U>SDP: dcd -f files/u-boot-qspi2-DCP-R7.0-r0.imx >Start Cmd:SDP: dcd -f files/u-boot-qspi2-DCP-R7.0-r0.imx New USB Device Attached at 2:11 100%2:11>Okay (0.008s) Okay U>SDP: write -f files/u-boot-qspi2-DCP-R7.0-r0.imx -ivt 0 2:11>Start Cmd:SDP: write -f files/u-boot-qspi2-DCP-R7.0-r0.imx -ivt 0 New USB Device Attached at 2:11 100%2:11>Okay (0.178s) Okay U>SDP: jump -f files/u-boot-qspi2-DCP-R7.0-r0.imx -ivt 0 2:11>Start Cmd:SDP: jump -f files/u-boot-qspi2-DCP-R7.0-r0.imx -ivt 0 New USB Device Attached at 2:11 100%2:11>Okay (7.03s) Okay U>

Any help is most welcome, of course.

i.MX ProcessorsのトピックUUU issues on IMX6SX

UUU issues on IMX6SX