Solutions
As illustrated in the figure, the Ameba is connected to the host MCU via interfaces such as UART/SPI, and the host MCU controls the network device and facilitates the transmission of network data using AT commands.
More Information
Connect Ameba SoC to the host as a Wi-Fi card through UART/SPI/SDIO/USB interfaces.
The following figure is the high-level block diagram for WHC FullMAC solution. The host MCU is responsible for running the TCP/IP protocol stack, enabling users to develop applications via socket interfaces on the host.
Linux host: Users can use standard wpa_supplicant and standard Linux Wi-Fi APIs.
P2P and NAN can be supported.
FreeRTOS host: Users can use Realtek Wi-Fi APIs.
More Information
Ameba operates as a Network Co-Processor (NCP), interfacing with the host MCU through UART/SPI/SDIO/USB communication channels to deliver full-stack networking capabilities. The architecture implements a dual-protocol stack design:
Compared to WHC FullMAC solution:
Layered Protocol Stack
SoC side: Full TCP/IP stack with auto-keep alive
Host side: Selective processing of critical application data (Traffic pre-filtering on SoC)
Power efficiency: Host wake-up frequency reduced in battery-powered scenarios (e.g., IP Camera)
Cross-Platform Compatibility
Unified development using Realtek Wi-Fi APIs across Linux and FreeRTOS systems
Flexible Development Modes
Development layer
Interface method
Kernel Space
Direct Socket API access
User Space
Netlink message
More Information
As shown in the figure below, Wi-Fi R-Mesh is a mesh network with tree topology used to extend the transmission distance of Wi-Fi, allowing stations that are relatively far from the AP to maintain a stable online status.
The well-designed Wi-Fi R-Mesh has the following advantages:
Application development unsensible
Path switch rapidly
High throughput
More stable
More Information