Pi Zero format boards that are supported.

I think it helps to use a serial port so you can capture the messages.
There is no indicator in system logs of what DTB's have loaded.

Code: 
Loading kernel...                                                          
/boot/kernel/kernel text=0x318 text=0xa5b378 text=0x27df90 data=0x1814e0 data=0x0+0x2c5000 0x8+0x1699f8+0x8+0x198602|
Loading configured modules...
/boot/kernel/ds3231.ko text=0x1280 text=0x1168 data=0x3b8 0x8+0x990+0x8+0x644
/etc/hostid size=0x25
/boot/entropy size=0x1000
Using DTB provided by EFI at 0x3ce8c000.
Loading DTB overlays: 'ds3231-i2c3.dtb,i2c4.dtb,pwm8.dtb,pwm9.dtb'
/boot/dtb/overlays/ds3231-i2c3.dtb size=0x186
/boot/dtb/overlays/i2c4.dtb size=0x3cf
/boot/dtb/overlays/pwm8.dtb size=0x27f
/boot/dtb/overlays/pwm9.dtb size=0x30b
Loading splash ok
applying DTB overlay '/boot/dtb/overlays/ds3231-i2c3.dtb'
applying DTB overlay '/boot/dtb/overlays/i2c4.dtb'
applying DTB overlay '/boot/dtb/overlays/pwm8.dtb'
applying DTB overlay '/boot/dtb/overlays/pwm9.dtb'
---<<BOOT>>---
GDB: debug ports: uart
GDB: current port: uart
KDB: debugger backends: ddb gdb
KDB: current backend: ddb
WARNING: Cannot find freebsd,dts-version property, cannot check DTB compliance
Copyright (c) 1992-2024 The FreeBSD Project.

My PWM devices are not showing up in /dev/pwm so this is where I start debugging.

Did the overlay apply cleanly. It did.
 
My FreeBSD built Rock Zero 3E Slave Port

mkdir /usr/ports/sysutils/u-boot-radxa-zero-3

Makefile
Code: 
MASTERDIR=    ${.CURDIR}/../u-boot-master

MODEL=        radxa-zero-3
BOARD_CONFIG=    radxa-zero-3-rk3566_defconfig
FAMILY=        rk356X

.include "${MASTERDIR}/Makefile"

pkg-descr
Code: 
U-Boot loader and related files for the Radxa Zero 3.

To install this bootloader on an sdcard just do:
dd if=/usr/local/share/u-boot/u-boot-radxa-zero-3/idbloader.img of=/path/to/sdcarddevice seek=64 bs=512 conv=sync
dd if=/usr/local/share/u-boot/u-boot-radxa-zero-3/u-boot.itb of=/path/to/sdcarddevice seek=16384 bs=512 conv=sync

I also jigger with u-boot-master to get newer version.
Also RK356X fails to build on 2024.10-u-boot due to a fragment in u-boot-master. I have deleted it with no problem.

Code: 
U-Boot 2024.10 (Nov 25 2024 - 18:58:06 -0500)

Model: Radxa ZERO 3E
DRAM:  1 GiB (effective 1022 MiB)
PMIC:  RK817 (on=0x40, off=0x00)
Core:  286 devices, 30 uclasses, devicetree: separate
MMC:   mmc@fe2b0000: 1
Loading Environment from nowhere... OK
In:    serial@fe660000
Out:   serial@fe660000
Err:   serial@fe660000
Model: Radxa ZERO 3E
Net:   eth0: ethernet@fe010000
Hit any key to stop autoboot:  0
 
Last edited:
---> I was looking at alternatives to RockChip and was browsing AllWinner.

Why are you looking for one alternative to RockChip ? What does not work with it ?

---> I like the Zero format as Pi Zero cases and hats are mostly usable.

Usually display + hat + board become something too thick. Since I want to build something that looks like a tablet,I can't use hats. In addition to this,usually I see that for the hats there are only the drivers for Linux.
 
ZioMario said:
Why are you looking for one alternative to RockChip ?
Click to expand...
That is a valid question. I suppose I hate to be hemmed in by one product.

Looking at the GPIO chart for OPI Zero2W was interesting. To see where pin assignments overlap. Like SPI and extra UARTS
 
----> Looking at the GPIO chart for OPI Zero2W was interesting. To see where pin assignments overlap. Like SPI and extra UARTS

How this is supposed to work ? You should port the driver from Linux ? You should write some code ?
 
Phishfry said:
OrangePi2W is the only true Zero Clone but it has unsupported H618.
I like the Zero format as Pi Zero cases and hats are mostly usable.
Click to expand...
I tested it out with OpenBSD a few months back. It all works well minus the wifi. I am surprised it is a no go with FreeBSD.

The only thing I noticed with a Pi Zero case, was that the Orange-Pi uses USB-C rather than microusb. So the case I tried was a little awkward there.
 
