uBoot with Pogoplug v2 Ping(Memory problem)

Re: uBoot with Pogoplug v2 Ping(Memory problem)

battscrew — Sat, 02 Apr 2011 11:28:50 -0400

Jeff Wrote:
-------------------------------------------------------
> Oops, my mistake! Here's a copy of the original
> Pogoplug Pink uBoot:
> http://jeff.doozan.com/debian/uboot/uboot.mtd0-pin
> k.kwb

i get a file not fond error is there a new location?

Re: uBoot with Pogoplug v2 Ping(Memory problem)

Storycrafter — Sun, 17 Oct 2010 20:16:35 -0400

AbsoluteNirvana, thanks a heap. Your flash fixed the 256M/128M issue for me.

Re: uBoot with Pogoplug v2 Ping(Memory problem)

Jason — Wed, 06 Oct 2010 23:11:41 -0400

aperson Wrote:
-------------------------------------------------------
> AbsoluteNirvana Wrote:
> --------------------------------------------------
> -----
> > If you trust my word you can use the version
> that
> > I built since it is working fine for me. I
> > modified Jeff's scripts that install uboot
> > (install_uboot_mtd0.sh from the uboot page) and
> > install debian squeeze
> (dockstar.debian-squeeze.sh
> > from the install debian) to use my version of
> > uboot for the pogoplug v2. I've hosted these
> > modified versions in my public dropbox folder
> > below:
> >
> >
> > [*]
> >
> http://dl.dropbox.com/u/194683/install_uboot_mtd0.
>
> > sh
> > [*]
> >
> http://dl.dropbox.com/u/194683/dockstar.debian-squ
>
> > eeze.sh
> >
> >
> > These are the scripts that I used to install
> > debian and the 256MB uboot on my pogoplug. Let
> me
> > know if you have any questions.
>
> I used your uboot image and mtd0 script.
> Everything worked just fine. I can now use all
> 256MB of RAM on my Pogoplug. Thanks,
> AbsoluteNirvana!

Definately thanks AbsoluteNirvana, I can now use all 256MB of my ram as well.

Re: uBoot with Pogoplug v2 Ping(Memory problem)

markweng — Tue, 21 Sep 2010 00:32:38 -0400

Hi aperson
After you update the uboot from AbsoluteNirvana

When you but into Pogo OS do you still see the 256MB of RAM also?

Thanks
Mark

Re: uBoot with Pogoplug v2 Ping(Memory problem)

aperson — Mon, 20 Sep 2010 22:44:45 -0400

AbsoluteNirvana Wrote:
-------------------------------------------------------
> If you trust my word you can use the version that
> I built since it is working fine for me. I
> modified Jeff's scripts that install uboot
> (install_uboot_mtd0.sh from the uboot page) and
> install debian squeeze (dockstar.debian-squeeze.sh
> from the install debian) to use my version of
> uboot for the pogoplug v2. I've hosted these
> modified versions in my public dropbox folder
> below:
>
>
> [*]
> http://dl.dropbox.com/u/194683/install_uboot_mtd0.
> sh
> [*]
> http://dl.dropbox.com/u/194683/dockstar.debian-squ
> eeze.sh
>
>
> These are the scripts that I used to install
> debian and the 256MB uboot on my pogoplug. Let me
> know if you have any questions.

I used your uboot image and mtd0 script. Everything worked just fine. I can now use all 256MB of RAM on my Pogoplug. Thanks, AbsoluteNirvana!

Re: uBoot with Pogoplug v2 Ping(Memory problem)

AbsoluteNirvana — Mon, 20 Sep 2010 01:32:31 -0400

I finally flashed the uboot.mtd0.kwb image that I compiled and I can confirm that it works and enables all 256MB of RAM.

PhantomsDad Wrote:
-------------------------------------------------------
> There is this in dmesg, but presumably this is
> some problem in my build.
>
>
> [ 2.215118]
> /build/buildd-linux-2.6_2.6.32-20-armel-qpwOHl/lin
> ux-2.6-2.6.32/debian/build/source_armel_none/driv
> ers/rtc/hctosys.c: unable to open rtc device
> (rtc0)
>

I have the same entry in my dmesg log as well. This error is from the kernel trying to initialize a soundcard when the pogoplug does not have one. It can be safely ignored.

aperson Wrote:
-------------------------------------------------------
> PhantomsDad Wrote:
> --------------------------------------------------
> -----
> > I didn't try your attachment, but I duplicated
> > what you did and installed on my pogoplug v2
> > (pink). Works fine and reports 256 megs of ram.
>
> > :)
>
> PhantomsDad, can you share your uBoot image since
> you've verified it works? I've got a Pogoplug V2
> and I'd like to use all 256MB of RAM too. I tried
> compiling my own uBoot image following
> AbsoluteNirvana's steps and testing it via
> tftp'ing it first (following Jeff's instructions).
> However, my device just hangs after that. ygater
> ran into the same problem (discussed on this
> thread) but just skipped testing via tftp and
> flashed it to mtd0. I am not so brave since I
> don't have a JTAG for recovery.

If you trust my word you can use the version that I built since it is working fine for me. I modified Jeff's scripts that install uboot (install_uboot_mtd0.sh from the uboot page) and install debian squeeze (dockstar.debian-squeeze.sh from the install debian) to use my version of uboot for the pogoplug v2. I've hosted these modified versions in my public dropbox folder below:

These are the scripts that I used to install debian and the 256MB uboot on my pogoplug. Let me know if you have any questions.

Re: uBoot with Pogoplug v2 Ping(Memory problem)

aperson — Sat, 18 Sep 2010 10:15:52 -0400

PhantomsDad Wrote:
-------------------------------------------------------
> I didn't try your attachment, but I duplicated
> what you did and installed on my pogoplug v2
> (pink). Works fine and reports 256 megs of ram.
> :)

PhantomsDad, can you share your uBoot image since you've verified it works? I've got a Pogoplug V2 and I'd like to use all 256MB of RAM too. I tried compiling my own uBoot image following AbsoluteNirvana's steps and testing it via tftp'ing it first (following Jeff's instructions). However, my device just hangs after that. ygater ran into the same problem (discussed on this thread) but just skipped testing via tftp and flashed it to mtd0. I am not so brave since I don't have a JTAG for recovery.

Re: uBoot with Pogoplug v2 Ping(Memory problem)

karamazov1 — Mon, 06 Sep 2010 22:12:23 -0400

Mark, I managed to get copies (from PogoPlug OS) of flash_erase and nandwrite. While in plugbox, I run the commands, and rebooted. After that, ended up in PogoPlug again. It seems more testing needs to be done with the Pink Pogos. I reinstalled uboot, and I'm back to plugbox with 128MB memory, oh well.

I will keep an eye for updates.

Thanks

Re: uBoot with Pogoplug v2 Ping(Memory problem)

markweng — Mon, 06 Sep 2010 17:37:18 -0400

karamazov1 Wrote:
-------------------------------------------------------
> Thanks Mark. I'm not sure what went wrong, but I
> had to reinstall uboot image since I couldn't boot
> into plugbox anymore. To start, booted into
> pogoplug and applyied the flash erase and
> nandwrite. Rebooted a couple times, and kept
> ending up at pogoplug. So I had ro reinstall uboot
> in order to get back into plugbox.
>
> Should I have applied the flash write/nandwrite
> from plugbox environment? If so, where do I get
> the binaries? I started doing this from plugbox,
> then I realized neither flush erase or nandwrite
> were present, this is what prompt me to boot into
> pogoplug
>
> Thanks

You can flash u-boot back to uboot.mtd0-pink.kwb in debian or PogoOS.
Check at Jeff's install file then you will find out where to get the flash_erase

