06-14-2020, 04:38 PM
(This post was last modified: 06-14-2020, 04:39 PM by Arwen.
Edit Reason: Removed duplicate wording
)
(06-14-2020, 04:18 PM)bero Wrote: Hi,The idbloader comes from building U-Boot. I don't know for certain what it is, but I think it's the initialization code for the SoC.
thanks! This is already very useful. Where does idbloader come from? (I presume I could just copy it off EMMC and into the SD card, but that's not really the idea...)
Same for TrustedFirmware-A: Is it this? https://github.com/ARM-software/arm-trusted-firmware
Or do I need to find a fork that supports the right SoC?
Also, if in the first step I decide not to mess with the bootloader, what files on the SD card does the preloaded bootloader try to use?
The TrustedFirmware-A can come from multiple places. It appears to be the run code for the management processors. Meaning after boot, what the management processors actually do. Again I am not certain.
Anyway, their are multiple places to start with U-Boot. Eventually I'd like that Wiki page to describe how to build mainline U-Boot, with USB & NVMe support. As well as how to use Grub, with video & keyboard support, as a target. Make it work a bit like x86/x64 PCs.
@Syonyk - After they changed the Wiki to the new cluster server, I was forced to change my password on the Wiki. But not on the Forum site. So I am guessing something is broke between them. Simply report it.
--
Arwen Evenstar
Princess of Rivendale
Arwen Evenstar
Princess of Rivendale