• Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 343 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.

Firmware dependent on slave chip

DV
Prodigy 170 points
Other Parts Discussed in Thread: TPS65950

Is the firmware (first level) boot loader dependent on a TLW4030/65950 being present? This code does not seem to be public domain.

I assume because the USB (for USB boot) operates through this chip it is almost required in any design.??

I know EVM and Beagle use MMC/SD card detect through this chip also but I assume the firmware does not look for card present when trying MMC/SD boot??? 

  • TI__Guru 64610 points

    DV said:

    Is the firmware (first level) boot loader dependent on a TLW4030/65950 being present? This code does not seem to be public domain.

    I assume because the USB (for USB boot) operates through this chip it is almost required in any design.??

    I know EVM and Beagle use MMC/SD card detect through this chip also but I assume the firmware does not look for card present when trying MMC/SD boot??? 

    The rom code of the OMAP35x does interact with the TPS65950 to enable certain voltage rails, etc. depending on the boot mode.  Primarily, enabling the MMC/SD voltage rail if a MMC/SD boot is desired.

    However, it does not require the TPS65950 to be present.  The fundamental assumption would then be that the appropriate voltage rails are available for the appropriate boot mode.

    It is my understanding the rom code sets up the USB ULPI PHY in the TPS65950 through the ULPI interface.  Therefore, any ULPI compliant transceiver should be supported.