E5810B does not complete bootup

[Clueless]

Hi all,

I have an E5810B ethernet-GPIB bridge that is not functional. With connection to the internal serial port I can see that it is partly alive. It gets this far:

ÿÀCCCCCCCC
Myreka Tornado Init
I2C:   ready
DRAM:  256 MiB
NAND:  128 MiB
MMC:   OMAP SD/MMC: 0

It doesn't seem to be responsive to any keys. Any thoughts ?

[jchw4]

Could you provide any photos?

[Clueless]

There's no other output than what I copied and pasted. I might add that on startup, it first illuminates the power, then USB, RS232 and fault, then all the LEDs and the display goes to all solid-block characters. And that's the end of it. If an ethernet cable is connected, the ethernet PHY establishes a link. That might not mean anything other than that the PHY is working and has power.

Let me know what pictures I could post if that would be helpful.

[Robert_the_Bob]

Hi All...


I had two such gateways that were as unresponsive as you described...
I could get both back to life by taking inspiration from another place inside this blog (JiriB post)...

https://www.eevblog.com/forum/repair/e5810b-bricked/

Below is the method I used to get/extract/prepare the two files needed to fix them ( MLO_XMODEM.bin    and     u-boot_YMODEM.bin )

Download the latest E5810B firmware from Keysight

https://www.keysight.com/us/en/lib/software-detail/instrument-firmware-software/e5810b-langpibusb-gateway-firmware-2426653.html

Unzip the received B-01-07.zip, locate & copy the file e5810_B_latest_firmware.hex to your /home/user
(user being of course your username)

Sudo su

Check if you have binwalk installed by just typing binwalk

If not found, then       apt install binwalk

binwalk -e  e5810_B_latest_firmware.hex

This should have created a folder    _e5810_B_latest_firmware.hex.extracted

Go inside this directory     cd _e5810_B_latest_firmware.hex.extracted

ls -l      You should see a file called 4A8B

binwalk -e 4A8B

This should have created a folder    _4A8B.extracted

Go inside this directory     cd _4A8B.extracted

MLO.hex  and   u-boot.hex are there: copy them to your /home/user

cp MLO.hex /home/user   and    cp u-boot.hex /home/user

Go back to your /home/user/ directory

cd /home/user

Process both files (As per JiriB procedure) respectively with:

dd if=MLO.hex skip=579 count=68240 bs=1 of=MLO_XMODEM.bin

and

dd if=u-boot.hex skip=123 count=264696 bs=1 of=u-boot_YMODEM.bin


Et voilà: you should now have the files required to go ahead with the remaining of JiriB procedure...


Attached is the E5810B UART0 Pinout (Baud Rate = 115200)


Best Regards...

[Clueless]

I saw that post by Jiri; it was a real tour de force in repair of a bricked Linux system. Sadly I could not do the same since I didn't have a working serial console. Specifically, the hardware worked and showed boot log messages but when it came to the all LEDs on state, it became unresponsive. It may have been possible to figure out how to access a JTAG or something but at that point I just sent it to Keysight. They have an annual service contract on these for around $40/year. Given the number of reports on units like this, it seems like that could be a good idea.