micron

I have resolved the problem with UART communication - was soldering point between TX and capacitor on board, so after desoldering connection through UART works. Armbian does not boot from USB via flash-drive, but when writing it to SDCard - I see start of the system, but it hungs on "Starting kernel" Adding boot logs: DDR V1.05 4bit PCB 2eef4a672d huan.he 23/04/14-10:58:56 LP4/4x derate disable, other dram:1x trefi ddrconfig:15 DDR3, 324MHz BW=32 Col=11 Bk=8 CS0 Row=16 CS=1 Die BW=16 Size=4096MB tdqss: cs0 dqs0: 626ps, dqs1: 482ps, dqs2: 723ps, dqs3: 723ps, change to: 324MHz clk skew:0x64 change to: 528MHz clk skew:0x64 change to: 666MHz clk skew:0x64 change to: 786MHz(final freq) clk skew:0x64 PHY drv:clk:50,ca:28,DQ:40,odt:145 vrefinner:50%, vrefout:50% dram drv:34,odt:60 cs 0: the read training result: DQS0:0x5b, DQS1:0x51, DQS2:0x53, DQS3:0x53, min : 0x6 0x13 0x10 0x10 0x10 0x2 0x1 0x6 , 0x8 0x8 0x4 0x3 0x5 0x4 0x2 0x2 , 0x7 0x5 0x1 0x6 , 0x2 0x10 0x10 0x3 0x13 0x5 0x12 0x6 , mid 0x2f 0x2f 0x29 0x29 0x2b 0x2a 0x29 0x27 , 0x2a 0x32 0x2e 0x29 0x3b 0x2c 0x39 0x2d , max :0x56 0x65 0x60 0x5f 0x62 0x52x50 0x50 0x4d , 0x4d 0x5a 0x54 0x56 0x57 0x4c 0x4f 0x54 ,, range:0x50 0x52 0x50 0x4f 0x52 0x50 0x50 0x4e ,0x4e 0x4e 0x4b0x50 0x4c 0x51 0x4f 0x47 0x4e 0x4e ,0x4c 0x4f 0x50 0x4c 0x51 0x4: DQS0:0xa2, DQS1:0x94, DQS2:0xac, DQS3:0xac, min :0x83 0x8ab 0x7a 0x79 0x78 0x74 0x73 0x73 0x73 0x79 , 0x8f 0x96 0x95 0x96 0x8d 0x98 0x90 0x97 0x92 0x93 , mid :0x9d 0xa5 0xa2 0xax94 0x92 0x90 0x8e 0x8d 0x8c 0x95 , 0xa8 0xaf 0xab 0xac 0xa9 0xb4 0xab 0xb1 0xad 0xb0 , max :0xb8 0xc1 0xbb 0xbb 0xbd 0 0xac 0xa9 0xa8 0xa6 0xb1 , 0xc1 0xc9 0xc4 0xc7 0xc6 0xbdd0 0xc6 0xcc 0xc9 0xce , range:0x35 0x37 0x31 0x32 0x35 0x36 0x0x36 0x35 0x33 0x38 , 0x32 0x33 0x31 0x36 0x32 0x2f 0x37 0x35 0x37 0x3b , out U-Boot SPL board init U-Boot SPL 2017.09-g0fbedd0675-230404 #zyf (Apr 11 2023 - 09:25:18) unknown raw ID 0 0 0 unrecognized JEDEC id bytes: 00, 00, 00 Trying to boot from MMC2 No misc partition spl: partition error Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x00080000 ... sha256(2493d19c1e...) + OK ## Checking uboot 0x00200000 ... sha256(01c15fcf12...) + OK ## Checking fdt 0x00308958 ... sha256(2867f75977...) + OK ## Checking atf-2 0xfe48d000 ... sha256(8ce3689111...) + OK ## Checking atf-3 0xfe490000 ... sha256(bc35c9ef85...) + OK Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00080000) Total: 334.426 ms INFO: Preloader serial: 0 NOTICE: BL31: v2.3():v2.3-679-geda1f5ce4:cl, fwver: v1.17 NOTICE: BL31: Built : 23:57:18, Dec 20 2023 INFO: rk_otp_init finish! INFO: ARM GICv2 driver initialized INFO: nonboot_cpus_off: clst_st=0xc0e, core_st=0xe1e0 boot_cpu=0 INFO: dfs].freq_mhz= 786MHz INFO: dfs DDR fsp_param[1].freq_mhz= 324MDR fsp_param[3].freq_mhz= 666MHz INFO: idle_st=0x0, pd_st=0xask: 1 INFO: rk_otp_init finish! INFO: RK3528 SoC (0x101) INFO: BL31: Initializing runtime services WARNING: No OPTE provided by BL2 boot loader, Booting device without OPTEE init Error initializing runtime service opteed_fast INFO: BL31: dress = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2017.09-armbian-2017.09-S3264-Pda90-H7573-V3999-Bb703-R448a (May 13 2025 - 12:27:23 +0300) Model: Rockchip RK3528 Evaluation Board MPIDR: 0x80000000 PreSerial: 0, raw, 0xff9f003.9 GiB Sysmem: init Relocation Offset: f9a58000 Relocation fdt: f79fa630 - f79fecd8 CR: M/C/I Using default environment DM: v2 no mmc device at slot 1 mmc@ffbf0000: 0, mmc@ffc30000: 1 (SD) Bootdev(atags): mmc 1 MMC1: Legacy, 52Mhz PartType: EFI No misc partition boot mode: None FIT: No boot partition Failed to load DTB, ret=-19 No valid DTB, ret=-22 Failed to get kernel dtb, ret=-22 Model: Rockchip RK3528 Evaluation Board MPIDR: 0x80000000 rockchip_set_serialno: could not find efuse/otp device CLK: (sync kernel. arm: enter 600000 KHz, init 1200000 KHz, kernel 0N/A) apll 600000 KHz gpll 1188000 KHz cpll 996000 KHz dpll 393000 KHz ppll 10KHz clk_100m 99600 KHz clk_150m 148500 KHz clk_200m 198KHz clk_400m 396000 KHz clk_500m 498000 KHz clk_600m 59clk_ppll_125m 125000 KHz No misc partition Net: No ethernet found. Hit key to stop autoboot('CTRL+C'): 0 Could not find misc partition ANDROID: reboot reason: "(none)" 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 FITFIT: No boot partition FIT: No fit blob FIT: No FIT image Unknown command 'bootrkp' - try 'help' switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot.scr 3906 bytes read in 23 ms (165 KiB/s) ## Executing script at 00c00000 Boot script loaded from mmc 1:1 176 bytes read in 18 ms (8.8 KiB/s) 6460789 bytes read in 563 ms (10.9 MiB/s) 28610568 bytes read in 2345 ms (11.6 MiB/s) 102238 bytes read in 289 ms (344.7 KiB/s) Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards. 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 Imagd) Data Size: 6460725 Bytes = 6.2 MiB Load Address: 0OK ## Flattened Device Tree blob at 0x08300000 Booting using the fdt blob at 0x08300000 reserving fdt memory region: addr=8300000 size=7f000 Using Device Tree in place at 0000000008300000, end 0000000008381fff WARNING: could not set reg FDT_ERR_BADOFFSET. ## reserved-memory: ramoops@110000: addr=110000 size=e0000 Adding bank: 0x00200000 - 0xfc000000 (size: 0xfbe00000) Total: 4660.229/5052.326 ms Starting kernel ... I think that MMC1 is sdcard, MMC2 is internal EMMC, so uboot is loaded from MMC1 sdcard (it has different version compared to standard boot), but the output is different compared to standard boot: Some suspicious data in log: MMC1: Legacy, 52Mhz PartType: EFI No misc partition FIT: No boot partition Failed to load DTB, ret=-19 No valid DTB, ret=-22 Failed to get kernel dtb, ret=-22 rockchip_set_serialno: could not find efuse/otp device Net: No ethernet found. I have full access to EMMC with all partitions and initial data to extract if needed. Will appreciate if someone could point me to custom armbian build steps for this board and suggest next steps. (https://gist.github.com/fensoft/1ff3ef81ab2bd9ed9364a564aa2cbcd5?permalink_comment_id=5576642#file-build-sh is what I tried and it does not work)

