imxq6 sabre sd locks up when starting Qt5_Cinematic experience

imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Gunnar Roth]

[-- Attachment #1: Type: text/html, Size: 1625 bytes --]

Re: imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Konstantin Kovalev]

Dear Gunnar,
You could try to enter in your u-boot and then do :
>editenv fdt_file
>fdt_file=imx6q-sabresd.dtb -> fdt_file=imx6q-sabresd-ldo.dtb
>saveenv
>reset
For me it works.

Best Regards,
Konstantin.

________________________________
> From: gunnar.roth@gmx.de 
> To: meta-freescale@yoctoproject.org 
> Date: Fri, 1 Aug 2014 13:18:35 +0200 
> Subject: [meta-freescale] imxq6 sabre sd locks up when starting 
> Qt5_Cinematic experience 
> 
> Hello, 
> I am using IMX6Q SABRE SD board for evaluating purposes of qt5 . about 
> two moth ago all as working fine with qt 5.2.1 to 5.3.0 using meta-qt5 
> layer. 
> Recently I started fresh and use repo like this 
> ~/repo init -u https://github.com/Freescale/fsl-community-bsp-platform 
> -b master; ~/repo sync 
> git clone -b jansa/master https://github.com/meta-qt5/meta-qt5.git 
> after changing bitbake.conf to use http instead of ftp for debian.org ( 
> i am behind a firewall,which blocks ftp here) everything builds well. 
> But the first problem is that it is trying to mount root filesystem on 
> "mmcblk1p2 instead of "mmcblk0p2 as it did before. using editenv 
> mmcroot, that can be fixed. 
> but I have read that should be fixed in master in this mailing list 
> and i pulled again to get this change but to no avail. 
> But the most serious problem is that starting Qt5_CinematicExperience 
> freezes the eval board after the screen going black. 
> ( i also tried master-next branches and even daisy but that does not 
> compile with meta-qt5 branches having qt 5.3.1) 
> I read about another freeze where "The solution is just change 
> "fdt_file=imx6q-sabresd.dtb" to "fdt_file=imx6q-sabresd-ldo.dtb". but 
> sadly I have no clue what to do here. 
> I would be very glad if anyone can shed some light on the solution to 
> my problem. 
> Best regards, 
> Gunnar Roth 
> 
> -- _______________________________________________ meta-freescale 
> mailing list meta-freescale@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/meta-freescale 
 		 	   		  

Re: imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Gunnar Roth]

Dear Konstantin,
thank you very much, now the boards runs again the Qt5CinematicExperience Demo.

But i have no clue why i have to change all this (mmcroot and fdt_file) in uboot, when i build an image for this very sabresd board.
Is the other setting beneficial for anyone using this board?

Clueless,
Gunnar 
 

Gesendet: Freitag, 01. August 2014 um 13:52 Uhr
Von: "Konstantin Kovalev" <lepeletie@hotmail.com>
An: "Gunnar Roth" <gunnar.roth@gmx.de>, "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Betreff: RE: [meta-freescale] imxq6 sabre sd locks up when starting Qt5_Cinematic experience
Dear Gunnar,
You could try to enter in your u-boot and then do :
>editenv fdt_file
>fdt_file=imx6q-sabresd.dtb -> fdt_file=imx6q-sabresd-ldo.dtb
>saveenv
>reset
For me it works.

Best Regards,
Konstantin.

________________________________
> From: gunnar.roth@gmx.de
> To: meta-freescale@yoctoproject.org
> Date: Fri, 1 Aug 2014 13:18:35 +0200
> Subject: [meta-freescale] imxq6 sabre sd locks up when starting
> Qt5_Cinematic experience
>
> Hello,
> I am using IMX6Q SABRE SD board for evaluating purposes of qt5 . about
> two moth ago all as working fine with qt 5.2.1 to 5.3.0 using meta-qt5
> layer.
> Recently I started fresh and use repo like this
> ~/repo init -u https://github.com/Freescale/fsl-community-bsp-platform
> -b master; ~/repo sync
> git clone -b jansa/master https://github.com/meta-qt5/meta-qt5.git[https://github.com/meta-qt5/meta-qt5.git]
> after changing bitbake.conf to use http instead of ftp for debian.org (
> i am behind a firewall,which blocks ftp here) everything builds well.
> But the first problem is that it is trying to mount root filesystem on
> "mmcblk1p2 instead of "mmcblk0p2 as it did before. using editenv
> mmcroot, that can be fixed.
> but I have read that should be fixed in master in this mailing list
> and i pulled again to get this change but to no avail.
> But the most serious problem is that starting Qt5_CinematicExperience
> freezes the eval board after the screen going black.
> ( i also tried master-next branches and even daisy but that does not
> compile with meta-qt5 branches having qt 5.3.1)
> I read about another freeze where "The solution is just change
> "fdt_file=imx6q-sabresd.dtb" to "fdt_file=imx6q-sabresd-ldo.dtb". but
> sadly I have no clue what to do here.
> I would be very glad if anyone can shed some light on the solution to
> my problem.
> Best regards,
> Gunnar Roth
>
> -- _______________________________________________ meta-freescale
> mailing list meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale[https://lists.yoctoproject.org/listinfo/meta-freescale]

Re: imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Otavio Salvador]

