#author("2026-05-28T23:09:50+09:00","","")
#author("2026-05-28T23:10:10+09:00;2026-05-28T23:09:50+09:00","","")
* 7.9-arm64 on Raspberry Pi Zero 2 W Rev 1.0 [#u2de2586]
-Posted by Mitsuki Shirase at 2026-05-28 (Thu) 00:58:15
-Release: 7.9-arm64-202605271
-Media: SD/microSD
-Hardware: Raspberry Pi Zero 2 W Rev 1.0 (CPU: ARM Cortex-A53 r0p4, Memory: 468172800 (446MB))

** Remarks [#d59a9a02]
#setlinebreak(on)
#FuguIta
Equipped with the PoE Ethernet / USB HUB HAT for Raspberry Pi Zero.
Wi-Fi is not recognized.
` bwfm0: failed loadfimware of file brcmfmac43430-sdio.raspberrypi,model-zero-2-w.bin`

dmesg
  OpenBSD 7.9 (RDROOT.MP) #4: Wed May 27 05:03:24 JST 2026
      kaw@nimbus72.localnet:/opt/fi/7.9/sys/arch/arm64/compile/RDROOT.MP
  real mem  = 468172800 (446MB)
  avail mem = 408776704 (389MB)
  random: good seed from bootblocks
  mainbus0 at root: Raspberry Pi Zero 2 W Rev 1.0
  efi0 at mainbus0: UEFI 2.11
  efi0: Das U-Boot rev 0x20250700
  smbios0 at efi0: SMBIOS 3.7.0
  smbios0: vendor U-Boot version "2025.07" date 07/01/2025
  smbios0: raspberrypi Raspberry Pi Zero 2 W Rev 1.0
  cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
  cpu0: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
  cpu0: 512KB 64b/line 16-way L2 cache
  cpu0: CRC32,ASID16
  cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4
  cpu1: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
  cpu1: 512KB 64b/line 16-way L2 cache
  cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4
  cpu2: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
  cpu2: 512KB 64b/line 16-way L2 cache
  cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4
  cpu3: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
  cpu3: 512KB 64b/line 16-way L2 cache
  "linux,cma" at mainbus0 not configured
  apm0 at mainbus0
  simplefb0 at mainbus0: 1824x984, 32bpp
  wsdisplay0 at simplefb0 mux 1: console (std, vt100 emulation)
  wsdisplay0: screen 1-5 added (std, vt100 emulation)
  "system" at mainbus0 not configured
  "axi" at mainbus0 not configured
  simplebus0 at mainbus0: "soc"
  bcmclock0 at simplebus0
  bcmmbox0 at simplebus0
  bcmgpio0 at simplebus0
  bcmaux0 at simplebus0
  bcmdmac0 at simplebus0: DMA0 DMA2 DMA4 DMA5 DMA8 DMA9 DMA10 DMA11
  bcmintc0 at simplebus0
  pluart0 at simplebus0: rev 2, 16 byte fifo
  bcmsdhost0 at simplebus0: 250 MHz base clock
  sdmmc0 at bcmsdhost0: 4-bit, sd high-speed, mmc high-speed, dma
  dwctwo0 at simplebus0
  bcmdog0 at simplebus0
  bcmrng0 at simplebus0
  bcmtemp0 at simplebus0
  "interrupt-controller" at simplebus0 not configured
  sdhc0 at simplebus0
  sdhc0: SDHC 3.00, 200 MHz base clock
  sdmmc1 at sdhc0: 4-bit, sd high-speed, mmc high-speed
  "firmware" at simplebus0 not configured
  "power" at simplebus0 not configured
  "mailbox" at simplebus0 not configured
  "gpiomem" at simplebus0 not configured
  "fb" at simplebus0 not configured
  simplebus1 at simplebus0: "nvmem"
  "nvmem_otp" at simplebus1 not configured
  "nvmem_cust" at simplebus1 not configured
  simplebus2 at mainbus0: "clocks"
  "clk-osc" at simplebus2 not configured
  "clk-usb" at simplebus2 not configured
  "phy" at mainbus0 not configured
  "arm-pmu" at mainbus0 not configured
  agtimer0 at mainbus0: 19200 kHz
  "cam1_regulator" at mainbus0 not configured
  "cam_dummy_reg" at mainbus0 not configured
  "fixedregulator_3v3" at mainbus0 not configured
  "fixedregulator_5v0" at mainbus0 not configured
  gpioleds0 at mainbus0: "ACT"
  usb0 at dwctwo0: USB revision 2.0
  uhub0 at usb0 configuration 1 interface 0 "Broadcom DWC2 root hub" rev 2.00/1.00 addr 1
  scsibus0 at sdmmc0: 2 targets, initiator 0
  sd0 at scsibus0 targ 1 lun 0: <Sandisk, SA128, 0072> removable
  sd0: 119152MB, 512 bytes/sector, 244023296 sectors
  uhub1 at uhub0 port 1 configuration 1 interface 0 "Terminus Technology USB 2.0 Hub" rev 2.00/1.11 addr 2
  bwfm0 at sdmmc1 function 1
  manufacturer 0x02d0, product 0xa9a6 at sdmmc1 function 2 not configured
  uhub2 at uhub1 port 2 configuration 1 interface 0 "Terminus Technology USB2.0 HUB" rev 2.00/1.00 addr 3
  uhidev0 at uhub2 port 1 configuration 1 interface 0 "WWW.WCH.CN WCH UART TO KB-MS_V1.8" rev 1.10/38.00 addr 4
  uhidev0: iclass 3/1
  ukbd0 at uhidev0: 8 variable keys, 6 key codes
  wskbd0 at ukbd0: console keyboard, using wsdisplay0
  uhidev1 at uhub2 port 1 configuration 1 interface 1 "WWW.WCH.CN WCH UART TO KB-MS_V1.8" rev 1.10/38.00 addr 4
  uhidev1: iclass 3/0, 2 report ids
  uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0
  ucc0 at uhidev1 reportid 2: 4 usages, 4 keys, array
  wskbd1 at ucc0 mux 1
  wskbd1: connecting to wsdisplay0
  uhidev2 at uhub2 port 1 configuration 1 interface 2 "WWW.WCH.CN WCH UART TO KB-MS_V1.8" rev 1.10/38.00 addr 4
  uhidev2: iclass 3/1
  ums0 at uhidev2: 3 buttons, Z dir
  wsmouse0 at ums0 mux 0
  uhidev3 at uhub2 port 1 configuration 1 interface 3 "WWW.WCH.CN WCH UART TO KB-MS_V1.8" rev 1.10/38.00 addr 4
  uhidev3: iclass 3/1, 2 report ids
  ums1 at uhidev3 reportid 2: 5 buttons, Z dir
  wsmouse1 at ums1 mux 0
  ure0 at uhub1 port 4 configuration 1 interface 0 "Realtek USB 10/100 LAN" rev 2.00/20.00 addr 5
  ure0: RTL8152 (0x4c10), address 00:e0:4c:36:12:38
  rlphy0 at ure0 phy 0: RTL8201E, rev. 2
  vscsi0 at root
  scsibus1 at vscsi0: 256 targets
  softraid0 at root
  scsibus2 at softraid0: 256 targets
  root on rd0a swap on rd0b dump on rd0b
  WARNING: CHECK AND RESET THE DATE!
  gpio0 at bcmgpio0: 54 pins
  bwfm0: failed loadfirmware of file brcmfmac43430-sdio.raspberrypi,model-zero-2-w.bin
- Is that firmware enabled on vanila OpenBSD rather than #FuguIta? -- [[kaw]] &new{2026-05-28 (Thu) 06:34:44};
- I have not been able to confirm it yet, so I apologize for the uncertainty, but I believe it is probably not enabled on vanilla OpenBSD either. -- [[Mitsuki Shirase]] &new{2026-05-28 (Thu) 08:22:25};
- I found brcmfmac43436-sdio.raspberrypi,model-zero-2-w.bin, brcmfmac43430-sdio.raspberrypi,model-zero-2-w.txt, etc in /etc/firmware. This was installed by 'pkg_add raspberrypi-firmware'. What about doing this by hand? (This is not installed in #FuguIta by default) -- [[kaw]] &new{2026-05-28 (Thu) 09:11:45};
#aname(update_firmware)
- The procedure to update firmware:
1. on other machine, download the firmware, then save it to #FuguIta device
 other_host # ftp http://firmware.openbsd.org/firmware/7.9/bwfm-firmware-20200316.1.3p5.tgz
 Trying 2a04:4e42::820...
 Requesting http://firmware.openbsd.org/firmware/7.9/bwfm-firmware-20200316.1.3p5.tgz
 100% |**************************************************| 11729 KB    00:02 ETA
 12011326 bytes received in 2.87 seconds (3.98 MB/s)
 other_host # mount /dev/sd0d /mnt
 other_host # cp bwfm-firmware-20200316.1.3p5.tgz /mnt
 other_host # umount /mnt
2. boot FuguIta device, then mount and update the firmware
 rpizero2w # mount /dev/sd0d /mnt
 rpizero2w # fw_update /mnt/bwfm-firmware-20200316.1.3p5.tgz
 fw_update: add bwfm; update none
 rpizero2w # rm /bwfm-firmware-20200316.1.3p5.tgz
 rpizero2w # umount /mnt
3. [[save the environment>fge2:usbfadm_sync]], then [[reboot with mode 3>fge2:boot_mode3]]
4. [[create Wi-Fi config, then enable it>fge3:netconf]]
~-- [[kaw]] &new{2026-05-28 (Thu) 14:31:25};
- Thank you for taking the time to verify this.  I was able to confirm that, when a wired connection is available, the system automatically downloads bwfm-firmware-20200316.1.3p5.tgz and runs fw_update during the initial boot process.  I believe the method you suggested is probably the best approach. #FuguIta -- [[Mitsuki Shirase]] &new{2026-05-28 (Thu) 21:03:18};
- Thank you for taking the time to verify this.  I was able to confirm that, when a wired connection is available, the system automatically downloads bwfm-firmware-20200316.1.3p5.tgz and runs fw_update during the initial boot process.  I believe the method you suggested is probably the best approach. #FuguIta -- [[Mitsuki Shirase]] &new{2026-05-28 (Thu) 23:09:50};

#comment
#setlinebreak(off)

#navi(FuguIta/Report)

Front page   Edit Diff History Attach Copy Rename Reload   New Page list Search Recent changes   Help   RSS of recent changes