I'm trying to initialize a new sflash chip on an ISM43340. Reading the community content, I was able to determine how to add the flash chip and size to the Wiced configuration.
However, determining how to initialize the sflash chip for the first time, took several days of digging, and I'm not sure it's the correct change or in the proper place.
=== Solution ?? ===
The line below was added to initialize the sflash when running the make: snip.sflash_write-.
- Is this the correct change? Is this the correct placement?
../43xxx_Wi-Fi/platforms/ISM43340_M4G_L44/ISM43340_M4G_L44.mk
RESOURCES_LOCATION ?= RESOURCES_IN_WICEDFS
=== Fix Attempts ===
The first attempt was to run snip.ota_fr-ISM43340_M4G_L44 because that's what the documentation suggests to use to flash a new OTA app file. However, that failed because the wiced_apps_common.c / wiced_apps_get_size code isn't designed to detect an uninitialized sflash chip.
When building the sflash_write, the filesystem.bin file wasn't being generated nor was the sflash being initialized. See below for the missing messages. It took a couple of days to root cause the problem and find a possible solution. BTW, this sflash initialization worked fine out of the box for the eval board: CYW943907AEVAL1F, but not for the ISM43340.
=== wiced_apps_common.c / wiced_apps_get_size code improvement? ===
There was no indication of a problem when running the http://192.168.10.1/wiced_ota_server/upgrade.html that there was a problem with the sflash. The wiced_apps_get_size() code essentially went into a nearly infinite loop because the entire chip was set to all 1s. It seems feasible to add a code check to prevent this problem. The chip being used was (MX25U1633FM2I) apparently factory initialized to all 1s, because the error eventually found in debugging that (wiced_apps_get_size) method was reading all 1s for the app_header.count field. That is, under the assumption that all sflash chips are either factory initialized to all 1s or all zeros.... perhaps a code check would be helpful.
===wiced_apps_common.c / wiced_apps_get_size code suggested change ===
wiced_result_t wiced_apps_get_size( const image_location_t* app_header_location, uint32_t* size ) {
...
WICED_VERIFY( init_sflash( &sflash_handle, PLATFORM_SFLASH_PERIPHERAL_ID, ...));
WICED_VERIFY( sflash_read( &sflash_handle, app_header_location->detail.external_fixed.location, .......));
// code change here suggested checking for 255 or 0, which will be an error 99.999999% of the time
if (app_header.count > 254 || app_header.count == 0) return ERR_CODE_SFLASH_NOT_INITIALIZED;
=== The messages below would NOT appear in the make/build log until after adding the make file line as mentioned above
(RESOURCES_LOCATION ?= RESOURCES_IN_WICEDFS) ====
16:20:54.367 -> NO Support Range Erase Command!!
16:21:05.562 -> Waiting for command
............
