CCS/TMS570LC4357: CCS/AJSM GUI functionality

Hello Oleg,

You said your device is not locked. How does the wrong unlock key (00112233445566...) work? BTW, the number used in your test is not the unlock pattern generated by HALCOGen.

If the device is not AJSM locked, the default visible lock key is: 0XFFFDFFFF_FFFFFFFF_FFFDFFFE_FFEFFFFF, and unlock key should 0x00000000_00000000_00000000_00000000

Hello QJ.

Thank you for quick response.

1) You are right absolutely – my device is unlocked with original code from manufacture (as you say: 0XFFFDFFFF_FFFFFFFF_FFFDFFFE_FFEFFFFF). And my unlocking code (00112233445566...) is not unlock pattern. But….

2) As I wrote in initial comment – the unlock code does not matter for “dbgauth” command line case. I tried to apply different unlock keys – and it works!

You can check on your test bed – and will get the same result.

3) Moreover, you may see the “correct” from the Halcogen key on the screenshot for LS31 device – it also successfully unlocks originally visible device (my LS31 is NOT locked also).

4) In addition I might suppose if the .dat file (which I got it by clicking “Test connection”) contains the key value (“zero” all words), so “dbgauth“ skips the key parameter defined by ‘-k’ option.

But I changed the key values in .dat file and it also does not matter for “dbgauth” unlocking of NOT locked device. Just in case see please my .dat file:

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

# config version=3.5

$ sepk

pod_drvr=jioxds110.dll

pod_port=0

pod_supply=0

pod_voltage_selection=0

pod_voltage=0

$ /

$ product

title="Texas Instruments XDS110 USB"

alias=TI_XDS110_USB

name=XDS110

$ /

$ uscif

tdoedge=FALL

tclk_program=DEFAULT

tclk_frequency=5.5MHz

jtag_isolate=enable

$ /

$ dot7

dts_usage=nothing

$ /

$ swd

swd_debug=disabled

swo_data=aux_uart

$ /

@ icepick family=icepick_c irbits=6 drbits=1 subpaths=3 systemresetsupported=1

& port18 address=18 default=no custom=no force=yes pseudo=no cancelreset=0x0

   @ ajsm family=ajsm irbits=4 drbits=1 unlock_key_w0=0x0 unlock_key_w1=0x0 unlock_key_w2=0x0 unlock_key_w3=0x04

& port17 address=17 default=no custom=no force=yes pseudo=no cancelreset=0x0

& port16 address=16 default=no custom=no force=yes pseudo=no cancelreset=0x0

   @ dap family=cs_dap irbits=4 drbits=1 subpaths=1 identify=0 revision=Legacy systemresetwhileconnected=1

     & portr5 type=debug address=0 default=no custom=no force=no pseudo=no

       @ cortexr5 family=cortex_rxx irbits=0 drbits=0 address=0x80001000 identify=0x02000100 traceid=0x1

     & /

& /

# /===================================

5) But the main problem – CCS reports the permanent error when AJSM is configured by GUI in accordance with SPNA232.

Please repeat what I did – and you will get the same results.

Hope I explained everything clear. Please let me know if you need any additional info from me to reproduce the situation.

Thanks and regards,

Oleg.

Hello,

Any unlock key except for 0x00..00 doesn't work. The AJSM module XOR the unlock key and the OTP content to generate "FFEFFFF_FFFDFFFE......"(default value in OTP).

If you use 00112233...ff, the output of XOR is FFFEDDCC..... which doesn't unlock the device. 

I tried on my bench:

The maximum speed of XDS110 USB is 2.5MHz. How did get 5.5MHz in your config file?

Hello QJ.

Your screenshot reports another (not concerned to the key) error: 

"Failed to find the specified device name in the board config info"

Please fix the device name and then you will be able to work with key (if no another errors in the config file).

Please try it again after fix.

Thanks in advance,

Oleg

QJ,

to respond another your question related to XDS and its frequency.
I get the "testBoard.dat" file from my CCS when I click button "Test Connection".

Specially to check again - I just generated 2 files. First - for my project with AJSM port. Second - it is downloaded from TI your "TMS570LC4357_UART_Boot" project.
I compared the both files - they are identical. Only one difference - presence of AJSM port.
The screenshot of comparison is attached.
And please let me know if you prefer I to send you both .dat files

I guess it does not mater what frequency CCS reports if I am able to connect to the device successfully. ...but I maybe wrong...

Thanks,
Oleg

QJ,

Let me append the additional info to my comment above on fail you got on device name.
I have identified this error - it appears when to use another device type in command line than in .dat file.
In your command line you use "cortexr5" parameter but seems your .dat file contains 'cortexr4' or another device type.

I just generated the same with yours fail by changing the command line parameter to "cortexr4" from "cortexr5", but my .dat file relates to the R5 device. See please the attached screenshot - the same fail as yours.
So please correct it and try to test again.

Thanks,
Oleg

QJ,

And one more.
The main problem - CCS AJSM GUI functionality fails with reporting of internal error if to follow the GUI configuration method described in SPNA232.
So please identify the cause and fix it.

Or provide the info me how to configure this functionality correctly.


Thanks in advance,
Oleg

QJ,

And additional info to you.
Based on your output it seems your .dat file does not contain AJSM debug port (Port18) info.
Please check and configure it properly if required.

Thanks and regards,
Oleg

Hello QJ.

Could you or somebody else to help me with this subject?

Thanks in advance,
Oleg.

I locked one LC4357 device with AJSM, and unlocked it with the unlock key generated through the HALCOGen

Hello TI engineers.

There is no response from you for about 2 weeks.
Could you please tell me if somebody is able to help me with this fail/problem?

Please respond me 'yes/no' - so I will understand what way to move forward.
Silence from you puts me in indeterminate state which harms my business.

Thanks in advance,
Oleg.

Hello TI engineers.

There is no response from you for about 2 weeks.
Could you please tell me if somebody is able to help me with this fail/problem?

Please respond me 'yes/no' - so I will understand what way to move forward.
Silence from you puts me in indeterminate state which harms my business.

Thanks in advance,
Oleg.

Hello Oleg,

As I mentioned before, the unlock key for the default OTP value at 0xF0000000 0s 0x00000000_00000000_00000000_00000000. It is not possible to unlock the device with a wrong unlock key for example 0x00112233445566778899aabbccddeeff.

You said that your TMS570LS3137 AJSM was unlocked successfully, but JTAG connection failed. Was the device locked successfully? Is the unlock key generated through HALCOGen? 

Can you please tell me the HALCOGen version you used to generate the AJSM lock key and unlock key?