Hello Rob, We have been using the STM32 F7 QSPI code, and found out the same issues.
I've attached some patches with the fixes we have made, hope that helps. On Mon, May 4, 2020 at 7:18 PM Rob Voisey <r...@fenconsultants.com> wrote: > Thanks Alan. I see it's almost an identical driver so I'll see if I can get > hold of an L4 board. > > Rob > > > On Mon, 4 May 2020 at 19:05, Alan Carvalho de Assis <acas...@gmail.com> > wrote: > > > Hi Rob, > > > > There are some QSPI usage examples for STM32L4 that is very similar > > and you can use as starting point. > > > > BR, > > > > Alan > > > > On 5/4/20, Rob Voisey <r...@fenconsultants.com> wrote: > > > Hi > > > > > > I haven't been able to find any code that uses the STM32F7 QSPI code > even > > > though it has been in the codebase for a few years. An example > candidate > > > would be the STM32F769I-DISC0 board which has an MX25L51245G flash > device > > > on that bus. It's also the combination that I need to get working for > my > > > board. > > > > > > To that end I wrote a driver for the MX25L51245G forked from the > existing > > > MX25RXX driver, and I'm having some trouble getting non-data commands > to > > > complete. The RDID command works fine but non-data commands hang in the > > > QSPI driver waiting on transfer complete status. I've spent a few hours > > > poking around but to narrow it down I was wondering if anyone knows the > > > status of the F7 QSPI driver? Is it up to date and tested? Is there any > > > code that uses it? I'd love to have a known good starting point. > > > > > > Cheers > > > > > > Rob > > > > > >
