MattWestB

Armbian Noble V24.11.X base-files broken _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v24.8.4 for rk322x-box running Armbian Linux 6.6.63-current-rockchip Packages: Ubuntu stable (noble) Support: DIY (community maintained) Its up to date and the kernel and system is the 24.11.1 armbian-bsp-cli-rk322x-box-current is hold back then its depending on armbian-bsp-cli-rk322x-box-current : Depends: base-files (>= 24.11.1) but 24.8.4-13ubuntu10-noble is to be installed That is not existing for all 32 bits arm. apt list -a base-files Listing... Done base-files/noble,now 24.8.4-13ubuntu10-noble armhf [installed] base-files/noble 24.5.5-13ubuntu10-noble armhf base-files/noble 24.5.1-13ubuntu10-noble armhf base-files/noble 24.2.1-13ubuntu7-noble armhf base-files/noble-updates 13ubuntu10.1 armhf base-files/noble 13ubuntu10 armhf Technical its Ubuntu Noble V24.11.1 only the base-files is failing so the the welcome screen is writing wrong information and other programs that is reading it from the system

@wanton beis Your device is having eMMC and no nand flash. If flashing factors Android on the bootloader in the eMMC can only booting eMMC or old bootloaders from the sd-card like Multitool. If eMMC is empty the SOC is looking for one sc-card for bootloader and if you have written one new arbian image on it it shall finding it and booting OK and also can booting USB-flash from the sd-card (jump starting). Then writing Android or one old Linux on the eMMC it can only booinng from eMMC system or sd-card all with old system so need updating the bootloadre in the eMMC or erasing the eMMC for booting newer systems from the sd-card and gettig jump loading of USB-flash.

Thanks @haven for the replay then im not alone with this issue. Was looking on the PCB and its one Toshiba THGBM9G9T8KBAIG but cant finding datasheet of it only some summery on AIX and i think the PCB is using wrong voltage for the flash and after some mouths its being fired and cant being recovered.

2 of my "new" H96 Max RK3318 V11 with display was stop using the MMC (around one week between and first running Armbian and the other Android 11). The booting SD-Card i finding this in the log: [Wed Nov 27 16:08:54 2024] dwmmc_rockchip ff520000.mmc: IDMAC supports 32-bit address mode. [Wed Nov 27 16:08:54 2024] dwmmc_rockchip ff520000.mmc: Using internal DMA controller. [Wed Nov 27 16:08:54 2024] dwmmc_rockchip ff520000.mmc: Version ID is 270a [Wed Nov 27 16:08:54 2024] dwmmc_rockchip ff520000.mmc: DW MMC controller at irq 37,32 bit host data width,256 deep fifo [Wed Nov 27 16:08:54 2024] mmc_host mmc2: card is non-removable. [Wed Nov 27 16:08:54 2024] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [Wed Nov 27 16:08:54 2024] mmc2: card has unknown MMCA version 6 [Wed Nov 27 16:08:54 2024] mmc2: error -22 whilst initialising MMC card [Wed Nov 27 16:08:54 2024] mmc_host mmc2: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) [Wed Nov 27 16:08:54 2024] mmc2: card has unknown MMCA version 6 [Wed Nov 27 16:08:54 2024] mmc2: error -22 whilst initialising MMC card [Wed Nov 27 16:08:54 2024] mmc_host mmc2: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0) [Wed Nov 27 16:08:54 2024] mmc2: card has unknown MMCA version 6 [Wed Nov 27 16:08:54 2024] mmc2: error -22 whilst initialising MMC card [Wed Nov 27 16:08:54 2024] mmc_host mmc2: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0) [Wed Nov 27 16:08:54 2024] mmc2: card has unknown MMCA version 6 [Wed Nov 27 16:08:54 2024] mmc2: error -22 whilst initialising MMC card [Wed Nov 27 16:08:55 2024] mmc2: Failed to initialize a non-removable card Was looking for the android firmware and using factory tool and the device is going in maskrom mode then pressing the "pin button" and connecting it to the PC. Flashing the Android firmware and its still showing Maskrom. Re connecting it and its not starting. Putting in Armbian SD-Card and its booting Armbian OK. Doing the same test with the second box and the same result. Conclusion: MMCA Version 6 = hard bricked MMC. So now need baying some A2 SD-Card for running Armbian and no Android TV with IPTV. If some have experience of recover not working MMC pleas share it and you thinking.

