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

T

t_e_s_t_o_cz

Hello

I'm happily using R13 or S13 with this SBC but when I connect SSD to its SATA 3.0 port, the drive is not attached for some reason.
Code: 
root@myespresso:~ # dmesg | grep -i ahci
ahci0: <AHCI SATA controller> mem 0xe0000-0xe0177 irq 27 on simplebus1
ahci0: AHCI v1.30 with 1 6Gbps ports, Port Multiplier supported with FBS
ahcich0: <AHCI channel> at channel 0 on ahci0
device_attach: ahcich0 attach returned 6

I think the kernel driver and everything else should be fine. SATA support is implemented as AHCI generic.

Can anyone confirm SATA works on his ESPRESSObin SBC with FreeBSD ?

PS: I've attached C14 "boot -v" boot log.

T.
 

Attachments

  • bootC14-log.txt
    10.6 KB · Views: 94
Yes some people have this working. It seems v7 is better supported.

Are you using version 5 or v7. If unknown does it have a molex power connector on board?
Amount of RAM too?

Is it new or used? I ask because SPI populated or not.
If a used board the SPI Rom might have older u-boot on it. So you need to short out SPI on boot to bypass.
 
Sorry. I missed your problem.

Try booting to u-boot prompt and type sata info to check the drive.

You might need to add a small u-boot script to help the SATA detection.
 
Here is what my Hummingboards setup looks like.
You must catch u-boot at the right time:

Code: 
Hit any key to stop autoboot:  0
=> sata
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part
SATA Device Info:
S/N: 162313400264
Product model number: SanDisk SD7SF6S256G1122
Firmware version: X3540000
Capacity: 500118192 sectors
sata - SATA sub system

Usage:
sata init - init SATA sub system
sata stop [dev] - disable SATA sub system or device
sata info - show available SATA devices
sata device [dev] - show or set current device
sata part [dev] - print partition table
sata read addr blk# cnt
sata write addr blk# cnt


=> sata info
Device 0: Model: SanDisk SD7SF6S256G1122 Firm: X3540000 Ser#: 162313400264
Type: Hard Disk
Supports 48-bit addressing
Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)


So from here you type boot and it starts up.

On Hummingboard I don't need a script to start SATA but BananaPi-M1 I do.
All the script does is run the two above commands.
forums.freebsd.org

u-boot env.txt

The aarch64 (ARM64) u-boot was found from FreeBSD ports in sysutils/u-boot-*. There was some information how to install it. Sometimes the U-Boot is used with uEnv.txt or similar file to configure it. The U-Boot reads the file and sets variables. At least in Armbian Linux. Is there any options to...
forums.freebsd.org forums.freebsd.org
I think the script also gives the SATA drive a chance to start.
You are essentially adding a slight delay to u-boot to allow the drive to initialize.
mkimage is found in sysutils/u-boot-tools

First though you must should make sure the drive is showing up manually from the u-boot command prompt.
 
Many thanks , I will test these ASAP.

Its truly v5 Espressobin. Having it quite some time already.
Just recently, I repurposed it -- did u-boot update (Armbian version) and u-boot env default.

T.
 
Well , I did the u-boot prompt things:

Sata seems not working
Code: 
=> sata info
Cannot scan SATA device 0 (err=-38)

=> sata stop 0
=> sata init
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 
Cannot scan SATA device 0 (err=-38)

but scsi command detects my SSD
Code: 
=> scsi info
=> scsi scan
scanning bus for devices...
  Device 0: (0:0) Vendor: ATA Prod.: Patriot Burst El Rev: HPS1
            Type: Hard Disk
            Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)
=> scsi info
Device 0: (0:0) Vendor: ATA Prod.: Patriot Burst El Rev: HPS1
            Type: Hard Disk
            Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)
=>

When continued
Code: 
=> boot


I made escape to to loader prompt to double check
Code: 
Type '?' for a list of commands, 'help' for more detailed help.
OK 
OK lsdev
disk devices:
    disk0:    61069312 X 512 blocks (removable)
      disk0p1: EFI
      disk0p2: FreeBSD swap
      disk0p3: FreeBSD ZFS
    disk1:    234441648 X 512 blocks


