Scott Picton

I'm a bit out of my depth now. @Gunjan Gupta might be the right person to fix this bug?

@mhel if you're talking about eMMC then I think you're talking about the Tinker Board S? I imagine that might have slight differences to the Tinker Board that my fix works for. The .spl.bin image is read from and dd'd to the affected SD card.

I've repaired my install by manually applying the failed dd step. 1. Mount the SD card on another Linux machine and open up a terminal. 2. `cd` to the SD card, for me it's `cd /media/scott/sdcard/` 3. `cd` to the u-boot image directory `cd usr/lib/linux-u-boot-current-tinkerboard/` 4. make note of which device the sd card is, you could use `mount | grep media` for example 5. for me it's `/dev/sdb` but it could be something like `/dev/mmcblk1` 6. IMPORTANT make sure you absolutely have the right device 7. run the following, replacing XXX with your target device `dd if=u-boot-rockchip-with-spl.bin of=/dev/XXX bs=32k seek=1 conv=notrunc`

@Z11ntal33r thanks for posting the log. It looks obvious to me that the issue is the u-boot update process. In your logs I can see: `dd: error reading '/usr/lib/linux-u-boot-current-tinkerboard/': Is a directory` A bit of a dig into the code shows there's probably a dd process before that step that zeros out the boot sectors. Hence no boot at all on our boards. Might be an easy I'm not really sure how to patch any of this but thought I'd share what I found to help move this along.

I have the same issue and just tried to get a serial dump but I get absolutely nothing. I've connected to pins 32 TX and 33 RX + GND. I confirmed I have the right pins by booting a known good image and get something starting with `U-Boot TPL 2022.04-armbian (Nov 25 2023 - 12:49:32)`. Is there anything we can check on the SD as to why it doesn't boot?