http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh

nandwrite I believe it is in PogoOS.

Hope this help...

My Pogolug Pink right now is not with me,so I can't test for you.

Mark

Re: uBoot with Pogoplug v2 Ping(Memory problem)

PhantomsDad — Mon, 06 Sep 2010 17:24:54 -0400

There is this in dmesg, but presumably this is some problem in my build.

[    2.215118] /build/buildd-linux-2.6_2.6.32-20-armel-qpwOHl/linux-2.6-2.6.32/debian/build/source_armel_none/driv
ers/rtc/hctosys.c: unable to open rtc device (rtc0)

Re: uBoot with Pogoplug v2 Ping(Memory problem)

PhantomsDad — Mon, 06 Sep 2010 17:20:10 -0400

AbsoluteNirvana Wrote:
-------------------------------------------------------
> I have compile of version of uBoot specific for
> the Pogoplug v2 (pink) that (hopefully) enables
> all 256MB of RAM. I built it using Jeff's
> instructions on how to build uBoot for the
> Dockstar with the following changes:
>
>
> [*] Instead of dramregs_pp128_A.txt I downloaded
> and used dramregs_pp256_A.txt from the root of
> pogoplug-u-boot-1.1.4.tgz on the Pogoplug
> opensource site.
> [*] I modified the doimage command in the
> mkDockstar.mtd0 script to use this
> dramregs_pp256_A.txt file as input:
> ./doimage -T nand -D 0x600000 -E 0x600000 -P 2048
> -R dramregs_pp256_A.txt u-boot.bin u-boot.nand
>
>
>
> These are the only changes that I believe are
> necessary in order to set the total memory to be
> 256MB instead of 128MB. The dramregs_pp256_A.txt
> file contains the exact same data as the
> dramregs_pp128_A.txt file with ecc proposed
> changes.
>
> Just as a disclaimer, I have not tested out this
> uBoot image myself as I don't have a JTAG setup to
> recover in case anything goes wrong. However,
> anyone else who has JTAG or is feeling brave,
> please feel free to test the attached
> uboot.mtd0.kwb image and let us know how it goes.
> I am happy to assist anyone who is interesting in
> testing this.

I didn't try your attachment, but I duplicated what you did and installed on my pogoplug v2 (pink). Works fine and reports 256 megs of ram. :)

BTW, building on my debian 32-bit system, I had to copy doimage from the same pogoplug-u-boot-1.1.4.tgz file you mentioned. The doimage jeff provides is for 64-bit systems.

Anything I should do to validate that everything is OK?

Re: uBoot with Pogoplug v2 Ping(Memory problem)

karamazov1 — Sun, 05 Sep 2010 23:18:29 -0400

Thanks Mark. I'm not sure what went wrong, but I had to reinstall uboot image since I couldn't boot into plugbox anymore. To start, booted into pogoplug and applyied the flash erase and nandwrite. Rebooted a couple times, and kept ending up at pogoplug. So I had ro reinstall uboot in order to get back into plugbox.

Should I have applied the flash write/nandwrite from plugbox environment? If so, where do I get the binaries? I started doing this from plugbox, then I realized neither flush erase or nandwrite were present, this is what prompt me to boot into pogoplug

Thanks

Re: uBoot with Pogoplug v2 Ping(Memory problem)

AbsoluteNirvana — Sun, 05 Sep 2010 19:42:22 -0400

