<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">is there not a way to use dfu-utilites to install the .jffs2 file to nand?<br><br><br>--- On <b>Wed, 9/16/09, Stuart Winter <i><m-lists@biscuit.org.uk></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Stuart Winter <m-lists@biscuit.org.uk><br>Subject: Re: [ARMedslack] [armedslack] Installing Armed on the Sheeva NAND Flash<br>To: armedslack@lists.polplex.co.uk<br>Date: Wednesday, September 16, 2009, 1:49 PM<br><br><div class="plainMail"><br>Hi Sam<br><br>> I just booted from the ArmedSlack-12.2, sshed into it and started the setup.<br>> It says I need to partition HardDrives. Is there any way to install<br>> ArmedSlack on the internal NAND Partitions instead of an external device.<br><br>The quick answer is "you can't".<br>The longer answer is you *may* be
able to do it, if you have a lot of<br>patience, enough experience and tenacity :-)<br><br>Things to note:<br><br> 1. The installer "partition probe" doesn't look for NAND devices<br><br> 2. Usually (from what I've read so far) you prepare a JFFS2 filesystem<br> and write it to the NAND using "nandwrite" from the mtd-utils package<br> then update the offsets in your u-boot boot loader config.<br> I can't possibly think of a way to include this in the Slackware<br> installer -- you'd have to install it on another machine using<br> installpkg ROOT=/tmp/newarmmachine<br> do some touchups to the configurations (since some of the package<br> post-installation scripts wouldn't have run since they use chroot and<br> run ARM binaries, which wouldn't work on an
x86-- unless you happened<br> to have a spare ARM box around to do the installation).<br><br> A script to do the installation would be something like this:<br><a href="ftp://ftp.armedslack.org/armedslack/armedslack-devtools/slackkit/sansinstaller" target="_blank">ftp://ftp.armedslack.org/armedslack/armedslack-devtools/slackkit/sansinstaller</a><br><br> You'd need to look at how to create a JFFS2 image of the result and<br> write it to the NAND using "nandwrite".<br><br>The research I did so far is here - ordered in some sort of useful<br>fashion:<br><br><a href="ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/" target="_blank">ftp://ftp.armedslack.org/armedslack/armedslack-devtools/sheevaplug/</a><br><br> What also occurred to be is that you could mount the existing jffs2<br> filesystem from
the Slackware installer, and wipe the contents:<br> mount -t jffs2 /dev/mtdblock2 /mnt/<br> or something like this. This would have to be one of the ugliest<br> ways of doing it.<br><br> 3. You'd need to use "nandwrite" to flash the kernel.<br><br> 4. The Slackware ARM 12.2 installer does not include the nandwrite<br> tools. The -current installer includes nandwrite and<br> flash_eraseall but this isn't available yet, and the installer<br> wouldn't work for a v12.2 installation.<br><br>All in all, I'd say that the contents of the NAND flash are to be prepared<br>by the vendor; especially since it'd need a stripped down Slackware.<br>In advance you'd have to know which packages to include in order to<br>make a working bootable Slackware installation, with enough
space<br>left over to have a useable system.<br><br><br><br>-- <br>Stuart Winter<br>Slackware ARM: www.armedslack.org<br>_______________________________________________<br>ARMedslack mailing list<br><a ymailto="mailto:ARMedslack@lists.armedslack.org" href="/mc/compose?to=ARMedslack@lists.armedslack.org">ARMedslack@lists.armedslack.org</a><br><a href="http://lists.armedslack.org/mailman/listinfo/armedslack" target="_blank">http://lists.armedslack.org/mailman/listinfo/armedslack</a><br></div></blockquote></td></tr></table><br>