AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
U boot source11/21/2022 ![]() random: get_random_u64 called from cache_random_seq_create 0x7c/0x150 with crng_init=0 mem auto-init: stack:off, heap alloc:off, heap free:off Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) Kernel command line: root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 Built 1 zonelists, mobility grouping on. CPU features: detected: GIC system register CPU interface CPU features: detected: ARM erratum 845719 psci: Using standard PSCI v0.2 function IDs psci: probing for conduit method from DT. 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 androidI 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 Now radxa uboot does not load boot partitions with boot.scr and does not found files on usb ![]()
0 Comments
Read More
Leave a Reply. |