@ExUser 44 From the first post download and flash multitool on one SD-Card (USB is not supported by factory android bootloader) and put it in the box and power on. Make one backup of the eMMCand then shutdown the box and copy the backup to one safe place. Download one Armbian from links in the first post (stable Ubuntu or debian server or desktop). Copy the tar file to the (multitool) sd-card image folder and puting it in the box and power it up. The safest and brutal is erase eMMC and write the Arbian image to ti but can being one brick. The more safe is only erase the eMMC then the SOC is not finding boot-loader on it its trying booting from sc-card . If only erasing eMMC you can burning Armbian on one SD-Card and the system shall booting from it and cant being bricked. Then getting it working try writing the eMMC with multitol and hope its working well (then you also getting USB boot support).

Thanks for great work @Jean-Francois Lessard !!! I think the trigger was not loaded OK with my manual install. My 2 boxes is for the moment HA in production and the second one is updated Android V11 (from V10) then it was having problems running large IPTV (corrupting the files system) that looks working OK now. Then i have getting all stable and also can getting HyperHDR also running (USB problems . . . with V1.4 hardware but one other box looks doing better but not the USB3) i can doing one rockade and doing more testing.

@E O Bernardini From the first page opening post is https://users.armbian.com/jock/rk322x/armbian/stable/ you find the last Jocks builds.

@Parth Yatin Temkar First burn the multi tool on on SD-Card and do not mixing with it. Put the SC-Card in the box and power it on. Look if the LED is start blinking slowly = it have starting. Very likely you is not getting any video then the board need setting for getting it working OK. Then it running its expanding the partition and then starting multi tool script. If you is getting video do one backup of the flash !!! And use the menu power down (the flash can being locked in write mode if hard power it off the writing). Put the SD-Card in the PC and copy the backup of the flash to it and also copy the Arbian image to the image folder (don need unpacking it). If not have video you need using SSH for connecting to the box thru Ethernet (IP from your router if you is not knowing it) or using the local console (it not populated on the PCB but normally working). Now is the tricky part then need erasing the flash so the old mini bootloader is away from the flash then the SOC is looking for it on the SD-Card and you can booting easier. If being brave do one erase flash from multi tool or with the RK-tools you have using and its safe as long the old is in the flash or the flash is empty. If going well you can booting SD-card with multi tool or Armbian now and installing one Armbian image from sd-card or booting Armbian form SD-Card. If booting Armbian its possible updating the flash bootloader from armbian-config program but its depends of the version if the image if its easy or not. Best is trying Armbian on SD-Card so knowing how it working and then flashing the flash. If messing the mini boot loader you must shutting the test points under the SOC on the PCB for getting it booting multi tool and do one flash erase. Photos is posted for some years ago with consolle and the test points for MASK-ROM and its prity easy to do on the box. PS: Your box have 1G RAM and 8G Flash as normal for this boxes.

For your version of RK3318_V1.4 (without display) its needs the configure file as you was doing OK. For other users its the command "ln -s /usr/lib/firmware/brcm/BCM43342.hcd /usr/lib/firmware/brcm/BCM.hcd" And its stop using different BT MAC-addresses after every reboot so can being used with BT devices.

Was installing the original Android backup and installing SSH server on it and then one "tar -zcvf device.tar.gz /sys/firmware/devicetree/base/" for dumping the device tree and attaching it her if you need it but i think its the same as your box.device.tar.gz

Was getting the service working but i cant saying way it was not working but some problems with the files the system cant accessing. Kernel still have some problem then loading the module but looks working as aspected. The time its ticking !!!!

