[Elphel-support] netboot script errors out

[Heinrich Mueller]

Am 23.02.2011 05:17, schrieb Brian Burke:
> My 353 was on 8.0.7.1, and I wanted to upgrade it to 8.0.9.  I setup 
> NFS and tried using the web interface - the "Check NFS" and "Validate 
> Files" functions worked, but pressing "Reflash" did nothing (it 
> reported it was working, but it didn't seem to do anything).
>
> At this point (if memory serves), I tried running nfs_update manually, 
> and this seems to have bricked the camera.  I no longer have access to 
> the log file, but it reported nothing but erases. The NIC lights no 
> longer light on the camera.
>
> Now I'm on to trying to flash to 8.0.9 via netboot.  I'm running 
> Ubuntu 10.10.  I installed the Elphel Software Kit for Ubuntu - 
> configured NFS, installed the cris tools (with the downgraded compiler 
> and accepting all defaults), and built the Elphel software using 
> 'elphel353_80_install_from_cvs.sh'.  I then downloaded and installed 
> 'elphel353-8.0.9', as that's the version I want.
>
> I then attempt to follow the instructions at 
> 'http://wiki.elphel.com/index.php?title=Netboot_firmware_upgrade'. 
> <http://wiki.elphel.com/index.php?title=Netboot_firmware_upgrade%27.>..
>
> I 'cd' to '/home/brian/elphel353-8.0.9/elphel353' - no problem.
>
> I run '. ./init_env' - prepends the two paths to my PATH.
>
> Then, I run the netboot command - 'sudo .netboot -mac 000E64000000 -ip 
> 192.168.1.9 -nfs 192.168.1.11:/nfs/images/8.0.9 -cmd update -d eth0 
> -nfs_dir /nfs/images/8.0.9' - and get this:
>
> ./netboot: line 40: cmdline: command not found
> cat: kimage: No such file or directory
> ./netboot: line 44: etraxfsboot: command not found
>
> Frustrating.  I know 'init_env' should help here, but it didn't.  What 
> am I missing?  Doing an 'echo $PATH' confirms that 
> '/home/brian/elphel353-8.0.9/elphel353/tools/build/bin' and 
> '/usr/local/cris/bin' are in there.  I can cd to 'tools/build/bin' and 
> see that 'etraxfsboot' and 'cmdline' are there, but 'whereis 
> etraxfsboot' gives me nothing.
>
> Any help at all would be greatly appreciated.  Thanks.
>
>
>
> _______________________________________________
> Support-list mailing list
> Support-list at support.elphel.com
> http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
I assume that this init_env script does an EXPORT?
You could add the directories to your bashrc and then do "source 
~/.bashrc" to refresh it.
After that use sudo for the netboot command.

Here's mine:
/#elphel
export AXIS_TOP_DIR="~/elphel/elphel353"
export PATH="$AXIS_TOP_DIR/tools/build/bin:$PATH"
export PATH="/usr/local/cris/bin:$PATH"
export AXIS_KERNEL_DIR="$AXIS_TOP_DIR/os/linux-2.6/"

Change that according to your configuration (AXIS_TOP_DIR).

Did you hook up the serial console (at the side of the unit)? What does 
for example cutecom say?
Did you boot the camera a few times like suggested?
http://wiki.elphel.com/index.php?title=Netboot_firmware_upgrade

Is your network configured correctly? :D

If all goes well, the serial console will tell you when to shut the 
camera down.

Cheers, Heinrich

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://support.elphel.com/pipermail/support-list_support.elphel.com/attachments/20110223/e8dffcf1/attachment-0002.html>