From: Sebastien Van Cauwenberghe <svancau@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add support for Digilent Zybo (Xilinx Zynq-7000)
Date: Mon, 27 Jun 2016 12:09:16 +0200 [thread overview]
Message-ID: <f38581f1-c8ca-d8ac-0630-065bea29dc01@gmail.com> (raw)
In-Reply-To: <526113c1-b1c6-f391-4c9f-1e84b4f2d6d1@gmail.com>
Hi Thomas, list,
I have some questions regarding the patch and how to make it more fit,
you'll find them below.
On 06/12/2016 10:12 PM, Thomas Petazzoni wrote:
>> +
>> +1) make zynq_zybo_defconfig
>> +2) make
>> +3) copy files BOOT.BIN, u-boot-dtb.img, rootfs.cpio.uboot,
>> + uImage, zynq-zybo.dtb into your SD card
>
> Please use genimage to generate a ready-to-use SD card image. You can
> check many of the other board configurations in Buildroot that are
> doing this.
>
> Also, why do you use an initramfs for the rootfs rather than the more
> traditional ext4 partition next to the FAT partition? This would be the
> preferred method for the defconfig in Buildroot.
>
I will go to ext4 but (as a beginner), I'll first investigate what is wrong with ext4
not booting (maybe mmc/ext4 compiled as a module).
In this case, I guess a board specific defconfig should be used ?
>> +Resulting system
>> +----------------
>> +A FAT32 partition should be created at the beginning of the SD Card
>> +and the following files should be installed:
>> + /BOOT.BIN
>> + /zynq-zybo.dtb
>> + /uImage
>> + /rootfs-cpio.uboot
>> + /u-boot-dtb.img
>> +
>> +
>> +All needed files can be taken from output/images/
>> +
>> +BOOT.BIN, uImage and u-boot-dtb.img are direct copies of the same files
>> +available on output/images/
>
> All of this can be simplified once you generate a complete SD card
> image with genimage.
>
Done genimage is really easier to prepare sd afterwards :)
>> +There is a patch attached that redefines the U-Boot's environment
>> +to work with Buildroot out-of-the-box.
>
> Why do you patch the U-Boot built-in environment instead of providing
> an uEnv.txt file?
>
I saw loading uEnv.txt was a board specific stuff and should be subject to patch anyways
so I added the environment in there so I can use the board without sd card but with
the flash memory.
>> +The serial console is accessible on the host on /dev/ttyUSB1 at 115200 bauds.
>
> Saying it's on /dev/ttyUSB1 on the host is wrong. It might be on your
> machine, but it might be on ttyUSB0 on mine, or on ttyUSB2. There is no
> point in giving this information, since you don't know.
>
Wrong phrasing, USB connection exposes two USB-to-serial interfaces (one for JTAG and one for UART), to get the console you need
to use the second one. I'll correct this explanation.
>> diff --git a/configs/zynq_zybo_defconfig b/configs/zynq_zybo_defconfig
>> new file mode 100644
>> index 0000000..e2c8841
>> --- /dev/null
>> +++ b/configs/zynq_zybo_defconfig
>> @@ -0,0 +1,25 @@
>> +BR2_arm=y
>> +BR2_cortex_a9=y
>> +BR2_ARM_ENABLE_NEON=y
>> +# BR2_COMPILER_PARANOID_UNSAFE_PATH is not set
>
> Please leave this option to the default.
>
>> +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_6=y
>> +BR2_BINUTILS_VERSION_2_26_X=y
>
> Please leave this to the default.
>
>> +BR2_GCC_VERSION_5_X=y
>
> Ditto.
>
>> +BR2_TARGET_GENERIC_GETTY_PORT="ttyPS0"
>> +BR2_LINUX_KERNEL=y
>
> Please use a fixed kernel version.
>
You mean, not "Use the latest kernel" option but "Specific version" and provide a version number ?
>> +BR2_LINUX_KERNEL_DEFCONFIG="multi_v7"
>> +BR2_LINUX_KERNEL_UIMAGE=y
>> +BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x8000"
>
> Can you try to use zImage instead, which is now the standard format on
> ARM?
>
Apparently the uImage is all I can use easily with the Zynq, maybe with another
defconfig in U-boot for this board, I'll be able to use zImages ?
>> +BR2_LINUX_KERNEL_DTS_SUPPORT=y
>> +BR2_LINUX_KERNEL_INTREE_DTS_NAME="zynq-zybo"
>> +BR2_TARGET_ROOTFS_CPIO=y
>> +BR2_TARGET_ROOTFS_CPIO_GZIP=y
>> +BR2_TARGET_ROOTFS_CPIO_UIMAGE=y
>
> As suggested above, what about using an ext4 filesystem instead?
>
>> +BR2_TARGET_UBOOT=y
>
> Please used a fixed version of U-Boot.
>
>> +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
>> +BR2_TARGET_UBOOT_PATCH="$(TOPDIR)/board/digilent/zybo/uboot"
>> +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="zynq_zybo"
>> +BR2_TARGET_UBOOT_NEEDS_DTC=y
>> +BR2_TARGET_UBOOT_FORMAT_DTB_IMG=y
>> +BR2_TARGET_UBOOT_SPL=y
>> +BR2_TARGET_UBOOT_ZYNQ_IMAGE=y
>
> Could you rework your patch according to the above suggestions? With
> those suggestions taken into account, your patch could be merged in
> Buildroot.
It's ongoing, thanks for your time ;)
S?bastien
next parent reply other threads:[~2016-06-27 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <526113c1-b1c6-f391-4c9f-1e84b4f2d6d1@gmail.com>
2016-06-27 10:09 ` Sebastien Van Cauwenberghe [this message]
2016-06-27 11:39 ` [Buildroot] [PATCH] Add support for Digilent Zybo (Xilinx Zynq-7000) Thomas Petazzoni
2016-06-27 15:29 ` Sebastien Van Cauwenberghe
2016-05-22 15:50 Sebastien Van Cauwenberghe
2016-06-12 20:12 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2016-05-22 15:43 Sebastien Van Cauwenberghe
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=f38581f1-c8ca-d8ac-0630-065bea29dc01@gmail.com \
--to=svancau@gmail.com \
--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