From: Johan Sagaert <sagaert.johan@proximus.be>
To: buildroot@busybox.net
Subject: [Buildroot] problem booting from ext2 µsd card
Date: Mon, 21 Sep 2015 01:59:49 +0200 [thread overview]
Message-ID: <55FF4875.9030403@proximus.be> (raw)
In-Reply-To: <CA+BsyQ7LQofzLgZKP_Zm4Ykbd+MOfWNw15qPRYAxXjURURuKVg@mail.gmail.com>
Brendan Heading schreef op 17/09/2015 om 13:20:
>> Then used cfdisk to create a single partition type 83 and maximum size as
>> suggested by cfdisk.
> What's the maximum size suggested by cfdisk ?
>
> Your script seems to be manually creating the ext2 filesystem and
> copying the files to it. buildroot can actually generate the ext2/3/4
> image for you, so you won't need the above script; you'd just need to
> copy the image directly to the sd (using dd).
>
>> The only thing i can think of is that my debian host is messing up the
>> partition.
>> and also tried cfdisk /z
> Can you mount the partition on your debian host ? If it works there it
> should also work on your target.
>
> I see the output of mke2fs you sent. It appears to be creating a 2GB
> partition which is the maximum size of an ext2 filesystem, so that
> looks right.
>
> My best suggestion is to bring your Linux system up without mounting
> the SD card (ie use an initramfs or similar) and then see if you can
> mount it manually and dump out the partition tables from there.
>
Brendan ;
The problem was caused by an overloaded power controller on the boards,
generating voltage dips on the 3V3 line
enough to corrupt sd-card communication but not enough to trigger a
poweron reset ...
It's not always software causing trouble....
Regards , Johan
prev parent reply other threads:[~2015-09-20 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 23:56 [Buildroot] problem booting from ext2 µsd card Johan Sagaert
2015-09-17 0:27 ` Brendan Heading
2015-09-17 8:03 ` Johan Sagaert
2015-09-17 11:20 ` Brendan Heading
2015-09-20 23:59 ` Johan Sagaert [this message]
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=55FF4875.9030403@proximus.be \
--to=sagaert.johan@proximus.be \
--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