Build failed in Jenkins: NuttX-Nightly-Build #117

2020-05-05 Thread Apache Jenkins Server
See Changes: -- [...truncated 579.02 KB...] 22450K .. .. .. .. .. 65% 9.64M 3s 22500K .. .. .. .. ..

Re: Adding support for STM32G474RET6

2020-05-05 Thread Nathan Hartman
On Sun, Apr 19, 2020 at 12:03 AM Nathan Hartman wrote: > I've begun work on supporting the STM32G474RET6, and also the > B-G474E-DPOW1 Discovery board. Just FYI, I've been working on adding support for the STM32G474 family and B-G474E-DPOW1 development board. So far, I have cranked out quite a bi

Re: QSPI on STM32F7

2020-05-05 Thread Rob Voisey
Actually it was my fault, I'm on a slightly old build and although I'd diffed stm32_qspi.c against the head I'd missed an actual fix amongst all the formatting corrections. I did a more thorough job this time and my MX23L51245G driver now appears to read, write and erase correctly. I'm still inter

Re: QSPI on STM32F7

2020-05-05 Thread Rob Voisey
Hi João, Thanks, I'd love to get those patches if you could email or commit them. Right now, using the MTD interface, I can read blocks of data but I can't erase them because that uses a non-data command and those never set TCF for reasons I've yet to understand. Rob On Tue, 5 May 2020 at 13:11

Re: QSPI on STM32F7

2020-05-05 Thread Alan Carvalho de Assis
Other option is creating a PR: https://github.com/apache/incubator-nuttx/pulls On 5/5/20, Alan Carvalho de Assis wrote: > Hi João, > > How are you doing? > > I think you forgot to attach the patches. > > BR, > > Alan > > On 5/5/20, Joao Matos wrote: >> Hello Rob, >> >> We have been using the STM

Re: QSPI on STM32F7

2020-05-05 Thread Alan Carvalho de Assis
Hi João, How are you doing? I think you forgot to attach the patches. BR, Alan On 5/5/20, 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, M

Re: QSPI on STM32F7

2020-05-05 Thread Joao Matos
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: > Thanks Alan. I see it's almost an identical driver so I'll see if I can get > hold