All Activity

So far no dice with Armbian. I am trying my luck with the Radxa official image and will report how that goes eventually. Meanwhile feel free to offer ideas or procedures i could tackle

If you want to understand what should be happening under a normal installation: Installing "multiboot" (i.e. pressing the hidden reset button while powering the device) runs the script aml_autoscript That script sets some uboot environment variables that are used by subsequent boots The boot process for these boxes is to use the original android uboot to intiialize the device and then hand off the boot process to the u-boot.ext from armbian. This is done in the script s905_autoscript (or emmc_autoscript). Which then essentially just runs (for emmc): if fatload mmc 1 0x1000000 u-boot.ext; then go 0x1000000; fi; (or "mmc 0" for SD card). The chainloaded u-boot then boots via the information in the extlinux/extlinux.conf file.

Current Armbian uses extlinux to load, not uboot scripts. I can't help you unless you are willing to follow my suggestions, which you seem to not want to do.

log into android and poweroff via any "power menu" apk inside android put you armbian flashed sd (try balena etcher) and use half of ear cleaning cotton bud's stick to put and press in AV/audio port ; keep pressing then put dc power - until anything comes in hdmi out-you can try 3sec 8sec method; put bud and press count 3 put dc in while pressing count upto 8 then let go

Thank you for the update, good to hear there is possible to run Linux on the box. In other hand, little bit is surprising, I try Nanopi M4 image and many other images, but non of work for me. Far as I know Rockchip have fixed boot order (emmc -> sd cadr ... ). Do you have a working Android on emmc and Armbian on sd card? On the weekend I will try also again the SD card boot. To answer your questions: I did not use any DTB at yet I only try rkbin boot loaders which not need to build. I was also able to extract the Android 11 Image there was model name "Giada JHS558" entered, I assume you have older Android version where the vendor use the Excavator Board as basis for the device tree.

Well, i have unbound the a24 driver by now: echo -n "6-0050" > /sys/bus/i2c/drivers/at24/unbind apparently it was an Radxa specific eeprom he had hanged on to: # i2cget 6 0x50 0x00 i | xxd -r -p WARNING! This program can confuse your I2C bus, cause data loss and worse! I will read from device file /dev/i2c-6, chip address 0x50, data address 0x00, 32 bytes using read I2C block data. Continue? [Y/n] RADXX but the neighbor is a mistery: i2cget 6 0x51 0x00 i | xxd -r -p WARNING! This program can confuse your I2C bus, cause data loss and worse! I will read from device file /dev/i2c-6, chip address 0x51, data address 0x00, 32 bytes using read I2C block data. Continue? [Y/n] R-Po����������������������������

this is the u-boot command i gave ,previosly loaded armbian ,kernel 5.9 , same command give ,ftdaddr null ,but os loads , for kernel version 6.18 doesnt load , it abort booti ${loadaddr} - ${dtb_mem_addr} this is the error message im getting for booti ${loadaddr} - ${dtb_mem_addr}, other commands works perfectly 42334720 bytes read in 2967 ms (13.6 MiB/s) reading dtb/amlogic/meson-gxl-s805x-p241.dtb 40339 bytes read in 58 ms (678.7 KiB/s) [rsvmem] get fdtaddr NULL! rsvmem - reserve memory Usage: rsvmem check - check reserved memory rsvmem dump - dump reserved memory rsvmem check failed "Synchronous Abort" handler, esr 0x96000210

According to i2cdetect the "UU" means the eeprom is being accessed (used) by something, and indeed after checking dmesg i've found this: [ 8.135029] at24 6-0050: Looking up vcc-supply property in node /i2c@2ac90000/at24c16@50 failed The at24 is again a built in module and i am not sure how i can prevent it from accessing the 0x50 on i2c 6?

