NetHub
NetHub
NetHub bridges device-side Wi-Fi capability to a selected host-link backend.
The current solution targets Wi-Fi SoCs such as BL616 / BL618 / BL616CL / BL618DG.
Current Status
| Item | Current status |
|---|---|
| Reference bring-up path | SDIO
|
| USB data path | device-side USB ECM backend implemented
|
| USB control transport | device-side USB ACM transport plumbing implemented
|
| SPI | not implemented |
| USER virtual channel | currently end-to-end in-tree on SDIO
|
| Low power | currently BL618DG only
|
| ATModule dependency | optional example composition only; not a NetHub core dependency |
Documentation Guide
- NetHubQuickBringup.md
- first-time bring-up and current support limits
- NetHubArchitecture.md
- current device and host architecture, profile boundaries, and APIs
- NetHubVirtualChannel.md
- current USER virtual-channel usage and limits
Current Conclusions
SDIOis the current in-tree reference path.USBdevice-side backend exists now and providesECM + ACM.SPIis still a stub.nethubcore exposes data-plane, control-path, and virtual-channel facades without directly depending onATModule.- The optional
ATModule + bflbwifid + bflbwifictrlflow is an example composition, not a hard requirement for NetHub data-path use cases.
In-Repo Reference Directories
examples/wifi/nethubcomponents/net/nethubbsp/common/msg_router/linux_host/userspace/nethub
Local Documentation Source
The in-repo documentation source is:
examples/wifi/nethub/docs/