Will it run FreeBSD ? [Embedded Version]

Sharing this information to this thread as well. I have a 610 and 640 up and working with pfSense. Both required a BIOS update first. BIOS update took care of watchdog timer. 610 gets a tad more complicated with it's ethernet ports due to them being tied to the C3K SOC eth ports via a Marvell 88E6190 embedded switch.

 
Hi FluffyB0nes, can you tell me how to update the BIOS on the Dell Edge610 ?
I have already installed different Linux versions (ubuntu, VyOS, Danos, FreeBSD), but I don´t get the interfaces up although the drivers are loaded.
 
Hi, I am also looking for the dell sd-wan edge 610 bios. Does anyone have a working bios they can share? thank you
 
Just saw this thread pop up, so I thought I'd ask....

Is there any chance of getting FreeBSD running on an old IBM ThinkPad 820 (PowerPC)? It switches on but the hard disk is probably dead. It uses a SCSI disk. Not sure if you can still get them.
 
any IBM ThinkPad is hardly embedded (in the context of FreeBSD), but the information is available
based on the information here, the 820 is a 7247-82x machine. So I'll say the chance to get FreeBSD running on it is slim, very slim.
Many thanks for the links. I'll refer back to this at some point if/when I find a suitable SCSI disk for the system, as I'm not sure whether the disk has any life in it.
 
As some might I have noticed I have taken an interest in Lora and LoraWAN.
I have made a purchase finally. I got two Helium Miners with Arm64 base.

Rock Pi but what version. When I originally discovered these I assume the worst. Rock Pi original with rk3308.
But I saw that they are RK3399 so they must be a Rock Pi 4. But what flavor??? With wireless probably Rock4B.
We shall see. They went for $60 on ebay and base RockPi4 is >$80 so worth a gamble. As a bonus a hat with a Lora Radio.
Semtech sx1301 radio in SPI factor via MiniPCIe slot. (USB version available too). SPI because its a 40Pin Hat without USB access.

I found this interesting too.
RK3566 driving a Lora Box. Browan MerryIOT
Bluetooth onboard and Lora under a shield. Looks like a similar MiniPCIe adapter for Lora radio. This one uses sx1302 radio.
 
I understand the interest in LoRa and LoRaWAN. It will be interesting to follow your journey. The thing I don't understand is why a cryptominer box would have (or need) LoRa?
 
The thing I don't understand is why
Believe me I don't understand the concept any more than you do.
Apparently they wirelessly network miners to ???

I am just a hardware scraper. These Nebra had bad firmware so everybody dumped them.
I am not sure they ever worked.
Sounds like what I would expect for crypto. Another ponzi scheme.

I am just glad they used hardware I am familiar with.
 
Despite my interest in Lora and LoraWAN I am realistic in that FreeBSD probably won't ever support it.
There are LoraWAN servers on github and alot of software available but I am sure to make it work on FreeBSD would be a herculean effort.
If there were a prefab Linux with Lora setup installed I might check it out.

There is a certain allure to me in a wireless network with a 5 mile range that uses AES keying. Even if low bitrate.
 
Well, LoRa is "just" another radio protocol so it could be made to work (on FreeBSD) in several iterations:
1) user programs that drive the hardware directly. Those probably exist for Linux, Arduino and whatnot and will probably port with some effort
2) figure out where LoRa fits into the FreeBSD driver infrastructure - is it dedicated (kind of like a serial port)? Or is it a generic network that needs a hardware driver? (probably not, you probably wouldn't want to run tcp/ip directly over it, because of the low bandwidth) - I have no idea how hard / time-consuming this task is
3) write FreeBSD driver(s) for the hardware - this is probably the hardest iteration
4) write some user programs and enjoy
 
Interesting, you can use LoRa to create a mesh network, like this Meshtastic. It should be possible to make something similar on FreeBSD. Could be useful for out of band monitoring for example.
 
How about a GPIO sensor net via LoraWAN....

Got my package today. Nebra is using Rock Pi 4 PLUS V1.73.
The PLUS model means MMC soldered on. NVMe slot on bottom.
Unsure what size MMC.
So I need to wipe MMC and probably clear SPI too. May need to short out SPI at boot to get past that so I can clear .

We have u-boot for rock-pi-4 but I wonder about the PLUS version.

Anybody running RockPi 4 PLUS ? How about Rock Pi 4 SE ??