What do You know! # i2cdetect -l i2c-1 i2c rk3x-i2c I2C adapter i2c-2 i2c rk3x-i2c I2C adapter i2c-3 i2c rk3x-i2c I2C adapter i2c-6 i2c rk3x-i2c I2C adapter i2c-10 i2c ddc it was always there, just missed i2c -tools 😁 next: # i2cdetect -F 6 Functionalities implemented by /dev/i2c-6: I2C yes SMBus Quick Command yes SMBus Send Byte yes SMBus Receive Byte yes SMBus Write Byte yes SMBus Read Byte yes SMBus Write Word yes SMBus Read Word yes SMBus Process Call yes SMBus Block Write yes SMBus Block Read no SMBus Block Process Call no SMBus PEC yes I2C Block Write yes I2C Block Read yes SMBus Host Notify no 10-bit addressing no Target mode no And finally: # i2cdetect -y 6 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: UU UU UU UU UU UU UU UU -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- So we seem to have something there (at address 0x50). What would be the next steps? read out the eerpom? Also, why does the OS not take care of this automatically? How come Raspbian OS does?

I just tried to enable the i2c6 (/boot/dtb/rockchip/overlay/rk3576-i2c6-m0.dtbo) overlay by armbian-config but as i try to enter the overlay utility i get thrown out to the CLI with "Invalid overlay_prefix rk35xx" What gives?

Yes it errors because your uboot environment is screwed up by everything you have previously done. That is why I said you need to reinstall an original android firmware to set things back to a clean state before proceeding.

Hi, the hardware in question: PCIe_TO_2-CH_SATA_HAT+ In expectation for the Rock 4D forum to arrive I am posting my issue here: The Rock 4D works and all is well The two SATA drives work over USB to SATA adapters - that is not ideal in the long term IMHO The HAT just arrived and i have no doubt in my mind that it can be defective in any way - i assume it is 100% operational. But when i connect it and plug the power in the Rock 4D boots, everything else works as usual, but the HAT just sits there without any signal. My questions: 1. How do i query the eeprom via the pins 27 & 28 (ID_SD & ID_SC), do i just enable the i2c_6 overlay? 2. What then? I queried the ahci module with: `modinfo ahci` but it is both a built in and i suspect it does not support my device anyway? Looking forward to try help get this nice board supported on Armbian for other FPC equipped devices.

Over the past year, Collabora has pushed mainline GStreamer toward a first-class media and Machine Learning platform, with new inference backends, extended metadata/tensor handling, and production-ready analytics building blocks. View the full article

With its latest release, GStreamer adds native support for AI inference engines including ONNX Runtime, LiteRT, and Burn, along with tensor decoders for YOLO, face detection, tracking, and more. View the full article

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 ed9827920 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-4-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-4/wine-proton-10.0-4-amd64-wow64.tar.xz) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v1.6.1 ~40fps@720p (low settings) box64 environment variables: Dead Space

Cheers, will do!

tried to boot this image Armbian_community_26.2.0-trunk.385_Aml-s9xx-box_trixie_current_6.18.8_minimal it gives this error scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... init_part() 282: PART_TYPE_DOS 1 Storage Device(s) found reading zImage ** Unable to read file zImage ** reading dtb/amlogic/meson-gxl-s805x-p241.dtb 26728 bytes read in 57 ms (457 KiB/s) [rsvmem] get fdtaddr NULL! rsvmem - reserve memory Usage: rsvmem check - check reserved memory rsvmem dump - dump reserved memory rsvmem check failed Bad Linux ARM64 Image magic! gxl_p241_v1#

