Jens J.

I think this is @Igor's signing key aml-s9xx-box:~:# gpg --keyserver keyserver.ubuntu.com --recv-keys 93D6889F9F0E78D5 gpg: key 93D6889F9F0E78D5: 1 duplicate signature removed gpg: key 93D6889F9F0E78D5: public key "Igor Pecovnik <igor@armbian.com>" imported gpg: Total number processed: 1 gpg: imported: 1

also getting this on latest community builds of aml-s9xx-box at https://www.armbian.com/amlogic-s9xx-tv-box/ e.g. https://dl.armbian.com/aml-s9xx-box/Bookworm_current_xfce ``` PRETTY_NAME="Armbian_community 25.8.0-trunk.90 bookworm" ``` wondering if something is broken or missing on the build

So when writing the u-boot to SD card, you need to follow a special process to "skip" over some bytes to prevent trashing the partition table. see https://www.cnx-software.com/2016/11/19/how-to-create-a-bootable-recovery-sd-card-for-amlogic-tv-boxes/ TLDR, something like: sudo umount /dev/sdX* sudo dd if=aml_sdc_burn.UBOOT of=/dev/sdX bs=1 count=442 sudo dd if=aml_sdc_burn.UBOOT of=/dev/sdX seek=1 skip=1 bs=512 sync

Have you tried `/boot/dtb/amlogic/meson-gxm-mini-m8s-pro.dtb` ? What is wifi chip? Is it LTM8830? If so this is QCA9377 clone, and this dtb should be fully working.

afaik, if your box had /dev/mmcblk1, assuming that's the internal storage (and not the sd card), then I believe it means your unit has emmc, not just raw nand. this has a nice explanation of emmc vs nand - TLDR: emmc has mmc controller on top of raw nand storage, making it easier to present the storage to the OS/kernel. With only raw nand, the kernel has to have the drivers in-tree to understand how to talk to the nand chip and handle all of the concerns to present it as a block device. https://www.toradex.com/blog/what-you-should-know-about-flash-storage regardless, glad you got it sorted out

wifi can be a tricky thing you need to identify what wifi chip it's using you could open up the box and look at the wifi module on the board, or you could grab a boot log from serial console output from original android installation, or you could try to run `lsusb` to see if there are any obvious usb-based wifi adapter VID/PIDs there (e.g. realtek, etc) If it's not usb internally-connected wifi module, then likely the module may be connected to internal SDIO bus, which I think will require custom dts to modify and produce a dtb which tells the kernel where to find the wifi adapter. (This usually involves dumping/grabbing the original dtb on the box, which is usually flashed to a particular amlogic partition, and then inspecting it, and hand translating it to modern devicetree - as steeman mentioned, all the android-based images use an ancient 3.x custom, vendor provided kernel, with very vendor specific devicetree features. Modern kernels use a different set of devicetree syntaxes. Then you have to make sure you have the right wifi driver installed/available. Then you have to make sure you have the right firmware installed/available (as most of these wifi modules require soft-loading firmware at boot). root@onecloud:~# lsusb Bus 001 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Does that image contain an s805_autoscript and/or aml_autoscript file at the root of the sdcard? Here's a copy of mine for an MXQ model (note that in my uEnv.txt, it uses a custom m201 dtb) If that doesnt work, then you'll need to get access to serial console to see what the stock uboot is doing, and what sdcard (mmc) files it's looking for on boot. armbian_s805_boot_files.zip

how exactly did you format the emmc? (what commands?) did you follow the install guide, and use `install-aml.sh` (which preserves the boot block on emmc, keeping the old uboot to chainload into new uboot with) ?

correct, unfortunately, some tvbox manufacturers have opted to use cheaper nand flash, rather than emmc-compatible flash, which is supported. Using nand flash directly requires additional support in the bootloader and kernel, which do not currently exist. (There has been _some_ work in the kernel on this, but it's nowhere near finished.) TLDR, you only be able to install to internal flash if it's eMMC.

How did you "install"? via armbian-config install (not for armbian tv boxes) or /root/install-aml.sh (specially made for board type "aml-s9xx-box") ? Did you try booting off of the armbian sd card again (holding the reset button for 7 seconds while powering up)? First thing to do when you think you might have "bricked" a board is to get serial console access on it so you can see what's actually going on, e.g. using a usb uart adapter connected to the serial port header (the four unpopulated pins, specifically: TX, RX, GND). With amlogic and the way armbian installs, the stock amlogic uboot is likely still there, and something else can be loaded from it (via usb, sd, etc).

Hi there, trying to iterate on making small changes to a kernel driver module, and using armbian to help build the kernel (cross-compiling off the device). I'm aware of kernel-patch mode, but for making small changes, compiling, and iterating like this over and over, making and then putting patches into place on each cycle is quite cumbersome. Is there some way to tell armbian build _not_ to update the kernel, i.e. let me build with dirty tree, as I'm in a dev cycle? I just want to edit something in my local kernel tree, then build the kernel, and repeat