Once you have the WICED IDE installed, you can import other WICED SDK .7z releases easily without reinstalling the IDE, or even changing the workspace. This method comes in handy when you have several releases you want to test and compare. You may keep several projects(SDKs) open in one workspace, but for simplicity we will start with closing the existing project.
**In the case you want to change the workspace in Eclipse and import the new SDK, please refer to the following blog post.
1. Right-click on your current project name in the IDE and select "Close Project". This will not modify or delete your files in anyway. It will, however, close the files you had open in the IDE, and you can choose to either save any changes that had been made. (This step is optional, you may have several projects open at once)
2. Extract the new WICED SDK .7z file to your chosen destination.
3. Click on the arrow next to the blue folder icon and select "Makefile Project with Existing Code"
4. Click on "Browse" and navigate to and then select the WICED SDK folder you created. The "Project Name" will be automatically filled in from the name in the "Existing Code Location" you choose. You may modify the name for clarity.
5. The new SDK will now be showing in the "Project Explorer" view.
6. You will have to create new target names when you import a new project. The make file will be linked to the previous project if you copy and paste existing targets from other projects, so it's best to create new ones.
In the "Make Target" window on the right, the "Hide Empty Folder" will be selected by default. You need to unselect this.
Right click on the project name and select "New".
This will allow you to make new targets. To obtain a complete list of build commands and options, enter the following text in the base WICED SDK directory on a command line:
For WICED SDK 3.3.1, the usage is as following:
Usage: make <target> [download] [run | debug] [JTAG=xxx] [no_dct]
One each of the following mandatory [and optional] components separated by '-'
* Application (apps in sub-directories are referenced by subdir.appname)
* Hardware Platform ()
* [RTOS] (ThreadX NoOS wiced_rtos_common.c FreeRTOS)
* [Network Stack] (wiced_network_common.c LwIP wiced_tcpip_common.c NoNS NetX NetX_Duo)
* [MCU-WLAN Interface Bus] (SDIO SPI)
Download firmware image to target platform
Reset and run an application on the target hardware (no download)
Connect to the target platform and run the debugger
JTAG interface configuration file from the tools/OpenOCD dirctory
Default option is BCM9WCD1EVAL1, direct JTAG option is jlink
DCT downloading is disabled and the DCT remains unmodified.
Only valid when the 'download' option is present
Generates a factory reset DCT
Shows the commands as they are being executed
Sets the maximum number of parallel build threads (default=4)
* Component names are case sensitive
* 'WICED', 'SDIO', 'SPI' and 'debug' are reserved component names
* Component names MUST NOT include space or '-' characters
* Building for release is assumed unless '-debug' is appended to the target
* Some platforms may only support a single interface bus option
Build for Release
Build, Download and Run using the default USB-JTAG programming interface
make snip.scan-BCM943362WCD4 download run
Build for Debug
Build, Download and Debug using command line GDB
make snip.scan-BCM943362WCD4-debug download debug
Reset and run an application on the target hardware
Clean output directory
Build a Factory Reset image for the SPI serial flash
make snip.ping-BCM943362WCD4 OTA=waf.ota_upgrade SFLASH=app-dct-ota-download
where: [OTA]=<OTA application build string>
Build string options are App name, RTOS and TCP stack ONLY
app : Add the application to the image
dct : Add the DCT to the image
ota : Add the OTA application to the image
download : Download the image after creation
That was it! Enjoy using your new SDK