FreeBSD 13-CURRENT on Rock Pi E

thanx man , i test it and changed everything you say , but problem in applying rock-pi-e-patch ! give error! but i double check and try from beginning, thanks for your help!
do you need 12.2 drivers to create release for 12.2?

and one other question! do you planning to update your github u-boot ports to 2021.01?

thanx @SleepWalker for your help.
i successfully created new u-boot .

Hi @SleepWalker, I have tried four (4) different Rock Pi E img.xz (from https://personalbsd.org/images/FreeBSD/) ranging from 2021 to 2023 and I used balenaEtcher on Windows 11 to burn the .img.xz file (I select and burn the actual [compressed] .img.xz file) directly to a Class 10 micro SD Card (32GB) but whenever I power-on my Rock PI E board, the green power led glows brightly but nothing else happens even after 10 mins ā€¦ should the blue led start flashing??

My Rock PI E does have an eMMC with a filesystem on it, if that may be a problem?

Is there anything else I may need to do to the img.xz file before I burn it to microSD? Is there anything you would like for me to mount/check of the img.xz file? Should I do a checksum, perhaps?

Is it necessary for the Rock PI E board to be connected to Ethernet when it gets powered on? (I have tried both, WAN and LAN ports plugged in before power-on and has not made a difference)

The Rock PI E boots ok with both Ubuntu and Debian from microSD (to make sure that the board is still working!) but I really want to get FreeBSD running on it ā€¦

Thanks very much!
Cheers,
Rodney

Hi @rodneygdavies

Yes, the problem may be related to the u-boot on the eMMC. Remove the eMMC or reset it and FreeBSD will start successfully from the SD card. Or burn the FreeBSD image to eMMC directly

Hi @SleepWalker

You were right! I removed the eMMC from my Rock Pi E board and now the blue LED lights up after about 15-30 seconds and remains on, solidly - Thank-you very much!

My Rock Pi E is the 1GB SDRAM version - I have just ordered a 512MB Rock Pi E.

I am using FreeBSD-aarch64-13.1-RELEASE-p5-Rock-Pi-E-20230130.img.xz and I have plugged in LAN ethernet socket to a Linksys router (running WRT) and I can see the greed ethernet LED link light come on after a few seconds - I get the same when I switch to WAN port.

On the router (router has IP:192.168.1.1/24) the logs show that there is an incoming DHCP DISCOVER request and an OFFER is made of 192.168.1.183 but then nothing else happens:

Sat Oct 15 13:35:10 2022 daemon.info dnsmasq-dhcp[1354]: DHCPDISCOVER(br-lan) 4a:ee:6f:67:3d:91
Sat Oct 15 13:35:10 2022 daemon.info dnsmasq-dhcp[1354]: DHCPOFFER(br-lan) 192.168.1.183 4a:ee:6f:67:3d:91

I get 100% packet loss when I ping 192.168.1.183 from the router :frowning: and I donā€™t seem to be able to make anything different happen.

I have another router I could use which has IP: 192.168.0.1/24 - might that be something to try?

Just wondering if you could please let me know if I may have missed a step or if there is anything else that I can try or change?

Thanks very much for your help and for your wonderful efforts!

Cheers,
Rodney

Hi @rodneygdavies.

This is a starter image, donā€™t expect too much from it.
It runs dhclient, it doesnā€™t have a routing daemon, and it canā€™t handle routing switching between ports correctly :slight_smile:

Select one of the LAN or WAN ports, connect to your network that has a dhcp server and turn on the device. After a full start, the device should receive an IP address and you can get to it via SSH with
Username: admin
Password: admin

Start over by burning the image to the SD card.

The first start may take longer as the filesystem is resizing to the full size of the SD card. Wait some time after startup until pings appear and donā€™t switch Ethernet between LAN and WAN, be patient.
I think everything should work.

The device is difficult to control as there is no HDMI, only a console port.

Good luck.

Hi @SleepWalker,

Thank-you very, very much! The image is working ok and you are a great legend! :slight_smile:

I attached a serial cable to use the serial console on UART2 and could see it booting up - I burned FreeBSD-aarch64-13.1-RELEASE-p5-Rock-Pi-E-20230130.img (uncompressed) to an SD card and powered up the RockPiE and the console showed everything as it booted and then I got to a login: prompt and I was able to login ok as per your instructions, above.

My next challenge is to try and build a boot/kernel/rootfs image of my own ā€¦ Iā€™ll have a look around first and go from there ā€¦

Here is the dmesg output if you are interested to see:

Copyright Ā© 1992-2021 The FreeBSD Project.
Copyright Ā© 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 13.1-RELEASE-p5 #0: Mon Jan 30 05:11:02 MSK 2023
root@honeycomb.local:/usr/crochet/work/obj/usr/crochet/src-release-13.1-p5/a
rm64.aarch64/sys/GENERIC arm64
FreeBSD clang version 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.
0-0-gd7b669b3a303)
VT: init without driver.
module firmware already present!
real memory = 534523904 (509 MB)
avail memory = 498679808 (475 MB)
Starting CPU 1 (1)
Starting CPU 2 (2)
Starting CPU 3 (3)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
arc4random: WARNING: initial seeding bypassed the cryptographic random device be
cause it was not yet seeded and the knob ā€˜bypass_before_seedingā€™ was enabled.
random: entropy device external interface
MAP 1cf13000 mode 2 pages 1
MAP 1cf19000 mode 2 pages 2
MAP 1ff30000 mode 2 pages 16
kbd0 at kbdmux0
ofwbus0:
simplebus0: on ofwbus0
clk_fixed0: on ofwbus0
rk_grf0: mem 0xff100000-0xff100fff on ofwbus0
rk3328_cru0: mem 0xff440000-0xff440fff on ofwbus0
Cannot set frequency for clk: aclk_bus_pre, error: 34
rk3328_cru0: Failed to set aclk_bus_pre to a frequency of 15000000
Cannot set frequency for clk: aclk_peri_pre, error: 34
rk3328_cru0: Failed to set aclk_peri_pre to a frequency of 15000000
clk_fixed1: on ofwbus0
regfix0: on ofwbus0
regfix1: on ofwbus0
regfix2: on ofwbus0
regfix3: on ofwbus0
clk_fixed2: on ofwbus0
simple_mfd0: <Simple MFD (Multi-Functions Device)> mem 0xff450000-0xff45ffff on ofwbus0
psci0: on ofwbus0
gic0: mem 0xff811000-0xff811fff,0xff812000-0x
ff813fff,0xff814000-0xff815fff,0xff816000-0xff817fff irq 49 on ofwbus0
gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 160
rk_pinctrl0: on ofwbus0
gpio0: mem 0xff210000-0xff2100ff irq 53 on rk_pi nctrl0
gpiobus0: on gpio0
gpio1: mem 0xff220000-0xff2200ff irq 54 on rk_pi nctrl0
gpiobus1: on gpio1
gpio2: mem 0xff230000-0xff2300ff irq 55 on rk_pi nctrl0
gpiobus2: on gpio2
gpio3: mem 0xff240000-0xff2400ff irq 56 on rk_pi nctrl0
gpiobus3: on gpio3
rk_i2c0: mem 0xff160000-0xff160fff irq 16 on ofwbus0
iicbus0: on rk_i2c0
rk805_pmu0: at addr 0x30 irq 57 on iicbus0
generic_timer0: irq 4,5,6,7 on ofwbus0
Timecounter ā€œARM MPCore Timecounterā€ frequency 24000000 Hz quality 1000
Event timer ā€œARM MPCore Eventtimerā€ frequency 24000000 Hz quality 1000
rk_tsadc0: mem 0xff250000-0xff2500ff irq 22 on of
wbus0
cpulist0: on ofwbus0
cpu0: on cpulist0
cpufreq_dt0: on cpu0
cpu1: on cpulist0
cpu2: on cpulist0
cpu3: on cpulist0
pmu0: irq 0,1,2,3 on ofwbus0
uart0: <16750 or compatible> mem 0xff130000-0xff1300ff irq 14 on ofwbus0
uart0: console (-1,n,8,1)
iic0: <I2C generic I/O> on iicbus0
rk3328codec0: mem 0xff410000-0xff410fff on ofwbus0
rockchip_dwmmc0: <Synopsys DesignWare Mobile Storage Host Controller (RockChip)>
mem 0xff500000-0xff503fff irq 41 on ofwbus0
rockchip_dwmmc0: num-slots property is deprecated
rockchip_dwmmc0: Hardware version ID is 270a
mmc0: <MMC/SD bus> on rockchip_dwmmc0
rockchip_dwmmc1: <Synopsys DesignWare Mobile Storage Host Controller (RockChip)>
mem 0xff520000-0xff523fff irq 43 on ofwbus0
rockchip_dwmmc1: num-slots property is deprecated
rockchip_dwmmc1: Hardware version ID is 270a
mmc1: <MMC/SD bus> on rockchip_dwmmc1
dwc0: mem 0xff540000-0xff54ffff irq 44 on ofwbus0
miibus0: on dwc0
OUI = 0xe04c, MODEL = 0x11, REV = 0x6
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 0 on miibus0
rgephy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1
000baseT-FDX-master, auto
OUI = 0xe04c, MODEL = 0x11, REV = 0x6
rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1
000baseT-FDX-master, auto
dwc0: Ethernet address: 0a:cc:d5:88:0e:c5
dwc1: mem 0xff550000-0xff55ffff irq 45 on ofwbus0
dwc1: PHY is integrated
miibus1: on dwc1
OUI = 0x20b1ac, MODEL = 0x0, REV = 0x0
dwc1: Ethernet address: 62:73:64:30:9a:66
dwcotg0: mem 0xff580000-0xff5bffff irq 46 on ofwbus0
usbus1 on dwcotg0
ehci0: mem 0xff5c0000-0xff5cffff irq 47 on ofwbus0
usbus2: EHCI version 1.0
usbus2 on ehci0
ohci0: mem 0xff5d0000-0xff5dffff irq 48 on ofwbus0
usbus3 on ohci0
gpioc0: on gpio0
gpioc1: on gpio1
gpioc2: on gpio2
gpioc3: on gpio3
pcm0: on ofwbus0
gpioled0: on ofwbus0
armv8crypto0: <AES-CBC,AES-XTS,AES-GCM>
Timecounters tick every 1.000 msec
rk805_pmu0: registered as a time-of-day clock, resolution 1.000000s
usbus1: 480Mbps High Speed USB v2.0
usbus2: 480Mbps High Speed USB v2.0
usbus3: 12Mbps Full Speed USB v1.0
ugen3.1: at usbus3
uhub0 on usbus3
uhub0: <Generic OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
ugen2.1: at usbus2
uhub1 on usbus2
uhub1: <Generic EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
ugen1.1: at usbus1
uhub2 on usbus1
uhub2: <DWCOTG OTG Root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
mmcsd0: 32GB <SDHC 00000 0.0 SN 0000001B MFG 04/2022 by 159 TI> at mmc0 50.0MHz/
4bit/1016-block
mmc1: No compatible cards found on bus
pcm0: no driver attached to cpu node
CPU 0: ARM Cortex-A53 r0p4 affinity: 0
Cache Type = <64 byte D-cacheline,64 byte I-cacheline,VIPT IC

