Dear Paul, As the bootblock might have been erased a simple solution will be to install our testing software (it is also used for initial flashing the cameras and MAC assignment) Please, get it from - http://elphel.cvs.sourceforge.net/viewvc/elphel/prod353/station/ (cvs -z3 -d:pserver:anonym...@elphel.cvs.sourceforge.net:/cvsroot/elphel co -P *prod353*)
Follow the INSTALL file instructions. This shouldn't take long. Then when you open http://127.0.0.1/prod353.html - check Manual Netboot radio button and try to reflash the camera. If you'll be having problems, don't hesitate to drop me a letter. Best regards, Oleg On 24 August 2010 07:59, Andrey Filippov <and...@elphel.com> wrote: > Paul, > > the problem seems that you erased the bootblock and the logs show that you > did not write anything to that block. All the rest seems to be flashed OK, > but the boot code is in the boot block. Can you please post the commands you > used, not just the output? > > > As for flashing the compiled image - what do you mean by "not running"? Not > started or binaries missing? If they are missing, it probably means that > something went wrong during build process, i.e. missing dependencies. > > Did you look at the build output carefully (you can send us compressed > build.log file)? It is very important - as the last step make compares > target.list (the list of all files that are supposed to be installed) and > target.list.new (list of the files that re going to be installed in your > build) and.warns you if there are any differences. If you did not add any > custom programs and did not change the release number (used in the archive > filename) - there should be no differences, you need to resolve any before > flashing the image to the camera. > > Andrey > > >
_______________________________________________ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
