some DRP examples with for example WUSB3801 for cc detection and role detection (IEC-347)

[savenlid]

Is your feature request related to a problem?

No response

Describe the solution you'd like.

Some examples where the wusb3801 ( or similar ) will detect the usb-c situation with help of cc-lines

and do full drp role.

if device is detected, turn on vbus.
and identify the device.

if a host is detected, instantiate the usb-ncm function.

preferably for the esp-p4.

I am myself on may way to do this.

Hardware with P4+WUSB3801 can be provided if you want.

Describe alternatives you've considered.

No response

Additional context.

No response

[github-actions]

Hi @savenlid! Please be aware that the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems. We hope that this message will help you until an Espressif Engineer looks at your issue.

---

Thank you for your detailed feature request regarding DRP (Dual Role Port) examples using the WUSB3801 for CC detection and role switching on ESP32-P4.

Current State in Espressif Documentation and Examples

Based on the available knowledge sources, there are currently no official Espressif examples or reference implementations specifically demonstrating the integration of the WUSB3801 (or similar USB Type-C CC controller) with the ESP32-P4 for full DRP role detection and switching. This includes scenarios such as:

• Using the WUSB3801 to detect the USB-C connection state and determine the port role (host/device).
• Automatically turning on VBUS when a device is detected.
• Identifying the connected device.
• Instantiating the USB-NCM (Network Control Model) function when a host is detected.

What Is Available

• The ESP32-P4 supports USB 2.0 Full-Speed OTG and has the necessary hardware and software support for both host and device roles, including CDC-NCM and CDC-ACM class drivers, as well as session and role negotiation protocols (SRP/HNP) at the controller level. However, these features are focused on the USB protocol layer and do not include reference designs for external CC logic or DRP switching using a chip like the WUSB3801 ESP32-P4 Technical Reference Manual.
• There are several USB host and device examples for ESP32-P4, including CDC-ACM, ECM, and NCM, but these assume the USB role is already determined and do not cover CC line or DRP logic (USB Host Examples, USB NCM Example).
• The technical reference manual describes the USB OTG controller's support for role switching and the relevant signals (e.g., ID pin, VBUS control), which could be used in conjunction with an external CC controller like the WUSB3801, but no software integration example is provided ESP32-P4 Technical Reference Manual.

Summary

I'm sorry, but there are currently no official Espressif examples or reference code that demonstrate full DRP role switching with a WUSB3801 (or similar) for CC detection and dynamic USB role assignment on ESP32-P4. The available examples focus on USB host/device functionality after the role is already established, and the technical documentation covers the necessary hardware features but not the integration with external CC logic.

If you proceed with your own implementation, you would need to:

• Interface the WUSB3801 with ESP32-P4 via I2C or GPIO to read CC status and determine the role.
• Use the ESP32-P4's USB OTG controller registers to switch between host and device modes as needed.
• Instantiate the appropriate USB stack (e.g., NCM device or host) based on the detected role.

If you are able to share your hardware and progress, it could be valuable for the community and may help Espressif consider adding such examples in the future.

If you need more information on the USB OTG controller or available USB class drivers, please refer to the ESP32-P4 Technical Reference Manual and the ESP-IDF USB Host API documentation.

[tore-espressif]

Hello @savenlid ,

providing better support for USB Type-C designs is currently one of our top priorities.
Internally, we work on development board based on FUSB302 and HUSB320 chips. We plan to add support for WUSB3801, TUSB320 and similar chips in the future.

We will keep this ticket updated once we have some new information

[savenlid]

Good news for me.
FYI: my PCBA with WUSB3801 is about 2 weeks away.
Turn-around time for PCBA is about 4weeks, 2 weeks PCB production and 2 weeks assembly.
Once I get it I will inform you of any success or failure, possibly sharing some code here.

I think the WUSB3801 is a $0.1 chip and FUSB302 is a $0.3 chip.
If FUSB302 contains any benefits, I would be interested.
Also to know presence of VUSB via such a chip instead of GPIO is nice.
The level will be a bit more defined.
Attached my current WUSB3801 implementation.
Ps / the ID pin is excessive / ds

