tly.
I'm still interested in João's patches in case there are other issues I
haven't run into yet.
Cheers
Rob
On Tue, 5 May 2020 at 13:33, Rob Voisey wrote:
> Hi João,
>
> Thanks, I'd love to get those patches if you could email or commit them.
>
> Right now, usin
May 2020 at 13:11, Joao Matos wrote:
> 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 wrote:
&
starting point.
>
> BR,
>
> Alan
>
> On 5/4/20, Rob Voisey 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 S
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
b
Hi
If any NuttX developers are exhibiting at or visiting Embedded World this
week and would like a chat about our favourite OS over a coffee let me
know. I'll be there Tuesday and Wednesday.
Rob
Hi
I posted a bug just now.
https://github.com/apache/incubator-nuttx/issues/136
I forgot to mention in the ticket I'm building from master at e59f242.
I feel bad for throwing out a report without finding the cause but I'm
pulled in many directions this month. The issue appears to be in code wh
My approach has always been to go direct to the copyright holder and get it
in writing that you can use the code under a license which is compatible
with yours. It makes things a lot simpler down the line, even if it's
usually a massive hassle up front.
Rob
On Fri, 17 Jan 2020, 14:44 Gregory Nutt
