configs: add nitrogen6sx_defconfig for Boundary Devices SoloX board
PATCH 1/1 configs: add nitrogen6sx_defconfig for Boundary Devices SoloX board
This board is using the exact same kernel and u-boot revision as the Nitrogen6x. They also share the same u-boot "autoboot" script.
The differences between the two configurations are:
- getty port is ttymxc0 instead of ttymxc1
- uImage load address is 0x80008000
- different device tree
http://boundarydevices.com/product/nit6_solox-imx6/
---
Hi all,
I didn't include this patch as part of the Freescale packages update as it is an addition. However this patch depends on the updates to be applied for graphics support and so on.
http://lists.busybox.net/pipermail/buildroot/2015-September/139278.html
I wish we could do an include of another defconfig, that'd simplify future config updates as it could look like:
include nitrogen6x_defconfig BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0" BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x80008000" BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6sx-nitrogen6sx"
That would also be very useful for all the Freescale sabre boards where every config is almost the same apart from uboot configuration or device tree name.
Regards,
Gary
--- configs/nitrogen6sx_defconfig | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 configs/nitrogen6sx_defconfig
configs/nitrogen6sx_defconfig new file +37 -0
@@ -0,0 +1,37 @@ +# architecture +BR2_arm=y +BR2_cortex_a9=y + +# system +BR2_TARGET_GENERIC_GETTY=y +BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0" +BR2_ROOTFS_POST_BUILD_SCRIPT="board/boundarydevices/nitrogen6x/post-build.sh" +BR2_PACKAGE_HOST_UBOOT_TOOLS=y + +# filesystem +BR2_TARGET_ROOTFS_EXT2=y +BR2_TARGET_ROOTFS_EXT2_2r1=y + +# Lock headers to match kernel +BR2_KERNEL_HEADERS_VERSION=y +BR2_DEFAULT_KERNEL_VERSION="3.14.28" +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_14=y + +# bootloader +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BOARDNAME="nitrogen6sx" +BR2_TARGET_UBOOT_FORMAT_IMX=y +BR2_TARGET_UBOOT_CUSTOM_TARBALL=y +# Last version of branch boundary-v2015.07 +BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="http://github.com/boundarydevices/u-boot-imx6/tarball/5115a9e/u-boot-5115a9e.tar.gz" + +# kernel +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_TARBALL=y +# Last version of branch boundary-imx_3.14.28_1.0.0_ga +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="https://github.com/boundarydevices/linux-imx6/tarball/3417c66/linux-imx6-3417c66.tar.gz" +BR2_LINUX_KERNEL_DEFCONFIG="nitrogen6x" +BR2_LINUX_KERNEL_INSTALL_TARGET=y +BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x80008000" +BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6sx-nitrogen6sx"
Signature · 1 line
2.5.1
PATCH 1/1 configs: add nitrogen6sx_defconfig for Boundary Devices SoloX board
Gary,
Quoted 6 lines · Gary Bisson
This board is using the exact same kernel and u-boot revision as the Nitrogen6x. They also share the same u-boot "autoboot" script.
The differences between the two configurations are:
- getty port is ttymxc0 instead of ttymxc1
- uImage load address is0x80008000
Do you have a reason to keep using uImage instead of using zImage? uImage are now a bit deprecated on ARM, and zImage is the modern way of booting the kernel even from U-Boot (using the bootz command).
Quoted 4 lines
I didn't include this patch as part of the Freescale packages update as it is an addition. However this patch depends on the updates to be applied for graphics support and so on.
http://lists.busybox.net/pipermail/buildroot/2015-September/139278.html
No problem, I applied them already.
Quoted 11 lines
I wish we could do an include of another defconfig, that'd simplify future config updates as it could look like:
include
nitrogen6x_defconfigBR2_TARGET_GENERIC_GETTY_PORT="ttymxc0" BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x80008000" BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6sx-nitrogen6sx"That would also be very useful for all the Freescale sabre boards where every config is almost the same apart from uboot configuration or device tree name.
Indeed. We don't have a solution for this in the upstream Buildroot. However, people in this situation are encouraged to use the concept of "defconfig" fragments, which can be merged together to give the final defconfig.
I've applied your patch.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 configs: add nitrogen6sx_defconfig for Boundary Devices SoloX board
Hi Thomas,
Quoted 6 lines · Thomas Petazzoni
Gary,
Quoted 3 lines · Gary Bisson
This board is using the exact same kernel and u-boot revision as the Nitrogen6x. They also share the same u-boot "autoboot" script.
Quoted 7 lines
Quoted 3 lines
The differences between the two configurations are:
- getty port is ttymxc0 instead of ttymxc1
- uImage load address is0x80008000Do you have a reason to keep using uImage instead of using zImage? uImage are now a bit deprecated on ARM, and zImage is the modern way of booting the kernel even from U-Boot (using the bootz command).
Legacy I guess. I should look into it but the main advantage I see of bootm/uImage is the CRC check. What is the story behind the switch to bootz?
Quoted 15 lines
Quoted 4 lines
I didn't include this patch as part of the Freescale packages update as it is an addition. However this patch depends on the updates to be applied for graphics support and so on.
http://lists.busybox.net/pipermail/buildroot/2015-September/139278.htmlNo problem, I applied them already.
Quoted 8 lines
I wish we could do an include of another defconfig, that'd simplify future config updates as it could look like:
include
nitrogen6x_defconfigBR2_TARGET_GENERIC_GETTY_PORT="ttymxc0" BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x80008000" BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6sx-nitrogen6sx"
Quoted 8 lines
Quoted 3 lines
That would also be very useful for all the Freescale sabre boards where every config is almost the same apart from uboot configuration or device tree name.
Indeed. We don't have a solution for this in the upstream Buildroot. However, people in this situation are encouraged to use the concept of "defconfig" fragments, which can be merged together to give the final defconfig.
Ok, I'll into the fragments concept.
Thanks,
Gary
PATCH 1/1 configs: add nitrogen6sx_defconfig for Boundary Devices SoloX board
Hi Gary,
Quoted 10 lines · Gary Bisson
Quoted 8 lines · Thomas Petazzoni
Quoted 6 lines · Gary Bisson
This board is using the exact same kernel and u-boot revision as the Nitrogen6x. They also share the same u-boot "autoboot" script.
The differences between the two configurations are:
- getty port is ttymxc0 instead of ttymxc1
- uImage load address is0x80008000
Quoted 7 lines
Quoted 3 lines
Do you have a reason to keep using uImage instead of using zImage? uImage are now a bit deprecated on ARM, and zImage is the modern way of booting the kernel even from U-Boot (using the bootz command).
Legacy I guess. I should look into it but the main advantage I see of bootm/uImage is the CRC check. What is the story behind the switch to bootz?
Multiplatform. See [1], for example.
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2011-September/066289.html
baruch
Signature · 3 lines
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -PATCH 1/1 configs: add nitrogen6sx_defconfig for Boundary Devices SoloX board
Hi Baruch,
Quoted 17 lines · Baruch Siach
Hi Gary,
Quoted 14 lines · Gary Bisson
Quoted 11 lines · Thomas Petazzoni
Quoted 6 lines · Gary Bisson
This board is using the exact same kernel and u-boot revision as the Nitrogen6x. They also share the same u-boot "autoboot" script.
The differences between the two configurations are:
- getty port is ttymxc0 instead of ttymxc1
- uImage load address is0x80008000Do you have a reason to keep using uImage instead of using zImage? uImage are now a bit deprecated on ARM, and zImage is the modern way of booting the kernel even from U-Boot (using the bootz command).
Quoted 8 lines
Quoted 3 lines
Legacy I guess. I should look into it but the main advantage I see of bootm/uImage is the CRC check. What is the story behind the switch to bootz?
Multiplatform. See [1], for example.
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2011-September/066289.html
Thanks for the link. So indeed the mx6qdl vs mx6sx is the perfect example to show the need of bootz.
Thanks,
Gary