On Fri, Aug 1, 2014 at 11:36 AM, Gunnar Roth <gunnar.roth@gmx.de> wrote:
> But i have no clue why i have to change all this (mmcroot and fdt_file) in uboot, when i build an image for this very sabresd board.
> Is the other setting beneficial for anyone using this board?

The mmcroot issue was fixed in master; so please update and confirm it
works for you.

The fdt_file is indeed a bug and we're after the root cause of it as
the 2014.07 version of U-Boot includes the PMIC support.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Gunnar Roth]

>> But i have no clue why i have to change all this (mmcroot and fdt_file) in uboot, when i build an image for this very sabresd board.
>> Is the other setting beneficial for anyone using this board?

>The mmcroot issue was fixed in master; so please update and confirm it
>works for you.

Hmm i built on top of 
2014-07-28 12:16 Otavio Salvador    o [HEAD] [m/master] [yocto/master] u-boot-fslc: Update to 7a3b1da revision
which says
main] 6ef8db67df3436a463851ff95dcfb6a66132f3c0 - commit 1 of 1196 (0%)
commit 6ef8db67df3436a463851ff95dcfb6a66132f3c0
Refs: HEAD, <m/master>, <yocto/master>, 1.6-34-g6ef8db6
Author:     Otavio Salvador <otavio@ossystems.com.br>
AuthorDate: Mon Jul 28 12:16:42 2014 -0300
Commit:     Otavio Salvador <otavio@ossystems.com.br>
CommitDate: Mon Jul 28 12:16:42 2014 -0300

    u-boot-fslc: Update to 7a3b1da revision

    This includes the following changes:

    7a3b1da mx6sabresd: Use mmcblk0 for CONFIG_MMCROOT



So i would assume them  mmcblk0 issue should be fixed in my build. I read about that change here and made an update and bitbaked again.
But it is not yet working for me.

>The fdt_file is indeed a bug and we're after the root cause of it as
>the 2014.07 version of U-Boot includes the PMIC support.

so this is about powermanagment device volatage regulator and we want to use device tree without ldo? well i have only a very very small knowledge of this stuff.
But would it be possible to set back in git to the ldo ftd as long as imx6q-sabresd.dtb does not work? That was a really bad linux experience for me.

Best regards,
Gunnar

Re: imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Otavio Salvador]

On Fri, Aug 1, 2014 at 12:33 PM, Gunnar Roth <gunnar.roth@gmx.de> wrote:
>>> But i have no clue why i have to change all this (mmcroot and fdt_file) in uboot, when i build an image for this very sabresd board.
>>> Is the other setting beneficial for anyone using this board?
>
>>The mmcroot issue was fixed in master; so please update and confirm it
>>works for you.
>
> Hmm i built on top of
> 2014-07-28 12:16 Otavio Salvador    o [HEAD] [m/master] [yocto/master] u-boot-fslc: Update to 7a3b1da revision
> which says
> main] 6ef8db67df3436a463851ff95dcfb6a66132f3c0 - commit 1 of 1196 (0%)
> commit 6ef8db67df3436a463851ff95dcfb6a66132f3c0
> Refs: HEAD, <m/master>, <yocto/master>, 1.6-34-g6ef8db6
> Author:     Otavio Salvador <otavio@ossystems.com.br>
> AuthorDate: Mon Jul 28 12:16:42 2014 -0300
> Commit:     Otavio Salvador <otavio@ossystems.com.br>
> CommitDate: Mon Jul 28 12:16:42 2014 -0300
>
>     u-boot-fslc: Update to 7a3b1da revision
>
>     This includes the following changes:
>
>     7a3b1da mx6sabresd: Use mmcblk0 for CONFIG_MMCROOT
>
>
>
> So i would assume them  mmcblk0 issue should be fixed in my build. I read about that change here and made an update and bitbaked again.
> But it is not yet working for me.

Have you used the .sdcard file? if not, do:

> env default -f -a
> saveenv

inside U-Boot and give it a new try.

>>The fdt_file is indeed a bug and we're after the root cause of it as
>>the 2014.07 version of U-Boot includes the PMIC support.
>
> so this is about powermanagment device volatage regulator and we want to use device tree without ldo? well i have only a very very small knowledge of this stuff.
> But would it be possible to set back in git to the ldo ftd as long as imx6q-sabresd.dtb does not work? That was a really bad linux experience for me.

