"Error initializing emulator" on CCS4.1.2 under Vista. Target: HVMotorCtrl+PFC Kit

Hi Michael,

You may be running into one of the issues discussed in this thread:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/40771.aspx

ki

Hi Ki,

I have tried the steps provided by your link, and update the USB firmware, windows drivers, etc..., but I got exactly the same problem. From the sound of the discussion, it seemed that the problem had not been resolved...

The USB still connects OK for CCS 3.3. I would try any suggestion you may have, because converting CCS 4.x back to CCS 3.3 would be a lot of hassles.

Regards,

Michael

Three people had similar issues on that thread. Two of the them resolved their issue with the firmware update, one is still ongoing. If the firmware update did not help, could you provide the information in:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/40771.aspx?PageIndex=2

The Debug Server logs would especially be very valuable.

Thanks

ki

Michael,

Are you still having this issue?  Can we set up a Webex  for some time tomorrow in order to try to solve it?  Please let me know what time will work for you and I will schedule it.

Thanks,

Dan

>>Michael,

>>Are you still having this issue?  Can we set up a Webex  for some time tomorrow in order to try to solve it?  Please let me know what time will work for you and I will schedule it.

>>Thanks,

>>Dan Rinkes

 Hi Dan ,

II received your message on May 4. I replied, not realizing that it was <noreply@e2e.ti.com>, and waited, and waited...

I finally looked at the return address today, and knew that this is the only way I could reply to you, through the Forum. My apology to all others who have to read this message.

Yes, I still have the afore-mentioned problem with CC4, and need it resolved quickly, or I'll never touch CC4 again.

I'll be out from Tuesday to Thursday this week attending TI sponsored Digital Power Workshop in Dallas, otherwise I will be available today, and Friday, and on...

Please call me at 281-285-7810 to set up Webex.

Your assistance will be greatly appreciated.

Regards,

Michael.

Thanks Michael, sorry I missed your message yesterday. 

I will set up a webex for Friday, say 2:00 CDT?  I think I have your e-mail address in another thread.  I will send confirmation there.

Regards,
Dan

I don't know if I'm posting to this thread correctly, so hopefully this message gets viewed.

I am having a similar problem. I am running Windows 7 64-bit. I had my TMDS1MTRPFCKIT working properly with CCS V3.3 before my OS upgrade. Now, I cannot get V3.3 working on my computer, so I want to work with that kit on CCS V4.1. I have a controlSTICK which came with version 4.1.0.02005 and I can execute code on that. However, the controlCARD with the motor controller kit has a TMS320F28035 uC and not the TMS320F28027. When I create a new target configuration for "Texas Instruments XDS100v1 USB Emulator" with device "Developer's Kit - Motor Control and PFC" and try to debug, I get the error message box as posted in the first post of this thread.

I went through the other forum that was linked before finding this forum and I didn't have any success. From the XDS100 wiki page, I was able to find the following link http://e2e.ti.com/support/microcontrollers/tms320c2000_32-bit_real-time_mcus/f/172/t/21086.aspx explaining how to program the EEPROM of the FTDI chip. I did that successfully. Is this what is meant by upgrading the firmware? If so, is it the latest version? If not, how do I upgrade the firmware with the latest upgrade?

Another interesting bit of info.... Following the link to the other forum, I ran dbgjtag on my ccBoard0.dat file. Everything passed inspection. I wanted to make sure I was running dbgjtag on the correct file. I changed my target configuration to the 28027 that works with my controlSTICK and clicked the debug button. I noticed that the ccBoard0.dat file I was running dbgjtag on had changed. This confirmed to me that I was running dbgjtag on the correct file, so I wasn't getting false results from an incorrect file. However, I noticed that in clicking the debug button (using the 28027 target configuration), I had actually uploaded and started executing code on the 28035 controlCARD. With that though, I got the message "C28xx: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map."

My concern then is that I might not be able to execute proper code in a more complicated project. I'd like to be able to use a 28035 target configuration with the 28035 controlCARD and not have a message saying some of the code may not be written to the target. I'd appreciate any feedback I can get. Thanks.

~Zach

Zach,

To make sure I understand correctly the main issue you are having is in connecting to Motor Control and PFC Developers kit (TMDS1MTRPFCKIT) using the onboard emulation with CCS 4.1.

Your target configuration appears to be correct as you have selected "Texas Instruments XDS100v1 USB Emulator" and "Developer's Kit - Motor Control and PFC". One thing I would suggest checking is that the correct target configuration is associated with the project. In other words, you could have a target configuration set as Default and if there is no target configuration linked to your project, it will use whatever is set to Default when you hit the "Debug active project" icon. To avoid confusion, I would suggest launching the desired configuration using the steps described here and then connect individually to the C28x and then CLA.

It might also help to perform the steps to delete the debug launch and target cache files as described in this troubleshooting section.

Aarti,

Yes, my main issue is wanting to connect my Motor Control and PFC Developers kit using onboard emulation with CCS 4.1.

First, the target configuration for the 28035 motor control board was set as default. I didn't set a specific target configuration to the project, so it was using the default one. Here, clicking the "Debug Launch" icon results in the "Error initializing emulator" dialog box.

Second, I tried going to the "Target Configurations" menu, right clicking on the 28035 target configuration, and clicking "Launch Selected Configuration". Again, the same error came up.

