Search the Community

Hi afiftyp, Thanks for the patches. I added them to my build. Unfortunately, bluetooth doesn't work for me. [ 7.691181] Bluetooth: Core ver 2.22 [ 7.691282] NET: Registered PF_BLUETOOTH protocol family [ 7.691287] Bluetooth: HCI device and connection manager initialized [ 7.691306] Bluetooth: HCI socket layer initialized [ 7.691315] Bluetooth: L2CAP socket layer initialized [ 7.691331] Bluetooth: SCO socket layer initialized . . . [ 7.873425] Bluetooth: HCI UART driver ver 2.3 [ 7.873455] Bluetooth: HCI UART protocol H4 registered [ 7.873460] Bluetooth: HCI UART protocol BCSP registered [ 7.873560] Bluetooth: HCI UART protocol LL registered [ 7.873565] Bluetooth: HCI UART protocol ATH3K registered [ 7.873603] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 7.873789] Bluetooth: HCI UART protocol Intel registered [ 7.873882] Bluetooth: HCI UART protocol Broadcom registered [ 7.873914] Bluetooth: HCI UART protocol QCA registered [ 7.873919] Bluetooth: HCI UART protocol AG6XX registered [ 7.873949] Bluetooth: HCI UART protocol Marvell registered . . . [ 10.147991] Bluetooth: hci1: command 0x0c03 tx timeout [ 10.148042] Bluetooth: hci1: BCM: Reset failed (-110)

First off, (and you likely know this already), Armbian doesn't support userspace upgrades to newer distributions. (But they usually work in my experience). Second, you are running on a board that Armbian doesn't support. It is a community supported board, which means that no Armbian resources are put in this board, it is soley maintained (or not maintained) by volunteers in the community. On to your issue. You are going to need to capture the boot log to see where it is failing to boot. You need to hook up a usb uart connector to your board to capture the boot output. I would also suggest trying to fresh install on your board to make sure that your target release actually works on your board at all (don't want to spend a lot of time debugging an upgrade issue, if it isn't an upgrade issue, and is just an issue in the current release).

Hello Armbian Team, i have the wish for the integration of - GPIO Support for RockPi 5b to the Edge Kerne - dtb's which are aviable for Kernel 5.10.160 mostly importend for me are the UARTS ( if tryed to compile the DTS files form 5.10.160 for the 6.8.2 .. ends after sending some to the UART with a Kernel segfault 😞 ) Thanks a lot for the good Work 🙂 René

@astrosky as I already told you, there are no spare buses to tinker with on tvboxes. The second uart (ttyS0 usually) you found perhaps is in use for communications with the bluetooth chip which happens via plain serial data. If your board has no bluetooth, then you may use it for your business, otherwise you will get garbage there too. Still an SBC is far better for these tasks, you easily get three or four UARTs on the pin headers you know what purposes are for.

If you want to dig deeper into this, you will need to find the uart pins on the board, hookup USB uart connector and capture the boot messages to see what is actually happening when booting. Since I don't have this board nor know of anyone that has tried running Armbian on that board.

@jock I knew something was off.....that's why I was seeing Random characters output when I echo ..thanks for telling me that and it also explains why I get permission denied sometimes. ...guess I still need to make it where it's a virgin uart with no influence on debug too! I thought it was just a console control. Yeah this took extra steps but it frees up a USB port on the box itself for keyboard and mouse with out using a hub and it sorta copies a pi now and I had all this laying around anyways so. Update:1 Ok successfully fixed the issue, disabled all access to that uart part temporarily. Was able to successfully communicate to the Arduino through nanpy. No more permission issues. This is super cool. Now the Arduino works like an extension to the TV box. The processing power of the TV box is way better than the Arduinos so this opens up a bit of a cool niche use case. I'll call it THE ARMBIAN PI.. Still dont have wifi though. I ran the config and such but wifi isn't being able to run. Not sure what's stopping that but I'm sure it's not too hard to fix. Update:2 Finally I do see one more serial port that I have yet to figure out what exactly it's for. But this gives me another idea to attach one more Arduino or to connect directly to a 3d printer. It shows up as a device in the serial list tree. Got any idea what it is? Would it might be the IR port?

