PICO-PI-IMX7: imx_usb_loader

wagnerteixeira · November 18, 2021, 2:42am

Hello!! I’m following the steps in the topic and I’m not able to follow. After run command sudo ~/imx_usb_loader/imx_usb u-boot-dtb.img the board power off and power on and i get the output:

config file </home/wagner/imx_usb_loader//imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0080 file_name=mx6ull_usb_work.conf
vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf
vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf
vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf
vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf
vid=0x1fc9 pid=0x0134 file_name=mx8mm_usb_work.conf
vid=0x1fc9 pid=0x013e file_name=mx8mn_usb_work.conf
vid=0x3016 pid=0x1001 file_name=mx8m_usb_sdp_spl.conf
config file </home/wagner/imx_usb_loader//mx6_usb_sdp_spl.conf>
parse /home/wagner/imx_usb_loader//mx6_usb_sdp_spl.conf
Trying to open device vid=0x0525 pid=0xb4a4
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename u-boot-dtb.img
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 3
jump_addr 0x00000000
== end work item

loading binary file(u-boot-dtb.img) to 877fffc0, skip=0, fsize=7c6ec type=aa

<<<509676, 509676 bytes>>>
succeeded (security 0x56787856, status 0x88888888)
jumping to 0x877fffc0

the u-boot console dont start, what am I doing wrong

RobertCNelson · November 18, 2021, 7:11pm

Hi @wagnerteixeira , this tool can be fun at times… Let’s double check and verify things.

What version of git checkout of imx_usb_loader are you running?

Which version of u-boot, did you build?

What version of the board do you have? (is there a revision stick/silkscreen on it for ID)…

Are you using a Virtual Machine when trying to connect over USB, or a native linux install?

What is the “lusb” of the device before you run imx_usb_loader?

Regards,

wagnerteixeira · November 18, 2021, 9:16pm

Hi @RobertCNelson! Thank you so much for your answer.

answering your questions:

What version of git checkout of imx_usb_loader are you running?

the last version of master branch

commit 30b43d69770cd69e84c045dc9dcabb1f3e9d975a
Author: matttcattt 65450351+matttcattt@users.noreply.github.com
Date: Sun May 17 04:45:34 2020 +0100

