From: bifferos <bifferos@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bifferboard: new board
Date: Mon, 12 Mar 2012 01:23:35 +0000 [thread overview]
Message-ID: <4F5D5017.2080908@yahoo.co.uk> (raw)
In-Reply-To: <1330788921-27127-1-git-send-email-arnout@mind.be>
On 03/03/2012 03:35 PM, Arnout Vandecappelle (Essensium/Mind) wrote:
> From: "Arnout Vandecappelle (Essensium/Mind)"<arnout@mind.be>
>
> Includes linux and busybox config (to make it fit in 1MB).
>
> Based on
> https://sites.google.com/site/bifferboard/Home/boards-with-1mb-flash/buildroot
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind)<arnout@mind.be>
<snip>
I noticed the bzImage is slightly larger than it should be, at 978064
bytes. It actually has only 0xf0000 - 0x2000 bytes of space available
for the firmware, since some of the space is taken up by the bootloader
and a config block. This leaves only 974848, so some applets (not very
many) need to be removed for it to work on 1MB devices. Perhaps the
better way is to just start with a very minimal configuration which is
guaranteed to fit. Anyhow, I tested out the patch with a version of the
hardware which has 8MB flash. Unfortunately it doesn't work:
Write protecting the kernel text: 1048k
Write protecting the kernel read-only data: 164k
init[1]: segfault at 0 ip (null) sp bf95bf40 error 4 in
busybox[8048000+7c000]
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 3.1.4-biff #5
Call Trace:
[<c02035a1>] ? 0xc02035a1
[<c01164c4>] ? 0xc01164c4
[<c011698b>] ? 0xc011698b
[<c011e52d>] ? 0xc011e52d
[<c0101a33>] ? 0xc0101a33
[<c0156dba>] ? 0xc0156dba
[<c010d72f>] ? 0xc010d72f
[<c014c76d>] ? 0xc014c76d
[<c014ce59>] ? 0xc014ce59
[<c014e529>] ? 0xc014e529
[<c014cea7>] ? 0xc014cea7
[<c010d591>] ? 0xc010d591
[<c0204674>] ? 0xc0204674
[<c010d591>] ? 0xc010d591
The kernel panic is odd. I'll try to get a better call stack and
experiment with other kernel versions if I have time, although I've been
really busy lately, hence the delay in testing out your patch.
best regards,
Biff.
next prev parent reply other threads:[~2012-03-12 1:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 0:52 [Buildroot] Kernel and buildroot in 1MB bifferos
2012-03-01 7:50 ` Thomas Petazzoni
2012-03-01 11:13 ` bifferos
2012-03-03 15:29 ` Arnout Vandecappelle
2012-03-03 15:35 ` [Buildroot] [PATCH] bifferboard: new board Arnout Vandecappelle
2012-03-05 9:49 ` Thomas Petazzoni
2012-03-06 7:00 ` Arnout Vandecappelle
2012-03-11 10:58 ` [Buildroot] [PATCH v2] " Arnout Vandecappelle
2012-03-12 14:46 ` bifferos
2012-03-12 1:23 ` bifferos [this message]
2012-03-16 1:58 ` [Buildroot] Debugging /sbin/init startup issues bifferos
2012-03-17 4:03 ` Charles Krinke
2012-03-17 14:10 ` bifferos
2012-03-18 13:50 ` [Buildroot] [PATCH] bifferboard: new board Arnout Vandecappelle
2012-03-18 16:12 ` bifferos
2012-03-18 17:13 ` Arnout Vandecappelle
2012-03-18 19:51 ` Alexandre Pereira da Silva
2012-03-18 20:54 ` bifferos
2012-03-18 21:40 ` Arnout Vandecappelle
2012-03-19 12:36 ` bifferos
[not found] ` <4F525794.5010406@yahoo.co.uk>
2012-03-03 17:00 ` [Buildroot] Kernel and buildroot in 1MB Arnout Vandecappelle
2012-03-01 12:18 ` Peter Korsgaard
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=4F5D5017.2080908@yahoo.co.uk \
--to=bifferos@yahoo.co.uk \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox