c6_wifi_join Directory Reference

Directory dependency graph for c6_wifi_join:

Directories
	inc
	src

Detailed Description

#492: the first application on this board that takes a real network all the way up over the ESP32-C6. It associates the co-processor's Wi-Fi station with a bench access point through libs/ra8_c6link, runs a NetX Duo DHCP client over the C6 link driver to obtain a lease, and pings the leased gateway to show the path carries traffic.

c6_wifi_link stops at "the radio is up and has an address", which is exactly the state an IP driver starts from. This app is that IP driver. wifi_hal_join does the same job through the ra8_wifi facade.

The C6 is only a layer-2 bridge

It forwards 802.3 frames between the Wi-Fi netif and the host and does nothing else, so ARP, DHCP and ICMP all run on the RA8 over NetX Duo, exactly as the on-chip Ethernet apps do. The only new part is the link driver: it transmits by handing NetX's framed packet to the facade and receives through the facade's 802.3 callback on a dedicated poll worker. The C6 link is a single polled SPI transport, so transmit and the receive poll are serialised behind one mutex inside the driver.

PASS is gated on the DHCP lease, not on the ping. A lease is a full DISCOVER/OFFER/REQUEST/ACK exchange and already proves traffic flows in both directions; the ping is reported separately so that a gateway which filters ICMP cannot turn a real success into a failure.

Credentials

The firmware image and build graph contain no SSID or passphrase. After boot it prints ra8_net_provision: READY v1 and waits for one bounded runtime packet:

RA8NET1:<ssid_hex>:<psk_hex>:<url_hex>

This application ignores the optional URL field. The bench runner obtains the private values only at execution time and writes the packet over the debug UART. Firmware never echoes the packet and explicitly erases its receive, credential, station-configuration, and RPC staging buffers after the synchronous join.