• State Answer Suggested
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 487 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.

TMS320C5535 HW USB Bootloader problems?

Marcus Sauter
Prodigy 50 points

We designed a board with 3 DSP´s which we want to connect via the USB interface. But we found a short-circuit between USB_VDDA3P3 and Ground on the first prototype boards. We are able to disconnect this powerlines and use the board in a different way (without USB).

But actual there is still a problem with the C5535. It seems to be that the bootloader doesn´t work anymore. We are able to connect every DSP over a JTAG-Chain and start a simple FW-File with the debugger of CCSV4. But if we program the file to the SPI-ROM nothing happened after a power on reset.

The BIN-file is tested on the ezdspC5535 and worked fine.

The design of each DSP on the prototype boards is similar to the ezdspC5535 design (except USB_VDDA3P3).

We found the note in the datasheet that every USB power supply should connect to ground if it isn´t used. Furthermore the pin USB_VBUS is still connected to 5V.

Is it possible that the bootloader doesn´t work due to the USB interface?

Maybe someone has another idea why the DSP doesn´t load the boot image.

 

 

Thanks in advance

 

Best regards

Marcus

  • 0
    TI__Genius 12575 points

    Hi,

    Is it possible to boot from other supported peripherals other than USB in your custom board. You mentioned you tried from SPI ROM, can you provide more details on this?

     

    • Is this a EEPROM & whether the bootloader requirements wrt this peripheral is taken care ?
    • How did you program boot image to this SPI device ? Does valid image exists ?
    • Did you observe the SPI activities during boot-loading process ? What happens after releasing the reset, did you observe SPI clocks etc is there any scope shots available to share.

    Also, as mentioned in the bootloader application note, each device has a fixed order in which it checks for a valid boot image on each supported boot device. The device order is 16-bit SPI EEPROM, 24-bit SPI serial flash, I2C EEPROM, and SD/SDHC/eMMC/moviNAND. Next the bootloader goes into an endless loop checking for data received on either the UART or USB. So looking at the order, the boot-loader checks for valid image from the USB  in the end, and will get into endless loop (between USB and UART) if no boot image is found. If SPI device has valid image then it should successfully boot from SPI.

    Let us know on the above.

    Also, not sure whether you had already followed below mentioned schematic checklist, if not I recommend you go through the schematic checklist and ensure the details mentioned in the checklists (including USB) are followed/taken-care.

    Regards

     Vasanth

     

  • 0 in reply to Vasantha K
    Prodigy 50 points

    Hi Vasantha,

     

    Thank you for the information.

     

    • We use a 24Bit SPI-ROM.
    • We program the SPI with the CCSV4- debugger and the “programmer_C5535_eZdsp.out”.
    • Until now we are able to see that the debugger is able to boot our FW.
      • We use CCSV4 to program the SPI.
      • Turn the device off and on. => FW is not running
      • We connect the device with the CCSV4-debugger. The program counter pointed to 0xff5xxx (somewhere in this range).
      • Now we pushed the “run-button” and the FW is running (LED on GPIO 17 is blinking).

     

    As well we tried to connect the DSP per UART. It didn´t work and we didn´t spend much time to this scenario. It was only an option for FW-Updates.

     

    At the moment I try to make some changes at the hardware to satisfy the new USB requirements.

     

    Best regards

    Marcus

  • 0 in reply to Marcus Sauter
    Prodigy 50 points
    Hi,

    we already found the problem. At start up the EMU0 is LOW for a short period and interrupts the Bootloader.
    Set EMU0 = HIGH, reset the device and the FW is running.

    But now I have another problem:
    I connect the device after a reset with the CCSV4-debugger (SPI-ROM is empty, no I2C-EEPROM, no SD, no eMMC). The EBSR register is set to 0x6000, I start the Bootloader with the "run-button", stop it after a few seconds and the EBSR-value is still 0x6000 (on the ezDSP the EBSR value = 0x5000).
    Mode 6 means: "SPI, I2S2, I2S3, and GPIO" = active.
    I tried to load a image via UartBoot but it seems that the bootloader didn´t reach the final endless loop.

    Is it possible to get more information about the bootloader / starting procedure


    Best regards

    Marcus