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
<Armbian-Discord>
<Tenkawa> Good to hear...hardware hiccups rate up there in the top 5 things in my opinion of hardest to consistently isolate.
<Armbian-Discord>
<Tabalugach> not sure, why htop is not showing my cpu freq, was working before
<Armbian-Discord>
<Demiurge> It seems like this repo is only about building u-boot, but it doesn't specify where to put it.
<Armbian-Discord>
<Tenkawa> Ah.. just a sec...
<Armbian-Discord>
<Tenkawa> let me look at my 3588s
<Armbian-Discord>
<Demiurge> I don't really want to put it on SD card. I have ssd and it also has SPI flash or something idk
<Armbian-Discord>
<Tenkawa> its a set of 2 dd commands... I have them in my builder scripts
<Armbian-Discord>
<Tenkawa> orange pi 5 doesn't have an ssd interface does it?
<Armbian-Discord>
<Tenkawa> thats a 3588s board
<Armbian-Discord>
<Demiurge> it has m2 slot
<Armbian-Discord>
<Tenkawa> not what I'm reading
<Armbian-Discord>
<Demiurge> nvme
<Armbian-Discord>
<Tenkawa> ok I see it.
<Armbian-Discord>
<Tenkawa> You'll need to use the rkdevtool most likely then
<Armbian-Discord>
<Tenkawa> To flash the spi
<Armbian-Discord>
<Tenkawa> from what I see on google/reddit
<Armbian-Discord>
<c0rnelius> the first partition needs an offset of 32768 and uboot gets flashed into the offset ```sudo dd if=idbloader.bin of=/dev/mmcblkX seek=64
<Armbian-Discord>
<c0rnelius> Disk identifier: BD38E1FA-247D-4893-AB81-0E1F0F6E1740
<Armbian-Discord>
<c0rnelius> Device Start End Sectors Size Type
<Armbian-Discord>
<c0rnelius> /dev/mmcblk0p1 32768 524287 491520 240M EFI System
<Armbian-Discord>
<c0rnelius> /dev/mmcblk0p2 524288 62333918 61809631 29.5G Linux filesystem
<Armbian-Discord>
<c0rnelius> ```
<Armbian-Discord>
<Demiurge> So which file is which?
<Armbian-Discord>
<c0rnelius> old vendor RK had three of them but most people are now using a more modern uboot. so you need the loader and uboot binary.
<Armbian-Discord>
<Demiurge> Where does the configuration go?
<Armbian-Discord>
<c0rnelius> it looks like OPI are using the same version of uboot that everyone else is on that SoC. So the above should apply to it.
<Armbian-Discord>
<Demiurge> Can I dd it to /dev/mtd*?
<Armbian-Discord>
<c0rnelius> names of the binary may vary? most people also store a copy of the binaries on the imgs they create. might be able to just find precompiled ones on their imgs.
<Armbian-Discord>
<Demiurge> No, like to SPI flash
<Armbian-Discord>
<c0rnelius> I don't own the board so not sure.
<Armbian-Discord>
<c0rnelius> someone else might have an idea
<Armbian-Discord>
<c0rnelius> i assume it can be done, as other vendors also provide an rkspi_loader.img for their boards. I don't know how to flash it off the top of my head.
<Armbian-Discord>
<Demiurge> So, would it look for u-boot on ssd? I didn't quite catch it
<Armbian-Discord>
<Demiurge> It seems like you've already answered, but I didn't understand it
<Armbian-Discord>
<Demiurge> Wait, it is already on SPI flash and I don't need to put it on nvme, nevermind
<Armbian-Discord>
<Demiurge> Where does u-boot looks for boot script and can I change it to ssd?
<Armbian-Discord>
<Demiurge> Like if default rkspi_loader.img is loaded
Armbian-Discord has quit [Remote host closed the connection]
Armbian-Discord has joined #armbian-rockchip
<Armbian-Discord>
<Tonymac32> not a clue what the rockchip code is doing
<Armbian-Discord>
<c0rnelius> If I understand what you are asking correctly, it would look on the first partition of the SD/MMC. Most people I believe just chainload it. So they setup a boot partition on either SD/MMC and then a ROOTFS on the SSD/NVME.
<Armbian-Discord>
<c0rnelius> I don't know much about loading using SPI so I'm no help there.
<Armbian-Discord>
<ManoftheSea> It shouldn't matter where u boot came from, it'll look for it's environment according to compiled-in options, which will define the boot order. Likely, it's "env on mmc"
<Armbian-Discord>
<ManoftheSea> I don't know what the vendor uboot does, but a fully open source uboot can change the 32k offset.
<Armbian-Discord>
<ManoftheSea> But loading spl/tpl is dependent on soc code, which likely can't do from nvme. That has to come from spi, then.
<Armbian-Discord>
<ManoftheSea> And I haven't finished my experimenting with u-boot spi (on helios64, so rk3399)
<Armbian-Discord>
<ManoftheSea> (which isn't the same as 3588, of course)
<Armbian-Discord>
<Tonymac32> I don't know why it would be incredibly different, of course every single Amlogic chip boots differently because they're lunatics, so I shouldn't be surprised
<Armbian-Discord>
<ManoftheSea> I don't know why there's not more sanity about DTBs for SoC and board, either.
<Armbian-Discord>
<Demiurge> I'm just gonna copy boot partition from armbian and use it to boot my linux xd
<Armbian-Discord>
<Demiurge> Is dtb kernel-specific?
<Armbian-Discord>
<Demiurge> make dtbs_install didn't give me 3588s dtb
<Armbian-Discord>
<Tenkawa> yes dtbs are kernel specific (minimally the build)
<Armbian-Discord>
<Demiurge> damn
<Armbian-Discord>
<Tenkawa> you have to use a kernel source that has it and target in it
<Armbian-Discord>
<Tenkawa> (or binaries)
<Armbian-Discord>
<Tenkawa> if using precompiled
<Armbian-Discord>
<Tenkawa> That's why you need their source repo and to follow their build instructions
<Armbian-Discord>
<Tabalugach> I try to install docker following :