tools: k3_fit_atf: Fix DM binary FIT load addresses
The DM binary runs on the MCU R5F Core0 after R5 SPL on J721E and J7200
SoCs. The binary is built alongside the TFA, OPTEE and A72 SPL binaries
and included in the tispl.bin FIT image. The R5 SPL loads the DM binary
at 0xA0000000 address, based on the value used in the FIT image build
script. The DM binary though is an ELF image and not a regular binary
file, and so is processed further to load the actual program segments
using the U-Boot's standard ELF loader library.
The DM binary does leverage a certain portion of DDR for its program
segments, and typically reserves 16 MB of DDR at 0xA0000000 with the
1st MB used for IPC between Linux and the remote processor, and
remaining memory for firmware segments. This can cause an incomplete
loading of the program segments if the DM binary is larger than 1 MB,
due to overlap of the initial loaded binary and the actual program
segments.
Fix this by using the address 0x89000000, which matches the current
"addr_mcur5f0_0load" env variable used by R5 SPL before the DM firmware
inclusion into the tispl.bin.
Fixes: df5363a67f
("tools: k3_fit_atf: add DM binary to the FIT image")
Signed-off-by: Suman Anna <s-anna@ti.com>
This commit is contained in:
parent
7ca1af635a
commit
7d67334dfe
@ -67,8 +67,8 @@ cat << __HEADER_EOF
|
|||||||
arch = "arm32";
|
arch = "arm32";
|
||||||
compression = "none";
|
compression = "none";
|
||||||
os = "DM";
|
os = "DM";
|
||||||
load = <0xa0000000>;
|
load = <0x89000000>;
|
||||||
entry = <0xa0000000>;
|
entry = <0x89000000>;
|
||||||
};
|
};
|
||||||
spl {
|
spl {
|
||||||
description = "SPL (64-bit)";
|
description = "SPL (64-bit)";
|
||||||
|
Loading…
Reference in New Issue
Block a user