• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 327 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.

DSPBios + Integra getiing started

serdar
Intellectual 390 points
Other Parts Discussed in Thread: OMAP-L138, SYSBIOS, TMS320C6748

Hi All,

I don't experience with DSPBios and I have a few getting started questions.

We will use OMAP-L138 on our design and there are DSP / Bios and ARM / Linux tasks. I have classified all of them. I have experience with Linux but nothing with DSP/Bios.

I have been trying to decide the way of code development on DSP, environment. I have L138 and C6748 SOM.

- Do you think using C6748 SOM is the better way to learn Bios and develop something before jumping L138?

- I know that one can develop code and run with Linux host and DVSDK tools or CCS and Emulator (XDS100 or XDS510) connects directly to DSP with Windows host. Which way is efficient? How can I debug with Linux host without emulator? I believe emulator is advantage and only works with CCS.

- What limitations will I face if i use L138 (hard or soft)?

- SysBios is new and people are still using DSP Bios. Which version of DSP Bios / SYS Bios you are recommending?

 

Thanks in advance

Serdar

  • 0
    TI__Expert 6860 points

    The 4.x DVSDK for the OMAP-L138 device is a good starting point.  It's shipped as part of the newer EVM kits.  You can also download that latest version at:

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

    On the DSP-side the DVSDK uses and provides DSP/BIOS 5.x (not SysBios 6.x) and additional DSP-side drivers.  Using SysBios is an option but be aware that certain piece such as DSPLink (SysLInk if using SysBios) for inter-processor communication (between ARM + DSP) or MFP (Multimedia Framework Components aka Codec Engine) isn't currently available for this device.

    To get familiar with DSP/BIOS, I'd recommend starting with the C6748 and begin your development/debugging for the DSP using CCS and an emulator.

    The DVSDK kit only contains the necessary subset of the components to support the OMAP-L138 but more are available for the C6748 device.  You can find a more complete  list of available packages/component on the C6748 product page and follow the link to "Development Software for TMS320C6748, C6746, C6742 Processors" in the Software and Development Tools section.

    http://focus.ti.com/docs/prod/folders/print/tms320c6748.html

    You can also find the certain components (SysBios, Network Development Kit) are being support on the the OMAP-L138/C6748 that are not referenced in the above link but can be found at:

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

  • 0 in reply to Arnie Reynoso
    Intellectual 390 points

    Arnie,

    Thanks, your answer are useful for me. But I have two more questions.

    - We have some tasks in current project that we probably use in different projects with C2000 or Cortex-M. So SYS BIOS looks good. But latest DVSDK includes DSP Link not SYS Link. I think I should start with DSP BIOS. What is your comment about migrating DSP BIOS to SYS BIOS or C6000 to C2000 or etc?

    - I used XDS100 with Cortex-M3 and it was  so slow. Is XDS100 enough for professional use? I think all of DSP BIOS debugging components are running over emulator.

     

    Serdar