Helios64, tftpboot

I'm trying to load files over tftp to my Kobol Helios64. This box has 2 ethernet ports, one 2.5Gbit, and one 1Gbit. When I give any network related command, it gives a repeated 'dw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init'.
But the command 'net list' (according to 'help net' the only subcommand of net) gives

=> net list
dw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio buseth0 : ethernet@fe300000 64:62:66:d0:0a:2a

In Linux that MAC address is the address of the 1Gbit port.

Any idea how to tftpboot this box?

Full bootlog:

DDR Version 1.25 20210517
In
soft reset
SRX
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT

U-Boot SPL 2022.07-armbian-2022.07-Se092-Pa6d7-H8c72-Vbe65-Bda0a-R448a (Jul 22 2024 - 17:36:21 +0000)
Trying to boot from SPI
Trying to boot from MMC1
Card did not respond to voltage select! : -110
spl: mmc init failed with error: -95
Trying to boot from MMC2
NOTICE:  BL31: lts-v2.8.8(release):armbian
NOTICE:  BL31: Built : 17:36:06, Jul 22 2024
INFO:    GICv3 with legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    Maximum SPI INTID supported: 287
INFO:    plat_rockchip_pmu_init(1624): pd status 3e
INFO:    BL31: Initializing runtime services
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2022.07-armbian-2022.07-Se092-Pa6d7-H8c72-Vbe65-Bda0a-R448a (Jul 22 2024 - 17:36:21 +0000)

SoC: Rockchip rk3399
Reset cause: RST
DRAM:  3.9 GiB
PMIC:  RK808 
Core:  339 devices, 31 uclasses, devicetree: separate
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net:   dw_dm_mdio_init: mdio node is missing, registering legacy mdio busNo ethernet found.