Are there different dts for all these Rock Pi 4 variants?
 
OK I got FreeBSD installed on the 32GB eMMC soldered on Nebra Miner Rock Pi 4-Plus.
There was no SPI flash soldered on these starting at version RockPi-4 V1.72 so that worked out good.
I did have to use an Armbian microSD image for RockPi4B to delete Miner OS on eMMC.
So I dd zero'ed from Linux the mmcblk1 then used a stock FreeBSD u-boot image created from sysutils/u-boot-rock-pi-4 flashed to a microSD card. I then flashed the aarch64 memstick installer image to usb and use that for FreeBSD installation. After installation I had to adjust disk path in /etc/fstab and flash u-boot to eMMC.

I was so happy I bought the last new one that was <$60. Threes company....
I like the chassis. I hope to mount the NVMe adapter where Lora radio was.
 
RK3566 driving a Lora Box. Browan MerryIOT
If you notice in the high rez picture there are 3 pin not populated.
Marked RX and TX. A utoob video pointed them out without explanation.
Probably the UART. With some careful soldering I could make that happen.
This box would be harder to find dtb's and uboot.
I do see a RK3568 defconfig for evb-rk3568
This is an evaluation board from Rockchip.
Guessing that is a good starting point for new unsupported RK board defconfig files. Perhaps a reference design?
Copy file and fixup for MerryIOT....
 
I have a new line of exploration. Facial Recognition cameras. I found RK3399 Lurking in Firefly Face-X2.
A Kiosk style device for scanning temps. Stereo Cameras and spot lighting.

I tore it apart and it has Firefly Face-RK3399 V2 development board with a expansion board.

Good Wiki where I see UART port pins and tried that with nothing.
So I rigged up a 2mm connector TTL cable to the serial debug connector and I saw u-boot.

I have bought two similar units to see what they use. I feel like they might all use the Firefly board.

Will they run FreeBSD? I will find out. DSI-MIPI2 display and dual CSI ports.
A microSD card slot hiding on the underneath has me confident I can wipe Android.
 
Interior photos of Firefly Face-X2
 

Attachments

  • IMG_0104.JPG
    IMG_0104.JPG
    1.7 MB · Views: 74
  • IMG_0114.JPG
    IMG_0114.JPG
    1.6 MB · Views: 82
  • IMG_0122.JPG
    IMG_0122.JPG
    1.8 MB · Views: 84
I just spread the 3 Debug pins wide so I could use my 2.54mm pitch FDT 232R-TTL.
(Bad boy and they were too short for connector so I had to hold them in place. Regardless I saw u-boot.)

I actually have a couple of 2mm FDT 232R-TTL inbound.

FTDI chip TTL-232R-3V3-2MM

I will need to rejigger the connector. Cut down to 3 pin.
 
I just spread the 3 Debug pins wide so I could use my 2.54mm pitch FDT 232R-TTL.
(Bad boy and they were too short for connector so I had to hold them in place. Regardless I saw u-boot.)

I actually have a couple of 2mm FDT 232R-TTL inbound.

FTDI chip TTL-232R-3V3-2MM

I will need to rejigger the connector. Cut down to 3 pin.
Me last one burnt out cuz electricity is hard.
 
I have a Turing TVTS-OP-BTTS7 that hit the door.

First pop back off and see CPU covered no UART pins but I see three unpopulated holes.(2.54mm pitch)
RX/TX/GND
Solder weekend coming up.

Did not have the Firefly Face-RK3399 dev board. Will have to research.
 
rk3399-firefly.dtb
I studied the dts for this and this will probably work. The Firefly RK3399 is a board by the same people.
It is probably close enough to boot to serial debug port.
I see HDMI but that is no big deal. No video output only DSI on dev board.
Ideally I try the official Ubuntu Image if that works scrape the dtb, decompile and reuse for FreeBSD.
 
Hello Covacat, Phishfry, and other arm64 running FreeBSD 14.0. Here is my first attempt at creating an image to 'dd' into a USB flash drive and boot on the Raspberry Pi 4B with 8 gigs dram memory. This Raspberry Pi is running FreeBSD 14.0-CURRENT snapshot from Was 14.0-CURRENT snapshot, now is using FreeBSD-15.0-CURRENT. 14.0-STABLE is testing now , not available at freebsd.org/where webpage aarch64 snapshot images for FreeBSD 15.0 current
Klara Systems, building customized freebsd images webpage document I used this document to create a bootable USB flash drive image.

