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.

How can I burn c5505 dsp using xds100v2 emulator in CCSv4?

Other Parts Discussed in Thread: TMS320VC5505

Hi all,

I'm using code composer studio V4 with  TMS320VC5505. For debugging I use xds100v2 jtag emulator. There is no menu item for burning dsp in CCSv4. How can I burn c5505 dsp using xds100v2 emulator?

  • Hello,

    The flash programmer is tightly integrated into CCSv4 so that when you try to load your program into flash memory, it will flash the device automatically.

    Thanks

    ki

  • Thanks for quick replaying. 

    When I execute debugging , it runs. I am not able to burn on chip rom of cc5505. Is it due to memory map file since  I place all memory sections on daram and saram? Does it work when i place text section on PDROM instead of ram section?

    Thanks

  • Hi,

    C5505 only has ROM and not internal flash memory, therefore non-writable. All memory sections must be loaded to RAM. 

    If you are using the C5505 EVM, Spectrum Digital has some example code that allows writing to the external Flash memory on board. Check:

    http://support.spectrumdigital.com/boards/evm5505/revd/

    Hope this helps,

    Rafael

  • Hi desouza,

    Thanks. I m able to load the user code on spi eeprom of evm5505 thanks to your suggestion. It runs and ok. 

    But as you stated it has no internal flash memory and the rom is non-writable. Does this mean my PCB must include external components such as spi eeprom, ext. flash on which I  can load the user code? If not so, how should I do to execute the code on vc5505?

    I hope I clearly stated my problem.

    Best regards... 

  • I have a question,

    * If I can't use this ROM why do you list it (ROM) in the dsp selector guide?

    After a more detailed serach i found that, this ROM is used for Hardware FFT alg.

    But it is still non-sense to add this "not usable" thing to selector guide!

     

    And let me quote some text from sprugh5.pdf (TMS320C55DSP User's Guide)

    section 1.2.1.3:

    1.2.1.3 On-Chip Single-Access Read-Only Memory (SAROM)

    The zero-wait-state ROM is located at the CPU byte address range FE 0000h - FF FFFFh. The ROM is

    composed of four 16K-word blocks, for a total of 128K-bytes of ROM. Each ROM block can perform one

    access per cycle (one read or one write). ...

    what about this write operation?

     

  • Hi,

    metusa said:

    Hi desouza,

    But as you stated it has no internal flash memory and the rom is non-writable. Does this mean my PCB must include external components such as spi eeprom, ext. flash on which I  can load the user code? If not so, how should I do to execute the code on vc5505?

    Yes, you are right. Typically for C5000, C6000, Integra, Sitara, etc. you need to have an external memory device that contains your code and initialized data. The bootloader code (preloaded from factory into the internal ROM) can perform several tasks to properly load the code from Flash (usually slow memory) to RAM (faster) and then correctly execute your program.

    Regards,

    Rafael

     

  • Hi,

    selami tastan said:

    I have a question,

    * If I can't use this ROM why do you list it (ROM) in the dsp selector guide?

    After a more detailed serach i found that, this ROM is used for Hardware FFT alg.

    But it is still non-sense to add this "not usable" thing to selector guide!

    I didn't say you can't use this memory; I said you can't write to it. ROM stands for Read-Only Memory.

    The C5505 ROM is preloaded in the factory and can hold several useful things like code (see my answer above about bootloader) and data tables that are useful depending on the application you are developing (HW FFT,  sinewave, etc.).  

    selami tastan said:

    access per cycle (one read or one write). ...

    what about this write operation?

    I am pretty sure this parenthesis explains the definition of "one access per cycle", but I understand the way it was put in the datasheet may cause confusion.

    Regards,

    Rafael

     

  • You said that 

    "The bootloader code (preloaded from factory into the internal ROM) can perform several tasks to properly load the code from Flash (usually slow memory) to RAM (faster) and then correctly execute your program."

    C5505 support secure boot images. At this point i have several questions.
    1 - Is there any restriction for this 24 bit SPI flashes? For example, can i use 1Mbit version of SPI flash used in C5505 EVM?
    2 - Does secure boot-up procedure support boot from 24 bit SPI flashes?
    3 - What do I have to do, to get these secure boot-up tools?

  • Hi,

    Unfortunately my knowledge is restricted to the generic bootloader process, but any device-specific implementation details are beyond my understanding. In this case I suggest you to ask these questions in the C5000 device forum, as you can get better answers from the device experts there. 

    Regards,

    Rafael