AT91SAM9263-EK

AT91SAM9263-EK

[Stutz Sven]

Hello Sascha,

thanks a lot for your help.

When I completely switch off the ecc, Barebox is loading the Linux kernel.
But I guess that the ecc is necessary especially for NAND-Flash devices.


The AT91SAM9263 controller has a ecc unit implemented. There are three 
registers and the error calculation is done automatically, only the 
error correction must be done in software.
Or is it better to you use the software ecc and I should try to fix the 
software problem?
Can you give me some hints to fix this problem?

Btw. I have found the description table for the NAND devices. But what 
would happen if I change the connections between the controller and the 
NAND-Flash, where are those port description stored or the timings to 
access the data bus?


best regards Sven



_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: AT91SAM9263-EK

[Sascha Hauer]

Hi Sven,

On Wed, Jul 18, 2012 at 11:44:29AM +0200, Stutz Sven wrote:
> 
> Hello Sascha,
> 
> thanks a lot for your help.
> 
> When I completely switch off the ecc, Barebox is loading the Linux kernel.
> But I guess that the ecc is necessary especially for NAND-Flash devices.

Indeed. You shouldn't use NAND without ecc.

> 
> 
> The AT91SAM9263 controller has a ecc unit implemented. There are
> three registers and the error calculation is done automatically,
> only the error correction must be done in software.
> Or is it better to you use the software ecc and I should try to fix
> the software problem?

If possible you should use hardware ecc. It may be though that it has
bugs that force you to use software ecc, but I'm not familiar with the
atmel hardware.

> Can you give me some hints to fix this problem?

Does it work in the kernel? If yes, try looking for differences. The
NAND layers are sufficiently similar.

> 
> Btw. I have found the description table for the NAND devices. But
> what would happen if I change the connections between the controller
> and the NAND-Flash, where are those port description stored or the
> timings to access the data bus?

I have no idea.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: AT91SAM9263-EK

[Jean-Christophe PLAGNIOL-VILLARD]

On 17:06 Wed 18 Jul     , Sascha Hauer wrote:
> Hi Sven,
> 
> On Wed, Jul 18, 2012 at 11:44:29AM +0200, Stutz Sven wrote:
> > 
> > Hello Sascha,
> > 
> > thanks a lot for your help.
> > 
> > When I completely switch off the ecc, Barebox is loading the Linux kernel.
> > But I guess that the ecc is necessary especially for NAND-Flash devices.
> 
> Indeed. You shouldn't use NAND without ecc.
> 
> > 
> > 
> > The AT91SAM9263 controller has a ecc unit implemented. There are
> > three registers and the error calculation is done automatically,
> > only the error correction must be done in software.
> > Or is it better to you use the software ecc and I should try to fix
> > the software problem?
> 
> If possible you should use hardware ecc. It may be though that it has
> bugs that force you to use software ecc, but I'm not familiar with the
> atmel hardware.
the hw ecc work on 9263 but we do not use it on the kernel
> 
> > Can you give me some hints to fix this problem?
> 
> Does it work in the kernel? If yes, try looking for differences. The
> NAND layers are sufficiently similar.
the drivers as the same on both barebox and linux
> 
> > 
> > Btw. I have found the description table for the NAND devices. But
> > what would happen if I change the connections between the controller
> > and the NAND-Flash, where are those port description stored or the
> > timings to access the data bus?
smc

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

AT91SAM9263-EK

[Stutz Sven]

