Lines Matching +full:wi +full:- +full:fi
5 The SimpleLink Wi-Fi CC3235SF LaunchPad development kit (CC3235SF-LAUNCHXL)
6 highlights CC3235SF, a single-chip wireless microcontroller (MCU) with
16 Cortex-M4 MCU and a network processor MCU to run all Wi-Fi and
18 * 40-pin LaunchPad standard leveraging the BoosterPack ecosystem
19 * On-board accelerometer and temperature sensor
22 * BoosterPack plug-in module for adding graphical displays, audio
25 * XDS110-based JTAG emulation with serial port for flash programming
35 #. Applications MCU - an ARM |reg| Cortex |reg|-M4 Core at 80 MHz, with 256Kb RAM,
39 #. Network Coprocessor (NWP) - a dedicated ARM MCU, which completely
40 offloads Wi-Fi and internet protocols from the application MCU.
50 +-----------+------------+-----------------------+
53 | UART | on-chip | serial port-interrupt |
54 +-----------+------------+-----------------------+
55 | GPIO | on-chip | gpio |
56 +-----------+------------+-----------------------+
57 | I2C | on-chip | i2c |
58 +-----------+------------+-----------------------+
59 | SPI_0 | on-chip | Wi-Fi host driver |
60 +-----------+------------+-----------------------+
89 Before flashing and debugging the board, there are a few one-time board
99 with CMSIS-DAP" appearing at /dev/ttyACM1 and /dev/ttyACM0.
110 #. Ensure the XDS-110 emulation firmware is updated.
112 Download and install the latest `XDS-110 emulation package`_.
115 …<http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#updating-the-xds110-fi…
132 .. code-block:: console
134 export PATH=$ZEPHYR_SDK_INSTALL_DIR/sysroots/x86_64-pokysdk-linux/usr/bin/openocd:$PATH
144 .. code-block:: cmake
171 .. zephyr-app-commands::
180 .. code-block:: console
198 .. zephyr-app-commands::
201 :maybe-skip-config:
205 Wi-Fi Support
209 to Zephyr, and communicates over a dedicated SPI to the network co-processor.
210 It is available as a Zephyr Wi-Fi device driver in
217 to enable Wi-Fi.
223 SimpleLink provides a few rather sophisticated Wi-Fi provisioning methods.
225 "Fast Connect" policy is enabled, with one-shot scanning.
228 re-specify the SSID and password.
230 To connect to an AP, first run the Zephyr Wi-Fi shell sample application,
233 See :zephyr:code-sample:`wifi-shell`
235 Once the connection succeeds, the network co-processor keeps the AP identity in
236 its persistent memory. Newly loaded Wi-Fi applications then need not explicitly
237 execute any Wi-Fi scan or connect operations, until the need to change to a new AP.
242 The SimpleLink Wi-Fi driver provides socket operations to the Zephyr socket
244 SimpleLink Wi-Fi driver, by setting :kconfig:option:`CONFIG_NET_SOCKETS_OFFLOAD`
250 - setting both :kconfig:option:`CONFIG_NET_SOCKETS_SOCKOPT_TLS`
252 - using the TI Uniflash tool to program the required certificates and
254 Root-Certificate Catalog.
256 See :zephyr:code-sample:`sockets-http-get` and
260 See the document `Simplelink Wi-Fi Certificates Handling`_ for details on
266 .. target-notes::
269 http://www.ti.com/microcontrollers/simplelink-mcus/overview.html
277 .. _CC3x20/CC3x35 SimpleLink Wi-Fi and IoT Network Processor Programmer's Guide:
287 http://www.ti.com/tool/download/SIMPLELINK-CC32xx-SDK/2.40.01.01
292 .. _XDS-110 emulation package:
295 .. _Simplelink Wi-Fi Certificates Handling: