Hardy Griech

One point for improvement could be to change the webserver example to use NCM by default. This would improve compatibility over the several OSes, because NCM is supported by Linux,...

One more thing (out of topic): how about adding iperf to the webserver example to get a reference example for performance measurements?

Out of curiosity: have you ever compared with ECM/RNDIS? And have you done a bidirectional test with e.g. `for MSS in 100 800 1450; do iperf -c 192.168.14.1 -e -i...

yes, that is a valid point: RNDIS is correctly detected by Win10. But there are some drawbacks: RNDIS changes somehow routing of my Linux desktop (Debian) and also RNDIS works...

@Keval-Joshi-TI : "funny" thing, if you limit in lwiperf_tcp_client_send_more() (in lwiperf.c) the txlen_max to 700 (instead of TCP_MSS) then `iperf -c 192.168.14.1 -e -i 1 -M 100 -l 8192 -r`...

Perhaps our lwIP configuration is different. Essential parts of mine: ``` #define TCP_MSS (1500 - 20 - 20) // MTU minus header sizes (best value til now) #define TCP_SND_BUF (8...

Out of curiosity: have you checked my NCM PR (#2227)? It should perform better and more bugfree than the original NCM device.

Solution could be to not use a probe requiring Zadig. Zadig has TMO too many compatibility issues. Question: does the most recent picoprobe still require Zadig? If yes, I'ld suggest...

Thanks for clarification. I saw the keyword "Zadig" which creates immediate rash on my side. Now that I have read the last sentence of the description I understand the issue....

I do not want to advertise for my own probe, but which probe are you using? E.g. when doing `probe-rs benchmark --address 0x20000000 --chip nrf52840_xxaa --speed 10000` with the official...