Official LE13 Test Images for Amlogic (Kodi-22)

  • Images in my test share are updated to Linux 6.19.y and with a change to the uImage.lzo kernel entry point that's currently needed to get the kernel booting on S4 boards; so I'm interested in reports of boot failures after updating. As part of that work I've added support for the Khadas VIM1S board, although this is not real-world usable at the moment (and thus won't be in official nightlies for a while) due to issues with the S4 DRM driver that result in a flickering screen when Kodi is running, and new alsa incantations being needed for audio routing/mixer settings. Khadas shipped a bunch of VIM1S (S905Y4) samples so there's common hardware among those needing (or wanting) to test the new stateless video codecs and dependencies (DRM, audio, etc.) Amlogic are working on.

  • I'm also interested to hear if WeTek Hub boards are booting fine now? - some folks had an issue we suspected of being noise on the UART that caused it to see a keypress and enter the u-boot console instead of booting. Feedback would be nice.

    As a Wetek Hub owner I can try to test this for you. I have some experience with linux and command-line. Is there a way to verify that the issue is solved? Can one for instance monitor the UART activity once the system has been started? Or do I just need to start the system multiple times and see what happens?

  • rawnar You create an SD card using the "box" image then boot from SD card and download or copy the "wetek-hub" board image over to /storage, then write the board image to the internal eMMC storage using emmctool, power off, and then boot. If the issue is fixed, the device boots fine. If it is not fixed, boot will not complete as noise on the UART lines is seen as a keypress and forces you into the u-boot console instead of booting into Linux. To recover from that you will need the 3.5mm to DB9 serial UART adapter WeTek originally shipped with the box, and some kind of DB9 to USB serial UART adapter (as computers don't have DB9 serial ports these days).

  • chewitt: I have made the SD card using the "box" image. Where can I find the "wetek-hub" board image? In your testing folder I can find the "wetek-play2" and "wetek-core2" board images, but not the "wetek-hub" one. Can I use the "wetek-play2" board image?

    Did some digging through the boxes and found the original UART to DB9 cable. I assume it uses RS232 levels for the serial communication.

  • I've not tried booting Hub/Play2 from each others images so can't guarantee that works. If you erase emmc so the board boots from SD card it's safe to experiment though. If you write the wrong image to emmc and there's an issue, it's not impossible to resolve but hope you like dismantling things and shorting pins on the emmc chips to temp disable them and boot from SD card again; as that's what'll be needed. I'm up to my neck in some Rockchip work at the moment, but test on SD card and if that works and you want the right image to write to emmc, I'll find some time to go build one.

    No idea on UART levels as I have a generic USB to DB9 adapter (cheap on Amazon) for those boxes. The only annoying thing is one of the cables WeTek shipped (can't remember which) is fema1e DB9 not ma1e, but that's solveable with a gender bender.