ecc Wrote:
-------------------------------------------------------
> Jeff Wrote:
> --------------------------------------------------
> -----
> > If any enterprising individual wants to take a
> > stab at compiling a Pink Pogoplug uBoot, the
> file
> > in question is probably
> > 'board/Marvell/sheevaplug/kwbimage.cfg' I'm not
> > sure what the correct values would be.
>
> I ran into this issue "in reverse": I compiled my
> own uBoot with Alexander Holler's patches.
> Everything worked OK when chainloading, but when I
> flashed it, it was configuring the board for 256M
> instead of 128M. I didn't even notice it until my
> Linux userland started going crazy.
>
> It looks like there are just two registers to
> change in the kwbimage.cfg file:
>
> --- dramregs_pp128_A.txt 2009-08-14
> 17:42:42.000000000 -0400
> +++ dramregs_pp256_A.txt 2009-08-14
> 17:42:42.000000000 -0400
> @@ -3,7 +3,7 @@
> 0xFFD01404 0x37543000
> 0xFFD01408 0x22125451
> 0xFFD0140C 0x00000a33
> -0xFFD01410 0x0000000d
> +0xFFD01410 0x000000cc
> 0xFFD01414 0x00000000
> 0xFFD01418 0x00000000
> 0xFFD0141C 0x00000C52
> @@ -11,7 +11,7 @@
> 0xFFD01424 0x0000F17F
> 0xFFD01428 0x00085520
> 0xFFD0147C 0x00008552
> -0xFFD01504 0x07FFFFF1
> +0xFFD01504 0x0FFFFFF1
> 0xFFD01508 0x10000000
> 0xFFD0150C 0x00000000
> 0xFFD01514 0x00000000
>
>
> But since you can't test it without booting it
> from flash, I'd only advise it for someone who has
> a JTAG cable and isn't afraid to use it.

I have compiled a version of uBoot specific for the Pogoplug v2 (pink) that (hopefully) enables all 256MB of RAM. I built it using Jeff's instructions on how to build uBoot for the Dockstar with the following changes:

Instead of dramregs_pp128_A.txt I downloaded and used dramregs_pp256_A.txt from the root of pogoplug-u-boot-1.1.4.tgz on the Pogoplug opensource site.

I modified the doimage command in the mkDockstar.mtd0 script to use this dramregs_pp256_A.txt file as input:

  ./doimage -T nand -D 0x600000 -E 0x600000 -P 2048 -R dramregs_pp256_A.txt u-boot.bin u-boot.nand

These are the only changes that I believe are necessary in order to set the total memory to be 256MB instead of 128MB. The dramregs_pp256_A.txt file contains the exact same data as the dramregs_pp128_A.txt file with ecc's proposed changes.

Just as a disclaimer, I have not tested out this uBoot image myself as I don't have a JTAG setup to recover in case anything goes wrong. However, anyone else who has JTAG or is feeling brave, please feel free to test the attached uboot.mtd0.kwb image and let us know how it goes. I am happy to assist anyone who is interesting in testing this.

Re: uBoot with Pogoplug v2 Ping(Memory problem)

markweng — Sat, 04 Sep 2010 23:14:11 -0400

with Jeff's help it is easy

cd /tmp
wget http://jeff.doozan.com/debian/uboot/uboot.mtd0-pink.kwb
flash_erase /dev/mtd0 0 4 
nandwrite /dev/mtd0 uboot.mtd0-pink.kwb

Re: uBoot with Pogoplug v2 Ping(Memory problem)

karamazov1 — Sat, 04 Sep 2010 22:00:11 -0400

Hey Mark, to restore the RAM size, is it as easy as your previous post? Download the original pink uboot, flash_erase and nandwrite? Do I need a JTAG cable? I don't have one if so...

Thanks

Re: uBoot with Pogoplug v2 Ping(Memory problem)

markweng — Thu, 02 Sep 2010 08:11:24 -0400

Thank again..
Pogoplug Pink back to normal with 256M memory..
Mark

Re: uBoot with Pogoplug v2 Ping(Memory problem)

ecc — Thu, 02 Sep 2010 07:59:00 -0400

Jeff Wrote:
-------------------------------------------------------
> If any enterprising individual wants to take a
> stab at compiling a Pink Pogoplug uBoot, the file
> in question is probably
> 'board/Marvell/sheevaplug/kwbimage.cfg' I'm not
> sure what the correct values would be.

