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

NDK issues with new hardware (C6748) (RTC?)

DanB57495
Expert 1340 points
Other Parts Discussed in Thread: OMAP-L138

Hello,

We are testing a new board layout that includes an Ethernet interface based on the Logic PD approach used with the OMAP-L138 using C6748 SOM (NOT OMAP SOM). The software runs successfully on the Experimenter board, but fails in the new hardware. All the initialization appears to run correctly, but when an Ethernet cable is connected we get a "NO PHY CONNECTED" error. All of the hardware connections appears to be the same, but one thing we don't have on this hardware is a second oscillator for the C6748 Real Time Clock (RTC). It is not obvious in the NDK literature whether the timers being used require RTC support. Is this the case?

Any thoughts are welcome.

Thanks in advance.

 

Dan.

  • 0
    Expert 1340 points

    I should also mention that we are now using an external clock (rather than crystal). The frequency is the same (24MHz) and the rest of the program (which doesn't currently use or change IO except mDDR and JTAG) runs fine.

    In the C6748.GEL file provided with the Experimenter/EVM kit, I have tried changing the "Set_Core_300MHz()"  PLL0 from:

    device_PLL0(0,24,1,0,1,11,5);

    to

    device_PLL0(1,24,1,0,1,11,5);

    to reflect the external clock. The (non-NDK )program runs equally well with this set or not, and it makes no difference for the "NO PHY CONNECTED" error.

    I'm not sure if this would effect anything?

    Dan.

  • 0 in reply to DanB57495
    Expert 1340 points

    OK....

    I cried "wolf"...

    Turns out it was a pull-down resistor that was missing on the MDC enable line!

    SORRY!!!

    Thanks for listening anyway.

     

    Dan.

     

     

     

  • 0 in reply to DanB57495
    TI__Expert 7250 points
    Glad to see this was resolved