[-- Attachment #1.1: Type: text/plain, Size: 2705 bytes --]

Hello everybody,

I am trying to learn and to play with the at91sam9263-ek (Rev. B) 
evalboard.

I was really successful building all parts (at91Bootstrap, Barebox, 
Linuximage) and when I upload all files via SAM-BA and I restart the 
device I get the prompt of barebox.

But nothing more
Everything is fine I can also switch on and off the on board leds but I 
cannot load/ start the kernel.

The addresses I use are:
         0x     0000 - 0x1 FFFF at91Bootstrap
         0x  2 0000 -  0x5 FFFF Barebox
         0x  6 0000 -  0x7 FFFF Bareboxenv
         0x  8 0000 -  47 FFFF kernel
         0x48 0000 -7c7 FFFF rootfs
     and rest is data ...

I have change the specific init.c file and boot file in the specific 
environment folder.
First I though the missing *.bb partitions can fix this problem. Then I 
modified the env/init file for that.  Apparently this placeholder "*" in 
this boot script (nand -a dev/nand0.* ) is not working correctly.
     addpart /dev/nand0 $nand_parts
     nand -a /dev/nand0.*

     nand -a dev/nand0.at91bootstrap
     nand -a dev/nand0.barebox
     nand -a dev/nand0.bareboxenv
     nand -a dev/nand0.kernel
     nand -a dev/nand0.rootfs

The second try was to change also this partition table in the specific 
init.c so that both match.
         devfs_add_partition("nand0", 0x00000, SZ_128K, 
DEVFS_PARTITION_FIXED, "at91bootstrap_raw");
         dev_add_bb_dev("at91bootstrap_raw", "at91bootstrap");
         devfs_add_partition("nand0", SZ_128K, SZ_256K, 
DEVFS_PARTITION_FIXED, "self_raw");
         dev_add_bb_dev("self_raw", "self0");
         devfs_add_partition("nand0", SZ_256K + SZ_128K, SZ_128K, 
DEVFS_PARTITION_FIXED, "env_raw");
         dev_add_bb_dev("env_raw", "env0");

But everything without success. It's a little bit strange because when I 
execute the command
     bootm -v /dev/nand0.kernel.bb
First I get the following output
         Barebox:/ bootm -v /dev/nand0.kernel.bb
             Image Name:     Linux-3.4.0
             OS:                      Linux
             Architecture:     ARM
             Type:                   Kernel Image
             Compression:    uncompressed
             Data Size:           2034784 Bytes = 1.9 MB
             Load Address:    20008000
             Entry Point:        20008000
         err -74
         loading os image failed with Out of memory

and if I try again the same command
         Barebox:/ bootm -v /dev/nand0.kernel.bb
         err -74
         Unknown OS filetype (try -f)

also if I try to memcpy or uimage I always get this err 74.

What is this Error 74 (-- Reset level 3)?
Why Out of memory?


Kind regards

Sven


	
Stutz Sven <stutzsven@gmx.de <mailto:stutzsven@gmx.de>>


[-- Attachment #1.2: Type: text/html, Size: 4642 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: AT91SAM9263-EK

[Sascha Hauer]

On Fri, Jul 13, 2012 at 11:35:39AM +0200, Stutz Sven wrote:
> Hello everybody,
> 
> 
> But everything without success. It's a little bit strange because
> when I execute the command
>     bootm -v /dev/nand0.kernel.bb
> First I get the following output
>         Barebox:/ bootm -v /dev/nand0.kernel.bb
>             Image Name:     Linux-3.4.0
>             OS:                      Linux
>             Architecture:     ARM
>             Type:                   Kernel Image
>             Compression:    uncompressed
>             Data Size:           2034784 Bytes = 1.9 MB
>             Load Address:    20008000
>             Entry Point:        20008000
>         err -74
>         loading os image failed with Out of memory
> 
> and if I try again the same command
>         Barebox:/ bootm -v /dev/nand0.kernel.bb
>         err -74
>         Unknown OS filetype (try -f)
> 
> also if I try to memcpy or uimage I always get this err 74.
> 
> What is this Error 74 (-- Reset level 3)?

-74 is EBADMSG, see include/asm-generic/errno.h. The nand driver throws
this when it can't read due to ecc errors. Something seems wrong with
your nand driver. I remember Jean-Christophe mentioned that the atmel
nand support is currently broken. Could you please try if either:

- barebox v2012.07.0 or
- current master

works for you?

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

AT91SAM9263-EK

[Stutz Sven]

[-- Attachment #1: Type: text/plain, Size: 2644 bytes --]

Hello everybody,

I am trying to learn and to play with the at91sam9263-ek (Rev. B) evalboard.

I was really successful building all parts (at91Bootstrap, Barebox, 
Linuximage) and when I upload all files via SAM-BA and I restart the 
device I get the prompt of barebox.

But nothing more
Everything is fine I can also switch on and off the on board leds but I 
cannot load/ start the kernel.

The addresses I use are:
         0x     0000 - 0x1 FFFF at91Bootstrap
         0x  2 0000 -  0x5 FFFF Barebox
         0x  6 0000 -  0x7 FFFF Bareboxenv
         0x  8 0000 -  47 FFFF kernel
         0x48 0000 -7c7 FFFF rootfs
     and rest is data ...

I have change the specific init.c file and boot file in the specific 
environment folder.
First I though the missing *.bb partitions can fix this problem. Then I 
modified the env/init file for that.  Apparently this placeholder "*" in 
this boot script (nand -a dev/nand0.* ) is not working correctly.
     addpart /dev/nand0 $nand_parts
     nand -a /dev/nand0.*

     nand -a dev/nand0.at91bootstrap
     nand -a dev/nand0.barebox
     nand -a dev/nand0.bareboxenv
     nand -a dev/nand0.kernel
     nand -a dev/nand0.rootfs

The second try was to change also this partition table in the specific 
init.c so that both match.
         devfs_add_partition("nand0", 0x00000, SZ_128K, 
DEVFS_PARTITION_FIXED, "at91bootstrap_raw");
         dev_add_bb_dev("at91bootstrap_raw", "at91bootstrap");
         devfs_add_partition("nand0", SZ_128K, SZ_256K, 
DEVFS_PARTITION_FIXED, "self_raw");
         dev_add_bb_dev("self_raw", "self0");
         devfs_add_partition("nand0", SZ_256K + SZ_128K, SZ_128K, 
DEVFS_PARTITION_FIXED, "env_raw");
         dev_add_bb_dev("env_raw", "env0");

But everything without success. It's a little bit strange because when I 
execute the command
     bootm -v /dev/nand0.kernel.bb
First I get the following output
         Barebox:/ bootm -v /dev/nand0.kernel.bb
             Image Name:     Linux-3.4.0
             OS:                      Linux
             Architecture:     ARM
             Type:                   Kernel Image
             Compression:    uncompressed
             Data Size:           2034784 Bytes = 1.9 MB
             Load Address:    20008000
             Entry Point:        20008000
         err -74
         loading os image failed with Out of memory

and if I try again the same command
         Barebox:/ bootm -v /dev/nand0.kernel.bb
         err -74
         Unknown OS filetype (try -f)

also if I try to memcpy or uimage I always get this err 74.

What is this Error 74 (-- Reset level 3)?
Why Out of memory?


Kind regards

Sven


[-- Attachment #2: stutzsven.vcf --]
[-- Type: text/x-vcard, Size: 135 bytes --]

begin:vcard
fn:Stutz Sven
n:Sven;Stutz
email;internet:stutzsven@gmx.de
tel;cell:0160771169
x-mozilla-html:FALSE
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox