I had the same problem. Although \\\'sales\\\' advised me to use the igep-x-loader code, I could not use it. It compiled and did nothing. Not even the leds started burning. According to isee support I ought to make sure that I use a certain cross-compiler, which is nonsense. I could compile the other x-loader code and even tried to compile the igep-x-loader with two different compilers.
Therefore, as a workaround for our seminar(PATS embedded linux seminar - [url=http://www.pats.ua.ac.be/pels]http://www.pats.ua.ac.be/pels[/url]) I modified the original x-loader source code to include support for the NAND flash of the
[b]ipegv2 RC6 board[/b]
. I tested this patch on my boards, and I hope that I covered everything, however, you never know for sure until it is tested extensively.
So, in attachement you can find the patch for x-loader and u-boot (small patch). The procedure is as follows:
Make sure your CROSS_COMPILER and ARCH is set and PATH includes your cross compiler...
git clone [url=git://git.igep.es/pub/scm/x-loader.git]git://git.igep.es/pub/scm/x-loader.git[/url]
git checkout 7a4eb1c5c2a6f2c83927c7a09a335481dc054d70 -b pels
git apply x-loader.pelsv5.diff
Now copy your x-load.bin.ift to your mmc card and rename it to MLO (\\\'M\\\'aria \\\'L\\\'udo \\\'O\\\'liver).
For the u-boot:
tar -xjf u-boot-2011.12.tar.bz2
patch -p1 -i ../u-boot.pels.diff
Now copy your u-boot.bin to your mmc card
Test whether you can boot with your mmc card. Test this a couple of times!!!
If all works as it should, you can flash your bootloaders into the NAND flash as follows:
Boot the device and interrupt the u-boot countdown. You should now get a u-boot shell.
The used partitioning is:
0x00000000 - 0x0007FFFF X-Loader Image
0x00080000 - 0x001FFFFF U-Boot Image
0x00200000 - 0x0027FFFF U-Boot Env Data (X-loader doesn\\\'t care)
If you would like a different partitioning, please adjust the addresses in x-loader and u-boot.
flash the MLO and u-boot.bin:
U-Boot# mmc dev
U-Boot# nandecc hw
U-Boot# fatload mmc 0 81000000 MLO
U-Boot# nand erase 0 80000
U-Boot# nand write 81000000 0 80000
U-Boot# nandecc sw
U-Boot# fatload mmc 0 81000000 u-boot.bin
U-Boot# nand erase 80000 180000
U-Boot# nand write 81000000 80000 180000
And that\\\'s it. Now you can try to boot from NAND. The first time that you get your u-boot, probably it will complain about crc error while reading the environment settings. That is because at the location where it tries to read the environment settings, nothing is written yet. just use saveenv to store the default settings into nand.