Fix MinGW Build (#114)

Which version of u-boot, did you build?

v2021.04

What version of the board do you have? (is there a revision stick/silkscreen on it for ID)…

PICO-PI REV:B1

Are you using a Virtual Machine when trying to connect over USB, or a native linux install?

Native linux install, Ubuntu 21.04, uname -a output:

Linux wagnerbernardesnote 5.11.0-40-generic #44-Ubuntu SMP Wed Oct 20 16:16:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

What is the “lusb” of the device before you run imx_usb_loader?

Bus 001 Device 007: ID 15a2:0076 Freescale Semiconductor, Inc. i.MX 7Solo/7Dual SystemOnChip in RecoveryMode

some more information:

Connecting to micro usb port of the board and connecting to serial using sudo picocom -b 115200 /dev/ttyUSB0

when executing the command sudo ~/imx_usb_loader/imx_usb SPL

I have this output on the serial:

U-Boot SPL 2021.04 (Nov 17 2021 - 22:53:15 -0300)
Trying to boot from USB SDP
SDP: initialize…
SDP: handle requests…

when executing sudo ~/imx_usb_loader/imx_usb u-boot-dtb.img

I have this output on the serial:

Downloading file of size 506078 to 0x877fffc0… done
Jumping to header at 0x877fffc0
Header Tag is not an IMX image
Found header at 0x877fffc0

U-Boot 2021.04 (Nov 17 2021 - 22:53:15 -0300)

CPU: Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 43C
Reset cause: POR
Model: TechNexion PICO-IMX7D Board and PI baseboard
Board: i.MX7D PICOSOM
I2C: ready
DRAM: 512 MiB

fabryx92 · January 10, 2022, 3:24pm

@wagnerteixeira did you figure out how to overcome this issue? I’m in the same situation as you.

RobertCNelson · January 10, 2022, 5:15pm

Hi @fabryx92 what Host OS are you building with? Wonder if this is a host tool chain (and libusb) issue…

Can you please share your serial log too…

Regards,

fabryx92 · January 10, 2022, 5:50pm

Hi @RobertCNelson , thanks for the reply. I’m mostly in the same situation as @wagnerteixeira was.

Let me give you some information about my situation:

The output of git log from imx_usb_loader:

commit 30b43d69770cd69e84c045dc9dcabb1f3e9d975a (HEAD -> master, origin/master, origin/HEAD)
Author: matttcattt <65450351+matttcattt@users.noreply.github.com>
Date:   Sun May 17 04:45:34 2020 +0100

    Fix MinGW Build (#114)
    
    Signed-off-by: Matthew Cattle <matttcattt@gmail.com>

The output of git log from u-boot (from which I build it):

commit d80bb749fab53da72c4a0e09b8c2d2aaa3103c91 (HEAD, tag: v2021.10)
Author: Tom Rini <trini@konsulko.com>
Date:   Mon Oct 4 11:09:26 2021 -0400

    Prepare v2021.10
    
    Signed-off-by: Tom Rini <trini@konsulko.com>

My board model: PICO-PI REV:B1
The output of uname -a from the machine I’m using:

5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

The output of lsusb:

Bus 001 Device 006: ID 15a2:0076 Freescale Semiconductor, Inc. SE Blank ULT1

The output of sudo ~/imx_usb_loader/imx_usb SPL:

config file <../imx_usb_loader//imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0080 file_name=mx6ull_usb_work.conf
vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf
vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf
vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf
vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf
vid=0x1fc9 pid=0x0134 file_name=mx8mm_usb_work.conf
vid=0x1fc9 pid=0x013e file_name=mx8mn_usb_work.conf
vid=0x3016 pid=0x1001 file_name=mx8m_usb_sdp_spl.conf
config file <../imx_usb_loader//mx7_usb_work.conf>
parse ../imx_usb_loader//mx7_usb_work.conf
Trying to open device vid=0x15a2 pid=0x0076
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename SPL
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 3
jump_addr 0x00000000
== end work item
No DCD table

loading binary file(SPL) to 00911400, skip=0, fsize=ac00 type=aa

<<<44032, 44032 bytes>>>
succeeded (security 0x56787856, status 0x88888888)
jumping to 0x00911400

The output of sudo ~/imx_usb_loader/imx_usb u-boot-dtb.img:

config file <../imx_usb_loader//imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0080 file_name=mx6ull_usb_work.conf
vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf
vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf
vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf
vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf
vid=0x1fc9 pid=0x0134 file_name=mx8mm_usb_work.conf
vid=0x1fc9 pid=0x013e file_name=mx8mn_usb_work.conf
vid=0x3016 pid=0x1001 file_name=mx8m_usb_sdp_spl.conf
config file <../imx_usb_loader//mx6_usb_sdp_spl.conf>
parse ../imx_usb_loader//mx6_usb_sdp_spl.conf
Trying to open device vid=0x0525 pid=0xb4a4
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename u-boot-dtb.img
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 3
jump_addr 0x00000000
== end work item

loading binary file(u-boot-dtb.img) to 877fffc0, skip=0, fsize=7c5cc type=aa

<<<509388, 509388 bytes>>>
succeeded (security 0x56787856, status 0x88888888)
jumping to 0x877fffc0

The output of the serial console taken from PuTTY:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2022.01.10 18:30:05 =~=~=~=~=~=~=~=~=~=~=~=

U-Boot SPL 2021.10 (Jan 10 2022 - 13:31:30 +0100)
Trying to boot from USB SDP
SDP: initialize...
SDP: handle requests...
Downloading file of size 509388 to 0x877fffc0... done
Jumping to header at 0x877fffc0
Header Tag is not an IMX image
Found header at 0x877fffc0

U-Boot 2021.10 (Jan 10 2022 - 13:31:30 +0100)

CPU:   Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 39C
Reset cause: POR
Model: TechNexion PICO-IMX7D Board and PI baseboard
Board: i.MX7D PICOSOM
I2C:   ready
DRAM:  512 MiB

RobertCNelson · January 11, 2022, 10:14pm

I just finished cleaning up the guide: Debian: Getting Started with the PICO-PI-IMX7

I’ve removed the need for DFU-utils, this means you need to keep it in USB boot mode thru out the process. But that solves one of the errors some users have seen…

I’ve also added more output, from the serial console side of imx_usb…

dpkg --list | grep libusb-1
ii  libusb-1.0-0:amd64                            2:1.0.24-3                                                   amd64        userspace USB programming library
ii  libusb-1.0-0-dev:amd64                        2:1.0.24-3                                                   amd64        userspace USB programming library development files
ii  libusb-1.0-doc                                2:1.0.24-3                                                   all          documentation for userspace USB programming

imx_usb_loader$ ldd imx_usb
	linux-vdso.so.1 (0x00007ffc3e5a7000)
	libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 (0x00007f3301c7f000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3301aba000)
	libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f3301a92000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f3301a70000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f3301cd4000)

sudo ../imx_usb_loader/imx_usb SPL
config file <../imx_usb_loader//imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0080 file_name=mx6ull_usb_work.conf
vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf
vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf
vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf
vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf
vid=0x1fc9 pid=0x0134 file_name=mx8mm_usb_work.conf
vid=0x1fc9 pid=0x013e file_name=mx8mn_usb_work.conf
vid=0x3016 pid=0x1001 file_name=mx8m_usb_sdp_spl.conf
config file <../imx_usb_loader//mx7_usb_work.conf>
parse ../imx_usb_loader//mx7_usb_work.conf
Trying to open device vid=0x15a2 pid=0x0076
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename SPL
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 3
jump_addr 0x00000000
== end work item
No DCD table

loading binary file(SPL) to 00911400, skip=0, fsize=ac00 type=aa

<<<44032, 44032 bytes>>>
succeeded (security 0x56787856, status 0x88888888)
jumping to 0x00911400

U-Boot SPL 2021.10 (Jan 11 2022 - 15:35:38 -0600)
Trying to boot from USB SDP
SDP: initialize...
SDP: handle requests...

sudo ../imx_usb_loader/imx_usb u-boot-dtb.img 
config file <../imx_usb_loader//imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0080 file_name=mx6ull_usb_work.conf
vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf
vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf
vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf
vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf
vid=0x1fc9 pid=0x0134 file_name=mx8mm_usb_work.conf
vid=0x1fc9 pid=0x013e file_name=mx8mn_usb_work.conf
vid=0x3016 pid=0x1001 file_name=mx8m_usb_sdp_spl.conf
config file <../imx_usb_loader//mx6_usb_sdp_spl.conf>
parse ../imx_usb_loader//mx6_usb_sdp_spl.conf
Trying to open device vid=0x0525 pid=0xb4a4
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename u-boot-dtb.img
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 3
jump_addr 0x00000000
== end work item

loading binary file(u-boot-dtb.img) to 877fffc0, skip=0, fsize=7c5cc type=aa

<<<509388, 509388 bytes>>>
succeeded (security 0x56787856, status 0x88888888)
jumping to 0x877fffc0

Downloading file of size 509388 to 0x877fffc0... done
Jumping to header at 0x877fffc0
Header Tag is not an IMX image
Found header at 0x877fffc0

U-Boot 2021.10 (Jan 11 2022 - 15:35:38 -0600)

CPU:   Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 46C
Reset cause: POR
Model: TechNexion PICO-IMX7D Board and PI baseboard
Board: i.MX7D PICOSOM
I2C:   ready
DRAM:  512 MiB
PMIC:  PFUZE3000 DEV_ID=0x30 REV_ID=0x11
MMC:   FSL_SDHC: 3, FSL_SDHC: 1, FSL_SDHC: 0
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@30be0000
Hit any key to stop autoboot: 0

U-Boot SPL 2021.10 (Jan 11 2022 - 15:35:38 -0600)
Trying to boot from MMC1


U-Boot 2021.10 (Jan 11 2022 - 15:35:38 -0600)

CPU:   Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 46C
Reset cause: POR
Model: TechNexion PICO-IMX7D Board and PI baseboard
Board: i.MX7D PICOSOM
I2C:   ready
DRAM:  512 MiB
PMIC:  PFUZE3000 DEV_ID=0x30 REV_ID=0x11
MMC:   FSL_SDHC: 3, FSL_SDHC: 1, FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@30be0000
Hit any key to stop autoboot:  0 
Saving Environment to MMC... Writing to MMC(0)... OK
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
194 bytes read in 2 ms (94.7 KiB/s)
1:	Linux 5.15.10-armv7-lpae-x15
Retrieving file: /boot/vmlinuz-5.15.10-armv7-lpae-x15
12116480 bytes read in 270 ms (42.8 MiB/s)
append: root=/dev/mmcblk2p1 ro rootfstype=ext4 rootwait quiet
Retrieving file: /boot/dtbs/5.15.10-armv7-lpae-x15/imx7d-pico-pi.dtb
49781 bytes read in 4 ms (11.9 MiB/s)
Kernel image @ 0x80800000 [ 0x000000 - 0xb8e200 ]
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Using Device Tree in place at 83000000, end 8300f274

Starting kernel ...

[    0.071939] debugfs: Directory 'dummy-iomuxc-gpr@30340000' with parent 'regmap' already present!
[    1.732781] debugfs: Directory 'dummy-reset-controller@30390000' with parent 'regmap' already present!
[    1.846461] CPUidle arm: CPU 0 failed to init idle CPU ops

Debian GNU/Linux 11 arm ttymxc4

default username:password is [debian:temppwd]

arm login: root
Password: 

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@arm:~# cat /proc/cpuinfo 
processor	: 0
model name	: ARMv7 Processor rev 5 (v7l)
BogoMIPS	: 48.00
Features	: half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 5

processor	: 1
model name	: ARMv7 Processor rev 5 (v7l)
BogoMIPS	: 48.00
Features	: half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 5

Hardware	: Freescale i.MX7 Dual (Device Tree)
Revision	: 0000
Serial		: 0000000000000000
root@arm:~#

Regards,

fabryx92 · January 12, 2022, 11:53am

I figured out what was causing the serial console to be stuck at DRAM line.

Thanks to the last @RobertCNelson 's reply I executed the command dpkg --list | grep libusb-1 and I saw that I had libusb-1.0-0:amd64 2:1.0.23-2-build1.
I think that this is the version included in Ubuntu 20.04 by default.

So I removed it and installed the newer version 1.0.24 (I downloaded it from https://ubuntu.pkgs.org/21.04/ubuntu-main-amd64/5/ ).

After that, launching the imx_usb_loader command I was able to proceed through the guide since the serial console doesn’t stack at the DRAM line.

Topic		Replies	Views
Loading the u-boot-dtb.img binary via USB Linux Discussions	3	1579	February 17, 2021
PICO-PI-IMX7 USB Flash Drive Linux Discussions	6	2042	January 23, 2022
PICO-PI-IMX7 boot loop Linux Discussions	4	1433	January 14, 2022
PICO-PI-IMX7d no kernel output Linux Discussions	11	1689	July 2, 2019
RE: PICO-PI-IMX7 and Siging In/Um? Linux Discussions	209	17359	January 20, 2020

PICO-PI-IMX7: imx_usb_loader

Related topics