|
|
Post by baumfalk on Feb 12, 2008 22:10:09 GMT 7
Hi everybody,
(and sorry for my original post in German...)
I have the following problem: I have unsuccessfully tried to upgrade my N5200 from 1.0.8 to 2.0.4: the upgrade process stopped with an error, although I have tried several times.
After reboot it shows version 2.0.4 in the display now, NFS is working fine, but I cannot access the device via webinterface anymore.
Now I am trying to use the method with USB stick and factory_test.sh (I have changed the filename in the script accordingly), but unfortunately it does not work as expected: the USB-device seems to be queried at startup (LED is blinking), but the N5200 boots regularly without actually performing the upgrade.
(I have used this procedure successfully earlier, no idea why it won't work now??)
Can somebody help me??
Arno.
|
|
|
|
Post by volatileacid on Feb 16, 2008 8:32:18 GMT 7
Google translate:
Hello,
I have the following problem: The upgrade my N5200 from 1.0.8 to 2.0.4 failed (even after several attempts).
After restarting the device logs funny but now with 2.0.4. The NCCR-service work, but I come by webinterface is no longer connected to the handheld.
Well, I try to stick via USB and the factory_test.sh. (I have the file name in the script accordingly amended). But unfortunately, it does not - it seems to stick when you are driving them, but does not in the upgrade routine but boots normally.
What can I do?
Arno.
|
|
|
|
Post by baumfalk on Feb 19, 2008 17:33:36 GMT 7
I have now tried to upgrade with several different memory-sticks (because it was metioned that the N5200 is somewhat peculiar about the devices it accepts), but the upgrade still did not work with any of those.
Some ideas what I could do?
Best regards
Arno
|
|
|
|
Post by udegel on Feb 23, 2008 22:12:09 GMT 7
Hi,
I have the same problem ... upgrade failed, then rebooted the N5200 and after that the display shows 2.00.04 but can't access the devices anymore.
The procedure with the USB-stick also didn't work ...
Could you solve the problem so far?
|
|
|
|
Post by baumfalk on Mar 5, 2008 16:51:49 GMT 7
No, unfortunately I still have no solution for the problem. Anybody else??
|
|
|
|
Post by hilldiggers on Jun 8, 2008 22:51:10 GMT 7
Has anyone any solutions to this? I have the same problem.  |
|
|
|
Post by freber on Feb 10, 2009 20:00:25 GMT 7
Ok, I apologise for reviving an old thread, but I have the same problem as of yesterday. My current firmware version is 2.00.04. Yesterday I got myself a new router/dhcp server and after that was configured it gave my N5200 the IP address 192.168.0.102 according to my specifications. On the LCD display, however, the IP address was listed as 192.168.2.1! I pointed my web browser to 192.168.0.102 and got the web interface, logged in, changed the IP address to a static value of 192.168.0.10 and was prompted to reboot. I did so, but then my FW was fried. It seems to boot ok, but when ready it says what everyone else in this thread sees - no WAN, no RAID. Ok, since I had the firmware fried in a similar way once before, I located the factory_test.sh and the firmware version I used to fix the problem that time. (1.00.10) I put them on a USB stick and rebooted. The USB memory flickers at power on, indicating that the device is initialised, perhaps even mounted. Near the end of the boot procedure it flickers again, but only very little, as if it looks for the script to run but does not locate it or it fails immediately on running it. After that the normal procedure of enabling the network interface and RAID is performed and failed. I have a few more detailed questions: - 1) Could the script fail if it was edited with a Windows editor? I.e. got CR+LF newlines instead of just LF? (I think I tried to make sure the file was in linux standard with "dos2unix" from Cygwin)
- 2) Is there a way to get some more feedback from the process? As in verifying that it actually tries to run the factory_test.sh script?
- 2.a) Does the N5200 print the boot sequence and error messages to the serial port or do I have to do the VGA connector thingy to see that?
- 2.b) Can I add more, unconditional
echo "agent2 0 BTMSG XYZ" > /tmp/avrpipe
commands in the factory_test.sh, possibly followed by "sleep 3" to get trace messages on the LCD?
It would be a real shame if the only way out of this was to replace the flash drive in my N5200. Can the IP stack really be so poorly implemented that an IP packet could trash the firmware to the degree of hardware failure? Even if the packet was malformed, which I seriously doubt it could have been, this should not be possible. To me it seems more likely that something is not right with my factory_test.sh file or both the USB-sticks I tried with. However, it worked that one time, long ago... |
|
|
|
Post by peterfu on Feb 10, 2009 22:58:07 GMT 7
|
|
|
|
Post by freber on Feb 10, 2009 23:21:25 GMT 7
Thanks, I will check this extra carefully when I get home today. I use Emacs under Windows and it can be told what file mode to use. So, the definition of "Windows based" is a bit shaky.  Also the dos2unix command fixes the problems. I hope that I messed up last night and that this will fix it. I admit that I was rather tired when I tried. Hmm... I think that I am still tired... I am also going to be brave and un-comment some of those commands in the script that appear to be sending text to the LCD. I hope something will happen - I need my data.  |
|
|
|
Post by freber on Feb 11, 2009 0:59:10 GMT 7
Sorry for the double post, but alas, I still can't make factory_test.sh to run on my N5200. I carefully checked that the file contained no Windows nastiness using "od -t x1", I also added LCD messages and three second delays at strategic places in the script. At first I thought I saw something flash on the LCD before the "2.00.04". After staring at the screen for some time, doing a number of reboots I think that it says "Starting network" and nothing at all about updating the firmware. This makes me believe that at least one of two things are true: - The command "echo "agent2 0 BTMSG Start FW upgrade" > /tmp/avrpipe" does NOT write "Start FW upgrade" on the bottom row of the LCD.
- My NAS completely ignores my script
As an additional test I added a "sleep 60" first in the script, but the boot time is exactly the same as it always was. I am guessing that I am rather screwed if it refuses to even read the script? EDIT: In addition to DOS newlines and types of USB-stick, what can cause firmware 2.00.04 to not read and/or execute the "factory_test.sh" script? |
|
|
|
Post by stanley on Mar 16, 2009 21:05:42 GMT 7
|
|