I ran into this issue "in reverse": I compiled my own uBoot with Alexander Holler's patches. Everything worked OK when chainloading, but when I flashed it, it was configuring the board for 256M instead of 128M. I didn't even notice it until my Linux userland started going crazy.

It looks like there are just two registers to change in the kwbimage.cfg file:

--- dramregs_pp128_A.txt	2009-08-14 17:42:42.000000000 -0400
+++ dramregs_pp256_A.txt	2009-08-14 17:42:42.000000000 -0400
@@ -3,7 +3,7 @@
 0xFFD01404 0x37543000
 0xFFD01408 0x22125451
 0xFFD0140C 0x00000a33
-0xFFD01410 0x0000000d
+0xFFD01410 0x000000cc
 0xFFD01414 0x00000000
 0xFFD01418 0x00000000
 0xFFD0141C 0x00000C52
@@ -11,7 +11,7 @@
 0xFFD01424 0x0000F17F
 0xFFD01428 0x00085520
 0xFFD0147C 0x00008552
-0xFFD01504 0x07FFFFF1
+0xFFD01504 0x0FFFFFF1
 0xFFD01508 0x10000000
 0xFFD0150C 0x00000000
 0xFFD01514 0x00000000

But since you can't test it without booting it from flash, I'd only advise it for someone who has a JTAG cable and isn't afraid to use it.

Re: uBoot with Pogoplug v2 Ping(Memory problem)

Jeff — Thu, 02 Sep 2010 00:13:58 -0400

Oops, my mistake! Here's a copy of the original Pogoplug Pink uBoot: http://jeff.doozan.com/debian/uboot/uboot.mtd0-pink.kwb

Re: uBoot with Pogoplug v2 Ping(Memory problem)

markweng — Wed, 01 Sep 2010 23:27:25 -0400

I did

wget http://jeff.doozan.com/debian/uboot/uboot-original-mtd0.kwb 
flash_erase /dev/mtd0 0 4 
nandwrite /dev/mtd0 uboot-original-mtd0.kwb

But "free" still shows

-bash-3.2# free
              total         used         free       shared      buffers
  Mem:       126064        21948       104116            0            0
 Swap:            0            0            0
Total:       126064        21948       104116

Is Dockstar and V2 has same original uboot?

Can someone who has pogoplug V2(Pink) post your original-mtd0 so I can give it a try.

Thanks for all your help

Mark

Re: uBoot with Pogoplug v2 Ping(Memory problem)

Jeff — Wed, 01 Sep 2010 21:16:09 -0400

Just follow the instructions at the bottom of http://jeff.doozan.com/debian/uboot/

Re: uBoot with Pogoplug v2 Ping(Memory problem)

markweng — Wed, 01 Sep 2010 20:29:14 -0400

Hi Jeff,
Thank you very much for your time...

Is it a way let Pogoplug V2(pink) go to back to original uBoot?
If so, can you show me how?

Mark

Re: uBoot with Pogoplug v2 Ping(Memory problem)

Jeff — Wed, 01 Sep 2010 18:57:08 -0400

Assuming Pogoplug still boots, those errors are nothing to worry about. uBoot is very verbose when reading bad NAND blocks.

The memory issue is probably the fault of the new uBoot, since there are a few definitions in uBoot that set up the RAM. Unfortunately, I do not have a Pink Pogoplug to test with, so there's not much I can do about it.

If any enterprising individual wants to take a stab at compiling a Pink Pogoplug uBoot, the file in question is probably 'board/Marvell/sheevaplug/kwbimage.cfg' I'm not sure what the correct values would be.

Or, if any generous individual wants to send me a Pink Pogoplug, I'd be happy to take a look at it.

-- Jeff

uBoot with Pogoplug v2 Ping(Memory problem)