update: if disconnect TX from USB-UART adaptor - then there is infinite output that changes every microsecond with more strings: ESC[1;47rESC[46;1H[ 45.827723][ Tible6] [dhd-wlan0] w l_ext_iapsta_evefs.readdy=1 (/system/etcb/init/hw/init.uo sr not foun db^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Hnt : [S] Link UP with c8::ca:98^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1HESC[1;46rESC[46;1H ESC[1;47rESC[46;1H[ 45.827747][ T6] [dhd-wlan0] wconsole:/ $ ^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Hl_notify_connect_status : wl_bss_conn.127^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Hect_done succeeded with c8:ca:98 ^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1HESC[1;46rESC[46;1H ESC[1;47rESC[46;1H[ 45.843270][ T6] [dhd-wlan0] wl_notify_connect_sonso le:/ $ c^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Htatus : wl_bss_connect_done succeeded127|^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H with c8:7f:54:e0:ca:98 vndr_oui: 00-90-127|^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H4C 00-0C-43 00-0C-E7 ^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1HESC[1;46rESC[46;1H ESC[1;47rESC[46;1H[ 45.881840][ T165] type=1400 audit(1699712132.610:14conssole:/ $ ^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H4): avc: denied { open } for comm="FD655_Demo" path="/sys/class/fd655/fd65console:/ $ ^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H5_vpause_127|y^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Hflag" dev="s127fig=|^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Hysfs" ino=19647 sc[ 82.040633][ T386] read descriptors^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H[ 82.040698][ T386] read strings^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H[ 82.043097][ T1] init: processing action (sys.usb.config=adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1) f82.045159][ T1] init: Co mmand 'symlink /coESC[46;159HnESC[46;159HfESC[46;159HiESC[46;159HgESC[46;159H But still no active shell session

Hello, finally CH340G usb-uart has arrived - I have checked it performs data transfer on 1.5M speed in RX/TX loop normally. But when connecting to board - there is no output to console at all. Have tried RX/TX changing still no output, just regular start of android TV box. Please suggest does UART needs to be enabled in some screen/menu?

kernel_ramfs is located at /dev/block/mmcblk2p6 Have extracted with dd and copying through wifi adb. Interesting usb debugging is enabled in tvbox, but when connecting usb v3 cable to tvbox, host machine does not see the 'adb device', adb connection over wifi is ok. Has anybody used USB adb on this device?

Meanwhile, I have enabled ADB and debugging over wifi, and have connected to cli: 127|rk3528_box:/ $ uname -a Linux localhost 5.10.157-ab10 #319 SMP PREEMPT Sat Nov 11 21:49:28 CST 2023 aarch64 Toybox I think it is possible to copy firmware image from ADB session. If someone did/have instructions please point here.

yes, next week should arrive CH340G, will check with it

I'm using debian, no access to windows. with RX-TX locked adapter sends echos, but no data from box. will tryCH340G once it arrives, cause I saw in this post was same issue.

@pessimism want are the PINouts of this board? I see you have connected to it with UART. Can you please map RX/TX/GND to GREY/WHITE/BLACK based on you photo. I have tried CP2102 usb adaptor, looks like same case as you had - no transmission on 1.5Mb speed. Meanwhile ordered CH340G.

I thought there should be any console output to hdmi, ok will try with uart. By the way @fensoft are you using armbian on it? is it stable?

Hello I was able to build image (both debian and ubuntu) according to this instructions: https://gist.github.com/fensoft/1ff3ef81ab2bd9ed9364a564aa2cbcd5?permalink_comment_id=5576642#file-build-sh image is flashed to microsd card. However tvbox does not boot from sdcard - I see that it boots up regulary to android. Also I have found that in AV jacker on board there is button, so if hold it during boot - you are into Android recovery with options (reboot system/ reboot to bootloader/ fastboot /udpates ADB /updates from SD card/ factory reset /wipe / power off) The question is how to make TV box boot from sdcard? I was setting up armbian to orange pi - and it by default boots from sdcard. But with tv box according to posts and videos also should.... I'm trying to flash: Transpeed ATV Android 13 TV BOX RK3528 With Voice Assistant TV Apps Dual Wifi Quad Core Cortex A53 Support 8K 4K Video BT5.0 with 4G ram: https://www.aliexpress.com/item/1005007785484949.html