Nanobsd rpi3


New Member

Reaction score: 1
Messages: 3

I am using nanobsd as root user on my amd64 PC for building an image for my rpi3.
After buidling, I have an error message in /usr/embedded/rpi3/_.cust.dos_boot_part :
+ dos_boot_part
+ local 'd=/usr/local/share/u-boot/u-boot-rpi3'
+ local 'f=/usr/embedded/rpi3/_.fat'
+ rm -rf /usr/embedded/rpi3/_.fat
+ echo 'NANO RM -rf /usr/embedded/rpi3/_.fat'
NANO RM -rf /usr/embedded/rpi3/_.fat
+ uname -r
+ command rm -x -rf /usr/embedded/rpi3/_.fat
+ mkdir /usr/embedded/rpi3/_.fat
+ chdir /usr/embedded/rpi3/_.fat
+ cp /usr/local/share/u-boot/u-boot-rpi3/LICENCE.broadcom /usr/local/share/u-boot/u-boot-rpi3/README /usr/local/share/u-boot/u-boot-rpi3/armstub8.bin /usr/local/share/u-boot/u-boot-rpi3/bootcode.bin /usr/local/share/u-boot/u-boot-rpi3/config.txt /usr/local/share/u-boot/u-boot-rpi3/fixup.dat /usr/local/share/u-boot/u-boot-rpi3/fixup_cd.dat /usr/local/share/u-boot/u-boot-rpi3/fixup_db.dat /usr/local/share/u-boot/u-boot-rpi3/fixup_x.dat /usr/local/share/u-boot/u-boot-rpi3/start.elf /usr/local/share/u-boot/u-boot-rpi3/start_cd.elf /usr/local/share/u-boot/u-boot-rpi3/start_db.elf /usr/local/share/u-boot/u-boot-rpi3/start_x.elf /usr/local/share/u-boot/u-boot-rpi3/u-boot.bin .
+ cp /usr/embedded/rpi3/_.w/boot/ubldr .
cp: /usr/embedded/rpi3/_.w/boot/ubldr: No such file or directory

What can I do to find ubldr file ?


New Member

Messages: 3


May be its NanoBSD problem?? I mean I do some builds early but from 'native' FreeBSD 11.0/11.1/12 and do not remember any kind of problems. Except not booted images...

But you may check first info here.

AW as I see this is u-boot problem. Does NanoBSD took u-boot sources?? Or may be you need to download in separately??

P.S. As advice... I DONT KNOW WHY ANY OFFICIAL (CROCHET TOO) BUILDS DO NOT WORK (cannt boot) , but strongly recommend look as raspbsd, which I personally using now on RPi3 for gateways and hot-spots (w/ additional - ralink prefered - external wifi).


Beastie's Twin

Reaction score: 2,562
Messages: 5,437

But nanobsd builds image with 2 readonly partitions and I think it's better with SD-card
I am having the same issue.
What issue? NanoBSD builds 2 partitions by default. That is how it works.
One is active image and the other is backup. That way you can roll back.

'I think it's better with SD-card'?
Memory disks help with any media that consume blocks over time.
That is how NanoBSD works. It uses memory disk to host certain directories.
Imagine a log file writing to a SD-card. It would be wore out in no time.

root@APU2:~ # mount
/dev/mmcsd0s1a on / (ufs, local, read-only)
devfs on /dev (devfs, local)
/dev/md0 on /etc (ufs, local, soft-updates)
/dev/md1 on /var (ufs, local, soft-updates)