RaptorSDS Posted August 6, 2023 Share Posted August 6, 2023 (edited) vor 16 Stunden schrieb n3o: I want install the most recent image of armbian with gui (so I don't want android) and in first post is written that it's necessary update bootloader "For fearless and bold people who are having issues when (re)booting images, there is the chance to upgrade the bootloader on NAND". Yes correct --> NAND install = legacy armbian but you can boot latest Armbian from SD card or USB and ignore NAND complete Bootloader update only possible with male - male USB cable and rktool outside of the box there are 3 bootloader 1. open ones , SD-Card , USB and NAND boot allow , boot SD-CARD/USB also if there a OS in NAND or install Armbian legacy to nand 2. open ones , SD-Card USB Boot NAND boot allow but boot NAND first , there you can try the new point in Multitool "Jump start " that always redirect boot to SD-Card or install Armbian legacy to nand 3 close ones (rare ones), that the ones with probleme where you have to update bootloader Please !!! do the simple steps first , simple install legacy to nand and try it --> flash multitool on SD-card , put image file in the folder , start multitool , save android , clean nand and install(flash) armbian to nand or flash image file on sd-card and boot armbian legacy or newest vor 16 Stunden schrieb n3o: ok, where I can find this file (and how to reach destination if android no more boot)? we do need them only when all other failed , RK322x have some already inside armbian , many work with many diffirent setups and hardware already no need to do 10 step ahead please simple first !!!! please dont do this 10 steps ahead , i only want to say make a backup of android its good to have one also if corrupt . Edited August 6, 2023 by RaptorSDS 1 Quote Link to comment Share on other sites More sharing options...
wslab Posted August 6, 2023 Share Posted August 6, 2023 Hello, I'm trying to install Armbian on "T9 Android 9.0 TV Box DDR3 RAM 32GB ROM RK3318": https://www.amazon.com/gp/product/B07GPCJSRR/ Tried booting from SD card using Armbian_23.5.1_Rk3318-box_jammy_current_6.1.30_minimal.img.xz (SHA 24ad44c3402b7f38c45a20d8abd2e69a3486e89108730481b066e3978e962e9f) and Armbian_23.5.1_Rk3318-box_jammy_current_6.1.30.img.xz (SHA f4d066a65f7483d7afb41c4b16899abdb9dda1d30c3f30eb67806e734f7a482c). Boot log from Armbian_23.5.1_Rk3318-box_jammy_current_6.1.30.img.xz: Spoiler =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2023.08.06 09:46:24 =~=~=~=~=~=~=~=~=~=~=~= �DDR version 1.15 20190428 ID:0xFFF In DDR3 333MHz Bus Width=32 Col=11 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=4096MB ddrconfig:3 OUT Boot1 Release Time: Sep 7 2018 15:49:55, version: 2.49 ChipType = 0x11, 193 mmc2:cmd19,100 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=29820MB FwPartOffset=2000 , 2000 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=29819MB FwPartOffset=2000 , 0 StorageInit ok = 56900 Raw SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 GPT 0x337a9e0 signature is wrong LoadTrust Addr:0x4000 LoadTrust Addr:0x4400 LoadTrust Addr:0x4800 LoadTrust Addr:0x4c00 LoadTrust Addr:0x5000 LoadTrust Addr:0x5400 LoadTrust Addr:0x5800 LoadTrust Addr:0x5c00 Addr:0x4000 No find trust.img! LoadTrustBL error:-3 Raw SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 GPT part: 0, name: uboot, start:0x4000, size:0x2000 GPT part: 1, name: trust, start:0x6000, size:0x2000 GPT part: 2, name: misc, start:0x8000, size:0x2000 GPT part: 3, name: baseparameter, start:0xa000, size:0x800 GPT part: 4, name: resource, start:0xa800, size:0x8000 GPT part: 5, name: kernel, start:0x12800, size:0x10000 GPT part: 6, name: dtb, start:0x22800, size:0x2000 GPT part: 7, name: dtbo, start:0x24800, size:0x2000 GPT part: 8, name: logo, start:0x26800, size:0x8000 GPT part: 9, name: vbmeta, start:0x2e800, size:0x800 GPT part: 10, name: boot, start:0x2f000, size:0x10000 GPT part: 11, name: recovery, start:0x3f000, size:0x20000 GPT part: 12, name: backup, start:0x5f000, size:0x8000 GPT part: 13, name: cache, start:0x67000, size:0x80000 GPT part: 14, name: system, start:0xe7000, size:0x400000 GPT part: 15, name: metadata, start:0x4e7000, size:0x8000 GPT part: 16, name: vendor, start:0x4ef000, size:0x60000 GPT part: 17, name: oem, start:0x54f000, size:0x320000 GPT part: 18, name: frp, start:0x86f000, size:0x400 GPT part: 19, name: security, start:0x86f400, size:0x1000 GPT part: 20, name: userdata, start:0x870400, size:0x31cdbdf find partition:uboot OK. first_lba:0x4000. find partition:trust OK. first_lba:0x6000. LoadTrust Addr:0x6000 No find bl30.bin Load uboot, ReadLba = 4000 Load OK, addr=0x200000, size=0xc1d10 RunBL31 0x10000 NOTICE: BL31: v1.3(release):0e7a845e NOTICE: BL31: Built : 16:24:22, Apr 29 2019 NOTICE: BL31:Rockchip release version: v1.3 INFO: ARM GICv2 driver initialized INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe INFO: BL31: Initializing runtime services INFO: BL31: Initializing BL32 INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-194-g646eecc5 #61 Wed Dec 5 06:31:51 UTC 2018 aarch64) INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.4 INF [0x0] TEE-CORE:init_teecore:83: teecore inits done INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2017.09-02229-g9061290-dirty (Mar 24 2022 - 15:41:05 +0800) PreSerial: 2 DRAM: 4 GiB Relocation Offset is: fcc04000 Using default environment rksdmmc@ff500000: 1, rksdmmc@ff520000: 0 Buswidth = 1, clock: 0 Buswidth = 1, clock: 400000 Buswidth = 1, clock: 400000 Sending CMD0 Sending CMD8 Sending CMD55 Sending CMD41 Sending CMD55 Sending CMD41 Sending CMD2 Sending CMD3 Sending CMD9 Sending CMD7 Sending CMD55 Sending CMD51 Sending CMD6 Sending CMD6 Sending CMD55 Sending CMD6 Buswidth = 4, clock: 400000 Sending CMD55 Sending CMD13 Buswidth = 4, clock: 50000000 Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table switch to partitions #0, OK mmc1 is current device Sending CMD16 Sending CMD18 Sending CMD12 do_rkimg_test found IDB in SDcard Boot from SDcard Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table get part misc fail -1 Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table init_resource_list: failed to get boot part, ret=-1 Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table init_resource_list: failed to get resource part, ret=-1 DTB: rk-kernel.dtb Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table get part misc fail -1 Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table init_resource_list: failed to get boot part, ret=-1 Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table init_resource_list: failed to get resource part, ret=-1 Can't find file:rk-kernel.dtb init_kernel_dtb dtb in resource read fail In: serial Out: serial Err: serial Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table get part misc fail -1 Sending CMD16 Sending CMD18 Sending CMD12 Sending CMD16 Sending CMD18 Sending CMD12 Sending CMD16 Sending CMD18 Sending CMD12 Sending CMD16 Sending CMD18 Sending CMD12 CLK: apll 400000000 Hz dpll 664000000 Hz cpll 1200000000 Hz gpll 491009999 Hz npll 600000000 Hz armclk 600000000 Hz aclk_bus 150000000 Hz hclk_bus 75000000 Hz pclk_bus 75000000 Hz aclk_peri 150000000 Hz hclk_peri 75000000 Hz pclk_peri 75000000 Hz Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 0 Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table android_bootloader_boot_flow Could not find misc partition MMC: block number 0xecdfe6b2 exceeds max(0x3a3d800) failed to read ca head from misc Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table get part misc fail -1 ANDROID: reboot reason: "(none)" get share memory, arg0=0x0 arg1=0x9e08000 arg2=0x3f8000 arg3=0x1 Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find security partition rkss_read_patition_tables fail ! ret: -1.Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find security partition rkss_read_patition_tables fail ! ret: -1.Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find security partition rkss_read_patition_tables fail ! ret: -1.ERR [0x0] TEE-CORE:ree_fs_open:1488: tee file not exists get share memory, arg0=0x0 arg1=0x9e08000 arg2=0x3f8000 arg3=0x1 Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find security partition rkss_read_patition_tables fail ! ret: -1.Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find security partition rkss_read_patition_tables fail ! ret: -1.Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find security partition rkss_read_patition_tables fail ! ret: -1.Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find security partition rkss_read_patition_tables fail ! ret: -1.Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find security partition rkss_read_patition_tables fail ! ret: -1.Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find security partition rkss_read_patition_tables fail ! ret: -1.Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find security partition rkss_read_patition_tables fail ! ret: -1.tee_fs_open : error. A54E481B8B69424182B83ACF16E99E2A/.01000000/lock_state/meta.0ERR [0x0] TEE-CORE:create_tee_file:1420: Failed to create new meta file ERR [0x0] TEE-CORE:ree_fs_open:1497: Failed to open TEE file 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 Sending CMD16 Sending CMD17 Sending CMD16 Sending CMD18 Sending CMD12 RKPARM: Invalid parameter part table Could not find "misc" partition avb_ab_flow.c:99: ERROR: Error reading A/B metadata. avb_ab_flow.c:178: ERROR: I/O error while loading A/B metadata. Can not load metadata Android boot failed, error -1. AVB boot failed and enter rockusb or fastboot! RKUSB: LUN 0, dev 1, hwpart 0, sector 0x0, count 0x3a3d800 | / - \ Multitool boots successfully though (multitool.img.xz SHA a4f369fa06076212d6f46c10355c6163f147c70b19abf4e36ea7cf3363d01467), multitool boot log: Spoiler DDR version 1.15 20190428 ID:0xFFF In DDR3 333MHz Bus Width=32 Col=11 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=4096MB ddrconfig:3 OUT Boot1 Release Time: Sep 7 2018 15:49:55, version: 2.49 ChipType = 0x11, 193 mmc2:cmd19,100 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=29820MB FwPartOffset=2000 , 2000 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=29819MB FwPartOffset=2000 , 0 StorageInit ok = 61762 Raw SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 GPT 0x337a9e0 signature is wrong LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xacc6c RunBL31 0x10000 NOTICE: BL31: v1.3(release):f947c7e NOTICE: BL31: Built : 10:31:25, Nov 1 2020 NOTICE: BL31: initializing secure efuse NOTICE: BL31: initializing non-secure efuse NOTICE: BL31: enabling efuse clock NOTICE: BL31:Rockchip release version: v1.3 U-Boot 2021.07-armbian (Nov 13 2021 - 11:25:20 +0000) Model: Rockchip RK3318 BOX DRAM: 4 GiB MMC: mmc@ff500000: 1, mmc@ff520000: 0, dwmmc@ff5f0000: 3 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Rockchip RK3318 BOX Net: eth1: ethernet@ff550000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:2... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 169 bytes read in 7 ms (23.4 KiB/s) 1: Multitool Retrieving file: /kernel.img 15949832 bytes read in 697 ms (21.8 MiB/s) append: boot=UUID=E2B5-C028 root=PARTUUID=7379cc53-03 rootwait console=ttyS2,115200 verbose=1 consoleblank=0 Retrieving file: /rk3318-box.dtb 71886 bytes read in 8 ms (8.6 MiB/s) ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 ERROR: reserving fdt memory region failed (addr=0 size=0) Using Device Tree in place at 0000000001f00000, end 0000000001f148cd Starting kernel ... Is booting from SD card not supported? Do I need to write the image to eMMC? Thanks in advance for any pointers! 0 Quote Link to comment Share on other sites More sharing options...
jock Posted August 7, 2023 Author Share Posted August 7, 2023 @wslab wrong thread, please refer to the first page of the correct thread, everything is written in there: https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/ 1 Quote Link to comment Share on other sites More sharing options...
n3o Posted August 7, 2023 Share Posted August 7, 2023 On 8/6/2023 at 1:12 PM, RaptorSDS said: Yes correct --> NAND install = legacy armbian but you can boot latest Armbian from SD card or USB and ignore NAND complete ok On 8/6/2023 at 1:12 PM, RaptorSDS said: Bootloader update only possible with male - male USB cable and rktool outside of the box there are 3 bootloader 1. open ones , SD-Card , USB and NAND boot allow , boot SD-CARD/USB also if there a OS in NAND or install Armbian legacy to nand 2. open ones , SD-Card USB Boot NAND boot allow but boot NAND first , there you can try the new point in Multitool "Jump start " that always redirect boot to SD-Card or install Armbian legacy to nand 3 close ones (rare ones), that the ones with probleme where you have to update bootloader ok, the 2 bootloader here https://github.com/ilmich/rkflashtool/tree/master/bin do You know of what type are? On 8/6/2023 at 1:12 PM, RaptorSDS said: Please !!! do the simple steps first , simple install legacy to nand and try it --> flash multitool on SD-card , put image file in the folder , start multitool , save android , clean nand and install(flash) armbian to nand referred to legacy armbian, what is difference between bullseye and jammy? Both kernel are current and both are 5.15.80. On 8/6/2023 at 1:12 PM, RaptorSDS said: or flash image file on sd-card and boot armbian legacy or newest I think it's bettere install legacy armbian to nand, and only after this flash armbian newest to sd (I think it's possible boot system directly from sd without install , true?) 0 Quote Link to comment Share on other sites More sharing options...
RaptorSDS Posted August 7, 2023 Share Posted August 7, 2023 vor 1 Stunde schrieb n3o: ok, the 2 bootloader here https://github.com/ilmich/rkflashtool/tree/master/bin do You know of what type are? no but ilmich would post close ones , so i thing there will be open ones , but simple first if you havent problem with legacy armbian please dont do step 10 infront of step 1 vor 1 Stunde schrieb n3o: bullseye and jammy bullseye debian 11 jammy ubuntu 22.04 vor 1 Stunde schrieb n3o: think it's bettere install legacy armbian to nand, and only after this flash armbian newest to sd (I think it's possible boot system directly from sd without install , true?) yes you can nand first , yes correct sd card direct without install when bootloader 1 else you maybe need "jump start" from multitool 0 Quote Link to comment Share on other sites More sharing options...
calusbr Posted August 7, 2023 Share Posted August 7, 2023 Hello everyone, I recently acquired a TV BOX MXQ PRO 4k 5g with the RK3228a chipset and the mxq-ep-2-v1.0 model board. I've been trying to install Armbian on it, but I've encountered some challenges that I could use some assistance with. Here's what I've experienced so far: 1. When I press the reset button (AV), it triggers the Android recovery mode instead of booting into the system. 2. My attempts to create a clean Armbian ISO "Armbian_23.8.0-trunk.56_Rk322x-box_bookworm_edge_6.3.8_xfce_desktop" on an SD card have not been successful in achieving a successful boot. 3. I've also considered using software like RKDevTool, SDDiskTool, or Rockchip Assistant, but I'm unsure if these proprietary tools are necessary or if there's an alternative solution. I've attached images of the board and the boot screen for reference. Could anyone provide guidance on how to successfully install Armbian on this device or recommend any tutorials for initializing the SD card? Your insights would be greatly appreciated. Thank you in advance for your help! [Attached Images: Images of the board and boot screen] Best regards, Lucas (calusbr) 0 Quote Link to comment Share on other sites More sharing options...
jock Posted August 8, 2023 Author Share Posted August 8, 2023 15 hours ago, calusbr said: I've attached images of the board and the boot screen for reference. Could anyone provide guidance on how to successfully install Armbian on this device or recommend any tutorials for initializing the SD card? Your insights would be greatly appreciated. Guidance is the first page of this thread. If you're unsure about a passage wrote there, explain with a post what you're unsure about. 0 Quote Link to comment Share on other sites More sharing options...
Benedito Portela Posted August 8, 2023 Share Posted August 8, 2023 Hi, I have a MXQ_PRO 4K, new, (mxq_r2b_lp3_v2.62_220225) too! It don't work the multitool, black screen, orange led turn on, in sdcard ou flashdrive! In other MXQ old, RQ329 that work fine, it's configured sdcard, that don't work in the new mxq, black screen and led turn off, what can be this problem? Thank you for help! 0 Quote Link to comment Share on other sites More sharing options...
jock Posted August 8, 2023 Author Share Posted August 8, 2023 23 minutes ago, Benedito Portela said: what can be this problem? We don't know! The board is new and it just does not work 🤷♂️ And please don't ask for solutions: proper serial logs, original device trees and firmware perhaps may help, but most we need the board in our hands to give the chance to support it. 1 Quote Link to comment Share on other sites More sharing options...
MattWestB Posted August 9, 2023 Share Posted August 9, 2023 (edited) @Benedito Portela The console is on the pads on the underside of the PCB as of the older version and you can see it in my tear down of the old version here https://github.com/MattWestb/R29-MXQ-LP3-V2.3-00908. The MASCROM pads i think being moved and looks being some pads near the memory but the photo is not sharp enough for see that and hopefully you dont need it but you need erasing the eMMC for getting the box booting external media with current kernel and if like getting it working good writing one new updated bootloader in the eMMC that making it booting all medias also USB storage by jump star from the eMMC to external media. I have not the HDMI and WiFi working but is not bad then i dont need them then using Eth and the HDMI is only making the CPU using more power and being heater so better not connecting it then have getting SSH working and using one good SHH terminal program to manage the box. Edit: The MASCROM pads is 110% the same only its little nearer the CPU then the layout is the same so shall working as the old version only look on the photos and you is finding them. Edited August 9, 2023 by MattWestB 0 Quote Link to comment Share on other sites More sharing options...
calusbr Posted August 9, 2023 Share Posted August 9, 2023 @jock Hello there, I've been following the steps outlined on page 1 carefully to install Armbian on my TV Box. Unfortunately, I've encountered a roadblock. Even though I've completed all the steps, when I insert the SDCARD into the TV Box and power it on, the device doesn't seem to start up. Strangely, the TV Box only powers on when the SDCARD is not connected, or if I press the reset button without the SDCARD, it boots into Android recovery mode. I'm at a loss on how to initiate the SDCARD boot with Multitool or load a clean Armbian image. Any guidance or insights on how to overcome this issue and successfully boot from the SDCARD would be highly appreciated. Thank you in advance for your help! 0 Quote Link to comment Share on other sites More sharing options...
Benedito Portela Posted August 9, 2023 Share Posted August 9, 2023 Hi MattWestB, thank you for attention! I saw your post, but i need of HDMI, Sound e Eth, i don't use SSH terminal! I wotk with electronic informatic hardware, i know a bit of linux, but the tvbox are very complicate to configure, i want help, if you know where i can learn about boot process, how change configs to setup to hardware correct, i'm grateful! 0 Quote Link to comment Share on other sites More sharing options...
MattWestB Posted August 9, 2023 Share Posted August 9, 2023 @Benedito Portela Im not one code warier but was installing my first Linux fro 2 diskettes one with kernel and the other with root FS and i think the kernel was 0.95 or somthing but im not so deep in it so i can doing little but im better electronic hardware. The HDMI problem we dont have and fix for then the persons with knowledge has nit getting there hands on one for digging deeper in it. Is you Italian ? If yes our 2 best is the same and if you can getting your box to one of them it can being possible they finding that hardware tricks that is needed for getting it working OK. I think your box shall being possible getting up and running but the HDMI i think cant being done for the moment (its over 1.5 years old problem with some boxes). That is needed if doing it the easy way is soldering the comport and using one terminal program and one USB-TTL 3.3V for making the first configuration then you cant see what you is doing with only keyboard then the HDMI is not working. 0 Quote Link to comment Share on other sites More sharing options...
Benedito Portela Posted August 9, 2023 Share Posted August 9, 2023 MattWestB, I'm brazillian! I have a mxq R329 working fine in a project, and wish have other like backup! I don't knew that tvbox have many variations and that it new don't work well, I sould be choice the orange pi or other simples raspberry clone to make project, but i get this used box, from a friend, and start in the tvbox's world! I'll continued to learn, any news, i tell you! Thank you! 1 Quote Link to comment Share on other sites More sharing options...
jock Posted August 9, 2023 Author Share Posted August 9, 2023 9 hours ago, calusbr said: Any guidance or insights on how to overcome this issue and successfully boot from the SDCARD would be highly appreciated. No guidance is possible without the serial logs; if people don't know what is going on, how can suggest you further steps? Next time buy an armbian properly supported SBC and you will have no troubles 0 Quote Link to comment Share on other sites More sharing options...
ego worker Posted August 10, 2023 Share Posted August 10, 2023 (edited) @Benedito Portela got the same board, https://github.com/kenavru/rk3228_TVBox here some of my logs. only images with legacy kernel 4.4 works, but still no HDMI ofc. Only SSH or serial. multitool works the same. would be nice to have working mainline at least ... Edited August 10, 2023 by ego worker 1 Quote Link to comment Share on other sites More sharing options...
fabiobassa Posted August 10, 2023 Share Posted August 10, 2023 (edited) DISCLAIMER We don't own , have studied , have even seen ANY of the new mxq_r2b_lp3_v2.62_220225 boards We don't know what is going on those, no further help, infos, tips avaible until we get one of PLEASE STOP asking why they don't work because WE SIMPLY DON'T KNOW Any of you can still donate one sample for further investigations Thanks for understanding it !!!! Edited August 10, 2023 by fabiobassa 1 Quote Link to comment Share on other sites More sharing options...
ego worker Posted August 10, 2023 Share Posted August 10, 2023 (edited) @fabiobassa so couldnt you give some hints what to check etc. Whats the proces of making new board work ? some tutorials, links where to learn it etc. Most of RK3228/9 just works fine, soc didn't change - then prob something with HW settings of DRAM/EMMC. Without this dev team will never increase cant find any other place to share info with any community about this board than this topic, and you say to stop ... for now focusing on recompiling DTB from android, but without any boot success regular just breaks from the beginig https://github.com/kenavru/rk3228_TVBox/blob/main/CurrentKernel.txt Internal error: kernel stack overflow: 0 [#1] PREEMPT SMP ARM hmm starting getting some life signals from hdmi xD [ 8.793093] rockchip-vop 20050000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11 [ 8.803291] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13 [ 8.813785] dwhdmi-rockchip 200a0000.hdmi: colorspace: RGB [ 8.819688] dwhdmi-rockchip 200a0000.hdmi: scan mode: Underscan [ 8.826025] dwhdmi-rockchip 200a0000.hdmi: colorimetry: No Data [ 8.832361] dwhdmi-rockchip 200a0000.hdmi: picture aspect: 16:9 [ 8.838696] dwhdmi-rockchip 200a0000.hdmi: active aspect: Same as Picture [ 8.845897] dwhdmi-rockchip 200a0000.hdmi: itc: IT Content [ 8.851792] dwhdmi-rockchip 200a0000.hdmi: extended colorimetry: xvYCC 601 [ 8.859077] dwhdmi-rockchip 200a0000.hdmi: quantization range: Full [ 8.865836] dwhdmi-rockchip 200a0000.hdmi: nups: Unknown Non-uniform Scaling [ 8.873359] dwhdmi-rockchip 200a0000.hdmi: video code: 16 [ 8.879201] dwhdmi-rockchip 200a0000.hdmi: ycc quantization range: Full [ 8.886291] dwhdmi-rockchip 200a0000.hdmi: hdmi content type: Graphics [ 8.893199] dwhdmi-rockchip 200a0000.hdmi: pixel repeat: 0 [ 8.899051] dwhdmi-rockchip 200a0000.hdmi: bar top 0, bottom 0, left 0, right 0 [ 14.251109] rockchip-vop 20050000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11 [ 14.261117] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13 [ 14.271538] dwhdmi-rockchip 200a0000.hdmi: colorspace: RGB [ 14.277411] dwhdmi-rockchip 200a0000.hdmi: scan mode: Underscan [ 14.283713] dwhdmi-rockchip 200a0000.hdmi: colorimetry: No Data [ 14.290010] dwhdmi-rockchip 200a0000.hdmi: picture aspect: 16:9 [ 14.296309] dwhdmi-rockchip 200a0000.hdmi: active aspect: Same as Picture [ 14.303475] dwhdmi-rockchip 200a0000.hdmi: itc: IT Content [ 14.309339] dwhdmi-rockchip 200a0000.hdmi: extended colorimetry: xvYCC 601 [ 14.316590] dwhdmi-rockchip 200a0000.hdmi: quantization range: Full [ 14.323236] dwhdmi-rockchip 200a0000.hdmi: nups: Unknown Non-uniform Scaling [ 14.330666] dwhdmi-rockchip 200a0000.hdmi: video code: 16 [ 14.336446] dwhdmi-rockchip 200a0000.hdmi: ycc quantization range: Full [ 14.343423] dwhdmi-rockchip 200a0000.hdmi: hdmi content type: Graphics [ 14.350308] dwhdmi-rockchip 200a0000.hdmi: pixel repeat: 0 [ 14.356151] dwhdmi-rockchip 200a0000.hdmi: bar top 0, bottom 0, left 0, right 0 [ 19.655318] rockchip-vop 20050000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11 [ 19.665302] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13 [ 19.675724] dwhdmi-rockchip 200a0000.hdmi: colorspace: RGB [ 19.681597] dwhdmi-rockchip 200a0000.hdmi: scan mode: Underscan [ 19.687899] dwhdmi-rockchip 200a0000.hdmi: colorimetry: No Data [ 19.694197] dwhdmi-rockchip 200a0000.hdmi: picture aspect: 16:9 [ 19.700495] dwhdmi-rockchip 200a0000.hdmi: active aspect: Same as Picture [ 19.707662] dwhdmi-rockchip 200a0000.hdmi: itc: IT Content [ 19.713528] dwhdmi-rockchip 200a0000.hdmi: extended colorimetry: xvYCC 601 [ 19.720781] dwhdmi-rockchip 200a0000.hdmi: quantization range: Full [ 19.727432] dwhdmi-rockchip 200a0000.hdmi: nups: Unknown Non-uniform Scaling [ 19.734856] dwhdmi-rockchip 200a0000.hdmi: video code: 16 [ 19.740634] dwhdmi-rockchip 200a0000.hdmi: ycc quantization range: Full [ 19.747615] dwhdmi-rockchip 200a0000.hdmi: hdmi content type: Graphics [ 19.754500] dwhdmi-rockchip 200a0000.hdmi: pixel repeat: 0 [ 19.760344] dwhdmi-rockchip 200a0000.hdmi: bar top 0, bottom 0, left 0, right 0 [ 25.050875] random: nonblocking pool is initialized [ 25.059333] rockchip-vop 20050000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11 [ 25.069306] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13 [ 25.079722] dwhdmi-rockchip 200a0000.hdmi: colorspace: RGB [ 25.085592] dwhdmi-rockchip 200a0000.hdmi: scan mode: Underscan [ 25.091895] dwhdmi-rockchip 200a0000.hdmi: colorimetry: No Data [ 25.098212] dwhdmi-rockchip 200a0000.hdmi: picture aspect: 16:9 [ 25.104513] dwhdmi-rockchip 200a0000.hdmi: active aspect: Same as Picture [ 25.111678] dwhdmi-rockchip 200a0000.hdmi: itc: IT Content [ 25.117542] dwhdmi-rockchip 200a0000.hdmi: extended colorimetry: xvYCC 601 [ 25.124799] dwhdmi-rockchip 200a0000.hdmi: quantization range: Full [ 25.131445] dwhdmi-rockchip 200a0000.hdmi: nups: Unknown Non-uniform Scaling [ 25.138891] dwhdmi-rockchip 200a0000.hdmi: video code: 16 [ 25.144653] dwhdmi-rockchip 200a0000.hdmi: ycc quantization range: Full [ 25.151625] dwhdmi-rockchip 200a0000.hdmi: hdmi content type: Graphics [ 25.158506] dwhdmi-rockchip 200a0000.hdmi: pixel repeat: 0 [ 25.164347] dwhdmi-rockchip 200a0000.hdmi: bar top 0, bottom 0, left 0, right 0 [ 30.463258] rockchip-vop 20050000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11 [ 30.473244] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13 [ 30.483665] dwhdmi-rockchip 200a0000.hdmi: colorspace: RGB [ 30.489536] dwhdmi-rockchip 200a0000.hdmi: scan mode: Underscan [ 30.495838] dwhdmi-rockchip 200a0000.hdmi: colorimetry: No Data [ 30.502135] dwhdmi-rockchip 200a0000.hdmi: picture aspect: 16:9 [ 30.508434] dwhdmi-rockchip 200a0000.hdmi: active aspect: Same as Picture [ 30.515605] dwhdmi-rockchip 200a0000.hdmi: itc: IT Content [ 30.521460] dwhdmi-rockchip 200a0000.hdmi: extended colorimetry: xvYCC 601 [ 30.528693] dwhdmi-rockchip 200a0000.hdmi: quantization range: Full [ 30.535315] dwhdmi-rockchip 200a0000.hdmi: nups: Unknown Non-uniform Scaling [ 30.542714] dwhdmi-rockchip 200a0000.hdmi: video code: 16 [ 30.548471] dwhdmi-rockchip 200a0000.hdmi: ycc quantization range: Full [ 30.555440] dwhdmi-rockchip 200a0000.hdmi: hdmi content type: Graphics [ 30.562320] dwhdmi-rockchip 200a0000.hdmi: pixel repeat: 0 [ 30.568162] dwhdmi-rockchip 200a0000.hdmi: bar top 0, bottom 0, left 0, right 0 [ 35.939134] rockchip-vop 20050000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11 [ 35.948952] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13 [ 35.959396] dwhdmi-rockchip 200a0000.hdmi: colorspace: RGB [ 35.965290] dwhdmi-rockchip 200a0000.hdmi: scan mode: Underscan [ 35.971615] dwhdmi-rockchip 200a0000.hdmi: colorimetry: No Data [ 35.977934] dwhdmi-rockchip 200a0000.hdmi: picture aspect: 16:9 [ 35.984255] dwhdmi-rockchip 200a0000.hdmi: active aspect: Same as Picture [ 35.991449] dwhdmi-rockchip 200a0000.hdmi: itc: IT Content [ 35.997336] dwhdmi-rockchip 200a0000.hdmi: extended colorimetry: xvYCC 601 [ 36.004612] dwhdmi-rockchip 200a0000.hdmi: quantization range: Full [ 36.011281] dwhdmi-rockchip 200a0000.hdmi: nups: Unknown Non-uniform Scaling [ 36.018727] dwhdmi-rockchip 200a0000.hdmi: video code: 16 [ 36.024501] dwhdmi-rockchip 200a0000.hdmi: ycc quantization range: Full [ 36.031475] dwhdmi-rockchip 200a0000.hdmi: hdmi content type: Graphics [ 36.038356] dwhdmi-rockchip 200a0000.hdmi: pixel repeat: 0 [ 36.044207] dwhdmi-rockchip 200a0000.hdmi: bar top 0, bottom 0, left 0, right 0 Edited August 10, 2023 by ego worker 1 Quote Link to comment Share on other sites More sharing options...
fabiobassa Posted August 10, 2023 Share Posted August 10, 2023 (edited) @ego worker Just phisically have the board in our hands !!!! This Is the best hint we can give About the tutorial, this 3ad Is a big tutorial. Here you can find infos on boot process, logs, other bugs we found ( DDR timing, trust, other, cec) Just go with trials and errors as we already have done or donate a sample for the purpose Edited August 10, 2023 by fabiobassa 0 Quote Link to comment Share on other sites More sharing options...
n3o Posted August 10, 2023 Share Posted August 10, 2023 On 8/7/2023 at 4:04 PM, RaptorSDS said: On 8/7/2023 at 2:23 PM, n3o said: ok, the 2 bootloader here https://github.com/ilmich/rkflashtool/tree/master/bin do You know of what type are? no but ilmich would post close ones , so i thing there will be open ones , but simple first if you havent problem with legacy armbian please dont do step 10 infront of step 1 On 8/7/2023 at 2:23 PM, n3o said: bullseye and jammy bullseye debian 11 jammy ubuntu 22.04 On 8/7/2023 at 2:23 PM, n3o said: think it's bettere install legacy armbian to nand, and only after this flash armbian newest to sd (I think it's possible boot system directly from sd without install , true?) yes you can nand first , yes correct sd card direct without install when bootloader 1 else you maybe need "jump start" from multitool bad news : I have tried to run the box with sdcard inside with multitool, but nothing happen (the tv goes to energy save). Removing the sd card android tried to boot, but it's stop to recovery mode If I choose "Reboot to bootloader" device stop and nothing more happen (same result as with sd card inserted), if I choose "View recovery logs" the following info appear (I have only made photo of last 3 pages and I have open kmsg file because .log files was empty). Here the screenshot What should I do? 0 Quote Link to comment Share on other sites More sharing options...
RaptorSDS Posted August 10, 2023 Share Posted August 10, 2023 vor 8 Minuten schrieb n3o: Removing the sd card android tried to boot, but it's stop to recovery mode Have you tried with SD-Card insert and manuall by press recovery button with tootbrush (trough audio port) --> than switch to bootloader or maybe sd-card boot direct the box has to have the sd-card already in slot to read it ID and some other stuff when bootloader has to read from it when boot first to recovery without SD-card than maybe some information missing (for the bootloader) 0 Quote Link to comment Share on other sites More sharing options...
n3o Posted August 10, 2023 Share Posted August 10, 2023 2 minutes ago, RaptorSDS said: Have you tried with SD-Card insert and manuall by press recovery button with tootbrush (trough audio port) --> than switch to bootloader or maybe sd-card boot direct no, I haven't made try this. What should I do precisely? Should insert toothpick inside audio jack port? 3 minutes ago, RaptorSDS said: the box has to have the sd-card already in slot to read it ID and some other stuff when bootloader has to read from it yes, I have insert sd card into the slot before turn on the box 0 Quote Link to comment Share on other sites More sharing options...
RaptorSDS Posted August 10, 2023 Share Posted August 10, 2023 (edited) vor 40 Minuten schrieb n3o: no, I haven't made try this. What should I do precisely? Should insert toothpick inside audio jack port? Yes correct toothpick (soory for my toothbrush) audio port ( be gentle there is only a micro switch) hold and than plug in the power adapter , or alternativ plug in powercord and as fast as possible push the button for 1sec the picture is from my box , you box is diffirent but the button and button position behind audio jack should be the same Edited August 10, 2023 by RaptorSDS 0 Quote Link to comment Share on other sites More sharing options...
n3o Posted August 10, 2023 Share Posted August 10, 2023 1 hour ago, RaptorSDS said: Yes correct toothpick (soory for my toothbrush) audio port ( be gentle there is only a micro switch) hold and than plug in the power adapter , Problem still occur ... nothing boot, monitor is always in save energy mode 0 Quote Link to comment Share on other sites More sharing options...
n3o Posted August 10, 2023 Share Posted August 10, 2023 I hope only that isn't necessary unbrick procedure such art3mis_17 here 0 Quote Link to comment Share on other sites More sharing options...
RaptorSDS Posted August 11, 2023 Share Posted August 11, 2023 @jock@n3o@fabiobassa so we try simple step , but looks like close bootoader or broken bootloader --> any idee to get multitool running @jock is there a maskrom mode for NAND ? i think its more easy to short a clock pin for n3o than all the flashing rktool android and bootloader stuff . i dont lnow it there a android image here for rktool ? 0 Quote Link to comment Share on other sites More sharing options...
n3o Posted August 11, 2023 Share Posted August 11, 2023 2 hours ago, RaptorSDS said: @jock is there a maskrom mode for NAND ? I think that maskrom mode for NAND is this (get from first post) https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes/?do=findComment&comment=121103 2 hours ago, RaptorSDS said: i think its more easy to short a clock pin for n3o than all the flashing rktool android and bootloader stuff . Considering my very few knowledge on electronic and the fact that I'm not expert on hardware, I think it's more easy the link above 2 hours ago, RaptorSDS said: i dont lnow it there a android image here for rktool ? what do You think of this https://drive.google.com/file/d/1SKX7fcWhqeGVN8qxZ5pVUEmMOHI_WvQ8/view ? I have take it from here https://4pda.to/forum/index.php?showtopic=892127 ... 0 Quote Link to comment Share on other sites More sharing options...
jock Posted August 11, 2023 Author Share Posted August 11, 2023 4 hours ago, RaptorSDS said: @jock is there a maskrom mode for NAND ? Yes, of course; NAND also have a clock, shorting the clock pin has the same effect on eMMC and NAND devices. Still I haven't seen a serial log, without that, going further with support is a waste of time. 0 Quote Link to comment Share on other sites More sharing options...
RaptorSDS Posted August 11, 2023 Share Posted August 11, 2023 vor 15 Minuten schrieb jock: Yes, of course; NAND also have a clock, shorting the clock pin has the same effect on eMMC and NAND devices. i thing you have found the NW018 Nand memory information , please do you have more information what is clock pin maybe datasheet or picture to get in MASKrom mode 0 Quote Link to comment Share on other sites More sharing options...
n3o Posted August 11, 2023 Share Posted August 11, 2023 23 minutes ago, jock said: Still I haven't seen a serial log, without that, going further with support is a waste of time. here I have posted serial log https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes/?do=findComment&comment=169159 5 minutes ago, RaptorSDS said: i thing you have found the NW018 Nand memory information , please do you have more information what is clock pin maybe datasheet or picture to get in MASKrom mode I have tried to connect usb otg (usb port near to spdif connector behind box) to my pc but I don't see it (I have tried to install 5.1 driver, 4.8, 4.5 and so on) but front blue led is turnon 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.