Thibault DESAULES Posted April 25, 2023 Share Posted April 25, 2023 Hello Armbian community I just acquired a Raxda Rock 3A with a Raxda Wireless module A8 (RTL8852BE) card. The Ubuntu distribution from Raxda seems to work pretty well, but it's not very recent, which is why I wanted to try Armbian! The current version (Armbian 23.02 Jammy Kernel 6.1.y, Size: 579Mb, Release date: Feb 27, 2023) seems to work, but I have two questions: 1) No wifi, the card is not detected (probably a driver issue, it works with the official OS), if there are members who have solved this? 2) I haven't seen much information on setting up a boot from an nvme storage, have you tried this? Have a great day! 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted April 25, 2023 Share Posted April 25, 2023 6 minutes ago, Thibault DESAULES said: but it's not very recent https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one 7 minutes ago, Thibault DESAULES said: seems to work pretty well In some cases (Rock 5, Bananapi 5, ...) we are providing images with pretty well working but outdated kernel which is responsible for interacting with hardware. Difference between legacy and modern mainline is extreme. 1) devices that are plugged to the board were never officially supported. Porting drivers to the mainline for all Linux community (by a few people) is done in best effort manner. 2) it always works this way https://docs.armbian.com/User-Guide_Getting-Started/#how-to-install-to-emmc-nand-sata-nvme-usb unless it doesn't / its broken. If its broken it can be broken for all boards. SPI boot method is not always working / supported. My 2c 0 Quote Link to comment Share on other sites More sharing options...
Thibault DESAULES Posted April 25, 2023 Author Share Posted April 25, 2023 yeah, From what I see there (https://docs.armbian.com/User-Guide_Getting-Started/#how-to-install-to-emmc-nand-sata-nvme-usb) didn't find relevant options from the armbian-config cli. Need to look more deeply into this ! 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted April 25, 2023 Share Posted April 25, 2023 If you will be digging in: - u-boot package contains information how to flash boot loader to eMMC/SD/SPI - this is install script that is called from armbian-config, also works as standalone armbian-install 0 Quote Link to comment Share on other sites More sharing options...
Thibault DESAULES Posted April 26, 2023 Author Share Posted April 26, 2023 Thank you, I will look at the links. I need to learn about the u-boot part (I don't know how it works) with regards to Wifi. I saw that an M2 card based on "Intel AX210NGW" was compatible. I might have one in my stuff, I need to look for it to test it. 0 Quote Link to comment Share on other sites More sharing options...
Thibault DESAULES Posted April 26, 2023 Author Share Posted April 26, 2023 Well, probably did something wrong, the boot from the MTD Flash doesn't seem to work. I try the following (for info, still investigating) the filesystem : root@rock-3a:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 199M 3.5M 195M 2% /run /dev/mmcblk0p2 15G 1.9G 13G 13% / tmpfs 991M 0 991M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 991M 0 991M 0% /tmp /dev/mmcblk0p1 256M 118M 139M 46% /boot /dev/zram1 47M 1.5M 42M 4% /var/log tmpfs 199M 0 199M 0% /run/user/0 I create a new partition on the nvme drive : root@rock-3a:~# fdisk /dev/nvme0n1 Welcome to fdisk (util-linux 2.37.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors Disk model: NE-128 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 3841CFFF-6149-C148-B421-99DF0D4B585B Command (m for help): n Partition number (1-128, default 1): First sector (34-250069646, default 2048): Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-250069646, default 250069646): Created a new partition 1 of type 'Linux filesystem' and of size 119.2 GiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o: Y The signature will be removed by a write command. Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. storage info : root@rock-3a:~# fdisk -l Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors Disk model: NE-128 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 3841CFFF-6149-C148-B421-99DF0D4B585B Device Start End Sectors Size Type /dev/nvme0n1p1 2048 250069646 250067599 119.2G Linux filesystem Disk /dev/mmcblk0: 14.84 GiB, 15931539456 bytes, 31116288 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 3841CFFF-6149-C148-B421-99DF0D4B585B Device Start End Sectors Size Type /dev/mmcblk0p1 32768 557055 524288 256M Linux extended boot /dev/mmcblk0p2 557056 30801920 30244865 14.4G Linux filesystem Disk /dev/mtdblock0: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: CE22CF47-BE9F-48CD-8FF4-CBA055568687 Device Start End Sectors Size Type /dev/mtdblock0p1 64 7167 7104 3.5M Linux filesystem /dev/mtdblock0p2 7168 7679 512 256K Linux filesystem /dev/mtdblock0p3 7680 8063 384 192K Linux filesystem /dev/mtdblock0p4 8064 8127 64 32K Linux filesystem /dev/mtdblock0p5 8128 8191 64 32K Linux filesystem /dev/mtdblock0p6 8192 16383 8192 4M Linux filesystem /dev/mtdblock0p7 16384 32734 16351 8M Linux filesystem Disk /dev/zram0: 990.64 MiB, 1038761984 bytes, 253604 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes and screenshot from armbian-config A small reboot after, the board still doesn't start from the nvme drive (it work from the sdcard... strange, I probably forgot something) 0 Quote Link to comment Share on other sites More sharing options...
SteeMan Posted April 26, 2023 Share Posted April 26, 2023 On 4/25/2023 at 12:04 PM, Thibault DESAULES said: The current version (Armbian 23.02 Jammy Kernel 6.1.y, Size: 579Mb, Release date: Feb 27, 2023) There is a bug in armbian-install in this version that will likely cause your scenario to fail. You can manually fix/verify the issue by looking at the armbianEnv.txt file installed on the nvme drive and look for the uuid of the drive. It should be prefixed with UUID= (compare to the armbianEnv.txt on your sd card). Or you can use a nightly image which will already contain the fix to armbian-install and retry. 0 Quote Link to comment Share on other sites More sharing options...
Thibault DESAULES Posted April 26, 2023 Author Share Posted April 26, 2023 Yeah ! I mean I see that the /etc/fstab look weird... I didn't touch a fstab since a while so I just correct the UUID of the partition to be mapped to the correct one to target the /boot from my sdcard and the root on the nvme drive just to confirm it was working. But I can't figured out for the moment why a pure nvme boot from the MTB flash doesn't work. Probably something that I don't understand yet with the ROCK 3A. I didn't check yet the /boot/armbianEnv.txt (computer offline right now, will take a look tomorrow, never open the file) 0 Quote Link to comment Share on other sites More sharing options...
Thibault DESAULES Posted April 27, 2023 Author Share Posted April 27, 2023 So I made some more test regarding the armbianEnv.txt first thing is if I boot with a fresh SDCard and the nvme drive (flash with the same image) I notice that the /boot was mounted from the nvme drive. I suppose the SPI flash has the bootloader installed : root@rock-3a:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 199M 8.5M 190M 5% /run /dev/mmcblk0p2 15G 1.9G 13G 14% / tmpfs 991M 0 991M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 991M 0 991M 0% /tmp /dev/nvme0n1p1 256M 118M 139M 46% /boot /dev/zram1 47M 1.4M 42M 4% /var/log tmpfs 199M 0 199M 0% /run/user/0 and the armbianEnv.txt look like this root@rock-3a:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false overlay_prefix=rk35xx fdtfile=rockchip/rk3568-rock-3a.dtb rootdev=UUID=6ce28e93-ed91-46ae-9035-701bfe34a5fd rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u nvme drive was flashed with the same image so the UUID the same : root@rock-3a:~# blkid /dev/nvme0n1p1: SEC_TYPE="msdos" LABEL_FATBOOT="armbi_boot" LABEL="armbi_boot" UUID="5F4E-9DB1" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="bootfs" PARTUUID="651eafa5-90c1-b34a-88be-6db5e1c4611c" /dev/nvme0n1p2: LABEL="armbi_root" UUID="6ce28e93-ed91-46ae-9035-701bfe34a5fd" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="eb6a0463-83fa-254b-a7bd-e703cd9c5e2a" /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="armbi_boot" LABEL="armbi_boot" UUID ="5F4E-9DB1" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="bootfs" PARTUUID="651eafa5-90c1-b34a-88be-6db5e1c4611c" /dev/mmcblk0p2: LABEL="armbi_root" UUID="6ce28e93-ed91-46ae-9035-701bfe34a5fd" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9e4b479e-7ebe-e64e-b580-511346abdf58" /dev/zram0: UUID="8b7f63d9-3035-4f2e-a856-07b574fb68d8" TYPE="swap" /dev/zram1: LABEL="log2ram" UUID="8a8c18d4-a1f8-4747-a5e0-fb5e299d8ae0" BLOCK_SIZE="4096" TYPE="ext4" /dev/mtdblock0: PTUUID="ce22cf47-be9f-48cd-8ff4-cba055568687" PTTYPE="gpt" root@rock-3a:~# lsblk -fe7 NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS mtdblock0 mmcblk0 ├─mmcblk0p1 vfat FAT16 armbi_boot 5F4E-9DB1 └─mmcblk0p2 ext4 1.0 armbi_root 6ce28e93-ed91-46ae-9035-701bfe34a5fd 12.1G 13% /var/log.hdd / zram0 [SWAP] zram1 41.7M 3% /var/log zram2 nvme0n1 ├─nvme0n1p1 vfat FAT16 armbi_boot 5F4E-9DB1 138.2M 46% /boot └─nvme0n1p2 ext4 1.0 armbi_root 6ce28e93-ed91-46ae-9035-701bfe34a5fd so for testing I just random the uuid root@rock-3a:~# tune2fs -U random /dev/nvme0n1p2 tune2fs 1.46.5 (30-Dec-2021) root@rock-3a:~# blkid /dev/nvme0n1p1: SEC_TYPE="msdos" LABEL_FATBOOT="armbi_boot" LABEL="armbi_boot" UUID="5F4E-9DB1" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="bootfs" PARTUUID="651eafa5-90c1-b34a-88be-6db5e1c4611c" /dev/nvme0n1p2: LABEL="armbi_root" UUID="22edd9bc-4fdb-4f15-9080-c8acf5084fc1" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="eb6a0463-83fa-254b-a7bd-e703cd9c5e2a" /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="armbi_boot" LABEL="armbi_boot" UUID="5F4E-9DB1" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="bootfs" PARTUUID="651eafa5-90c1-b34a-88be-6db5e1c4611c" /dev/mmcblk0p2: LABEL="armbi_root" UUID="6ce28e93-ed91-46ae-9035-701bfe34a5fd" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9e4b479e-7ebe-e64e-b580-511346abdf58" /dev/zram0: UUID="8a6ccc03-1293-45e2-bd5a-b367fb0b53d0" TYPE="swap" /dev/zram1: LABEL="log2ram" UUID="2c5f8064-5636-4c8f-9548-e2c801d94754" BLOCK_SIZE="4096" TYPE="ext4" /dev/mtdblock0: PTUUID="ce22cf47-be9f-48cd-8ff4-cba055568687" PTTYPE="gpt" and change the uuid from the armbianEnv.txt and the fstab root@rock-3a:~# cat /boot/armbian armbianEnv.txt armbian_first_run.txt.template root@rock-3a:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false overlay_prefix=rk35xx fdtfile=rockchip/rk3568-rock-3a.dtb rootdev=UUID=22edd9bc-4fdb-4f15-9080-c8acf5084fc1 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@rock-3a:~# cat /etc/fstab UUID=6ce28e93-ed91-46ae-9035-701bfe34a5fd / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1 UUID=5F4E-9DB1 /boot vfat defaults 0 2 tmpfs /tmp tmpfs defaults,nosuid 0 0 filesystem look fine (/boot and root on nvme) root@rock-3a:~# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 199M 8.5M 190M 5% /run /dev/nvme0n1p2 116G 1.9G 113G 2% / tmpfs 991M 0 991M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 991M 0 991M 0% /tmp /dev/nvme0n1p1 256M 118M 139M 46% /boot /dev/zram1 47M 1.1M 43M 3% /var/log tmpfs 199M 0 199M 0% /run/user/0 But the board still doesn't boot without the sdcard, so there is something that I'm still missing 🤨 probably related to the u-boot and the SPI flash stuff (I'm no used to wotk with those) 0 Quote Link to comment Share on other sites More sharing options...
Thibault DESAULES Posted May 3, 2023 Author Share Posted May 3, 2023 Hi, Just trying to get more information from the u-boot and it seems that it can't find any device to boot from. Look like it doesn't try to boot from nvme : DDR Version V1.10 20210810 In ddrconfig:0 LPDDR4X, 324MHz BW=32 Col=10 Bk=8 CS0 Row=16 CS=1 Die BW=16 Size=2048MB tdqss: cs0 dqs0: -24ps, dqs1: -120ps, dqs2: -96ps, dqs3: -217ps, change to: 324MHz PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x64 change to: 528MHz PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x58 change to: 780MHz PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x58 change to: 1560MHz(final freq) PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:22% dram drv:40,odt:80 vref_ca:00000071 clk skew:0x3f cs 0: the read training result: DQS0:0x32, DQS1:0x30, DQS2:0x38, DQS3:0x2f, min : 0xf 0x10 0x12 0x10 0x2 0x4 0x8 0x4 , 0xa 0x8 0x4 0x1 0x9 0x7 0x c 0x4 , 0x16 0x15 0xe 0xd 0x4 0x2 0x6 0x6 , 0xc 0x8 0x6 0x1 0x10 0xe 0x c 0xb , mid :0x29 0x2a 0x2c 0x29 0x1b 0x1d 0x21 0x1d ,0x23 0x22 0x1d 0x1c 0x25 0x21 0x2 4 0x1e , 0x30 0x2f 0x29 0x29 0x20 0x1d 0x1f 0x22 ,0x25 0x22 0x1f 0x1b 0x29 0x27 0x2 5 0x25 , max :0x43 0x45 0x47 0x42 0x35 0x37 0x3b 0x37 ,0x3d 0x3d 0x36 0x37 0x42 0x3c 0x3 d 0x39 , 0x4a 0x4a 0x45 0x45 0x3d 0x39 0x39 0x3e ,0x3f 0x3d 0x39 0x35 0x42 0x41 0x3 f 0x40 , range:0x34 0x35 0x35 0x32 0x33 0x33 0x33 0x33 ,0x33 0x35 0x32 0x36 0x39 0x35 0x3 1 0x35 , 0x34 0x35 0x37 0x38 0x39 0x37 0x33 0x38 ,0x33 0x35 0x33 0x34 0x32 0x33 0x3 3 0x35 , the write training result: DQS0:0x3b, DQS1:0x28, DQS2:0x2c, DQS3:0x14, min :0x76 0x79 0x7a 0x77 0x69 0x69 0x6e 0x70 0x6b ,0x5e 0x5c 0x56 0x56 0x60 0x5 9 0x5d 0x5e 0x58 , 0x6b 0x6b 0x65 0x66 0x5c 0x55 0x58 0x5e 0x5c ,0x4f 0x4d 0x4a 0x48 0x53 0x5 0 0x4f 0x53 0x48 , mid :0x90 0x93 0x93 0x92 0x81 0x84 0x87 0x88 0x84 ,0x79 0x77 0x70 0x70 0x7a 0x7 4 0x78 0x77 0x72 , 0x86 0x86 0x7e 0x7f 0x76 0x71 0x73 0x78 0x77 ,0x6a 0x69 0x62 0x61 0x6f 0x6 d 0x6a 0x6f 0x64 , max :0xab 0xae 0xad 0xae 0x9a 0x9f 0xa1 0xa1 0x9e ,0x95 0x93 0x8a 0x8b 0x95 0x9 0 0x93 0x91 0x8d , 0xa2 0xa1 0x97 0x99 0x91 0x8e 0x8f 0x93 0x93 ,0x86 0x85 0x7b 0x7a 0x8b 0x8 a 0x85 0x8b 0x80 , range:0x35 0x35 0x33 0x37 0x31 0x36 0x33 0x31 0x33 ,0x37 0x37 0x34 0x35 0x35 0x3 7 0x36 0x33 0x35 , 0x37 0x36 0x32 0x33 0x35 0x39 0x37 0x35 0x37 ,0x37 0x38 0x31 0x32 0x38 0x3 a 0x36 0x38 0x38 , CA Training result: cs:0 min :0x5a 0x4e 0x4c 0x41 0x4b 0x3d 0x51 ,0x58 0x47 0x4e 0x40 0x4e 0x3c 0x5 1 , cs:0 mid :0x93 0x91 0x86 0x83 0x85 0x80 0x79 ,0x90 0x8a 0x84 0x82 0x84 0x81 0x7 8 , cs:0 max :0xcc 0xd5 0xc0 0xc6 0xbf 0xc4 0xa1 ,0xc8 0xce 0xbb 0xc4 0xbb 0xc6 0x9 f , cs:0 range:0x72 0x87 0x74 0x85 0x74 0x87 0x50 ,0x70 0x87 0x6d 0x84 0x6d 0x8a 0x4 e , out U-Boot SPL board init U-Boot SPL 2017.09-armbian (Feb 17 2023 - 22:34:20) unrecognized JEDEC id bytes: ef, 80, 18 Trying to boot from MMC2 MMC error: The cmd index is 1, ret is -110 Card did not respond to voltage select! mmc_init: -95, time 10 spl: mmc init failed with error: -95 Trying to boot from MMC1 MMC error: The cmd index is 0, ret is -110 mmc_init: -110, time 4 spl: mmc init failed with error: -110 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### # Reset the board to bootrom # With an sdcard + nvme drive, it seems to boot (probably from the sdcard I suppose) and the nvme drive is listed after... Any idea ? DDR Version V1.10 20210810 In ddrconfig:0 LPDDR4X, 324MHz BW=32 Col=10 Bk=8 CS0 Row=16 CS=1 Die BW=16 Size=2048MB tdqss: cs0 dqs0: -24ps, dqs1: -96ps, dqs2: -96ps, dqs3: -192ps, change to: 324MHz PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x64 change to: 528MHz PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x58 change to: 780MHz PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x58 change to: 1560MHz(final freq) PHY drv:clk:36,ca:36,DQ:29,odt:60 vrefinner:16%, vrefout:22% dram drv:40,odt:80 vref_ca:00000071 clk skew:0x3a cs 0: the read training result: DQS0:0x31, DQS1:0x30, DQS2:0x37, DQS3:0x2f, min : 0xe 0xf 0x10 0xf 0x0 0x4 0x7 0x4 , 0xa 0x8 0x4 0x2 0xa 0x7 0x c 0x4 , 0x16 0x14 0xe 0xc 0x2 0x0 0x5 0x6 , 0xc 0x8 0x6 0x1 0xf 0xe 0x c 0xb , mid :0x27 0x29 0x2a 0x28 0x1a 0x1c 0x20 0x1c ,0x23 0x22 0x1d 0x1c 0x26 0x21 0x2 4 0x1e , 0x2f 0x2f 0x29 0x28 0x1f 0x1b 0x1e 0x21 ,0x25 0x22 0x1f 0x1b 0x28 0x27 0x2 5 0x25 , max :0x41 0x43 0x44 0x41 0x34 0x35 0x39 0x35 ,0x3d 0x3d 0x36 0x36 0x42 0x3c 0x3 d 0x39 , 0x49 0x4a 0x44 0x44 0x3c 0x37 0x38 0x3d ,0x3f 0x3d 0x39 0x35 0x42 0x40 0x3 f 0x40 , range:0x33 0x34 0x34 0x32 0x34 0x31 0x32 0x31 ,0x33 0x35 0x32 0x34 0x38 0x35 0x3 1 0x35 , 0x33 0x36 0x36 0x38 0x3a 0x37 0x33 0x37 ,0x33 0x35 0x33 0x34 0x33 0x32 0x3 3 0x35 , the write training result: DQS0:0x36, DQS1:0x27, DQS2:0x27, DQS3:0x14, min :0x72 0x75 0x75 0x73 0x65 0x64 0x6a 0x6b 0x67 ,0x5e 0x5c 0x55 0x56 0x5e 0x5 9 0x5d 0x5e 0x58 , 0x67 0x66 0x5f 0x60 0x55 0x50 0x53 0x59 0x58 ,0x4f 0x4d 0x4b 0x48 0x53 0x5 1 0x50 0x53 0x48 , mid :0x8c 0x8f 0x8f 0x8e 0x7d 0x7f 0x83 0x83 0x80 ,0x78 0x76 0x6f 0x6f 0x79 0x7 4 0x77 0x76 0x71 , 0x81 0x80 0x78 0x79 0x70 0x6c 0x6e 0x73 0x72 ,0x6a 0x69 0x64 0x61 0x6f 0x6 e 0x6a 0x6f 0x64 , max :0xa7 0xaa 0xa9 0xa9 0x96 0x9b 0x9d 0x9b 0x9a ,0x93 0x91 0x89 0x89 0x95 0x8 f 0x91 0x8f 0x8b , 0x9b 0x9b 0x92 0x93 0x8b 0x88 0x89 0x8d 0x8d ,0x86 0x85 0x7d 0x7a 0x8b 0x8 b 0x85 0x8b 0x80 , range:0x35 0x35 0x34 0x36 0x31 0x37 0x33 0x30 0x33 ,0x35 0x35 0x34 0x33 0x37 0x3 6 0x34 0x31 0x33 , 0x34 0x35 0x33 0x33 0x36 0x38 0x36 0x34 0x35 ,0x37 0x38 0x32 0x32 0x38 0x3 a 0x35 0x38 0x38 , CA Training result: cs:0 min :0x59 0x4e 0x4c 0x41 0x4b 0x3c 0x50 ,0x57 0x47 0x4e 0x3f 0x4e 0x3b 0x5 1 , cs:0 mid :0x92 0x91 0x86 0x83 0x84 0x7f 0x78 ,0x90 0x8a 0x84 0x81 0x84 0x80 0x7 7 , cs:0 max :0xcb 0xd4 0xc0 0xc5 0xbe 0xc3 0xa1 ,0xc9 0xce 0xba 0xc4 0xba 0xc6 0x9 e , cs:0 range:0x72 0x86 0x74 0x84 0x73 0x87 0x51 ,0x72 0x87 0x6c 0x85 0x6c 0x8b 0x4 d , out U-Boot SPL board init U-Boot SPL 2017.09-armbian (Feb 17 2023 - 22:34:20) unrecognized JEDEC id bytes: ef, 80, 18 Trying to boot from MMC2 ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(2f01bd8955...) + OK ## Checking uboot 0x00a00000 ... sha256(ab53d4f780...) + OK ## Checking fdt 0x00b2ecd8 ... sha256(4bdde2de3f...) + OK ## Checking atf-2 0xfdcc9000 ... sha256(f1fecab971...) + OK ## Checking atf-3 0xfdcd0000 ... sha256(d7aa45eb18...) + OK Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000) Total: 747.9 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-152-g4e725b15f:cl NOTICE: BL31: Built : 10:51:13, Jul 15 2021 INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: pmu v1 is valid INFO: dfs DDR fsp_param[0].freq_mhz= 1560MHz INFO: dfs DDR fsp_param[1].freq_mhz= 324MHz INFO: dfs DDR fsp_param[2].freq_mhz= 528MHz INFO: dfs DDR fsp_param[3].freq_mhz= 780MHz INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE init ialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0xa00000 INFO: SPSR = 0x3c9 U-Boot 2017.09-armbian (Feb 17 2023 - 22:34:20 +0000) Model: Radxa ROCK3 Model A PreSerial: 2, raw, 0xfe660000 DRAM: 2 GiB Sysmem: init Relocation Offset: 7d349000 Relocation fdt: 7b9f69a0 - 7b9fecc8 CR: M/C/I Using default environment no mmc device at slot 1 dwmmc@fe2b0000: 1 (SD), dwmmc@fe2c0000: 2, sdhci@fe310000: 0 Bootdev(atags): mmc 1 MMC1: Legacy, 52Mhz PartType: EFI No misc partition boot mode: None FIT: No boot partition No resource partition No resource partition Failed to load DTB, ret=-19 Failed to get kernel dtb, ret=-19 I2c0 speed: 100000Hz vsel-gpios- not found! Error: -2 vdd_cpu init 900000 uV PMIC: RK8090 (on=0x40, off=0x00) vdd_logic init 900000 uV vdd_gpu init 900000 uV vdd_npu init 900000 uV io-domain: OK Model: Radxa ROCK3 Model A rockchip_set_serialno: could not find efuse/otp device CLK: (sync kernel. arm: enter 816000 KHz, init 816000 KHz, kernel 0N/A) apll 816000 KHz dpll 780000 KHz gpll 1188000 KHz cpll 1000000 KHz npll 1200000 KHz vpll 24000 KHz hpll 24000 KHz ppll 200000 KHz armclk 816000 KHz aclk_bus 150000 KHz pclk_bus 100000 KHz aclk_top_high 300000 KHz aclk_top_low 200000 KHz hclk_top 150000 KHz pclk_top 100000 KHz aclk_perimid 300000 KHz hclk_perimid 150000 KHz pclk_pmu 100000 KHz No misc partition Net: eth1: ethernet@fe010000 Hit key to stop autoboot('CTRL+C'): 0 Device 0: Vendor: 0x1e4b Rev: SN07202 Prod: 9120209F03621 Type: Hard Disk Capacity: 122104.3 MB = 119.2 GB (250069680 x 512) ... is now current device Scanning nvme 0:1... Found U-Boot script /boot.scr reading /boot.scr 3252 bytes read in 0 ms ## Executing script at 00c00000 Boot script loaded from nvme 0 reading /armbianEnv.txt 200 bytes read in 0 ms reading /uInitrd 23236178 bytes read in 23 ms (963.5 MiB/s) reading /Image 31273472 bytes read in 29 ms (1 GiB/s) reading /dtb/rockchip/rk3568-rock-3a.dtb 113692 bytes read in 1 ms (108.4 MiB/s) ** Unable to read file /dtb/rockchip/overlay/rk35xx-fixup.scr ** Unknown command 'kaslrseed' - try 'help' Fdt Ramdisk skip relocation No misc partition ## Loading init Ramdisk from Legacy Image at 0a200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 23236114 Bytes = 22.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 0x0a100000 Booting using the fdt blob at 0x0a100000 reserving fdt memory region: addr=a100000 size=82000 Using Device Tree in place at 000000000a100000, end 000000000a184fff can't found rockchip,drm-logo, use rockchip,fb-logo WARNING: could not set reg FDT_ERR_BADOFFSET. failed to reserve fb-loader-logo memory Adding bank: 0x00200000 - 0x80000000 (size: 0x7fe00000) Total: 1891.677 ms Starting kernel ... 0 Quote Link to comment Share on other sites More sharing options...
Thibault DESAULES Posted May 7, 2023 Author Share Posted May 7, 2023 Not directly related but I test an Intel AX210 NGW that is working fine but not directly detected I install linux-firmware to get it working. https://fr.aliexpress.com/item/1005002129145403.html root@rock-3a:~# lspci | grep Network 0000:01:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.