Re: [U-Boot] [EXT] Saving u-boot environment on LS1046ardb QSPI bricks flash memory

2019-09-13 Thread Matthew Ratson
Hi Ashish,

Thank you very much for your quick response and the information you
provided, greatly appreciated.

Do you possibly know what is the latest Denx u-boot release where this
issue does not exist, and QSPI builds are working?

Thanks,
Matthew

On Fri, Sep 13, 2019 at 5:22 AM Ashish Kumar  wrote:

>
>
> > -Original Message-
> > From: U-Boot  On Behalf Of Matthew
> > Ratson
> > Sent: Friday, September 13, 2019 12:55 AM
> > To: u-boot@lists.denx.de
> > Subject: [EXT] [U-Boot] Saving u-boot environment on LS1046ardb QSPI
> > bricks flash memory
> >
> > Caution: EXT Email
> >
> > Hi there,
> >
> > I am currently working with a LS1046ardb development board from
> > NXP/Layerscape. Using their provided firmware image from the primary QSPI
> > memory bank, I have tried to flash my own compiled u-boot (using the
> > ls1046ardb_qspi_defconfig file) onto the alternate memory bank. I have
> also
> > flashed a Reset Configuration Word (RCW) which was provided by NXP.
> >
> > This process is successful and the alternate bank boots into u-boot.
> > However, I discovered that after simply executing a "saveenv" command and
> > then rebooting again into the alternate bank, the alternate flash memory
> > seems to be "bricked". I can no longer boot into the alternate bank and
> > instead, the board will boot into the default bank.
> >
> > I am wondering if this issue and has been noticed already by someone or
> if
> > there is something I am not doing correctly.
> >
> > Is their a specific denx RCW that I should use instead, rather than the
> one
> > provided by NXP?
> >
> > Any help would be greatly appreciated!
> Hi Matthew,
>
> This driver is broken in upstream and it is work in progress to  fix  and
> update in upstream.
> You can still fetch this from github as few other people have also
> reported the same.
> On  github repo there are 2 version of driver.
>
> One with old xfer method and one with new spi-mem version.
> I am debugging the spi-mem version as this is the recommended version by
> maintainers .
> LS1046 is working via both methods. There are some debug prints in spi-mem
> version.
>
> https://github.com/erashish007/u-boot-spi-mem/
> br:  spi-mem-port
> https://github.com/erashish007/u-boot-spi-mem/
> br: xfer_wrking
>
> Regards
> Ashish
> > ___
> > U-Boot mailing list
> > U-Boot@lists.denx.de
> >
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.d
> > enx.de%2Flistinfo%2Fu-
> > boot&data=02%7C01%7CAshish.Kumar%40nxp.com%7C8e1f67af6f3948
> > 9afc0e08d737bbfd91%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C
> > 637039152865550331&sdata=C6DTwmG7cZXPey9J%2BTNUcqIr937vWhu
> > 1gE6Tq2tGr0g%3D&reserved=0
>
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot


Re: [U-Boot] [EXT] Saving u-boot environment on LS1046ardb QSPI bricks flash memory

2019-09-13 Thread Ashish Kumar


> -Original Message-
> From: U-Boot  On Behalf Of Matthew
> Ratson
> Sent: Friday, September 13, 2019 12:55 AM
> To: u-boot@lists.denx.de
> Subject: [EXT] [U-Boot] Saving u-boot environment on LS1046ardb QSPI
> bricks flash memory
> 
> Caution: EXT Email
> 
> Hi there,
> 
> I am currently working with a LS1046ardb development board from
> NXP/Layerscape. Using their provided firmware image from the primary QSPI
> memory bank, I have tried to flash my own compiled u-boot (using the
> ls1046ardb_qspi_defconfig file) onto the alternate memory bank. I have also
> flashed a Reset Configuration Word (RCW) which was provided by NXP.
> 
> This process is successful and the alternate bank boots into u-boot.
> However, I discovered that after simply executing a "saveenv" command and
> then rebooting again into the alternate bank, the alternate flash memory
> seems to be "bricked". I can no longer boot into the alternate bank and
> instead, the board will boot into the default bank.
> 
> I am wondering if this issue and has been noticed already by someone or if
> there is something I am not doing correctly.
> 
> Is their a specific denx RCW that I should use instead, rather than the one
> provided by NXP?
> 
> Any help would be greatly appreciated!
Hi Matthew,

This driver is broken in upstream and it is work in progress to  fix  and 
update in upstream.
You can still fetch this from github as few other people have also reported the 
same.
On  github repo there are 2 version of driver. 

One with old xfer method and one with new spi-mem version. 
I am debugging the spi-mem version as this is the recommended version by 
maintainers .
LS1046 is working via both methods. There are some debug prints in spi-mem 
version.

https://github.com/erashish007/u-boot-spi-mem/
br:  spi-mem-port
https://github.com/erashish007/u-boot-spi-mem/
br: xfer_wrking

Regards
Ashish 
> ___
> U-Boot mailing list
> U-Boot@lists.denx.de
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.d
> enx.de%2Flistinfo%2Fu-
> boot&data=02%7C01%7CAshish.Kumar%40nxp.com%7C8e1f67af6f3948
> 9afc0e08d737bbfd91%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C
> 637039152865550331&sdata=C6DTwmG7cZXPey9J%2BTNUcqIr937vWhu
> 1gE6Tq2tGr0g%3D&reserved=0
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot