I have a CC1310 application that boots and runs in the following situations:
- When running on the CC1310 launchpad, under debug from Code Composer, running through the on-board debug system (the XDS110 system running in the MSP432 on the latest version of the LaunchPad).
- When running on the CC1310 launchpad, after reset or power-on, without connection to Code Composer, with power in through the micro-SD. I think that the XDS110 isn't doing anything debuggish in this case (because I'm not debugging through Code Composer) though I'd be interested in hearing if that's not correct.
- When running on a production board, under debug from Code Composer, or immediately upon flashing the image from Code Composer (does Code Composer) strobe the reset pin?) In this case the XDS110 is the same one, on the same launchpad, but disconnected from the on-LaunchPad CC1310 (by removing all the jumper to the MCU side of the Launchpad) and connected to the production board from the power, ground, RST, TMS, and TCK leads from the debugger side of the LaunchPad. The processor on the production board debugs nicely, and the program runs great, as long as the program is started in the debugger.
But...
When started independent of the debugger (power and ground), the production board never gets to the simple LED flashing that I use as a debugging test. Run it in the debugger; it starts fine. Remove and re-apply the same power, and nothing happens. Run it in the debugger, and it starts fine.
Can the CC1310 have some state that won't let it start? I've checked the TCK pin, shorting to power, as a measure to prevent halt-in-boot, without success.
I'm somewhat hindered in getting to scopes and other probes right now, so I'm trying to exhaust other avenues first.
I'll appreciate any hints or suggestions.
-- Bob