P4-USB.pdf

[savenlid]

@tore-espressif

Using 2.0.0 i try to do NCM bring-up / tear-down repeatedly

Using the wusb3801 to help me detect the connects, disconnect and assert its as "SRC" connecting.
(SRC means a host is connecting and I need to be Sink /device)

It both does work and does not work.
It is usable, the NCM works, even 2:nd attach with error.

But gives this error on the 2:nd connect.
Meaning trying to bring up the 2:nd time.

E (46998) usb_phy: usb_new_phy(339): selected PHY is in use
E (46998) TinyUSB: tinyusb_driver_install(140): Install USB PHY failed
E (47008) usb-netif: usb_ip_init_default_config(192): ./main/usb_stack.c:192

I'm not sure what example-code to follow, I read your test-cases for NCM ( not ideal ).

My tear-down follows you example

tinyusb_net_deinit();
ESP_ERROR_CHECK(tinyusb_driver_uninstall());

But your test-case I assume is not repeating bring up / tear.-down multiple times.

[roma-jam]

Hi @savenlid,

could you please provide the part of the code where tinyusb driver is configured and installed?

[savenlid]

@roma-jam

Yes, of-course.
The code is, collected bits of info via google-fu. ( its in the quick-and-dirty-stage).
tried to upload as a file, did not work.
I did find a bug, so now the tear-down works,
Unfortunately the DHCP do not assign an ip any more after the first tear-down.

// First attach, works.
I (18639) TinyUSB: TinyUSB Driver installed on port 1
I (18649) esp_netif_lwip: DHCP server started on interface usb-wired with IP: 192.168.4.1
I (18919) esp_netif_lwip: DHCP server assigned IP to a client, IP is: 192.168.4.2

// tear down

// second attach DHCP don't assign an ip to my laptop.
I (209269) TinyUSB: TinyUSB Driver installed on port 1
I (209279) esp_netif_lwip: DHCP server started on interface usb-wired with IP: 192.168.4.1

// the bulk of the code:

typedef struct
{
esp_netif_t *esp_netif_p;
} ac_usb_ncm_t;

ac_usb_ncm_t ac_usb_ncm;

static esp_err_t netif_recv_callback(void *buffer, uint16_t len, void *ctx)
{
if (ac_usb_ncm.esp_netif_p)
{
void *buf_copy = malloc(len);
if (!buf_copy)
{
return ESP_ERR_NO_MEM;
}
memcpy(buf_copy, buffer, len);
return esp_netif_receive(ac_usb_ncm.esp_netif_p, buf_copy, len, NULL);
}
return ESP_OK;
}

void device_event_handler(tinyusb_event_t *event, void *arg)
{
switch (event->id) {
case TINYUSB_EVENT_ATTACHED:
// Device has been attached to the USB Host and configured
break;
case TINYUSB_EVENT_DETACHED:
// Device has been detached from the USB Host
break;
default:
break;
}
}

