• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 669 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.

Ethernet boot loading 6678

Greg Reuter
Intellectual 535 points

Hi,

Can I boot DSP6678 from Ethernet (BootP) without booting from something else (I2C) first?

On or board, currently in schematic capture, we’re going to connect SGMII directly to another microprocessor’s SGMII (no PHY), and plan to boot from Ethernet.

My TMDXEVM6678L (1.0) won’t generate BootP requests seen by WireShark unless I first put it in emulator debug, then pull the USB cable, then press warm reset.  The emulator must be initializing something, but I’m not even executing a GEL.  What could it be?

Does the Ethernet Boot Parameter table default to something usable on power-up?

Greg Reuter

  • 0
    Intellectual 535 points

    Hi,

    Does anybody bootload directly from Ethernet?

    Greg Reuter

  • 0 in reply to Greg Reuter
    TI__Genius 9915 points

    Hi Greg,

    There is an advisory (Advisory 8) in the errata file for this EVM. C6678 rev1.0 have some PLL lock issues, which will prevent them from booting in any native boot that need PLL. In the EVM if you set in native boot, it will work as we have programmed the FPGA, to always boot in I2C and initialize the PLL and then jump to the desired boot. But moving forward, in the rev2.0, you don't need to do it and you can directly boot in ethernet boot.

    Thanks,

    Aurn.

  • 0 in reply to ArunMani
    Intellectual 535 points

    Thanks Arun.

    I see sprz334d advisory 8 explains the PLL problem.
    That's a tough one.

    Our EVM has 1.0 silicon
    JTAG ID (address 0x02620018) = 0x0090E02F
    CORE ID (address 0x01812000) = 0x00080000

    Sprs691b and Sprz334d differ on silicon revision part numbers, so I'd better coordinate with our distributor to ensure we order 2.0 correctly.

    Thanks for the help.

    Greg Reuter