Configuration:
- Stellaris (LM4F120XL) Launchpad
- BoosterPackEM adapter (modified to connect GPIOA - GPIO2)
- CCS v5 updated to 5.0.6, required increasing the stack size to even get the example code to work - that cost me a GOB of time to figure that one out.
- CC3000 SDK, updated with the last week.
- CC3000EM - stock jumper settings
- System Patched with 1.19
- Basic WiFi Application, modified to include dumping patch level and scanning for APs
- Stock, Non-Rooted Google Nexus 7 Tablet
- Stock (Precompiled) Android App
Test / Results
- Start Firmware
- Scan for access points, see the access points I expect, stop scan
- Dump patch level, verifying 1.19
- On Android Tablet, start CC3x Config Tool
- Wait for access points to display
- Pick the desired access point, Enter WPA2 Key, click "Configure CC3x for {SSID}
- On terminal window to Launchpad, start SimpleConfig
- Wait. Wait.. Wait...
- Finally break application, find it in the loop waiting for SimpleConfig to complete.
- AFAIK, no callbacks have occurred outside of the keep alive. I know that's happening, but the one that ends SimpleConfig does not fire.
- After SimpleConfig, nothing works - API to retrieve patch level fails, scanning for APs returns nothing.
- Problem persists after a POR.
- Repatching restores operation of patch level and scan APIs.
Troubleshooting:
- Tried switching order of starting simpleconfig on Android and Launchpad
- Tried invoking simpleconfig many times on Android while Launchpad stuck waiting.
- Tried skipping scan/patch apis before starting SimpleConfig
I have Saleae logic analyzer traces of both SImpleConfig and recovery by Re-Patching, but don't have a good way to interpret them.
TI, any ideas? I'm trying to sick as close to the supplied example before venturing off on my own, but I can't even get the stock stuff from TI to work properly - and there's no feedback as to why things are failing. This doesn't give me warm fuzzies about what my customers would experience if I can't get the demo to work out of the box, using all TI stuff.
Also on the CC3x Android App, a scrolling log of what it's doing (with timestamps) would be MUCH better.