MC firmware loading

[dmitri_lechtchinski]

Hello,

I'm trying to find details on the MC firmware image loading process on boot.

DPAA2UM chapter 3.1 has an overview but not any details.

My questions are:

1. Where can I find a definition of the FIT format? How is this image parsed for MC loading?
2. How is validation of the image performed against its checksum/version?
3. At what address does the image needs to be loaded, is it the start of MC memory base? (MCFBALR/HR)

Also, can you please point me to the reference for this in U-Boot code?

Thanks,
Dmitri

[dmitri_lechtchinski]

Thanks, I have a question regarding the implementation:

In mc_init(), mc_ram_addr is obtained by mc_get_dram_addr() which has the following comment:

/*
 * Return the MC address of private DRAM block.
 * As per MC design document, MC initial base address
 * should be least significant 512MB address of MC private
 * memory, i.e. address should point to end address masked
 * with 512MB offset in private DRAM block.
 */

Does this mean that MCFBALR/HR actually points to the last 512MB of the MC-reserved memory block?
Is there reference in documentation to this memory mapping?

[ufedor]

1) Useful reference:

https://www.marcusfolkesson.se/blog/fit-vs-legacy-image-format/

2) Refer to the U-Boot source:

https://source.codeaurora.org/external/qoriq/qoriq-components/u-boot/tree/drivers/net/fsl-mc/mc.c?h=...

3) Yes.