| Message ID | 20240409094826.4131643-1-tejas.arvind.bhumkar@amd.com |
|---|---|
| State | Accepted |
| Commit | 3a6f440dd3709efa8ea3851e9baf8e774f798fd1 |
| Delegated to: | Michal Simek |
| Headers | show |
| Series | [v2] configs: zynqmp_kria: Deactivate CONFIG_SPI_FLASH_BAR | expand |
On 4/9/24 11:48, Tejas Bhumkar wrote: > 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> > --- > Changes in v2: Updated commit message. > > configs/xilinx_zynqmp_kria_defconfig | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/configs/xilinx_zynqmp_kria_defconfig b/configs/xilinx_zynqmp_kria_defconfig > index 7cb8b62d32..7af8b27be9 100644 > --- a/configs/xilinx_zynqmp_kria_defconfig > +++ b/configs/xilinx_zynqmp_kria_defconfig > @@ -155,7 +155,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 Applied. M
diff --git a/configs/xilinx_zynqmp_kria_defconfig b/configs/xilinx_zynqmp_kria_defconfig index 7cb8b62d32..7af8b27be9 100644 --- a/configs/xilinx_zynqmp_kria_defconfig +++ b/configs/xilinx_zynqmp_kria_defconfig @@ -155,7 +155,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
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> --- Changes in v2: Updated commit message. configs/xilinx_zynqmp_kria_defconfig | 1 - 1 file changed, 1 deletion(-)