Paul, Please have a look at this README also: http://elphel.cvs.sourceforge.net/viewvc/elphel/elphel353-7.1/README.flash?view=log There are instructions on how to reflash with the boot block rewriting.
Oleg On 24 August 2010 13:10, Oleg K Dzhimiev <o...@elphel.com> wrote: > Paul, > > Please, try "prod353" I mentioned in my previous letter. It should correct > the boot block. > > Oleg > > On 24 August 2010 11:48, Paul Shersby <p...@film360.com> wrote: > >> More information regarding our 'flashing' problem: >> >> The commands used in trying to reflash the boot block are in the attached >> script 'netboot-full'. Seems it had accidentally been renamed to >> 'netboot-full.dat' in the last post. Most importantly we would like to >> write >> a correct boot block, regardless of the remaining image, so that we could >> just reflash a distributed image. >> >> As for the build, we're currently repeating it. A problem showed up: Some >> executables were missing in the target.list.new, basically busybox_old and >> the links to it. So we've put them in place manually and continued. >> But our foremost problem is now getting the boot block fixed. >> >> >> The file 'target.list.diff' shows the message about the missing files in >> target.list.new. >> By the way, it seems your descriptions >> "->" means ... >> "<-" means ... >> are inverted. >> >> >> _______________________________________________ >> 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
