CCS/TMS570LC4357: CCS AJSM feature support fail

Hello Oleg,

The DAP gel file tries to connect the target. Since the target is AJSM locked, the failed connection is expected. 

If you add GEL_System() and the unlock key (blue number) to tms570lc43x gel file, the target should be unlocked:

hotmenu AJSM_Unlock_Demo(){
    GEL_System("C:\\ti\\ccs900\\ccs\\ccs_base\\common\\uscif\\dbgauth.exe -c

               c:\\Users\\xxx\\AppData\\Local\\TEXASI~1\\CCS\\ccs900\\0\\0\\BrdDat\\testBoard.dat -s ajsm -t cortexr5 -k 2d1e060f325f99af8583c241b7c7d9e3 -m 1"); 

}

Attached is the gel file for my test.5852.tms570lc43xx_ajsm_unlock.gel

Hello QJ.

Many thanks for your reply and provided .gel file.

The recommended by you way to unlock a device under CCS is not GUI and it works in different way than GUI.
The provided by you way invokes the "dbgauth" command line utility which performs all required job to connect and unlock a device. And it works correct (and I considered this way as alternative one if CCS AJSM GUI fail is unresolved).

But the CCS AJSM GUI operates in different way - it executes several GEL (General Extension Language) functions calls:
OnPreTargetConnect() -> GEL_EvalOnTarget("AJSM", "AJSM_Unlock()", 1) -> AJSM_Unlock() -> GEL_Connect()
And these functions calls generate the CCS internal error.
And I reported this error as a main problem.

I provided a detail description of this CCS AJSM GUI fail in the thread:
e2e.ti.com/.../910657

Also in addition reported that I did an experiment with 'tms570ls3137' and applied both ways at the same time:
1) Command line utility invoking from .gel file like GEL_System(" ... dbgauth.exe ...");
2) CCS AJSM GUI unlocking

And provided the results of my experiment - I pointed that the first way works correct and unlocks the device but the second way generates the internal CCS error.
See please the link to provided by me screenshot and reported error:
e2e.ti.com/.../clip_5F00_image007.png


OK.
So currently you are able to reproduce the first way of device unlocking on your site. And it works correct.
Now please reproduce the second way - and it will generate the fail which I report. To do that, please enter your device unlocking key (blue key in your post above) into the CCS AJSM GUI form.
To enter your unlocking key please use the CCS GUI form like I posted:
e2e.ti.com/.../clip_5F00_image001.png

After that please try to debug any application - you will get the internal CCS fail which I reported. ...but it should to unlock a device.

So my initial and main request is to resolve this fail.
Please fix it and inform me how to do that. Or please tell me that it cannot be fixed. So I will be able to move forward.


Thanks in advance and regards,
Oleg.

Hello Oleg,

I never have a problem to unlock the device using command line and GEL file with the correct AJSM unlock key. To be honest, I didn't try the CCS GUI you mentioned. "Test Connection" on the GUI performs the integrity scan-test on JTAG IR and DR, but I noticed that it doesn't try to unlock the device. GEL is my preference since it unlocks the device automatically during startup.

How does the no-working GUI method impact your application? I will check with CCS team how to use the GUI to unlock the device.

Hello QJ.

Thank you for your response. Moreover on weekend.

No-working GUI does not impact my application. It impacts my debugging process.
Usage of .GEL files with the " GEL_System(" ...dbgauth.exe...") " function call produces the output into CCS Output window and discovers an unlocking key. As result this unlocking key can be easy seen by everyone who is near me - but this is forbidden.
I will not describe all specific and details of my debugging process in the field - just only let me say the command-line usage (and .GEL file as a particular case) for device unlocking is not good for me.

As I see the best option for me is CCS AJSM GUI usage for device unlocking at debugging.
So please contact CCS team (as you promise) and ask them to fix this fail and ASAP.


Thanks in advance and regards,
Oleg.

Hello Chester.

Thank you for suggestion.
The recommended by you workaround should work for me until CCS AJSM GUI fail be fixed.
One more thanks.

Please let me know whether I have to mark this forum's thread as resolved or keep it opened until CCS issue to be fixed.
And which way I will be informed when the fix is ready.
And the fix to be available for last CCS release only or for CCS v8.xx too.


Thanks in advance and regards,
Oleg.

Hello Oleg,

Please close this thread first. I will email you when I get answer from CCS team. Thanks

Thank you QJ.
So I close this thread.

Regards,
Oleg.