it actually did not require recompiling the bootloader at all actually heres what i did and it works! I worked on connecting a TV box running Armbian with an Arduino using a UART connection, allowing them to communicate. The aim was to control the Arduino using commands sent from the TV box. Firstly, I programmed the Arduino to react to simple text commands that would turn an LED on or off. This step was crucial to test whether commands from the TV box were being correctly received by the Arduino. Next, I focused on setting up the TV box for UART communication. Through the terminal, I found the UART device (/dev/ttyS2) and temporarily disabled its console service using the command sudo systemctl start serial-getty@ttyS2.service or sudo systemctl stop serial-getty@ttyS2.service This was necessary to use the port for sending commands to the Arduino without interference from the TV box’s system. To ensure the setup worked, I connected the TV box to a Windows computer using a USB-to-Serial adapter ( using my Arduino uno for this shorting the reset and GND together to by pass the chips mcu ) and monitored the communication with PuTTY. By sending a test message from the TV box and seeing it in PuTTY, I confirmed the UART port was functioning correctly. This allowed for successful data transmission between the two devices. A key part of this was a external port i made. i went in and solder on pin cables and routed it as neat as i could permanently so i can access the UART easily . This setup made it easy to connect and disconnect the Arduino without opening the TV box each time. It effectively allowed the Arduino to act like a USB-to-Serial device and vice versa, simplifying the communication process. I adjusted permissions to access the UART port without needing administrative rights and ensured the baud rates on both devices matched. this has thus far enabled general commutations through the UART and when i want to log back in through uart if ever i can simply start the serial -getty and log in this then allows me to run NANpy, making the arduino act like a slave to the tv box much like how people take rasberry pis and do the same thing to expand the gpio ports through serial communication using nanpy on the pi! this basically turns our silly ole tv box with the rk3318 into a raspberry pi with out the features lacking! that was the one thing about the pi that made it better for most tasks. well this helps level that disadvantage! @jock

@tj13 don't worry, it's no pain. Bug reports are always appreciated, but without logs or whatever it is very uneasy to guess if the problem is related with the broken installation script or whatever. Surely you can follow the posts of this thread to get a clue; if you installed the system in eMMC perhaps you can try the Multitool from this page and see if it works (I never tried it on TInkerboard), so at least you have a way to backup and access the filesystem. At last, the uart adapter suggested by @SteeMan can give some important hints about what went bad.

