Yes. You can reflash it, but it is supposed to eliminate the need for jtag. I did a screen dump of the boot process some days ago, after installing the RSEL kernel. On the working card, it looks like it fails to read the uImage and reverts to the uImage in nvram OR possibly defaults to nvram to begin with.., but is able to load the rootfs partition. It is probably an environment variable in u Boot, but I had been assuming all along that I built the boot.scr and/or uImage (based on the RSEL vmlinuz) incorrectly, which may be the case on the new card. The boot order, if the nvram image is not used, is USB0, USD1, microsd, esata, then tftp, which is where I get stuck trying to boot to the new card.
Here is the output on both cards: New card: /dev/sdb1 : start= 16, size= 39088, Id=83 /dev/sdb2 : start= 39104, size= 15484736, Id=83 Existing card: /dev/mmcblk0p1 : start= 16, size= 39088, Id=83 /dev/mmcblk0p2 : start= 39104, size= 15646528, Id=83 > There's a kernel image in the firmware? I wasn't aware of that. Have you > precisely copied the partitions (layout and size) to the new card? Is the > output of: > > # sfdisk -d > > on them identical? > > > Try the attached init script. > > > > Thanks for the advice, Gordan. I'm learning as I go... >> > > Any time. :) > > Gordan > > _______________________________________________ > users mailing list > [email protected] > http://lists.redsleeve.org/mailman/listinfo/users > > -- Thanks, Ian M Perkins
_______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