esp_err_t ac_usb_ncm_bring_up()
{

tinyusb_config_t config = TINYUSB_DEFAULT_CONFIG(device_event_handler);
// Run TinyUSB on the High-speed port
config.port = TINYUSB_PORT_HIGH_SPEED_0;
config.phy.skip_setup = false;    // 2.0.0

// .external_phy = false, // old
// .device_descriptor = &atlas_dev_default, // NS 250823, crash
ESP_RETURN_ON_ERROR(tinyusb_driver_install(&config), TAG, "%s:%d", FILE, LINE);

// Tiny-usb-netinit
// =============================================
unsigned int mac_tmp[6] = {};
sscanf(CONFIG_USB_NETIF_DEFAULT_MAC, "%02x:%02x:%02x:%02x:%02x:%02x",
            &mac_tmp[0], &mac_tmp[1], &mac_tmp[2],
            &mac_tmp[3], &mac_tmp[4], &mac_tmp[5]);
tinyusb_net_config_t _net_config = {
    // locally administrated address for the ncm device as it's going to be used internally
    // for configuration only
    .on_recv_callback = netif_recv_callback,
};
for (size_t i = 0; i < 6; i++)
{
    _net_config.mac_addr[i] = mac_tmp[i];
}

ESP_RETURN_ON_ERROR(tinyusb_net_init(&_net_config), TAG, "%s:%d", __FILE__, __LINE__);

// =====================================================================================
// The net-interface
esp_netif_ip_info_t _netif_usb_ip = {};

_netif_usb_ip.ip.addr = esp_ip4addr_aton(CONFIG_USB_NETIF_DEFAULT_IP);

// _netif_usb_ip.gw.addr = esp_ip4addr_aton(CONFIG_USB_NETIF_DEFAULT_GATEWAY);
_netif_usb_ip.gw.addr = esp_ip4addr_aton("127.0.0.1");
_netif_usb_ip.netmask.addr = esp_ip4addr_aton(CONFIG_USB_NETIF_DEFAULT_NETMASK);

// Definition of
// 1) Derive the base config (very similar to IDF's default WiFi AP with DHCP server)
esp_netif_inherent_config_t base_cfg = {
  .flags = ESP_NETIF_DHCP_SERVER | ESP_NETIF_FLAG_AUTOUP, // Run DHCP server; set the netif "ip" immediately
    .ip_info = &_netif_usb_ip,                              // Use the same IP ranges as IDF's soft AP
    .if_key = CONFIG_USB_NETIF_IF_KEY,                                  // Set mame, key, priority
    .if_desc = "usb ncm config device",
    .route_prio = 0
};  // was 30

ac_usb_ncm.esp_netif_p = netif_create(&base_cfg, NULL, NULL);  // ns 250911
esp_netif_action_start(ac_usb_ncm.esp_netif_p, 0, 0, 0);

uint8_t s_sta_mac[6] = {};
ESP_ERROR_CHECK(esp_read_mac(s_sta_mac, ESP_MAC_ETH));
ESP_ERROR_CHECK(esp_netif_set_mac(ac_usb_ncm.esp_netif_p, s_sta_mac));

return ESP_OK;

}

// void esp_netif_action_stop(void *esp_netif, esp_event_base_t base, int32_t event_id, void *data)

esp_err_t ac_usb_ncm_tear_down(void) // 250911
{

esp_netif_destroy(ac_usb_ncm.esp_netif_p); 
tinyusb_net_deinit();
ESP_ERROR_CHECK(tinyusb_driver_uninstall());

return ESP_OK;

}

[savenlid]

Hi again @roma-jam

after i hard-coded the ip on my laptop i could reach the web-server in the esp32-p4 even on 2nd attach, so the network is there. but DHCP just wants to work once.

If I never bring down the netif, DHCP will work ( continue to work ).
But that brings in a memory-leak, and errors when netif-cb cant send to usb anymore.
Periodically netif wants to send something, a beacon I guess.

[roma-jam]

Hi, @savenlid

thanks for the information. Right now it seems that the issue isn't related to the original one WUSB3801 for cc detection and role detection and isn't related to tinyusb_driver_uninstall();

It seems, that right now the problem is that it is not possible to have something like this:

ac_usb_ncm.esp_netif_p = netif_create(&base_cfg, NULL, NULL); 
esp_netif_action_start(ac_usb_ncm.esp_netif_p, 0, 0, 0);
...
esp_netif_destroy(ac_usb_ncm.esp_netif_p); 

// And then again
esp_netif_action_start(ac_usb_ncm.esp_netif_p, 0, 0, 0);

am I right? If yes, please, open the new issue, related exactly to this scenario.

[savenlid]

@roma-jam

FYI on the unrelated issue, I got it working.

you need to tear down dhcp-s explicitly.
err = esp_netif_dhcps_stop(esp_netif_p);
esp_netif_destroy(esp_netif_p);

destroy of the complete if still leaves dhcp-data-structures etc intact in memory.
possibly even allocated.
at the next connect it gets reused, and it was already "connected" , it saw no need to give a dhcp-adress again.

my personal opinion is that bring down the if should bring down associated stuff also.