LAUNCHXL-CC26X2R1: Device revision '0x4' unknown for selected target

Hi Michel,

What is your system's OS and what version of CCS and Uniflash are you trying? Did you receive this LaunchPad from TI or a third-party?  Is it brand-new out-of-box or is its previous usage unknown?  Are the default XDS110 jumpers connected and are you using a short USB cable?  Do you have multiple LaunchPads to test with and do any of them work with your environment?

Regards,
Ryan

Hi,

Thanks for the quick response.

Answers:

Windows 10.

Uniflash 8.0.0.4026

CCS 12.0.0.00009

Brandnew launchpad (Digikey)

Long USB cable, but just tried short cable (delivered in the package) same result.

XDS1110 jumper is (XDS1110-power)

Only one launch pad.

I am able to debug the buttonled project.

Regards,

Michel

Thanks for all of the information!  Please know that project_zero expects to have the bim_offchip (Boot Image Manager) application loaded consecutively.  Here is an excerpt from the Project Zero README:

Note on the Boot Image Manager
This project is configured to be managed and launched by the BIM or Boot Image Manager example app. This means that this project does not include a CCFG section to configure the device at boot, and therefore requires that the BIM project is programmed into the device first.

The application supports secure OAD i.e. Image authentication needs to be done before executing the newly transferred image. This is done by the BIM example app. A security header is added to this application image in order to support this.

If BIM is not present in the device internal Flash, the project can usually be started from the IDE but will not be executed after a pin reset. Read more about BIM and OAD in the BLE5-Stack User's Guide. 

This would not seem related to your "device revision unknown" error, however the operational buttonled project and crashing debug sessions could be explained by the BIM missing.

Regards,
Ryan

Hi Ryan,

I shall order a new launchpad to see if that solves the problem.

I was aware of the BIM but will check it more in depth.

If the new launchpad solves the issue i will close the ticket.

Regards,

Michel

If you are able to debug other SDK project then I do not know whether a new LaunchPad will resolve your issue.  You could try non-OAD BLE projects such as simple peripheral to further test.  Does the application run when loading the application images with Uniflash?

Regards,
Ryan

Hi Ryan,

I've tried to debug the simple_peripheral_CC26X2R1_LAUNCHXL_tirtos7_ticlang. Same issue (CCS dissapears /crashes)

I was able to debug project buttonled_CC26X2R1_LAUNCHXL_tirtos7_ticlang

I was able to download the project zero with uniflash (windows version), and able to use it with the iphone app.

I was also able to flash simple_peripheral_CC26X2R1_LAUNCHXL_tirtos7_ticlang and able to connect to it.

Normally when something is strange, something is not good.

Regards,

Michel

This could be a CCSTUDIO issue.  You could try re-installing CCS or evaluate an older version such as 11.2

Regards,
Ryan

Hi Ryan,

I installed V11_2 on another pc.

Device revision still unknown. but enable to start the debugger without a crash.

Sounds strange to me, but is solves the issue. 

Should i remain to V11_2 for now?

I will update the ticket when i receive the new launchpad.

Thx for the help.

Regards,

Michel

I'm notifying the CCS Team to determine whether they can provide any further assistance.

Regards,
Ryan

Michel,

Do you still have the environment setup that crashes?

If so could you enable debug server logging, then run through the scenario that crashes, then attach the log to this thread.  Maybe we can figure out what is going on from the log.

There is information on how to enable debug server logging at the link below. 

https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html

I believe the device revision message would be coming from the flash loader.  The fact that the crash occurs during downloading makes me think something is going on with the flash loader as well.

I had a CC1352R1 on hand that I tried loading the same example on with CCSv12.  I was not able to reproduce.  I believe I have a CC26x2 LP at home that I could try tomorrow.

Regards,

John

Hi John,

I installed V11_2 on my pc. That works fine.

I will install V12 again and see if the error occurs again.

Regards

Michel

Hi John,

Installed V12 again, problem is again there. Attached the requested log.

Also will attach the CCS crash dmp. but not able to add that to the same reply.

Regards,

Michel

ds.log

bdeca976-5b5b-48b9-a09e-d55a1ba93798.zip

And the  CSS dmp file.

Regards,

Michel

Thanks Michel!

Michel,

The crash dump was very useful.  The root of the issue is that there is an issue in the debug symbols that is causing the symbol manager to crash.  This will be corrected in our next compiler patch.

We would have expected this to crash in 11.2 as well but maybe there is a slightly different sequence happening.

There is a workaround that you can try that changes the symbol manager 

You will need to manually launch a debug session and connect before loading a program.

Open the Target Connections View from the view menu

Expand Projects

Expand your project

Right click on the .ccxml file and select "Launch Selected Configuration"

This will start the debugger

Next go to the Expressions view and enter 

symbol_loader=1

click the button to "Connect"

Now try loading the program (via the button on the toolbar) 

Regards,

John

Hi John,

I tried to follow your guideline.

I opened Target Configuration View (instead of Target Connection)

Clicked the button Connect to Target.

also did the expression part, Expression view row:

symbol_loader=1 short 1 GEL variable

Loaded the debug version of simple_peripheral_CC26X2R1_LAUNCHXL_tirtos7_ticlang

Message on Console:

Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
Cortex_M4_0: Device revision '0x4' unknown for selected target. Assuming latest known revision: Rev. 2.1.
Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
Cortex_M4_0: GEL Output: Board Reset Complete.
Cortex_M4_0: AutoRun: Target not run as the symbol "main" is not defined

In debug window:
No symbols are defined.

The program is able to start up and run (no crash) after hitting the button resume.

Also without the symbol_loader expression the application runs without symbols.

Regards,

Michel

Michel,

It should still load with symbols, it won't load all symbols as that setting basically reverts to our old symbol manager which did not have the best support for GCC or Clang but it should still load symbols. 

There will be an updated compiler release that fixes the issue in the symbols that triggers the problem.  I was actually trying binaries generated with it earlier today and I was not getting the crash.

This is a link to the bug

https://sir.ext.ti.com/jira/browse/EXT_EP-10863

It will be fixed in the 2.1.1 release that is coming shortly.

Regards,

John

Hi Ryan,

I have received the new launch pad. It first asks for een firmware upgrade for the Probe.

IcePick_C: Warning: A firmware update is required for the XDS110 probe. The current firmware is version 3.0.0.13. The probe must be upgraded to firmware version 3.0.0.20 to be compatible with this software. Click the "Update" button to update the firmware. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 9.8.0.00235) 

It is still reporting the same issue:

Cortex_M4_0: Device revision '0x4' unknown for selected target. Assuming latest known revision: Rev. 2.1.

Regards,

Michel

I will check with the SimpleLink HW Tools Team and let you know if there is a known source and fix for this issue.

Regards,
Ryan