compile command option collection and explanation
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
We have different options in the command input line for setting a global define. Below topic is a simple explanation for these inputs.
Actually you can also get most of them from the makefile. We also provide examples after wiced studio installed.
- snip.scan-BCM943362WCD4
Build for release
- snip.apsta-BCM943362WCD4-debug
Keyword:debug,
It means if you want to use Jtag or Jlink to have a debug, you need to add this option to get a debug image.
- snip.apsta-BCM943340WCD1-FreeRTOS-LwIP download run
Keyword : FreeRTOS-LwIP download run
It means use FreeRTOS system, LwIP network protocol and use the default USB-JTAG programming interface.
- demo.aws_iot.shadow-BCM94343W_AVN download_apps download run
Keyword:download_apps
If you want to download app into external flash by using SFLASH_WRITER_APP, you need to enable this option.
- snip.scan-BCM943362WCD4-FreeRTOS-LwIP-SDIO download run
Keyword: FreeRTOS-LwIP-SDIO
It means using FreeRTOS system, LwIP network protocol, SDIO interface for communication.
- snip.scan-BCM943362WCD4-ThreadX-NetX_Duo-SDIO download run
Keyword: ThreadX-NetX_Duo-SDIO
It means using Threadx OS system, Netx network protocol, SDIO interface communication.
- snip.scan-BCM943362WCD4-ThreadX-NetX-SPI download run
Keyword: ThreadX-NetX-SPI
It means using Threadx OS system, Netx network protocol, SPI communication interface.
- test.wifi_join-CYW954907AEVAL1F VERBOSE=1 download run
Keyword: VERBOSE=1
It means compile and download log will output with a more detailed logs.
we also have some other options like [JTAG=xxx] [no_dct] [JOBS=x] , below comments are important for input compile options:
Notes
* 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
Below are instructions for OTA2, please refer to the document carefully .
Key words are:
//Build an OTA2 Update Image suitable for upgrade server:
ota2_image
ota2_download
//Build an OTA2 Factory Reset Image suitable for manufacturing FLASHing of the device:
ota2_factory_image
ota2_factory_download
//It includes waf/ota2_bootloader, OTA2_factory_reset_image.bin, waf/ota2_failsafe, DCT, Application LUT, ota2_extract, and the application
ota2_manuf_image
ota2_manuf_download
// Below is for secure flash and version management.
APP_VERSION_FOR_OTA2_MAJOR=1
APP_VERSION_FOR_OTA2_MINOR=3
SECURE_SFLASH=1
keys=<keys_dir>
//show update from version of the SDK.
UPDATE_FROM_SDK=<bootloader_sdk>
//There were optional structures in the System DCT that are now always included. They are the Bluetooth (BT), Peer to Peer (P2P) and Over The Air 2 (OTA2) sub-structures. This information must also be designated so that the code knows which (if any) of the optional structures were used in the original application build DCT.
APP_USED_BT=1
APP_USED_P2P=1
APP_USED_OTA2=1
reference:
- Subscribe to RSS Feed
- Mark Article as New
- Mark Article as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Generally, running "make" without any argument should print the usage.
You probably want to improve the usage in Makefile because it does not explain everything (e.g. download_apps).