Brent,

This sounds some type of a driver issue.  When I see something like this, my first inclination is to close CCS and restart the computer. 

Trying to connect in a brand new CCS workspace might be my next step if the above doesn't work.

Hopefully this gets you closer.  Let us know if it doesn't.


Thank you,
Brett

Hi Brett,

Thanks for the response.  I had tried the closing of CC, re-powering computer, new works pace to no avail.

One thing of note is that I can plug in a 28027 controlCard and utilize both the XDS100v1 and SIGNUM emulators to download and run programs.

It is just the 28069 card.  Which was working fine until I tried downloading this morning.

Any other thoughts?

Brent

To confirm:
The F28069 cCARD that you are using looks something like the picture in the below link, correct?
http://www.ti.com/tool/tmdscncd28069?keyMatch=tmdscncd28069&tisearch=Search-EN


Thank you,
Brett

Hi Brett,

Yes, that is the card I have.  I have been using it for about a month with no issues.

Brent

Hi Brent,

I did just notice that, according to your first post, even though xds100v1 is selected xds100v2 is being tried.  Perhaps this shows that something is just a bit off in your target configuration.  (or maybe you have a target configuration inside your project folder).  This leads me to believe we're fighting a CCS issue.

How are you currently trying to connect to the device?

Can you try connecting via Method 1) described in the below with your xds100v1+F28069 target configuration:
http://e2e.ti.com/support/microcontrollers/c2000/f/171/p/328069/1151169.aspx#1151169


Thank you,
Brett

Hi Brett,

Good catch on that.  Thank you for following up.  I cleaned out the project and work space, then created a new target configuration file.

I have been launching the project in the following way (NOTE: the 28027 flashing LED project, I am not having problems with):

1) While in C/C++ perspective, I hit the debug button at the top.

With the now cleaned up project and launching this way, I still see the same issue.  Specifically it stays stuck on the Progress Information pop up (this is using the on board XDS100 emulator).

Hitting the cancel button does not help.  I have to remove power on the board at which point I get that Error connecting to the target (Error - 1041 @ 0xFFFFFF66).

I see in the link you provided the following steps:

1)  This way has more steps, but you have control of each step.
a) From the CCS Edit view, right-click on the target configuration and click "Launch Selected Configuration". 
b) within the CCS Debug view's Debug window, right-click on the C28xx core and click Connect Target
c) load your .out file by clicking on the load icon.  (just above the 'u' in "Code Composer Studio - Device" in your screenshot).  HotKey: Ctrl+Alt+L
d) You should now be at Step29 in the workshop manual.  You can now run the code, single step, view memory, etc.  

For 1b) I see two C28xx core

1) I try the first (i.e. right clicking and Connecting To Target).  I don't really get any feed back except when I right click again I do not have the option to connect anymore, so I continue with the next step.

2) Ctrl+Alt+L

It is hanging as follows:

Once I remove power from the board, I see the following:

I got another 28069 and see the same issue.

Did I perform your steps correctly?

Brent

Hi Brett,

Trying your method a couple of more times.  Sometimes it get hung up when I do the connect, other times it will get hung up when I do the ctrl/alt/delete.

In both instances, I do not see the device show a Connected Device.  Right below where I do right click to connect device it always shows Disconnected Device.

Brent

Brent,

You should right-click on
  Texas Instruments XDS100v1 USB Emulator_0/C28xx [Non-Project Debug Session]
to attempt to connect to your device.  See attached.

(for future reference the other core you see is the CLA core)

If successful, you should then see that the C28xx's Device's Thread should go into the "suspended" state.

Let me know if you can get this far.

---

Another thing to mention: unless you have a good reason to, we'd prefer you move to CCS5.  I personally find CCS5 to be a little less quirky.


Thank you,
Brett

Hi Brett,

Thanks for the clarification.  I tried as you asked.  I still have the same issue.  Specifically it hangs until I remove power at which point the 1041 error pop’s up.

I am trying this on a F28069 Piccolo Experimenter Kit.  I also have the HVLLC kit (came with 28027).

If I plug my two 28069 controlCards into the HVLLC Kit and do what you describe I see something different:

C28xx: GEL Output:

Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: GEL Output:

Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: Flash Programmer: Error erasing flash memory. Device is locked or not connected. Operation cancelled

     C28xx: Flash Programmer: Error erasing Flash memory.

     C28xx: Flash Programmer: Device is locked or not connected. Operation cancelled.

     C28xx: Trouble Writing Memory Block at 0x3f4532 on Page 0 of Length 0x16

     Cannot write to target

 I am able to:

1. Launch the configuration
2. Connect like you describe above

I went and viewed memory

CSM_PWL_P0  : origin = 0x3F7FF8, length = 0x000008     /* Part of FLASHA.  CSM password locations in FLASHA

The locations are indeed 0 on both of the 28069s => they are locked.

I had a few questions I am hoping you can answer

1. I went in and tried to unlock the board and it still says it is locked.  I take it I need new chips at this point?
2. What causes this?  It has happened on two boards.  I would really like to not have this happen again. 
3. Is it better once you get a board to just program passwords?  If I had, would I have been able to unlock the processor or was it in a state it would not have mattered?
4. Why could I connect to the processors when I plugged the controlCards into the HVLLC kit and not the docking station that is part of the 28069 Experimenter Kit?  I have went back and forth numerous times and this is consistent.

 Thanks for your help Brett,

 Brent

Appreciate you working through this with me.

I am thinking what I will probably do is put my code in Sectors other than A and within CC disable the erasing of A.

This should at least keep it from permanently locking the device.