A problem during loading mx200

[Aleksey Stepanov]

Hello, we have a problem during loading telepresence mx200 terminal.

The terminal starts up and after booting we see a black screen instead of wallpaper.

The Touch panel displays "Connecting.." message.

Also mx200  takes ip-address from dhcp server and can be ping, but refuses telnet, ssh and web connections.

We have made factory reset with button on the back, but there is no result.

[Danny De Ridder]

When the main application dies, you would see the issues you are explaining. However, ssh to the MX200 might work if you login as root as opposed to admin. Admin requires the main application to be up, or, in later releases, the codec might load a so-called maintenance shell which offers reduced troubleshooting/maintenance. If admin nor root work, the only possible way to see what's going on is to connect into the maintenance port.

Connecting to that port requires special cable explained here :

https://supportforums.cisco.com/docs/DOC-24305

https://supportforums.cisco.com/docs/DOC-27936#comment-14777

Regards,

Danny.

[Aleksey Stepanov]

Thanks a lot. I made this cable and connected to the terminal. But all i can see is a cyclic message like:

U-Boot 2009.03-34 (Jun 10 2009 - 07:47:10) MPC83XX

Reset Status: Check Stop, External/Internal Soft, External/Internal Hard

CPU:   e300c1, MPC8343EA, Rev: 3.0 at 400 MHz, CSB: 133.333 MHz

I2C:   ready

DRAM:  DDR2 RAM: 512 MB

RAM data bus test

And the terminal does not boot at all..

[Danny De Ridder]

Hello,

thanks for taking the time to make the cable. I hope it shows more text after the "RAM data bus test" message, like booting linux etc. I would recommend we try to break into U-boot. This can be done by pressing b followed by c immediately after your reboot the unit.

When you have entered U-boot you should see a prompt like "Intrepid>"

Then enter:

setenv othbootargs noconsolefile allowroot noboot

setenv console ttyS0

boot

And capture all the screen output to a file so you can attach it in your reply later.

When you get as far as a login prompt, please login as root and do :

cat /var/log/* /var/log/eventlog/*

Hopefully we can see whether this is a hardware or software error then.

[Aleksey Stepanov]

I hope it shows more text after the "RAM data bus test" message, like booting linux etc. I would recommend we try to break into U-boot.

Unfortunately only this message i see at the screen..

I think that this case is a reason for replacement of the unit.

Thanks you for your cooperation.