TMS320C6657: Distinguish C6657 vs 55 vs 54

Geoffrey,

I remember the discussion and the solution we discussed here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1059129/tms320c6654-distinguish-c6654-or-55

There is no other way to differentiate in software, other than DEVSPEED register.

May the customer can use any of the reserved memory area and store the specific values to differentiate them in future.

Regards

Shankari G

Geoffrey,

Please try the "CorePac Revision ID Register" values on C6654 and C6657.

Please Check whether the " version-bits and revision-bits" of   "CorePac Revision ID Register" values are different for C6657 and C6654.

Regards

Shankari G

We will check, thank you Shankari 

Geoffrey

Shankari, 

It turns out both 6654 and 6657 have 0x00080001 @ address 0x01812000. Do you have any other ideas ? 

Geoffrey

Geoffrey,

As a last try.......How about JTAGID register??... Please do check this as a last try....

I guess, this value might help, us.....

=========================

0x02620018 0x0262001B 4B JTAGID -- page no: 207 in the C6657 data sheet

==========================

====================================

I have only C6657 in my hand and donot have C6654, to experiment and check...

=====================================

Regards

Shankari G

Hi,

JTAGID register contains the same value (0x0B97A02F) for both C6654 and C6657

regards

Gildas Rolland,

Oh, OK. 

====

There is one indirect method using the target configuration file using CCS.

For example, when we launch the "evm6657ls.xml" file to connect to the target using CCS, it will display the total number of cores for the particular device.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1064425/faq-tms320c6657-how-to-create-target-configuration-and-do-test-connection-on-c6657-evm

For C6657 - it will display two number of cores

For C6654, it will display one number of core.

Please use the appropriate target configuration files.

Regards

Shankari G

My need is to differentiate 54, 55 and 57 by embedded software, so target configuration file is not usable

Gildas,

I experimented with the "target configuration- xml file of different devices to respond to C6657 EVm, but that doesnot help.

Let me have a discusstion with internal team and get back about it's possibility.

 Actually, me, Geoffrey and Mukul already discussed about this, last year. And most likely, the answer was like this...

For Keystone II devices, The JTAG ID register gives appropriate values to distinguish between the devices such as K2E, K2H, K2G etc. But the devices such as C6657, C6654 etc were older devices with no particular revision/version IDs maintained.......

However, Please wait for a couple of days to hear from the internal hardware team.

Regards

Shankari G