Third, I went through the steps to delete the debug launch and target cache files. Opening CCS afterwards and looking at target configurations, all were gone as expected. I created a new target configuration as I did before ("Texas Instruments XDS100v1 USB Emulator" and "Developer's Kit - Motor Control and PFC"). I then made that configuration the default and tried the step listed just above, right clicking and selecting "Launch Selected Configuration". Again, the same error came up.

Lastly, I tried simply clicking the "Debug Launch" icon again. Here, there was a difference from before. Before, it would pull up the error message. Now, no error message comes up. The console window shows:

**** Build of configuration F2803x_RAM for project FlashingLeds-F28035 ****

C:\TI CCS\ccsv4\utils\gmake\gmake -k all 

C:\TI CCS\ccsv4\utils\gmake\gmake: Nothing to be done for `all'.

Build complete for project FlashingLeds-F28035

However, the connection to the target still doesn't appear to have been made. All things under the Target menu having to do with code are gray and cannot be selected (Load Program, Connect Target, Run, etc...)

Any suggestions for the next thing to try? Thanks.

~Zach

Zach,

Could you double-check that you have the correct jumper setting on the kit for onboard emulation? The [M3]-J5 jumper should be disabled to use on-board emulation. When I placed a jumper on J5 while connected to on-board emulator, I saw similar "error initializing emulator" messages.

If this is not the issue, I would carefully go through the suggested troubleshooting steps here again. The reason I say this is because I was just trying to test the connection to the same kit with CCS 4.1 and 4.2.1 and ran into errors and problems, but once I deleted all the debug launches and target cache files as described in that page, power cycled the board and re-plugged the USB connector, I was able to connect to target with both CCS 4.1 and 4.2.1. Note that I did use the method of "Lauch Selected Configuration" instead of "Debug Active Project" but it should work both ways.

If you're still having trouble with CCS 4.1, I would recommend downloading and trying it with the latest version CCS v4.2.1. There have been a lot of fixes and improvements made since 4.1.0, and it is generally best to use the latest version whenever possible. It can be download from this page.

Aarti,

Is the jumper you labeled correct? On my board, the [M3] section appears to be the PFC section, while [M1] is the USB section. If you mean the USB section, then I don't have jumpers anywhere there... J1, J3, J4, and J5 are all left un-jumpered and I don't see a J2.

I will go through your other suggestions and try things again. I'll post the results. Thanks.

Zach,

You are right. I actually tested with the High Voltage Motor Control and PFC kit (TMDSHVMTRPFCKIT) so the jumpers are different. Sorry about the confusion regarding that. For the TMDS1MTRPFCKIT, you are right, the [M1]J5 is the jumper that controls on-board emulation and you seem to have that set correctly.

I'm afraid I don't really have any other ideas at this time but I would recommend going through the other troubleshooting suggestions as well.

Aarti,

I went through all of your suggestions now and finally have it working. It took installing V4.2.1.00004. The first two times I ran that, I had 4 windows firewall alerts that I allowed. I then could connect to the 28035 controlCARD using the 28035 target configuration and execute code. However, when I clicked the "terminate all" button, I got a blue screen. My computer automatically restarted before I could write down the error code, but it said something about a service thread unexpectedly stopping. The third time (and all others after that) I didn't get the windows firewall anymore and I am able to debug and terminate all without crashing the computer.

When I was running V4.1.....whatever I was just running that I posted earlier (I forgot already).....I was asked if I wanted to update and I did, yet I still wasn't running the most up-to-date version of software. Should I be getting asked to install the most recent software in the future?

Anyway, thanks for your help.

~Zach

Zach,

Sorry to hear about all your troubles but I'm glad you finally have it working with CCS 4.2.1.

Zach Tatge said:

When I was running V4.1.....whatever I was just running that I posted earlier (I forgot already).....I was asked if I wanted to update and I did, yet I still wasn't running the most up-to-date version of software. Should I be getting asked to install the most recent software in the future?

CCS should prompt you when there are new updates and ask if you want to update. It could be that with your previous version you still weren't up to the latest update or, more likely, something was corrupted in your workspace or target configurations that was affecting the target connection.

This thread is the closest I have found to the problems I am experiencing, except following through everything Zach did, I still can not connect:

• OS: WIndows 7 64 bit
• EVK: HVMTRPFCKIT (F28035)
• CCV4.2.4.00033 (first install was 4.1.3 but upgraded as part of this process)
• M3-J5 no jumper
• Connection: Texas Instruments XDS100v1 USB
• Board or Device: Developers Kit - Motor Control and  PFC (F28035)
• Project: HVACI_Sensorless [F2803x_RAM]
• Device Manager sees TI XDS100 Channel A and B under USB Controllers
• Device Manager sees USB Serial Port COM6
• I ran the GUI demo which successfully communicated using COM6
• Different combinations of powering down/disconnecting the EVK and re-starting CCv4

I have tried connecting to the target through the project (Debug Active Project) and non-project debug (Launch TI Debugger | Connect Target)

I always get some form of the Error Connecting to Target message.

Error connecting to the target:
(Error -1041 @ 0xFFFFFF87)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
(Release 5.0.429.0)

Error connecting to the target:
(Error -1135 @ 0x0)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
(Release 5.0.429.0)

I'm not sure what to try next. Help!!!!

Glen