Thanks Rafael!
↧
Forum Post: RE: 6713DSK Diagnostics Fails
↧
Forum Post: RE: Ultra librarian - TMS320C6748_ZWT_361 - Altium
In my previous post I had typo in url reference. The CAD file link is:
Regards,
Janet
↧
↧
Forum Post: RE: JTAG daisy chain with C6748 and C66x
Hi,
Yes, it is possible to create a configuration that has multiple devices and connect to them using a single debug session (and workspace, etc.). Check the wiki page below:
http://processors.wiki.ti.com/index.php/Target_Configuration_-_Custom_Configurations
The difference is that, instead of selecting routers, cores, etc. you will be selecting devices.
Also, keep in mind the extra length of the JTAG routing may limit the maximum TCLK speed - one of the parameters set in the Advanced tab of the target configuration editor. Check section 3 of the page below:
http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems
Hope this helps,
Rafael
↧
Forum Post: RE: DSS openSession
Robson,
[quote user="Robson Tovo"]Where do I access the Target configuration editor? Does this change saves to the .ccxml file?[/quote]
From inside CCS, you can simply double-click on any .ccxml file and it opens the target configuration editor. Any changes to it will be saved to the .ccxml.
[quote user="Robson Tovo"]How do I create a configuration to bypass all the cores I don't use?[/quote]
Check: http://processors.wiki.ti.com/index.php/Multi-Core_Debug_with_CCSv5#Debug_Configurations
You can also modify the .ccxml file in the target configuration editor and set all the other C66x cores to "Bypass".
Hope this helps,
Rafael
↧
Forum Post: RE: Combining .out files
Azim,
The link you provided seems to have all the information you need. Try running the command:
hex2000 app.out boot.out --section_name_prefix="data" --load_image -o ROM_simple.obj
Additional information on the hex2000 tool can be found here:
http://www.ti.com/lit/ug/spru513g/spru513g.pdf
Let me know if you need additional assistance!
BR,
↧
↧
Forum Post: RE: Getting CCS to use another folder for temporary usage other than using C:\Temp
After a bit of digging I found the way to do it using the GUI, but I want to be able to do the same thing from command line. Is this possible??? The snapshot shows the properties that I am trying to change (marked by "c:/Ricky_Changed_It_temp/f2837x/sun/debug")
Thanks,
Ricky Whitaker
↧
Forum Post: RE: AM335x starterware debug issue
Will,
Sorry, but Ki is out in vacation and I am unsure if he already has fully characterized this issue. I was only able to take a look at it today and, just like him, I can't seem to make any sense out of the problem. In my case, though, I randomly stop at breakpoints at that specific function irrespective of the line where it is set and the breakpoint type (hardware or software).
Just to confirm if the function call was being executed more than once, I set a small ETB trace job starting and stopping at the function addresses, and I can verify it is accessed multiple times, which confirms the expected behavior.
Just FYI, I set the PC Trace job (menu Tools --> Hardware Trace Analyzer --> PC Trace) as below:
Ki is back next week and I will be able to sync up with him.
I apologize for the inconvenience,
Rafael
↧
Forum Post: RE: Could not obtain valid waveform from TI CCS4 graph
Hi,
I am unsure what may be happening in this case, but I have some comments/tips:
- If the variables are double - i.e., floating point, why are you displaying them as 16-bit integers?
- some of the CCSv4.0 releases had severe issues to display graphs, especially dual graphs. I would be careful using such an old release.
If the changes to the parameters do not fix the display, you could try to get a CCSv5.5 or v6.0.1 to see if you can load the .out generated from the v4 project and display the graphs properly.
You can use a newer release without interfering with your previous one if you install CCS in a different directory and use a different workspace. Also, if you import the project, make sure to create a backup copy (CCS projects are not backwards compatible, therefore opening your existing project in a v6 session will render it unusable in v4).
Hope this helps,
Rafael
↧
Forum Post: RE: Problems view issue with custom build system
Roman,
Thanks for sending the project. I can see the pop ups and we are analyzing this.
Regards,
Rafael
↧
↧
Forum Post: RE: Forcing small memory model.. not...
Hi Lisa...
Just an FYI, the issue has been resolved with the help of a couple members in the MCu forum..
Here's the post for you edification:
-----
Hi guys..
Both of your suggestions helped and solved the issue...
Setting the include file as Leo suggested cleared all the warnings about redefinition..
Setting the data=small and the code=large solved the library incompatibility..:)
And finally setting the --near_data to globals (seems it won't take the blank setting), made that warning go away..
So, now its compiled, and I'll see if it loads and runs :)
Thanks again Randy and Leo..
(and yes Randy I agree with your rake on IDEs.. and will revisit your details on this)
↧
Forum Post: RE: Toolchain Setup GNaU for Stellaris LM3S1968 in Code Composer Studio (CCS)
I know this has to do with setting up driverlib-cm3 for the linker, but I don't know how to do this properly. Also, when it comes to specifying the linker command file what should I use?
↧
Forum Post: RE: Warning #770-D conversion from pointer to small integer
If you build with --verbose_diagnostics, the compiler echoes the problem source line with a ^ character indicating where the problem begins. Look in the Console view, not the Problems view, to see it. You would see that the problem isn't with buffer, but with converting &DMA1SA to an unsigned short. The problem is that, in large data model, pointers are 20-bits, and an unsigned short is 16-bits. This conversion loses bits. It doesn't matter because DMA1SA is always located in the first 16-bits of the address space. But at the time the compiler processes this line, that fact is not known. Thus the diagnostic.
It is a bug in the older compiler that no diagnostic is issued. You can disable the diagnostic with the option --diag_suppress=770. Or, you might prefer
#pragma diag_suppress=770
Thanks and regards,
-George
↧
Forum Post: RE: IPC example C6678 - shared memory
[quote user="Eran Hershber1"]I am trying to compile the 'shmIpcBenchmark_c6678' example with no success.[/quote]
I don't recognize this example. It is unlikely anyone on this forum can be of much help. Where did you get this example from? I may be able to direct you to a forum more likely to help.
Thanks and regards,
-George
↧
↧
Forum Post: RE: Combining .out files
Azim,
I'm not familiar with that error. I would look at the linker command files and memory maps for each of those out files to ensure they don't overlap. Hopefully one of the code generation gurus will see this post and lend us some help.
BR,
↧
Forum Post: RE: CCS ram/ flash bugs C2000 piccolo 28069 out of RAM
Forwarding your query to a CCS expert.
Regards,
Gautam
↧
Forum Post: RE: Programming Tiva targets with hex files - what HW?
Rafael,
Thanks for jogging my failing memory. A brief explanation:
We have a field service tool that uses hex files for updating a device's FW. The first two device types were an AVR AT90 and a Infineon C164. Both, by default, produce hex files that are 16-bit big-endian data. So that is what our service tool supports.
Rather than take the default 'CCS->Properties->Build->Steps->Apply Predefined Step->Intel-Hex' settings, I set them to produce a 16bit data, big-endian hex file. This allowed my existing tool to be used without modification.
A year+ passed and UniFlash became available. I assume that the program hex file option does not have a way of specifying the data width or endian-ness of the hex file. So byte stream mode is a logical default.
As our field service tool AND UniFlash will be difficult at this time to modify to accept another hex file format, my solution will be to create two hex files, one 16-bit big-ending and one byte stream.
I would recommend a couple of changes to UniFlash. If you would be so kind as to forward to the UniFlash team, I would appreciate it.
1) add more file types to the 'UniFlash->Program->Load Program->Browse" dialog.
2) in the documentation for supported file types, identify how is a file type determined, if it is by file extension, then a table of file extensions vs file type would be most useful.
3) Consider file types for intel hex files that would 'specify' the data width and ended-ness. I have seen hex extensions of .a90, .hex, .h86, ... I suspect .hex could be used for byte stream and .h86 for 16-bit, big-endian.
↧
Forum Post: RE: RE: Can't download CCS?
when downloading anything it takes me to "U.S. Government export approval" form. After filling it i get white page (404). I dont understand whats wrong.
↧
↧
Forum Post: RE: What's the replacement of __FUNCTION__ in ARM CGT5.1 ?
__FUNCTION__ is not a preprocessor name. It is a variable. You need to change your code to expect a variable where you want to use __FUNCTION__. The implementation of dbg_LogMsg needs to change to ...
int dbg_LogMsg(unsigned char, char *, const char *);
A call to it looks like ...
dbg_LogMsg(55, "ERR.", __FUNCTION__);
The GCC compiler documentation on __FUNCTION__ can be found at https://gcc.gnu.org/onlinedocs/gcc/Function-Names.html .
Thanks and regards,
-George
↧
Forum Post: RE: CCSv5.5 crashes on launch of debug session
Hi,
Do you have a sensor hub booster pack connected to your Tiva Launchpad while testing the program.
At the sensor hub example programs which particular example are you trying out?
Have you tried the temperature_tmp006 example program and see the output at serial console?
- kel
↧
Forum Post: RE: Setting up CCSv6 on Ubuntu 64bit 14.04
Hi Arun,
just thought to check for any updates with your enquiry.
Best regards,
Lisa
↧