Lines Matching +full:zephyr +full:- +full:sdk +full:-
1 .. zephyr:board:: cc3220sf_launchxl
5 The SimpleLink Wi-Fi CC3220SF LaunchPad development kit (CC3220SF-LAUNCHXL)
6 highlights CC3220SF, 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.
47 Zephyr has been ported to the Applications MCU, with basic peripheral
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 +-----------+------------+-----------------------+
64 For consistency with TI SimpleLink SDK and BoosterPack examples,
75 `CC3220 SDK`_ on Windows and Linux using TI tools: Code Composer
82 Note that zephyr.bin produced by the Zephyr SDK may not load via
83 UniFlash tool. If encountering difficulties, use the zephyr.elf
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…
127 :ref:`installing the latest Zephyr SDK instructions <toolchain_zephyr_sdk>`.
132 .. code-block:: console
134 export PATH=$ZEPHYR_SDK_INSTALL_DIR/sysroots/x86_64-pokysdk-linux/usr/bin/openocd:$PATH
137 the one in the Zephyr SDK. If for some reason you wish to continue to use
144 .. code-block:: cmake
162 board can be built, flashed, and debugged with openocd and gdb per the Zephyr
171 .. zephyr-app-commands::
180 .. code-block:: console
186 When using OpenOCD from Zephyr SDK to flash the device, you may notice
198 .. zephyr-app-commands::
201 :maybe-skip-config:
205 Wi-Fi Support
208 The SimpleLink Host Driver, imported from the SimpleLink SDK, has been ported
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.
224 To keep it simple for Zephyr development and demos, the SimpleLink
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
243 offload point, enabling Zephyr BSD socket API calls to be directed to the
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
284 .. _CC3220 SDK:
285 http://www.ti.com/tool/download/SIMPLELINK-CC3220-SDK
290 .. _XDS-110 emulation package:
293 .. _Simplelink Wi-Fi Certificates Handling: