Solved RPi zero W

Ofloo

Well-Known Member

Reaction score: 11
Messages: 312

Downloaded the latest 12.1 version from website today.

When i boot up the RPi-zero W I see this on the console.

Code:
MMC:   mmc@7e300000: 1
Loading Environment from FAT... In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
Bus usb@7e980000: scanning bus usb@7e980000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
U-Boot> [AMMC:   mmc@7e300000: 1
Loading Environment from FAT... In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
Bus usb@7e980000: scanning bus usb@7e980000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
MMC Device 0 not found
no mmc device at slot 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found EFI removable media binary efi/boot/bootarm.efi
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@7e300000.blk...
Found 3 disks
FDT memrsv map 0: Failed to add to map
BootOrder not defined
EFI boot manager: Cannot load any image
586456 bytes read in 60 ms (9.3 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
FDT memrsv map 0: Failed to add to map
Consoles: EFI console 
FreeBSD/arm EFI loader, Revision 1.1

   Command line arguments: l
   EFI version: 2.70
   EFI Firmware: Das U-Boot (rev 8217.1792)
   Console: efi (0)
   Load Path: /efi\boot\bootarm.efi
   Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x42f,0x18fa8)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x42f,0x18fa8)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(2,0x01,0,0x193d7,0x1d92c29)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
Loading kernel...
/boot/kernel/kernel data=0x71dfe4+0x1ee01c syms=[0x4+0xc1330+0x4+0xcb9cc]
Loading configured modules...
/boot/kernel/umodem.ko text=0x2418 data=0x244+0x4 syms=[0x4+0xa00+0x4+0xaf6]
loading required module 'ucom'
/boot/kernel/ucom.ko text=0x40cc data=0x3d8+0x838 syms=[0x4+0xeb0+0x4+0xc2e]
/boot/entropy size=0

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...               
Using DTB provided by EFI at 0x7ef7000.
Kernel entry at 0x12c00100...
Kernel args: (null)
modulep: 0xc0abc000
relocation_offset 0
It seems to always hang on relocation_offset 0, .. has the console gone to hdmi and isn't serial supported, ...?
 
OP
Ofloo

Ofloo

Well-Known Member

Reaction score: 11
Messages: 312

Today tried stable, ..

Code:
U-Boot 2020.07 (Jul 30 2020 - 02:31:07 +0000)

DRAM:  448 MiB
RPI Zero W (0x9000c1)
MMC:   mmc@7e300000: 0
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
Bus usb@7e980000: USB DWC2
scanning bus usb@7e980000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found EFI removable media binary efi/boot/bootarm.efi
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@7e300000.blk...
** Unrecognized filesystem type **
Found 3 disks
BootOrder not defined
EFI boot manager: Cannot load any image
626192 bytes read in 64 ms (9.3 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Consoles: EFI console
    Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm EFI loader, Revision 1.1

   Command line arguments: l
   EFI version: 2.80
   EFI Firmware: Das U-Boot (rev 8224.1792)
   Console: efi (0)
   Load Path: /efi\boot\bootarm.efi
   Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x42f,0x18fa8)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x42f,0x18fa8)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,0x01,0,0x193d7,0x1d92c29)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
Loading kernel...
/boot/kernel/kernel text=0x6ef154 data=0x83390 data=0x0+0x1ec000 syms=[0x4+0xc31a0+0x4+0xccc4a]
Loading configured modules...
/etc/hostid size=0x25
/boot/kernel/umodem.ko text=0x1520 text=0xf40 data=0x234+0x4 syms=[0x4+0xe70+0x4+0xa74]
loading required module 'ucom'
/boot/kernel/ucom.ko text=0x1714 text=0x2d3c data=0x3c4+0x838 syms=[0x4+0x13e0+0x4+0xbac]
/boot/entropy size=0x1000

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB provided by EFI at 0x7ef6000.
Kernel entry at 0x14c00180...
Kernel args: (null)
|
 
OP
Ofloo

Ofloo

Well-Known Member

Reaction score: 11
Messages: 312

FreeBSD13 snapshot

Code:
onsoles: EFI console
    Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm EFI loader, Revision 1.1
(Thu Jul 30 10:10:47 UTC 2020 root@releng1.nyi.freebsd.org)

   Command line arguments: l
   Image base: 0x1aa88000
   EFI version: 2.80
   EFI Firmware: Das U-Boot (rev 8224.1792)
   Console: comconsole (0)
   Load Path: /efi\boot\bootarm.efi
   Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x42f,0x18fa8)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(1,0x01,0,0x42f,0x18fa8)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(0)/SD(0)/HD(2,0x01,0,0x193d7,0x1d92c29)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
Loading /boot/loader.conf.local
Loading kernel...
/boot/kernel/kernel text=0x651ee0 data=0x85868 data=0x0+0x254000 syms=[0x4+0x79c40+0x4+0xd3420]
Loading configured modules...
/boot/entropy size=0x1000
/etc/hostid size=0x25
/boot/kernel/umodem.ko text=0x1be0 text=0x1330 data=0x2b8+0x8 syms=[0x4+0x1090+0x4+0xbd9]
loading required module 'ucom'
/boot/kernel/ucom.ko text=0x1f48 text=0x2fa8 data=0x4c8+0x83c syms=[0x4+0x14f0+0x4+0xc5d]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
Using DTB provided by EFI at 0x7ef6000.
Kernel entry at 0x14c00180...
Kernel args: (null)
-
 
OP
Ofloo

Ofloo

Well-Known Member

Reaction score: 11
Messages: 312

I just noticed what happens,.. after uart stops it moves to serial otg and creates device /dev/ttyACM0 and continues from there. And you're required to power it from the second micro usb interface the one with data in order to get such an interface. The port marked as USB not as PWR

Also uart runs at 115200 while OTG runs at 9600.
 
Top