SATA on Espressobin Marvell ARMADA 3720 anyone can confirm it works ?

this is what i use for sd card, and it works fine:
setenv bootcmd 'load mmc 0:1 $fdt_addr dtb/marvell/armada-3720-espressobin.dtb; load mmc 0:1 $kernel_addr EFI/BOOT/bootaa64.efi; bootefi $kernel_addr $fdt_addr'

this is what im trying to use for scsi, boots but stops at mounting the opnsense ufs, shows no disk available:
setenv bootcmd 'scsi scan; scsi dev 0; load scsi 0:1 $fdt_addr dtb/marvell/armada-3720-espressobin.dtb; load scsi 0:1 $kernel_addr EFI/BOOT/bootaa64.efi;setenv bootargs $console root=PARTUUID=00000000-02 rw rootwait; bootefi $kernel_addr $fdt_addr'0

not sure what i am missing
 
covacat said:
looks like ahci driver fails to attach
if it works (the ahci driver) when booting from emmc then it means that some initialization done by u-boot is not done by the ahci driver so it depends on u-boot version
or there are differences in the dtb
the best way would be to add the missing bits to the driver/dtb
Click to expand...
i still get "device_attach: ahcich0 attach returned 6" even when successfully booting on mmc
 
Sorry I just rebooted and checked. Seems I was wrong. I had trouble with 2022 SPI flash. Using 2020.

Code: 
TIM-1.0
WTMI-devel-18.12.1-
WTMI: system early-init
SVC REV: 5, CPU VDD voltage: 1.062V
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v2.3(): (Marvell-devel-18.12.0)
NOTICE:  BL1: Built : 14:44:01, Sep  1 2020
NOTICE:  BL1: Booting BL2
NOTICE:  BL2: v2.3(): (Marvell-devel-18.12.0)
NOTICE:  BL2: Built : 14:44:01, Sep  1 2020
NOTICE:  BL1: Booting BL31
NOTICE:  BL31: v2.3(): (Marvell-devel-18.12.0)
NOTICE:  BL31: Built : 14:44:01

U-Boot 2020.10-rc3 (Sep 01 2020 - 14:44:01 +0000)

DRAM:  1 GiB
Comphy-0: USB3_HOST0    5 Gbps  
Comphy-1: PEX0          2.5 Gbps
Comphy-2: SATA0         5 Gbps  
Target spinup took 0 ms.
AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: ncq led only pmp fbss pio slum part sxs
PCIE-0: Link down
MMC:   sdhci@d0000: 0, sdhci@d8000: 1
Loading Environment from SPIFlash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 4 KiB, total 4 MiB
OK
Model: Marvell Armada 3720 Community Board ESPRESSOBin (eMMC)
Net:   eth0: neta@30000
Hit any key to stop autoboot:  0
=>

So I flash 2020 SPI then reboot. Then setenv default -a then reset.
Then scsi scan and scsi dev 0. This sets disk active.
boot

