Hi Nick,
We checked Altium version 14 and it opens in it as well. Can you please ensure that you are double clicking on the Schdoc and not the PRJSCR or PRJDOC file?
Thanks,
Gerold
Hi Nick,
We checked Altium version 14 and it opens in it as well. Can you please ensure that you are double clicking on the Schdoc and not the PRJSCR or PRJDOC file?
Thanks,
Gerold
Thanks for all your help and suggestions. I have worked around the problem by signing up for the 90 day license. Works fine.
[quote user="Franz Boeni"]The error happened as I told you before. [/quote]While searching the forum came across a thread which describes what sounds like the same problem - see Flashing ARM does not work anymore after update to CCS5.5. That thread has an updated FlashStellaris.dll which may solve your problem.
I'm new to Code Composer, so please be patient.
I am inheriting a project that uses a TI C55 DSP with a CCSv4 development environment. The computer in our lab (which I don't plan to use for primary development or debugging) is able to successfully compile and run the debugger. A partial screenshot is here:
However, when I loaded CCS in my laptop and imported the project, the debugger cannot find the main program, and therefore does not run, as shown below. I am expecting the debugger to find the main() thread in startup.c, which is partially shown, but it does not. There's probably something fundamental that I am missing or needs to be changed in my compile/debug options, but can't seem to find it.
I am getting a <symbol is not available> message.
Thanks in advance for any help you may have.
Kevin
Rafael,
The picture you pasted just connect to one core every ccs, it's also OK for me. You can try connect all core every ccs,when you connect to the second ccs, it will stop woking.
The error shown in the message box I sent before means ccs has stopped woking, it appears a problem which leads to program stop woking normally.
Regards,
Si
Hi Robert,
I've attached a patch which you can use on CCS v6.0.1.00040.
Thanks,
- Baltasar
Hi,
I am a debugging a program on my 6657 EVM board and get this error.I am working with xds 100
C66xx_0: Breakpoint Manager: Retrying with a AET breakpoint
C66xx_0: Trouble Setting Breakpoint with the Action "Continue or Finish Stepping" at 0xffffffff: (Error -1175 @ 0x7B835C) Requested operation failed for security violation. Check security/priviledge settings, and retry the operation. (Emulation package 5.1.232.0)
Please advise.(Please visit the site to view this file)
The code is attached.
Ivgeni.
Hi Rafael,
Turn on the "CDT GDB debugging" works great. I would suggest that you talk with the CCS team to make it a default. This is especially useful for university classroom environment where regular C/C++ programs are exercised before going to Launchpad.
thanks again,
frank
Hi Ki,
Yeah I am new to CCS, but I required it very urgent for my project work urgently.
So I asked for the help.
Thanks for your support and feedback. :)
Regards
Gaurav
Bosch India
Sudarshan,
TPS54231, TPS54232 and TPS54233 are fixed switching frequency devices (570kHz, 1000kHz, and 300kHz).
You have to adjust your design input parameters such that Tj does not exceed 150 degC.
For the test conditions of VinMax=28V, Vout=4.8V, Iout=2A, fsw=1MHz (inherent frequency for TPS54232)
PowerDissipation=1.5459 Watt
Tj= = TA + ( IC_PD * ThetaJA) =30 + (1.5459*100) = 184.6 degC
Either try TPS54231 or TPS54233 (their cost is also 55 cents) because of lower switching frequency or LM3485 with IC_Cost= 52 cents.
Regards,
Flora
Hi Carl,
The syntax the looks ok. What is likely happening is that all the .text is getting allocated prior to this specification and so when it reaches this line in the linker command file there is no .text from libmath.a left to allocate. Try moving this specification earlier in the linker command file (before other .text sections gets allocated).
Here is a related thread for reference:
http://e2e.ti.com/support/development_tools/compiler/f/343/t/139984.aspx
Please keep us informed
Best Regards,
Lisa
I have an old C54x project compiled in CCSv3.1 and I'm using CCSv6 and CCSv5.5 for debug only. I could not get CCSv3.1 to install on Windows 7, so I tried CCSv5.5. Also we are using a BlackHawk USB560v2 which is not supported by CCSv3.3. I am using the .gel file from CCSv3.1.
CCSv6 and CCSv5.5 work and I am able to step through code and examine variables.
Hi Greg
The error has been fixed and the model can now be exported successfully. Please try from your end and let us know if you are facing any issues.
Thanks
Ranjani
Clement,
I did some tests on your example code and found out the watchpoint is taking some time to react and halt the target.
I modified your testcase as shown below and I found out the target is halted inside the delay loop instead of the printf() call. I measured the number of profile clock showed something around 20 cycles
int main(void) { unsigned int count_delay; printf("hello world\n"); hi.word1 = 123; for (count_delay = 40; count_delay > 0; count_delay--); hi.word1++; for (count_delay = 40; count_delay > 0; count_delay--); (...)
Looking at the watchpoint properties I can spot it is "imprecise" by nature. What it means is it takes some cycles to react and halt the target - which is usually a property of the device itself.
I will do some more testing on this testcase and see if I find something that indicates otherwise. I will report back if I find something different, ok?
Regards,
Rafael
I think my first response, while correct from a purely technical viewpoint, is nonetheless off the mark.
[quote user="David Sabol"]By setting the floating point support to VFPv3D16 the issue goes away. Is this because the rtsv7R4_T_be_v3D16_eabi.lib is built with that option so they need to match?[/quote]
Yes.
But this raises a better question: Why do you choose to use the RTS library rtsv7R4_T_be_v3D16_eabi.lib? The typical method is to let CCS choose your base build options based on your choice of target processor, and then let the linker choose the best RTS library for you based on your build options. You aren't doing that, and I don't know why.
Thanks and regards,
-George
Thanks. That did the trick. You might consider adding a warning to address this scenario.
[quote user="David Littell"] (Please note that the "Load Program" approach won't work in this case as it blows away the bootloader when I use it to program the application and blows away the application when I program the bootloader - just imagine my joy. The only way I could find to not destroy the bootloader was to use Fill Memory/Load Memory to program the app from the "TI text" file.)[/quote]Under CCS Project Properties -> Debug -> MSP430 Properties -> Download Options what is "Erase Options" set to?
I think setting Erase Options to "Replace written memory options, retain unwritten memory locations" may allow the "Load Program" approach to change just the booterloader or application.
Si,
I filed the bug SDSCM00050737 today. Please check its status and a published workaround on the link SDOWP in my signature below.
Regards,
Rafael
[quote user="will hsu90429"]Is there any update on this issue?[/quote]
Hi Will,
Sorry for the delay in response. I was away for awhile. The latest status is this:
It doesn't appear to be a debug issue. One theory is that because the function in question is an ISR, halting in an ISR can impact the behavior of the system. According to one of the emulation engineers, It could be that the EDMA might have been triggering off or causing an error during a halt inside the ISR prior to clearing the interrupt and disabling the transfer. We don't know too much about the behavior of the EDMA on the device, I am requesting help from the device experts.
ki
[quote user="George Mock"]CCS does not support building executables, DLL's, libraries, etc for execution on hosted systems like Windows, Linux, or Apple. [/quote]However, since CCS is built upon the Eclipse CDT, this thread develop a PC application with CCS suggests it is possible to use CCS to compile and debug a local executable.
[I haven't tried it myself]