The ESP EFI FAT32 files I copied from the present booting RPI3 Freebsd 14.0-CURRENT snapshot. The klara systems help me to use make buildkernel, make installkernel, makefs , create image

FreeBSD this is my building platform
fred@Fred_RasPi4B:~ $ uname -mnopr
FreeBSD Fred_RasPi4B 14.0-CURRENT arm64 aarch64
fred@Fred_RasPi4B:~ $ uname -aK
FreeBSD Fred_RasPi4B 14.0-CURRENT FreeBSD 14.0-CURRENT #7 main-n261078-57fcf46dee45-dirty: Sat Feb 25 06:04:13 PST 2023 root@Fred_RasPi4B:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC-VCHIQ arm64 1400081
fred@Fred_RasPi4B:~ $ date
Sun Sep 24 17:02:16 PDT 2023
Covacat, I am looking for hints and directions on how to debug a boot kernel. I can enable boot debug messages
fred@Fred_RasPi4B:~ $ mount
/dev/da0p10 on / (ufs, local, soft-updates)
devfs on /dev (devfs)
/dev/da0p1 on /mnt/msdos (msdosfs, local)
/dev/gpt/rootfs on /mnt/rootfs (ufs, local, soft-updates)
fred@Fred_RasPi4B:~ $ pwd
/home/fred
fred@Fred_RasPi4B:~ $ cd /mnt/rootfs
fred@Fred_RasPi4B:/mnt/rootfs $ ls
COPYRIGHT boot entropy lib media net rescue sbin usr
bin dev etc libexec mnt proc root tmp var
fred@Fred_RasPi4B:/mnt/rootfs $ ls boot
beastie.4th color.4th efi.4th gptboot.efi loader.efi loader_4th.efi logo-fbsdbw.4th menu.4th shortcuts.4th
boot1.efi defaults entropy images loader.help.efi loader_lua.efi logo-orb.4th menu.rc support.4th
brand-fbsd.4th delay.4th firmware kernel loader.help.kboot loader_simp.efi logo-orbbw.4th menusets.4th uboot
brand.4th dtb fonts loader.4th loader.kboot logo-beastie.4th lua modules version.4th
check-password.4th efi frames.4th loader.conf.d loader.rc logo-beastiebw.4th menu-commands.4th screen.4th zfs
fred@Fred_RasPi4B:/mnt/rootfs $ cat loader.conf config.txt
cat: loader.conf: No such file or directory
cat: config.txt: No such file or directory
fred@Fred_RasPi4B:/mnt/rootfs $ cat /boot/loader.conf /etc/rc.conf
beastie_disable="NO"
loader_color="YES"

# Disable the beastie menu and color
# beastie_disable="YES"
# loader_color="NO"

vm.pageout_oom_seq="4096"
vm.pfault_oom_attempts="1"

kern.cam.boot_delay="5000"


hostname="Fred_RasPi4B"
keymap="us.kbd"
ifconfig_genet0="DHCP"
defaultrouter="192.168.1.1"
kld_list="linux64"
dbus_enable="YES"
# moused_enable="YES"




FreeBSD kernel Debug tools
So, I am looking for tips, hints, tricks to debug a new aarch64 kernel made from /usr/ghostbsd-src , which is almost the same as FreeBSD /usr/src

I believe you could boot a working aarch64 FreeBSD snapshot image and then compare configuration files /boot/loader.conf /etc/rc.conf to see what is different. Maybe one could swap the /boot/kernel/kernel image files. First move the broken kernel image file to different name like /boot/kernel/kernel_ghost_broken, before copying in a working kernel image file. Yes, I can set those kernel_boot_debug messages in /boot/loader.conf. I have them set on a x86_64 GhostBSD system, that is where I can locate the name I don't have at hand.

Glad to hear of your successes with other arm64 Single Board Computers. Do you suggest a JTAG board to connect to debug these kinds of problems? Tigar Board here in Portland Oregon is one such board. Orange Colored Tigard JTAG aarch64 board
 

Attachments

  • Ghostbsd_arm64_boot_failure_photo_2023-09-24_16-33-09.jpg
    Ghostbsd_arm64_boot_failure_photo_2023-09-24_16-33-09.jpg
    143.2 KB · Views: 53
Back
Top