• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 1053 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

C6713 standlone

Amir Shafiq
Intellectual 450 points

Other Parts Discussed in Thread: TMS320C6713B

I am using tms320c6713. I have development my code on it. now

1: i want to run the code stand alone. i.e i dont want to use ccs with it. whenever i should reset dsk. it automatically load program into memory and run. How can i do that ? please help

2. In standalone mode , i want to send "digital data" from dsk to pc or Visual c or visual basic program. Which interface i can use with it. any examples would be helpful

3. in RTDX mode with PC/Matlab; is there any limit on data size that we can use? because my program was running fine when i was transferring  256 point. but when i used 1024 points ,it wasn't working

4. Any reference of good study material for DSP/Bios that should discuss how to make and configure cdb files will also be appreciated

 

Thanks and best Regards

M Amir Shafiq

 

  • 0
    TI__Guru* 84110 points

    Start with the TI Embedded Processors Wiki pages. Here you can click on major topics from the first page to manually search for topics of interest, or you can use either the Google-based or Wiki-based searches from the home page to find helpful information. For example, when I did a Google-based search for "c6713", the first topic it found was Flashing the C6713 EVM which sounds pretty close to your first question.

    The next great resource is the Product Folder on www.ti.com. In the upper-right corner, do a search by part number for TMS320C6713B, or click the auto-link for the part number on this sentence. Click on Technical Documents and look through the list of App Notes and User's Guides. At the end of the list of User's Guides, click on "View User Guides for TMS320C67x DSP" to get a longer listing - then search for DSP/BIOS to find API and User's Guides for DSP/BIOS.

    Amir Shafiq said:
    In standalone mode , i want to send "digital data" from dsk to pc or Visual c or visual basic program.

    You will have to look at the various interface connectors available on your board. If you are using the C6713 DSK, then the choices for data communication are either RTDX through the emulation interface or some communication method using the expansion connectors. Refer to the DSK documentation on online support for RTDX communication, although you already know how to do that.

    If you need a different communication path than RTDX, then the easiest is probably a UART through an expansion port daughtercard from one of our Third Party vendors. Not to recommend one over another, the one daughtercard vendor that I know without searching is Link Research, who has a line of DSK-compatible daughtercards. Other vendors are also available if you want to search for them.

  • 0 in reply to RandyP
    TI__Guru*** 125430 points

    Be sure to check out the App Note Creating a Secondary Bootloader for Flash Bootloading on C6000 and the corresponding examples.  For the actual writing of flash you might try the Flashburn utility from Software Design Solutions.

  • 0 in reply to RandyP
    Intellectual 450 points

    Dear TI

    i have some problems creating hex file using hex6x.

    i am using tms320c6713 dsk kit and ccs3.3

    when i use this command on cmd

     

    >>hex6x real_fft_ahex.cmd

    i get following errors and no proper hex file is created

     

    "    Microsoft Windows XP [Version 5.1.2600]

    (C) Copyright 1985-2001 Microsoft Corp.

     

     

    C:\Documents and Settings\Amir Shafiq\Desktop\real_fft>hex

    6x real_fft_ahex.cmd

    >> WARNING: can't convert RAM-model .cinit with -image

    Translating real_fft.out to ASCII-Hex format...

       "real_fft.out"   ==> .vecs

       "real_fft.out"   ==> .vectors

       "real_fft.out"   ==> vectors

    >> WARNING: section 'vectors' at 03000h falls in unconfigured memory (skipped)

       "real_fft.out"   ==> bootload

    >> WARNING: section 'bootload' at 03400h falls in unconfigured memory (skipped)

       "real_fft.out"   ==> .text

    >> WARNING: section '.text' at 0237a0h falls in unconfigured memory (skipped)

       "real_fft.out"   ==> .const

    >> WARNING: section '.const' at 029840h falls in unconfigured memory (skipped)

       "real_fft.out"   ==> .switch

    >> WARNING: section '.switch' at 0298a0h falls in unconfigured memory (skipped)

       "real_fft.out"   ==> .cinit

    >> WARNING: section '.cinit' at 04000h falls in unconfigured memory (skipped)     "

      

    My cmd file real_fft_ahex.cmd and real_fft.cmd is also listed below.

    can u please tell me where i am making mistake

      

    "real_fft_ahex.cmd" file

     *********************************************************************

     real_fft.out

     -a

    -map real_fft.map

     -memwidth  8

     -image

     ROMS

    {

        FLASH: org = 000h, len = 0x3000,romwidth = 8, files = {real_fft.hex}

    }

     *********************************************************************

     

     

    also "real_fft.cmd" file is given below

     *********************************************************************

    -q

    -cr

    -m real_fft.map

    -o real_fft.out

    /*-stack 0x2000*/

    -x

    /* Memory for TMS320C6713 */

    MEMORY   {

     

    FLASH:         o = 00000000h   l = 00003000h

    vecs:          o = 00003000h   l = 00000200h

    boot:          o = 00003400h   l = 00000200h

    IDRAM:         o = 00004000h   l = 00400000h

     

    //FLASH:              org=0x90000000, len=0x00020000 /*flash memory*/  

     

    }

     

    SECTIONS {

                                    "vectors"       > vecs

                                    "bootload"      > boot

                                    .EXTRAM      {} > IDRAM 

                                    .switch      {} > IDRAM  

               .text:       {} > IDRAM

               .const:      {} > IDRAM

               .cinit:      {} > IDRAM

               .bss:        {} > IDRAM

               .sysmem:     {} > IDRAM

               .cio:        {} > IDRAM

               .far:        {} > IDRAM

               .stack:      {} > IDRAM }

     

     

  • 0 in reply to Amir Shafiq
    Intellectual 450 points

    Also please comment on point 3 mentioned above in my question. i.e

     

    3. in RTDX mode with PC/Matlab; is there any limit on data size that we can use? because my program was running fine when i

    was transferring  256 point. but when i used 1024 points ,it wasn't working

     

  • 0 in reply to Amir Shafiq
    TI__Guru* 84110 points

    Amir Shafiq said:

    3. in RTDX mode with PC/Matlab; is there any limit on data size that we can use? because my program was running fine when i

    was transferring  256 point. but when i used 1024 points ,it wasn't working

    There is no reason for there to be any data size limitation for any communication mechanism. There may be fixed-size buffers that you have created or that are created in the DSP/BIOS configuration, and these might limit the amount of data that can be transferred before the buffer is emptied. Try sending your data in smaller packets or increase the size of the RTDX buffer in the DSP/BIOS configuration.

    Amir Shafiq said:
    >> WARNING: can't convert RAM-model .cinit with -image

    The warning messages are intended to show you have a problem in your file-conversion process. This one is telling you that the RAM-model is not compatible with building a ROM hex file. Use the ROM-model for your auto-initialization since you want to build a ROM/FLASH version of your program. The means using the -c option instead of the -cr option.

    Amir Shafiq said:
    >> WARNING: section 'vectors' at 03000h falls in unconfigured memory (skipped)

    Why do you have three vectors-related sections? You have .vecs, .vectors, and vectors, which probably means something is not the way you intended it to be. In any case, this last one, "vectors", is being placed at 03000h but your ROMS directive in the hex6x .cmd file has only configured 03000h of memory space.

    Amir Shafiq said:
    >> WARNING: section '.text' at 0237a0h falls in unconfigured memory (skipped)

    .text is also being placed outside your configured FLASH space. You need to understand more of what the hex6x program is doing and how it uses your .out file as input to hex6x. This information is in the C6000 Assembly Language Tools User's Guide.

    You will want to consider the LOAD and RUN commands in your application .cmd file. And you will want to compare the section sizes between the two .map files. The two map files should be given different names so they do not overwrite each other.