spl, rk3399: fix FIT image loading out-of-range
v2 cover spl, rk3399: fix FIT image loading out-of-range
The patches in this series address an issue I met when trying to enable FIT signature verification by SPL on a RockPi4B board.
- The first patch avoids a buffer overflow when writing to INTMEM1 SRAM
- The second one addresses reliability issues I had with back-to-back MMC reads from the microSD card. By allowing DMA operation, the issue is gone and generally speaking DMA is preferred over FIFO mode anyways.
Jerome Forissier (2):
spl: fit: add config option for temporary buffer when loading image
rockchip: rk3399: enable spl-fifo-mode for sdmmc only when needed
arch/arm/dts/rk3399-u-boot.dtsi | 2 + common/spl/Kconfig | 45 +++++++++++++++++++ common/spl/spl_fit.c | 79 ++++++++++++++++++++++++++++++--- 3 files changed, 120 insertions(+), 6 deletions(-)
Signature · 1 line
2.34.1
PATCH v2 1/2 spl: fit: add config option for temporary buffer when loading image
When the load address of a FIT image isn't properly aligned, spl_load_fit_image() may write past the end of the destination buffer. It is not an issue in many cases because the memory happens to be writeable and nothing important is present in the overflow. On RockPi4 however there is a configuration where a TF-A image (bl31_0xff3b0000.bin) has to be loaded into a 8K range of SRAM memory, between 0xff3b0000 and 0xff3b2000. The end address is a hard limit, because due to the way the hardware is wired, the addresses wrap and any overflow gets written back to 0xff3b0000 thus overwriting previous data.
To address this problem, introduce a helper function which loads data using a temporary buffer allocated on the stack. The size of the buffer is defined by SPL_LOAD_FIT_IMAGE_BUFFER_SIZE (default 0x0 or disabled).
--- common/spl/Kconfig | 45 +++++++++++++++++++++++++ common/spl/spl_fit.c | 79 ++++++++++++++++++++++++++++++++++++++++---- 2 files changed, 118 insertions(+), 6 deletions(-)
common/spl/Kconfig +45 -0
@@ -1339,6 +1339,51 @@ config SPL_OPENSBI_LOAD_ADDR help Load address of the OpenSBI binary. +config SPL_LOAD_FIT_IMAGE_BUFFER_SIZE + hex "Read unaligned external FIT images to a temporary buffer in SPL" + default 0x0 + depends on SPL_LOAD_FIT + help + An aligned FIT image is such that it starts at the beginning + of a block in media and has a load_addr in its FIT header + that is DMA aligned in RAM. These aligned images can be read + directly from media to RAM. Unaligned external FIT images + are those that need reading some extra data before and/or after + the image because they don't occupy fully the blocks they're + in in media, or their destination is not DMA aligned and must + be read somewhere aligned before copying them to load_addr. + + With this option set to 0x0 full blocks will just be read in + the closest DMA aligned address, and the unaligned image + inside those read blocks will later be copied to + load_addr. Meanwhile memory outside [load_addr, + load_addr+length) will have been written. That's no problem + when the block length, image size and load_addr have been + taken into account when laying out memory. + + But in some cases not all memory is writable, or undesired + effects arise when writing outside [load_addr, + load_addr+length). For instance, in RK3399, one of the + images is ATF2, of size 8KiB which should be loaded into + INTMEM1, at address 0xff3b0000. This address is DMA aligned + but tight. It maps to a 8KiB SRAM area. If the image on + media is not block aligned some extra bytes get read before + and after, and everything extra written in + 0xff3b2000-0xff3bffff corrupts SRAM at + 0xff3b0000-0xff3b1fff before the image is memcpyied in place. + + With this option set to a nonzero value a DMA aligned buffer + will be allocated on the stack and the image will be read + in chuncks of blocks to this buffer, with each chunk being + memcpyied to [load_addr,load_addr+length), so never writing + outside the destination area. + + The advantage of enabling this option is safety, and the + disadvantage is more stack use and slower image load (one read + per chunk instead of just one). + + The default is 0x0 to replicate previous behaviour. + config TPL bool depends on SUPPORT_TPL
common/spl/spl_fit.c +73 -6
106 lines not on this page · raw message
Signature · 1 line
2.34.1
PATCH v2 2/2 rockchip: rk3399: enable spl-fifo-mode for sdmmc only when needed
In reply to Jerome ForissierCommit 5c606ca35c42 ("rockchip: rk3399: enable spl-fifo-mode for sdmmc") mentions that the RK3399 SoC can't do DMA between SDMMC and SRAM. According to the TRM "7.3.2 Embedded SRAM access path" [1], only the 8KB SRAM at 0xff3b0000 (INTMEM1) is in this situation. The 192KB SRAM can be accessed by both DMA controllers.
Assuming the only use case for writing from MMC to INTMEM1 is loading a FIT image, and with the introduction of a temporary buffer for that purpose (CONFIG_SPL_LOAD_FIT_IMAGE_BUFFER_SIZE, which is required anyways to ensure the destination boundaries are enforced), then spl-fifo-mode is not needed anymore and DMA can be enabled safely.
---
Changes since v1:
- Fixed conditional (#if ... == 0 instead or #ifndef)
--- arch/arm/dts/rk3399-u-boot.dtsi | 2 ++ 1 file changed, 2 insertions(+)
arch/arm/dts/rk3399-u-boot.dtsi +2 -0
@@ -124,8 +124,10 @@ &sdmmc { u-boot,dm-pre-reloc; +#if (CONFIG_SPL_LOAD_FIT_IMAGE_BUFFER_SIZE == 0) /* mmc to sram can't do dma, prevent aborts transferring TF-A parts */ u-boot,spl-fifo-mode; +#endif }; &spi1 {
Signature · 1 line
2.34.1