Linux version 5.5.1-rk3399-tv (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #trunk SMP PREEMPT Mon Feb 24 20:23: Booting Linux on physical CPU 0x0000000000 Loading Ramdisk to 71330000, end 71db9cef … OK Verifying Checksum … OK Flattened Device Tree blob at 08300000 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Reading /dtb/rockchip/rk3399-rock-pi-4.dtbĥ4559 bytes read in 3 ms (17.3 MiB/s) Loading init Ramdisk from Legacy Image at 0a200000 … Here is the output from the working run.ĭevice 0: RKPARM: Invalid parameter part table And the most amazing thing is that it is run using a script that is designed to work with SD \ USB. I tried to write the same image on a Samsung EVO970, the system does not start … I don’t understand why one model works and the other doesn’t. Took a simple NVME (Orico), recorded an image of Armbian and it … normally starts with NVMe. To raxda: Is it possible to make such uboot?
#U boot source android
I would really like if there are no boot flags on mmcblk0, then the android booted with mmcblk1. To change boot partition, I use ‘parted toogle N boot’ where N is partition number where the flag changes. Number Start End Size File system Name Flagsĥ 134MB 252MB 117MB fat16 xubuntu msftdataħ 789MB 1325MB 537MB fat16 slax boot, espĨ 1325MB 1862MB 537MB fat16 ARMB54 msftdataġ1 13,1GB 13,4GB 268MB fat16 bootmint boot, espġ2 13,4GB 13,5GB 117MB fat16 BootMain boot, espġ3 13,5GB 15,9GB 2409MB fat32 BAKU msftdata The rootfs partitions are located on nvme. Now I use mutiboot with changing boot flag on mmcblk0 partitions. 1 USB Device(s) foundĭevice 0: unknown Waiting for PHY auto negotiation to complete. USB5: Can't get the usbphy registobe failed, error -6 USB4: Can't get the usbphy register address This file has been truncated.Now radxa uboot does not load boot partitions with boot.scr and does not found files on usb Sun8i-r16-nintendo-nes-classic-edition.dtb \ u-boot_clockworkpi_cpi3.patch diff -git a/arch/arm/dts/Makefile b/arch/arm/dts/Makefile
#U boot source Patch
I’ve tested this patch against HEAD of the upstream u-boot master branch as well as 2019.07.
The rest of the AXP settings appear to match the defaults for all sun8i boards and are the same as those listed on the GameShell schematic.
The AXP_DLDO settings turn on power to the wifi chip, which is probably unnecessary as the Linux kernel does this later in the boot, but it seemed like a good idea to include it to avoid issues with MMC1 timeouts. I don’t think I’ve got the LCD mode quite right, as the display backlight just flashes on startup and using the bmp command to load an image appears to do nothing. The datasheet for the chip on my board says that it’s DDR3L-1600, but I have no idea what that translates to in terms of A33 DRAM clock settings. It’s probably possible to clock the RAM faster.
The DRAM clock is set to the first timing I got working. I couldn’t find a defconfig for u-boot on the gameshell, but was able to get it figured out based on the device tree and schematics.
0 kommentar(er)
