mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-03 00:31:57 +00:00
407b49b35c
Using find_package to locate Zephyr.
Old behavior was to use $ENV{ZEPHYR_BASE} for inclusion of boiler plate
code.
Whenever an automatic run of CMake happend by the build system / IDE
then it was required that ZEPHYR_BASE was defined.
Using ZEPHYR_BASE only to locate the Zephyr package allows CMake to
cache the base variable and thus allowing subsequent invocation even
if ZEPHYR_BASE is not set in the environment.
It also removes the risk of strange build results if a user switchs
between different Zephyr based project folders and forgetting to reset
ZEPHYR_BASE before running ninja / make.
Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
|
||
|---|---|---|
| .. | ||
| boards | ||
| src | ||
| CMakeLists.txt | ||
| prj.conf | ||
| README.rst | ||
| reel_board.overlay | ||
| sample.yaml | ||
.. _wifi_sample: Wi-Fi sample ############ Overview ******** This sample allows testing Wi-Fi drivers for various boards by enabling the Wi-Fi shell module that provides a set of commands: scan, connect, and disconnect. It also enables the net_shell module to verify net_if settings. Building and Running ******************** Verify the board and chip you are targeting provide Wi-Fi support. For instance you can use TI's CC3220 by selecting the cc3220sf_launchxl board. .. zephyr-app-commands:: :zephyr-app: samples/net/wifi :board: cc3220sf_launchxl :goals: build :compact: Sample console interaction ========================== .. code-block:: console shell> wifi scan Scan requested shell> Num | SSID (len) | Chan | RSSI | Sec 1 | kapoueh! 8 | 1 | -93 | WPA/WPA2 2 | mooooooh 8 | 6 | -89 | WPA/WPA2 3 | Ap-foo blob.. 13 | 11 | -73 | WPA/WPA2 4 | gksu 4 | 1 | -26 | WPA/WPA2 ---------- Scan request done shell> wifi connect "gksu" 4 SecretStuff Connection requested shell> Connected shell>