• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 100 subscribers
  • Views 667 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.

Programming the DSP

Bendous
Intellectual 340 points
Other Parts Discussed in Thread: OMAP-L137

Can anyone please answer this question:

 

I am designing a PCB using the C6747. I understand the DSP is programmed through the JTAG. Is there any other way to program the DSP? e.g. things like SPI, UART, ... etc.

 

Any help or suggestions are most welcome.

  • 0
    TI__Mastermind 24340 points

    Hi Bendous,

    In development phase, I strongly advise to have Jtag in your board. Without Jtag you might not be able to debug your program at all.

    After the devepment phase, you can burn images to the spi flash using the serial utility:

    http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L137

     

  • 0
    Prodigy 50 points

    I set up my board with external circuitry (controlled by an MSP430 that we needed anyway), so that it can boot from NOR flash, UART2, or EMULATION mode.  This is done by configuring the BOOTx pins with configurable pullup or pulldown resistors.   The bootloader documentation tells which pins do what.  To get these 3 boot modes, I had to touch 3 different pins.

    By doing this, it will let me put the board into either boot mode, then program from there.  

    Beware however, the internal pullup and pulldown pins on the C64x are quite strong.  I believe the docs say that at least a 20K is required on the BOOTx pins.  You can set your default boot mode with 20k resistors, then if you want an alternate boot mode, separately enable 2k resistors in the opposite direction.  Remember that yo may need to release the 2k resistors for the pin to operate back in normal mode.  It does get a bit tricky.

    Also, on the non BOOTx pins, you need about a 2K resistor just to overcome the internal pullup or pulldown.  The datasheet talk about that.  That's crazy strong since the IPU and IPD can't be disabled.  Too bad.  Make for slightly more tricky design, and doesn't help for power consumption either.

     

     

  • 0 in reply to Mariana
    Intellectual 340 points

    Mariana,

    Thanks for the pointer.

    Could you please answer this question for me and correct me if i am wrong:

    - The serial utility will connect to the DSP through one of the UARTs and burn the application code onto the flash. is this on-chip flash or off-chip? if it is off-chip, is it SPI, I2C, or EMIF?

    Thanks.

  • 0 in reply to Bendous
    TI__Mastermind 24340 points

    Bendous said:
    is this on-chip flash or off-chip?

    Off ship flash, works for the one in the OMAP-L137 EVM.

    Bendous said:
    if it is off-chip, is it SPI, I2C, or EMIF?

     The default is for the SPI flash. But it has the option (-flashType) to be NAND or NOR as well.

  • 0 in reply to Mariana
    Intellectual 865 points

    Hi Mariana.

    I've looked through the given link.

    I jush only use C6747 and try to flashing to spi-flash. but i have some problem to write it.

    I type like below.

    sfh_OMAP-L137.exe -erase -targetType C6747

    and the command line freez with " Waiting for SFT on the OMAP-L137" messages

    It seems like i type  wrong command.

    please tell me a correct command.

  • 0 in reply to Jay Hong
    TI__Mastermind 27585 points

    Are you using the Spectrum Digital EVM? If not you may have to rebuild the sfh to match your custom board.

    Jeff

  • 0 in reply to jc-ti
    Intellectual 865 points

    Hi jeff

    thank you for your answer.

    I've made custom C6747 board. I'll test with rebuild sfh.

    one strange thing is i have a another custom board using OMAP-L137 and uart boot working fine.

    i just exchanged OMAP to C6747. I think it should work with profer command. because the option have a targetType. so i don't understand why i have to rebuild for my custom board.

     

    melon.