scanning bus for devices...
Hit any key to stop autoboot:  0  0
=> help
?         - alias for 'help'
adc       - ADC sub-system
base      - print or set address offset
bdinfo    - print Board Info structure
blkcache  - block cache diagnostics and control
boot      - boot default, i.e., run 'bootcmd'
bootd     - boot default, i.e., run 'bootcmd'
bootefi   - Boots an EFI payload from memory
bootelf   - Boot from an ELF image in memory
bootflow  - Boot flows
booti     - boot Linux kernel 'Image' format from memory
bootm     - boot application image from memory
bootmenu  - ANSI terminal bootmenu
bootp     - boot image via network using BOOTP/TFTP protocol
bootvx    - Boot vxWorks from an ELF image
bootz     - boot Linux zImage image from memory
cmp       - memory compare
config    - print .config
coninfo   - print console devices and information
cp        - memory copy
crc32     - checksum calculation
dhcp      - boot image via network using DHCP/TFTP protocol
dm        - Driver model low level access
echo      - echo args to console
editenv   - edit environment variable
efidebug  - Configure UEFI environment
env       - environment handling commands
exception - Forces an exception to occur
exit      - exit script
ext2load  - load binary file from a Ext2 filesystem
ext2ls    - list files in a directory (default /)
ext4load  - load binary file from a Ext4 filesystem
ext4ls    - list files in a directory (default /)
ext4size  - determine a file's size
false     - do nothing, unsuccessfully
fastboot  - run as a fastboot usb or udp device
fatinfo   - print information about filesystem
fatload   - load binary file from a dos filesystem
fatls     - list files in a directory (default /)
fatmkdir  - create a directory
fatrm     - delete a file
fatsize   - determine a file's size
fatwrite  - write file into a dos filesystem
fdt       - flattened device tree utility commands
fstype    - Look up a filesystem type
fstypes   - List supported filesystem types
fsuuid    - Look up a filesystem UUID
go        - start application at address 'addr'
gpio      - query and control gpio pins
gpt       - GUID Partition Table
gzwrite   - unzip and write memory to block device
help      - print command description/usage
i2c       - I2C sub-system
iminfo    - print header information for application image
imxtract  - extract a part of a multi-image
itest     - return true/false on integer compare
led       - manage LEDs
ln        - Create a symbolic link
load      - load binary file from a filesystem
loadb     - load binary file over serial line (kermit mode)
loads     - load S-Record file over serial line
loadx     - load binary file over serial line (xmodem mode)
loady     - load binary file over serial line (ymodem mode)
loop      - infinite loop on address range
ls        - list files in a directory (default /)
lzmadec   - lzma uncompress a memory region
md        - memory display
md5sum    - compute MD5 message digest
mdc       - memory display cyclic
mdio      - MDIO utility commands
meminfo   - display memory information
mii       - MII utility commands
mm        - memory modify (auto-incrementing address)
mmc       - MMC sub system
mmcinfo   - display MMC info
mw        - memory write (fill)
mwc       - memory write cyclic
net       - NET sub-system
nfs       - boot image via network using NFS protocol
nm        - memory modify (constant address)
panic     - Panic with optional message
part      - disk partition related commands
pci       - list and access PCI Configuration Space
ping      - send ICMP ECHO_REQUEST to network host
pinmux    - show pin-controller muxing
pmic      - PMIC sub-system
poweroff  - Perform POWEROFF of the device
printenv  - print environment variables
pxe       - commands to get and boot from pxe files
random    - fill memory with random pattern
read      - Load binary data from a partition
regulator - uclass operations
reset     - Perform RESET of the CPU
rockusb   - use the rockusb protocol
run       - run commands in an environment variable
save      - save file to a filesystem
saveenv   - save environment variables to persistent storage
scsi      - SCSI sub-system
scsiboot  - boot from SCSI device
setenv    - set environment variables
setexpr   - set environment variable as the result of eval expression
sf        - SPI flash sub-system
sha1sum   - compute SHA1 message digest
showvar   - print local hushshell variables
size      - determine a file's size
sleep     - delay execution for some time
source    - run script from memory
sspi      - SPI utility command
strings   - display strings
sysboot   - command to get and boot from syslinux files
test      - minimal test like /bin/sh
tftpboot  - boot image via network using TFTP protocol
time      - run commands and summarize execution time
true      - do nothing, successfully
ums       - Use the UMS [USB Mass Storage]
unlz4     - lz4 uncompress a memory region
unzip     - unzip a memory region
usb       - USB sub-system
usbboot   - boot from USB device
version   - print monitor, compiler and linker version
=> printenv
altbootcmd=setenv boot_syslinux_conf extlinux/extlinux-rollback.conf;run distro_bootcmd
arch=arm
baudrate=1500000
board=helios64
board_name=helios64
board_rev=1.2
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootaa64.efi; if fdt addr -q ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi
boot_efi_bootmgr=if fdt addr -q ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr;fi
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf}
boot_net_usb_start=usb start
boot_pci_enum=pci enum
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_syslinux_conf=extlinux/extlinux.conf
boot_targets=mmc1 mmc0 usb0 scsi0 pxe dhcp 
bootcmd=run distro_bootcmd
bootcmd_dhcp=devtype=dhcp; run boot_net_usb_start; run boot_pci_enum; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;setenv efi_fdtfile ${fdtfile}; setenv efi_old_vci ${bootp_vci};setenv efi_old_arch ${bootp_arch};setenv bootp_vci PXEClient:Arch:00011:UNDI:003000;setenv bootp_arch 0xb;if dhcp ${kernel_addr_r}; then tftpboot ${fdt_addr_r} dtb/${efi_fdtfile};if fdt addr -q ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r}; else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi;fi;setenv bootp_vci ${efi_old_vci};setenv bootp_arch ${efi_old_arch};setenv efi_fdtfile;setenv efi_old_arch;setenv efi_old_vci;
bootcmd_mmc0=devnum=0; run mmc_boot
bootcmd_mmc1=devnum=1; run mmc_boot
bootcmd_pxe=run boot_net_usb_start; run boot_pci_enum; dhcp; if pxe get; then pxe boot; fi
bootcmd_scsi0=devnum=0; run scsi_boot
bootcmd_usb0=devnum=0; run usb_boot
bootdelay=0
cpu=armv8
cpuid#=5456433235302e303000000000198408
distro_bootcmd=scsi_need_init=; for target in ${boot_targets}; do run bootcmd_${target}; done
efi_dtb_prefixes=/ /dtb/ /dtb/current/
eth1addr=64:62:66:d0:0a:2b
ethaddr=64:62:66:d0:0a:2a
fdt_addr_r=0x01f00000
fdtcontroladdr=f5ee3ce0
fdtfile=rockchip/rk3399-kobol-helios64.dtb
fdtoverlay_addr_r=0x02000000
kernel_addr_r=0x02080000
kernel_comp_addr_r=0x08000000
kernel_comp_size=0x2000000
load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile}
loadaddr=0x800800
mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi
partitions=uuid_disk=${uuid_gpt_disk};name=loader1,start=32K,size=4000K,uuid=${uuid_gpt_loader1};name=loader2,start=8MB,size=4MB,uuid=${uuid_gpt_loader2};name=trust,size=4M,uuid=${uuid_gpt_atf};name=boot,size=112M,bootable,uuid=${uuid_gpt_boot};name=rootfs,size=-,uuid=B921B045-1DF0-41C3-AF44-4C6F280D3FAE;
pxefile_addr_r=0x00600000
ramdisk_addr_r=0x06000000
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev_for_efi;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done; setenv devplist
scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;run boot_efi_bootmgr;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootaa64.efi; then echo Found EFI removable media binary efi/boot/bootaa64.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; setenv efi_fdtfile
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_conf}; then echo Found ${prefix}${boot_syslinux_conf}; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scan_sf_for_scripts=${devtype} read ${scriptaddr} ${script_offset_f} ${script_size_f}; source ${scriptaddr}; echo SCRIPT FAILED: continuing...
script_offset_f=0xffe000
script_size_f=0x2000
scriptaddr=0x00500000
scsi_boot=run boot_pci_enum; run scsi_init; if scsi dev ${devnum}; then devtype=scsi; run scan_dev_for_boot_part; fi
scsi_init=if ${scsi_need_init}; then scsi_need_init=false; scsi scan; fi
serial#=000100001174
sf_boot=if sf probe ${busnum}; then devtype=sf; run scan_sf_for_scripts; fi
soc=rk3399
stderr=serial
stdin=serial
stdout=serial
usb_boot=usb start; if usb dev ${devnum}; then devtype=usb; run scan_dev_for_boot_part; fi
vendor=kobol
ver=U-Boot 2022.07-armbian-2022.07-Se092-Pa6d7-H8c72-Vbe65-Bda0a-R448a (Jul 22 2024 - 17:36:21 +0000)

