Hello,
On Fri, Feb 06, 2026 at 11:25:26AM +0100, Mark Kettenis wrote:
</snip>
>
> Do you now see all the output at 11520? With that I mean the DDR
> training output, U-Boot, the OpenBSD bootloader at least?
>
no, there are first few lines garbled at the boot. This is
how serial console output reads before boot reaches OpenBSD
boot prompt.
--------8<---------------8<-----------------8<--------
lifty# cu -l usb0.2.00001.0 -s 115200
Connected to /dev/cuaU0 (speed 115200)
W__7_4lk__s__c_c_e__6___w2_.____{_k_____S8G__L___O_S_F__u_F#W_m>__}__,____,_Y__Y_,Y_k___*__q___W_,__9hyN_Y_______M__q__p___x__I_&____a__I_A_______Q___{q__6____Q___7_Y_V___'__eg_H_e_
U-Boot 2025.07 (Oct 10 2025 - 13:49:09 -0600)
Model: FriendlyElec NanoPC-T6
SoC: RK3588
DRAM: 8 GiB
PMIC: RK806 (on=0x40, off=0x00)
Core: 391 devices, 34 uclasses, devicetree: separate
MMC: mmc@fe2c0000: 1, mmc@fe2e0000: 0
Loading Environment from nowhere... OK
In: serial@feb50000
Out: serial@feb50000
Err: serial@feb50000
Model: FriendlyElec NanoPC-T6
SoC: RK3588
Net: No ethernet found.
Hit any key to stop autoboot: 0
Scanning for bootflows in all bootdevs
Seq Method State Uclass Part Name Filename
--- ----------- ------ -------- ---- ------------------------
----------------
Scanning global bootmeth 'efi_mgr':
0 efi_mgr ready (none) 0 <NULL>
** Booting bootflow '<NULL>' with efi_mgr
Booting: Label: mmc 1 Device path:
/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,0000000000000000)/SD(1)/SD(0)
disks: sd0* sd1
>> OpenBSD/arm64 BOOTAA64 1.22
boot>
--------8<---------------8<-----------------8<--------
I will reboot to Linux later today and retry with faster serial line
to obtain a readable output. Will do it later today.
thanks and
regards
sashan
