lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
lanefu-er has quit [Ping timeout: 255 seconds]
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
lanefu-er has joined #armbian-rockchip
lanefu-er has quit [Ping timeout: 255 seconds]
lanefu-er has joined #armbian-rockchip
<DC-IRC>
<gambl0r> hi guys, I tried flashing `Armbian_23.8.1_Orangepi5-plus_bookworm_legacy_5.10.160.img.xz` to emmc via rkdevtool and also via dd, it doesn't boot
<DC-IRC>
<gambl0r> I'll try minimal now
<DC-IRC>
<spooky8086> Try to clear the spi
<DC-IRC>
<gambl0r> I did that, then wrote it again, same thing
<DC-IRC>
<gambl0r> your image boots from emmc just fine
<DC-IRC>
<gambl0r> I just wrote armbian jammy to emmc, that booted fine too
<DC-IRC>
<efectn> The image might be broken
<DC-IRC>
<efectn> Did you verify checksum
<DC-IRC>
<gambl0r> `Armbian_23.8.1_Orangepi5-plus_jammy_legacy_5.10.160.img.xz` works after I flashed via dd
<DC-IRC>
<gambl0r> @efectn I downloaded it twice, from different systems, same thing on both
<DC-IRC>
<tenkawa42> I think the image itself has a problem
<DC-IRC>
<tenkawa42> I don't believe you are the first person I've heard complain about this
<DC-IRC>
<efectn> Let me check it tonight
<DC-IRC>
<tenkawa42> Its very likely the u-boot boot order is wrong
<DC-IRC>
<gambl0r> I've never had an issue with corrupt downloads so it's highly likely an issue with the image
<DC-IRC>
<tenkawa42> Its set to always boot from emmc first
<DC-IRC>
<tenkawa42> One doesn't boot at all
<DC-IRC>
<tenkawa42> And I can't remember what the other odd scenario was