Environment size: 4955/32764 bytes
=> net list
dw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio buseth0 : ethernet@fe300000 64:62:66:d0:0a:2a 
=> dhcp
dw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busNo ethernet found.
dw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio bus=>

The 2.5Gbit NIC is connected to the USB bus. Yet it is not shown after an 'usb start ; usb tree'. Nor is any usb device I connect. Maybe that is related to the serial port, which is connected to an FTDI chip, which is connected to the USB-C port, in device mode. Maybe for this reason the whole bus is disabled. Wiki.

Mijzelf,

> I'm trying to load files over tftp to my Kobol
> Helios64. This box has 2 ethernet ports, one
> 2.5Gbit, and one 1Gbit. When I give any network
> related command, it gives a repeated
> 'dw_dm_mdio_init: mdio node is missing,
> registering legacy mdio busdw_dm_mdio_init'.

Do

mii info
mdio list

> In Linux that MAC address is the address of the
> 1Gbit port.

> U-Boot
> 2022.07-armbian-2022.07-Se092-Pa6d7-H8c72-Vbe65-Bda0a-R448a
> (Jul 22 2024 - 17:36:21 +0000)
>
> SoC: Rockchip rk3399

This is a recent u-boot. I would expect the 1Gbit port to work. Unfortunately, it's not in mainline u-boot yet.

"mdio node is missing" is a warning when the DTB was parsed and the driver does not find its definition in the device tree blob. The driver in use does not consider it's an error. "registering legacy mdio" seems to correspond to other mdio definition in rk3399-base.dtsi.

> The 2.5Gbit NIC is connected to the USB bus. Yet it is not shown after an 'usb start ; usb tree'. Nor is any usb device I connect. Maybe that is related to the serial port,
> which is connected to an FTDI chip, which is connected to the USB-C port, in device mode. Maybe for this reason the whole bus is disabled. Wiki.

It's a strange design. It's multiplexing to TypeC0 (OTG) and TypeC1(Host). So looks like you're right. You're using the USB 3.0 bus in OTG mode to connect serial console with a USB-C cable to other box? then the bus is not in Host mode (needed for USB LAN). To verify, you can try to attach a USB thumb drive to the front panel, it will not be recognized when you do "usb start".

They also say

Quote

In case you are using the USB-C for one of the others functionalities but you still need to access SoC serial console for debug purpose, UART2 Debug is also exposed on P14 header.

======

1. I did not see the envs ipaddr and servrip in your listing

