2 of 2 people found this helpful
The Wiced Soft AP Libraries are still not exposed on the Mbed platform. The work on getting them integrated is still in progress and will be made available soon.
If there is anything I can do to expedite this process, please sign me up. I'll code, document, test, whatever you need. I have a box full of these CY8CPROTO-062-4343W kits sitting here on my bench waiting to come to life.
I would assume the necessary firmware blob for the D11 core has everything needed during DHD init. Hopefully the WICED library is complete too. Then as you say, we just need to expose the function calls and we should be in business.
Looking through all the WICED code, seems to me the biggest hurdle is ensuring all the RTOS statements are converted over to mbed OS. One could probably follow the API path set by the Odin-W2 to make everything compliant.
One other thing that needs to be looked at: The latest version of mbed OS 5.12.3 seems to chew up too much memory for this CY8CPROTO-062-4343W board. That will need to be resolved before new code gets pushed in.
The firmware here is compatible with the WWD driver of Wiced ecosystem.
>>This is really frustrating because I can see all the WWD code in WICED Studio that surely should be able to properly communicate with this WiFi chip and configure it as needed.
What you are inferring is absolutely true. They is no issue in LBEE5KL1DX running as SoftAp. Its just that the middleware that ties the mbed headers to wwd driver apis for softap is not yet been pushed to mbed mainline that is open.
>>One could probably follow the API path set by the Odin-W2 to make everything compliant.
Yes you could do that but The softap APIs have to be tied to the mbed top layer stack libraries(libwiced_driver.a). This effort is already in progress and should be pushed into mainline soon.