TMDSRM48HDK: Hercules RM48x Development Kit

Hi Brian,

Brian Stuecker1 said:

The ethernet port is not functional, so we are unable to flash the board.

Sorry i don't get this, we don't flash the board through ethernet right.

We will flash the board with either onboard XDS100v2 emulator or through external debugger right.

Brian Stuecker1 said:

We replaced it with another one and it worked perfectly. 

Did you replaced the controller on the same board, or did you test with other board?

if you are using HDK board then make sure that 12v, 5v, 3.3v and 1.2v are within the range or not?

--
Thanks & Regards,
Jagadish.

We sent the below in response to the email we received, since we haven't gotten a reply to that, I'm assuming you did not get it.

To go into more detail:

 We initially powered up the TMDSRM48HDK using our system’s power supply. All 4 power status LEDs lit up (DS2-DS5) and we were able to successfully flash the board using the USB Mini port (J7). The firmware we are using is not new and has worked on multiple TMDSRM48HDK’s before and since this one. We also had Dipswitch S2.4 (ETHERNET ON) turned on and Jumper J8 jumpered (this is our standard setup). Everything appeared to be fully functional up until we tried to communicate via ethernet. It was not viable on network and we couldn’t ping it even though the flashing succeeded. When we hit these problems, we stepped back and powered the TMDSRM48HDK using the supply provided in the kit and tried flashing again and hit the same result. Next, we grabbed a new TMDSRM48HDK and flashed it while it was powered using our system’s power supply (the same way the first TMDSRM48HDK was initially powered and set up). We again saw good status LEDs and the flashing was successful. This time we were able to connect to the TMDSRM48HDK via ethernet, and everything worked normally. Again, the only perceivable difference between the 2 TMDSRM48HDK’s was that the first one wouldn’t communicate over ethernet even though we got a successful flash and everything lit up correctly.

At that point we boxed the TMDSRM48HDK that wouldn’t communicate via ethernet, and decided to reach out as this problem is specific to this board. We did not go into any other troubleshooting. Hopefully this helps.

Hi Brian,

Brian Stuecker1 said:

At that point we boxed the TMDSRM48HDK that wouldn’t communicate via ethernet, and decided to reach out as this problem is specific to this board. We did not go into any other troubleshooting. Hopefully this helps.

Now i understood, thanks for detailed explanation.

--
Thanks & regards,
Jagadish. 

Hi Brian,

I am suspecting this issue is due to the Ethernet PHY transceiver IC (DP83640)

Are you sending any debug information of PHY to the serial port, something like below:

If PHY IC working correctly, then we should get PHY ID and PHY Alive Status as SUCCESS. If we didn't get the success for PHY ID and Alive status then there must be some problem with the DP83640 PHY IC.

So please check and update this status.

--
Thanks & regards,
Jagadish.