README.md 5.62 KB
Newer Older
1
2
# Build Instructions for the CC3200

3
Currently the CC3200 port of MicroPython builds under Linux and OSX **but not under Windows**.
4
5
6
7
8
9
10
11
12
13
14
15

The tool chain required for the build can be found at <https://launchpad.net/gcc-arm-embedded>.

In order to download the image to the CC3200 you will need the CCS_Uniflash tool from TI, which at this 
moment is only available for Windows, so, you need Linux/OSX to build and Windows to flash the image.

## To build an image suitable for debugging:

In order to debug the port specific code, optimizations need to be disabled on the 
port file (check the Makefile for specific details). You can use CCS from TI.
Use the CC3200.ccxml file supplied with this distribution for the debuuger configuration. 
```bash
16
make BTARGET=application BTYPE=debug BOARD=LAUNCHXL
17
18
19
```
## To build an image suitable to be flashed to the device:
```bash
20
make BTARGET=application BTYPE=release BOARD=LAUNCHXL
21
22
23
```
## Building the bootloader
```bash
24
make BTARGET=bootloader BTYPE=release BOARD=LAUNCHXL
25
26
```

27
## Regarding old revisions of the CC3200-LAUNCHXL
28
First silicon (pre-release) revisions of the CC3200 had issues with the ram blocks, and MicroPython cannot run
29
30
there. Make sure to use a **v4.1 (or higer) LAUNCHXL board** when trying this port, otherwise it won't work.

31
## Flashing the CC3200
32
- Make sure that you have built both the *bootloader* and the *application* in **release** mode.
33
34
- Make sure the SOP2 jumper is in position.
- Open CCS_Uniflash and connect to the board (by default on port 22). 
35
- Format the serial flash (select 1MB size in case of the CC3200-LAUNCHXL, 2MB in case of the WiPy, leave the rest unchecked).
36
- Mark the following files for erasing: `/cert/ca.pem`, `/cert/client.pem`, `/cert/private.key` and `/tmp/pac.bin`.
37
- Add a new file with the name of /sys/mcuimg.bin, and select the URL to point to cc3200\bootmgr\build\<BOARD_NAME>\bootloader.bin.
38
- Add another file with the name of /sys/factimg.bin, and select the URL to point to cc3200\build\<BOARD_NAME>\mcuimg.bin.
39
- Click "Program" to apply all changes.
40
- Flash the latest service pack (servicepack_1.0.0.10.0.bin) using the "Service Pack Update" button.
41
42
43
44
45
46
47
- Close CCS_Uniflash, remove the SOP2 jumper and reset the board.

## Playing with MicroPython and the CC3200:

Once the software is running, you have two options to access the MicroPython REPL:

- Through telnet. 
48
  * Connect to the network created by the board (as boots up in AP mode), **ssid = "wipy-wlan", key = "www.wipy.io"**.
49
50
51
52
53
    * You can also reinitialize the WLAN in station mode and connect to another AP, or in AP mode but with a
      different ssid and/or key.
  * Use your favourite telnet client with the following settings: **host = 192.168.1.1, port = 23.**
  * Log in with **user = "micro" and password = "python"**

54
55
56
57
58
59
60
61
62
63
64
65
66
- Thru UART (serial).
  * This is enabled by default in the standard configuration, for UART0 (speed 115200).
  * For CC3200-LAUNCHXL, you will need to configure Linux `ftdi_sio` driver as described
    in the [blog post](http://www.achanceofbrainshowers.com/blog/tech/2014/8/19/cc3200-development-under-linux/).
    After that, connecting a board will create two `/dev/ttyUSB*` devices, a serial
    console is available on the 2nd one (usually `/dev/ttyUSB1`).
  * WiPy doesn't have onboard USB-UART converter, so you will need an external one,
    connected to GPIO01 (Tx) and GPIO02 (Rx).
  * Usage of UART port for REPL is controlled by MICROPY_STDIO_UART setting (and
    is done at the high level, using a suitable call to `os.dupterm()` function
    in boot.py, so you can override it at runtime regardless of MICROPY_STDIO_UART
    setting).

67
68
The board has a small file system of 192K (WiPy) or 64K (Launchpad) located in the serial flash connected to the CC3200. 
SD cards are also supported, you can connect any SD card and configure the pinout using the SD class API.
69
70
71
72
73
74
75
76
77
78
79

## Uploading scripts:

To upload your MicroPython scripts to the FTP server, open your FTP client of choice and connect to:
**ftp://192.168.1.1, user = "micro", password = "python"**

I have tested the FTP server with **FileZilla, FireFTP, FireFox, IE and Chrome,** other clients should work as well, but I am 
not 100% sure of it.

## Upgrading the firmware Over The Air:

80
OTA software updates can be performed through the FTP server. After building a new **mcuimg.bin** in release mode, upload it to:
81
82
`/flash/sys/mcuimg.bin` it will take around 6s (The TI simplelink file system is quite slow because every file is mirrored for
safety). You won't see the file being stored inside `/flash/sys/` because it's actually saved bypassing FatFS, but rest assured that
83
84
85
86
the file was successfully transferred, and it has been signed with a MD5 checksum to verify its integrity. 
Now, reset the MCU by pressing the switch on the board, or by typing:

```python
87
88
import machine
machine.reset()
89
90
```

91
92
93
94
95
96
97
98
99
100
There's a script which automates this process from the host side:

- Make sure the board is running and connected to the same network as the computer.

```bash
make BTARGET=application BTYPE=release BOARD=LAUNCHXL WIPY_IP=192.168.1.1 WIPY_USER=micro WIPY_PWD=python deploy-ota
```

If `WIPY_IP`, `WIPY_USER` or `WIPY_PWD` are omitted the default values (the ones shown above) will be used.

101
102
103
104
105
106
107
### Note regarding FileZilla:

Do not use the quick connect button, instead, open the site manager and create a new configuration. In the "General" tab make 
sure that encryption is set to: "Only use plain FTP (insecure)". In the Transfer Settings tab limit the max number of connections 
to one, otherwise FileZilla will try to open a second command connection when retrieving and saving files, and for simplicity and 
to reduce code size, only one command and one data connections are possible.