boot
this disk1 is my SSD , great

However when FreeBSD boots , I still see ahci channel empty and no SSD attached .
Any ideas please ?

PS: I;ve attached the new boot log , using boot.scr with "scsi scan" works

T.
 

Attachments

  • boot7-log.txt
    11.1 KB · Views: 71
It appears that AHCI is working.
ahci0: <AHCI SATA controller> mem 0xe0000-0xe0177 irq 27 on simplebus1
ahci0: AHCI v1.30 with 1 6Gbps ports, Port Multiplier supported with FBS
ahcich0: <AHCI channel> at channel 0 on ahci0
device_attach: ahcich0 attach returned 6
Click to expand...

I dunno why the drive is not showing.

t_e_s_t_o_cz said:
lsdev disk devices:
disk0: 61069312 X 512 blocks (removable) disk0p1: EFI disk0p2: FreeBSD swap disk0p3: FreeBSD ZFS
disk1: 234441648 X 512 blocks
Click to expand...
Do you have a file structure on the mSATA showing as disk1?

I would flash only u-boot to microSD and FreeBSD Generic Arm Image to mSATA
You might need to fiddle with these settings from loader prompt if successful.
set currdev=
set rottdev=
The problem with this approach is you are using Armbian u-boot. It might not recognize the FreeBSD loader early.

This is the approach I took on RockPro64 and Hummingboard. u-boot kicker on microSD and rest on SATA/NVMe.
 
I don't have an device_attach line for my ahci in dmesg.
Maybe it doesn't spit one out if all good.
ahci0: <i.MX6 Integrated AHCI controller> mem 0x2200000-0x2203fff irq 14 on simplebus0
ahci0: AHCI v1.30 with 1 3Gbps ports, Port Multiplier supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
Click to expand...

So "returned 6" is an error state. I learned something new today.
 
Phishfry said:
It appears that AHCI is working.


I dunno why the drive is not showing.


Do you have a file structure on the mSATA showing as disk1?

I would flash only u-boot to microSD and FreeBSD Generic Arm Image to mSATA
You might need to fiddle with these settings from loader prompt if successful.
set currdev=
set rottdev=
The problem with this approach is you are using Armbian u-boot. It might not recognize the FreeBSD loader early.

This is the approach I took on RockPro64 and Hummingboard. u-boot kicker on microSD and rest on SATA/NVMe.
Click to expand...

disk0 = SD card with FreeBSD installed
disk1 = now empty , SATA SSD.

I don't really intent to boot from the SATA SSD, if its that what you understood. I do like to boot from SD/USB whatever and use the SATA SSD as data-disk.

I thought would be a good to check if the SATA is present also within bootloader environment.

ESPRESSObit has got SPI and mine loads u-boot from it. If I understand correctly, your workarounds at RockPro64/Hummingboard succeeded to boot EFI-loader and the rest from SATA with using u-boot load from SD card...thinking, if there's a chance EFI-loader drops/stops my SATA device because its not using it and so its not detected/attached by ahci kernel drivers...
 
yuripv79 said:
Anything non-0 is bad, and gets that message printed. Sadly, even looking at the boot -v output above, there are no hints as to why it happened.

Though it does not seem to be working even on the level above the OS:
Click to expand...
yes, its wierd, u-boot sata command fails to scan it , however scsi command succeeds .... could this be a sign of HW incompatibility with AHCI kernel divers ??

There's been a patch to kernel which adds FDT tag of "armada-3700-ahci" to ahci_generic kernel driver. There must be a reason why. I'm gonna ask the commiter , if it really was an Espressobin like board or what HW.

ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 should occur but device_attach: ahcich0 attach returned 6 shows up instead.

On the other side, I've quickly tested OpenBSD install disk and Armbian boot disk. Both systems detect my SATA SSD nicely.
 
t_e_s_t_o_cz said:
yes, its wierd, u-boot sata command fails to scan it , however scsi command succeeds .... could this be a sign of HW incompatibility with AHCI kernel divers ??
Click to expand...
No there are two different ways disk drives show up in u-boot. SCSI or SATA.
I wouldn't give it much thought.
I am surprised that both are baked into Armbian u-boot configuration.
Most u-boot board config files use either one or the other.

On BananaPi-M1 u-boot uses SCSI and Hummingboard uses SATA.
They don't offer both disk tools. Only the one that works for that platform.
 
t_e_s_t_o_cz said:
adds FDT tag of "armada-3700-ahci" to ahci_generic kernel driver.
Click to expand...
Yes that is the right direction.
There does not seem to be any SOC based driver in use.
I was thinking something like <Marvell AHCI controller>.

Yours:
ahci0: <AHCI SATA controller> mem 0xe0000-0xe0177 irq 27 on simplebus1

Mine:
ahci0: <i.MX6 Integrated AHCI controller> mem 0x2200000-0x2203fff irq 14 on simplebus0
 
Phishfry, thanks for the explanation of u-boot SATA/SCSI,

I've actually built my own OPNsense the last year. Its using FreeBSD 13 and FreeBSD 13 aarch64 EFI binary, so it is about the same as booting aarch64 GENERIC.
Using my third ESPRESSObin (with Armbian u-boot too). Anyway I've checked my logs of it and result is the same misbehaviour of AHCI.

I also think, if its worth to test the original ESPRESSObin u-boot, however it might not be able to boot aarch64 EFI, as mentioned here https://wiki.freebsd.org/arm64/ESPRESSObin[\url]
 
I actually ended up getting this to work with that above OPNSense image.
I ditched my v5 Espressobin boards and got v7 boards.
What a difference. Boot Jumpers actually work right.
I was able to flash SPI from uboot 2017 to uboot 2020 with Armbian flash files.

I used Ganbold image from above as foundation as it works.
Wiped root partition and stuffed 13.2-RELEASE inside. Kept EFI but freshened.
Modified fstab to sata disk. It finally works.
Using 32GB SATA DOM booting from Armbian SPI flash.

I feel like I have taken two steps forward.
 
I am trying to get yrzr opnsense image to boot on my Espressobinv7 with a sata ssd plugged in, I am having trouble with it. Been able to boot the image off an mmc sd card without any issues. But when trying to boot off the ssd it appears to boot halfway but then stop when trying to boot the GEOM managed disk which doesn't show up. I've found out that my issue may be related that i am booting off u-boot Armbian 2022.04 and that appears to only have 'scsi' option that reads my ssd but not 'sata' ? is this correct? Or is there any way i can force the ssd to be detected when trying to boot via 'scsi'? Am I doing this all wrong? any insight will be much appreciated. Output is below.

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: 1.108V
Setting clocks: CPU 1000 MHz, DDR 800 MHz
CZ.NIC's Armada 3720 Secure Firmware 0b68a33-dirty (May 16 2022 17:51:06)
Running on ESPRESSObin
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v2.6(release):a921da5e
NOTICE:  BL1: Built : 17:54:27, May 16 2022
NOTICE:  BL1: Booting BL2
NOTICE:  BL2: v2.6(release):a921da5e
NOTICE:  BL2: Built : 17:54:27, May 16 2022
NOTICE:  BL1: Booting BL31
NOTICE:  BL31: v2.6(release):a921da5e
NOTICE:  BL31: Built : 17:54:27, 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 w25q32dw 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
scanning bus for devices...
  Device 0: (0:0) Vendor: ATA Prod.: SanDisk SD6SB1M1 Rev: X231
            Type: Hard Disk
            Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
Device 0: (0:0) Vendor: ATA Prod.: SanDisk SD6SB1M1 Rev: X231
            Type: Hard Disk
            Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
... is now current device
1256188 bytes read in 27 ms (44.4 MiB/s)
16032 bytes read in 5 ms (3.1 MiB/s)
MMC: no card present
Scanning disk [email]sdhci@d0000.blk[/email]...
Disk [email]sdhci@d0000.blk[/email] not ready
Scanning disk ahci_scsi.id0lun0...
Found 3 disks
No EFI system partition
Booting /EFI\BOOT\bootaa64.efi
Consoles: EFI console
    Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm64 EFI loader, Revision 1.1
   Command line arguments: root=PARTUUID=00000000-02 rw rootwait
   Image base: 0x3e98c000
   EFI version: 2.90
   EFI Firmware: Das U-Boot (rev 8226.1024)
   Console: efi (0x1000)
   Load Path: /EFI\BOOT\bootaa64.efi
   Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/Scsi(0,0)/HD(1,MBR,0x8e6515d4,0x800,0x19000)
Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/Scsi(0,0)/HD(1,MBR,0x8e6515d4,0x800,0x19000)
Setting currdev to disk0p1:
Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/Scsi(0,0)/HD(2,MBR,0x8e6515d4,0x19800,0x5e6800)
Setting currdev to disk0p2:
Loading /boot/defaults/loader.conf
Loading /boot/defaults/loader.conf
Loading /boot/device.hints
Loading /boot/loader.conf
console vidconsole is invalid!
Available consoles:
    efi
    comconsole
Loading /boot/loader.conf.local
|
c-
console vidconsole is invalid!
no valid co  ______  _____  _____
Available c /  __  |/ ___ |/ __  |
    efi     | |  | | |__/ | |  | |___  ___ _ __  ___  ___
    comcons | |  | |  ___/| |  | / __|/ _ \ '_ \/ __|/ _ \
|           | |__| | |    | |  | \__ \  __/ | | \__ \  __/
            |_____/|_|    |_| /__|___/\___|_| |_|___/\___|console vidconsole is invalid!
Available consoles:
 +-------------------console vidconsole is invalid!@@@@@@@@@@@@@@@@@@@@@@@@@@
Available consoles:                        |   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    1. Boot Multi user [Enter]             |   @@@@@                    @@@@@
    2. Boot Single user                    |       @@@@@            @@@@@
