Yes. Except the C code should use the "csymbol" names per the technique I mentioned in my first post.
Thanks and regards
-George
↧
Forum Post: RE: How to get the start address of the memory segment defined in linker file.
↧
Forum Post: RE: mod .common$.diags_ENTRY / EXIT to auto calculate in System Analyzer
Hi Norton,
I will respond to all your questions, but before I do so, please export the data from your log view into a .csv file and send it to me. I want to take a look at the logs that are showing up and get back to you as soon as I have seen these. Sorry for the delay in replying.
Thanks &
Regards
Ralph
↧
↧
Forum Post: RE: Errors #17003-D, #10015-D and #10281-D appearing out-of-the-blue
The key point is this: All of the near variables must be allocated within 32K bytes of each other. That's the amount of memory which can be addressed by 15-bits.
[quote user="Remco Poelstra"]I'm unsure how you've determined that .data_sh1ram and .data_sh2ram contain near variables. I can't find any such hint in the map file.[/quote]
That map file doesn't tell you that. I determined that from the error diagnostics you show in earlier posts.
[quote user="Remco Poelstra"]I've put some variables in L1 and L2 RAM to make them faster to access by the core. Is that spoiled by them becoming far variables?[/quote]
The problem is that you have near variables too far apart in memory. I see two ways to fix the problem. One is to move the near variables sections around so they are close to each other. The other is to not have near variables in some of the sections.
This wiki article talks about this problem from a different perspective. I'm worried it will only confuse you. But perhaps some of the background information at the beginning is helpful.
Thanks and regards,
-George
↧
Forum Post: RE: XDS200 USB detection issue in Ubuntu in Paralles on Mac
I have the same issue. Just got four XDS200 emulators. All of them fail to connect on MacBook with Parallels 9.0.24237. I have been running XDS100, MSP430FET, USB560, and other emulators on this combination before with CCS 4 and no issue. I cannot use the XDS200 with CCS 6.
using Windows 7. When I plug the emulator, it enumerates on the Mac as:
- XDS2xx USB Emulator - Composit:
- Product ID: 0xbef0
- Vendor ID: 0x0451 (Texas Instruments)
- Version: 1.00
- Serial Number: S200-000E99039000
- Speed: Up to 480 Mb/sec
- Manufacturer: Spectrum Digital
- Location ID: 0x1a120000 / 4
- Current Available (mA): 500
- Current Required (mA): 500
The Windows machine then installs two drivers:
- XDS2xx Emulator CDC Serial Port (COM10)
- XDS2xx User CDC Serial Port (COM12)
When I use a debug session on CCS v 6, it just hangs. If I run the Test Connection, I get:
- [Start: Texas Instruments XDS2xx USB Emulator_0]
- Execute the command:
- %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
- [Result]
- -----[Print the board config pathname(s)]------------------------------------
- C:\Users\ADMINI~1\AppData\Local\TEXASI~1\ CCS\ti\0\0\BrdDat\testBoard.dat
- -----[Print the reset-command software log-file]-----------------------------
- This utility has selected a 560/2xx-class product.
- This utility will load the program 'xds2xxu.out'.
Closing the window hangs CCS. Disconnecting the emulator finishes the process with an error if emulator fail to connect.
If I use BlackHawk USB560M and Spectrum Digital XDS560v2 STM with CCS 6, I am also unable to get them to work, but CCS does not hang. I get this error:
- [Start: Blackhawk USB560-M Emulator_0
- Execute the command:
- %ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
- [Result]
- -----[Print the board config pathname(s)]------------------------------------
- C:\Users\ADMINI~1\AppData\Local\TEXASI~1\ CCS\ti\0\0\BrdDat\testBoard.dat
- -----[Print the reset-command software log-file]-----------------------------
- This utility has selected a 560/2xx-class product.
- This utility will load the program 'bh560usbm.out'.
- The library build date was 'May 21 2014'.
- The library build time was '17:30:09'.
- The library package version is '5.1.507.0'.
- The library component version is '35.34.40.0'.
- The controller does use a programmable FPGA.
- The old VHDL code has a version number of '0' (0x00000000).
- The new VHDL code has a version number of '386336272' (0x17070610).
- An error occurred while hard opening the controller.
- -----[An error has occurred and this utility has aborted]--------------------
- This error is generated by TI's USCIF driver or utilities.
- The value is '-183' (0xffffff49).
- The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.
- The explanation is:
- The controller has detected a cable break far-from itself.
- The user must connect the cable/pod to the target.
- [End: Blackhawk USB560-M Emulator, 20-pin JTAG Cable_0]
Similar for Spectrum Digital. I am trying to debug a Tiva TM4C129 with an adapter board.
↧
Forum Post: RE: XDS200 on Mac with Parallels Windows VM
If I use BlackHawk USB560M and Spectrum Digital XDS560v2 STM with CCS 6, I am also unable to get them to work, but CCS does not hang. I get this error:
- [Start: Blackhawk USB560-M Emulator_0
- Execute the command:
- %ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
- [Result]
- -----[Print the board config pathname(s)]------------------------------------
- C:\Users\ADMINI~1\AppData\Local\TEXASI~1\ CCS\ti\0\0\BrdDat\testBoard.dat
- -----[Print the reset-command software log-file]-----------------------------
- This utility has selected a 560/2xx-class product.
- This utility will load the program 'bh560usbm.out'.
- The library build date was 'May 21 2014'.
- The library build time was '17:30:09'.
- The library package version is '5.1.507.0'.
- The library component version is '35.34.40.0'.
- The controller does use a programmable FPGA.
- The old VHDL code has a version number of '0' (0x00000000).
- The new VHDL code has a version number of '386336272' (0x17070610).
- An error occurred while hard opening the controller.
- -----[An error has occurred and this utility has aborted]--------------------
- This error is generated by TI's USCIF driver or utilities.
- The value is '-183' (0xffffff49).
- The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.
- The explanation is:
- The controller has detected a cable break far-from itself.
- The user must connect the cable/pod to the target.
- [End: Blackhawk USB560-M Emulator, 20-pin JTAG Cable_0]
Similar for Spectrum Digital. I am trying to debug a Tiva TM4C129 with an adapter board.
The Spectrum Digital and BlackHawk USB560 worked fine using CCS v4.
↧
↧
Forum Post: RE: Dynamic linking library for C665x
Hello George,
Thank you for your reply. Could you give me an advice if you have already gotten it from your expert?
Regards,
Kazu
↧
Forum Post: RE: Migrating CCSv3.3 example project to CCSv6
Ki,
I installed the stand-alone version of 3_30_01_25. That version was detected when I started up Code Composer and I added it and then went to Windows->Preferences->Code Composer->RTSC and selected that version in the pull-down for XDC tools.
However, when I imported the legacy v3.3 project via the wizard (I used video_preview project from DVSDK 1_11) I still get the error:
!WARNING: Unresolved tool: com.ti.ccstudio.buildDefinitions.C6000.Debug.37064202::XDC
↧
Forum Post: RE: CCS5.3.0: meta-data cannot be interpreted
Hi Francois,
I'm attaching a fixed version of your .cproject file. I had to adjust the tool reference IDs.
Please upgrade to the latest version of CCS (v6.0.1), if you haven't already. The bug that caused these types of project corruption has been fixed in newer builds of CCS.
Thanks,
- Baltasar
↧
Forum Post: RE: ccs6 Cannot read System Setup data from XML file
Hi Billy,
Did you try running fsclean? just curious if that helped at all. If you tried it and you still have the error, can you attach your ccxml file here?
Thanks
ki
↧
↧
Forum Post: RE: CCS studio
Hello,
As a new user, I strongly suggest you go through some of the introductory training material for CCS. Check out the CCS training page: http://processors.wiki.ti.com/index.php/Category:CCS_Training
Thanks
ki
↧
Forum Post: RE: Emulator will not stay connected
Hello,
Are you using a USB hub with your laptop or are you plugging the cable directly to a USB port physically on your laptop?
Thanks
ki
↧
Forum Post: RE: content of a memory of a pointer in Watch Window
Hello Owen.
I would instead suggest using the memory window at the desired address.
Thanks
ki
↧
Forum Post: RE: Migrating from CCSv3 to CCSv6 compilation error
Thank you for submitting a test case. I can reproduce your results.
I cannot explain why the compiler issues that diagnostic. So, I submitted SDSCM00050807 to the SDOWP system. Feel free to follow it with the SDOWP link below in my signature. One of two things may happen. One, this will be confirmed as a bug and fixed in a future release. Or two, it is determined this is not a bug, in which case an explanation of why a diagnostic is needed will be supplied.
Thanks and regards,
-George
↧
↧
Forum Post: RE: CCSV6 Product Families Support
Hi Charlie
here is also a video showing this:
https://www.youtube.com/watch?v=IkrBOidvdG8
Best regards,
Lisa
↧
Forum Post: RE: Warning: #10247-D creating output section "BSLSKEY" without a SECTIONS specification.
I think you are getting confused, in part, because you name everything bslkey, with only minor variations. While all these things are in different namespaces, and thus can have the same name, it is wise to avoid doing that until you understand all the differences between them.
Here is what you need to do. I'll name everything bslkey_something, where that something describes what it is. Note I use all caps for the memory range name, following the unwritten convention for linker command files.
In C code you need to write ...
#pragma RETAIN(bslkey_c_variable) #pragma DATA_SECTION(bslkey_c_variable, "bslkey_section_name") const WORD bslkey_c_variable = 0xAA55;
In the linker command file you write ...
MEMORY { ... BSLKEY_MEMORY_RANGE : origin = 0xFFDA, length = 0x0002 ... } SECTIONS { ... bslkey_section_name > BSLKEY_MEMORY_RANGE ... } Hope this helps ...
-George
↧
Forum Post: RE: More fun with CCS6 and DM6437
OK, definite progress! Now it's whining about the version of DSP/BIOS tools with which the project was originally created. I bumbled around in the CCS App Center and found a "DSP/BIOS v5" download. Is that the ticket to success?
↧
Forum Post: RE: wlan_station errors
I was able to get the wlan_station example built without problems in CCS 6.0.1. I simply imported the ti_rtos_config and wlan_station projects into CCS and was able to build without errors.
As far as the example itself not running as expected, I would suggest posting that question to the SimpleLink forum for the experts there to comment on.
↧
↧
Forum Post: RE: CCS6 update error
Could you please post your logs? You can find them in <installdir>\ccsv6\install_logs* - if you zip up all the install_logs* folders there and include the <installdir>\ccsv6\eclipse\downloads\*.log file, I could take a look and see what's going on.
Thanks
Danish
↧
Forum Post: RE: UniFlash Tiva LM USB DFU interface MISSING
Thanks Ricky, didn't think of looking that up. I appreciate the info.
Also, thank you for looking into my other issue, it has been a show stopper for us for quite a while now.
-Matt
↧
Forum Post: RE: CCS v5.5 Update Errors
Many thanks for your swift reply, danishinnis. I'll post back if I encounter any problems!
↧