Thank you, looking more calmly, I found the headers marked as G, R, T. Would these be: ground, tx, rx? I think I'm confusing it with my second TVbox which has a slightly different PCB, if this is the UART interface, I'll solder headers and connect my USB adapter, at what baud rate should I listen? It worked, it was these pads, here is the output with booting from the SD card: DDR Version V1.10 20190926 In ID:0xFFF 660MHz DDR3 Bus Width=16 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB mach:2 OUT U-Boot SPL 2021.04-armbian (May 06 2021 - 19:15:25 +0000) Trying to boot from MMC2 I/TC: I/TC: Non-secure external DT found I/TC: Switching console to device: /serial@11030000 I/TC: OP-TEE version: 3.10.0-40-ga1d5c81f (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #6 Wed Sep 16 21:36:15 UTC 2020 arm I/TC: Primary CPU initializing M/TC: Not protecting region 1: 0x68400000-0x68600000 I/TC: Primary CPU switching to normal world boot U-Boot 2021.04-armbian (May 06 2021 - 19:15:25 +0000) Model: Generic Rockchip rk322x TV Box board DRAM: 992 MiB MMC: dwmmc@30000000: 1, dwmmc@30020000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial@11030000 Out: serial@11030000 Err: serial@11030000 Model: Generic Rockchip rk322x TV Box board Net: eth0: ethernet@30200000 starting USB... Bus usb@30040000: USB DWC2 Bus usb@30080000: USB EHCI 1.00 Bus usb@300c0000: USB EHCI 1.00 Bus usb@30100000: USB EHCI 1.00 scanning bus usb@30040000 for devices... 1 USB Device(s) found scanning bus usb@30080000 for devices... 1 USB Device(s) found scanning bus usb@300c0000 for devices... 1 USB Device(s) found scanning bus usb@30100000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2909 bytes read in 5 ms (567.4 KiB/s) ## Executing script at 60000000 Boot script loaded from mmc 1 238 bytes read in 5 ms (45.9 KiB/s) 6094752 bytes read in 282 ms (20.6 MiB/s) 8771448 bytes read in 475 ms (17.6 MiB/s) 50042 bytes read in 10 ms (4.8 MiB/s) 786 bytes read in 7 ms (109.4 KiB/s) Applying kernel provided DT overlay rk322x-emmc.dtbo 1286 bytes read in 7 ms (178.7 KiB/s) Applying kernel provided DT overlay rk322x-led-conf1.dtbo 232 bytes read in 7 ms (32.2 KiB/s) Applying kernel provided DT fixup script (rk322x-fixup.scr) ## Executing script at 600f0000 ## Loading init Ramdisk from Legacy Image at 64000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 6094688 Bytes = 5.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 61f00000 Booting using the fdt blob at 0x61f00000 EHCI failed to shut down host controller. EHCI failed to shut down host controller. Using Device Tree in place at 61f00000, end 61f74fff Starting kernel ... I/TC: Secondary CPU 1 initializing I/TC: Secondary CPU 1 switching to normal world boot I/TC: Secondary CPU 2 initializing I/TC: Secondary CPU 2 switching to normal world boot I/TC: Secondary CPU 3 initializing I/TC: Secondary CPU 3 switching to normal world boot Armbian 24.2.1 bookworm ttyS2 rk322x-box login: this is the emmc boot output running the same image from the sd card written on it: ⸮⸮DDR Version V1.10 20190926 In ID:0xFFF 660MHz DDR3 Bus Width=16 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB mach:2 OUT U-Boot SPL 2021.04-armbian (May 06 2021 - 19:15:25 +0000) Trying to boot from MMC2 I/TC: I/TC: Non-secure external DT found I/TC: Switching console to device: /serial@11030000 I/TC: OP-TEE version: 3.10.0-40-ga1d5c81f (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #6 Wed Sep 16 21:36:15 UTC 2020 arm I/TC: Primary CPU initializing M/TC: Not protecting region 1: 0x68400000-0x68600000 I/TC: Primary CPU switching to normal world boot U-Boot 2021.04-armbian (May 06 2021 - 19:15:25 +0000) Model: Generic Rockchip rk322x TV Box board DRAM: 992 MiB MMC: dwmmc@30000000: 1, dwmmc@30020000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial@11030000 Out: serial@11030000 Err: serial@11030000 Model: Generic Rockchip rk322x TV Box board Net: eth0: ethernet@30200000 starting USB... Bus usb@30040000: USB DWC2 Bus usb@30080000: USB EHCI 1.00 Bus usb@300c0000: USB EHCI 1.00 Bus usb@30100000: USB EHCI 1.00 scanning bus usb@30040000 for devices... 1 USB Device(s) found scanning bus usb@30080000 for devices... 1 USB Device(s) found scanning bus usb@300c0000 for devices... 1 USB Device(s) found scanning bus usb@30100000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 Device 0: unknown device switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... libfdt fdt_check_header(): FDT_ERR_BADMAGIC 7[r[999;999H[6n8Card did not respond to voltage select! : -110 Scanning disk dwmmc@30000000.blk... Disk dwmmc@30000000.blk not ready Scanning disk dwmmc@30020000.blk... Found 2 disks No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-8e-44-db-3b-e1-5d ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk322x-rk322x-box ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-rk322x ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 missing environment variable: bootfile Retrieving file: pxelinux.cfg/default ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 Config file not found ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 ethernet@30200000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@30200000 =>

@Caio Lima Viana If you post pictures of the front and back of your board, someone on here may be able to identify the uart connection points

@tj13You get details by hooking up a USB uart adapter and reading the serial console output of the boot process.

unfortunately I don't have access to the serial UART of the TV box, I didn't find any pad with the tx rx labels on the PCB, I'm going to try to replace the rootfs, in the functional Armbian image, with the exception of the boot directory, then write it using multitool , I'll post here if this works. Thank you very much for the tips and quick responses

@Caio Lima Viana Yes, copying sdcard to emmc should work, there is no difference. About the reason it does not boot, if you don't get any output on the HDMI and the board does not answer on the network, serial UART is the essential tool to get some clue about. You can surely do a clean installation on eMMC with multitool, then "transplant" the whole rootfs, but if you don't know where the issue is, you may transfer the problem too and get stuck again.

I try to find where is problem with UART5 dmesg |grep serial [ 1.306076] sun50i-h616-pinctrl 300b000.pinctrl: pin-224 (5000000.serial) status -517 [ 1.306095] dw-apb-uart 5000000.serial: Error applying setting, reverse things back [ 1.306231] sun50i-h616-pinctrl 300b000.pinctrl: pin-226 (5001400.serial) status -517 [ 1.306249] dw-apb-uart 5001400.serial: Error applying setting, reverse things back [ 1.333692] 5000000.serial: ttyS0 at MMIO 0x5000000 (irq = 296, base_baud = 1500000) is a 16550A [ 1.334902] 5001400.serial: ttyS1 at MMIO 0x5001400 (irq = 297, base_baud = 1500000) is a 16550A dmesg don't show ttyS5 only ttyS0 and ttyS1 so UART5 on PIN26 header is ttyS1 not ttyS5 ?

@astrosky you'd definitely want to go with an armbian supported SBC rather than tinkering with a tvbox. Yes, tvboxes usually have one exposed UART, but it is for debug and is already in use for kernel and system logs. It can be altered to be used as a general purpose UART, but requires some effort (modify bootloader, change the kernel device tree) that IMHO it is not worth for. SBCs have their own exposed pins with two or more UARTs, SPI, I2C, I2S and GPIOs that you may easily use without having to solder and desolder things on the board. They are more suitable for serious projects.

Actually these boards have UART correct? Can the UART send communication signals? If so I'm pretty sure I can use the UART parts to create a link to Arduino and then! Have gpio ! I can't believe I didn't think of this before. But I'm certain this is feasible. Uart is a very legacy communication protocol and I'm sure it's fast enough for general purposes scripts and such! The goal is to use it like a MCU and to send commands to the Arduino with out taking up my precious USB ports!

This is so cool, I remember reading about this in the Orange Pi user manual but skipped over it because I found it annoying for some reason that I don't remember now. I set this up and man it's really convenient not to have hdmi and stuff to test linux builds and experiment with your SBC. I also found that we have to enable UART serial console in some SBCs and distros by modifying image files? Is this the case or all distros provide a way to access serial console in some way? I really like this serial console setup, thanks for that suggestion again.

Thank you for answer. I've only tested the Legacy 4.4 image briefly, and baked the latest image for rk322x. If I boot with the SD card (MULTITOOL), press the REBOOT menu, and remove the SD card, then I can boot with the latest image burned into eMMC and use all functions. I'm just curious as to why I have to go through procedures like "SD boot" and "Remove SD after REBOOT" to boot. I still don't know how to check LOG through UART.

Hello, there can be dozen of problems with those symptoms: the kernel does not boot, the image you used is bad, the board is unsupported and does not boot, HDMI does not work on your board, the eMMC is empty, etc... etc... You should try a newer image with a mainline kernel (4.4 is unsupported and unmaintained anymore) and possibly provide UART serial logs to debug the problem.

Description Add support to OrangePi Zero 2W (allwinner H618), changes: Patch for u-boot v2024.04-rc5, includes: allwinner-h616-THS-workaround.patch allwinner-h616-GPU-enable-hack.patch allwinner-pwrled-config-option.patch allwinner-enable-autoboot-keyed.patch allwinner-boot-splash.patch Kernel patch for adding zero2w dts, some part are taken from the orange pi official repo. Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] Documentation summary for feature / change Please delete this section if entry to main documentation is not needed. If documentation entry is predicted, please provide key elements for further implementation into main documentation and set label to "Needs Documentation". You are welcome to open a PR to documentation or you can leave following information for technical writer: [ ] short description (copy / paste of PR title) [ ] summary (description relevant for end users) [ ] example of usage (how to see this in function) How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Build and install the current image to SD, and then test on zero2w [x] Build and install the edge image to SD, and then test on zero2w [x] HDMI: test if HDMI output correctly [x] Network: test if wifi connect to access point correctly [x] Uart: test uart0 to get the kernel output [x] USB: test onboard type-c (host) [x] USB: test onboard type-c (otg) [x] USB: test usb port on the 24pin connector [x] GPIO: test GPIO voltage level - pull down and pull up by gpioset, both ok Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

