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)
Its standard practice at my company to have a "boot-up" app run diagnostics on a system before jumping to the main App located at a higher ROM address. We have a wiced app proted to uVelocity that works with a BCM43362 when the wiced App is the first thing executed on start up, meaning, the app is at the base ROM address for the processor. (STM32F415). When we run the boot-up app first, and then jump to the wiced app, which is linked to a higher memory address, the wiced app is unable to communicated over SDIO with the BCM43362.
Has anyone linked their wiced app to a higher address and had it work? We are trying to make sure that there is not some memory locality dependancy hidden somehwere in the wiced libraries.
We did verify that is was not a case of the boot-up app leaving RAM in a bad or unclean state, as we reset the whole internal RAM to 0s before running main in our wiced APP.
I should clarify, the Pin PB8 was used for WL_GPIO6 in our system.Toggling this pin (WL_GPIO6) seems to cause the BCM43362 to stop talking over SDIO. Normally we do not touch this pin, and everything works fine. Its a bit odd that toggling this pin, before wiced was initialized, caused wiced to fail initialization over the SDIO.