Have testing more and all display elements is working OK. But the kernel is having problem then loading the module: [Wed Oct 9 09:18:18 2024] ------------[ cut here ]------------ [Wed Oct 9 09:18:18 2024] WARNING: CPU: 0 PID: 442 at kernel/workqueue.c:1788 __queue_work+0x480/0x578 [Wed Oct 9 09:18:18 2024] Modules linked in: ch341(+) brcmutil v4l2_vp9 videobuf2_dma_contig tm16xx(+) v4l2_h264 usbserial cfg80211 ledtrig_netdev snd_soc_spdif_tx videobuf2_dma_sg hci_uart v4l2_mem2mem btqca videobuf2_memops btrtl btintel gpio_ir_recv dw_hdmi_i2s_audio videobuf2_v4l2 rc_core videodev btbcm bluetooth lima dw_hdmi_cec snd_soc_rockchip_spdif videobuf2_common snd_soc_rk3328 snd_soc_rockchip_i2s rfkill snd_soc_simple_card snd_soc_simple_card_utils gpu_sched mc drm_shmem_helper rk_crypto snd_soc_core rng_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd soundcore cpufreq_dt zram binfmt_misc sch_fq_codel dm_mod nfnetlink ip_tables x_tables autofs4 dwmac_rk stmmac_platform stmmac pcs_xpcs gpio_syscon adc_keys [Wed Oct 9 09:18:18 2024] CPU: 0 PID: 442 Comm: (udev-worker) Not tainted 6.6.54-current-rockchip64 #1 [Wed Oct 9 09:18:18 2024] Hardware name: Rockchip RK3318 BOX (DT) [Wed Oct 9 09:18:18 2024] pstate: a00000c5 (NzCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [Wed Oct 9 09:18:18 2024] pc : __queue_work+0x480/0x578 [Wed Oct 9 09:18:18 2024] lr : __queue_work+0x1e4/0x578 [Wed Oct 9 09:18:18 2024] sp : ffff80008166b540 [Wed Oct 9 09:18:18 2024] x29: ffff80008166b540 x28: ffff199e48f132b0 x27: 0000000000000000 [Wed Oct 9 09:18:18 2024] x26: ffffbc7084518008 x25: ffff199e4041e000 x24: ffffbc708487dcb8 [Wed Oct 9 09:18:18 2024] x23: ffff199e48f132b8 x22: 0000000000000011 x21: ffff199e40408400 [Wed Oct 9 09:18:18 2024] x20: 0000000000000100 x19: ffff199f3e72ee40 x18: ffff199f3e7af04c [Wed Oct 9 09:18:18 2024] x17: ffff5d2eba203000 x16: ffff800080000000 x15: 00000000000001ef [Wed Oct 9 09:18:18 2024] x14: 0000000000000000 x13: ffffbc70841cc198 x12: ffffbc7084879b68 [Wed Oct 9 09:18:18 2024] x11: 0000000000000040 x10: ffffbc7084897470 x9 : ffffbc7084897468 [Wed Oct 9 09:18:18 2024] x8 : ffff199e40800028 x7 : 0000000000000000 x6 : 0000000000000000 [Wed Oct 9 09:18:18 2024] x5 : ffff199e40800000 x4 : 0000000000000000 x3 : 0000000000000001 [Wed Oct 9 09:18:18 2024] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000 [Wed Oct 9 09:18:18 2024] Call trace: [Wed Oct 9 09:18:18 2024] __queue_work+0x480/0x578 [Wed Oct 9 09:18:18 2024] queue_work_on+0x68/0x84 [Wed Oct 9 09:18:18 2024] tm16xx_led_set+0x60/0x6c [tm16xx] [Wed Oct 9 09:18:18 2024] led_set_brightness+0x90/0xe0 [Wed Oct 9 09:18:18 2024] led_trigger_set+0x268/0x274 [Wed Oct 9 09:18:18 2024] led_trigger_set_default+0xa4/0xcc [Wed Oct 9 09:18:18 2024] led_classdev_register_ext+0x284/0x3a0 [Wed Oct 9 09:18:18 2024] devm_led_classdev_register_ext+0x58/0xb0 [Wed Oct 9 09:18:18 2024] tm16xx_probe+0x390/0x6e0 [tm16xx] [Wed Oct 9 09:18:18 2024] tm16xx_i2c_probe+0x5c/0x80 [tm16xx] [Wed Oct 9 09:18:18 2024] i2c_device_probe+0x104/0x2e8 [Wed Oct 9 09:18:18 2024] really_probe+0x184/0x3c8 [Wed Oct 9 09:18:18 2024] __driver_probe_device+0x7c/0x16c [Wed Oct 9 09:18:18 2024] driver_probe_device+0x3c/0x110 [Wed Oct 9 09:18:18 2024] __driver_attach+0xf4/0x1fc [Wed Oct 9 09:18:18 2024] bus_for_each_dev+0x74/0xd4 [Wed Oct 9 09:18:18 2024] driver_attach+0x24/0x30 [Wed Oct 9 09:18:18 2024] bus_add_driver+0x110/0x234 [Wed Oct 9 09:18:18 2024] driver_register+0x60/0x128 [Wed Oct 9 09:18:18 2024] i2c_register_driver+0x48/0xec [Wed Oct 9 09:18:18 2024] tm16xx_init+0x5c/0x1000 [tm16xx] [Wed Oct 9 09:18:18 2024] do_one_initcall+0x44/0x2c4 [Wed Oct 9 09:18:18 2024] do_init_module+0x58/0x1e8 [Wed Oct 9 09:18:18 2024] load_module+0x1c94/0x1ec4 [Wed Oct 9 09:18:18 2024] init_module_from_file+0x84/0xc4 [Wed Oct 9 09:18:18 2024] __arm64_sys_finit_module+0x1f4/0x2f0 [Wed Oct 9 09:18:18 2024] invoke_syscall+0x48/0x118 [Wed Oct 9 09:18:18 2024] el0_svc_common.constprop.0+0xc8/0xe8 [Wed Oct 9 09:18:18 2024] do_el0_svc+0x20/0x2c [Wed Oct 9 09:18:18 2024] el0_svc+0x40/0xf4 [Wed Oct 9 09:18:18 2024] el0t_64_sync_handler+0x13c/0x158 [Wed Oct 9 09:18:18 2024] el0t_64_sync+0x190/0x194 [Wed Oct 9 09:18:18 2024] ---[ end trace 0000000000000000 ]--- And the service is not loading OK then the "ExecStart=/usr/sbin/display-service" is pointing to "/sbin/display-service". Fixing it but the service cant starting then its missing some files that very likely is handles from the module that is not working OK. Good thing is that pause is used and activity LED and WiFi and Eth looks working OK also USB activity is working (Zigbee stick). If getting the service working then it shall showing the time on the display if not configure somthing else. Some hints getting the module loading OK and getting the service working OK ?