@thuvasooriya wrote rather than to use HDMI and a monitor, I used a usb-uart (usb-serial) dongle that lets me connect over the serial console with the debug pins and I'm literally able to boot up in a serial console and (even) configure networking, i.e. I didn't even need network and can change the network interface configurations. That would also be a way to troubleshoot boot up problems if there is. I used the serial debug pins/console to configure networking as more than often, the default setup of network isn't what I want, and playing with the network interfaces will lock me out of ssh. After I've network configured over usb-uart, I can then ssh remotely into the device over the network. And that if you use dynamic IP, it may help to install and use avahi-daemon and avahi-tools (i.e. multicast DNS), I installed avahi-daemon on the OPi Z3 Armbian board so that I can find it from my main linux box using avahi-browse -a , and that ssh into there could be simply ssh orangepizero3.local that's a way to practically use it headless , in fact, after I've setup things, it is now my WiFi AP on the desk.

Maybe we can bundle our effords regarding a working S805 image? I also have hundreds of new TV sticks (not boxes) with an Amlogic S805 (Meson 8B). The original Android ROM has the codename stvm8b. Currently I only have a working Android 4.2.2 image with a patched kernel for real 1080p output which can be flashed using TWRP onto the internal eMMC. I really would love to get some kind of more recent and non-Android image up and running. It's a real struggle to get any custom images as most links are dead already which makes it more complicated. Currently I have full UART access to the device and I'm able to interact with the uBoot shell. I also see the full kernel output of the working Android image and have a root shell there. But as others already pointed out kernel 3.10 is way to old to be used in production. So "porting" a more recent kernel would be great. My main goal is to get a Linux image up and running on the box which makes it still useful as device for digital signage or as a small webserver. Some more details on the hardware: ro.product.name=stvm8b ro.product.device=stvm8b ro.product.board=stvm8b ro.product.cpu.abi=armeabi-v7a ro.board.platform=meson8 uBoot output dropping to shell: QA5:A;SVN:B72;POC:1FF;STS:0;BOOT:0;INIT:0;READ:0;CHECK:0;PASS:0; no sdio debug board detected TE : 76654 BT : 15:34:06 May 13 2015 ##### VDDEE voltage = 0x044c CPU clock is 792MHz DDR mode: 32 bit mode DDR size: 1GB (auto) DDR check: Pass! DDR clock: 636MHz with 2T mode DDR pll bypass: Disabled DDR init use : 14831 us HHH Boot From SDIO C SD_boot_type: 00000002 card_type: 00000003 0x0000009f ucl decompress...pass 0x12345678 Boot from internal device 1st eMMC on SDIO C TE : 301370 System Started U-Boot Version: 2011.03-ad3b84b(20150513.153356) clr h-ram DRAM: 1 GiB relocation Offset is: 2feb4000 show partition table: part: 0, name : logo, size : 2000000 part: 1, name : recovery, size : 2000000 part: 2, name : misc, size : 2000000 part: 3, name : boot, size : 2000000 part: 4, name : system, size : 40000000 part: 5, name : cache, size : 20000000 part: 6, name : backup, size : 20000000 part: 7, name : data, size : end aml_card_type=0x0 MMC: [mmc_register] add mmc dev_num=0, port=1, if_type=6 [mmc_register] add mmc dev_num=1, port=2, if_type=6 SDIO Port B: 0, SDIO Port C: 1 power init out reg=c110804c,value=dfffffff IR init done! register usb cfg[0][1] = 3ff6c19c register usb cfg[0][2] = 3ff6c184 NAND: EMMC BOOT: not init nand do not init nand : cause boot_device_flag without nand get_boot_device_flag: init_ret -1 get_boot_device_flag EMMC BOOT: Emmckey: Access range is illegal! [mmc_init] SDIO Port C:1, if_type=7, initialized OK! [mmc_get_partition_table] skip cache partition. Partition table get from SPL is : name offset size flag =================================================================================== 0: bootloader 0 400000 0 1: reserved 2400000 4000000 0 2: cache 6c00000 20000000 2 3: env 27400000 800000 0 4: logo 28400000 2000000 1 5: recovery 2ac00000 2000000 1 6: misc 2d400000 2000000 1 7: boot 2fc00000 2000000 1 8: system 32400000 40000000 1 9: backup 72c00000 20000000 1 10: data 93400000 13ec00000 4 mmc read lba=0x12000, blocks=0x1 mmc read lba=0x12001, blocks=0x1 mmc_read_partition_tbl: mmc read partition OK! eMMC/TSD partition table have been checked OK! i=0,register --- emmc_key MMC BOOT, emmc_env_relocate_spec : env_relocate_spec 59 set_storage_device_flag: store 2 bad chip version!!! efuse mac is : ac:db:da:3d:c4:e5 set ethaddr is : ac:db:da:3d:c4:e5 usid is MH0507015420365 mmc flash is used high freq info->dtbversion = 1025 boardname=stvm8b boardtype=m8b_dongle wifi=rtl8189es dtbtype=stvm8b_dongle_1g Multi dtb tool version: v2 . Multi dtb detected, support 5 dtbs. aml_dt soc: stvm8b platform: dongle variant: 1g dtb 0 soc: stvm8b plat: dongle vari: 1g dtb 1 soc: stvm8b plat: dongle vari: 512m dtb 2 soc: stvm8b plat: normal vari: 1g dtb 3 soc: stvm8b plat: normal vari: 1gcm dtb 4 soc: stvm8b plat: normal vari: 512mcm Find match dtb: 0 vpu clk_level in dts: 3 set vpu clk: 182150000Hz, readback: 182150000Hz(0x701) Net: Meson_Ethernet init suspend firmware done. (ret:0) cvbs trimming.1.v5: 0xa0, 0x0 preboot new... check board version... bad chip version!!! efuse mac is : ac:db:da:3d:c4:e5 set ethaddr is : ac:db:da:3d:c4:e5 usid is MH0507015420365 mmc flash is used high freq info->dtbversion = 1025 boardname=stvm8b boardtype=m8b_dongle wifi=rtl8189es dtbtype=stvm8b_dongle_1g Hardware version information has been written and the check is successful hdmi tx power init mode = 8 vic = 16 set HDMI vic: 16 mode is: 8 viu chan = 1 config HPLL config HPLL done reconfig packet setting done Hit Enter key to stop autoboot -- : 1 tstc enter exit abortboot: 1 The original name was "MyGica ATV185" and each device has a Quad-Core processor (Cortex A5, 1 GHz), 1 GB RAM, 8 GB internal eMMC storage, a WIFI module, 1x USB2.0, 1x microSD slot, 1x HDMI plug and 1x microUSB as power supply. The device should be the same like the ODroid C1 Would love to participate in the process of creating a useful image for the S805 platform and especially for this piece of hardware.

