SPI driver is not working in S32K144 EVB

2021-04-16 Thread Sathish Touch energy
> > > Hello, > We are trying to check SPI driver functionality for our application on > NUTTX-10.0.0 baseline. > On the supported platform link ( > https://nuttx.apache.org/docs/latest/introduction/detailed_support.html#other-armv4) > of nuttx we see the support for SPI driver is available for

Re: SPI driver is not working in S32K144 EVB

2021-04-16 Thread Alan Carvalho de Assis
Hi Sathish, Are you using a supported S32K1xx board or a custom board? There are support to LPSPIx i then EVB boards directory, so I'm assuming it was tested/validated. Maybe someone from NXP could confirm/deny it. Do you have analyzed the SPI pins? if you don't implement the Chip Select logic

Re: SPI driver is not working in S32K144 EVB

2021-04-16 Thread Sathish Touch energy
> > >> Hello, >> We are trying to check SPI driver functionality for our application on >> NUTTX-10.0.0 baseline. >> On the supported platform link ( >> https://nuttx.apache.org/docs/latest/introduction/detailed_support.html#other-armv4) >> of nuttx we see the support for SPI driver is available

RE: IMXRT1064 and 2 Ethernet interfaces

2021-04-16 Thread David Sidrane
Hi Vadim , This sounds familiar.Please check if that code is a copy of the Kinetis driver. If so, see the changes that were done to it in https://github.com/apache/incubator-nuttx/pull/1273 David -Original Message- From: Вадим Ястребов [mailto:woody_haw...@mail.ru.INVALID] Sent:

Re: IMXRT1064 and 2 Ethernet interfaces

2021-04-16 Thread Gregory Nutt
I don't have any good input for your specific problem, but the dual Ethernet configuration was well tested in the past with the SAMA5Dx configurations.  Those boards have two Ethernet interfaces on board and no problems like your have been noted. Most testing used apps/examples/bridge: $

IMXRT1064 and 2 Ethernet interfaces

2021-04-16 Thread Вадим Ястребов
Hello everyone, I have encountered a problem related to initializing 2 Ethernet interfaces on IMXRT1064 and I was wondering if you have any idea where to look for solutions. Sometimes both interfaces work fine. Sometimes, when initializing the second interface with ifconfig followed by ifup,