On Mon, Jan 06, 2025 at 03:33:16PM +0100, Ahmad Fatoum wrote:
> Hello Sascha,
>
> On 06.01.25 14:47, Sascha Hauer wrote:
> > These files are generated from yaml files in U-Boot. Ideally we would
> > use these yaml files and convert them ourselves, but for now just use
> > the binary files and leave the conversion for later patches.
> >
>
> What do these blobs do?
They contain various configuration options evaluated by the ROM.
There are four yaml files: board-cfg.yaml, pm-cfg.yaml, rm-cfg.yaml and
sec-cfg.yaml. An example board-cfg.yaml looks like this:
board-cfg:
rev:
boardcfg_abi_maj: 0x0
boardcfg_abi_min: 0x1
control:
subhdr:
magic: 0xC1D3
size: 7
main_isolation_enable: 0x5A
main_isolation_hostid: 0x2
secproxy:
subhdr:
magic: 0x1207
size: 7
scaling_factor: 0x1
scaling_profile: 0x1
disable_main_nav_secure_proxy: 0
msmc:
subhdr:
magic: 0xA5C3
size: 5
msmc_cache_size: 0x0
debug_cfg:
subhdr:
magic: 0x020C
size: 8
trace_dst_enables: 0x00
trace_src_enables: 0x00
These files are loaded and evaluated against a schema and then
serialized. The yaml files are added for each board in U-Boot, many of
them are identical and hardly ever touched once added to the U-Boot
tree.
I haven't yet found any TI documentation about the binaries.
>
> > Signed-off-by: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>
> > ---
> > arch/arm/boards/beagleplay/combined-dm-cfg.bin | Bin 0 -> 1346 bytes
> > arch/arm/boards/beagleplay/combined-sysfw-cfg.bin | Bin 0 -> 1740 bytes
> > 2 files changed, 0 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/arm/boards/beagleplay/combined-dm-cfg.bin b/arch/arm/boards/beagleplay/combined-dm-cfg.bin
> > new file mode 100644
> > index 0000000000..83fb5ee925
> > Binary files /dev/null and b/arch/arm/boards/beagleplay/combined-dm-cfg.bin differ
> > diff --git a/arch/arm/boards/beagleplay/combined-sysfw-cfg.bin b/arch/arm/boards/beagleplay/combined-sysfw-cfg.bin
> > new file mode 100644
> > index 0000000000..25f35d46ce
> > Binary files /dev/null and b/arch/arm/boards/beagleplay/combined-sysfw-cfg.bin differ
>
> We haven't had any binary files in barebox' git so far. Do we want to start now?
>
> Can we make these firmware/ blobs, until the YAML tooling is imported?
By that you mean just move them from the board directory to firmware/ or
something else?
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
