• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 98 subscribers
  • Views 922 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.

DSK6416 newer Target Content available online?

fabb
Prodigy 40 points
Other Parts Discussed in Thread: CCSTUDIO

Hello there,

I'm a student of Computer Engineering at the University of Technology in Vienna, Austria. I'm taking my first steps with DSPs with a Spectrum Digital DSK6416.

The DSK6416 is from 2006, it came with CCS3.1 and DSP/BIOS 4. I ported the Dsp_App Example (that came with the board and uses EDMA with ping-pong buffers) to CCS4 with DSP/BIOS5 which worked finally. I have some questions to the recentlyness of the used Target Content:

TI seems to sell the DSK6416 now (http://focus.ti.com/docs/toolsw/folders/print/tmdsdsk6416.html) which also comes with CCS4. The website says that "Target board specific Code Composer Studio development tools" is included. Is this newer Target Content also available for download?

Speaking of Target Content, I noticed that the one provided on the CD that came with the board is even newer than the one available at http://c6000.spectrumdigital.com/dsk6416/ (especially the BSL has some minor differences). Am I missing something about that?

I also found a (not substantially) newer CSL at http://focus.ti.com/docs/toolsw/folders/print/sprc090.html. Is this really the newest available CSL for the C6416? (It does work, but using a lib_3x library irritates me a little bit)

I tried out using the DDK for EDMA McBsp access of the AIC23 (the TSK example worked nearly, but there seems some audible memory inference of RTDX vs EDMA happening - I guess I'll start a new thread for this when I find out more). I found the two DDK sites http://focus.ti.com/docs/toolsw/folders/print/sprc118.html and http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/ddk/index.html. It's a bit confusing to having two sites with different versions and no links to each other. Is the DDK 1.20 provided on the second site really the newest one?

Is there any preferred alternative over using CSL+BSL or CSL+DDK(+BSL)? (apart from using Matlab which won't be possible with CCS4 until Matlab2010a as far as I have understood from http://e2e.ti.com/support/microcontrollers/tms320c2000_32-bit_real-time_mcus/f/171/p/31145/109108.aspx)

Also, I ported the Dsk_App Example further to DSP/BIOS6 which also worked finally. But: while the version in CCS3.1+DSP/BIOS4 and CCS4+DSP/BIOS5 ran with about 5-10% CPU load, CCS4+DSP/BIOS6 used 95% CPU (!). If there's a known problem you can point me to without the necessity of posting the code, I'd be thankful. Otherwise I guess a new thread would be a better place for this.

Thanks for your answers!

Fabian

  • 0
    TI__Mastermind 18130 points

    fabb said:
    TI seems to sell the DSK6416 now (http://focus.ti.com/docs/toolsw/folders/print/tmdsdsk6416.html) which also comes with CCS4. The website says that "Target board specific Code Composer Studio development tools" is included. Is this newer Target Content also available for download?

    To my knowledge these kits are still shipping with CCSv3.1, but I will need to verify. I have not seen any updates from Spectrum for updated Target Content, but I have updated a few to CCSv4 in the past without too many issues.

    fabb said:
    Speaking of Target Content, I noticed that the one provided on the CD that came with the board is even newer than the one available at http://c6000.spectrumdigital.com/dsk6416/ (especially the BSL has some minor differences). Am I missing something about that?
    I am not sure about this. You'd need to ask Spectrum about the differences - I don't even have a recent CD to check myself. Sorry!

    fabb said:
    I also found a (not substantially) newer CSL at http://focus.ti.com/docs/toolsw/folders/print/sprc090.html. Is this really the newest available CSL for the C6416? (It does work, but using a lib_3x library irritates me a little bit)
    Yes, this is the newest functional CSL supporting these "legacy" devices. CSL3.x was developed for C672x and C6455, but all devices after this switched over to the PSP driver model.

    fabb said:
    I tried out using the DDK for EDMA McBsp access of the AIC23 (the TSK example worked nearly, but there seems some audible memory inference of RTDX vs EDMA happening - I guess I'll start a new thread for this when I find out more). I found the two DDK sites http://focus.ti.com/docs/toolsw/folders/print/sprc118.html and http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/ddk/index.html. It's a bit confusing to having two sites with different versions and no links to each other. Is the DDK 1.20 provided on the second site really the newest one?
    Yes, I believe the DDK v1.20 was the last version created.

    fabb said:
    Is there any preferred alternative over using CSL+BSL or CSL+DDK(+BSL)? (apart from using Matlab which won't be possible with CCS4 until Matlab2010a as far as I have understood from http://e2e.ti.com/support/microcontrollers/tms320c2000_32-bit_real-time_mcus/f/171/p/31145/109108.aspx)
    Well, the preferred method of development is whatever you are most comfortable with, but the CSL(+DDK+BSL) is the most common method for this board. Keep in mind that the BSL will not be of as much use with a custom board, but for working with the DSK it certainly comes in handy.

    fabb said:
    Also, I ported the Dsk_App Example further to DSP/BIOS6 which also worked finally. But: while the version in CCS3.1+DSP/BIOS4 and CCS4+DSP/BIOS5 ran with about 5-10% CPU load, CCS4+DSP/BIOS6 used 95% CPU (!). If there's a known problem you can point me to without the necessity of posting the code, I'd be thankful. Otherwise I guess a new thread would be a better place for this.
    I have not ported this example to BIOS6, but 95% CPU load for the dsk_app example certainly seems too high. If I get some time today I will try this out.

  • 0 in reply to TimHarron
    Prodigy 40 points

    Thanks for your fast and informative answers Tim!

    TimHarron said:
    TI seems to sell the DSK6416 now (http://focus.ti.com/docs/toolsw/folders/print/tmdsdsk6416.html) which also comes with CCS4. The website says that "Target board specific Code Composer Studio development tools" is included. Is this newer Target Content also available for download?

    To my knowledge these kits are still shipping with CCSv3.3, but I will need to verify. I have not seen any updates from Spectrum for updated Target Content, but I have updated a few to CCSv4 in the past without too many issues.[/quote]

    On the site http://focus.ti.com/docs/toolsw/folders/print/tmdsdsk6416.html#What%27s%20Included it says that "CCSTUDIO,Code Composer Studio (CCStudio) Integrated Development Environment (IDE) - v4.x" is included.

    TimHarron said:
    Speaking of Target Content, I noticed that the one provided on the CD that came with the board is even newer than the one available at http://c6000.spectrumdigital.com/dsk6416/ (especially the BSL has some minor differences). Am I missing something about that?

    I am not sure about this. You'd need to ask Spectrum about the differences - I don't even have a recent CD to check myself. Sorry![/quote]

    Ok, so you at TI sell the board now but you don't provide the Windows Driver / DSK Diagnostic Tool / BSL etc? I now also sent a ticket to Spectrum Digital asking them for recent online content.

    TimHarron said:
    I also found a (not substantially) newer CSL at http://focus.ti.com/docs/toolsw/folders/print/sprc090.html. Is this really the newest available CSL for the C6416? (It does work, but using a lib_3x library irritates me a little bit)
    Yes, this is the newest functional CSL supporting these "legacy" devices. CSL3.x was developed for C672x and C6455, but all devices after this switched over to the PSP driver model.

    fabb said:
    I tried out using the DDK for EDMA McBsp access of the AIC23 (the TSK example worked nearly, but there seems some audible memory inference of RTDX vs EDMA happening - I guess I'll start a new thread for this when I find out more). I found the two DDK sites http://focus.ti.com/docs/toolsw/folders/print/sprc118.html and http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/ddk/index.html. It's a bit confusing to having two sites with different versions and no links to each other. Is the DDK 1.20 provided on the second site really the newest one?
    Yes, I believe the DDK v1.20 was the last version created.

    fabb said:
    Is there any preferred alternative over using CSL+BSL or CSL+DDK(+BSL)? (apart from using Matlab which won't be possible with CCS4 until Matlab2010a as far as I have understood from http://e2e.ti.com/support/microcontrollers/tms320c2000_32-bit_real-time_mcus/f/171/p/31145/109108.aspx)
    Well, the preferred method of development is whatever you are most comfortable with, but the CSL(+DDK+BSL) is the most common method for this board. Keep in mind that the BSL will not be of as much use with a custom board, but for working with the DSK it certainly comes in handy. [/quote]

    Ok, thanks. So PSP is the new way to go, but with that old board I'm stuck with legacy CSL and DDK.

    TimHarron said:
    Also, I ported the Dsk_App Example further to DSP/BIOS6 which also worked finally. But: while the version in CCS3.1+DSP/BIOS4 and CCS4+DSP/BIOS5 ran with about 5-10% CPU load, CCS4+DSP/BIOS6 used 95% CPU (!). If there's a known problem you can point me to without the necessity of posting the code, I'd be thankful. Otherwise I guess a new thread would be a better place for this.

    I have not ported this example to BIOS6, but 95% CPU load for the dsk_app example certainly seems too high. If I get some time today I will try this out.[/quote]

    It's also strange as recompiling the DSP/BIOS6 configuration takes ages (about 15x than recompiling the version with DSP/BIOS6) and the .out file has 6.5x the size (1.41MB instead of 180KB).

    I can prepare a ported version for you, is there a way I can upload it here?

    Thanks,

    Fabian

  • 0 in reply to TimHarron
    TI__Mastermind 18130 points

    TimHarron said:
    To my knowledge these kits are still shipping with CCSv3.1, but I will need to verify.

    This is correct. I have requested that the DSK6416/6713 product folders be updated to reflect that they are not shipping with CCSv4; however, keep in mind that you should be able to port them into CCSv4 fairly easily. If you attempt this path let us know.

    *edit* Updated my quote as this answer was verified as correct. The DSK ships with v3.1, not v3.3.

  • 0 in reply to fabb
    TI__Mastermind 18130 points

    fabb said:
    I can prepare a ported version for you, is there a way I can upload it here?

    Yes, up towards the top you can click on "Options" and add a zip attachment in there.

  • 0 in reply to TimHarron
    Prodigy 40 points

    Ok, I stripped my expanded version of the Dsk_App Example (removed the ringbuffer and processing stuff). Attached you will find a CCS4 workspace with both a DSP/BIOS 5 and 6 version of the project, they contain (nearly) the same code (I #ifdef'd the differences needed between DSP/BIOS 4, 5 and 6). I also included the compiled stuff so you can alternatively directly load the .out files. You will need the BSL for building.

    Over here, this DSP/BIOS5 version needs only 1% CPU and when switch 1 (the second) is depressed (which simulates an extra load) there's a total load of 15%. The .out file has 168KB.

    The DSP/BIOS6 version needs (without the load simulator) 28% CPU and when you press switch 1 you will only hear the last buffer repeated as the CPU load exceeds 100%. The .out file has 1,14MB.

    I built the DSP/BIOS6 configuration upon the "Full BIOS with Rta Configuration" Template.

    Just a random thought: maybe DSP/BIOS6 somehow uses floating point operations?

    dsp_bios_5vs6.zip
  • 0 in reply to fabb
    TI__Mastermind 20805 points

    DSP/BIOS 6.20.0x support for the 6416 is missing support for the Cache.  This might explain your problem.  You might be able to enable the cache with code of your own to get beyond this, but there may be other issues.

    Since most 641x users and evm kits have CCSv3 and BIOS 4.90 or 5.x, the 641x support was removed starting with DSP/BIOS 6.21.   DSP/BIOS 6.21 supports 64x+ and 674x devices (as well as others as specified in the release notes).

    Unfortunately, your only options are to stay with DSP/BIOS 4/5 or use one of the devices supported by DSP/BIOS 6.21.

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/index.html

  • 0 in reply to TimHarron
    Prodigy 40 points

    TimHarron said:

    To my knowledge these kits are still shipping with CCSv3.3, but I will need to verify.

    This is correct. I have requested that the DSK6416/6713 product folders be updated to reflect that they are not shipping with CCSv4; however, keep in mind that you should be able to port them into CCSv4 fairly easily. If you attempt this path let us know.

    [/quote]

    Spectrum Digital says that the DSK ships with CCS3.1 and not CCS3.3:

    The most rescent release of the C6416T CCS DSK Tools and BSL can be found on the latest CD Rom.  The current release of tools is CCS 3.1, not CCS 3.3.  TI never updated the DSK Tools release to CCS 3.3.

    Your CD has the latest content.  The Target Content is created with the latest version of C6000 CCS DSK Tools version 3.1.  There is not a more recent release based on CCS 3.3 or CCS v4.  If you are using CCS 3.3, then you may have to rebuild the BSL source under the new CCS Tools and versioning.

  • 0 in reply to fabb
    TI__Mastermind 18130 points

    Thanks for clearing that up Karl.

    fabb said:
    Spectrum Digital says that the DSK ships with CCS3.1 and not CCS3.3:
    Looks like my knowledge was incorrect. I apologize for the confusion here. At this point it seems like most/all of your concerns have been addressed, even if not the way you would have hoped, but to get this discussion back on track do you still have any lingering questions or concerns?