@mkultra Looks like the command package is not installer as standard in ubuntu: # route Command 'route' not found, but can be installed with: apt install net-tools But install net-tools it shall working OK (I hope)

Thanks @jock and the LED cofig was from memory and form the very old install and it was running on the default one. Something is crashing the kernel then loading modules but i shall looking if its being OK then not loading the new drive. And in the e log: [Tue Oct 8 20:04:53 2024] tm16xx_led_set+0x60/0x6c [tm16xx] [Tue Oct 8 20:04:53 2024] tm16xx_probe+0x390/0x6e0 [tm16xx] [Tue Oct 8 20:04:53 2024] tm16xx_i2c_probe+0x5c/0x80 [tm16xx] [Tue Oct 8 20:04:53 2024] tm16xx_init+0x5c/0x1000 [tm16xx] [Tue Oct 8 20:04:53 2024] tm16xx 4-0024: Display initialized successfully So its loaded OK. But cant testing it by instruction then the display-utils is not installed and i cant finding how to do that. The service call is also not working (/sbin/display-service dont exist) but writing to sys-class is working OK. cat /sys/class/leds/display/digits 4 3 2 1 cat /sys/class/leds/display/segments 0 1 2 3 4 5 6 echo "boot" > /sys/class/leds/display/value Is showing "BOOT". Do you have some other ways testing the e display and setting up service call ? Thanks for great work done and continuing doing it well !!! Edit: Was looking in the Makefile and was doing the "install: module module-install service-install" part manually and now its working !!! I think we need one package for installing it in the system for normal users and adding boot and WiFi / Eth indicator from OS.

I have 2 H69Max branded boxes with 4G RAM and 64G eMMC. PCB is only labeled RK3318_V1.4 with fd6551 LED-driver chip. Using LED conf 7 and working great WiFi and BT AP6330 looks working OK but using Eth for network access. Only USB is worse then other RK3X boxes if using little bandwidth on them. I have one backup of original Android but its very large and must look if i can extracting the original DTS files from it.