diff options
| author | Tejas Bhumkar <tejas.arvind.bhumkar@amd.com> | 2024-04-09 15:18:26 +0530 |
|---|---|---|
| committer | Michal Simek <michal.simek@amd.com> | 2024-04-10 09:06:22 +0200 |
| commit | 3a6f440dd3709efa8ea3851e9baf8e774f798fd1 (patch) | |
| tree | 93b3fdd4101741e55e34b295593716e95163f2fa /configs/xilinx_zynqmp_kria_defconfig | |
| parent | fa2f0c97af96bdae82fcbc32c9b0fd6f0cb2b34f (diff) | |
| download | u-boot-3a6f440dd3709efa8ea3851e9baf8e774f798fd1.tar.gz | |
configs: zynqmp_kria: Deactivate CONFIG_SPI_FLASH_BAR
The Kria board features a recovery application that activates
when the FW_EN button is pressed.
Upon power-up flash operates in 3B mode, However, the recovery
application changes it back to 4B mode.
Currently, after a reset, u-boot activates CONFIG_SPI_FLASH_BAR
and assumes the flash is in 3B mode. However, there's no code
or reset lines connected to the flash that could return it to
3B mode. To resolve this issue, changes were made to disable
CONFIG_SPI_FLASH_BAR, which activates 4-byte opcodes.
Signed-off-by: Tejas Bhumkar <tejas.arvind.bhumkar@amd.com>
Link: https://lore.kernel.org/r/20240409094826.4131643-1-tejas.arvind.bhumkar@amd.com
Signed-off-by: Michal Simek <michal.simek@amd.com>
Diffstat (limited to 'configs/xilinx_zynqmp_kria_defconfig')
| -rw-r--r-- | configs/xilinx_zynqmp_kria_defconfig | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/configs/xilinx_zynqmp_kria_defconfig b/configs/xilinx_zynqmp_kria_defconfig index 28b28f68411..7167dd4b71b 100644 --- a/configs/xilinx_zynqmp_kria_defconfig +++ b/configs/xilinx_zynqmp_kria_defconfig @@ -156,7 +156,6 @@ CONFIG_MMC_HS200_SUPPORT=y CONFIG_MMC_SDHCI=y CONFIG_MMC_SDHCI_ZYNQ=y CONFIG_DM_MTD=y -CONFIG_SPI_FLASH_BAR=y CONFIG_SPI_FLASH_STMICRO=y # CONFIG_SPI_FLASH_USE_4K_SECTORS is not set CONFIG_SPI_FLASH_MTD=y |