Re: [meta-freescale] [meta-fsl-arm-extra][PATCH v3 1/4] cgtqmx6: Update Congatec-QMX6 machine configuration
Due to decisions we've taken, having only one partition, for now
I would like to keep it as it is.
Anyway I will think about this in the near future.
Does your generated .sdcard image works?
To make it work I have to change those three U-boot environment variables
with:
setenv loadfdt 'fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}'
setenv loaduimage 'fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${uimage}'
setenv mmcroot '/dev/mmcblk0p2 rootwait rw'
By default we have only one partition, installing the uImage and the dts
files into
the /boot folder.
I don't like to have now two different structures for our customers,
that's why I
want to keep the old one.
Even with that I could add some small description to make the sdcard file
works.
What do you think?--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm-extra][PATCH v3 1/4] cgtqmx6: Update Congatec-QMX6 machine configuration
On Thu, Sep 4, 2014 at 10:47 AM, alejandro.de-cabo-gar...@congatec.com wrote:
Due to decisions we've taken, having only one partition, for now
I would like to keep it as it is.
Anyway I will think about this in the near future.
Does your generated .sdcard image works?
To make it work I have to change those three U-boot environment variables
with:
setenv loadfdt 'fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}'
setenv loaduimage 'fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${uimage}'
setenv mmcroot '/dev/mmcblk0p2 rootwait rw'
By default we have only one partition, installing the uImage and the dts
files into
the /boot folder.
I don't like to have now two different structures for our customers, that's
why I
want to keep the old one.
Even with that I could add some small description to make the sdcard file
works.
What do you think?
I think you to miss the opportunity to follow the community standard
may be counterproductive for Congatec in the long term.
The idea of the .sdcard is to allow user to go easy to a working
system and I think this is key for usability. All the documentation we
have done, and we are working on, rely on this to easy the first
experience of the user/customer.
In case your concern is to not change the U-Boot code in your Git, you
can adapt the environment using a patch file in the U-Boot recipe.
This is not a blocker to accept the patchset but I do believe this
would be a plus in first experience of users.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [meta-fsl-arm-extra][PATCH v3 1/4] cgtqmx6: Update Congatec-QMX6 machine configuration
Update config file:
* U-boot provider: u-boot-qmx6
- UBOOT_CONFIG variable defines the Congatec-QMX6 module
variant to build. For testing purposes by default is set
to: pn016103
- This variable must be set in the conf/local.conf file
according with the module partnumber. The possible values
are:
pn016100, pn016101, pn016102, pn016103, pn016104, pn016105,
pn016106, pn016110, pn016111, pn016112, pn016113
If a PN016101 is the target module, the line added to the
conf/local.conf would be like the following:
UBOOT_CONFIG = pn016101
* Linux kernel provider: linux-qmx6
- Config file is the same for all the variants, due to that
the SOC_FAMILY variables includes all SOCs to include the
firmware of all machines.
* The rootfs must be transfered to the first ext3 partiton of
a micro-SD card (detailed steps are in 'qmx6_readme_yocto_1.6.txt'
file in section 2. 'Transfer the root file system'
It can be found in: http://www.congatec.com/products/qseven/conga-qmx6.html
under the Drivers section. (Login requiered)
Signed-off-by: Alex de Cabo alejandro.de-cabo-gar...@congatec.com
---
conf/machine/cgtqmx6.conf | 30 +++---
1 file changed, 23 insertions(+), 7 deletions(-)
diff --git a/conf/machine/cgtqmx6.conf b/conf/machine/cgtqmx6.conf
index 467379a..ea2f373 100644
--- a/conf/machine/cgtqmx6.conf
+++ b/conf/machine/cgtqmx6.conf
@@ -6,18 +6,34 @@
include conf/machine/include/imx-base.inc
include conf/machine/include/tune-cortexa9.inc
-SOC_FAMILY = mx6:mx6q
+SOC_FAMILY = mx6:mx6dl:mx6q
-# Use u-boot imx
-UBOOT_SUFFIX = bin
+# Use u-boot QMX6
UBOOT_PADDING = 2
-PREFERRED_PROVIDER_u-boot = u-boot-imx
-PREFERRED_VERSION_u-boot-imx = 2009.08
+PREFERRED_PROVIDER_u-boot = u-boot-qmx6
-PREFERRED_PROVIDER_virtual/kernel ?= linux-congatec
+UBOOT_CONFIG ??= pn016103
+UBOOT_CONFIG[pn016100] = cgt_qmx6_pn016100
+UBOOT_CONFIG[pn016101] = cgt_qmx6_pn016101
+UBOOT_CONFIG[pn016102] = cgt_qmx6_pn016102
+UBOOT_CONFIG[pn016103] = cgt_qmx6_pn016103
+UBOOT_CONFIG[pn016104] = cgt_qmx6_pn016104
+UBOOT_CONFIG[pn016105] = cgt_qmx6_pn016105
+UBOOT_CONFIG[pn016106] = cgt_qmx6_pn016106
+UBOOT_CONFIG[pn016110] = cgt_qmx6_pn016110
+UBOOT_CONFIG[pn016111] = cgt_qmx6_pn016111
+UBOOT_CONFIG[pn016112] = cgt_qmx6_pn016112
+UBOOT_CONFIG[pn016113] = cgt_qmx6_pn016113
-UBOOT_MACHINE = cgtqmx6_config
+UBOOT_MAKE_TARGET = u-boot.${UBOOT_CONFIG}.imx
+
+#Use linux kernel QMX6
+PREFERRED_PROVIDER_virtual/kernel = linux-qmx6
+KERNEL_DEVICETREE = imx6q-qmx6.dtb imx6dl-qmx6.dtb
SERIAL_CONSOLE = 115200 ttymxc1
MACHINE_FEATURES += pci
+
+#Create only tar.bz2 image
+IMAGE_FSTYPES = tar.bz2
--
1.9.1
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm-extra][PATCH v3 1/4] cgtqmx6: Update Congatec-QMX6 machine configuration
Hello Alex,
On Thu, Aug 21, 2014 at 11:11 AM, Alex de Cabo
alejandro.de-cabo-gar...@congatec.com wrote:
Update config file:
* U-boot provider: u-boot-qmx6
- UBOOT_CONFIG variable defines the Congatec-QMX6 module
variant to build. For testing purposes by default is set
to: pn016103
- This variable must be set in the conf/local.conf file
according with the module partnumber. The possible values
are:
pn016100, pn016101, pn016102, pn016103, pn016104, pn016105,
pn016106, pn016110, pn016111, pn016112, pn016113
If a PN016101 is the target module, the line added to the
conf/local.conf would be like the following:
UBOOT_CONFIG = pn016101
* Linux kernel provider: linux-qmx6
- Config file is the same for all the variants, due to that
the SOC_FAMILY variables includes all SOCs to include the
firmware of all machines.
Very good.
* The rootfs must be transfered to the first ext3 partiton of
a micro-SD card (detailed steps are in 'qmx6_readme_yocto_1.6.txt'
file in section 2. 'Transfer the root file system'
It can be found in: http://www.congatec.com/products/qseven/conga-qmx6.html
under the Drivers section. (Login requiered)
I am wondering if you could use our sdcard image, as is, as this would
make it easier to use for most users in the first time.
Any reason to not? Nitrogen uses an script in the first partition next
to the kernel to script this. This seems solid and flexible.
Signed-off-by: Alex de Cabo alejandro.de-cabo-gar...@congatec.com
---
conf/machine/cgtqmx6.conf | 30 +++---
1 file changed, 23 insertions(+), 7 deletions(-)
diff --git a/conf/machine/cgtqmx6.conf b/conf/machine/cgtqmx6.conf
index 467379a..ea2f373 100644
--- a/conf/machine/cgtqmx6.conf
+++ b/conf/machine/cgtqmx6.conf
@@ -6,18 +6,34 @@
include conf/machine/include/imx-base.inc
include conf/machine/include/tune-cortexa9.inc
-SOC_FAMILY = mx6:mx6q
+SOC_FAMILY = mx6:mx6dl:mx6q
-# Use u-boot imx
-UBOOT_SUFFIX = bin
+# Use u-boot QMX6
UBOOT_PADDING = 2
UBOOT_PADDING should be removed; this is needed for old U-Boot
releases, 2013.04 uses proper i.MX headers.
-PREFERRED_PROVIDER_u-boot = u-boot-imx
-PREFERRED_VERSION_u-boot-imx = 2009.08
+PREFERRED_PROVIDER_u-boot = u-boot-qmx6
-PREFERRED_PROVIDER_virtual/kernel ?= linux-congatec
+UBOOT_CONFIG ??= pn016103
+UBOOT_CONFIG[pn016100] = cgt_qmx6_pn016100
+UBOOT_CONFIG[pn016101] = cgt_qmx6_pn016101
+UBOOT_CONFIG[pn016102] = cgt_qmx6_pn016102
+UBOOT_CONFIG[pn016103] = cgt_qmx6_pn016103
+UBOOT_CONFIG[pn016104] = cgt_qmx6_pn016104
+UBOOT_CONFIG[pn016105] = cgt_qmx6_pn016105
+UBOOT_CONFIG[pn016106] = cgt_qmx6_pn016106
+UBOOT_CONFIG[pn016110] = cgt_qmx6_pn016110
+UBOOT_CONFIG[pn016111] = cgt_qmx6_pn016111
+UBOOT_CONFIG[pn016112] = cgt_qmx6_pn016112
+UBOOT_CONFIG[pn016113] = cgt_qmx6_pn016113
-UBOOT_MACHINE = cgtqmx6_config
+UBOOT_MAKE_TARGET = u-boot.${UBOOT_CONFIG}.imx
Ok.
+#Use linux kernel QMX6
Space between # and Use ;-)
+PREFERRED_PROVIDER_virtual/kernel = linux-qmx6
+KERNEL_DEVICETREE = imx6q-qmx6.dtb imx6dl-qmx6.dtb
SERIAL_CONSOLE = 115200 ttymxc1
MACHINE_FEATURES += pci
+
+#Create only tar.bz2 image
+IMAGE_FSTYPES = tar.bz2
If you keep this, fix comment to have an space before Create.
Along with those comments, this patch should come /after/ kernel and
u-boot updates or machine breaks in the mid of it.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