markweng — Wed, 01 Sep 2010 16:00:53 -0400

Hi Jeff
Thanks for all your work...

Today I face something very strange..
The Pink has 256M memory,but today I installed new uBoot and the dockstar.debian-squeeze.sh

then I check the memory with "free" and "top" then shows only 128M memory

I wonder what I did wrong

free

debian:~# free
             total       used       free     shared    buffers     cached
Mem:        124080     111476      12604          0       8784      55460
-/+ buffers/cache:      47232      76848
Swap:       297196        476     296720
debian:~#

top

Mem: 21948K used, 104116K free, 0K shrd, 0K buff, 7972K cached
CPU:   0% usr   0% sys   0% nice 100% idle   0% io   0% irq   0% softirq
Load average: 0.00 0.00 0.00
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
  342   340 root     S    11156   9%   0% /usr/local/cloudengines/bin/hbplug
  315     1 root     S     3404   3%   0% udhcpc -b Pogoplug
  421   416 root     R     3404   3%   0% top
    1     0 root     S     3400   3%   0% init
  416   415 root     S     2676   2%   0% -bash
  341     1 root     S     2672   2%   0% -sh
  415   414 root     S     2580   2%   0% /usr/sbin/dropbear
  414     1 root     S     2100   2%   0% /usr/sbin/dropbear
  340     1 root     S     1696   1%   0% /usr/local/cloudengines/bin/hbwd /usr/local/cloudengines/bin/hbplug
   49     2 root     SW<      0   0%   0% [khubd]
  339     2 root     SW<      0   0%   0% [xce]
    2     0 root     SW<      0   0%   0% [kthreadd]
    3     2 root     SWN      0   0%   0% [ksoftirqd/0]
    4     2 root     SW<      0   0%   0% [events/0]
    5     2 root     SW<      0   0%   0% [khelper]
   46     2 root     SW<      0   0%   0% [kblockd/0]
   51     2 root     SW<      0   0%   0% [kmmcd]
   65     2 root     SW       0   0%   0% [crypto]
   66     2 root     SW       0   0%   0% [crypto_ret]
   71     2 root     SW       0   0%   0% [pdflush]
   72     2 root     SW       0   0%   0% [pdflush]
   73     2 root     SW<      0   0%   0% [kswapd0]
   74     2 root     SW<      0   0%   0% [aio/0]
  227     2 root     SW<      0   0%   0% [mtdblockd]
  228     2 root     SW<      0   0%   0% [nftld]
  262     2 root     SW<      0   0%   0% [kcryptd/0]

I put netconsole and here it shows

