Network with RNDIS, CDC-ECM

[torstenmay]

Hi,

I'm thinking about using an ESP32-S2 and wondering what this statement really means:

• Network with RNDIS, CDC-ECM (work in progress)
• it can be found on the main Tinyusb website

Does it mean all network over USB class implementations are work in progress or just the CDC-ECM?
Is anyone using the drivers already?
Is there an overview what might be missing?

Thanks Torsten

[hathach]

The whole net driver is WIP, which mean API can change significantly later on if needed. You can try out the example here https://github.com/hathach/tinyusb/tree/master/examples/device/net_lwip_webserver

But it doesn't have freeRTOS to run with esp32s2. related article on rp2040 https://www.hackster.io/news/hermann-stamm-wilbrandt-gives-the-raspberry-pi-pico-web-server-client-over-usb-capabilities-74104c572db1

[hathach]

@torstenmay that is great to hear, you could follow the CMAKEList.txt examples of cdc_msc_freertos / hid_composite_freertos. All of these end with _freertos can be compiled and run with esp32s2 (just run make BOARD=espressif_saola_1 with all then flash target, It should just work. You need to set the OS to freertos, for stack to properly use the correct freeRTOS queue API without hacking.

#define CFG_TUSB_OS               OPT_OS_FREERTOS

[torstenmay]

Hi @hathach

i checked the two example projects and adapted some of the really ugly hacks. :)

However the network example has much more dependencies like esp_netif and lwip.

Just to give you some ideas what I have changed please have a lool here: esp32s2.diff.txt
I enabled to lwip prints and attached to output here: log.txt

The result is that a new network interface will show up:

Please have a look into the patch and give me your opinion about my modifications.

Regards Torsten

[hathach]

The diff txt is not too useful for discusion, for code discuss, PR is the best way to do. Could you make an draft PR with your webserver example changes, it is not meant to be merged, but we could use the github file changes for suggestion/discusion.

[torstenmay]

Hi @hathach

I opened the draft PR:
#809

Hope i did correctly as this is my first draft PR and still learning how to do it.

Regards Torsten

[hathach]

Thank you for the PR. I will check it out whenever I could.

[chegewara]

Hi,
i know it is kind of old topic, but i have question.
Espressif is having cdc-ncm example that lats us running net_lwip_webserver like code here:
https://github.com/espressif/esp-idf/tree/master/examples/network/sta2eth

My question is, because it is not clear to me, which stack setup ethernet speed detected by OS?

• is it tinyusb
• is it lwip

Im asking, because esp32P4 has USB HS and ethernet speed detected on my ubuntu is only 10Mbits.

Thanks

[HiFiPhile]

If you use NCM driver it's defined here

tinyusb/src/class/net/ncm_device.c

Line 167 in eda3cce

tu_static struct ncm_notify_t ncm_notify_speed_change = {

But in any case the reported speed is just an indication, won't affect the real speed at all.

[chegewara]

Actually im not asking about USB port speed (FS vs HS). I am asking about ethernet device speed, which is 10, 100, 1000Mbits/s.

Thanks

[HiFiPhile]

Yes I know you are talking about Ethernet speed.
With NCM driver reported Ethernet speed change according to USB speed.

With older ECM driver it's defined here:

tinyusb/src/class/net/ecm_rndis_device.c

Line 86 in eda3cce

tu_static const struct ecm_notify_struct ecm_notify_csc =

[chegewara]

Thank you very much. It is exactly what i am looking for, just espressif component seems to be outdated and is using one speed (10Mb)

tu_static struct ecm_notify_struct ncm_notify_speed_change =
{
    .header = {
        .bmRequestType_bit = {
          .recipient = TUSB_REQ_RCPT_INTERFACE,
          .type      = TUSB_REQ_TYPE_CLASS,
          .direction = TUSB_DIR_IN
        },
        .bRequest = CDC_NOTIF_CONNECTION_SPEED_CHANGE,
        .wLength = 8,
    },
    .downlink = 10000000,
    .uplink = 10000000,
};

https://github.com/espressif/tinyusb/blob/33d36cb23d6f8415d0e8a09d15a5e6cd8c0a6d05/src/class/net/ncm_device.c#L223-L236

Thanks