• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 977 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320C6747: TMS320C6747 Hardware Design

Cristian Tanase
Prodigy 160 points
Part Number: TMS320C6747
Other Parts Discussed in Thread: DA8XX, TLV320AIC3106, SYSBIOS

Hi Everibody,

Does have anyone experience in using TMS320C6747  DSP with only the internal memory?

I need to run a simple FFT function so it does not make any  sense for me to tie SDRAM externally to reduce cost and space.

Appreciate the answer,

Cristian


  • 0
    TI__Guru** 114410 points
    Cristian,

    We have several audio customers who have gone into production with no SDRAM on this part as well as DA8xx (audio derivative devices) so if the intent of the question is to verify that this design is supported then the answer is yes.

    If you have more questions regarding how the software or hardware needs to be configured. Please post the questions here and we can provide required guidance.

    Regards,
    Rahul
  • 0 in reply to Rahul Prabhu
    Prodigy 160 points
    Hi Rahul,

    Thank you for the answer.

    There are also a few questions regading the design and the planning of this project.

    It is quite challenging to fit a serial FLASH to the device. What I have found on the web is a Winbound serial FLASH memory ( W25X32) that is obsolete now. Any suggestions?

    Also, the only development board for this device is the one for OMAP L137 . This is using a driver for the CODEC TLV320AIC3106. By using only the DSP variant TMS320C6747( my device) the software driver could be further used with this device? Is there any direct software compatibility between this two parts ( L137 & TMS320C6747) ?


    Thank you,
    Cristian
  • 0 in reply to Cristian Tanase
    TI__Guru** 114410 points
    Yes, OMAPL137 and C6747 are pin to pin and software compatible. These devices were created to provide scalability to users who may want to add a low power host to the device. Both devices are DSP boot master as in the DSP is the master core on the chip and always boots first.

    The AIC codec on these parts are configured using I2C interface and that is accessible to both the ARM and the DSP so there is no modification to the driver when you are using low level driver or register level configurations.

    There are several SPI parts that can be used with this device. From other designs that I have seen on e2e, the following part has worked with C674x devices
    S25FL064K0SMFI011 (Spansion)

    I will check internally and provide more recommendations.

    For hardware design refer to the following wikis:
    processors.wiki.ti.com/.../OMAP-L137_Hardware_Design_Guide
    processors.wiki.ti.com/.../_AM1x_Schematic_Review_Checklist
    processors.wiki.ti.com/.../OMAP-L137_Complementary_Products

    Regards,
    Rahul
  • 0 in reply to Rahul Prabhu
    TI__Guru** 114410 points

    Here are some other recommendation from previous designs that we have supported with these parts:

    8Mbit:

    Winbond W25Q80BVSSIG

    Macronix MX25L8035EM2I-10G

    16 Mbit:

    MX25L1606EM21-12G

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Prodigy 160 points
    Rahul,

    Thanks again for the fast answers.

    Do you have any data about the life expectancy of the product?

    Cristian
  • 0 in reply to Cristian Tanase
    TI__Guru** 114410 points
    The life expectancy depends on temperature and speeds at which the device is running. Please refer to the Power On Hours section (5.4) of the device datasheet :
    www.ti.com/.../tms320c6747.pdf

    Regards,
    Rahul
  • 0 in reply to Rahul Prabhu
    Prodigy 160 points

    Hi Rahul,

    In the end we decided to go ahead with the C6747 DSP.

    I would like to know the following:

    1. There are some code examples for the start like : UART & SPI code?

    2. How can I run the DSP Library for C6747?   After installing the CCS  there is any example of using the DSP Library ( for eg,  compileing a FIR and an FFT ).

    3. Considering the fact that we are not going to use external memory, there is anything that should set to the compiler?  

    Thank you,

    cristian

  • 0 in reply to Cristian Tanase
    TI__Guru** 114410 points
    Cristian,

    This is a relatively mature device in our family and is mostly used home audio and performance audio kind of applications. However for use cases outside of that application space we didn`t have a unified SDK offering. We plan to change that by adding this device support to Processor SDK RTOS software in 2Q17 time frame. If possible our recommendation would be to use this updated release for a better and integrated user experience with latest tools and RTOS software.

    However if the project needs to start right a way, there are several packages that we have supported on this device over the years that I am listing here for your reference:

    Peripheral driver examples using DSPBIOS or SYSBIOS:
    software-dl.ti.com/.../index.html
    (Please read release notes for supported features and dependencies)

    No-OS bare-metal register CSL code examples:
    processors.wiki.ti.com/.../QuickStartOMAPL1x_rCSL

    Board BSL library for C6747:
    support.spectrumdigital.com/.../

    For DSPLIB, we do provide examples in the DSPLIB for C674x that you can use as starting point for FFT and FIR:
    http://www.ti.com/tool/SPRC265
    Examples are provided under dsplib_c674x_x_X_x_X\packages\ti\src\<function name>

    when you are creating an application without external memory, the linker command file that you define must not define DDR memory and should place all the code and data sections in on chip RAM or internal memory. With RTOS, you will need to create a custom platform without DDR section or in the configuration file place all code/data to non- SD RAM memory on the device.

    the compiler generates a map file at the end of a compile when -map option is specified which you can see to ensure no code/memory section is placed in external memory.


    Regards,
    Rahul

    PS: Once you get started, if you have questions, please feel free to post them on E2E so that we can provide the required guidance