We're trying to narrow down the root cause and fix it.

Please use don't rely on master for products as those things happen
during the development; your best bet is daisy as it is the current
stable release.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Gunnar Roth]

> Am 01.08.2014 um 19:19 schrieb Otavio Salvador <otavio@ossystems.com.br>:
> 
> On Fri, Aug 1, 2014 at 12:33 PM, Gunnar Roth <gunnar.roth@gmx.de> wrote:
>>>> But i have no clue why i have to change all this (mmcroot and fdt_file) in uboot, when i build an image for this very sabresd board.
>>>> Is the other setting beneficial for anyone using this board?
>> 
>>> The mmcroot issue was fixed in master; so please update and confirm it
>>> works for you.
>> 
>> Hmm i built on top of
>> 2014-07-28 12:16 Otavio Salvador    o [HEAD] [m/master] [yocto/master] u-boot-fslc: Update to 7a3b1da revision
>> which says
>> main] 6ef8db67df3436a463851ff95dcfb6a66132f3c0 - commit 1 of 1196 (0%)
>> commit 6ef8db67df3436a463851ff95dcfb6a66132f3c0
>> Refs: HEAD, <m/master>, <yocto/master>, 1.6-34-g6ef8db6
>> Author:     Otavio Salvador <otavio@ossystems.com.br>
>> AuthorDate: Mon Jul 28 12:16:42 2014 -0300
>> Commit:     Otavio Salvador <otavio@ossystems.com.br>
>> CommitDate: Mon Jul 28 12:16:42 2014 -0300
>> 
>>    u-boot-fslc: Update to 7a3b1da revision
>> 
>>    This includes the following changes:
>> 
>>    7a3b1da mx6sabresd: Use mmcblk0 for CONFIG_MMCROOT
>> 
>> 
>> 
>> So i would assume them  mmcblk0 issue should be fixed in my build. I read about that change here and made an update and bitbaked again.
>> But it is not yet working for me.
> 
> Have you used the .sdcard file? if not, do:
> 
>> env default -f -a
>> saveenv
> 
> inside U-Boot and give it a new try.
> 

Yes always write the .sdcard file to my sdcard and boot from this. To be honest i don’t know what i can do otherwise.
Btw how can i define the size of the rootfs , so to have more space available? Right now i always did a resize of the partition afterwards,
but somehow i must be able to give the size of the roots including free space. 


>>> The fdt_file is indeed a bug and we're after the root cause of it as
>>> the 2014.07 version of U-Boot includes the PMIC support.
>> 
>> so this is about powermanagment device volatage regulator and we want to use device tree without ldo? well i have only a very very small knowledge of this stuff.
>> But would it be possible to set back in git to the ldo ftd as long as imx6q-sabresd.dtb does not work? That was a really bad linux experience for me.
> 
> We're trying to narrow down the root cause and fix it.
> 
> Please use don't rely on master for products as those things happen
> during the development; your best bet is daisy as it is the current
> stable release.
> 

Yes that is right, but i need qt 5.3.1 which actually is the latest stable release of qt and meta-qt5 does support this only with master branch and there they use streamer 1.0 which is not in daisy, at least i got compile errors when mixing daisy and meta-qt5 master.
But as i saw in other messages here   imx6q-sabresd-ldo.dtb  will be used for now. I will pull next week and see if it works.
Best regards,
Gunnar

> -- 
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Gunnar Roth]

