[meta-freescale] i.MX6 Sabre Smart Devices board and GPS (AH-1613)
Hi. Maybe I am out of place with this question but will try anyway. I recent got my hands on a imx6dlsabresd board and it has worked great with the community BSP. One thing I would like to is to enable the GPS on my board. I have realized that this involves some work which I mostly found on forums what people have tried to do (enable power and reset, and configure ttymx2). My question: Is it expected for the GPS to function on Linux? Has anybody done that? This thread [1] mentions that it requires some firmware only found in Android BSP and I am a bit alarmed by the fact that there is so little mentions of GPS in the official Linux BSP documentation. Hopefully someone in the community has some hints on what can be expected on this board and GPS. [1]. https://community.nxp.com/thread/356465 Best Regards Mirza -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH] u-boot-fslc: fix 2016.09 revision
2017-02-09 11:45 GMT+01:00 Mirza Krak :
> 2017-02-09 11:22 GMT+01:00 Otavio Salvador :
>> On Thu, Feb 9, 2017 at 5:21 AM, Mirza Krak wrote:
>>> 2017-02-09 0:57 GMT+01:00 Otavio Salvador
>>> :
>>>> On Sat, Feb 4, 2017 at 10:39 AM, Mirza Krak wrote:
>>>>> From: Mirza Krak
>>>>>
>>>>> In commit e4bc3c319710 ("u-boot-fslc: Bump revision to 0dea106") the
>>>>> SRCREV was updated for the 2016.09 recipe. But that revision does not
>>>>> exist in tree.
>>>>>
>>>>> Update the revision to point at the v2016.09.01 tag which was the intent
>>>>> in previous commit.
>>>>>
>>>>> Signed-off-by: Mirza Krak
>>>>
>>>> Which branch is this target to?
>>>
>>> master, sorry for not mentioning this in the initial patch.
>>
>> So this is not needed; meta-fsl-arm should be used up to krogoth.
>> Other versions are supported on meta-freescale.
>>
>> Please use meta-freescale and see if it works for you.
>
> Ok, that explains why no body else was complaining beside me :)
>
> Will try meta-freescale and report back.
Works with meta-freescale.
Reason of my confusion was that [1] does not really mention
meta-freescale at all and that was my starting point.
[1]. http://freescale.github.io/#main-section
Best Regards
Mirza
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH] u-boot-fslc: fix 2016.09 revision
2017-02-09 11:22 GMT+01:00 Otavio Salvador :
> On Thu, Feb 9, 2017 at 5:21 AM, Mirza Krak wrote:
>> 2017-02-09 0:57 GMT+01:00 Otavio Salvador :
>>> On Sat, Feb 4, 2017 at 10:39 AM, Mirza Krak wrote:
>>>> From: Mirza Krak
>>>>
>>>> In commit e4bc3c319710 ("u-boot-fslc: Bump revision to 0dea106") the
>>>> SRCREV was updated for the 2016.09 recipe. But that revision does not
>>>> exist in tree.
>>>>
>>>> Update the revision to point at the v2016.09.01 tag which was the intent
>>>> in previous commit.
>>>>
>>>> Signed-off-by: Mirza Krak
>>>
>>> Which branch is this target to?
>>
>> master, sorry for not mentioning this in the initial patch.
>
> So this is not needed; meta-fsl-arm should be used up to krogoth.
> Other versions are supported on meta-freescale.
>
> Please use meta-freescale and see if it works for you.
Ok, that explains why no body else was complaining beside me :)
Will try meta-freescale and report back.
Best Regards
Mirza
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH] u-boot-fslc: fix 2016.09 revision
2017-02-09 0:57 GMT+01:00 Otavio Salvador :
> On Sat, Feb 4, 2017 at 10:39 AM, Mirza Krak wrote:
>> From: Mirza Krak
>>
>> In commit e4bc3c319710 ("u-boot-fslc: Bump revision to 0dea106") the
>> SRCREV was updated for the 2016.09 recipe. But that revision does not
>> exist in tree.
>>
>> Update the revision to point at the v2016.09.01 tag which was the intent
>> in previous commit.
>>
>> Signed-off-by: Mirza Krak
>
> Which branch is this target to?
master, sorry for not mentioning this in the initial patch.
Best Regards
Mirza
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [meta-fsl-arm][PATCH] u-boot-fslc: fix 2016.09 revision
From: Mirza Krak
In commit e4bc3c319710 ("u-boot-fslc: Bump revision to 0dea106") the
SRCREV was updated for the 2016.09 recipe. But that revision does not
exist in tree.
Update the revision to point at the v2016.09.01 tag which was the intent
in previous commit.
Signed-off-by: Mirza Krak
---
recipes-bsp/u-boot/u-boot-fslc_2016.09.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-bsp/u-boot/u-boot-fslc_2016.09.bb
b/recipes-bsp/u-boot/u-boot-fslc_2016.09.bb
index c673365bd1ba..e6f39bcb0a62 100644
--- a/recipes-bsp/u-boot/u-boot-fslc_2016.09.bb
+++ b/recipes-bsp/u-boot/u-boot-fslc_2016.09.bb
@@ -2,5 +2,5 @@ include u-boot-fslc.inc
PV = "v2016.09+git${SRCPV}"
-SRCREV = "0dea106b4985c15c055e7ae187b05a53d6a82a41"
+SRCREV = "0012fc243518872e025259ee1f20a8cd7be3bfae"
SRCBRANCH = "2016.09+fslc"
--
2.1.4
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [PATCH] mfgtool-initramfs-image.bbclass: do not overwrite IMAGE_CLASSES
From: Mirza Krak Use the += operator instead to add image_types_uboot to IMAGE_CLASSES which will correctly append that image type. Signed-off-by: Mirza Krak --- Based on mailing list discussion: https://lists.yoctoproject.org/pipermail/meta-freescale/2017-January/019949.html classes/mfgtool-initramfs-image.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/classes/mfgtool-initramfs-image.bbclass b/classes/mfgtool-initramfs-image.bbclass index 42792f6..afe5124 100644 --- a/classes/mfgtool-initramfs-image.bbclass +++ b/classes/mfgtool-initramfs-image.bbclass @@ -15,7 +15,7 @@ FEATURE_PACKAGES_f2fs = "packagegroup-fsl-mfgtool-f2fs" IMAGE_FSTYPES = "cpio.gz.u-boot" IMAGE_FSTYPES_mxs = "cpio.gz.u-boot" IMAGE_ROOTFS_SIZE ?= "8192" -IMAGE_CLASSES = "image_types_uboot" +IMAGE_CLASSES += "image_types_uboot" # Filesystems enabled by default DEFAULT_FS_SUPPORT = " \ -- 2.1.4 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] mfgtool-initramfs-image.bbclass conflict with other layers
2017-01-05 20:22 GMT+01:00 Mirza Krak : > Hi. > > My first post on this list, be gentle :). > > I am running morty branch and trying to build for "colibri-vf" target. > > Here is my setup: > meta > meta-poky > meta-yocto-bsp= "morty:5aa481dfedfd089f0d6e8a3bae1b84134d5dff4c" > meta-freescale= "morty:6ec09e6a0f09d1cb9c3761b339590c0a0baeeeb3" > meta-fsl-arm = "master:154ccf1e8b08e3d6219bd455b7dfe9ff7ab975b0" > meta-fsl-arm-extra = "morty:69ed94bb781a9c1bfbba4fb3026e4cbf3a194878" > meta-toradex-bsp-common = > "morty-next:ad286efa19257f83985f5f5844a2d500118e40ef" > meta-toradex-nxp = "morty-next:06d4bf9c8b936976d2469b50680a2bbb53cb6f54" > meta-mender-core = "master:10b22602b5a3a8615fcb58b55ae8191712365cf6" > oe-meta-go= "master:fbd51ce7e5acaf1ec298a384f1b3fb791ee7483a" > > And I am running in to a parse error but I can not determain which > layer is to blame. > > In meta-mender-core there is a file called mender-image.bbclass that > does following: > IMAGE_CLASSES += "mender-sdimg mender-artifactimg" > IMAGE_FSTYPES_append = " sdimg mender" > > But when I run "bitbake " I get the following error: > ERROR: > /home/mirzak/project/mender.io/ubifs-support/layers/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb: > No IMAGE_CMD defined for IMAGE_FSTYPES entry 'mender' - possibly > invalid type name or missing support class > ERROR: > /home/mirzak/project/mender.io/ubifs-support/layers/meta-freescale/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb: > No IMAGE_CMD defined for IMAGE_FSTYPES entry 'mender' - possibly > invalid type name or missing support class > ERROR: Failed to parse recipe: > /home/mirzak/project/mender.io/ubifs-support/layers/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb > > Now looked at fsl-image-mfgtool-initramfs.bb and it does modify IMAGE_CLASSES. > > I changed the following line: > IMAGE_CLASSES = "image_types_uboot" > to > IMAGE_CLASSES += "image_types_uboot" > > And then everything is fine again, no parse error and it starts to build. > > I thought that this could be a layer priority issue but it seems that > it is in order for me. Pre-mature send. meta-mender-core = 6 and meta-freescale = 5. Any ides on what is to blame? Please let me know if you want me produce more debug output. Best Regards Mirza -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] mfgtool-initramfs-image.bbclass conflict with other layers
Hi. My first post on this list, be gentle :). I am running morty branch and trying to build for "colibri-vf" target. Here is my setup: meta meta-poky meta-yocto-bsp= "morty:5aa481dfedfd089f0d6e8a3bae1b84134d5dff4c" meta-freescale= "morty:6ec09e6a0f09d1cb9c3761b339590c0a0baeeeb3" meta-fsl-arm = "master:154ccf1e8b08e3d6219bd455b7dfe9ff7ab975b0" meta-fsl-arm-extra = "morty:69ed94bb781a9c1bfbba4fb3026e4cbf3a194878" meta-toradex-bsp-common = "morty-next:ad286efa19257f83985f5f5844a2d500118e40ef" meta-toradex-nxp = "morty-next:06d4bf9c8b936976d2469b50680a2bbb53cb6f54" meta-mender-core = "master:10b22602b5a3a8615fcb58b55ae8191712365cf6" oe-meta-go= "master:fbd51ce7e5acaf1ec298a384f1b3fb791ee7483a" And I am running in to a parse error but I can not determain which layer is to blame. In meta-mender-core there is a file called mender-image.bbclass that does following: IMAGE_CLASSES += "mender-sdimg mender-artifactimg" IMAGE_FSTYPES_append = " sdimg mender" But when I run "bitbake " I get the following error: ERROR: /home/mirzak/project/mender.io/ubifs-support/layers/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'mender' - possibly invalid type name or missing support class ERROR: /home/mirzak/project/mender.io/ubifs-support/layers/meta-freescale/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'mender' - possibly invalid type name or missing support class ERROR: Failed to parse recipe: /home/mirzak/project/mender.io/ubifs-support/layers/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb Now looked at fsl-image-mfgtool-initramfs.bb and it does modify IMAGE_CLASSES. I changed the following line: IMAGE_CLASSES = "image_types_uboot" to IMAGE_CLASSES += "image_types_uboot" And then everything is fine again, no parse error and it starts to build. I thought that this could be a layer priority issue but it seems that it is in order for me. -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] mfgtool-initramfs-image.bbclass conflict with other layers
2017-01-05 20:25 GMT+01:00 Mirza Krak : > 2017-01-05 20:22 GMT+01:00 Mirza Krak : >> Hi. >> >> My first post on this list, be gentle :). >> >> I am running morty branch and trying to build for "colibri-vf" target. >> >> Here is my setup: >> meta >> meta-poky >> meta-yocto-bsp= "morty:5aa481dfedfd089f0d6e8a3bae1b84134d5dff4c" >> meta-freescale= "morty:6ec09e6a0f09d1cb9c3761b339590c0a0baeeeb3" >> meta-fsl-arm = "master:154ccf1e8b08e3d6219bd455b7dfe9ff7ab975b0" >> meta-fsl-arm-extra = "morty:69ed94bb781a9c1bfbba4fb3026e4cbf3a194878" >> meta-toradex-bsp-common = >> "morty-next:ad286efa19257f83985f5f5844a2d500118e40ef" >> meta-toradex-nxp = "morty-next:06d4bf9c8b936976d2469b50680a2bbb53cb6f54" >> meta-mender-core = "master:10b22602b5a3a8615fcb58b55ae8191712365cf6" >> oe-meta-go= "master:fbd51ce7e5acaf1ec298a384f1b3fb791ee7483a" >> >> And I am running in to a parse error but I can not determain which >> layer is to blame. >> >> In meta-mender-core there is a file called mender-image.bbclass that >> does following: >> IMAGE_CLASSES += "mender-sdimg mender-artifactimg" >> IMAGE_FSTYPES_append = " sdimg mender" >> >> But when I run "bitbake " I get the following error: >> ERROR: >> /home/mirzak/project/mender.io/ubifs-support/layers/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb: >> No IMAGE_CMD defined for IMAGE_FSTYPES entry 'mender' - possibly >> invalid type name or missing support class >> ERROR: >> /home/mirzak/project/mender.io/ubifs-support/layers/meta-freescale/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb: >> No IMAGE_CMD defined for IMAGE_FSTYPES entry 'mender' - possibly >> invalid type name or missing support class >> ERROR: Failed to parse recipe: >> /home/mirzak/project/mender.io/ubifs-support/layers/meta-fsl-arm/recipes-fsl/images/fsl-image-mfgtool-initramfs.bb >> >> Now looked at fsl-image-mfgtool-initramfs.bb and it does modify >> IMAGE_CLASSES. >> >> I changed the following line: >> IMAGE_CLASSES = "image_types_uboot" >> to >> IMAGE_CLASSES += "image_types_uboot" >> >> And then everything is fine again, no parse error and it starts to build. >> >> I thought that this could be a layer priority issue but it seems that >> it is in order for me. > > Pre-mature send. > > meta-mender-core = 6 and meta-freescale = 5. > > Any ides on what is to blame? Please let me know if you want me > produce more debug output. > re-send, since my initial mail is in "waiting for moderator approval". I am member on the list now so hopefully this will go all the way. Best Regards Mirza -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