U-Boot 2010.06-00695-gbd23130-dirty (Aug 30 2010 - 23:04:56)
Marvell-Dockstar/Pogoplug by Jeff Doozan
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: .......  read_nand_cached: error reading nand off 0x89e200 size 8192 bytes
read_nand_cached: error reading nand off 0x8a0200 size 8192 bytes
read_nand_cached: error reading nand off 0x8a2200 size 8192 bytes
read_nand_cached: error reading nand off 0x8a4200 size 8192 bytes
read_nand_cached: error reading nand off 0x8a6200 size 8192 bytes
read_nand_cached: error reading nand off 0x8a8200 size 8192 bytes
read_nand_cached: error reading nand off 0x8aa200 size 8192 bytes
read_nand_cached: error reading nand off 0x8ac200 size 8192 bytes
read_nand_cached: error reading nand off 0x8ae200 size 8192 bytes
read_nand_cached: error reading nand off 0x8b0200 size 8192 bytes
read_nand_cached: error reading nand off 0x8b2200 size 8192 bytes
read_nand_cached: error reading nand off 0x8b4200 size 8192 bytes
read_nand_cached: error reading nand off 0x8b6200 size 8192 bytes
read_nand_cached: error reading nand off 0x8b8200 size 8192 bytes
read_nand_cached: error reading nand off 0x8ba200 size 8192 bytes
read_nand_cached: error reading nand off 0x8bc200 size 8192 bytes
read_nand_cached: error reading nand off 0x8be200 size 8192 bytes
read_nand_cached: error reading nand off 0x8c0200 size 8192 bytes
read_nand_cached: error reading nand off 0x8c2200 size 8192 bytes
read_nand_cached: error reading nand off 0x8c4200 size 8192 bytes
read_nand_cached: error reading nand off 0x8c6200 size 8192 bytes
read_nand_cached: error reading nand off 0x8c8200 size 8192 bytes
read_nand_cached: error reading nand off 0x8ca200 size 8192 bytes
read_nand_cached: error reading nand off 0x8cc200 size 8192 bytes
read_nand_cached: error reading nand off 0x8ce200 size 8192 bytes
read_nand_cached: error reading nand off 0x8d0200 size 8192 bytes
read_nand_cached: error reading nand off 0x8d2200 size 8192 bytes
read_nand_cached: error reading nand off 0x8d4200 size 8192 bytes
read_nand_cached: error reading nand off 0x8d6200 size 8192 bytes
read_nand_cached: error reading nand off 0x8d8200 size 8192 bytes
read_nand_cached: error reading nand off 0x8da200 size 8192 bytes
read_nand_cached: error reading nand off 0x8dc200 size 8192 bytes
read_nand_cached: error reading nand off 0x8de200 size 8192 bytes
read_nand_cached: error reading nand off 0x8e0200 size 8192 bytes
read_nand_cached: error reading nand off 0x8e2200 size 8192 bytes
read_nand_cached: error reading nand off 0x8e4200 size 8192 bytes
read_nand_cached: error reading nand off 0x8e6200 size 8192 bytes
read_nand_cached: error reading nand off 0x8e8200 size 8192 bytes
read_nand_cached: error reading nand off 0x8ea200 size 8192 bytes
read_nand_cached: error reading nand off 0x8ec200 size 8192 bytes
read_nand_cached: error reading nand off 0x8ee200 size 8192 bytes
read_nand_cached: error reading nand off 0x8f0200 size 8192 bytes
read_nand_cached: error reading nand off 0x8f2200 size 8192 bytes
read_nand_cached: error reading nand off 0x8f4200 size 8192 bytes
read_nand_cached: error reading nand off 0x8f6200 size 8192 bytes
read_nand_cached: error reading nand off 0x8f8200 size 8192 bytes
read_nand_cached: error reading nand off 0x8fa200 size 8192 bytes
read_nand_cached: error reading nand off 0x8fc200 size 8192 bytes
read_nand_cached: error reading nand off 0x8fe200 size 8192 bytes
read_nand_cached: error reading nand off 0x900200 size 8192 bytes
read_nand_cached: error reading nand off 0x902200 size 8192 bytes
read_nand_cached: error reading nand off 0x904200 size 8192 bytes
read_nand_cached: error reading nand off 0x906200 size 8192 bytes
read_nand_cached: error reading nand off 0x908200 size 8192 bytes
read_nand_cached: error reading nand off 0x90a200 size 8192 bytes
read_nand_cached: error reading nand off 0x90c200 size 8192 bytes
read_nand_cached: error reading nand off 0x90e200 size 8192 bytes
read_nand_cached: error reading nand off 0x910200 size 8192 bytes
read_nand_cached: error reading nand off 0x912200 size 8192 bytes
read_nand_cached: error reading nand off 0x914200 size 8192 bytes
read_nand_cached: error reading nand off 0x916200 size 8192 bytes
read_nand_cached: error reading nand off 0x918200 size 8192 bytes
read_nand_cached: error reading nand off 0x91a200 size 8192 bytes
read_nand_cached: error reading nand off 0x91c200 size 8192 bytes
read_nand_cached: error reading nand off 0x91e200 size 8192 bytes                                                                                          . done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...