Given where you are, my only suggestion is to restore the box to a clean android firmware (so the uboot environment is restored to a clean state). Then restart with a current build (don't use the 6 year old build that you found somewhere). The two versions aren't compatible. Then get things running cleanly from SD card first, and then if you still want move the install to emmc.

Please use a build that isn't 7 years old. https://www.armbian.com/amlogic-s9xx-tv-box Read the FAQ and the install instructions linked there

moving to amlogic tv box forum

here is the full log dtb/amlogic/meson-gxl-s805x-p241.dtb copied -u-boot-s905x-s912 u-boot.ext then renamed it as u-boot.ext manually booted from sd card , then installed to emmc sudo /root/install-aml.sh previously i could save bootcmd as env , after this ,i couldnot save env ,from u-boot now it gives this error gxl_p241_v1#saveenv Saving Environment to aml-storage... _find_partition_by_name()-198: do not find match in table env get partition info failed !! gxl_p241_v1## This saves all environment variables to eMMC/SD gxl_p241_v1#saveenv Saving Environment to aml-storage... _find_partition_by_name()-198: do not find match in table env get partition info failed !! ------------------------------------------------------------------------------------------------------------------------------------------------------------ is there any way to manually erase the default vendor , u-boot , and install armbian one ? Armbian_20.10_Arm-64_focal_current_5.9.0 this is the image i succesfully booted , -------------------------------------------------------------------------------------------------------- i tried to boot this image Armbian_community_26.2.0-trunk.385_Aml-s9xx-box_trixie_current_6.18.8_minimal it gives this error scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... init_part() 282: PART_TYPE_DOS 1 Storage Device(s) found reading zImage ** Unable to read file zImage ** reading dtb/amlogic/meson-gxl-s805x-p241.dtb 26728 bytes read in 57 ms (457 KiB/s) [rsvmem] get fdtaddr NULL! rsvmem - reserve memory Usage: rsvmem check - check reserved memory rsvmem dump - dump reserved memory rsvmem check failed Bad Linux ARM64 Image magic! gxl_p241_v1# --------------------------------------------------------------------------------------------------------------------------------------------------- vendor u-boot ,bootcmd u-boot default bootcmd gxl_p241_v1#printenv bootcmd bootcmd=run storeboot gxl_p241_v1#printenv storeboot storeboot=get_system_as_root_mode;echo system_mode: ${system_mode};if test ${system_mode} = 1; then setenv fs_type ro rootwait skip_initramfs;run storeargs;fi;get_valid_slot;get_avb_mode;echo active_slot: ${active_slot};if test ${active_slot} != normal; then setenv bootargs ${bootargs} androidboot.slot_suffix=${active_slot};fi;if test ${avb2} = 0; then if test ${active_slot} = _a; then setenv bootargs ${bootargs} root=/dev/mmcblk0p23;else if test ${active_slot} = _b; then setenv bootargs ${bootargs} root=/dev/mmcblk0p24;fi;fi;fi;if imgread kernel ${boot_part} ${loadaddr}; then bootm ${loadaddr}; fi;run update ------------------------------------------------------------------------------------------------------------------------------------------------------------ LOG After i installed armbin (Armbian_20.10_Arm-64_focal_current_5.9.0)to emmc , reboot gives this error [ OK ] Reached target Reboot. [ 650.054096] watchdog: watchdog0: watchdog did not stop! [ 650.541411] reboot: Restarting system bl31 reboot reason: 0xd bl31 reboot reason: 0x0 system cmd 1. GXL:BL1:9ac50e:bb16dc;FEAT:BFFC39BE:100;POC:3;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;1.0;1.0;CHK:0; TE: 241336 BL2 Built : 10:47:34, Jan 14 2019. gxl g152d217 - guotai.shen@droid11-sz set vcck to 1120 mv set vddee to 1000 mv Board ID = 7 CPU clk: 984MHz DDR enable rdbi DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0 16bit @ 912MHz bist_test rank: 0 1b 00 37 27 0f 3f 1c 01 38 2b 11 45 27 27 27 27 27 27 27 27 27 27 27 27 693 - PASS Rank0: 1024MB-2T-13 AddrBus test pass! Set ddr ssc: ppm1000- eMMC boot @ 1 sw8 s emmc switch 3 ok BL2: rpmb counter: 0x00000020 emmc switch 1 ok OTP_ARB=00000001 Load FIP HDR from eMMC, src: 0x0000c200, des: 0x01700000, size: 0x00004000, part: 1 Load BL3x from eMMC, src: 0x00010200, des: 0x01704000, size: 0x000f4000, part: 1 NOTICE: BL3-1: v1.0(release):3bc3888 NOTICE: BL3-1: Built : 11:28:51, May 10 2019 [BL31]: GXL CPU setup! NOTICE: BL3-1: GXL secure boot! NOTICE: BL3-1: BL33 decompress pass mpu_config_enable:system pre init ok dmc sec lock MVN_1=0x01010100 MVN_2=0x01010000 [Image: gxl_v1.1.3375-8f9c8a7 2019-01-24 10:45:03 guotai.shen@droid11-sz] OPS=0x34 21 0d 34 00 25 ae dc 97 5b 00 83 fe 04 b3 53 02 [0.856523 Inits done] secure task start! high task start! low task start! INFO: BL3-2: ATOS-V2.4-238-g14a47cb #1 Tue Dec 3 07:25:46 UTC 2019 arm INFO: BL3-2: Chip: GXL Rev: D (21:D - 30:2) INFO: BL3-2: crypto engine DMA INFO: BL3-2: secure time TEE INFO: BL3-2: CONFIG_DEVICE_SECURE 0xb200000e U-Boot 2015.01-g186a540 (Mar 14 2020 - 17:11:46) DRAM: 1 GiB Relocation Offset is: 36e86000 register usb cfg[0][1] = 0000000037f51910 [CANVAS]canvas init boot_device_flag : 1 Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc. init bus_cycle=6, bus_timing=7, system=5.0ns reset failed get_chip_type and ret:fffffffe get_chip_type and ret:fffffffe chip detect failed and ret:fffffffe nandphy_init failed and ret=0xfffffff1 MMC: aml_priv->desc_buf = 0x0000000033e866b0 aml_priv->desc_buf = 0x0000000033e889f0 SDIO Port B: 0, SDIO Port 😄 1 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 40000000 [mmc_startup] mmc refix success init_part() 282: PART_TYPE_DOS [mmc_init] mmc init success check_valid_dts() 248: Decrypt dtb: Sig Check -2 get_partition_from_dts() 71: ret -249 get_partition_from_dts() 74: ret -249 get_ptbl_from_dtb()-269: get partition table from dts faild mmc_device_init()-1251: get partition table from dtb failed get_ptbl_rsv()-491: magic faild MPT, ▒׋ mmc_device_init()-1278: dtb&rsv are not exist, no LPT source _find_partition_by_name()-198: do not find match in table env get partition info failed !! Using default environment In: serial Out: serial Err: serial reboot_mode=cold_boot itest - return true/false on integer compare Usage: itest [.b, .w, .l, .s] [*]value1 <op> [*]value2 [store]To run cmd[emmc dtb_read 0x1000000 0x40000] _verify_dtb_checksum()-2755: calc 79d92d6, store f26b0ab5 update_dtb_info()-2863: cpy 1 is not valid _verify_dtb_checksum()-2755: calc ab3aca1f, store f6004a13 update_dtb_info()-2863: cpy 0 is not valid dtb_read()-2972: total valid 0 emmc - EMMC sub system Usage: emmc dtb_read addr size emmc dtb_write addr size emmc erase dtb emmc erase key emmc fastboot_read addr size emmc fastboot_write addr size [store]decrypt dtb: Sig Check -2 vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters vpu: clk_level = 2 vpu: set clk: 200000000Hz, readback: 200000000Hz(0x501) vpu: vpu_clk_gate_init_off finish vpp: vpp_init hpd_state=0 vpp: vpp_matrix_update: 2 cvbs performance type = 6, table = 0 cvbs_config_hdmipll_gxl cvbs_set_vid2_clk Net: dwmac.c9410000[KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 MACADDR:02:5b:97:dc:ae:25(from chipid) Warning: dwmac.c9410000 MAC addresses don't match: Address in SROM is 4a:f1:62:3d:0c:33 Address in environment is 02:5b:97:dc:ae:25 CONFIG_AVB2: avb2 Start read misc partition datas! _find_partition_by_name()-198: do not find match in table misc Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read misc 0x33e75090 0x0 0x820] failed to store read misc. info->magic = info->version_major = 0 info->version_minor = 0 info->slots[0].priority = 0 info->slots[0].tries_remaining = 0 info->slots[0].successful_boot = 0 info->slots[1].priority = 0 info->slots[1].tries_remaining = 0 info->slots[1].successful_boot = 0 info->crc32 = 0 Magic is incorrect. boot-info is invalid. Resetting. save boot-info info->magic = info->version_major = 1 info->version_minor = 0 info->slots[0].priority = 15 info->slots[0].tries_remaining = 7 info->slots[0].successful_boot = 0 info->slots[1].priority = 14 info->slots[1].tries_remaining = 7 info->slots[1].successful_boot = 0 info->crc32 = -1075449479 _find_partition_by_name()-198: do not find match in table misc Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_write_ops,L110:cmd [store write misc 0x33e75090 0x0 0x820] failed active slot = 0 wipe_data=successful wipe_cache=successful upgrade_step=0 reboot_mode:::: cold_boot [KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]fb_addr for logo: 0x3d800000 [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]fb_addr for logo: 0x3d800000 [OSD]VPP_OFIFO_SIZE:0xfff00fff [CANVAS]addr=0x3d800000 width=3840, height=2160 _find_partition_by_name()-198: do not find match in table logo Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read logo 0x1080000 0x0 0x2000] Err imgread(L523):Fail to read 0x2000B from part[logo] at offset 0 There is no valid bmp file at the given address [OSD]osd_hw.free_dst_data: 0,719,0,575 [KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 gpio: pin GPIOAO_2 (gpio 102) value is 1 Command: bcb uboot-command Start read misc partition datas! _find_partition_by_name()-198: do not find match in table misc Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read misc 0x33e75080 0x0 0x440] failed to store read misc. bcb - bcb Usage: bcb This command will run some commands which saved in misc partition by mark to decide whether execute command! Command format: bcb bcb_mark Example: /dev/block/misc partiton is saved some contents: uboot-command N/A setenv aa 11;setenv bb 22;setenv cc 33;saveenv; So you can execute command: bcb uboot-command [KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 (Re)start USB... USB0: USB3.0 XHCI init start Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... init_part() 282: PART_TYPE_DOS 1 Storage Device(s) found fail in cmd [fatsize usb 0 factory_update_param.aml], rcode 1 File factory_update_param.aml not exist in Upan?? get upgrade version failed Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 CONFIG_SYSTEM_AS_ROOT: systemroot system_mode: 1 [KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 Start read misc partition datas! _find_partition_by_name()-198: do not find match in table misc Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read misc 0x33e75090 0x0 0x820] failed to store read misc. info->magic = info->version_major = 0

Hi, welcome. Syncing forums and tags with supported boards is (still) a manual job and from time to time I either cannot keep up or miss things. Like in this case. I'll fix this later and then move appropriately. Until then feel free to state your question in "Beginners" using the "other" tag. Cheers

Hello to everyone. Being new around here I figured to drop one message here first... So, i have this Radxa Rock 4D SBC and i am quite impressed with it Me being me and SBC being what it is, yada... yada, i now have this hat+ from Waveshare - it is an dual SATA to PCIe adapter. It was designed for the Raspberry pi 5 obviously but Radxa has since started putting those FPC connectors on and i really would appreciate a 24/7 NAS with a SBC footprint... Long story short, it does not work out of the box - i have no doubt the product is okay it's just the HAT fails to initiate the OS and register. It reportedly has an eprom with data on it but my guess is it has to have a dtb overlay active and my rock 4D lacks anything in that regard (a "sata" in the overlay name) My issues? 1. Where is the Rock 4D forum or where do i post this issue best to?

I tried Armbian_26.2.1_Nanopim4v2_trixie_current_6.18.8_minimal.img.xz, wrote it on TF card and it booted into Linux without any changes.

device x92 android tv, amlogic s912, armbian file: Armbian_5.84_Aml-s905_Debian_stretch_default_5.1.0-rc1_20190507.img