Itamar,<br> I have read over many guides, including the Fedora wiki, Ubuntu ARM-specific wiki pages, <a href="http://plugcomputer.org" target="_blank">plugcomputer.org</a>, and a few other places but yet have not found what I've been looking for. All the pages I've read specifically refer to accessing U-Boot over serial (using the $40 box from Global Scale, or I can DIY) from another PC, and I can't do this at the moment. Specifically, I think the problem boils down to knowing specific offsets to data on the NAND on my GuruPlug board.<br>
<br>There are existing tools that will supposedly do what I want -- flash onboard NAND:<br> 1. mtd-utils: <a href="http://www.linux-mtd.infradead.org/">http://www.linux-mtd.infradead.org/</a><br> 2. sheeva-uboot-tools: <a href="http://code.google.com/p/sheeva-uboot-tools/">http://code.google.com/p/sheeva-uboot-tools/</a><br>
<br>I assume that the latter tool relies on the former. Now, fw_printenv (part of mtd-utils) always throws "bad CRC" at me because I haven't figured out the correct offsets/sizes yet. I've done a nanddump on the partitions of the MTD that have the interesting bits on them, namely, the u-boot loader and the kernel. There is a third partition, that holds the rootfs:<br>
<br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">[root@guru ~]# cat /proc/mtd<br>dev: size erasesize name<br>mtd0: 00100000 00020000 "u-boot"<br>
mtd1: 00400000 00020000 "uImage"<br>mtd2: 1fb00000 00020000 "root"<br></blockquote>
<br>I looked at the uImage bit in a hex editor, and found nothing interesting or configurable, just kernel junk. In the "u-boot" partition, I have found bits that look like configuration information, but I _do not_ want to modify the default u-boot options, in fact, I'd rather leave them in case I get a JTAG cable later or do something to bork my OS. I also can't discern where in this file lie the custom settings vs. the default settings, so I won't change any bits here yet...<br>
<br>I have considered another alternative, that is, only flashing over the uImage and rootfs MTD partitions. This would be fine, assuming that the shipped version of U-Boot does not limit functionality on my system... and I think this would allow me to install Fedora 12.<br>
<br>An additional alternative would be to fake passed parameters to the kernel, i.e. hack the kernel source to default to "root=/dev/sda" and thus overriding my current /proc/cmdline:<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
[root@guru ~]# cat /proc/cmdline<br>console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs<br></blockquote><div><br>If anyone has any more information, please advise. I am considering writing to Global Scale / the kernel developers over at Marvell to see if they can drop me any hints... <br>
</div><br><div class="gmail_quote">On Sun, May 9, 2010 at 9:30 PM, Itamar Reis Peixoto <span dir="ltr"><<a href="mailto:itamar@ispbrasil.com.br" target="_blank">itamar@ispbrasil.com.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div>On Sun, May 9, 2010 at 3:46 AM, Jon Hermansen <<a href="mailto:jon.hermansen@gmail.com" target="_blank">jon.hermansen@gmail.com</a>> wrote:<br>
> Hello all,<br>
> I just got a brand new GuruPlug a few days ago and I was hoping to install<br>
> Fedora ARM on it as soon as possible. Well, the only problem is, I neglected<br>
> to get the JTAG breakout box / cables required to get the U-Boot prompt and<br>
> thus, as far as I can tell, can't do much about loading a new U-Boot version<br>
> (hopefully to boot from microSD), putting a new U-Boot config, Linux kernel<br>
> and accompanying rootfs on the NAND/external MicroSD card. I can see the<br>
> /dev/mtd* devices from Debian 5.0.3, kernel 2.6.32-00007-g56678ec, but I<br>
> have yet to write to them from my live system as I want to be absolutely<br>
> sure about what I'm doing on this front.<br>
><br>
> I'd also like to know if I can use the internal NAND/external MicroSD card<br>
> as one big device, as opposed to two seperate devices. I realize the NAND is<br>
> not addressed as a block device, but if they both can contain filesystems,<br>
> does that mean that I can use UnionFS (or something similiar) to bridge two<br>
> seperate filesystems and divide the space taken up by data between the two<br>
> storage devices?<br>
><br>
> If anyone could provide any more information on what I'm attempting to do<br>
> (flash NAND, reinstall OS) without a JTAG cable, either on a SheevaPlug or a<br>
> GuruPlug (from what I've read, they are nearly the same), it would be<br>
> greatly appreciated.<br>
><br>
> Thanks to all of you guys for working out the kinks in Fedora ARM, and I'm<br>
> looking forward to using my favorite distro on the smallest PC I've ever<br>
> had...<br>
><br>
> Jon Hermansen<br>
><br>
</div></div>start here -> <a href="https://fedoraproject.org/wiki/Architectures/ARM" target="_blank">https://fedoraproject.org/wiki/Architectures/ARM</a><br>
<br>
<br>
--<br>
------------<br>
<font color="#888888"><br>
Itamar Reis Peixoto<br>
</font></blockquote></div><br>