SAFETI-HALCOGEN-CSP: XDS110 firmware downgrade

Patroklos Anagnostou1

Part Number: SAFETI-HALCOGEN-CSP
Other Parts Discussed in Thread: HALCOGEN

Hello,

Upon executing the Halcogen TAU unit tests, I see that my debugger probe XDS110 downgrades from firmware version 3.0.0.11 to 2.3.0.2

I tried to look for this setting in the files but I was unable to find where this version is set. It results in upgrading/downgrading back and forth between unit-testing and code debugging and I assume there is a risk related to that.

Could you please point me to the setting I should update to fix this to 3.0.0.11 or latest? Thank you

over 5 years ago

0 QJ Wang over 5 years ago

TI__Guru**** 196816 points

Hello,

This link provides the steps to upgrade the firmware of xds110 emulator:

http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html

0 QJ Wang over 5 years ago in reply to QJ Wang

TI__Guru**** 196816 points

https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds_software_package_download.html

0 Patroklos Anagnostou1 over 5 years ago in reply to QJ Wang

Prodigy 240 points

Thank you, it is indeed possible to manually update the debugger.

My issue is that HalcogenTAU automatically downgrades it to v2 in order to work and CCS automatically updates it everytime to v3 to work.

Is the version information part of ccs, the targetconfig, the connection file, some other debugger settings file? Can I set the v3 to halcogenTAU too?

I have multiple ccs versions, I will try to cleanup to see if this is causing the issue.

0 QJ Wang over 5 years ago in reply to Patroklos Anagnostou1

TI__Guru**** 196816 points

Hello,

When using ccsv8.1.x with TI Emulators package version 6.0.14.5 or newer, the firmware on the XDS110 is updated automatically when connecting from inside CCS.

Note that the firmware is not automatically reverted to a prior version unless there's been a major change. For most scenarios, all changes are backwards compatible to ensure this works. If a change is needed that is not backwards compatible, then the major version numbers will change as a flag that it can't work.

Examples:

CCS supports firmware 2.3.0.12, XDS110 has firmware 2.3.0.8 → XDS110 will be updated to 2.3.0.12
CCS supports firmware 2.3.0.12, XDS110 has firmware 2.3.0.14 → XDS110 will not be reverted
CCS supports firmware 2.3.0.12, XDS110 has firmware 2.4.0.1 → XDS110 will be reverted to 2.3.0.12

The latest xds110 is 3.0.0.11. The compiler needed for HALCoGen TAU is v5.1.6 and CSP examples were developed under CCS6

You can use new CCS with latest xds110 driver (3.0.011) for HalCoGen TAU, but you have to use compiler 5.x

0 Patroklos Anagnostou1 over 5 years ago in reply to QJ Wang

Prodigy 240 points

Hello,

I read this info in the documentation. Indeed it is a major version number change, so the downgrading rule also applies.

If the final project is meant to be compiled with TI compiler v.18.12.x, I believe the tests must also be done with the same compiler to support the certification claim.

In that case, which CCS can be used and is reverting XDS110 to former versions necessary?

Thank you for your support

0 QJ Wang over 5 years ago in reply to Patroklos Anagnostou1

TI__Guru**** 196816 points

Hello,

You can select an old version compiler from CCS project configuration. Downgrading or upgrading the XDS110 depends on the version of emulator package in CCS. Changing the compiler should not cause the xds110 firmware be updated.

Arm-based microcontrollers

Arm-based microcontrollers forum

SAFETI-HALCOGEN-CSP: XDS110 firmware downgrade