I saw the driver code of the w5500 on Nuttx, but I did not find any routine
using these driver codes. The w5500_initialize interface has not been called by
any code. Have any friends used the w5500 on nuttx?
int w5500_initialize(FAR struct spi_dev_s *spi_dev,
FAR const struc
Hello,
I did implement the w5500 device driver, but I am only using it on a
proprietary custom board at the moment. Alan is currently working on using
the w5500 with the STM32F4Discovery board. Apparently there are still some
issues, but I guess once those are resolved Alan will upstream the
res
Hi Prelude and Michael,
Yes, I'm adding W5500 to ESP32-S2 to test the SPI driver that I implemented
and because I was facing some issues on it I decided to test on
STM32F4Discovery board. I'll submit the PR to mainline.
I got it working, but for some reason it is stopping after 5 pings:
https://p
Hi all,
This thread has stalled for a while, so let's get back on track!
When we last discussed Graduation to TLP, we concluded that these items remain:
1. We need to review our STATUS file and fix any missing items:
https://incubator.apache.org/projects/nuttx.html
2. Ensure Mentors and IPMC ha
Trying to get the touchscreen on my board registered and tested. It *seems*
to register, and at one random point the touchscreen example app did report
something that looked useful but I now cannot make any sense of it.
The ADC itself is registered and the ADC example app works fine, but when I
+1 with tools/checkelease.sh:
./tools/checkrelease.sh --release 11.0.0-RC2
Downloading release files from
https://dist.apache.org/repos/dist/dev/incubator/nuttx/11.0.0-RC2/
gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created
gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created
gpg:
> The only clue I have is that g_inode_sem.holder is set to -1, which
intuitively seems wrong to me, but this is way beyond me at this time of my
NuttX journey!
The value -1 is not an error. It means that one thread is waiting to
take a count from the semaphore. The value of the semaphore was 0
SIOCGIFHWADDR gets the MAC address of an Ethernet interface.
E.g., something like this works on Linux:
strcpy(req.ifr_name, dev_name);
ret = ioctl(tmpsock, SIOCGIFHWADDR, &req);
if ((ret >= 0) && (req.ifr_hwaddr.sa_family == ARPHRD_ETHER))
{
memcpy((void *) mac_addr, (const void *
