Problems on the DDK uart

You need to remove the cdb file from your project and add the tcf file instead.

Hi Brad,

Ya I did do that, however when I add the tcf file, it appears to have 2 files in Generated Files, which are .s62 and .c files. When building the solution, it appears the errors as shown at the first post. I wonder why it happens.

Anyway thanks for your solution. Maybe I can give it a few tries later.

Matthew,

Are the files actually being created in the same folder as the .tcf file? Is the folder marked as "Read-Only" by chance?"

The reason Brad mentioned removing the .cdb file is that your build log shows the .cdb file instead of the .tcf file. The .s62 and _c.c files are both generated by BIOS when the .tcf is built and should be located in the same directory.

Hi Tim,

I'm not sure whether i add the .tcf file correctly or not, 'cause i add it in DSP/BIOS Config, and it happens to have the same error. Is it i have to add it into the same folder as those two files?

By the way, one of my friend asking that what if we use the .cdb file from board as a replacement? He told me that it works on compilation, but the function is not working.

----------------------------  uarttest.pjt - Debug  ----------------------------
[uarttestcfg.tcf] "C:\CCStudio_v3.3\bios_5_31_02\xdctools\tconf" -b -Dconfig.importPath="C:/CCStudio_v3.3/bios_5_31_02/packages" -v64 uarttestcfg.tcf
C:\CCStudio_v3.3\bios_5_31_02\xdctools\tconf: usage: tconf [-b] [-g[=<opts>]] [-p <dir>] [-D<name>=<value>] [-js <js options ...>] [script [args ...]]
    Options:
    -D<name>=<val>    define the symbol <name> with the string value <val>
    -g[=<opts>]    use graphical debugger to run script, and
            optionally pass <opts> to debugger
    -h        display this message
    -js        pass all subsequent options to Configuration Shell
    -p <dir>    add <dir> to tconf search path

    Configuration Shell Options:
        -f <file>    execute <file> prior to executing script
        -w        enable warning messages

    Graphical Debugger Options:
        -i    break at the first line of the startup script