ache,64 byte ERG,64 byte CWG>
Instruction Set Attributes 0 = <CRC32,SHA2,SHA1,AES+PMULL>
Instruction Set Attributes 1 = <>
Processor Features 0 = <AdvSIMD,FP,EL3 32,EL2 32,EL1 32,EL0 32>
Processor Features 1 = <>
Memory Model Features 0 = <TGran4,TGran64,SNSMem,BigEnd,16bit ASID,1TB PA>
Memory Model Features 1 = <8bit VMID>
Memory Model Features 2 = <32bit CCIDX,48bit VA>
Debug Features 0 = <DoubleLock,2 CTX BKPTs,4 Watchpoints,6 Breakpoints,PMUv3,Debugv8>
Debug Features 1 = <>
Auxiliary Features 0 = <>
Auxiliary Features 1 = <>
AArch32 Instruction Set Attributes 5 = <CRC32,SHA2,SHA1,AES+VMULL,SEVL>
AArch32 Media and VFP Features 0 = <FPRound,FPSqrt,FPDivide,DP VFPv3+v4,SP VFPv3
+v4,AdvSIMD>
AArch32 Media and VFP Features 1 = <SIMDFMAC,FPHP DP Conv,SIMDHP SP Conv,SIMDSP,
SIMDInt,SIMDLS,FPDNaN,FPFtZ>
CPU 1: ARM Cortex-A53 r0p4 affinity: 1
CPU 2: ARM Cortex-A53 r0p4 affinity: 2
CPU 3: ARM Cortex-A53 r0p4 affinity: 3
Release APsā€¦done
GEOM: mmcsd0: the secondary GPT header is not in the last LBA.
Trying to mount root from ufs:/dev/gpt/install [rw,noatime]ā€¦
Warning: bad time from time-of-day clock, system time will not be set accurately
Dual Console: Serial Primary, Video Secondary
uhub0: 1 port with 1 removable, self powered
uhub2: 1 port with 1 removable, self powered
uhub1: 1 port with 1 removable, self powered
random: randomdev_wait_until_seeded unblock wait
ugen2.2: <Realtek 802.11n WLAN Adapter> at usbus2
random: unblocking device.
dwwdt0: mem 0xff1a0000-0xff1a00ff irq 20 on ofwbus0
dwwdt0: cannot find clock
device_attach: dwwdt0 attach returned 6
lo0: link state changed to UP
dwc0: link state changed to DOWN
ubt0 on uhub1
ubt0: on usbus2
WARNING: attempt to domain_add(bluetooth) after domainfinalize()
WARNING: attempt to domain_add(netgraph) after domainfinalize()
Security policy loaded: MAC/ntpd (mac_ntpd)
admin@rock-pi-e:/etc %

I am keen to help you with advancing this further and getting images built/tested/working if there is anything I may be able to do to help?

Thanks again, very much for your help @SleepWalker! :slight_smile:

Cheers,
Rod