compiling for C6713

Hi John,

have you double checked permissions?  Have you seen this wiki and made sure all include paths and variables are included as directed?  Including the file search path under the linker options?

http://processors.wiki.ti.com/index.php/Include_paths_and_options

Please keep us informed.

Best Regards,
LIsa

Hi Lisa,

Thank you for your response. I was not aware of that wiki page. Thank you for bringing it to my attention.

After reading the wiki, I still believe I am correctly configuring the include path for the compiler. Do you see anything wrong in the include paths above? I do not believe I am having problems with the linker. I interpreted your suggestion to read the part about the linker to mean I am struggling with linking.

I started another fresh project to test my process. I used the File->New Project wizard, with the settings visible below:

Do these settings look correct for the TI C6713?

I now have a new problem. I am able to point the new project to the include path (as shown in my 1st post) and the header files seem to be found successfully. However, those header files are exhibiting a compile error. With a simpler source file, shown here:

... the compile error is:

Why would this error occur?

Many thanks for any help.

Sincerely,
John

*edit*
I searched the forums for "#error NO CHIP DEFINED" and people suggested manually defining the preprocessor symbol, CHIP_6713. I did this, as shown below and the compile error is resolved. Is this a valid solution?

I have now read through the entire thread cited in my original post. It explains my issues above.

After following the instructions by Darrell, I am seeing some problems. I have to say "thanks" and also "wow" for Darrell's contribution. I never would have figured this out without Darrell's guidance. I made screenshots along the way.

When I build the project, I see a warning. When I hit debug, I see a run time error.

Here is the warning:

'Building target: Chassaing_Sine8_LED.out'
'Invoking: C6000 Linker'
"C:/ti/ccsv5/tools/compiler/c6000_7.3.4/bin/cl6x" -mv6700 -g --define=CHIP_6713 --display_error_number --diag_warning=225 --mem_model:data=far --abi=coffabi -z -m"Chassaing_Sine8_LED.map" --warn_sections --display_error_number -i"C:/ti/ccsv5/tools/compiler/c6000_7.3.4/lib" -i"C:/ti/ccsv5/tools/compiler/c6000_7.3.4/include" --reread_libs --rom_model -o "Chassaing_Sine8_LED.out"  "./c6713dskinit.obj" "./Vectors_poll.obj" "./Sine8_LED.obj" -l"rts6700.lib" "../C6713dsk.cmd" "../csl6713.lib" "../dsk6713bsl.lib"
<Linking>
warning #10247-D: creating output section ".vecs" without a SECTIONS
   specification
warning #10210-D: creating ".stack" section with default size of 0x400; use the
   -stack option to change the default size
'Finished building target: Chassaing_Sine8_LED.out'

Here is the run time error:

For what it is worth, I tested the drivers. I was not sure about Darrell's step,

"In this folder, right mouse click (RMC) on c6713dsk.exe, and "troubleshoot compatibility.  Get it running as an XP program.  It should be persistent, so you only have to do it once."

For that step, I walked through the Windows troubleshooting wizard and everything seemed to line up with what Darrell states. I assume it worked. I have no idea how to know if all is well.

For the next step with the diagnostic tool, I believe it is working. Here is my evidence:

Thanks for any help resolving this final run-time problem.

Sincerely,
John

Hi John,

glad to hear to are a step further.  Regarding the error with the emulator.  How have you configured your emulator/traget configuration file(.ccxml)?  If you run a different example or project do you still get this error or do they connect and load/run/debug without problems?

Best Regards,
Lisa

Hi Lisa,

Thanks for keeping me on track.

I was previously able to run a simple 'hello world' application, but that does not appear to be working anymore. Maybe my drivers have a problem now?

Here are the settings I used for the CCXML, per the instructions in Darrell's thread.

Hi John,

there doesn't seem to be anything that looks suspicious.   Have you tried the spectrum digital software to test the connection?  What result do you get?  Did anything change with the hardware?  Jumpers, power, etc?  Another possibly silly thing to check is USB port.  I have had experience on a computer where an emulator seemed to only work from certain of the USB ports.   Do you see anything problematic in your device manager?

Best Regards,
Lisa

The diagnostic tool from Spectrum Digital says it fails connect to the device while CCS or the diagnostic tool is running. I shut down CCS to be sure. Under Windows Task Manager - Processes, I looked for a process to terminate, but saw no obvious named processes.

This is frustrating. I left the board plugged into my PC overnight because I did not want anything to change. So, I know the USB port is the same. I wonder if the steps for the driver in Darrell's instructions changed my ability to use the diagnostic tool. Also, when I shutdown CCS at the end of the day yesterday, CCS emitted an error message, but I do not remember what it said.

Now a different behavior is noticeable.

1. I tried unplugging the USB cable from the PC's port and disconnected the power supply. I reconnected the the power supply, then reconnected the USB cable to the PC.
2. Now the demo used in Darrell's thread works!? There is no error message and the 'BUSY' LED shows program control, blinking once in a while.
3. I ran the diagnostic tool again, and it still says FAIL due to CCS or the diagnostic tool being in use.
4. I ran the demo program from Darrell's thread again, and it continues to run fine. Other source code examples build and execute without a run time error.
5. I rebooted my PC and nothing worked, program or diagnostics tool.
6. I unplugged the USB from the PC and reconnected. This puts me back to the demo program working, but I cannot get the diagnostic tool to work since yesterday.

Is there a problem with the Diagnostic tool now? I'm really confused.

Hi John,

if it is only the diagnostic tool that is failing now, I would not be too concerned.  Can you use CCCS fine now?

Best Regards,
Lisa

OK, I will not worry about the diagnostic tool.

I believe I am close, but I'm not sure how to confirm that I am really connected to the hardware or if my debug session is using an emulator. At least I can compile and run the debugger. However, I suspect I am not able to interact with the hardware. How can I tell?

Thanks.

OK, I am running now. I'm a little embarrassed to say that some of my problem came from the fact that I could not recognize a DIP switch from this other thing on the board (which happens to switch on/off). The Sine8 demo from the Chassaing book allows me to control the state of an LED by pressing the "DIP switch".

This support item can be closed !

Hi John,

thanks for the update and very glad to hear you are up and running.  

All the best with development.

Best Regards,
Lisa