setenv ipaddr <this box IP address>
setenv serverip <tftp server IP address>

After you have set ipaddr, do

ping <your router IP address>

2. I guess to see the USB LAN working, you could use your own converter and connect to those pins on P14.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

=> mii info
NULL device name!
No such device: <NULL>
NULL device name!
No such device: <NULL>
NULL device name!
No such device: <NULL>
(repeated 32 times in total)
=> mdio list
No MDIO bus found
=> setenv ipaddr 192.168.1.50
=> setenv serverip 192.168.1.254
=> ping 192.168.1.254
dw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busNo ethernet found.
dw_dm_mdio_init: mdio node is missing, registering legacy mdio busdw_dm_mdio_init: mdio node is missing, registering legacy mdio busping failed; host 192.168.1.254 is not alive
=>

> Unfortunately, it's not in mainline u-boot yet.
You mean this u-boot, or any rk3399 u-boot?

> You're using the USB 3.0 bus in OTG mode to connect serial console with a USB-C cable to other box? then the bus is not in Host mode (needed for USB LAN). To verify, you can try to attach a USB thumb drive to the front panel, it will not be recognized when you do "usb start".

Yes, that is the case, cablewise. And indeed, with an usb thumb inserted:

=> usb reset
resetting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe900000: probe failed, error -22
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
=> usb tree
USB device tree:
  1  Hub (480 Mb/s, 0mA)
     u-boot EHCI Host Controller 
   
=> usb start
=> usb tree
USB device tree:
  1  Hub (480 Mb/s, 0mA)
     u-boot EHCI Host Controller 
   
=>

But somehow the host and otg mode can be combined. When I boot to linux, I can login over serial, and both the 2.5Bbit NIC and the usb shumb show up in lsusb:

helios64 login: root
Password: 
 _   _      _ _            __   _  _   
| | | | ___| (_) ___  ___ / /_ | || |  
| |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ 
|  _  |  __/ | | (_) \__ \ (_) |__   _|
|_| |_|\___|_|_|\___/|___/\___/   |_|  
                                       
Welcome to Armbian 24.8.1 Bookworm with Linux 6.12.54-current-rockchip64

System load:   10%              Up time:       2 min
Memory usage:  4% of 3.76G      IP:            192.168.1.50
CPU temp:      41°C             Usage of /:    10% of 15G    

[ 0 security updates available, 1 updates total: apt upgrade ]
Last check: 2025-10-22 19:57

Last login: Wed Oct 22 19:56:44 CEST 2025 from fd4a:34e9:33f8:20:e84:8c61:89b8:c101 on pts/0
root@helios64:~# lsusb
Bus 002 Device 003: ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN
Bus 002 Device 002: ID 2109:0815 VIA Labs, Inc. USB3.0 Hub             
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 125f:c96a A-DATA Technology Co., Ltd. C906 Flash Drive
Bus 001 Device 002: ID 2109:2815 VIA Labs, Inc. USB2.0 Hub             
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It seems to me this u-boot isn't matured out. There were lots of troubles when the Helios64 was launched (mainly Covid 19, and supply chain problems, AFAIK), and Kobol went out of business in 2021, before the software was 'ready'.

The only supported way to install an OS is using an microSD cart.

> > Unfortunately, it's not in mainline u-boot yet.
>
> You mean this u-boot, or any rk3399 u-boot?

This u-boot specifically. There are quite a few other rk3399 u-boots in mainline, but I don't see the rk3399-kobol-helios64.dts being used anywhere.

> But somehow the host and otg mode can be combined.
> When I boot to linux, I can login over serial, and
> both the 2.5Bbit NIC and the usb shumb show up in
> lsusb:

Cool!

> It seems to me this u-boot isn't matured out.

Agree.

> There were lots of troubles when the Helios64 was
> launched (mainly Covid 19, and supply chain
> problems, AFAIK), and Kobol went out of business
> in 2021, before the software was 'ready'.
>
> The only supported way to install an OS is using
> an microSD cart.

Quote

Welcome to Armbian 24.8.1 Bookworm with Linux 6.12.54-current-rockchip64

I guess you have recently updated the kernel and rootfs?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

> I guess you have recently updated the kernel and rootfs?

Yes. There is a clean install of Armbian on emmc, which is up-to-date. I want to try to install Debian 13 on an SSD, using the netinstaller. But I probably will have to provide the files on μSD.