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> <T​enkawa> Good to hear...hardware hiccups rate up there in the top 5 things in my opinion of hardest to consistently isolate.
<Armbian-Discord> <T​abalugach> not sure, why htop is not showing my cpu freq, was working before
<Armbian-Discord> <T​abalugach> update: running with sudo htop, without nope
<Armbian-Discord> <T​enkawa> htop might need access to /sys
<Armbian-Discord> <T​enkawa> ie notice the perms:
<Armbian-Discord> <T​enkawa> ls -l /sys/devices/system/cpu/cpufreq/policy4/cpuinfo_cur_freq
<Armbian-Discord> <T​enkawa> -r-------- 1 root root 4096 Jan 5 09:40 /sys/devices/system/cpu/cpufreq/policy4/cpuinfo_cur_freq
<Armbian-Discord> <T​enkawa> for the user running it (thus needing sudo in your example)
<Armbian-Discord> <D​emiurge> How can I install u-boot on RK3588? I can't find any info anywhere or maybe I'm just blind
<Armbian-Discord> <D​emiurge> It doesn't say where the chip looks for u-boot and what the partitions must look like
<Armbian-Discord> <D​emiurge> I assume you have figured it out, since the image for orange Pi 5 is hosted on the site
<Armbian-Discord> <D​emiurge> Not very armbian specific, but I have nowhere to ask
<Armbian-Discord> <T​enkawa> @Demiurge technically its a 3588s which is a bit different SoC
<Armbian-Discord> <T​enkawa> Github
<Armbian-Discord> <T​enkawa> oops
<Armbian-Discord> <T​enkawa> wrong paste
<Armbian-Discord> <T​enkawa> https://github.com/orangepi-xunlong
<Armbian-Discord> <T​enkawa> This is their software repo for the boards
<Armbian-Discord> <T​enkawa> There's a u-boot repo on there
<Armbian-Discord> <T​enkawa> There's also guide's here:
<Armbian-Discord> <T​enkawa> I'm thinking "this" branch in theory
<Armbian-Discord> <D​emiurge> It seems like this repo is only about building u-boot, but it doesn't specify where to put it.
<Armbian-Discord> <T​enkawa> Ah.. just a sec...
<Armbian-Discord> <T​enkawa> let me look at my 3588s
<Armbian-Discord> <D​emiurge> 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> <T​enkawa> its a set of 2 dd commands... I have them in my builder scripts
<Armbian-Discord> <T​enkawa> orange pi 5 doesn't have an ssd interface does it?
<Armbian-Discord> <T​enkawa> thats a 3588s board
<Armbian-Discord> <D​emiurge> it has m2 slot
<Armbian-Discord> <T​enkawa> not what I'm reading
<Armbian-Discord> <D​emiurge> nvme
<Armbian-Discord> <T​enkawa> ok I see it.
<Armbian-Discord> <T​enkawa> You'll need to use the rkdevtool most likely then
<Armbian-Discord> <T​enkawa> To flash the spi
<Armbian-Discord> <T​enkawa> from what I see on google/reddit
<Armbian-Discord> <c​0rnelius> 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> <c​0rnelius> sudo dd if=u-boot.itb of=/dev/mmcblkX seek=16384```
<Armbian-Discord> <T​enkawa> Thanks
<Armbian-Discord> <c​0rnelius> yep
<Armbian-Discord> <T​enkawa> I have almost everything shutdown
<Armbian-Discord> <c​0rnelius> one example: ```Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
<Armbian-Discord> <c​0rnelius> Units: sectors of 1 * 512 = 512 bytes
<Armbian-Discord> <c​0rnelius> Sector size (logical/physical): 512 bytes / 512 bytes
<Armbian-Discord> <c​0rnelius> I/O size (minimum/optimal): 512 bytes / 512 bytes
<Armbian-Discord> <c​0rnelius> Disklabel type: gpt
<Armbian-Discord> <c​0rnelius> Disk identifier: BD38E1FA-247D-4893-AB81-0E1F0F6E1740
<Armbian-Discord> <c​0rnelius> Device Start End Sectors Size Type
<Armbian-Discord> <c​0rnelius> /dev/mmcblk0p1 32768 524287 491520 240M EFI System
<Armbian-Discord> <c​0rnelius> /dev/mmcblk0p2 524288 62333918 61809631 29.5G Linux filesystem
<Armbian-Discord> <c​0rnelius> ```
<Armbian-Discord> <D​emiurge> So which file is which?
<Armbian-Discord> <c​0rnelius> 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> <D​emiurge> Where does the configuration go?
<Armbian-Discord> <c​0rnelius> config of what?
<Armbian-Discord> <c​0rnelius> 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> <D​emiurge> Can I dd it to /dev/mtd*?
<Armbian-Discord> <c​0rnelius> 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> <D​emiurge> No, like to SPI flash
<Armbian-Discord> <c​0rnelius> I don't own the board so not sure.
<Armbian-Discord> <c​0rnelius> someone else might have an idea
<Armbian-Discord> <c​0rnelius> 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> <D​emiurge> So, would it look for u-boot on ssd? I didn't quite catch it
<Armbian-Discord> <D​emiurge> It seems like you've already answered, but I didn't understand it
<Armbian-Discord> <D​emiurge> Wait, it is already on SPI flash and I don't need to put it on nvme, nevermind
<Armbian-Discord> <D​emiurge> Where does u-boot looks for boot script and can I change it to ssd?
<Armbian-Discord> <D​emiurge> 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> <T​onymac32> not a clue what the rockchip code is doing
<Armbian-Discord> <c​0rnelius> 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> <c​0rnelius> I don't know much about loading using SPI so I'm no help there.
<Armbian-Discord> <M​anoftheSea> 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> <M​anoftheSea> I don't know what the vendor uboot does, but a fully open source uboot can change the 32k offset.
<Armbian-Discord> <M​anoftheSea> 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> <M​anoftheSea> And I haven't finished my experimenting with u-boot spi (on helios64, so rk3399)
<Armbian-Discord> <M​anoftheSea> (which isn't the same as 3588, of course)
<Armbian-Discord> <T​onymac32> 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> <M​anoftheSea> I don't know why there's not more sanity about DTBs for SoC and board, either.
<Armbian-Discord> <D​emiurge> I'm just gonna copy boot partition from armbian and use it to boot my linux xd
<Armbian-Discord> <D​emiurge> Is dtb kernel-specific?
<Armbian-Discord> <D​emiurge> make dtbs_install didn't give me 3588s dtb
<Armbian-Discord> <T​enkawa> yes dtbs are kernel specific (minimally the build)
<Armbian-Discord> <D​emiurge> damn
<Armbian-Discord> <T​enkawa> you have to use a kernel source that has it and target in it
<Armbian-Discord> <T​enkawa> (or binaries)
<Armbian-Discord> <T​enkawa> if using precompiled
<Armbian-Discord> <T​enkawa> That's why you need their source repo and to follow their build instructions
<Armbian-Discord> <T​abalugach> I try to install docker following :
<Armbian-Discord> <T​abalugach> but hit the wall
<Armbian-Discord> <I​gorPec> try this https://github.com/armbian/documentation/pull/297/files