Lines Matching +full:directory +full:- +full:to +full:- +full:scan
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
21 * UART through USB to PC
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,
36 and access to external serial 4MB flash with bootloader and peripheral
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 +-----------+------------+-----------------------+
65 the I2C driver defaults to I2C_BITRATE_FAST mode (400 kHz) bus speed
79 instructions on installation of tools, and how to flash the board using
87 prefer command line tools to an IDE.
89 Before flashing and debugging the board, there are a few one-time board
90 setup steps to follow.
96 #. Jumper SOP[2..0] (J15) to [010], and connect the USB cable to the PC.
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…
120 #. Switch Jumper SOP[2..0] (J15) back to [001].
129 After the installation, add the directory containing the OpenOCD executable
130 to your environment's PATH variable. For example, use this command in Linux:
132 .. code-block:: console
134 export PATH=$ZEPHYR_SDK_INSTALL_DIR/sysroots/x86_64-pokysdk-linux/usr/bin/openocd:$PATH
136 If you had previously installed TI OpenOCD, you can simply switch to use
137 the one in the Zephyr SDK. If for some reason you wish to continue to use
140 :zephyr_file:`boards/ti/cc3220sf_launchxl/board.cmake` to point the build
141 to the paths of the OpenOCD binary and its scripts, before
144 .. code-block:: cmake
153 which prepends a debug header enabling the flash to persist over
169 To build and flash an application, execute the following commands for <my_app>:
171 .. zephyr-app-commands::
178 To see program output from UART0, connect a separate terminal window:
180 .. code-block:: console
184 Then press the reset button (SW1) on the board to run the program.
186 When using OpenOCD from Zephyr SDK to flash the device, you may notice
189 resets the network processor. You would need to manually hit the reset button
190 on the board to properly reset the device after flashing.
195 To debug a previously flashed image, after resetting the board, use the 'debug'
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
216 Set :kconfig:option:`CONFIG_WIFI_SIMPLELINK` and :kconfig:option:`CONFIG_WIFI` to ``y``
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.
226 This enables the cc3220sf_launchxl to automatically reconnect to the last
227 good known access point (AP), without having to restart a scan, and
228 re-specify the SSID and password.
230 To connect to an AP, first run the Zephyr Wi-Fi shell sample application,
231 and connect to a known AP with SSID and password.
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`
245 to ``y``.
250 - setting both :kconfig:option:`CONFIG_NET_SOCKETS_SOCKOPT_TLS`
251 and :kconfig:option:`CONFIG_TLS_CREDENTIAL_FILENAMES` to ``y``,
252 - using the TI Uniflash tool to program the required certificates and
253 keys to the secure flash filesystem, and enabling the TI Trusted
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
285 http://www.ti.com/tool/download/SIMPLELINK-CC3220-SDK
290 .. _XDS-110 emulation package:
293 .. _Simplelink Wi-Fi Certificates Handling: