Hqnicolas Posted July 6, 2023 Author Posted July 6, 2023 4 hours ago, mvpwar said: can boot from mmc...no need usb for editing and include armbian kernel 6.2 on EMMC you will need to boot from usb 0 Quote
Hqnicolas Posted July 6, 2023 Author Posted July 6, 2023 18 hours ago, hotnikq said: It's about the v0.5 flash drive image that I have done... Flash This UpdateV4.img file on EMMC and v0.5 on USB stick on port 3.0 Please post the LOG from TTL 0 Quote
mvpwar Posted July 7, 2023 Posted July 7, 2023 (edited) 11 hours ago, hotnikq said: Flash This UpdateV4.img file on EMMC the v4 update.img and v5 update.img can not change the partition so the box would boot fail with the maskrom state, it need to be flashed the u-boot.img and MiniLoader.bin to specify the partition name, like Uboot and Loader 11 hours ago, hotnikq said: and v0.5 on USB stick on port 3.0 Please post the LOG from TTL I will try it later @hotnikq the reason is below, from RKDevTool_manual_v1.2_en.pdf RKDevTool_manual_v1.2_en.pdf Edited July 7, 2023 by mvpwar 0 Quote
mvpwar Posted July 7, 2023 Posted July 7, 2023 20 hours ago, hotnikq said: Flash This UpdateV4.img file on EMMC and v0.5 on USB stick on port 3.0 Please post the LOG from TTL fail @hotnikq U-Boot SPL board init U-Boot SPL 2017.09-gc613b7ea04-210315 #zzz (Mar 15 2021 - 18:08:14) unknown raw ID phN unrecognized JEDEC id bytes: 00, 00, 00 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 No misc partition ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256+ OK ## Checking uboot 0x00a00000 ... sha256+ OK ## Checking fdt 0x00b3bb50 ... sha256+ OK ## Checking atf-2 0xfdcc9000 ... sha256+ OK ## Checking atf-3 0xfdcd0000 ... sha256+ OK ## Checking optee 0x08400000 ... sha256+ OK Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000) Total: 224.238 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= 780MHz 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 INFO: BL31: Initializing BL32 I/TC: I/TC: Start rockchip platform init I/TC: Rockchip release version: 1.0 I/TC: OP-TEE version: 3.6.0-307-g0b06ae94 #1 Fri May 7 01:52:27 UTC 2021 aarch64 I/TC: Initialized INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0xa00000 INFO: SPSR = 0x3c9 U-Boot 2017.09 #qmx_srv (Mar 20 2023 - 17:46:24 +0800) Model: Rockchip RK3568 Evaluation Board PreSerial: 2, raw, 0xfe660000 DRAM: 7.7 GiB Sysmem: init Relocation Offset: ed23d000 Relocation fdt: eb9f8820 - eb9fecd0 CR: M/C/I Using default environment Hotkey: ctrl+` dwmmc@fe2b0000: 1, dwmmc@fe2c0000: 2, sdhci@fe310000: 0 Bootdev(atags): mmc 0 MMC0: HS200, 200Mhz PartType: EFI DM: v1 No misc partition boot mode: None FIT: No boot partition No resource partition No resource partition Failed to load DTB, ret=-19 No find valid DTB, ret=-22 Failed to get kernel dtb, ret=-22 io-domain: OK Failed to get scmi clk dev dmc_fsp failed, ret=-19 Model: Rockchip RK3568 Evaluation Board 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 390000 KHz gpll 1188000 KHz cpll 1000000 KHz npll 24000 KHz vpll 24000 KHz hpll 24000 KHz ppll 200000 KHz armclk 816000 KHz aclk_bus 150000 KHz pclk_bus 50000 KHz aclk_top_high 300000 KHz aclk_top_low 200000 KHz hclk_top 150000 KHz pclk_top 50000 KHz aclk_perimid 300000 KHz hclk_perimid 150000 KHz pclk_pmu 100000 KHz Net: No ethernet found. Hit key to stop autoboot('CTRL+C'): 0 Could not find misc partition ANDROID: reboot reason: "(none)" optee api revision: 2.0 TEEC: Reset area[0] info... TEEC: Reset area[1] info... Not AVB images, AVB skip android_image_load_by_partname: Can't find part: boot Android image load failed Android boot failed, error -1. ## Booting FIT Image FIT: No boot partition FIT: No fit blob FIT: No FIT image Could not find misc partition Could not find root part Card did not respond to voltage select! mmc_init: -95, time 10 switch to partitions #0, OK mmc0(part 0) is current device Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** ## Error: "mtd_boot" not defined ## Error: "mtd_boot" not defined ## Error: "mtd_boot" not defined starting USB... Bus dwc3@fcc00000: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 Bus dwc3@fd000000: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus dwc3@fcc00000 for devices... 1 USB Device(s) found scanning bus dwc3@fd000000 for devices... cannot reset port 1!? 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device No ethernet found. missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rockchip No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found No ethernet found. 0 Quote
Hqnicolas Posted July 7, 2023 Author Posted July 7, 2023 (edited) 22 hours ago, mvpwar said: the v4 update.img and v5 update.img can not change the partition so the box would boot fail with the maskrom state, it need to be flashed the u-boot.img and MiniLoader.bin to specify the partition name, like Uboot and Loader it's Friday night! let's build another build H96MAX 8GB RK3566 UPDATE.img How to build V7 8G_Linux_Pack_Firmware.zip @mvpwar @Kenneth Hidalgo can you test it? Following the tutorial instead of set Address on 0x0000A000 You will set Address on 0x0000c800 Edited July 8, 2023 by hotnikq 0 Quote
mvpwar Posted July 8, 2023 Posted July 8, 2023 (edited) 3 hours ago, hotnikq said: H96MAX 8GB RK3566 UPDATE.img How to build V7 8G_Linux_Pack_Firmware.zip @mvpwar @Kenneth Hidalgo can you test it? Following the tutorial instead of set Address on 0x0000A000 You will set Address on 0x00010800 I found the root partition is -@0x0000c800(root:grow) , flash root.img to the 0x00010800 ? @hotnikq U-Boot 2017.09-g32ed8ff-210328-dirty #pc (Apr 21 2021 - 20:51:20 +0800) Model: Rockchip RK3568 Evaluation Board PreSerial: 2, raw, 0xfe660000 DRAM: 7.7 GiB Sysmem: init Relocation Offset: ed39f000, fdt: eb9f8e18 Using default environment Hotkey: ctrl+` dwmmc@fe2b0000: 1, dwmmc@fe2c0000: 2, sdhci@fe310000: 0 Bootdev(atags): mmc 0 MMC0: HS200, 200Mhz PartType: EFI boot mode: recovery (misc) FIT: No recovery partition No resource partition No resource partition Failed to load DTB Failed to get kernel dtb, ret=-19 io-domain: OK Model: Rockchip RK3568 Evaluation Board 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 390000 KHz gpll 1188000 KHz cpll 1000000 KHz npll 24000 KHz vpll 24000 KHz hpll 24000 KHz ppll 100000 KHz armclk 816000 KHz aclk_bus 150000 KHz pclk_bus 50000 KHz aclk_top_high 300000 KHz aclk_top_low 200000 KHz hclk_top 150000 KHz pclk_top 50000 KHz aclk_perimid 300000 KHz hclk_perimid 150000 KHz pclk_pmu 50000 KHz Net: No ethernet found. Hit key to stop autoboot('CTRL+C'): 0 ## Booting FIT Image FIT: No recovery partition FIT: No FIT image ANDROID: reboot reason: "recovery" optee api revision: 2.0 TEEC: Waring: Could not find security partition Vboot=0, AVB images, AVB verify lib/avb/libavb_user/avb_ops_user.c: init lock state error Error determining whether device is unlocked. read_is_device_unlocked() ops returned that device is UNLOCKED Could not find "recovery" partition avb_slot_verify.c:661: ERROR: recovery: Error loading footer. Verify recovery with vbmeta. avb_slot_verify.c:759: ERROR: vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED lib/avb/libavb_user/avb_ops_user.c: init rollback index error avb_slot_verify.c:880: ERROR: vbmeta: Error getting rollback index for location. AVB verify failed Android boot failed, error -1. MMC error: The cmd index is 1, ret is -110 Card did not respond to voltage select! mmc_init: -95, time 10 switch to partitions #0, OK mmc0(part 0) is current device Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** starting USB... Bus dwc3@fcc00000: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 Bus dwc3@fd000000: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus dwc3@fcc00000 for devices... 1 USB Device(s) found scanning bus dwc3@fd000000 for devices... cannot reset port 1!? 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device No ethernet found. missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rockchip No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found No ethernet found. No ethernet found. Edited July 8, 2023 by mvpwar 0 Quote
Hqnicolas Posted July 8, 2023 Author Posted July 8, 2023 (edited) 1 hour ago, mvpwar said: found the root partition is -@0x0000c800(root:grow) , Thank you! Please use 0x0000c800 Flash the update again and do root on 0x0000c800 Please consider to rename this root partition to "recovery" on a second try rename it to "root" Edited July 8, 2023 by hotnikq 0 Quote
Hqnicolas Posted July 8, 2023 Author Posted July 8, 2023 (edited) 1 hour ago, mvpwar said: Card did not respond to voltage select! My god, that's good be a difference in voltage regulator 👀 It's a device with tcs4525 Or sti8070? This uboot from 8gb device don't like to boot from USB... I think we have somebody in this girl with SD card reader soldered on 8gb device Edited July 8, 2023 by hotnikq 0 Quote
mvpwar Posted July 8, 2023 Posted July 8, 2023 4 minutes ago, hotnikq said: My god, that's good be a difference in voltage regulator 👀 It's a device with tcs4525 Or sti8070? how to check 0 Quote
Hqnicolas Posted July 8, 2023 Author Posted July 8, 2023 (edited) 8 minutes ago, mvpwar said: how to check I think by reading DTB from the kernel 4 that boot... You will find things like this Edited July 8, 2023 by hotnikq 0 Quote
mvpwar Posted July 8, 2023 Posted July 8, 2023 1 hour ago, mvpwar said: Android boot failed, error -1. MMC error: The cmd index is 1, ret is -110 Card did not respond to voltage select! mmc_init: -95, time 10 switch to partitions #0, OK mmc0(part 0) is current device Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** starting USB... @hotnikqMaybe the mmc error is mmc1, which is the sd card slot(default no exists) boot first , and then u-boot try to boot the mmc0 (emmc) , after it is failed to mount ext2, finally try to scan usb for booting 0 Quote
Hqnicolas Posted July 8, 2023 Author Posted July 8, 2023 Just now, mvpwar said: hotnikqMaybe the mmc error is mmc1 Ah ok, so, the uboot is fine, I don't know why it doesn't detect the root.img 🤔 Did you try to boot flashdrive? 0 Quote
mvpwar Posted July 8, 2023 Posted July 8, 2023 3 minutes ago, hotnikq said: I think by reading DTB from the kernel 4 that boot... You will find things like this the ubuntu and debian10 can be booting on my box... 0 Quote
Hqnicolas Posted July 8, 2023 Author Posted July 8, 2023 (edited) 2 minutes ago, mvpwar said: the ubuntu The old 8gb image that I made? Can you share it here? The only difference between 4gb and 8gb ROM on my old Ubuntu is miniliaderall.bin Edited July 8, 2023 by hotnikq 0 Quote
mvpwar Posted July 8, 2023 Posted July 8, 2023 1 minute ago, hotnikq said: Did you try to boot flashdrive? usb? the root partition and usb-stick both failed for testing 2 minutes ago, hotnikq said: I don't know why it doesn't detect the root.img I also have no idea, why you can boot without the boot partition ... 0 Quote
Hqnicolas Posted July 8, 2023 Author Posted July 8, 2023 1 minute ago, mvpwar said: usb-stick both failed for testing USB stick with the v0.5 image from this topic? 0 Quote
mvpwar Posted July 8, 2023 Posted July 8, 2023 1 minute ago, hotnikq said: The old 8gb image that I made? en ,but there is only 4G total at the 8G box , and hdmi is bad, so the images is not good the debian10 image is good, usb3,usb2.0 both works , hdmi works, the only problem is the kernel is 4.19.193 @hotnikq 0 Quote
mvpwar Posted July 8, 2023 Posted July 8, 2023 2 minutes ago, hotnikq said: USB stick with the v0.5 image from this topic? yes, my usb stick flashed your v0.5 named "Armbian_23.08.0-trunk_Station-m2_jammy_edge_6.2.16_xfce_desktop.img" 0 Quote
Hqnicolas Posted July 8, 2023 Author Posted July 8, 2023 @mvpwar One more trick... 7 minutes ago, hotnikq said: The only difference between 4gb and 8gb ROM on my old Ubuntu is miniliaderall.bin Can you flash the 4gb device update image And put the 8gb mini loader all.bin It will make the device work again on maskrom and Reeboot to loader So you can flash root.img 0 Quote
mvpwar Posted July 8, 2023 Posted July 8, 2023 2 minutes ago, hotnikq said: Can you flash the 4gb device update image which update.img ? I can change the miniLoaderall.bin by RKdevTool 0 Quote
Kenneth Hidalgo Posted July 8, 2023 Posted July 8, 2023 Hi Friends, I was able to solve the problem of space in the Root partition, with the file parameters.txt that they sent me, thank you very much and the device is almost functional 0 Quote
mvpwar Posted July 8, 2023 Posted July 8, 2023 2 minutes ago, Kenneth Hidalgo said: with the file parameters.txt that they sent me, my file not work? @Kenneth Hidalgo 0 Quote
Hqnicolas Posted July 8, 2023 Author Posted July 8, 2023 43 minutes ago, mvpwar said: which update.img ? this one 0 Quote
mvpwar Posted July 8, 2023 Posted July 8, 2023 (edited) @hotnikq I want to upgrade the debian 10 firmware, and manual flashed the new boot.img which has the new kernel to instead of boot partition Can you help to create a new boot.img by integrating the v6.2 binary kernel boot file from your root.img into the new boot.img? or provide a tutorial or link about how to create the boot.img The key to this issue is that the boot partition does not have 6.2 kernel binary files. If there are any, everything is fine because I can now use kernel 4.19.13 of Armbian(Debian_23.08.0-H96MAX_RK3566_bookworm_ROOT_edge_6.2.16_xfce_desktop.img) I found you can make the boot.img, the boot.img of ubuntu is different from debian10 and android Edited July 8, 2023 by mvpwar 0 Quote
Hqnicolas Posted July 8, 2023 Author Posted July 8, 2023 (edited) 5 hours ago, mvpwar said: found you can make the boot.img, the boot.img of ubuntu is different from debian10 and android You will need to find a Linux Fit image compiler, that will compile uboot mainline and kernel mainline, for root partition you can use armbian v0.7 root. https://uthings.uniud.it/building-mainline-u-boot-and-linux-kernel-for-orange-pi-boards Edited July 8, 2023 by hotnikq 0 Quote
Hqnicolas Posted July 8, 2023 Author Posted July 8, 2023 (edited) 13 hours ago, mvpwar said: I also have no idea, why you can boot without the boot partition ... My Uboot.img stop scaning for android boot.img and starts scaning for mmc0 and mmc1 partitions that can boot... "can be an armbian SD-Card" so it found the root.img v0.7 inside EMMC, that have kernel inside, and boot from it. it pass the board from uboot legacy to armbian mainline 14 hours ago, hotnikq said: Please consider to rename this root partition to "recovery" on a second try rename it to "root" Also try to rename it to boot partition Edited July 8, 2023 by hotnikq 0 Quote
mvpwar Posted July 9, 2023 Posted July 9, 2023 can you backup your box without the root partition ? @hotnikq 0 Quote
Hqnicolas Posted July 9, 2023 Author Posted July 9, 2023 (edited) 19 minutes ago, mvpwar said: can you backup your box without the root partition ? $ lsblk mmcblk1 179:0 0 29,1G 0 disk ├─mmcblk1p1 179:1 0 4M 0 part ├─mmcblk1p2 179:2 0 4M 0 part ├─mmcblk1p3 179:3 0 4M 0 part └─mmcblk1p4 179:4 0 29,1G 0 part /var/log.hdd sudo dd if=/dev/mmcblk1p1 of=~/p1.img bs=4096 status=progress sudo dd if=/dev/mmcblk1p2 of=~/p2.img bs=4096 status=progress sudo dd if=/dev/mmcblk1p3 of=~/p3.img bs=4096 status=progress P1.img P2.img P3.img P4 = root.img from tutorial Edited July 9, 2023 by hotnikq 0 Quote
mvpwar Posted July 13, 2023 Posted July 13, 2023 @hotnikq abandon, no ideas maybe the box only support the kernel 4.19.193, your box is the most special 0 Quote
Hqnicolas Posted July 13, 2023 Author Posted July 13, 2023 (edited) On 7/13/2023 at 10:38 AM, mvpwar said: your box is the most special the 4gb version, the only difference is that I execute debug on the device let's start a campaign for interested users to send me an 8gb device in exchange for firmware development... @mvpwar keep your box, someday someone will build this firmware @ufsm is our white knight, he will put the V0.5 BETA image on SD Card and build the EMMC image for 8gb devices @chinhhut whatsap Edited July 16, 2023 by hotnikq 0 Quote
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.