I have traced the USB communication and it gets as far as it polling for new
data, but never gets any. It is all detected, instantiated properly, and so
forth – just doesn’t get data. So, as suggested, a protocol issue. The keyboard
I’m using reports itself as subclass BOOTIF and protocol KEYBO
RNDIS didn't work on Ubuntu for me (maybe need to find a driver), but CDC-ECM
is the right protocol for Linux I think.
My wish is to get RNDIS and CDC-ECM enabled (as a composite device I think) so
users have no need to download or install drivers for Windows or Linux. Mac
probably needs someth
I've been through 3 different Windows RNDIS drivers and they all behave the
same. One more variant to try tomorrow from some searching.
As you saw RNDIS is a Microsoft thing, and supposedly should just work. There's
probably a change that Windows made that has broken thingsjust for a change!
On 1/26/2023 1:52 PM, Gregory Nutt wrote:
Perhaps you need a driver on Windows? It appears so from a quick
Google where I find articles like:
https://learn.microsoft.com/en-us/windows-hardware/drivers/network/overview-of-remote-ndis--rndis-
https://supportcommunity.zebra.com/s/article/14
Perhaps you need a driver on Windows? It appears so from a quick Google
where I find articles like:
https://learn.microsoft.com/en-us/windows-hardware/drivers/network/overview-of-remote-ndis--rndis-
https://supportcommunity.zebra.com/s/article/14464?language=en_US
https://support.lenovo.com/
Hi Tim,
I think someone already commented of this issue using RNDIS on Windows.
It works fine with Linux (not sure about MacOS). So it will requires
some investigation to understand what is going on.
Try to use it connected to some Linux machine to confirm.
BR,
Alan
On 1/26/23, Tim Hardisty
I have CDC-ECM working just fine to my Linux machine. Ping now working too.
I cannot get RNDIS to work. It is seen by Windows and has an IP, but pings in
either direction fail.
If I ping from my board to the windows machine I get:
arp_send: ERROR: arp_wait failed: -110
Looks like arp is failin
Hi Russel,
Did you try to update the firmware version for the new board that is
not working?
Maybe ST changed the UART pins connected to virtual console
(/dev/ttyACM0) from a board to other.
BR,
Alan
On 1/26/23, Russell Haley wrote:
> Hi there community,
>
> I have access to a couple of STM32
Aha! - was missing the CONFIG_SYSTEM_PING!
I looked at the CONFIG_NETUTILS_PING help and it said it depended on NET_ICMP
and was selected by SYSTEM_PING...that confused me.
Thanks!
I can run ping now but it fails with:
ERROR: socket() failed: 93
That's "protocol not supported", so I will dig
Hi Tim,
Did you enable ICMP protocol?
Basically you need these flags:
CONFIG_NET_ICMP
CONFIG_NETUTILS_PING
CONFIG_SYSTEM_PING
BR,
Alan
On 1/26/23, Tim Hardisty wrote:
> Hi Alan - yes, I'm doing that to check what I missed for RNDIS (followed
> your video guide btw), but I can't explain why t
Hi Alan - yes, I'm doing that to check what I missed for RNDIS (followed your
video guide btw), but I can't explain why the PING app isn't available: any
thoughts on that?
> On 25/01/2023, 23:12, "Alan C. Assis" mailto:acas...@gmail.com>> wrote:
> When you had double about your configuration,
Hi there community,
I have access to a couple of STM32F446RE Nucleo boards and wanted to get
started with Nuttx. I was able to build the nucleo-f446re:nsh example code but
I had a great deal of trouble running it because I was not able to gain access
to the nsh shell.
I say was, because I eve
12 matches
Mail list logo