Among the things to try, get and set up a usb-serial (usb-uart) dongle to the debug UART pins, and you should be able to see the boot up in a serial console. The boot messages may provide a clue to what went wrong.

Hello! I have installed Armbian Bookworm on Khadas VIM3. Also I have enabled "UARTa" , "UARTc" in armbian-config utility. After reboot in file /boot/armbienEnv.txt I have checked options about uart (uarc). Also there are many files /dev/ttyS[0-7] exists. After this I try to connect "minicom -D /dev/ttyS0" (ttyS0, S1, and S3 etc). But no answer from my device on pins 15,16 OR 18,19 (this is a UARTA,UARTC, UART linux). Python sripts pyserial output: "i/o error". Does Armbian (Bookworm or Jammy) supports Khadas VIM3 UART? Are there successful cases? One more question: On Ubuntu Server files /dev/ttyS* are absent. However Khadas supports UART (on https://docs.khadas.com/products/sbc/common/applications/gpio/uart ) Thank you!

The box can be toothpicked into a loader from where there are options available including ADB - which I also have no experience with. When trying to boot a generic rk3566 LE image from SD the device stays dark. Which means to me it's trying to boot. Good but not progress. I now have a UART adaptor but didnt get a word over the line yet. UART may need enabling or may be misconfigured or may not be a UART port at all. Flying blind is not great. ADB may be a more productive approach. Eyeballing the board there is a wifi 2.4/5 & BT chip (LGX9358) which had me worried cos no search engine hits but device tree says wifi_chip_type = "ap6398s" and this seems known. I tried to contact the manufacturer wrt general information and about getting maybe access to their (legacy) kernel SDK, but haven't heard back yet. Other sources suggest that this manufacturer is not interested in open source software on their products. Maybe this is true, maybe not, I'll wait, it's only been a week. There is a lot to learn and I havent spent much time on this yet, busy with other stuff.