Tool/software: Code Composer Studio
We have 6 Launchpad dev boards, Four ordered 2 months ago, and 2 more just ordered and received
The revs of the boards received earlier (QTY: 4) are
BOARD Label Processor
Rev 1.0 WCS037A CC2642 R1F C TI XJ9J P7CK G4
The revs of the boards just received (QTY 2) are
BOARD Label Processor
Rev B WCS037 CC2642 R1F E TI X8AJ P3QJ G4
In both cases the SDK is simplelink_cc26x2_sdk_2_30_00_34, and CCS is version CCS8.3.0.00009_win32
We have done all the updates suggested during installation and initial project loads on 3 separate Win10 machines
Off the box the new devices appear as "Project Zero" in a network scan. The problem starts with the new units (Rev B boards) as the Project Zero is built under CCS, and then after building and linking, this message appears
After performing the upgrade successfully the CC2652 is no longer operational:
Our current status is that we have one board "down" as shown above. We did NOT and will not perform the upgrade on the second one. This board under power is still seen as a Project Zero device...
=================
More related facts.
Of the four initial (Rev 1.0) boards:
- 2 have been "killed" by the same forced upgrade
- 2 did not exhibit this issue. We do not recall whether a firmware update was forced (we rather think not!!!!) and these boards now run both Project Zero and our own software successfully but with a twist:
--- one runs both connected to the host under the debugger and in stand-alone as a release build
--- one runs ONLY connected and in debug mode, NOT stand-alone.
Rev levels are identical, sofware loaded is exactly the same, but their behaviours are different.
=================
Questions:
[1] How does the forced debug probe update work and why does it put the CC2652 in this error mode? Is there a way to bypass making this upgrade? Or is there an incompatibility between this debug probe and the latest CCS updates? Or???
[2] Of the 6 boards received in total, why do 4 need this update, and 2 did not?
[3] Any idea why, in the 2 older boards we have that passed the initial stage, one only will work in released mode, and one not?
Our development work is stalled.. Thanks for any help or insight you may have.
