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.

TMS320F28069 Piccolo controlSTICK CCS4 XDS100 debug crash

Other Parts Discussed in Thread: CONTROLSUITE, TMS320F28069

I prepared 2 computers with CCS, ControlSuite and executed the two support executables for this new processor, TMS320F28069.

The first computer is a Windows 7 64bit and the second is a Windows XP sp3 machine.

Both computers properly access the USB controlStick using the e pre-programmed application using the GUI demonstration software.

Both fail identically when attempting to access the controlSTICK for debugging, CCS shuts down, leaving only a JAVA console window.

 

 

  • Michael,

    If I understand, this is an issue with Code Composer Studio crashing.  I am going to move this thread to the CCS forum for the experts there to comment.  In the meantime, please see if there are any debug logs as described here:

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#CCS_Diagnostic_Logs

    Here are a few more suggestions that may help:

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#General_IDE

    Regards,

    Lori

  • Attached the DebugServerlog file from the windows 7 64bit installation.

  • Additionally, i am able to initiate a manual debug session using the "Target" \ "Launch TI Debugger" menu item. I manually connect target , and am able to see the instructions in flash program memory (pre-programmed from the factory) in the Disassembly window, view Registers and single step etc.
  • Michael, Can you let me know the exact CCS version you are using? Also, can you check if any crash dump files were created during the CCS crash? More information here: http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#Crash_Dump_File Please attached if you find any. These information should help with the investigation. Thanks. Ricky
  • I am using the latest version with all of the updates posted a few days ago, Version: 4.2.3.00004
    log.zip
  • Thank you for providing this info. I searched and found the found the following post that might be related to this issue: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/51824.aspx

    You mentioned that you had looked at E2E and found other users had posted similar issues. Can you please point us to those forum posts? In the meantime, CCS team will continue to investigate the issue.

  • The other posts involved issues with XDS100 and had similar software version, files naming etc issues as described in the link you provided. Since I'm seeing this issue on two OSs I'm leaning towards a possibility of software revision issue. A few days ago, shortly after placing the order for the controlSTICK, I downloaded the March revision of CCSv4 from the ti website, installed it on both computers, licensed them with xds100 unlimited, 3 days later the latest revision of ccs came out and I upgraded both installs. I installed control suite with all of the options also from the web. I read all of the documentation and installed the two executables that support the 28069. The contolSTICK arrived with a corresponding CD with software, then I tried it and got the same results on both computers. My plan today is to uninstall all of the software from one of the machines, clean up the registry and any straggling remnants or folders if there are any. I will re-install the software on the CD that came with the controlSTICK and avoid upgrading any of the software. If it works, then I'll know. BTW, it is surprising to me no one else has encountered this yet. I appreciate the incredible complexity of CCS4 regarding support for so many varied architectures but I can't help feeling a little let down. This is my first encounter with CCS and it is not a good out of the box experience. This level of troubleshooting is expected when using eclipse with plugins and troubleshooting open ocd jtag as evidenced by the struggles of developers using open source software and development. I expected a much more polished and robust package in ccs.
  • TMX320F28069 controlSTICK is working now using CD software supplied with the hardware.  I uninstalled CCS4 Version: 4.2.3.00004 with all of the upgrades.  The version on CD is Version: 4.2.1.00004.  I setup the target configuration and succesfully entered debug mode with the project.  Although this may not have been necessary, I directed CCS to install in C:\TI alongside the controlSUITE software to make sure the paths had no spaces in it.  For reference, this installation was  done on the windows 7 64-bit machine.  I will repeat this for the windows xp sp3 machine...but I have high hopes.  I just have to make sure I keep a test computer around to check upgrades don't break the environment going forward and leave a golden development machine intact. 

  • Thank you keeping us posted and I am glad, that the setup is working and problem is resolved. We should still, on our end, find out as to why 4.2.3.00004 is not working and causing the crash. 

  • Michael,

    Based on the information given, I believe the crash was caused by installing the two executables that support the 28069 you got from the controlSuite over the latest CCS version.

    The version of the Flash Setup installer available in the ControlSuite is only applicable for CCS4.2.1 and below. CCS4.2.2 and above should have F2806x support out of the box without applying any patches on top.

    I'm sorry for the inconvenience this has caused, and I'll see if the controlSUITE needs to be updated or not.

    Regards,

    Ricky