From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] freescale/imx6-sabresd: document how to create a bootable SD
Date: Thu, 14 Aug 2014 14:42:48 +0200 [thread overview]
Message-ID: <53ECAEC8.8030007@lucaceresoli.net> (raw)
In-Reply-To: <53EC8982.1000809@freescale.com>
Dear Vincent,
Vincent Stehl? wrote:
> On 08/14/2014 10:35 AM, Luca Ceresoli wrote:
>> Document how to create a bootable SD card for the two supported SABRESD cards:
>> i.MX6Q and i.MX6DL.
>
> Hi Luca,
>
> Thanks for the script and documentation!
>
> A few comments below:
>
[...]
>> --- /dev/null
>> +++ b/board/freescale/imx6sabresd/create-boot-sd.sh
>> @@ -0,0 +1,85 @@
>> +#!/bin/sh
>> +
>> +set -u
>> +set -e
>> +
>> +PROGNAME=$(basename $0)
>> +
>> +usage()
>> +{
>> + echo "Create an SD card that boots on an i.MX6DL SABRESD board."
>> + echo "It is supposed to work also for the i.MX6Q SABRESD board, but"
>> + echo "it this is not tested."
>
> It is now, and the resulting SD card boots fine :)
>
> I needed to do just one change, though: the partitions names (see below).
>
>> + echo
>> + echo "Note: all data on the the card will be completely deleted!"
>> + echo "Use with care!"
>> + echo "Superuser permissions may be required to write to the device."
>> + echo
>> + echo "Usage: ${PROGNAME} <sd_block_device>"
>> + echo "Arguments:"
>> + echo " <sd_block_device> The device to be written to"
>> + echo
>> + echo "Example: ${PROGNAME} /dev/mmcblk0"
>> + echo
>> +}
>> +
>> +if [ $# -ne 1 ]; then
>> + usage
>> + exit 1
>> +fi
>> +
>> +if [ $(id -u) -ne 0 ]; then
>> + echo "${PROGNAME} must be run as root"
>> + exit 1
>> +fi
>> +
>> +DEV=${1}
>> +PART1=${DEV}p1
>> +PART2=${DEV}p2
>
> This naming is not fully true: with my USB SD card reader for example I
> have /dev/sde1, /dev/sde2.
>
> That makes the mkfs step (and the script) fail for me. If I change just
> this naming, it works fine.
Yup, right.
[...]
>> +# ext2 partition: root filesystem
>> +mkfs.ext2 ${PART2}
>> +mount ${PART2} ${TMPDIR}
>> +tar -C ${TMPDIR}/ -xf output/images/rootfs.tar
>> +sync
>> +umount ${TMPDIR}
>
> Maybe you want to mention somewhere that your script uses the rootfs.tar
> and not the rootfs.ext2 as of now?
>
> And if one day you support both the rootfs.ext2 and the rootfs.tar, I
> suggest you use the rootfs.ext2 in priority when both are generated (and
> maybe a resize2fs step). This way, you will benefit from the tune2fs
> done by buildroot.
I'll have a look at this as soon as I can.
>
>> +
>> +# Cleanup
>> +rmdir ${TMPDIR}
>> +sync
>> +echo Done
>> diff --git a/board/freescale/imx6sabresd/readme.txt b/board/freescale/imx6sabresd/readme.txt
>> new file mode 100644
>> index 0000000..c93347f
>> --- /dev/null
>> +++ b/board/freescale/imx6sabresd/readme.txt
>> @@ -0,0 +1,66 @@
>> +*******************************************************
>> +Freescale i.MX6Q and i.MX6DL SABRESD development boards
>> +*******************************************************
>> +
>> +This file documents the Buildroot support for the Freescale SABRE Board for
>> +Smart Devices Based on the i.MX 6 Series (SABRESD).
>> +
>> +Read the SABRESD Quick Start Guide for an introduction to the board:
>> +http://cache.freescale.com/files/32bit/doc/quick_start_guide/SABRESDB_IMX6_QSG.pdf
>> +
>> +Build
>> +=====
>> +
>> +First, configure Buildroot for your SABRESD board.
>> +For i.MX6Q:
>> +
>> + make freescale_imx6sabresd_defconfig
>> +
>> +For i.MX6DL:
>> +
>> + make freescale_imx6dlsabresd_defconfig
>> +
>> +Build all components:
>> +
>> + make
>> +
>> +You will find in ./output/images/ the following files:
>> + - imx6dl-sabresd.dtb or imx6q-sabresd.dtb
>> + - rootfs.ext2
>> + - rootfs.tar
>> + - u-boot.imx
>> + - uImage
>> +
>> +Create a bootable SD card
>> +=========================
>> +
>> +To determine the device associated to the SD card have a look in the
>> +/proc/partitions file:
>> +
>> + cat /proc/partitions
>> +
>> +Run the following script as root on your SD card. This will partition the card
>> +and copy the bootloader, kernel, DTBs and root filesystem as needed.
>> +
>> +*** WARNING! The script will destroy all the card content. Use with care! ***
>> +
>> + ./board/freescale/imx6sabresd/create-boot-sd.sh <your-sd-device>
>> +
>> +Boot the SABRESD board
>> +======================
>> +
>> +To boot your newly created system (refer to the SABRESD Quick Start Guide for
>> +guidance):
>> +- insert the SD card in the SD3 slot of the board;
>> +- locate the BOOT dip switches (SW6), set dips 2 and 7 to ON, all others to OFF;
>> +- connect a Micro USB cable to Debug Port and connect using a terminal emulator;
>
> You might want to mention 115200n8.
I just sent a v2 patchset with this change as well as a fix to the
partition naming, since it may take some time before I can test the
ext2 change.
--
Luca
next prev parent reply other threads:[~2014-08-14 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 8:35 [Buildroot] [PATCH 1/2] configs/freescale_imx6dlsabresd: add defconfig for iMX6DL SabreSD Luca Ceresoli
2014-08-14 8:35 ` [Buildroot] [PATCH 2/2] freescale/imx6-sabresd: document how to create a bootable SD Luca Ceresoli
2014-08-14 10:03 ` Vincent Stehlé
2014-08-14 12:42 ` Luca Ceresoli [this message]
2014-08-14 9:34 ` [Buildroot] [PATCH 1/2] configs/freescale_imx6dlsabresd: add defconfig for iMX6DL SabreSD Vincent Stehlé
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=53ECAEC8.8030007@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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