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.

C66xx questions

I have a customer in Turkey asking the following questions.

·         Some functions are available in both support library and SYS/Bios, and they are wondering which ones to use

·         They need Boot sequence on C66x user guide

·         They want to know which boot to use (NOR, NAND)

·         Can they program the NOR Flash using JTAG?

·         Are there any memory limitations for flashing their program into the device (code limitation?)

·         They want to understand how to interface the C66x with the audio codec for the data bus? They will use I2C for control bus

·         They are asking for the FPGA code of the EVM, would it be possible to give them this code?

·         What about the power connector for XDS560 available on the EVM? It seems that there is a power connector for the XDS560 available on the EVM schematics. And they would like to understand if they should use it or not while using their own XDS560 emulator.

 

  • Nine questions. I hope I do not inhibit some answers by offering some answers.

    Hector Rivera said:
    Some functions are available in both support library and SYS/Bios, and they are wondering which ones to use

    "support library" = run-time support library or chip support library or board support library or platform support library? The answer may depend mostly on which functions are being considered.

    Hector Rivera said:
    They need Boot sequence on C66x user guide
    They want to know which boot to use (NOR, NAND)

    Have you supplied them with the C66x DSP Bootloader User Guide SPRUGY5? Each C66x device may have a different set of boot options. You will need to be specific to determine which boot modes are available.

    Hector Rivera said:
    Can they program the NOR Flash using JTAG?

    Yes. When TI will supply or if TI will supply this application, I do not know.

    I will leave the other questions for better experts than I.

    Regards,
    RandyP

  • Randy P,

    THank you

  • HI Hector,

    Here are some of the answers

    ·         They want to know which boot to use (NOR, NAND)

    <AVM> Only NOR boot is supported.

    ·         Are there any memory limitations for flashing their program into the device (code limitation?)

    <AVM> The size of the NOR flash determines the code limitation.


    I will refer the other questions to an expert.

     

    Thanks,

    Arun.

  • Here is the answers for the remaining questions.

     

     

    They want to understand how to interface the C66x with the audio codec for the data bus? They will use I2C for control bus

     

    [TI]  The C66x DSPs do not have a dedicated interface for Audio CODEC connectivity.  They do have multiple programmable interfaces that can be used with Audio CODECs.  The C6678 contains TSIP interfaces which are simple synchronous time slot interfaces for data octets.  The SPI interface is another possibility on C66x devices.

     

    ·         They are asking for the FPGA code of the EVM, would it be possible to give them this code?

     

    [TI]  The EVM FPGA design is still changing.  When the design stabilizes, the FPGA code will be available.  This is still a few weeks out.  This FPGA implementation is basically glue logic, power sequence control and a programming interface for the programmable clock generators.

     

    ·         What about the power connector for XDS560 available on the EVM? It seems that there is a power connector for the XDS560 available on the EVM schematics. And they would like to understand if they should use it or not while using their own XDS560 emulator.

     

    [TI]  The power connector on the EVM for is for an XDS560v2 mezzanine board.  EVMs can be ordered with this mezzanine board mounted.  They will begin shipping late 2Q11.  This power connector is not needed  and not used when an external emulator pod is used.

     

    Thanks,

    Arun.