I am running out of ideas to make my Nanopi R2S Plus to run FreeBSD #freebsd #arm #arm64

[maulanahirzan@mastodon.bsd.cafe]

I am running out of ideas to make my Nanopi R2S Plus to run FreeBSD

#freebsd #arm #arm64

[winterschon@mastodon.bsd.cafe]

@maulanahirzan R2S Plus uses U-Boot on a RK3328 SOC, similarly as the Rock64. Sometimes there is sufficient overlap with an embedded SoM or SoC where a build which works for one might also work with the other.

- https://simonevellei.com/blog/posts/freebsd-on-a-rock64-board/
- RK3328 bug discussions: https://reviews.freebsd.org/D19335

Rock64 images, could work, might need changes, might be flawless
- https://download.freebsd.org/releases/arm64/aarch64/ISO-IMAGES/14.3/

[maulanahirzan@mastodon.bsd.cafe]

@winterschon thank you for the hint. To be honest l, I do not want to give up with this device.

[winterschon@mastodon.bsd.cafe]

@maulanahirzan I know what you mean. There are a number of both NanoPi and Jetson boards over here which I've either bricked, screwed up and need to debug, etc.

Do you have the TTL serial port already enabled/usable? It's very difficult to debug the boot process and capture code/logs/timestamps/etc without DEBUG UART access. On most NanoPi those UART headers are inside the chassis and require either dupont connectors or pogo-pins, but on the R2S-Plus it has its own usb-c debug port on the right-most side.

> USB-C to Debug UART converter, 1500000bps baud
> https://wiki.friendlyelec.com/wiki/images/f/f1/NanoPi_R2S_Plus-layout.jpg

[maulanahirzan@mastodon.bsd.cafe]

@winterschon yes I have the boot log from both succesful and failed images. After numerous trial and errors (manual hook, compiled u-boot for r2s plus via ports), I found that there is no trust.img from FreeBSD, that's why nanopi skipped the sdcard. I flashed armbian (working image) trust.img to the sd card and Nanopi showed loader error.

maybe I need to recompile the u-boot with ATF load turned off?