[WICED-SDK-1.x -> WICED-SDK-2.x]
I see that some SDK-2.x example applications use wiced_init().
This API function includes code to do things like scanning that I will not need.
In the older SDK-1.x, we used wiced_management_init( COUNTRY, NULL ) .
What is the intent of the higher layer SDK-2.x API and is there any reason I cant use the old method to avoid unnecessary code?
Im also confused what this new WWD_ component is and why some of the previously existing functions have moved into it.Show Less
To define a WEP key in an application wifi_config_dct.h you must:
- #define CLIENT_AP_SECURITY WICED_SECURITY_WEP_PSK
- #define CLIENT_AP_PASSPHRASE "x00x05""x01x02x03x04x05" // For a 40-bit key
"x00" is the key index (ranging from 0 - 3)
"x05" is the length of the key being either x05 or x0D (for 40- or 104-bit WEP)
"x01x02x03x04x05" is the value of the WEP key (40-bit in this case)
NOTE: You can only define a single key in the DCT and for most WEP configurations the default key is index 0.Show Less
[WICED-SDK-2.2.1, MCU: STM32F205]
From what I see in code, the Broadcom External Flash talks over SPI2 and we are using SPI1 for our CGI External Flash.
When I look at SDK/Apps/waf/bootloader/bootloader.c and try to mimic the function of platform_restore_factory_app() but change the SPI port to our external flash (SPI 1) I see init_sflash and sflash_read.
init_sflash then calls sflash_platform_init with the requested SPI port. At that point the requested SPI port is ignored and the SFLASH (SPI 2) is always used. There is no way to change the spi port to our external flash.
Furthermore when you follow the sflash_read path, even if you were to manually update the SPI port to our SPI1, you eventually get to a call sflash_platform_send_recv_byte which then ignores the requested SPI port and uses the sflash spi, SPI 2.
There is no way for me to use these functions and supply a different SPI port. Can this be changed so that we can input the SPI we need? Is there some other function I am supposed to use to talk to SPI1?Show Less