Hello,
Thank you for bringing this to our attention!
I have forwarded this info to the Webench team, and reply here once I hear back from them.
Hello,
Thank you for bringing this to our attention!
I have forwarded this info to the Webench team, and reply here once I hear back from them.
The published .stp file has been updated.
Project can build without errors and warnings, but it links forever using v7.4. This problem happens in both ccs v3 & v5. However, the same project builds successfully with compiler v6.x. All the examples in the tutorial could work with both compiler versions (v7.4 & v6).
Hi,
Sorry for the delay on this I must have missed it come through.
You are right, WEBENCH will not allow you to design using this device in Over Voltage Protection mode (OVP) at full load. If this is something that you really want to do we would recommend consulting the datasheet for design guidance.
Best regards,
Tommy
If you are using CCSv3.1, then you are most likely using BIOS 4.x. That version of BIOS is not compatible with CCSv6 (or v5 or v4). That is why you are having import issues. You need to migrate your project to BIOS 5.x first by converting the BIOS 4.x CDB files to BIOS 5.x tcf file. See:
http://processors.wiki.ti.com/index.php/Migrating_from_BIOS_4.9_to_BIOS_5.x
If you have any question with this migration, I suggest you post them in the TI-RTOS forum where the BIOS experts there can help you best.
Good luck.
ki
Which exact keystone device are you using? In some devices the DSP is held in reset by some application processor (ARM) and you need to run a routine to release the DSP from reset (usually via some GEL routine).
Ki,
Thank you for your prompt reply.
Yes, I was wondering how exactly I would have to alter the values of my registers (for example, how do I set the value of the CTRL register, say, to 5h?). I probably should have been more specific with my questioning, apologies.
Okay, so the way I understand it, I can reference by address without the header file, and the header file will enable me to use a name as a reference? In other words, I do not need any header file to access them using just the address, am I correct?
As far as the version of CCS goes, I shall do that!
Thanks again for helping out!
Regards
Madhsuudan
Hi,
Good, that you already recovered your launchpad, and be able to use it again.
Now, you have to know why it was locked. Possible that the previous program you load to it before caused it to be locked. Some causes are mentioned at the "JTAG Communication Failures" post.
- kel
Hi Ki,
Thank you for your reply. I am using Intel® Core™ i5-3230M CPU @ 2.60GHz × 4 , 4GB RAM, Ubuntu 12.04 LTS 32 bit. Yes, I modified ccstudio.ini file. Please have look at my ccstudio.ini file below and let me know if any modifications are required.
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
-product
com.ti.ccstudio.branding.product
--launcher.XXMaxPermSize
512M
-showsplash
com.ti.ccstudio.branding
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dosgi.instance.area.default=@user.home/workspace_v5_5
-Dorg.eclipse.equinox.http.jetty.customizer.class=com.ti.ccstudio.gui.composer.http.jetty.MaqettaJettyCustomizer
-Xms512m
-Xmx1024m
Thanks & Regards,
Anjibabu
Hi all,
Currently I am using a very old TI DSP (C33 series) to build a firmware for our device.
I met a problem that when I tried to link a .out file.
The .cmd file looks like:
======CMD START=====
-r
-x
d:\DEV\LCDIST\DISP\PTFSYST\BOOT\sbi_timer.obj
d:\DEV\LCDIST\DISP\PTFSYST\BOOT\sbs_atInit.obj
d:\DEV\LCDIST\DISP\PTFSYST\BOOT\sbs_atPerm.obj
d:\DEV\LCDIST\DISP\PTFSYST\MEMOIRE\smf2_drv.obj
d:\DEV\LCDIST\MAIN\OBJEMU_IEC61850\dm_ITMem.obj
d:\DEV\LCDIST\DISP\PTFSYST\MEMOIRE\smf_drv.obj
-l d:\DEV\LCDIST\MVP\UCA2\OBJEMU_IEC61850\mvp_IEC61850.lib
d:\DEV\LCDIST\DISP\PTFSYST\BOOT\sbi_tmi.obj
d:\DEV\LCDIST\SUPERVISION\OBJEMU_IEC61850\dsuf_msf.obj
d:\DEV\LCDIST\SUPERVISION\OBJEMU_IEC61850\dsu_Boot.obj
d:\DEV\LCDIST\SUPERVISION\OBJEMU_IEC61850\dsu_Coproce.obj
d:\DEV\LCDIST\SUPERVISION\OBJEMU_IEC61850\dsuf.obj
...
d:\DEV\LCDIST\SUPERVISION\OBJEMU_IEC61850\dsuf_tr_cmde.obj
...
-l d:\DEV\LCDIST\MAIN\OBJEMU_IEC61850\main_IEC61850.lib
d:\DEV\LCDIST\SUPERVISION\OBJEMU_IEC61850\dsuf_mvp.obj
d:\DEV\LCDIST\SUPERVISION\OBJEMU_IEC61850\dsuf_mvp_pcf.obj
d:\DEV\LCDIST\SUPERVISION\OBJEMU_IEC61850\dsuf_mvp_str.obj
...
-l d:\DEV\LCDIST\DISP\LIV50300PL\util\util.lib
-l d:\DEV\LCDIST\lib\tex\rts.pc.lib
-l d:\DEV\LCDIST\lib\tex\mathrco2acfim.lib
SECTIONS
{
.text:
{
*(.text)
}
}
======CMD END=====
Then I adjust the location of the overflowed .obj files. If I am lucky, the overflow problem may disappear, if not, another overflow problem will appear.
After a lone adjustment work are done, the overflow problem disappeared at last, but the next time when we fix some bugs in the code or try add some new features to the firmware, we link all libraries and .obj files again, then we will encounter some other overflow problems.
The adjustment work for some .obj files need to be done again, the procedure of adjusting the location of some .obj files is like a nightmare, sometimes it makes me crazy.
How can we avoid this from happening? Is there any way to let the overflow problem never show again?
Thank you very much!
Just installed CCSv6 (previously had CCSv5.X). I now have a problem trying to create a new Grace project for
a MSP430G2432 target. I have all the latest updates for CCSv6. The host is running Windows 8.1.
Here are my steps:
Selected File->New->CCS Project.
In CSS Project window set Target: -> MSP430G2432
Connection: {did not change from TI MSP430 USB1 [Default] }
Set Project Name: EM4325_tag
Project templates and Examples: Selected "Empty Grace (MSP430) Project
Clicked "Next" button.
At top of next popup dialog is:
RTSC Configuration Settings
None of the currently selected products supplied the Target. Please specify the Target manually, or try using a pre-3.30 version of XDCtools.
I probably missed a checkbox on something during the installation of CCSv6. Any help would be appreciated.
Thanks
leon
Hi AartiG,
Thank you very much, you help me a lot.
I'm using Windows 7 Professional 64bit as Admin. Update of TINA-TI is not possible. I get an error message "INVALID ENUM VALUE" .
Is there any solution for that Problem ? Can I download the Update Software for manually Installation ?
I'm using Windows 7 Professional 64bit as Admin. Update of TINA-TI is not possible. I get an error message "INVALID ENUM VALUE" . Installed TINA-TI Version is 9.3.50.40 SF-TI .
Is there any solution for that Problem ? Can I download the Update Software for manually Installation ?
Hi,
Thread you referred is related to undefined identifiers but in my case I am getting undefined identifiers as well as errors in header files. Please find below the console log. armadillo_bits folder belongs to library that I added.
(Please visit the site to view this file)
Thanks & Regards,
Anjibabu
That's Great, Peter!
Goodluck & Regards,
Gautam
Thank you for heads-up on the TINA update problem.
We are looking into it, but it is complicated by the fact that we are unable to reproduce the error on our end.
We are working on the problem and will post any findings to this thread.
Thank you again for letting us know, and thank you for your interest in TINA-TI.
Regards,
John
[quote user="ReinierC"]I am using CCS 5.5 (C6000 codegen tools v7.6.0) for building our project, which consist of a main executable project and 15 dependent static libraries.[/quote]
If there are 15+ projects being rebuilt each time, I wouldn't consider 3-4 minutes as excessively long ( it depends on the size of the projects, of course). Do you already have parallel builds enabled?
If building from command line is an option for you, that could potentially be faster and avoid some of the overhead that comes with the CCS GUI.
http://processors.wiki.ti.com/index.php/Projects_-_Command_Line_Build/Create
hi....even I'm facing the same prob. did u find any solution? If so plz let me know.
thank you..
The link order is a big influence on many aspects of the output executable file. But whether the .bss section gets filled with 0 is not one of them.
Does the auto-generated linker command file have any directives regarding the .bss or .far sections?
Thanks and regards,
-George