On 14/10/21, Michal Simek wrote:
> 
> 
> On 10/13/21 15:48, Jorge Ramirez-Ortiz wrote:
> > When boot.bin is configured for secure boot the CSU will disable the
> > JTAG interface on all cases.
> > 
> > Some boards might rely on this interface for flashing to QSPI in which
> > case those systems might end up bricked during development.
> > 
> > This commit will restore the interface under CSU control
> > 
> > Signed-off-by: Jorge Ramirez-Ortiz <jo...@foundries.io>
> > ---
> > 
> >   v3: delete unvalid removal of empty line
> > 
> >   arch/arm/mach-zynqmp/Kconfig                 |  8 +++++
> >   arch/arm/mach-zynqmp/include/mach/hardware.h | 31 +++++++++++++++-----
> >   board/xilinx/zynqmp/zynqmp.c                 | 19 ++++++++++++
> >   3 files changed, 51 insertions(+), 7 deletions(-)
> > 
> > diff --git a/arch/arm/mach-zynqmp/Kconfig b/arch/arm/mach-zynqmp/Kconfig
> > index f7b08db355..ee0895d9a2 100644
> > --- a/arch/arm/mach-zynqmp/Kconfig
> > +++ b/arch/arm/mach-zynqmp/Kconfig
> > @@ -149,6 +149,14 @@ config SPL_ZYNQMP_ALT_BOOTMODE_ENABLED
> >       Overwrite bootmode selected via boot mode pins to tell SPL what should
> >       be the next boot device.
> > +config SPL_ZYNQMP_RESTORE_JTAG
> > +   bool "Restore JTAG"
> > +   depends on SPL
> > +   help
> > +    Booting SPL in secure mode causes the CSU to disable the JTAG interface
> > +    even if no eFuses were burnt. This option restores the interface if
> > +    possible.
> 
> here should be tab and 2 spaces.
>
ok

> I have fixed it myself and applied.

thanks a lot Michal for taking care of this

> M

Reply via email to