DSPRelated.com
Forums

CCS + c6713: sine8_LED problems

Started by tvyi...@rit.edu October 2, 2006
1. It can't find the .h files in the include folder generating error.
2. I've changed the path in the files. It finds the files, but generates
3 warning messages.
3. I load the program, depress SW 01, LED 1 goes on, yet no sound
appears.
4. I load the sine8_LED.out from the disk and it works.
5. This tells me that the CCS is not compiling properly.
6. I've done this several time, according to the text on the c6713.
7. Anyone with some advice?
> Thomas Young wrote:
>
> Here they are:
>
> --------------------------- sine8_LED.pjt - Debug ---------------------------
> [Sine8_LED.c] "C:\CCStudio_v3.1\C6000\cgtools\bin\cl6x" -g -s
> -fr"C:/CCStudio_v3.1/MyProjects/sine8_LED/Debug" -d"CHIP_6713" -mv6710
> -@"../sine8_LED/Debug.lkf" "Sine8_LED.c"
> [c6713dskinit.c] "C:\CCStudio_v3.1\C6000\cgtools\bin\cl6x" -g -s
> -fr"C:/CCStudio_v3.1/MyProjects/sine8_LED/Debug" -d"CHIP_6713" -mv6710
> -@"../sine8_LED/Debug.lkf" "c6713dskinit.c"
> [Vectors_poll.asm] "C:\CCStudio_v3.1\C6000\cgtools\bin\cl6x" -g -s
> -fr"C:/CCStudio_v3.1/MyProjects/sine8_LED/Debug" -d"CHIP_6713" -mv6710
> -@"../sine8_LED/Debug.lkf" "Vectors_poll.asm"
> [Linking...] "C:\CCStudio_v3.1\C6000\cgtools\bin\cl6x" -@"Debug.lkf"
>
> >> warning: creating output section .vecs without SECTIONS specification
> >> warning: creating .stack section with default size of 400 (hex) words.
> Use
> -stack option to change the default size.
> >> warning: Detected a near (.bss section relative) data reference to the symbol
> _DSK6713_AIC23_codecdatahandle defined in section .far. The
> reference occurs in
> C:\CCStudio_v3.1\MyProjects\sine8_LED\Debug\c6713dskinit.obj,
> section .text, SPC offset 00000058. Either make the symbol near
> data by placing it in the .bss section, or make the references to
> the symbol far. For C/C++ code use 'far' or 'near' modifiers on
> the type definition of the symbol or compile with the
> --mem_model:data switch.
> Is it a "path" problem? How can I set the search path? thanks for any help.

I doubt the .vec or stack warnings matters. For interrupt vectors, as long as they
are linking to address 0x0 then they should be Ok -- you can easily check that by
looking at the generated .map file.

However, the near/.far warning you have to resolve. Is c6713dskinit.c TI's code? It
looks to me like this code has an external C var that's being addressed as 16-bit,
but your code that creates this var treats it as .far. As this var is the handle to
an _xxx_AIC23_open() call somewhere, maybe that explains why you hear no sound, but
code appears to run and LEDs work?

-Jeff

> -----------
> From: Jeff Brower [mailto:j...@signalogic.com]
> Sent: Mon 10/2/2006 11:42 AM
> To: Thomas Young
> Cc: c...
> Subject: Re: [c6x] CCS + c6713: sine8_LED problems
>
> TV Yite-
>
> > 1. It can't find the .h files in the include folder generating error.
> > 2. I've changed the path in the files. It finds the files, but
> > generates 3 warning messages.
>
> What are the warning messages?
>
> > 3. I load the program, depress SW 01, LED 1 goes on, yet no sound
> > appears.
> > 4. I load the sine8_LED.out from the disk and it works.
> > 5. This tells me that the CCS is not compiling properly.
> > 6. I've done this several time, according to the text on the c6713.
> > 7. Anyone with some advice?
>
> Advice: solve one problem at a time. The first "unusual thing" you see,
> fix it. What's the first warning message?
>
> -Jeff
TV Yite-

> 1. It can't find the .h files in the include folder generating error.
> 2. I've changed the path in the files. It finds the files, but
> generates 3 warning messages.

What are the warning messages?

> 3. I load the program, depress SW 01, LED 1 goes on, yet no sound
> appears.
> 4. I load the sine8_LED.out from the disk and it works.
> 5. This tells me that the CCS is not compiling properly.
> 6. I've done this several time, according to the text on the c6713.
> 7. Anyone with some advice?

Advice: solve one problem at a time. The first "unusual thing" you see,
fix it. What's the first warning message?

-Jeff