Code: 
Loading kernel...
/boot/kernel/kernel text=0x2a8 text=0x8d5250 text=0x212d5c data=0x1ae510 data=0x0+0x2a9000 0x8+0x1295d0+0x8+0x14e631|
Loading configured modules...
/boot/kernel/umodem.ko text=0x2060 text=0x1350 data=0x6c8+0x10 0x8+0xee8+0x8+0xb42
loading required module 'ucom'
/boot/kernel/ucom.ko text=0x249f text=0x3380 data=0x8a0+0x858 0x8+0x1188+0x8+0xb19
/boot/entropy size=0x1000
/etc/hostid size=0x25
Using DTB provided by EFI at 0x7efb000.
EFI framebuffer information:
addr, size     0x0, 0x0
dimensions     0 x 0
stride         0
masks          0x00000000, 0x00000000, 0x00000000, 0x00000000
---<<BOOT>>---
WARNING: Cannot find freebsd,dts-version property, cannot check DTB compliance
Copyright (c) 1992-2021 The FreeBSD Project.
Copyright (c) 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.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC arm64
FreeBSD clang version 14.0.5 (https://github.com/llvm/llvm-project.git llvmorg-14.0.5-0-gc12386ae247c)
VT: init without driver.
module firmware already present!
real memory  = 1073692672 (1023 MB)
avail memory = 1024892928 (977 MB)
Starting CPU 1 (1)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
random: unblocking device.
random: entropy device external interface
MAP 3eb12000 mode 2 pages 1
MAP 3eb16000 mode 2 pages 3
MAP 3eb1a000 mode 2 pages 4
MAP 3ff30000 mode 2 pages 16
kbd0 at kbdmux0
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
simplebus1: <Flattened device tree simple bus> on simplebus0
simple_mfd0: <Simple MFD (Multi-Functions Device)> mem 0x13800-0x138ff,0x13c00-0x13c1f on simplebus1
simple_mfd1: <Simple MFD (Multi-Functions Device)> mem 0x18800-0x188ff,0x18c00-0x18c1f on simplebus1
psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0
gic0: <ARM Generic Interrupt Controller v3.0> mem 0x1d00000-0x1d0ffff,0x1d40000-0x1d7ffff on simplebus1
gpio0: <Armada 37x0 North Bridge GPIO Controller> mem 0x13800-0x138ff,0x13c00-0x13c1f irq 7,8,9,10,11,12,13,14,15,16,17,18 on simple_mfd0
gpiobus0: <OFW GPIO bus> on gpio0
gpio1: <Armada 37x0 South Bridge GPIO Controller> mem 0x18800-0x188ff,0x18c00-0x18c1f irq 19,20,21,22,23 on simple_mfd1
gpiobus1: <OFW GPIO bus> on gpio1
gpioregulator0: <GPIO controlled regulator> on ofwbus0
generic_timer0: <ARMv8 Generic Timer> irq 0,1,2,3 on ofwbus0
Timecounter "ARM MPCore Timecounter" frequency 12500000 Hz quality 1000
Event timer "ARM MPCore Eventtimer" frequency 12500000 Hz quality 1000
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
cpu1: <Open Firmware CPU> on cpulist0
uart0: <Marvell Armada 3700 UART> mem 0x12000-0x123ff irq 4 on simplebus1
uart0: console (115200,n,8,1)
gpioc0: <GPIO controller> on gpio0
gpioc1: <GPIO controller> on gpio1
xhci0: <Generic USB 3.0 controller> mem 0x58000-0x5bfff irq 5 on simplebus1
xhci0: 32 bytes context size, 32-bit DMA
usbus0 on xhci0
sdhci_xenon0: <Armada Xenon SDHCI controller> mem 0xd0000-0xd02ff,0x1e808-0x1e80b on simplebus1
sdhci_xenon0: Can't allocate IRQ
device_attach: sdhci_xenon0 attach returned 12
sdhci_xenon0: <Armada Xenon SDHCI controller> mem 0xd8000-0xd82ff,0x17808-0x1780b on simplebus1
sdhci_xenon0: Can't allocate IRQ
device_attach: sdhci_xenon0 attach returned 12
ahci0: <AHCI SATA controller> mem 0xe0000-0xe1fff irq 6 on simplebus1
ahci0: AHCI v1.30 with 1 6Gbps ports, Port Multiplier supported with FBS
ahcich0: <AHCI channel> at channel 0 on ahci0
mvneta0: <NETA controller> mem 0x30000-0x3001f on simplebus1
mvneta0: could not allocate resources
device_attach: mvneta0 attach returned 6
iichb0: <Marvell Armada 37x0 IIC controller> mem 0x11000-0x110ff on simplebus1
iichb0: cannot allocate interrupt
device_attach: iichb0 attach returned 6
spi0: <Armada 37x0 SPI controller> mem 0x10600-0x1064f on simplebus1
spi0: cannot allocate interrupt
device_attach: spi0 attach returned 6
armv8crypto0: <AES-CBC,AES-XTS,AES-GCM>
Timecounters tick every 1.000 msec
CPU  0: ARM Cortex-A53 r0p4 affinity:  0
                   Cache Type = <64 byte D-cacheline,64 byte I-cacheline,VIPT ICache,64 byte ERG,64 byte CWG>
 Instruction Set Attributes 0 = <CRC32,SHA2,SHA1,AES+PMULL>
 Instruction Set Attributes 1 = <>
 Instruction Set Attributes 2 = <>
         Processor Features 0 = <GIC,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
Release APs...done
usbus0: 5.0Gbps Super Speed USB v3.0
Trying to mount root from ufs:/dev/ada0s2a [rw]...
ugen0.1: <Generic XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Generic XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <InnoLite SATA Slim D150Q 110520B> ATA8-ACS SATA 2.x device
ada0: Serial Number 20120116AAT0IDC000A5
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: 15272MB (31277232 512 byte sectors)
uhub0: 2 ports with 2 removable, self powered
WARNING: /: TRIM flag on fs but disk does not support TRIM
Warning: no time-of-day clock registered, system time will not be set accurately
Dual Console: Serial Primary, Video Secondary
Setting hostuuid: c6ecb217-4213-4b3a-b0c5-675ae5662ce6.
Setting hostid: 0xe66901e0.
Starting file system checks:
/dev/ada0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/ada0s2a: clean, 1109318 free (1102 frags, 138527 blocks, 0.1% fragmentation)
Mounting local filesystems:.
ELF ldconfig path: /lib /usr/lib /usr/lib/compat
Setting hostname: EspressoBin.
Setting up harvesting: [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,[NET_ETHER],NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED
Feeding entropy: .
lo0: link state changed to UP
Starting Network: lo0.
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
Starting devd.
add host 127.0.0.1: gateway lo0 fib 0: route already in table
add host ::1: gateway lo0 fib 0: route already in table
add net fe80::: gateway ::1
add net ff02::: gateway ::1
add net ::ffff:0.0.0.0: gateway ::1
add net ::0.0.0.0: gateway ::1
Updating /var/run/os-release done.
Updating motd:.
Clearing /tmp (X related).
Creating and/or trimming log files.
Starting syslogd.
Mounting late filesystems:.
Performing sanity check on sshd configuration.
Starting sshd.
Starting cron.
Starting background file system checks in 60 seconds.

Tue Sep  5 01:52:50 UTC 2023

FreeBSD/arm64 (EspressoBin) (ttyu0)
 
Phishfry said:
This is the problem with the 2020 firmware. Networking is not right.
Click to expand...
just had a look in the u-boot 2020.10 provided dtb
neta@3000 does not declare an interrupt also the address space is 0x20 wide instead of 0x4000, also has no clocks declared
can you try to use 2022 dtb with 2020 u-boot
just load it from loader prompt and see if it works
if it work you can make it permanent by altering loader.conf
 
Thanks for the help.
Let me add that networking works with the 2022 flash-image.
At least I get a primary interface. I didn't mess with the switch.
With the 2020 image if I run dhcp command from u-boot I see an IP gets assigned.

I will test out other dtb as I am using the four compiled from our source tree /contrib/.

I noticed that ganbolds OPNSense image seems to be using the same dtb as the one in FreeBSD /boot/dtb/marvell/
At least bitwise it seems the same. This one is different than the ones I compiled from source.
I discounted it as there are 4 different dts v5,v5-emmc,v7,v7-emmc in our source tree.
This is because ethernet jacks are different between v5 and v7 boards.
I do notice that u-boot source tree has a single dts for espressobin.
Need to study differences more.

I was also wanting to boot purely from SATA and with jumpers it is possible. BUBT cannot flash to SCSI though...
Maybe dd right to SATA with flash-image.bin I dunno. Many learning experiences on this board.

I also am wondering if I even need Ganbolds OPNSense u-boot from his image. Maybe SPI u-boot is enough.
Many experiments needed. So little time.
 
Experiment 1: Try and boot FreeBSD image copied to SATA without u-boot flashed to bootsector.

Pass: With Armbian 2020 flash-image on SPI I can boot up FreeBSD on SATA without any modification.

Method: Use ROCKPRO 13.2-RELEASE image.
Blank the bootsector.
dd if=/dev/zero of=/dev/da0 bs=512 seek=40 count=32728

One glitch. It stalls at boot loader.
set rootdev=disk0p1:
boot

To make permanent add to /boot/loader.conf

So with this arrangement I have network issue still but SPI u-boot is enough for EFI FreeBSD on SATA.
I am using the default dtb's in /boot/dtb/. Nothing added.

Conclusion: The OPNSense image was a red herring. u-boot from that is not needed. SPI u-boot is sufficient.
 
Moving forward with those findings I decided to flash SPI to newest for debug. 2022 from Armbian.

Code: 
TIM-1.0
mv_ddr-devel-g251bc63 DDR4 16b 1GB 1CS
WTMI-devel-18.12.1-1d97715
WTMI: system early-init
SVC REV: 5, CPU VDD voltage is invalid, using default value: 1.202V
Setting clocks: CPU 1200 MHz, DDR 750 MHz
CZ.NIC's Armada 3720 Secure Firmware 0b68a33-dirty (May 16 2022 17:51:06)
Running on unknown board
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v2.6(release):a921da5e
NOTICE:  BL1: Built : 17:55:42, May 16 2022
NOTICE:  BL1: Booting BL2
NOTICE:  BL2: v2.6(release):a921da5e
NOTICE:  BL2: Built : 17:55:42, May 16 2022
NOTICE:  BL1: Booting BL31
NOTICE:  BL31: v2.6(release):a921da5e
NOTICE:  BL31: Built : 17:55:42, May 16 2022


U-Boot 2022.04-armbian (May 16 2022 - 17:50:52 +0000)

DRAM:  1 GiB
Core:  38 devices, 20 uclasses, devicetree: fit
WDT:   Not starting watchdog@8300
Comphy chip #0:
Comphy-0: USB3_HOST0    5 Gbps
Comphy-1: PEX0          5 Gbps
Comphy-2: SATA0         6 Gbps
Target spinup took 0 ms.
AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: ncq led only pmp fbss pio slum part sxs
PCIe: Link down
MMC:   sdhci@d0000: 0, sdhci@d8000: 1
Loading Environment from SPIFlash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 4 KiB, total 4 MiB
OK
Model: Globalscale Marvell ESPRESSOBin Board
Net:   eth0: ethernet@30000
Hit any key to stop autoboot:  0
=>

So the issue is not SATA, but the newer u-boot flash finds the eMMC, which confuses FreeBSD boot sequence.

So I may need to modify the DTB to disable the eMMC.

Code: 
=> mmc list
sdhci@d0000: 0
sdhci@d8000: 1

=> mmc info
MMC: no card present

=> mmc dev 1
switch to partitions #0, OK
mmc1(part 0) is current device
=> mmc info
Device: sdhci@d8000
Manufacturer ID: 15
OEM: 0
Name: 4FTE4R
Bus Speed: 52000000
Mode: MMC High Speed (52MHz)
Rd Block Len: 512
MMC version 5.1
High Capacity: Yes
Capacity: 3.6 GiB
Bus Width: 8-bit
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 3.6 GiB WRREL
Boot Capacity: 4 MiB ENH
RPMB Capacity: 512 KiB ENH
Boot area 0 is not write protected
Boot area 1 is not write protected
=>

Loader Prompt showing the problem (Two disk devices now):

Code: 
Type '?' for a list of commands, 'help' for more detailed help.
OK lsdev
disk devices:
    disk0:    7634944 X 512 blocks (removable)
    disk1:    31277232 X 512 blocks
      disk1p1: EFI
      disk1p2: FreeBSD UFS
http: (unknown)
net devices:
    net0:
OK show rootdev
variable 'rootdev' not found
OK set rootdev=disk1p2
OK show currdev
disk1p2:
OK show rootdev
disk1p2
OK
boot

The SATA disk1 is now missing and only eMMC showing:
Code: 
mountroot> ?

List of GEOM managed disk devices:
  diskid/DISK-2F45FEFC mmcsd0boot1 mmcsd0boot0 mmcsd0

mountroot>
panic: mountroot: unable to (re-)mount root.
cpuid = 1
time = 215
 
I used the aach64 installer image on memstick and attempted to install FreeBSD onto eMMC.

It recognizes the eMMC but has trouble formatting it in partitioning stage.

This is probably a flaw in bsdinstall as this error appears ARM64 wide.
I saw the same problem on Rockchip I know. Flashing OS image to eMMC no problem.

Because all prebuilt ARM images are 5+Gigs now I need to rework a smaller image for 4GB eMMC.

This problem seems to parallel my Rock64 eMMC 'not booting' now issue.
Works from sd-card but losses root mount at re-root with eMMC.

I will figure this stuff out. seems the dtb may be the answer. Need to start de-compiling dtb to set to disabled.

How can I get u-boot to disable eMMC... I erased it from there.
I guess there is the fdt command. Can I set to disabled with that?

sdhci@d8000=disabled

Maybe I need to break out the dremel to disable?

I dread building A-TF for A_3700. My cross OS compiling skills are very weak.
Somebody please build that on FreeBSD. Then we can try and make our own flash-bin from u-boot build.
Depending on Armbian for u-boot stinks.
My env has grown from 1300 to 4370 and it's mostly Linux cruft.
Environment size: 4370/65532 bytes
Click to expand...
 
covacat said:
can you try to use 2022 dtb with 2020 u-boot
just load it from loader prompt and see if it works
if it work you can make it permanent by altering loader.conf
Click to expand...
Thanks so much for helping.
When experimenting with these different dtb I have been using u-boot to set fdt_name to try different files.
env set fdt_name armada-3720-espressobin-v7-emmc.dtb
This should carry thought to FreeBSD right?

Do I need all these other fdt env settings in u-boot? Isn't name enough?

fdt_addr=0x6f00000
fdt_addr_r=0x6f00000
fdtcontroladdr=3fadcf40
fdtfile=marvell/armada-3720-espressobin.dtb
 
i don't mess with u-boot.env i use loader.conf like this
#h616_name="/boot/dtb/allwinner/sun50i-h616-jj.dtb"
#h616_name="/boot/dtb/allwinner/sun50i-h616-orangepi-zero2.dtb"
h616_name="/boot/dtb/allwinner/zero3.dtb"
h616_load="YES"
h616_type="dtb"
vfs.root.mountfrom="ufs:/dev/ufs/root"

the vfs.root ... line is to force root from the sd card (the android box (the sun50i-h616-jj.dtb) has emmc which gets to be mmcsd0 so i labeled the ufs partitition
with tunefs

or to test from the loader prompt
load -t dtb /path/to/test.dtb
 
From the loader prompt it looks like the eMMC is marked disabled already.

Code: 
OK fdt prop /soc/internal-regs@d0000000/sdhci@d8000
compatible = "marvell,armada-3700-sdhci", "marvell,sdhci-xenon"
reg = <0x000d8000 0x00000300 0x00017808 0x00000004>
interrupts = <0x00000000 0x0000001a 0x00000004>
clocks = <0x0000000b 0x00000000>
clock-names = "core"
status = "disabled"
phandle = <0x00000034>
OK

Thanks to this excellent document:
 
So the eMMC shows up in FreeBSD with Armbian u-boot 2022 even though disabled in dtb yet in dmesg it shows up as mmcsd0 READ ONLY.
Even though I zero'ed it.
Even when I set status="enable" from loader fdt command.

What could be setting it to READ ONLY? Probably device tree.


covacat said:
vfs.root.mountfrom="ufs:/dev/ufs/root"

the vfs.root ... line is to force root from the sd card (the android box (the sun50i-h616-jj.dtb) has emmc which gets to be mmcsd0 so i labeled the ufs partitition
with tunefs
Click to expand...
Out of desperation I tried tunefs -L and set name to rootfs. fstab uses that name so I figured it can't hurt.

I did forget to add the loader helper.vfs.root.mountfrom="ufs:/dev/ufs/rootfs"
 
it has 2 sdhci controllers at d0000 and d8000 and one is sdcard and one emmc
one has a cd-gpios (the sd) and wp-inverted card-detect and write-protect inverted so it should be the sdcard, not the emmc
 
Phishfry said:
I dread building A-TF for A_3700. My cross OS compiling skills are very weak.
Somebody please build that on FreeBSD. Then we can try and make our own flash-bin from u-boot build.
Depending on Armbian for u-boot stinks.
My env has grown from 1300 to 4370 and it's mostly Linux cruft.
Click to expand...

Meaning this? http://tinkering-is-fun.blogspot.com/2019/02/espressobin-building-u-boot.html

Also, where can I find a pre-compiled U-Boot 2020.10-rc3 (Sep 01 2020 - 14:44:01 +0000) flash-image-ddr4-1g-1cs-1000_800.bin ? Or will I have to compile it myself?
 
Are you sure you are booting from SPI? Perhaps it is using u-boot on eMMC???
You need to set jumpers correctly to boot from Serial NOR (SPI) too.

ESPRESSObin Wiki | Ports and Interfaces

ESPRESSObin Wiki
wiki.espressobin.net wiki.espressobin.net

To wipe eMMC and possible u-boot choose the correct mmc dev from uboot, to make it active and use command:
mmc erase 0 2000000
 
The OpenSUSE page has real good details. It covers V5 boards.

HCL:EspressoBin - openSUSE Wiki

en.opensuse.org en.opensuse.org

I did not find this step necessary. Used u-boot in SPI to flash.
boot the board using alternative (not SPI Flash) way and obtain U-boot command line;
Click to expand...

Here is me flashing:
Code: 
Hit any key to stop autoboot:  0
=> bubt flash-image.bin spi usb
Burning U-Boot image "flash-image.bin" from "usb" to "spi"
Bus usb@58000: Register 2000104 NbrPorts 2
Starting the controller
USB XHCI 1.00
Bus usb@5e000: USB EHCI 1.00
scanning bus usb@58000 for devices... 2 USB Device(s) found
scanning bus usb@5e000 for devices... 1 USB Device(s) found
Image checksum...OK!
Erasing 991232 bytes (242 blocks) at offset 0 ...Done!
Writing 988048 bytes from 0x6000000 to offset 0 ...Done!
 
I was able to use the FreeBSD 13.2 USB Memstick image for aarch64 and install to SATA.
The problem with eMMC being READONLY probably made bsdinstall fail with that locked target.
 
You must log in or register to reply here.
Back
Top