SatSig topic:

Modem software corrupt

(Read 5497 times)

Feb 3^rd, 2009 at 10:16am

hello,
I had some problem with my Idirect 5000 series modem.

I have achieved a lock and in the course of activation I tried to load the cumulative image file package and before the end of the process there was light outage and by the time the light came back I noticed the tx and rx light did not come up. I couldn't get into the modem through the lan port(Isite) and I tried to get in through the com port(hyperterminal) but the modem was responding with eror messages. looks like a corrupt file. It was not booting properly as in the booting process was stopping at the middle. The last prompt of the booting lines was #000007 and all kind of messages. I guess the software is corrupt but the firm ware is still okay because is showing sdram successful.

The only problem is that is not booting up to the Idirect loggin.

So does anybody have a solution to my problem. I need to know what to do to make it boot normally as it was before the light outage.

Feb 3^rd, 2009 at 12:15pm

Can you provide the exact string of errors you are seeing on console?

If you were loading a BSP, I am assuming this is a 7.1.1 or later remote (iDS)?

Feb 5^th, 2009 at 1:04am

1. Are you an HNO?
2. What IDS version? Assuming 7.1 or above (please advise)

If you are an HNO, or your HNO is willing to provide you with the zimage file in the cumulative_update pkg, you may be able to recover this remote.

Before I type a dissertation, I would like to solicit the status of this remote?

Is it still down?
Your iDS version?
Whether or not you are an HNO or have access to an uzipped cumulative update image set?

Thanks

M

Feb 15^th, 2009 at 4:56pm

hello Mike,

This is the exact corrupt page showing on the hyper terminal of idirect modem 5150 series am looking forward for any solution to revive the modem back.

DRAM Test ................................
DRAM Test Successful
+Ethernet eth0: MAC address 00:60:43:00:00:00
IP: 192.168.0.1/255.255.255.0, Gateway: 192.168.0.2
Default server: 192.168.0.2

RedBoot(tm) bootstrap and debug environment [ROM]
release, version "iDirect 1.1" - built 16:16:40, Apr 29 2005

Platform: iDirect iDS Platform (XScale)
Copyright (C) 2004, 2005 iDirect Technologies, Inc.

Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x10000000, [0x0001c540-0x01fd1000] available
FLASH: 0x50000000 - 0x52000000, 256 blocks of 0x00020000 bytes each.
== Executing boot script in 5.000 seconds - Press <Space Bar> to abort
RedBoot> fis load Linux
RedBoot> exec
Using base address 0x01600000 and length 0x00100000
$T050f:00600000;0d:0000b4ec;#71$T050f:00600000;0d:0000b4ec;#71

Feb 15^th, 2009 at 6:47pm

Good afternoon. Are are you an HNO or a user?

Reason I ask, is if you intend to fix this problem yourself then you will need the ability to access the NMS and unzip the cumulative_update file that is located in the image sets of the NMS. Do you have access to the NMS image sets?

If you are a user, then you more than likely do not. If you are an HNO (Hub Administrator) then you definitely have access to that image set and should be able to unzip it to a temp folder on the NMS, and transition it to the desktop of the client that is connected to the iDirect box. You will also need a copy of iSite for your version of software as we will need to TFTP that file from the client to the iDirect unit.

If you have access to the NMS, I can walk you thru extracting a specific file from the cumulative_update image set (be advised, the procedures will be provided outside of this forum, thru private message).

If you do not have access to the NMS then you may as well prepare to RMA that box. Unless you can get your provider (the hub operator) to extract the image for you.

Let me know how you want to proceed.

r/
M

Feb 23^rd, 2009 at 7:36pm

Dear mike,

Thanks for the prompt reply. I guess I am with you all the way and I hope with your assistance I should get to the root of this problem.

As regards your question , I think I can access the NMS file with my level of understanding of the modem. I have been working with I direct modem for about three years now and I have had enough experience to understand the technical language.

So, I'll appreciate it if you can walk me tru the solutions .

thnks

Feb 23^rd, 2009 at 8:14pm

I will get it typed up and it will come to you in the form of PM. So, keep an eye on your inbox (for this forum)

M