temporary_name

Hello there! I have a generic S805 TV box which, I assume, has a dead NAND memory chip. It doesn't boot and only outputs the following message over UART: QA5:B;SVN:B72;POC:3FF;STS:0;BOOT:0;INIT:0;READ:82;BOOT:1;INIT:10;USB:3;SERIAL:4;STS:0;BOOT:0;INIT:0;READ:82;BOOT:1;INIT:10;USB:3; I found firmware for a similar TV box online and extracted the bootloader.bin file from it. I then wrote it to the beginning of an SD card using dd like this: sudo dd if=bootloader.bin of=/dev/sdX Where sdX is my SD card. Now, at least, the box is trying to boot from the SD card and I can get into U-Boot. Here are the logs I see now: So, is it possible to run Armbian without a NAND chip? I can’t write the system image to the SD card because the bootloader has to be placed at the beginning of the card, and it’s quite large — it overwrites the partition table of the SD card. I tried writing the system image to a USB flash drive instead, but as you can see from the logs, U-Boot can’t initialize USB. (Re)start USB(0)... USB: dwc_usb driver version: 2.94 6-June-2012 USB (1) peri reg base: c1108820 USB (1) use clock source: XTAL input USB (1) base addr: 0xc90c0000 dwc_otg: usb_lowlevel_init: Bad value for SNPSID: 0x00000000 Error, couldn't init Lowlevel part Is this a problem with an incompatible U-Boot, or is the SoC already in very bad shape?

Hello there! I want to ask a question about burning images into SD cards. I followed the steps of OP, I tried to burn the image via DD and via balenaEtcher, and both of them didn't created a boot partition (balenaEtcher did warn me that the image does not contain a partition table). As far as I recall, those files like uEnv.txt, .dtb, etc must be placed in the boot partition, am I right? Did I do something wrong, or did I should somehow create those parts by myself? Thanks! Image used: Armbian-unofficial_23.11.0-trunk_Onecloud_bullseye_edge_6.6.2.burn.img