Hello all:
I am interested in using the external SFLASH memory on the 43907 eval kit as a large buffer space and staging area for a bunch of packets yet to be sent. The eval kit has plenty of extra space to accommodate, but how should I go about this as to not overwrite all the other stuff in the flash mem?
Solved! Go to Solution.
Are you using CYW943907AEVAL1F? If yes, then the flash connected in EVK is only 8 MB which is already taken up the ota2 staging area. If you have added your own flash which has 32 MB of free space after the ota2_image staging area, then you can add your own defines in ota2_image_defines.mk (but don't change before the ota2 staging area, please add after that area) and check the wiced_apps.mk to understand how you can set a rule for "variable staging area", so that that the sflash_write application downloads according to the vacant memory location in sflash (might require some additional changes in standard_platform_targets.mk file as well).
I am not clear about the question. Staging area concept exists for ota2 image. If that's the case, as the staging area comes at the very end of flash layout, you don't have any risk of overwriting other stuff. You can update this OTA2_IMAGE_STAGING_AREA_SIZE macro (43xxx_Wi-Fi/platforms/CYW943907AEVAL1F/ota2_image_defines.mk) to a value of your choice based on your application.Please let me know if your question has some other implications.
Hi rroy​, you bring up a great point about the ota2 staging area. Before I get to my follow up questions I want to be a little more clear about my project:
So for example, say I wanted to allocate a 32MB section of the flash for this purpose. I guess my questions then are these:
Are you using CYW943907AEVAL1F? If yes, then the flash connected in EVK is only 8 MB which is already taken up the ota2 staging area. If you have added your own flash which has 32 MB of free space after the ota2_image staging area, then you can add your own defines in ota2_image_defines.mk (but don't change before the ota2 staging area, please add after that area) and check the wiced_apps.mk to understand how you can set a rule for "variable staging area", so that that the sflash_write application downloads according to the vacant memory location in sflash (might require some additional changes in standard_platform_targets.mk file as well).