Rebuilding the bootloaders
#1
Assuming the v1.1 update from mrfixit writes all of the bootloaders it looks like the bootloaders consist of three binaries: idbloader.img, uboot.img and trust.img (which strings suggests is a version of [Arm] Trusted Firmware-A).

It looks like the source for uboot.img would be uboot.img is https://github.com/mrfixit2001/rockchip-u-boot. Is that right (and is the build process "obvious")?

Additionally is there source (or partial source) available for either of the other components?


Thanks!
PineTime: wasp-os and MicroPython, Pinebook Pro:  Debian Bullseye
#2
@danielt 

@ayufan and @Mrfixit2001  might have something to add.

I am still learning the arm embedded boot process, but this is probably a good start:

http://opensource.rock-chips.com/wiki_Boot_option
#3
@hmuller, thank you, that link clears up a lot.

The @Mrfixit2001 boot sequence seems to require "/boot" to be the first partition. An experiment today making partitions of the binary blobs similar to the below failed;

http://opensource.rock-chips.com/wiki_Partitions
--
Arwen Evenstar
Princess of Rivendale
#4
(12-08-2019, 07:15 PM)Arwen Wrote: @hmuller, thank you, that link clears up a lot.

The @Mrfixit2001 boot sequence seems to require "/boot" to be the first partition. An experiment today making partitions of the binary blobs similar to the below failed;

http://opensource.rock-chips.com/wiki_Partitions

I remember setting LegacyBIOSBoot attribute in the GPT table whilst getting my early SD card experiments to boot... the UART logs from u-boot suggest that I don't need it anymore but it might be worth fiddling with that flag just in case I missed something.
PineTime: wasp-os and MicroPython, Pinebook Pro:  Debian Bullseye


Forum Jump:


Users browsing this thread: 1 Guest(s)