All of that is correct. I have not been able to start a debug session on the Windows 7 PC.
↧
Forum Post: RE: Emulator will not stay connected
↧
Forum Post: View LOG_printf in CCS6
Can someone please guide me how to view my Log_printfs on CCS v6? I am trying to get a Hello, World program running that uses LOG_printf (&trace, "hello world!"); from example code. Where do I view the output? I am using an eZDSP 5515 board.
↧
↧
Forum Post: RE: CCSv5 breakpoints don't work after code reload
[quote user="Eddie3909"] I've switched 100% to first selecting the core and then right clicking on the column adjacent to the code where I want the breakpoint, then selecting the HW breakpoint option.[/quote]
This is what I do too.
[quote user="Eddie3909"]I think the issue is that we're used to simply double clicking in the column. That creates a software breakpoint??[/quote]
It depends... if the debugger memory map specifies that program memory location as writable, then it will default to a software breakpoint. If the debugger memory map says that it is read-only, then it will automatically use a hardware breakpoint. If no debugger memory map is used (or that region is not defined in the map), then it will assume the memory is writable.
[quote user="Eddie3909"]Hardware breakpoints definitely work better. It there a way to configure CCS so that is sets a HW breakpoint when double clicking?[/quote]
If the memory is writable, then it will always default to a software breakpoint. I don't think you can change this behavior. Sorry
Ok, so I'm a bit confused now. You mentioned that you confirmed you are using HW breakpoints but then you mentioned that you have double-clicked in the editor margin to reset breakpoints (which I assume is defaulting to SW) but then also that you right-click on the column and use the option to explicitly set HW breakpoints. Which types of breakpoints is causing the problems?
↧
Forum Post: RE: MSP430, CCS 5.5, save\dump memory to hex file
Hi Ricky,
Thanks for your reply, I have been at this all day.
You are correct, I was able to compare against a .hex file with your suggestion of selecting "All Files", even though it is not shown as an expected file type.
However, the plot thickens. I had reprogrammed my boot loader with CCS and then downloaded the application with the serial port, so I have a clean start. I compared the file and it failed at the second byte (0x8001). As this file was from earlier experiments, I decided to create a new hex file from a memory save\dump.
I saved memory from 0x8000 to 0xFFFF, my area of concern. I can only save it to a .out file if I want to end up with a .hex file, which I did. Then I ran "hex430.exe -i -o=filename_out memdump.out". The file FAILS COMPARE! Looking at it in the editor, it is not even close. This whole process seems to be broken.
So, I decided to use the MSP430Flasher to save\dump memory. It can't access the FET430 so I need to exit my debug session in CCS... OK. Then, it doesn't like the firmware version in the FET430. It needs to program it... OK. I have programmed this thing at least 8 times today between CCS and MSP430Flasher.
So, now I can download directly to a hex file (even though the MSP430_Flasher_Doc.pdf doesn't explicitly state that this is supported with the "-r" option. Using the command line "MSP430Flasher.exe -n [mem_dump.hex,MAIN]".
Then back to CCS, reprogram the FET430, compare the file. The file FAILS COMPARE! So, looking at the hex file in the editor, it starts at address 0x2100 and goes to 0x7ff0 which I believe is not valid memory for my part. I deleted that portion of the file so that it starts at address 0x8000. I perform the verify and IT SUCCEEDS!!.
This leaves several key points on file verify deficiencies in the TI tools:
- The CCS memory save and convert is BROKEN
- Switching between Flasher and CCS is cumbersome and time consuming
- The verify tools do not allow the user to specify a range
- The download tool in MSP430Flasher does not allow the user to specify a range
- CCS does not list .hex or .TXT as default types in the compare menu
- The document MSP430_Flasher_Doc.pdf does not fully describe files supported for the "-r" option
- MSP430Flasher did not acquire the correct memory range even though the part is indicated on the command line.
- On a side note, the memory save to .dat does not allow for address information to be inserted with the file (at least I haven't found it). And it does not support columns. Every mode that I have used is just a long column 1 document which is not the most user-friendly.
I appreciate your suggestion as that did get me over the hurdle but was really one small part of the puzzle. Please make the process of comparing files-to-parts, parts-to-files, files of many types, and user controlled address ranges available and simpler.
I have several products that I have to support in this manner. They were migrated over from Freescale S08 parts to MSP430. However, I must say that this process was MUCH simpler and flexible on the S08 parts using the older version 5.x to 6.x Code Warrior tools (ancient stuff). I expected the new Java wiz-bang CCS tools to be a breeze but it is not.
Regards,
Jim
↧
Forum Post: RE: Webench and the TIDA-00056 for an H2S Sensor
Ajinder,
I'm sorry to say that I am at my wits end. for the life of me I cannot understand what I'm doing wrong however when I put the sensor in testing I cannot get a reading on any H2S. Are there limitations to the TIDA-00056? the sensor I am using is 0-100ppm H2S and I am testing it with 5ppm premixed certified gas. Please advise.
Nicole Stanton
↧
↧
Forum Post: RE: Compiler 4.34 does not compile in parallel
It could be that the Makefile isn't written in a fashion that permits parallelization. For instance, the following rule cannot be parallelized:
all: cl430 a.c cl430 b.c cl430 c.c
This is just a simple example; there are other ways that the Makefile might force serialization.
↧
Forum Post: RE: View LOG_printf in CCS6
Thanks very much. You are right. For some reason, running the program wasn't executing the Log_printf statement. When I step through the program, it all works.
↧
Forum Post: RE: Error while installing CCS5.4
Actually i on working on C54x dsp family. CCS6 doesnt support C54x family so chose CCS5.
and its CCS5.4.0.00091.
↧
Forum Post: RE: LTSpice model for LM3481
Bryon,
Please follow the directions in the following post if you do not have a direct TI support contact. If you do have a direct TI support contact, please have them request the unencrypted PSpice model for you.
http://e2e.ti.com/support/development_tools/webench_design_center/f/234/t/36943.aspx
Britt
↧
↧
Forum Post: RE: CCSv6 Auto Complete gone?
Thanks Franks. Updating to a CCSv6 fixed my auto-completion problem.
↧
Forum Post: RE: CodeCoverage results cannot be retrieved using DSS Scripting
Hello Timo,
Thank you for posting such a detailed test case, especially your whole script. It was very helpful to have all that information. I was able to go through it and I think i know what the issue is:
[quote user="Timo Kauppinen"]Rowboat.prototype.activateAnalysis = function(duration){
this.scriptingEnv.traceWrite("*** activateAnalysis invoked ***");
this.debugSession.target.runAsynch();
this.scriptingEnv.traceWrite("print out analysis object to see if it's valid: "+this.analysis.getName());
this.analysis.run();
this.scriptingEnv.traceWrite("Analysis started");
};[/quote]
I see you run the target asynchronously and then you run the analysis. I would recommend running the analysis first. Otherwise by the time the analysis starts, you may have missed capturing the data you were trying to capture. Most people start the analysis right after configuring it. Give that a try and see if that helps.
Thanks
ki
↧
Forum Post: RE: Count Event Question
I don't think CCS exposes any particular breakpoint option to non-intrusively counting the number of times a particular PC is executed. The closest that I think of here is using skip count along with a HW breakpoint. Skip count can be configured by right clicking on the breakpoint and then breakpoint options. Basically, say if skip count of a HW breakpoint job is configured as 10, the CPU will halt whenever the breakpoint is hit the 11th time.
However, it is possible to realize this use-case using AETLib. Briefly, AETLib is an embedded C library, which exposes APIs for setting up AET related trace and trigger jobs from the application SW. For more details, please refer to:
http://processors.wiki.ti.com/index.php/AETLIB
http://processors.wiki.ti.com/index.php/CToolsLib
The AETLib source and examples are available at:
https://gforge.ti.com/gf/project/ctoolslib/frs/?action=FrsReleaseBrowse&frs_package_id=82
I got to modify an existing AETLib example (halt_on_watchpoint) to realize this use-case. The modified source file is attached. In this modified example, I am using AET counter 0 to count the number of times test_func2 is called.
I hope this helps.
Thanks,
Karthik.
(Please visit the site to view this file)
↧
Forum Post: RE: GUI Composer not binding to new widgets
I didn't spend too much time, but after I clean up the html file and remove all the bindings from the json file, I can bind the widget again.
The html file contains gc_1_2 in some paths, it should have gc_1_5. I don't know how that happen. Also change the data-gc-version to 1.5.201401031800. Do both of these edit outside of CCS, with CCS closed.
↧
↧
Forum Post: RE: CCSV6_ installation _errors
Steven,
We are still trying to figure out what causes this. We would like to ask if you could generate a "process monitor" log for the installer start-up. Process monitor is a Microsoft tool that logs all system activity. I'm hoping that it might provide a hint as to what the installer is having a problem with on your PC. The log file will be huge, but it will also compress very well. When I ran it locally to capture just the installer start-up, the resulting file was 130MB and compressed to 13MB.
To generate the, go here to download the tool. Run the tool and then immediately try to run the installer. As soon as the installer fails, click the capture button on the tool to halt the capture. Then, save the process monitor log to a file (save all events), zip the file, and post it here.
If you send me an email to the address in my profile, we could also arrange a time to go through this via a remote desktop session. FYI, I'm on Eastern Standard Time.
↧
Forum Post: RE: DSP lib 3.4 build error with CCSv5.5
Hi Aarti
Unfortunately it was the c:\cygwin\bin. I need that for my other work, but can remove it for builds ..... tribal knowledge :)
But now I get another error. It can't find cl6x. Shouldn't it be looking for this in my "C:\ti\C6000 Code Generation Tools 7.2.6" directory? My other projects I build in the same workspace can find it.
Cheers
Eddie
**** Build of configuration Debug for project DSPLIB_LIB_GEN ****
"C:\\ti\\ccsv5\\utils\\bin\\gmake" C6X_GEN_INSTALL_DIR=C:/ti/C6000 Code Generation Tools 7.2.6 "PATH=C:/ti/ccsv5/eclipse/jre/bin/client;C:/ti/ccsv5/eclipse/jre/bin;C:/ti/ccsv5/eclipse/jre/lib/i386;C:\\Program Files\\Common Files\\Microsoft Shared\\Windows Live;C:\\Program Files (x86)\\Common Files\\Microsoft Shared\\Windows Live;c:\\Ruby19\\bin;C:\\Program Files (x86)\\IBM\\RationalSDLC\\common;C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\Program Files (x86)\\IBM\\RationalSDLC\\ClearCase\\bin;C:\\Program Files (x86)\\IBM\\gsk8\\lib;C:\\Program Files (x86)\\IBM\\gsk8\\bin;d:\\Program Files\\MATLAB\\R2011b\\runtime\\win64;d:\\Program Files\\MATLAB\\R2011b\\bin;C:\\Program Files\\IVI Foundation\\VISA\\Win64\\Bin\\;C:\\Program Files (x86)\\IVI Foundation\\VISA\\WinNT\\Bin\\;C:\\Program Files (x86)\\IVI Foundation\\VISA\\WinNT\\TekVISA\\BIN;C:\\Program Files\\SciTools/bin/pc-win64;C:\\Program Files (x86)\\Windows Live\\Shared;D:\\Program Files\\TortoiseGit\\bin;d:\\Program Files\\doxygen\\bin;;C:\\ti\\ccsv5\\eclipse;;C:/ti/ccsv5/utils/cygwin" -k all
gmake: *** No rule to make target `Code'.
gmake: *** No rule to make target `Generation'.
gmake: *** No rule to make target `Tools'.
gmake: *** No rule to make target `7.2.6'.
C:/ti/ccsv5/utils/bin/gmake -f lib/dsplib.a64P.mk lib/dsplib.a64P
gmake[1]: Entering directory `C:/ti/dsplib_c64Px_3_4_0_0/packages/ti/dsplib'
cl64P ./src/DSP_add16//c64P/DSP_add16.c ...
if [ ! -d package/lib/lib/dspliba64P/./src/DSP_add16//c64P ]; then mkdir -p package/lib/lib/dspliba64P/./src/DSP_add16//c64P ; fi;
rm -f package/lib/lib/dspliba64P/./src/DSP_add16//c64P/DSP_add16.o64P.dep
"C:/ti/C6000/bin/"cl6x -c -mv64p -c -k -mw -o3 --symdebug:none --mem_model:data=far -Dti_targets_C64P -Dxdc_target_types__=ti/targets/std.h -eo.o64P -ea.s64P -fr=package/lib/lib/dspliba64P/./src/DSP_add16//c64P -fs=package/lib/lib/dspliba64P/./src/DSP_add16//c64P -ppa -ppd=package/lib/lib/dspliba64P/./src/DSP_add16//c64P/DSP_add16.o64P.dep -I. -Ic:/nightlybuilds/dsplib -Ic:/ti/mathlib_c66x_3_1_0_0/packages -I../.. -IC:/ti/C6000/include -fc ./src/DSP_add16//c64P/DSP_add16.c
C:/ti/C6000/bin/cl6x: not found
gmake[1]: *** [package/lib/lib/dspliba64P/./src/DSP_add16//c64P/DSP_add16.o64P] Error 127
cl64P ./src/DSP_add32//c64P/DSP_add32.c ...
if [ ! -d package/lib/lib/dspliba64P/./src/DSP_add32//c64P ]; then mkdir -p package/lib/lib/dspliba64P/./src/DSP_add32//c64P ; fi;
rm -f package/lib/lib/dspliba64P/./src/DSP_add32//c64P/DSP_add32.o64P.dep
"C:/ti/C6000/bin/"cl6x -c -mv64p -c -k -mw -o3 --symdebug:none --mem_model:data=far -Dti_targets_C64P -Dxdc_target_types__=ti/targets/std.h -eo.o64P -ea.s64P -fr=package/lib/lib/dspliba64P/./src/DSP_add32//c64P -fs=package/lib/lib/dspliba64P/./src/DSP_add32//c64P -ppa -ppd=package/lib/lib/dspliba64P/./src/DSP_add32//c64P/DSP_add32.o64P.dep -I. -Ic:/nightlybuilds/dsplib -Ic:/ti/mathlib_c66x_3_1_0_0/packages -I../.. -IC:/ti/C6000/include -fc ./src/DSP_add32//c64P/DSP_add32.c
C:/ti/C6000/bin/cl6x: not found
So I tried to do the GNU Makefile method. The instructions said I had to change the tool defines as shown below from the makefile.
# (Mandatory) Specify where various tools are installed.
# C6X_GEN_INSTALL_DIR - C6x Code gen tools install directory
export C6X_GEN_INSTALL_DIR ?= C:\ti\C6000 Code Generation Tools 7.2.6
# PATH TO MATHLIB INSTALL DIR
export MATHLIB_INSTALL_DIR ?= c:/ti/mathlib_c66x_3_1_0_0
# PATH TO DSPLIB INSTALL DIR
export DSPLIB_INSTALL_DIR ?= c:/nightlybuilds/dsplib
# ROOT Directory
export ROOTDIR := ../..
But - this is going sound really dumb - I can't find the C64x+ mathlib in the wiki. I don't see it in the mathlib download page linked from here
http://processors.wiki.ti.com/index.php?title=Software_libraries
Could you point me to it? I can only seem to find the C66x and C67x math libraries.
↧
Forum Post: RE: Migrating From CCS v3 to CCS v6
Update:
I worked with Ki offline and it looks like there is a bug in CCS with handling of *.asm files. He also promised to fix the bug in a future release.
-Tamil
↧
Forum Post: MSP430FG4618 Experimenter Board-assembly project-no symbols defined at 0x000000
Hi TI E2E community,
I'm having a very frustrating problem that I've tried searching all over these forums and google to find a solution but am having no luck.
I am using this board and cable. Using Code Composer v6.0
https://estore.ti.com/MSP-EXP430FG4618-MSP430FG4618F2013-Experimenter-Board-P1007.aspx
https://estore.ti.com/msp-fet.aspx
Here's the steps I've been following,
-Open CCS
-Create new CCS project
-Using template, create empty assembly-only project (using all default settings so far)
-Replace given code with my code
-Build project
-debug
That's when I keep getting "no symbols defined at 0x000000"/"no source available for 0x0"
The code that I'm using works perfectly at my school's lab (using CCS5.1) but refuses to work at my home PC. I'm very new to this so I don't quite know how to solve this. This code is straight from the professor's example.
.cdecls C,LIST,"msp430fg4618.h" .text .global _START START mov.w #0x300,SP StopWDT mov.w #WDTPW+WDTHOLD,&WDTCTL SetupP1 bis.b #0x04,&P2DIR Mainloop xor.b #0x04,&P2OUT mov.w #0xA000,R7 L1 dec.w R7 jnz L1 jmp Mainloop .sect ".reset" .short START .end
Please let me know if I left any vital information out. Thank you very much for your time and help.
↧
↧
Forum Post: OPA4188 Pin Names
I am trying to use the OPA4188 Spice Model and using PSpice as my simulation. The model/part doesn't have any pin names (ie. Out, Vs, -Vs..). Its labeled as 1,2,3,4,5 and without knowing the pin names its hard to run simulation and get correct result.
↧
Forum Post: RE: WEBENCH Login Issue
you'll get the answer here bro
↧
Forum Post: RE: XDS200 USB detection issue in Ubuntu in Paralles on Mac
Same issue present in Parallels 9.0.24251.1052177 and Mac OX 10.9.5. Cannot use XDS200.
↧