Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
It's important to understand that WICED™ generally indicates a black box module (simple external serial interface expected) where a Cypress wireless radio is used in conjunction with a small MCU combined with a lightweight RTOS like FreeRTOS or ThreadX. Cypress really only makes the chips that go in these production/certified partner modules. In addition, we produce an SDK and a Dev Kit customers can use for development. However, our module partners (see table in the 2016 IoT Solutions Guide), which build the actual production modules you would use, often will also supply their own development boards and lower barrier to entry SW development environments.
In addition to WICED, we also have partners that support Linux "Radio Only" modules. For these modules, one develops on a higher end Cortex A type processor and uses a Linux Driver package to interface (normally SDIO) to the radio module which is provided by the CPU manufacture, which in most cases is NXP/Freescale i.MX based.
The gray area between these two is that some module partners will actually support development on your own MCU using the WICED SW stack. Vendors like Inventek Systems refers to this type of implementation as "Virtual WICED"
Thank you for clarification the background of the WICED.
So regarding to my first question I guess the SW produced with the help of WICED SDK will be actually executed in WICED module's MCU. In case of production the WICED module will be replaced with the partners module and I will need to adjust my application software (built on top of SDK) to this partners module interface.
On other hand, in case I needed to built my own platform ( == partner module) I would like to know whether I can adjust also the firmware in WICED chip's controller (M3 core in aforementioned chips) using the SDK, or it is solely in control of Cypress developers and burned into ROM memory.