A|ai3. Escape to loader prompt             |    @@@@@@@@@@@       @@@@@@@@@@@
 |  4. Reboot                              |         \\\\\         /////
 |  5. Cons: Dual (Serial primary)         |   ))))))))))))       (((((((((((
 |                                         |         /////         \\\\\
 |  Options:                               |    @@@@@@@@@@@       @@@@@@@@@@@
 |  6. Kernel: default/kernel (1 of 1)     |       @@@@@            @@@@@
 |  7. Boot Options                        |   @@@@@                    @@@@@
 |                                         |   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 |                                         |   @@@@@@@@@@@@@@@@@@@@@@@@@@@@
 +-----------------------------------------+
   Autoboot in 0 seconds. [Space] to pause     23.1 ``Quintessential Quail'' console vidconsole is invalid!
Available consoles:
Loading kernel...
/boot/kernel/kernel text=0x2a8 text=0x928b30 text=0x21cf64 data=0x1b25d0 data=0x0+0x38a000 syms=[0x8+0x131940+0x8+0x156d2b]
Loading configured modules...!
/boot/kernel/pfsync.ko text=0x2f63 text=0x7f1c data=0xb38+0x8 syms=[0x8+0x1830+0x8+0x1192]
loading required module 'pf'
/boot/kernel/pf.ko text=0xe41c text=0x3e7d4 data=0x59f0+0x3bc syms=[0x8+0x5958+0x8+0x4727]
/boot/kernel/if_bridge.ko text=0x36a3 text=0x710c data=0xd38+0x8 syms=[0x8+0x1bd8+0x8+0x15d7]
loading required module 'bridgestp'
/boot/kernel/bridgestp.ko text=0x12e4 text=0x4acc data=0x2c8+0x28 syms=[0x8+0xb88+0x8+0x6e9]
/boot/kernel/if_enc.ko text=0x15ca text=0x934 data=0x750 syms=[0x8+0xca8+0x8+0xb71]
/boot/entropy size=0x1000
/boot/kernel/pflog.ko text=0xf78 text=0x898 data=0x430 syms=[0x8+0x9f0+0x8+0x712]
/boot/kernel/if_gre.ko text=0x2736 text=0x4938 data=0x8c8+0x40 syms=[0x8+0x16f8+0x8+0xfaf]
/boot/kernel/if_lagg.ko text=0x3d27 text=0xa628 data=0xd18+0x8 syms=[0x8+0x1cb0+0x8+0x15bd]
loading required module 'if_infiniband'
/boot/kernel/if_infiniband.ko text=0x1102 text=0x10fc data=0x300+0x8 syms=[0x8+0x8d0+0x8+0x59a]
/boot/kernel/carp.ko text=0x33ec text=0x6e54 data=0xc60+0x48 syms=[0x8+0x1980+0x8+0x1225]
/etc/hostid size=0x25
Using DTB provided by EFI at 0x7f00000.
EFI framebuffer information:
addr, size     0x0, 0x0
dimensions     0 x 0
stride         0
masks          0x00000000, 0x00000000, 0x00000000, 0x00000000
---<<BOOT>>---
KDB: debugger backends: ddb
KDB: current backend: ddb
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.1-RELEASE-p8 stable/23.1-n250461-cf0d42d1ca7 SMP arm64
FreeBSD clang version 13.0.0 ([email]git@github.com[/email]:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303)
VT: init without driver.
module firmware already present!
real memory  = 1071546368 (1021 MB)
avail memory = 1019772928 (972 MB)
Starting CPU 1 (1)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
random: unblocking device.
random: entropy device external interface
MAP 3eac4000 mode 2 pages 1
MAP 3eac8000 mode 2 pages 3
MAP 3eacc000 mode 2 pages 4
MAP 3fef0000 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,0x1d80000-0x1d81fff,0x1d90000-0x1d91fff,0x1da0000-0x1dbffff irq 28 on simplebus1
gpio0: <Armada 37x0 North Bridge GPIO Controller> mem 0x13800-0x138ff,0x13c00-0x13c1f irq 29,30,31,32,33,34,35,36,37,38,39,40 on simple_mfd0
gpiobus0: <OFW GPIO bus> on gpio0
gpio1: <Armada 37x0 South Bridge GPIO Controller> mem 0x18800-0x188ff,0x18c00-0x18c1f irq 41,42,43,44,45 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
pmu0: <Performance Monitoring Unit> irq 4 on ofwbus0
spi0: <Armada 37x0 SPI controller> mem 0x10600-0x10fff irq 6 on simplebus1
uart0: <Marvell Armada 3700 UART> mem 0x12000-0x121ff irq 9,10,11 on simplebus1
uart0: console (115200,n,8,1)
gpioc0: <GPIO controller> on gpio0
gpioc1: <GPIO controller> on gpio1
mvneta0: <NETA controller> mem 0x30000-0x33fff irq 14 on simplebus1
mvneta0: version is 10
mvneta0: Ethernet address: 00:51:82:11:22:00
mdio0: <MDIO> on mvneta0
mdioproxy0: <MII/MDIO proxy, MDIO side> on mdio0
e6000sw0: <Marvell 88E6341> on mdio0
e6000sw0: multi-chip addressing mode (0x1)
e6000sw0: CPU port at 0
e6000sw0: fixed port at 0
e6000sw0: PHY at port 1
miibus0: <MII bus> on e6000sw0
e1000phy0: <Marvell 88E1000 Gigabit PHY> PHY 17 on miibus0
e1000phy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
e6000sw0: PHY at port 2
miibus1: <MII bus> on e6000sw0
e1000phy1: <Marvell 88E1000 Gigabit PHY> PHY 18 on miibus1
e1000phy1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
e6000sw0: PHY at port 3
miibus2: <MII bus> on e6000sw0
e1000phy2: <Marvell 88E1000 Gigabit PHY> PHY 19 on miibus2
e1000phy2:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
e6000sw0: switch is ready.
etherswitch0: <Switch controller> on e6000sw0
xhci0: <Generic USB 3.0 controller> mem 0x58000-0x5bfff irq 16 on simplebus1
xhci0: 32 bytes context size, 32-bit DMA
usbus0 on xhci0
ehci0: <Marvell Integrated USB 2.0 controller> mem 0x5e000-0x5efff irq 17 on simplebus1
usbus1: EHCI version 1.0
usbus1 on ehci0
safexcel0: <SafeXcel EIP-97 crypto accelerator> mem 0x90000-0xaffff irq 18,19,20,21,22,23 on simplebus1
sdhci_xenon0: <Armada Xenon SDHCI controller> mem 0xd0000-0xd02ff,0x1e808-0x1e80b irq 25 on simplebus1
ahci0: <AHCI SATA controller> mem 0xe0000-0xe0177 irq 27 on simplebus1
ahci0: AHCI v1.30 with 1 6Gbps ports, Port Multiplier supported with FBS
ahcich0: <AHCI channel> at channel 0 on ahci0
device_attach: ahcich0 attach returned 6
armv8crypto0: <AES-CBC,AES-XTS,AES-GCM>
Timecounters tick every 1.000 msec
mvneta0: link state changed to UP
e6000sw0port1: link state changed to DOWN
e6000sw0port2: link state changed to DOWN
e6000sw0port3: link state changed to DOWN
usbus0: 5.0Gbps Super Speed USB v3.0
usbus1: 480Mbps High Speed USB v2.0
spibus0: <OFW SPI bus> on spi0
spibus0: <unknown card> at cs 0 mode 0
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 = <>
         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
ugen1.1: <Marvell EHCI root HUB> at usbus1
ugen0.1: <Generic XHCI root HUB> at usbus0
uhub0 on usbus1
uhub1 on usbus0
uhub0: <Marvell EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
uhub1: <Generic XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Trying to mount root from ufs:/dev/ufs/OPNsense [rw]...
uhub1: 2 ports with 2 removable, self powered
uhub0: 1 port with 1 removable, self powered
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
mountroot: waiting for device /dev/ufs/OPNsense...
Mounting from ufs:/dev/ufs/OPNsense failed with error 19.
Loader variables:
  vfs.root.mountfrom=ufs:/dev/ufs/OPNsense
  vfs.root.mountfrom.options=rw
Manual root filesystem specification:
  <fstype>:<device> [options]
      Mount <device> using filesystem <fstype>
      and with the specified (optional) option list.
    eg. ufs:/dev/da0s1a
        zfs:zroot/ROOT/default
        cd9660:/dev/cd0 ro
          (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
  ?               List valid disk boot devices
  .               Yield 1 second (for background tasks)
  <empty line>    Abort manual input
mountroot> ?
List of GEOM managed disk devices:

mountroot>
 
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
 
cyberpunked said:
i am booting off u-boot Armbian 2022.04 and that appears to only have 'scsi' option
Click to expand...
SCSI is SATA disk. I don't know why there are two different disk subsytems with uboot.

I recommend you flash the 2022 flash-image from Armbian to your SPI.
make sure you use the correct image.
 
covacat said:
the best way would be to add the missing bits to the driver/dtb
Click to expand...
There seems to be different dtb's floating around.

I recommend you compile the one from our source tree DTS.
All models are there.
v5
v5-emmc
v7
v7-emmc

forums.freebsd.org

In depth Device Tree Questions

I have some fundamental questions understanding the Device Tree syntax. Question One: Device Node numbers. Like this snippet: uart@20000000 { interrupt-parent = < 1 >; }; Where is the number 20000000 coming from? Where is this assigned from? I don't see it in the dts...
forums.freebsd.org forums.freebsd.org
 
I had trouble with the OS on the eMMC interfering so I used u-boot to erased it from u-boot.

mmc erase 0 2000000

Also bubt is backwards from normal source device/destination device.

bubt flash-image.bin spi usb
 
Phishfry said:
SCSI is SATA disk. I don't know why there are two different disk subsytems with uboot.

I recommend you flash the 2022 flash-image from Armbian to your SPI.
make sure you use the correct image.
Click to expand...
I thought I already spi flashed the latest armbian, isn't this right?
Console shows
U-Boot 2022.04-armbian (May 16 2022 - 17:50:52 +0000)
 
You must log in or register to reply here.
Back
Top