[meta-freescale] R: R: [ANN] FSL Test Plan Announcement 1.6 | imx53qsb + qt5.2
Gianluca Cinci
gianluca.cinci at giuneco.it
Tue Apr 29 03:02:46 PDT 2014
On 29/04/2014 11:34, Simone wrote:
> Hello Gianluca,
> There is a valid reason for the settings of DMA zone at 180?
> It seems odd to me..
i found some imx53 issue/patches here :
https://github.com/Freescale/meta-fsl-arm/pull/3/files
Gianluca
P.S.
i found also this document but at the moment don't know if it can be usefull
https://community.freescale.com/servlet/JiveServlet/previewBody/93334-102-1-2448/iMX5%20Android%20GB%20Memory%20Usage%20and%20Optimization.pdf
>
> Regards
> Simone
>
>
> -----Messaggio originale-----
> Da: Gianluca Cinci [mailto:gianluca.cinci at giuneco.it]
> Inviato: martedì 29 aprile 2014 11:06
> A: Simone; meta-freescale at yoctoproject.org
> Oggetto: Re: R: [meta-freescale] [ANN] FSL Test Plan Announcement 1.6 | imx53qsb + qt5.2
>
> Hi Simone ,
> for the kernel panic i recompile the kernel with the dma zone = 180 , i have it at 112.
>
> Now , when i start the application the second time i don't have any kernel panic , but this message comes out:
>
> GPU : AXI Read/Write Error or MMU page fault (probably the value 180 is too high???)
>
> and the machine freeze....
>
>
> regards
> Gianluca
>
> P.S.
> in previous mail i omitted this application outputs messages:
>
> EGLFS: Unable to query physical screen size, defaulting to 100 dpi.
> EGLFS: To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_H.
> libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile Color formats don't match. Falling back to copy forward swap.
> Color formats don't match. Falling back to copy forward swap.
>
>
>
>
>
> On 29/04/2014 10:44, Simone wrote:
>> Ciao Gianluca,
>> Exactly the same problems here.
>>
>> Best Regards
>> Simone
>>
>>
>>
>> -----Messaggio originale-----
>> Da: meta-freescale-bounces at yoctoproject.org [mailto:meta-freescale-bounces at yoctoproject.org] Per conto di Gianluca Cinci
>> Inviato: martedì 29 aprile 2014 10:24
>> A: meta-freescale at yoctoproject.org
>> Oggetto: Re: [meta-freescale] [ANN] FSL Test Plan Announcement 1.6 | imx53qsb + qt5.2
>>
>> Hi Diane,
>> hi all.
>>
>> I go forward into the daisy test and with the image fsl-image-multimedia , the qt5 framework run on the imx53qsb.
>> 1)
>> why if i insert the qtbase (and other packages like qtbase-plugins) into the my local.conf and i "cook" a core-image-base image the qt5 application exit with this error?
>>
>> -------------------
>> EGL Error : Could not create the egl surface: error = 0x3003 Aborted
>> --------------------
>>
>>
>> I notice that the /usr/ folder was quite different for the two images ; what libraries or binaries are missing on core-image-base for run a qt5 application?
>>
>> 2) after i make a fsl-image-multimedia i try the CinematicExperience (that has some video problem like screen micro freeze and rendering
>> problems) :
>>
>> 2a) when i kill the application this output come out:
>>
>> del_all_devices_contexts: Destroyed context 0 on device id = 1
>> del_all_devices_contexts: Destroyed context 1 on device id = 1
>> del_all_devices_contexts: Destroyed context 1 on device id = 2 Not all allocated memory blocks were freed. Doing it now.
>> Freeing list entry #0, gpuaddr=100000
>> Freeing list entry #1, gpuaddr=105000
>> Freeing list entry #2, gpuaddr=10a000
>> Freeing list entry #3, gpuaddr=10f000
>> Freeing list entry #4, gpuaddr=114000
>> Freeing list entry #5, gpuaddr=76c4e000
>> Freeing list entry #6, gpuaddr=76800000
>> Freeing list entry #7, gpuaddr=76840000
>> Freeing list entry #8, gpuaddr=76880000
>> Freeing list entry #9, gpuaddr=76881000
>> .........
>> .........
>>
>> -----------------------------------------------
>> Now , when i restart the application i receive this kernel panic and the machine freeze:
>> --------------------
>> Unhandled fault: external abort on non-linefetch (0x1008) at 0xd0ac0edc Internal error: : 1008 [#1] PREEMPT last sysfs file: /sys/devices/system/cpu/online Modules linked in:
>> CPU: 0 Not tainted (2.6.35.3-11.09.01+yocto+ged51f22 #1)
>> PC is at kgsl_yamato_regread+0xc/0x24
>> LR is at kgsl_yamato_isr+0x18/0x80
>> pc : [<80376c2c>] lr : [<80377450>] psr: 60070193
>> sp : c81dff58 ip : ffffab5e fp : 00000000
>> r10: 00000000 r9 : c81de000 r8 : 00000000
>> r7 : 0000000c r6 : 00000000 r5 : 00000000 r4 : 806a0b28
>> r3 : d0ac0000 r2 : c81dff5c r1 : 000003b7 r0 : 806a0b28
>> Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
>> Control: 10c5387d Table: ba6e4019 DAC: 00000015 Process QSGRenderThread (pid: 1700, stack limit = 0xc81de2e8)
>> Stack: (0xc81dff58 to 0xc81e0000)
>> ff40: 806a0b28
>> cff48780
>> ff60: 806a0b28 80373b5c cf263f40 803792dc 803792d0 800e9e50 00000000 80641e3c
>> ff80: 0000000c cf263f40 00000001 800eb8b4 0000000c 00000000 00000001
>> 80090068
>> ffa0: 20070010 ffffffff d0800000 80090bc8 32681000 01aae330 00003910
>> 00000000
>> ffc0: 01aac450 4c298b80 002f0498 01aac450 00001850 002f8420 00000000
>> 00000000
>> ffe0: 32682ec0 3216d934 4bef37e4 4bc6a0b0 20070010 ffffffff 8e38d48b
>> 59ebdc88
>> [<80376c2c>] (kgsl_yamato_regread+0xc/0x24) from [<80377450>]
>> (kgsl_yamato_isr+)
>> [<80377450>] (kgsl_yamato_isr+0x18/0x80) from [<80373b5c>]
>> (kgsl_intr_isr+0x24/)
>> [<80373b5c>] (kgsl_intr_isr+0x24/0x28) from [<803792dc>]
>> (z430_irq_handler+0xc/)
>> [<803792dc>] (z430_irq_handler+0xc/0x18) from [<800e9e50>]
>> (handle_IRQ_event+0x)
>> [<800e9e50>] (handle_IRQ_event+0x24/0xdc) from [<800eb8b4>]
>> (handle_level_irq+0)
>> [<800eb8b4>] (handle_level_irq+0xd8/0x184) from [<80090068>]
>> (asm_do_IRQ+0x68/0)
>> [<80090068>] (asm_do_IRQ+0x68/0x88) from [<80090bc8>] (__irq_usr+0x48/0xc0) Exception stack(0xc81dffb0 to 0xc81dfff8)
>> ffa0: 32681000 01aae330 00003910
>> 00000000
>> ffc0: 01aac450 4c298b80 002f0498 01aac450 00001850 002f8420 00000000
>> 00000000
>> ffe0: 32682ec0 3216d934 4bef37e4 4bc6a0b0 20070010 ffffffff
>> Code: e12fff1e e5903088 f57ff04f f57ff04f (e7933101) ---[ end trace 0efc6cf93f26278e ]--- Kernel panic - not syncing: Fatal exception in interrupt [<80095144>] (unwind_backtrace+0x0/0xe0) from [<804aacfc>]
>> (panic+0x68/0xdc)
>> [<804aacfc>] (panic+0x68/0xdc) from [<80094158>] (die+0x2a8/0x2f8) [<80094158>] (die+0x2a8/0x2f8) from [<8009026c>] (do_DataAbort+0x84/0x98) [<8009026c>] (do_DataAbort+0x84/0x98) from [<8009092c>]
>> (__dabt_svc+0x4c/0x60)
>> Exception stack(0xc81dff10 to 0xc81dff58)
>> ff00: 806a0b28 000003b7 c81dff5c
>> d0ac0000
>> ff20: 806a0b28 00000000 00000000 0000000c 00000000 c81de000 00000000
>> 00000000
>> ff40: ffffab5e c81dff58 80377450 80376c2c 60070193 ffffffff [<8009092c>] (__dabt_svc+0x4c/0x60) from [<80376c2c>]
>> (kgsl_yamato_regread+0xc/)
>> [<80376c2c>] (kgsl_yamato_regread+0xc/0x24) from [<80377450>]
>> (kgsl_yamato_isr+)
>> [<80377450>] (kgsl_yamato_isr+0x18/0x80) from [<80373b5c>]
>> (kgsl_intr_isr+0x24/)
>> [<80373b5c>] (kgsl_intr_isr+0x24/0x28) from [<803792dc>]
>> (z430_irq_handler+0xc/)
>> [<803792dc>] (z430_irq_handler+0xc/0x18) from [<800e9e50>]
>> (handle_IRQ_event+0x)
>> [<800e9e50>] (handle_IRQ_event+0x24/0xdc) from [<800eb8b4>]
>> (handle_level_irq+0)
>> [<800eb8b4>] (handle_level_irq+0xd8/0x184) from [<80090068>]
>> (asm_do_IRQ+0x68/0)
>> [<80090068>] (asm_do_IRQ+0x68/0x88) from [<80090bc8>] (__irq_usr+0x48/0xc0) Exception stack(0xc81dffb0 to 0xc81dfff8)
>> ffa0: 32681000 01aae330 00003910
>> 00000000
>> ffc0: 01aac450 4c298b80 002f0498 01aac450 00001850 002f8420 00000000
>> 00000000
>> ffe0: 32682ec0 3216d934 4bef37e4 4bc6a0b0 20070010 ffffffff
>> -------------------
>>
>> This messages remember me the dma zone allocate value ... is this correct? (i'm going to recompile the kernel and try it , i send report when i finish the task)
>>
>>
>> 3)
>> after the first qt5 demo application run test (CinematicExperience) i decide to build my example application:
>> i bitbake the "meta-toolchain-qt5.bb" recipe I modified the qt creator start script and i add the new qt 5.2 kits.
>>
>> When i try to compile , some includes are missing (eg KHR/khrplatform.h) and , when i import the QtMultimedia 5.0 into a qml file , the ide say me that it can't find the module
>>
>> Thank you very much
>>
>> regards
>> Gianluca Cinci
>>
>>
>> On 19/04/2014 17:49, Gianluca Cinci wrote:
>>> Hi Diane ,
>>> thanks for the answer!
>>> Next week i prepare a new mail with more information
>>>
>>> On 16/04/2014 19:57, Daiane Angolini wrote:
>>>> On Tue, Apr 15, 2014 at 11:34 AM, Gianluca Cinci
>>>> <gianluca.cinci at giuneco.it> wrote:
>>>>> Hi all, hi Diane
>>>>> i tried the snapshot 20140407 (daisy) on imx53qsb.
>>>> Thanks!
>>>>
>>>> Have you reported your test using the Form?
>>> At this moment my scenario is:
>>> filesystem : yocto 1.6
>>> kernel : yocto 1.4
>>> u-boot : yocto 1.4
>>>
>>> and this is why i don't use the Form
>>>
>>>
>>>>> The filesystem (ubi) boot ok , ( i must to try kernel and uboot)
>>>>>
>>>>> My question is about qt 5.2
>>>>> I compiled with this local.conf:
>>>> Have you replied to a digest email? I´m kind of confused on the
>>>> message context.
>>> I reply to your mail on meta-freescale at yoctoproject.org mailing list.
>>>
>>> Many thanks
>>> Gianluca
>>>
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>>
>
More information about the meta-freescale
mailing list