---> https://www.amazon.co.uk/Flirc-Raspberry-Pi-Zero-Case/dp/B08837L144

I saw that case. I've discharged it because it is built with anodized aluminum. Can't modify a single atom of it. But I like the aesthetics. I've chosen this one :

ameridroid.com

ROCKPro64 PLAYBOX Enclosure

Looking to turn your ROCKPro64 into a tablet-like device? Why not try the ROCKPro64 Playbox Enclosure for the ROCKPro64 SBC and Pine A64 7in. LCD touchscreen, with a slim Graphene heatsink included? This will turn your SBC into a powerful, portable handheld computing device. NOTES Pine64...
ameridroid.com
 
ZioMario said:
How this is supposed to work ? You should port the driver from Linux ? You should write some code ?
Click to expand...
Pin Muxing.
All are set as GPIO (except UART console) and you must mux them to whatever.
Many pins have several options.
Everybody trys to follow Pi 40pin Muxing.

You use DTBO overlay files to set muxing.
 
So for example I want 1.3" OLED display hat on my Zero stack. There is github for FreeBSD driver and userland.
You must set an device tree overlay for SPI to use the OLED Display Hat.
www.ebay.com

1.3inch 128X64 OLED Screen Module HAT for Raspberry Pi 0 Zero 2 W 3 Model B 4 5 | eBay

Resolution: 128x64. Standard Raspberry Pi 40PIN GPIO extension header, supports Raspberry Pi series boards, Jetson Nano. RASPBERRY PI PIN (BCM). This compact display would be the ideal choice. Interface: 4-wire SPI, 3-wire SPI, I2C.
www.ebay.com

I am hoping for the driver to work with this hat.
 
---> So for example I want OLED display hat on my Zero stack. There is github for driver and userland.

Can I give a look ? please post a picture of the hat,better if connected with the soc. And share the github address please. I would like to evaluate.
 
Phishfry said:
So for example I want 1.3" OLED display hat on my Zero stack. There is github for FreeBSD driver and userland.
You must set an device tree overlay for SPI to use the OLED Display Hat.
www.ebay.com

1.3inch 128X64 OLED Screen Module HAT for Raspberry Pi 0 Zero 2 W 3 Model B 4 5 | eBay

Resolution: 128x64. Standard Raspberry Pi 40PIN GPIO extension header, supports Raspberry Pi series boards, Jetson Nano. RASPBERRY PI PIN (BCM). This compact display would be the ideal choice. Interface: 4-wire SPI, 3-wire SPI, I2C.
www.ebay.com

I am hoping for the driver to work with this hat.
Click to expand...

display of 1.3 inches ? You will become blind. I've bought this one :

8inch Capacitive Touch Display, Wide Color Gamut, 1280×800, Optical Bonding Toughened Glass Panel, HDMI/Type-C Display Interface, 10-Point Touch, Aluminum Alloy Case | 8HP-CAPLCD Monitor

8inch Capacitive Touch Display, Wide Color Gamut, 1280×800, Optical Bonding Toughened Glass Panel, HDMI/Type-C Display Interface, 10-Point Touch, Aluminum Alloy Case | 8HP-CAPLCD Monitor
www.waveshare.com www.waveshare.com

I'm interested to find the driver for the touchscreen.
 
covacat made h618 support on 13.2 but then he wasn't ready to actually get it into tree. i have it, and device, never tried but i don't know it enough to make it good. despite i want it working

this is some cheap 64bit arm that looks good h3 replacement maybe. except h3 lts in many lts boards. we would need another lts option here

boards with various capabilities are needed actually. not just server, not just mobile. not just rpi. not just rk*. not just video out

btw, rockchip is good but why the closed boot eh? same is the rpi

actually arm is so difficult still. there is no standard to this time iirc. 32bit and 64bit x86 systems are much more standardized as separate socs. sad fact

do you know how much embedded hw has flowed through fbsd src over years? it's like poof gone

in that entire period, some actual big machines have lasted decades with no plans to lose it. eg amd64 machines. many of them may lose computational value completely before before fbsd loses them. there are reasons for that
 
Are there any 65x30mm boards where both HDMI and networking are supported by FreeBSD?

Based on the conversation above and the wiki it sounds like the situation is:
  • Banana Pi BPI-M2 ZERO: ??? - SOC supported
  • Mango Pi MQ-Pro: ??? - SOC partially supported
  • Mango Pi MQ-Quad: SOC unsupported upstream
  • Orange Pi Zero 2W: SOC unsupported upstream
  • Radxa Zero: SOC unsupported?
  • Radxa Zero 3E: no video, ethernet
  • Radxa Zero 3W: no video, no wifi
  • Raspberry Pi Zero W: video, no wifi
  • Raspberry Pi Zero 2W: video (I assume), no wifi
 
You must log in or register to reply here.
Back
Top