Lines Matching +full:directory +full:- +full:to +full:- +full:scan
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
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 .. zephyr:board-supported-hw::
55 the I2C driver defaults to I2C_BITRATE_FAST mode (400 kHz) bus speed
69 instructions on installation of tools, and how to flash the board using
77 prefer command line tools to an IDE.
79 Before flashing and debugging the board, there are a few one-time board
80 setup steps to follow.
86 #. Jumper SOP[2..0] (J15) to [010], and connect the USB cable to the PC.
89 with CMSIS-DAP" appearing at /dev/ttyACM1 and /dev/ttyACM0.
100 #. Ensure the XDS-110 emulation firmware is updated.
102 Download and install the latest `XDS-110 emulation package`_.
105 …<http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#updating-the-xds110-fi…
110 #. Switch Jumper SOP[2..0] (J15) back to [001].
119 After the installation, add the directory containing the OpenOCD executable
120 to your environment's PATH variable. For example, use this command in Linux:
122 .. code-block:: console
124 export PATH=$ZEPHYR_SDK_INSTALL_DIR/sysroots/x86_64-pokysdk-linux/usr/bin/openocd:$PATH
126 If you had previously installed TI OpenOCD, you can simply switch to use
127 the one in the Zephyr SDK. If for some reason you wish to continue to use
130 :zephyr_file:`boards/ti/cc3220sf_launchxl/board.cmake` to point the build
131 to the paths of the OpenOCD binary and its scripts, before
134 .. code-block:: cmake
143 which prepends a debug header enabling the flash to persist over
159 To build and flash an application, execute the following commands for <my_app>:
161 .. zephyr-app-commands::
168 To see program output from UART0, connect a separate terminal window:
170 .. code-block:: console
174 Then press the reset button (SW1) on the board to run the program.
176 When using OpenOCD from Zephyr SDK to flash the device, you may notice
179 resets the network processor. You would need to manually hit the reset button
180 on the board to properly reset the device after flashing.
185 To debug a previously flashed image, after resetting the board, use the 'debug'
188 .. zephyr-app-commands::
191 :maybe-skip-config:
195 Wi-Fi Support
199 to Zephyr, and communicates over a dedicated SPI to the network co-processor.
200 It is available as a Zephyr Wi-Fi device driver in
206 Set :kconfig:option:`CONFIG_WIFI_SIMPLELINK` and :kconfig:option:`CONFIG_WIFI` to ``y``
207 to enable Wi-Fi.
213 SimpleLink provides a few rather sophisticated Wi-Fi provisioning methods.
214 To keep it simple for Zephyr development and demos, the SimpleLink
215 "Fast Connect" policy is enabled, with one-shot scanning.
216 This enables the cc3235sf_launchxl to automatically reconnect to the last
217 good known access point (AP), without having to restart a scan, and
218 re-specify the SSID and password.
220 To connect to an AP, first run the Zephyr Wi-Fi shell sample application,
221 and connect to a known AP with SSID and password.
223 See :zephyr:code-sample:`wifi-shell`
225 Once the connection succeeds, the network co-processor keeps the AP identity in
226 its persistent memory. Newly loaded Wi-Fi applications then need not explicitly
227 execute any Wi-Fi scan or connect operations, until the need to change to a new AP.
232 The SimpleLink Wi-Fi driver provides socket operations to the Zephyr socket
233 offload point, enabling Zephyr BSD socket API calls to be directed to the
234 SimpleLink Wi-Fi driver, by setting :kconfig:option:`CONFIG_NET_SOCKETS_OFFLOAD`
235 to ``y``.
240 - setting both :kconfig:option:`CONFIG_NET_SOCKETS_SOCKOPT_TLS`
241 and :kconfig:option:`CONFIG_TLS_CREDENTIAL_FILENAMES` to ``y``,
242 - using the TI Uniflash tool to program the required certificates and
243 keys to the secure flash filesystem, and enabling the TI Trusted
244 Root-Certificate Catalog.
246 See :zephyr:code-sample:`sockets-http-get` and
250 See the document `Simplelink Wi-Fi Certificates Handling`_ for details on
256 .. target-notes::
259 http://www.ti.com/microcontrollers/simplelink-mcus/overview.html
267 .. _CC3x20/CC3x35 SimpleLink Wi-Fi and IoT Network Processor Programmer's Guide:
277 http://www.ti.com/tool/download/SIMPLELINK-CC32xx-SDK/2.40.01.01
282 .. _XDS-110 emulation package:
285 .. _Simplelink Wi-Fi Certificates Handling: