This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

recommended practice for debugging a 2802x with locked flash via the JTAG



Is there recommended practice for debugging a 2802x with locked flash via the JTAG and CCS4.x ?

With the older 280x parts it was very easy to connect to a locked part, enter the csm password and unlock for debugging. This does not seem to hold true with the 2802x family.

With CCS3.3 I was able to eventually connect  by: forcing the target into SCI boot mode (pull JTAG TDO low and powerup) and then connect the JTAG (remove jumper from TDO). Enter the CSM password and 'unlock'. This would not always be a reliable process, and CCS3.3 would crash on a regular basis. 

This seems to be even less reliable with CCS4.2. 

Is there a better way? 

  • Jason,

    You should be able to connect locked F28027 device just like F280x parts. Do you have any snapshots of the problem you encountered?

    I just tried connecting to a locked F28027 without any issues.

    Procedure followed:

    1) Right Click on F28027.ccxml file and choose launch selected configuration.

    2) Select Debug perspective

    3) Select Target -> Connect Target

    4) Before executing (or) Pressing Hit Run. Unlock the device by entering password in 0xAE0 - 0xAE7.

    5) Proceed with your debug.

    Regards,

    Manoj

     

  • This method only works for me when using a unlocked system. If I lock the flash (using the csmpassword.asm file in my project as per D.Alter) then I get the following message when trying to connect with a BlackHawkUSB2000 JTAG:

    Error connecting to the target:

    Error 0x80000240/-233

    Fatal Error during: Initialization, OCS, 

    My understanding from the documentation is that you can only break into the system when waiting in the boot ROM.

    The method of connecting also seems to play a big role; if you boot up and run (stand alone) with the flash locked you cannot easily reconnect the JTAG. If your JTAG is connected when you boot in debug mode from CCS, the behaviour is different. 

  • I just checked by connecting to locked F28027 device using CCS4.0v (and XDS510USB emulator) without any issues. Can you brief the method you use to connect to the device?

     

    -Manoj

  •  

    What does not work:

    1) Connect  BlackHawk USB2000 to JTAG header on target (in house product, not an eval board)

    2) Power up target 

    3) From CCS4.2 CC++ view:  Target menu -> Launch TI debugger.

    4) From Debug View: press connect target icon...   then I get the error message.

     

    What does work (although buggy an prone to locking up)

    1) jump JTAG TDO to ground (the header is convenient for this)

    2) power up target

    3) remove jumper and connect BlackHawk

    4) From CCS4.2 CC++ view:  Target menu -> Launch TI debugger.

    5) From CCS4.2 Debug view:  press connect target icon...  I get a message that part is locked and calibration is not done

    6) From CCS4.2 Debug view: Tools-> On chip Flash -> Enter CSM passwords,Unlock flash 

    7) proceed to debug (running the calibration is recommended before running the application)