From: Stutz Sven <stutzsven@gmx.de>
To: barebox@lists.infradead.org
Subject: AT91SAM9263-EK
Date: Fri, 13 Jul 2012 11:33:57 +0200 [thread overview]
Message-ID: <4FFFEB85.3060003@gmx.de> (raw)
[-- 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
next reply other threads:[~2012-07-13 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 9:33 Stutz Sven [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-13 9:35 AT91SAM9263-EK Stutz Sven
2012-07-16 9:10 ` AT91SAM9263-EK Sascha Hauer
[not found] <50065575.4090808@web.de>
2012-07-18 9:44 ` AT91SAM9263-EK Stutz Sven
2012-07-18 15:06 ` AT91SAM9263-EK Sascha Hauer
2012-07-18 16:38 ` AT91SAM9263-EK Jean-Christophe PLAGNIOL-VILLARD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FFFEB85.3060003@gmx.de \
--to=stutzsven@gmx.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.