[3rdparty,4/5] ccimx6ul: Add machine configuration for ConnectCore 6UL SOM

Submitted by Gonzalez, Alex on Nov. 6, 2018, 3:08 p.m. | Patch ID: 156124

Details

Message ID 1541516922-22117-5-git-send-email-alex.gonzalez@digi.com
State Changes Requested, archived
Delegated to: Otavio Salvador
Headers show

Commit Message

Gonzalez, Alex Nov. 6, 2018, 3:08 p.m.
This patch provides machine configuration for the ConnectCore 6UL
System-On-Module with the following hardware specification:

* Based on a NXP i.MX6UL SoC
* Industrial temperature ranges (-40ºC to +85ºC)
* Up to 1GB DDR3 memory
* Up to 2GB NAND flash
* Dual Ethernet
* On module 802.11 WiFi and Bluetooth 4.2 (QCA6564)
* On module NXP Kinetis KL03
* On module Microchip ATECC508A crypto element

More details about the SOM can be found at:
https://www.digi.com/products/embedded-systems/system-on-modules/connectcore-for-i-mx6ul

Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
---
 conf/machine/include/ccimx6ul.inc | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 conf/machine/include/ccimx6ul.inc

Patch hide | download patch | download mbox

diff --git a/conf/machine/include/ccimx6ul.inc b/conf/machine/include/ccimx6ul.inc
new file mode 100644
index 000000000000..f79af8f687b4
--- /dev/null
+++ b/conf/machine/include/ccimx6ul.inc
@@ -0,0 +1,34 @@ 
+#@TYPE: Machine
+#@NAME: ConnectCore 6UL System-On-Module.
+#@DESCRIPTION: Machine configuration for Digi's ConnectCore 6UL System-On-Module.
+
+MACHINEOVERRIDES =. "mx6:mx6ul:ccimx6ul:use-mainline-bsp:"
+
+include conf/machine/include/imx-base.inc
+include conf/machine/include/tune-cortexa7.inc
+
+PREFERRED_PROVIDER_virtual/bootloader = "u-boot-digi"
+PREFERRED_PROVIDER_u-boot = "u-boot-digi"
+PREFERRED_RPROVIDER_u-boot-fw-utils = "u-boot-fslc-fw-utils"
+
+UBOOT_BOOTSCRIPT = "boot.scr"
+
+UBOOT_CONFIG ??= "ccimx6ulstarter1GB ccimx6ulstarter"
+UBOOT_CONFIG[ccimx6ulstarter1GB] = "ccimx6ulstarter1GB_defconfig"
+UBOOT_CONFIG[ccimx6ulstarter] = "ccimx6ulstarter_defconfig"
+
+MACHINE_EXTRA_RDEPENDS += " \
+    mtd-utils-ubifs \
+    u-boot-fw-utils \
+"
+# mkfs.ubifs parameters for boot partition (the one holding kernel and device tree files)
+# Max LEB count (-c 255) calculated for a partition of up to 32 MiB considering 128 KiB erase-block size.
+MKUBIFS_BOOT_ARGS ?= "-m 2048 -e 126976 -c 255"
+
+# mkfs.ubifs parameters for rootfs partition
+# Max LEB count (-c 8191) calculated for a partition of up to 1 GiB considering 128 KiB erase-block size.
+MKUBIFS_ARGS ?= "-m 2048 -e 126976 -c 8191"
+
+IMAGE_CLASSES += "image_types_digi"
+# Overwrite the defaults in imx-base not to include wic images
+IMAGE_FSTYPES = "tar.bz2 ubifs boot.ubifs"

Comments

Otavio Salvador Nov. 10, 2018, 1:22 a.m.
On Tue, Nov 6, 2018 at 1:23 PM Alex Gonzalez <alex.gonzalez@digi.com> wrote:
>
> This patch provides machine configuration for the ConnectCore 6UL
> System-On-Module with the following hardware specification:
>
> * Based on a NXP i.MX6UL SoC
> * Industrial temperature ranges (-40ºC to +85ºC)
> * Up to 1GB DDR3 memory
> * Up to 2GB NAND flash
> * Dual Ethernet
> * On module 802.11 WiFi and Bluetooth 4.2 (QCA6564)
> * On module NXP Kinetis KL03
> * On module Microchip ATECC508A crypto element
>
> More details about the SOM can be found at:
> https://www.digi.com/products/embedded-systems/system-on-modules/connectcore-for-i-mx6ul
>
> Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>

Why a .inc? It seems a single machine makes use of this so it does not
need this indirection. Am I missing something?
Gonzalez, Alex Nov. 12, 2018, 8:58 a.m.
On Fri, Nov 09, 2018 at 11:22:46PM -0200, Otavio Salvador wrote:
>On Tue, Nov 6, 2018 at 1:23 PM Alex Gonzalez <alex.gonzalez@digi.com> wrote:

>>

>> This patch provides machine configuration for the ConnectCore 6UL

>> System-On-Module with the following hardware specification:

>>

>> * Based on a NXP i.MX6UL SoC

>> * Industrial temperature ranges (-40ºC to +85ºC)

>> * Up to 1GB DDR3 memory

>> * Up to 2GB NAND flash

>> * Dual Ethernet

>> * On module 802.11 WiFi and Bluetooth 4.2 (QCA6564)

>> * On module NXP Kinetis KL03

>> * On module Microchip ATECC508A crypto element

>>

>> More details about the SOM can be found at:

>> https://www.digi.com/products/embedded-systems/system-on-modules/connectcore-for-i-mx6ul

>>

>> Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>

>

>Why a .inc? It seems a single machine makes use of this so it does not

>need this indirection. Am I missing something?

>


There is another Digi SBC board that uses this include that I plan to submit 
in the near future. Also, this is an .inc for a SOM, so it is possible that 
other boards based on the same SOM use it in future.

>-- 

>Otavio Salvador                             O.S. Systems

>http://www.ossystems.com.br        http://code.ossystems.com.br

>Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750
Otavio Salvador Nov. 12, 2018, 11:53 a.m.
On Mon, Nov 12, 2018 at 6:59 AM Gonzalez, Alex <Alex.Gonzalez@digi.com> wrote:
>
> On Fri, Nov 09, 2018 at 11:22:46PM -0200, Otavio Salvador wrote:
> >On Tue, Nov 6, 2018 at 1:23 PM Alex Gonzalez <alex.gonzalez@digi.com> wrote:
> >>
> >> This patch provides machine configuration for the ConnectCore 6UL
> >> System-On-Module with the following hardware specification:
> >>
> >> * Based on a NXP i.MX6UL SoC
> >> * Industrial temperature ranges (-40ºC to +85ºC)
> >> * Up to 1GB DDR3 memory
> >> * Up to 2GB NAND flash
> >> * Dual Ethernet
> >> * On module 802.11 WiFi and Bluetooth 4.2 (QCA6564)
> >> * On module NXP Kinetis KL03
> >> * On module Microchip ATECC508A crypto element
> >>
> >> More details about the SOM can be found at:
> >> https://www.digi.com/products/embedded-systems/system-on-modules/connectcore-for-i-mx6ul
> >>
> >> Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
> >
> >Why a .inc? It seems a single machine makes use of this so it does not
> >need this indirection. Am I missing something?
> >
>
> There is another Digi SBC board that uses this include that I plan to submit
> in the near future. Also, this is an .inc for a SOM, so it is possible that
> other boards based on the same SOM use it in future.

Until it is used, it is better to avoid it.