TI's Webench Altium Connector User's Manual(see attached). (Please visit the site to view this file)
On page 9 the directions indicate to download a simulation export file. The figure on page 9 shows 3 output types; schematic, board layout and simulation.When I run export, I only have an option to export a schematic or a layout. Why is the simulation export option not available in my window?
I am having the same problem with CCS 5.4.0.00091.
[quote user="desouza"]Please follow the evolution of this at the wiki page below:
http://processors.wiki.ti.com/index.php/J-Link_Emulator_Support[/quote]Having looked at the history of that wiki page shows that a warning saying "Note that Jlink is not supported/tested with CCSv6.x." was added after I created this thread. Therefore, won't worry about using J-Link with CCSv6.
[With some targets such as AM3517 using a J-Link is significantly faster than a XDS100v2, but with a TMC129 there was no noticeable difference in speed between using a J-Link or Stellaris ICDI and the J-Link didn't support hardware watchpoints]
Hi Shinya,
Could you please send me the file you are trying to load for me to reproduce this problem? You can attach to the forum thread or email to me at v-yang@ti.com
Thanks,
Victor
Hi Timothy,
[quote user="Timothy Frank"]I am using CCS V6, with a CCS V5 license file[/quote]
CCSv6 license file is compatible with CCSv5 but not the other way round! I would like you to check the actual license being used by your CCSv6.
Regards,
Gautam
Can you provide the Eclipse log mentioned here?
http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv6#CCS_Diagnostic_Logs
Thanks
ki
Ok, thanks. There was some reference to a clock in the log, hence I was curious. The log is still under analysis.
ki
Actually - I guess the other issue (moving or renaming a workspace) is also an absolute path problem. I'll be the Workspace would use absolute paths to the project files.....ah well....Might be nice to have an option of "projects are relative to workspace" for 'dangerous' users such as myself.....
[quote user="Robbie Valentine"]
When I comment out the
SysCtlDelay(1);
instruction and immediately hit the for loop after the GetRDAC() function CCS shows 0 for rdac in the watch window. When I have the delay in i get the valid value as expected.
[/quote]
I suspect this has more to do with the device/hardware rather than the tools, and that the SysCtlDelay, for some reason, is required before the variable gets udpated to the correct value. If you step through the assembly code in CCS it might give you a better understanding of exactly which instruction is updating the value of the variable and where in the sequence of code that is happening.
As to why the SysCtlDelay is required (if that is really the case) I think the folks in the TivaWare forum would be in a better position to answer that.
Tony,
I don't think I've heard of such an issue in CCS 5.5. Would you be able to share a simple project that demonstrates this behavior?
[quote user="mohamed azim"]Screen shots of the steps for combining the HEX files would be very useful.[/quote]
Screen shots don't make much sense, because this entire process happens on the command line. And the commands you need to run are shown in the article. The ofd470 commands show you the state of the files before and after they are combined. Since you are using the C2000 compiler tools, replace those commands with ofd2000. The hex470 commands do the actual work. Replace those commands with hex2000.
Thanks and regards,
-George
Hi,
I have a problem with CCSv6.0.0 in combination with an custom build-system (SCons). After building (not always, but regularly), the following errormessages pop up. This is very annoying, as you have to close the dialog every time it appears.
This seems to be a bug with the CCS, as with the normal CDT eclipse, this error does not occur. Do you have any advice in how this can be avoided? Can we expect a bugfix of this?
Kind regards,
Roman
One of the Wireless Connectivity forums is the best place for this. I wish I could be more specific, but I just don't know. I recommend you start a new thread on one of those forums. Just take your best guess as to which forum. If you get it wrong, they'll move it for you. It is not a big deal at all.
Thanks and regards,
-George
Hi,
I have an issues with problems view in CCSv6.0.0 when using a custom build system (SCons).
When there are compile errors or warnings, these appear as they should.
But the errors remain in the Problems view even if they have been fixed and a new compilation finishes without problems.
This seems to be a CCS related bug, as the CDT version of eclipse does not behave like this.
Do you know of any workarounds to this problem? Will this be fixed in a future version?
Kind regards,
Roman
If you want to request this then we need to continue this By email. I will need the business case to see if we can do it. c-cockrill@ti.com
Hi,
Assuming the install path is correct (D:\ drive), can you see if the file is physically there? I have seen in the past that disk corruption causes the file to become inaccessible or simply broken, therefore CCS is unable to access or properly execute it.
This file changed very little over the years. The one I have here has a size of 262800 bytes.
To work around this issue you could either scan the disk for errors (perhaps the file can be recovered) or either install a newer release of the TI emulators package or reinstall using the instructions at the wiki page below:
http://processors.wiki.ti.com/index.php/XDS_Emulation_Software_Package
To find out the TI Emulators package version you have, go to the menu Help --> About --> Installation details
Hope this helps,
Rafael
Hi Ki,
When I go to Help --> CCS Support. I do not get any response from the program.
Omar
Thanks, George. It worked.
Had to do it the right way: declare vars on .c files and extern on .h files.
David, thanks for sending the logs. It looks like traceSettingsPath at line 20 of autotrace.java needs to be changed to the absolute path of the file (including the drive and all the sub-directories).
I agree that upgrading to CCS v6, which includes upgrading to the latest compiler, is likely to fix this problem. I hope that is a practical solution for you.
Thanks and regards,
-George