[-- Attachment #1: Type: text/plain, Size: 3648 bytes --]

Hi,
i just want to notify that master branch i pulled yesterday has both these issues fixed.
Thanks for the effort.
Gunnar
> Am 02.08.2014 um 10:00 schrieb Gunnar Roth <gunnar.roth@gmx.de>:
> 
>> 
>> Am 01.08.2014 um 19:19 schrieb Otavio Salvador <otavio@ossystems.com.br>:
>> 
>> On Fri, Aug 1, 2014 at 12:33 PM, Gunnar Roth <gunnar.roth@gmx.de> wrote:
>>>>> But i have no clue why i have to change all this (mmcroot and fdt_file) in uboot, when i build an image for this very sabresd board.
>>>>> Is the other setting beneficial for anyone using this board?
>>> 
>>>> The mmcroot issue was fixed in master; so please update and confirm it
>>>> works for you.
>>> 
>>> Hmm i built on top of
>>> 2014-07-28 12:16 Otavio Salvador    o [HEAD] [m/master] [yocto/master] u-boot-fslc: Update to 7a3b1da revision
>>> which says
>>> main] 6ef8db67df3436a463851ff95dcfb6a66132f3c0 - commit 1 of 1196 (0%)
>>> commit 6ef8db67df3436a463851ff95dcfb6a66132f3c0
>>> Refs: HEAD, <m/master>, <yocto/master>, 1.6-34-g6ef8db6
>>> Author:     Otavio Salvador <otavio@ossystems.com.br>
>>> AuthorDate: Mon Jul 28 12:16:42 2014 -0300
>>> Commit:     Otavio Salvador <otavio@ossystems.com.br>
>>> CommitDate: Mon Jul 28 12:16:42 2014 -0300
>>> 
>>>   u-boot-fslc: Update to 7a3b1da revision
>>> 
>>>   This includes the following changes:
>>> 
>>>   7a3b1da mx6sabresd: Use mmcblk0 for CONFIG_MMCROOT
>>> 
>>> 
>>> 
>>> So i would assume them  mmcblk0 issue should be fixed in my build. I read about that change here and made an update and bitbaked again.
>>> But it is not yet working for me.
>> 
>> Have you used the .sdcard file? if not, do:
>> 
>>> env default -f -a
>>> saveenv
>> 
>> inside U-Boot and give it a new try.
>> 
> 
> Yes always write the .sdcard file to my sdcard and boot from this. To be honest i don’t know what i can do otherwise.
> Btw how can i define the size of the rootfs , so to have more space available? Right now i always did a resize of the partition afterwards,
> but somehow i must be able to give the size of the roots including free space. 
> 
> 
>>>> The fdt_file is indeed a bug and we're after the root cause of it as
>>>> the 2014.07 version of U-Boot includes the PMIC support.
>>> 
>>> so this is about powermanagment device volatage regulator and we want to use device tree without ldo? well i have only a very very small knowledge of this stuff.
>>> But would it be possible to set back in git to the ldo ftd as long as imx6q-sabresd.dtb does not work? That was a really bad linux experience for me.
>> 
>> We're trying to narrow down the root cause and fix it.
>> 
>> Please use don't rely on master for products as those things happen
>> during the development; your best bet is daisy as it is the current
>> stable release.
>> 
> 
> Yes that is right, but i need qt 5.3.1 which actually is the latest stable release of qt and meta-qt5 does support this only with master branch and there they use streamer 1.0 which is not in daisy, at least i got compile errors when mixing daisy and meta-qt5 master.
> But as i saw in other messages here   imx6q-sabresd-ldo.dtb  will be used for now. I will pull next week and see if it works.
> Best regards,
> Gunnar
> 
>> -- 
>> Otavio Salvador                             O.S. Systems
>> http://www.ossystems.com.br        http://code.ossystems.com.br
>> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> 
> -- 
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale


[-- Attachment #2: Type: text/html, Size: 15960 bytes --]

Re: imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Trevor Woerner]

(old thread... sorry, just catching up)

On 08/02/14 04:00, Gunnar Roth wrote:
> Btw how can i define the size of the rootfs , so to have more space available? Right now i always did a resize of the partition afterwards,
> but somehow i must be able to give the size of the roots including free space. 

There are a couple variables you can play with in your conf/local.conf
to affect the size of the final image.

First off you can set "IMAGE_OVERHEAD_FACTOR" to a number, say 20
(IMAGE_OVERHEAD_FACTOR = "20"). This will ask that an extra 20% size be
added to your final image.

You can also specify a size (in KB) for your image using IMAGE_ROOTFS_SIZE.

In my experience, however, sometimes these variables get ignored.
Sometimes they're ignored because the code that is used to calculate
these sizes (for the specific build you're doing) doesn't take these
variables into account. If the size you specify is too small, the build
will ignore your request and make the output the size it would have
anyway without any input from you. Sometimes different types of output
will ignore the suggestions you make in your configuration file (e.g.
vmdk versus hddimage).

Nominally you could look in poky/meta/classes/image_types.bbclass and
see how things are calculated. You could also make use of "bitbake -e |
grep <some variable>" to see what your build thinks of the various
things calculated in this bbclass file.

But at the end of the day, unless you have a specific need for the extra
space, all you're doing is increasing the time it takes your "dd"
command to write your cfcard.  If you have a 2GB card and are only using
200MB the "dd" will only take one tenth the time it would take to write
out the entire 2GB card... and all you're doing with all that extra time
is writing empty file space!

There are some intelligent tools [1] that can help you write a 2GB card
with a 200MB image and only take the amount of time that it would take
to write a 200MB card, but those tools aren't integrated into the build
system (yet?). But they certainly work/help if you use them manually
after your build completes but before you write your cfcard (if your
image has lots of empty space added to it, otherwise there's no savings).

Best regards,
    Trevor


[1] https://source.tizen.org/documentation/reference/bmaptool