Paul,
Did you have any output when the camera had 192.168.0.200? I'm trying to
think what else can be done...
Today I tried erasing mtd0 with flash_eraseall - but was able to recover
with prod353.
Could you also try:
0. 'cd' to the folder where you built the firmware. There's a netboot
script.
1. ./netboot -d eth0 -mac 000E64000000 -ip 192.168.0.9 -nfs
192.168.0.15:/nfs/latest80
-cmd boot ("/usr/local/sbin" should contain cmdline,etraxfsboot & netboot -
in case the scriptexits before the 2nd step)
2. Put the camera into the netboot-mode and check the serial output (can
take up to 30 secs)
3. Try 1 & 2 with but with "-cmd all" - reflash
> ./netboot -d eth0 -mac 000E64000000 -ip 192.168.0.9 -nfs
> 192.168.0.15:/nfs/latest80
> -cmd all
Best regards,
Oleg
On 25 August 2010 05:11, Paul Shersby <p...@film360.com> wrote:
> Latest information regarding our reboot problem:
>
> We installed the prod353-station and did the manual netboot. The result was
> similar as before. When asking for reboot, the camera was pingable (at
> 192.168.0.200) and nmap showed the ftp port to be open. But after
> reinserting the network cable, there was no ping, no serial output, and no
> serial echo.
> Then we tried again checking 'clean cameras', which didn't work either. The
> reflash logs state the first block to be erased and written to start at
> 0x40000, which might mean that the boot block was skipped.
> We tried a third time, again checking 'manual netboot' with the same
> negative result. Attached are all files with the logs from /tmp/prod353.
>
> _______________________________________________
> Support-list mailing list
> Support-list@support.elphel.com
> http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
>
>
_______________________________________________
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
