Ah, got it. Running 'run tftpkernel' fixed the issue.
Brad Dober Ph.D. Candidate Department of Physics and Astronomy University of Pennsylvania Cell: 262-949-4668 On Fri, Sep 25, 2015 at 11:16 AM, Marc Welz <m...@ska.ac.za> wrote: > You need both a valid root file system and kernel on your roach for > the "soloboot" macro to bring up your system. The "run tftproot" > programs a new file system, but it seems that the kernel image isn't > correct, so that must have been managled somehow (possibly with a "run > tftpkernel"). So try to update your kernel. Also: don't try updating > uboot until you are a lot more comfortable with the entire thing, > recovering from a failed uboot update is a lot harder. But you may > have an imls command, it might tell you if it can find a valid kernel > on flash. > > regards > > marc > > > > > On Fri, Sep 25, 2015 at 2:53 PM, Brad Dober <do...@sas.upenn.edu> wrote: > > Hi Casperites, > > > > I'm booting up a new ROACH2 and it was booting fine on soloboot last > night. > > I came in this morning to see this on bootup: > > > > type run netboot to boot via dhcp+tftp+nfs > > > > type run soloboot to run from flash independent of network > > > > > > Hit any key to stop autoboot: 2 \0x08\0x08\0x08 1 \0x08\0x08\0x08 0 > > > > Wrong Image Format for bootm command > > > > ERROR: can't get kernel image! > > > > > > I just tried running tftproot from the latest github version, and it > loads > > without throwing an error, but when I run 'reset', the same error: > > > > > > Wrong Image Format for bootm command > > > > ERROR: can't get kernel image! > > > > > > comes up when trying to boot into soloboot. > > > > > > Any idea what could be the culprit? > > > > > > Brad Dober > > Ph.D. Candidate > > Department of Physics and Astronomy > > University of Pennsylvania > > Cell: 262-949-4668 >