[uarttest.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -eoo64 -fr"C:/CCStudio_v3.3/ddk/apps/uart/evmdm642/Debug" -i"." -i"C:/CCStudio_v3.3/ddk/apps/uart/evmdm642/../../../include" -d"CHIP_6416" -d"_UARTHW_EVMDM642_" -mv6400 -@"evmdm642/Debug.lkf" "uarttest.c"

[uarttest_params.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -eoo64 -fr"C:/CCStudio_v3.3/ddk/apps/uart/evmdm642/Debug" -i"." -i"C:/CCStudio_v3.3/ddk/apps/uart/evmdm642/../../../include" -d"CHIP_6416" -d"_UARTHW_EVMDM642_" -mv6400 -@"evmdm642/Debug.lkf" "uarttest_params.c"

[uarttestcfg.s62] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -eoo64 -fr"C:/CCStudio_v3.3/ddk/apps/uart/evmdm642/Debug" -i"." -i"C:/CCStudio_v3.3/ddk/apps/uart/evmdm642/../../../include" -d"CHIP_6416" -d"_UARTHW_EVMDM642_" -mv6400 -@"Debug.lkf" "uarttestcfg.s62"
"uarttestcfg.s62", ERROR!  : [E1000] Cannot open source file uarttestcfg.s62: No
                                     such file or directory

>> Compilation failure

[uarttestcfg_c.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -eoo64 -fr"C:/CCStudio_v3.3/ddk/apps/uart/evmdm642/Debug" -i"." -i"C:/CCStudio_v3.3/ddk/apps/uart/evmdm642/../../../include" -d"CHIP_6416" -d"_UARTHW_EVMDM642_" -mv6400 -@"Debug.lkf" "uarttestcfg_c.c"
Fatal error: could not open source file "uarttestcfg_c.c"
1 fatal error detected in the compilation of "uarttestcfg_c.c".
Compilation terminated.

>> Compilation failure

Build Complete,
  2 Errors, 0 Warnings, 0 Remarks.

Matthew said:

I'm not sure whether i add the .tcf file correctly or not, 'cause i add it in DSP/BIOS Config, and it happens to have the same error. Is it i have to add it into the same folder as those two files?

By the way, one of my friend asking that what if we use the .cdb file from board as a replacement? He told me that it works on compilation, but the function is not working.

Hi Tim,

I think I had unchecked the read only to the folders related to them, yet the problem still occured. The only thing is that I cant even found those 2 files. What actually I can do with that?

Thanks in advance.

Oh ya, there is one more file missing, the .cmd file . By the way, I found that the windows XP folder's Read only has only green-filled state. Is it possible for me to use that state to run the compilation?

The tconf step does not appear to be executing properly.  It normally doesn't spew out all the command-line options like you showed earlier.  So it seems like tconf is being invoked improperly somehow.  As a result it's not generating the files needed to build your application.

So any way for me to solve the problems? Or is there anyone did that before? I need some guides on that, thank.

I just ran a quick test.  Here's the generated output for Config1.tcf:

[Config1.tcf] "C:\ti\BIOS\bios_5_32_04\xdctools\tconf" -b -Dconfig.importPath="C:/ti/BIOS/bios_5_32_04/packages"  Config1.tcf

Comparing with your earlier output the main difference appears to be the inclusion of a "-v64".  I think that option does not belong with the tcf and is causing it to spit out the message with all the allowed options.  Go to your project options and then to the DspBiosBuilder tab.  In my project the only options ther is "-v6x" (which does not show up on the command line).  I changed to to "-v64" and I get the same message you are seeing.  So what you need to do is go to that window and change it to "-v6x".

Brad

Hi Brad,

I had solved all the problems and there has no problem on compilation.

However when i try to run the output file, there has no word sending through com port to hyperterminal, which i had set it given in the read me file. Is there anything wrong with my procedures? Mind to guide me on that. Thanks in advance.

Is there anyone can help me on such matter?Thanks in advance.

Try setting a breakpoint in the driver functions (mdBindDev, mdSubmitChan, etc.).  See which functions are getting called and what status they return.

Are you using the DM642 Video Port Mini-Driver in addition to the UART driver for the DM642 EVM? There was a problem in the VPMD which overwrites a few registers in the EVM's FPGA which essentially disables the UART. This is a simple fix, so if you are in fact using the VPMD and UART drivers I will be happy to detail the fixes in more depth.

Hi Tim,

Yes the uart driver will be using along with vpmd soon, but first I have to try to know more about the uart usage. However when I tried on the tutorial given, it cannot work, that means i may need to do some debuggings and testing on the codes or hardware. So may i know more in depth about the fix? probably i may need it in future.

thanks in advance

thanks for your suggestion brad, will try that as well

There are four hard register writes into FPGA registers that should be modified. I'll quote the code changes I made. Look for the comments with my initials.

static void configSAA7105(SAA7105_Mode videoMode, Bool slaveModeEnable,
SAA7105_AnalogFormat outMode, SAA7105_InputFormat inFormat, Bool enableBT656Sync)
{
/***************************************************************/
/* Enable master/slave mode */
/***************************************************************/
*(volatile Uint8 *)(0x90080010) |= 0x1; //reset OSD -TH
initSAA7105Def();
setVideoDisplay(videoMode, outMode, inFormat, enableBT656Sync);
enableSlaveMode(slaveModeEnable);
loadCursor(NULL);
enableColorBars(FALSE);
*(volatile Uint8 *)(0x90080010) |= 0x04; // -TH
*(volatile Uint8 *)(0x90080014) |= 0x18; // -TH
}

*(volatile Uint8 *)(0x90080010) |= 0x28; //reset OSD -TH

Brad Griffis said:

[Config1.tcf] "C:\ti\BIOS\bios_5_32_04\xdctools\tconf" -b -Dconfig.importPath="C:/ti/BIOS/bios_5_32_04/packages"  Config1.tcf