[nightly] Core TISDK 2013.06 build 2013-07-21_01-01-44

[nightly] Core TISDK 2013.06 build 2013-07-21_01-01-44

[Denys Dmytriyenko]

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

Re: [nightly] Core TISDK 2013.06 build 2013-07-21_01-01-44

[Christian Gagneraud]

Hi there,

I have been looking at these test/build reports recently, is there a 
more detail report available somewhere?
As a user of a am335x-evm and a BeagleBoard Black, I would like to know 
more about test failure for the EVM.

As well, I'm considering moving from Arago/Danny (kernel 3.2) to 
Arago/Dylan (kernel 3.8?). I would like to know if there are any plan to 
use Dylan for the next stable Arago.

Also, do you think it is conceivable to hope for a working Qt5 with TI 
OpenGL stuff?

Regards,
Chris


On 21/07/13 17:55, Denys Dmytriyenko wrote:
> Status for 07/21/13
>
>
>     Status for 07/21/13
>
>
>     BUILD_ID: build-2013-07-21_01-02-45
>
>
>     Clean Build: false
>
>
>     Clean Sources: false
>
>
>     _Repository Revisions_
>
> Repository 	Git URL 	Branch 	Commit ID 	Layers
> bitbake 	git://git.openembedded.org/bitbake 	master 	1.17.0 	layers=
> meta-arago 	git://arago-project.org/git/meta-arago.git 	danny 	HEAD 
> layers=meta-arago-distro:meta-arago-extras
> meta-openembedded 	git://git.openembedded.org/meta-openembedded 
> danny 	HEAD 	layers=toolchain-layer:meta-oe
> meta-ti 	git://arago-project.org/git/meta-ti.git 	danny 	HEAD 	layers=
> meta-linaro 	git://git.linaro.org/openembedded/meta-linaro.git 
> danny 	HEAD 	layers=
> oe-core 	git://git.openembedded.org/openembedded-core 	danny 	HEAD 
> layers=meta
>
>
>     _Build and Target Test Results_
>
> Machine 	Build Result 	Target Test Result
> am335x-evm 	PASSED 	FAILED
> am37x-evm 	PASSED 	PASSED
> omap5-evm 	FAILED 	SKIPPED
> dra7xx-evm 	FAILED 	SKIPPED
> beagleboard 	PASSED 	PASSED
> am3517-evm 	PASSED 	PASSED
> am180x-evm 	PASSED 	FAILED
>
> These builds were performed using the build-oesdk.sh script at:
>
> git://arago-project.org/git/projects/tisdk-build-scripts.git
>
> The configuration file passed to this script had the contents:
>
> MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS BUILD_ID 
> SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT DEPLOY_ROOT FS_FILTER 
> SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE NFS_ROOT CONFIG_FILE LOG_DIR 
> TISDK_VERSION"
> TISDK_VERSION="2013.06"
> MACHINES="am335x-evm am37x-evm omap5-evm dra7xx-evm beagleboard 
> am3517-evm am180x-evm"
> NUM_ARM9_BUILDS="1"
> NUM_CORTEX_BUILDS="1"
> TOOLCHAIN_ROOT_ARM9="/opt/arago-2011.09/armv5te/bin/"
> TOOLCHAIN_ROOT_CORTEX="/opt/linaro-2013.03/bin/"
> BUILD_ID="`date +build-%F_%H-%M-%S`"
> SCRIPTS_ROOT="$PWD"
> BUILD_ROOT="/home/jenkins/tisdk-build"
> TEST_ROOT="$BUILD_ROOT/testing"
> PACKAGE_ROOT="$BUILD_ROOT/packaging"
> DEPLOY_ROOT="$BUILD_ROOT/deploy/$TISDK_VERSION"
> FS_FILTER="tisdk-rootfs-"
> FS_IMAGE_TYPE="tar.gz"
> SDK_FILTER="arago-core-tisdk-image-"
> SDK_IMAGE_TYPE="tar.gz"
> NFS_ROOT="/home/jenkins/nfs-root"
> SOURCE_DIR="${BUILD_ROOT}/sources"
> CLEAN_BUILD="false"
> CLEAN_ALL="false"
> CONFIG_FILE="${BUILD_ROOT}/configs/arago-danny-config.txt"
> LOG_DIR="${BUILD_ROOT}/log-files"
> DL_DIR="/OE/downloads"
> INSTALLER_EXTRAS_ROOT="/home/jenkins/extra-files/installer_content"
> TEST_SCRIPTS="$SCRIPTS_ROOT/test-scripts"
> TEST_SCRIPTS_TGT="home/root/test-scripts"
> TEST_LOCAL_IFACE="eth1"
> OPENTEST_CLI="$SCRIPTS_ROOT/opentest_cli_0.7.tar.gz"
> OPENTEST_TEE_IP="10.218.102.142"
> RUN_BUILD_TESTS="true"
> STAF_ROOT="/usr/local/staf"
> SKIP_TEST_FAILURES="false"
> PRODUCTIZE_SDK="false"
> BITBAKE_COMMAND="arago-core-tisdk-image"
> RESULTS_CONFIG_COMMENTS="false"
> INSTALL_JAMMER="/home/jenkins/installjammer"
> INSTALLER_ROOT="$BUILD_ROOT/installer"
> MPI_FILE="$SCRIPTS_ROOT/mpi-files/ti-sdk-base.mpi"
> SD_CARD_CONTENT="/home/jenkins/extra-files/sd_content"
> PACKAGE_BOOT_UIMAGE="false"
> WEBGEN_ROOT="/home/jenkins/webgen"
> WEB_EXTRAS_ROOT="/home/jenkins/extra-files/web_content"
> WEBGEN_MAK_ROOT="$SCRIPTS_ROOT/publish-sdk-data"
> COPY_TO_WEB="true"
> WEB_HOST=""
> CLEAN_AFTER_COPY="true"
> BACKUP_RESULTS="/home/jenkins/jobs/arago-core-tisdk-nightly/workspace"
>
>
>
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [nightly] Core TISDK 2013.06 build 2013-07-21_01-01-44

[Denys Dmytriyenko]

Christian,

On Tue, Jul 23, 2013 at 02:26:24PM +1200, Christian Gagneraud wrote:
> Hi there,
> 
> I have been looking at these test/build reports recently, is there a
> more detail report available somewhere?

Yes, but detailed reports are not yet published externally - it's on my 
"to do" list.


> As a user of a am335x-evm and a BeagleBoard Black, I would like to
> know more about test failure for the EVM.

There are some issues with the boot sequence of an automated test - looks 
like it's trying to load a wrong kernel image, I'll look into it later. 
Otherwise, the latest Dylan build works and boots fine for me on am335x-evm 
when loaded manually on SD card.


> As well, I'm considering moving from Arago/Danny (kernel 3.2) to
> Arago/Dylan (kernel 3.8?). I would like to know if there are any
> plan to use Dylan for the next stable Arago.

Actually, Arago/Danny has been using kernel 3.8 for quite some time now - we 
already had couple internal releases with it. You would need to specifically 
request AM-SDK branding to get 3.2 kernel, as the default is 3.8 in Danny and 
in Dylan. The only change Dylan brings is to update the underlying Yocto 
framework with all the user-space apps to the latest versions.


> Also, do you think it is conceivable to hope for a working Qt5 with
> TI OpenGL stuff?

It's in the plans. Prabu was able to get it built after some massaging, but 
there are still few issues. Also, we would need to make sure the fallback 
mechanism works for legacy devices w/o GLES, since Qt5 requires it...

-- 
Denys


> On 21/07/13 17:55, Denys Dmytriyenko wrote:
> >Status for 07/21/13
> >
> >
> >    Status for 07/21/13
> >
> >
> >    BUILD_ID: build-2013-07-21_01-02-45
> >
> >
> >    Clean Build: false
> >
> >
> >    Clean Sources: false
> >
> >
> >    _Repository Revisions_
> >
> >Repository 	Git URL 	Branch 	Commit ID 	Layers
> >bitbake 	git://git.openembedded.org/bitbake 	master 	1.17.0 	layers=
> >meta-arago 	git://arago-project.org/git/meta-arago.git 	danny
> >	HEAD layers=meta-arago-distro:meta-arago-extras
> >meta-openembedded 	git://git.openembedded.org/meta-openembedded
> >danny 	HEAD 	layers=toolchain-layer:meta-oe
> >meta-ti 	git://arago-project.org/git/meta-ti.git 	danny 	HEAD 	layers=
> >meta-linaro 	git://git.linaro.org/openembedded/meta-linaro.git
> >danny 	HEAD 	layers=
> >oe-core 	git://git.openembedded.org/openembedded-core 	danny 	HEAD
> >layers=meta
> >
> >
> >    _Build and Target Test Results_
> >
> >Machine 	Build Result 	Target Test Result
> >am335x-evm 	PASSED 	FAILED
> >am37x-evm 	PASSED 	PASSED
> >omap5-evm 	FAILED 	SKIPPED
> >dra7xx-evm 	FAILED 	SKIPPED
> >beagleboard 	PASSED 	PASSED
> >am3517-evm 	PASSED 	PASSED
> >am180x-evm 	PASSED 	FAILED
> >
> >These builds were performed using the build-oesdk.sh script at:
> >
> >git://arago-project.org/git/projects/tisdk-build-scripts.git
> >
> >The configuration file passed to this script had the contents:
> >
> >MANDATORY_INPUTS="MACHINES NUM_ARM9_BUILDS NUM_CORTEX_BUILDS
> >BUILD_ID SCRIPTS_ROOT BUILD_ROOT TEST_ROOT PACKAGE_ROOT
> >DEPLOY_ROOT FS_FILTER SDK_FILTER FS_IMAGE_TYPE SDK_IMAGE_TYPE
> >NFS_ROOT CONFIG_FILE LOG_DIR TISDK_VERSION"
> >TISDK_VERSION="2013.06"
> >MACHINES="am335x-evm am37x-evm omap5-evm dra7xx-evm beagleboard
> >am3517-evm am180x-evm"
> >NUM_ARM9_BUILDS="1"
> >NUM_CORTEX_BUILDS="1"
> >TOOLCHAIN_ROOT_ARM9="/opt/arago-2011.09/armv5te/bin/"
> >TOOLCHAIN_ROOT_CORTEX="/opt/linaro-2013.03/bin/"
> >BUILD_ID="`date +build-%F_%H-%M-%S`"
> >SCRIPTS_ROOT="$PWD"
> >BUILD_ROOT="/home/jenkins/tisdk-build"
> >TEST_ROOT="$BUILD_ROOT/testing"
> >PACKAGE_ROOT="$BUILD_ROOT/packaging"
> >DEPLOY_ROOT="$BUILD_ROOT/deploy/$TISDK_VERSION"
> >FS_FILTER="tisdk-rootfs-"
> >FS_IMAGE_TYPE="tar.gz"
> >SDK_FILTER="arago-core-tisdk-image-"
> >SDK_IMAGE_TYPE="tar.gz"
> >NFS_ROOT="/home/jenkins/nfs-root"
> >SOURCE_DIR="${BUILD_ROOT}/sources"
> >CLEAN_BUILD="false"
> >CLEAN_ALL="false"
> >CONFIG_FILE="${BUILD_ROOT}/configs/arago-danny-config.txt"
> >LOG_DIR="${BUILD_ROOT}/log-files"
> >DL_DIR="/OE/downloads"
> >INSTALLER_EXTRAS_ROOT="/home/jenkins/extra-files/installer_content"
> >TEST_SCRIPTS="$SCRIPTS_ROOT/test-scripts"
> >TEST_SCRIPTS_TGT="home/root/test-scripts"
> >TEST_LOCAL_IFACE="eth1"
> >OPENTEST_CLI="$SCRIPTS_ROOT/opentest_cli_0.7.tar.gz"
> >OPENTEST_TEE_IP="10.218.102.142"
> >RUN_BUILD_TESTS="true"
> >STAF_ROOT="/usr/local/staf"
> >SKIP_TEST_FAILURES="false"
> >PRODUCTIZE_SDK="false"
> >BITBAKE_COMMAND="arago-core-tisdk-image"
> >RESULTS_CONFIG_COMMENTS="false"
> >INSTALL_JAMMER="/home/jenkins/installjammer"
> >INSTALLER_ROOT="$BUILD_ROOT/installer"
> >MPI_FILE="$SCRIPTS_ROOT/mpi-files/ti-sdk-base.mpi"
> >SD_CARD_CONTENT="/home/jenkins/extra-files/sd_content"
> >PACKAGE_BOOT_UIMAGE="false"
> >WEBGEN_ROOT="/home/jenkins/webgen"
> >WEB_EXTRAS_ROOT="/home/jenkins/extra-files/web_content"
> >WEBGEN_MAK_ROOT="$SCRIPTS_ROOT/publish-sdk-data"
> >COPY_TO_WEB="true"
> >WEB_HOST=""
> >CLEAN_AFTER_COPY="true"
> >BACKUP_RESULTS="/home/jenkins/jobs/arago-core-tisdk-nightly/workspace"
> >
> >
> >
> >_______________________________________________
> >meta-arago mailing list
> >meta-arago@arago-project.org
> >http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [nightly] Core TISDK 2013.06 build 2013-07-21_01-01-44

[Christian Gagneraud]

On 23/07/13 15:15, Denys Dmytriyenko wrote:
> Christian,
>
> On Tue, Jul 23, 2013 at 02:26:24PM +1200, Christian Gagneraud wrote:
>> Hi there,
>>
>> I have been looking at these test/build reports recently, is there a
>> more detail report available somewhere?
>
> Yes, but detailed reports are not yet published externally - it's on my
> "to do" list.

Good to hear, thanks! I have no strong needs for this, i was just 
curious about the am335x-evm test failures.

>
>
>> As a user of a am335x-evm and a BeagleBoard Black, I would like to
>> know more about test failure for the EVM.
>
> There are some issues with the boot sequence of an automated test - looks
> like it's trying to load a wrong kernel image, I'll look into it later.
> Otherwise, the latest Dylan build works and boots fine for me on am335x-evm
> when loaded manually on SD card.
>
>
>> As well, I'm considering moving from Arago/Danny (kernel 3.2) to
>> Arago/Dylan (kernel 3.8?). I would like to know if there are any
>> plan to use Dylan for the next stable Arago.
>
> Actually, Arago/Danny has been using kernel 3.8 for quite some time now - we
> already had couple internal releases with it. You would need to specifically
> request AM-SDK branding to get 3.2 kernel, as the default is 3.8 in Danny and
> in Dylan. The only change Dylan brings is to update the underlying Yocto
> framework with all the user-space apps to the latest versions.

Yes, that's right, Arago/Danny already use kernel 3.8. My mistake!
To be more precise, my question was related to QA stuff. For now, build 
and test automation are still done with Arago/Danny, any plan to switch 
to or add Arago/Dylan config?

On the side, any plan to add beaglebone and/or beaglebone-black to the 
list of machines used by your continuous integration systems?

>
>
>> Also, do you think it is conceivable to hope for a working Qt5 with
>> TI OpenGL stuff?
>
> It's in the plans. Prabu was able to get it built after some massaging, but
> there are still few issues. Also, we would need to make sure the fallback
> mechanism works for legacy devices w/o GLES, since Qt5 requires it...

Interesting! What I found so far:
  - https://github.com/prabindh/qt-configs
  - http://e2e.ti.com/search/default.aspx#q=qt5&g=29&sc=forum
  - and of course https://github.com/meta-qt5/meta-qt5, which depends on 
oe master :(

What I would like to achieve by the next months is to provide an 
{arago|angstrom|poxy}-danny-qt5 SDK and custom rootfs to the dev guys. 
Will see how it goes!

Regards,
Chris

Re: [nightly] Core TISDK 2013.06 build 2013-07-21_01-01-44

[Denys Dmytriyenko]

On Tue, Jul 23, 2013 at 04:43:54PM +1200, Christian Gagneraud wrote:
> On 23/07/13 15:15, Denys Dmytriyenko wrote:
> >Christian,
> >
> >On Tue, Jul 23, 2013 at 02:26:24PM +1200, Christian Gagneraud wrote:
> >>Hi there,
> >>
> >>I have been looking at these test/build reports recently, is there a
> >>more detail report available somewhere?
> >
> >Yes, but detailed reports are not yet published externally - it's on my
> >"to do" list.
> 
> Good to hear, thanks! I have no strong needs for this, i was just
> curious about the am335x-evm test failures.
> 
> >
> >
> >>As a user of a am335x-evm and a BeagleBoard Black, I would like to
> >>know more about test failure for the EVM.
> >
> >There are some issues with the boot sequence of an automated test - looks
> >like it's trying to load a wrong kernel image, I'll look into it later.
> >Otherwise, the latest Dylan build works and boots fine for me on am335x-evm
> >when loaded manually on SD card.
> >
> >
> >>As well, I'm considering moving from Arago/Danny (kernel 3.2) to
> >>Arago/Dylan (kernel 3.8?). I would like to know if there are any
> >>plan to use Dylan for the next stable Arago.
> >
> >Actually, Arago/Danny has been using kernel 3.8 for quite some time now - we
> >already had couple internal releases with it. You would need to specifically
> >request AM-SDK branding to get 3.2 kernel, as the default is 3.8 in Danny and
> >in Dylan. The only change Dylan brings is to update the underlying Yocto
> >framework with all the user-space apps to the latest versions.
> 
> Yes, that's right, Arago/Danny already use kernel 3.8. My mistake!
> To be more precise, my question was related to QA stuff. For now,
> build and test automation are still done with Arago/Danny, any plan
> to switch to or add Arago/Dylan config?

Yes, indeed - that's the next step. I still need to finish the devkit portion 
of our SDK, but otherwise everything seems to be getting ready to switch the 
nightly builds and tests to using Dylan.


> On the side, any plan to add beaglebone and/or beaglebone-black to
> the list of machines used by your continuous integration systems?

Starting with kernel 3.8, the only difference between AM335 EVM, EVM-SK and 
Beaglebone is in the devtree. When we build for am335x-evm, we copy all the 
DTBs, so the same images can be used on SK or Beaglebone. No need to build for 
those separately!

From a run-time testing perspective, those are obviously different tests on 
actual boards - I would need to check the board farm for proper setup. BTW, 
current nightly tests are sent to our internal board farm, which is shared. I 
am working on setting up my own personal board farm - I do have all the 
boards, I just need to whip our automation software in shape, which is not an 
easy task...


> >>Also, do you think it is conceivable to hope for a working Qt5 with
> >>TI OpenGL stuff?
> >
> >It's in the plans. Prabu was able to get it built after some massaging, but
> >there are still few issues. Also, we would need to make sure the fallback
> >mechanism works for legacy devices w/o GLES, since Qt5 requires it...
> 
> Interesting! What I found so far:
>  - https://github.com/prabindh/qt-configs
>  - http://e2e.ti.com/search/default.aspx#q=qt5&g=29&sc=forum
>  - and of course https://github.com/meta-qt5/meta-qt5, which depends
> on oe master :(
> 
> What I would like to achieve by the next months is to provide an
> {arago|angstrom|poxy}-danny-qt5 SDK and custom rootfs to the dev
> guys. Will see how it goes!

Let us know how it goes. And patches are welcome, as usual!

-- 
Denys

Re: [nightly] Core TISDK 2013.06 build 2013-07-21_01-01-44

[Denys Dmytriyenko]

On Tue, Jul 23, 2013 at 02:02:45AM -0400, Denys Dmytriyenko wrote:
> On Tue, Jul 23, 2013 at 04:43:54PM +1200, Christian Gagneraud wrote:
> > On 23/07/13 15:15, Denys Dmytriyenko wrote:
> > >Christian,
> > >
> > >On Tue, Jul 23, 2013 at 02:26:24PM +1200, Christian Gagneraud wrote:
> > >>Hi there,
> > >>
> > >>I have been looking at these test/build reports recently, is there a
> > >>more detail report available somewhere?
> > >
> > >Yes, but detailed reports are not yet published externally - it's on my
> > >"to do" list.
> > 
> > Good to hear, thanks! I have no strong needs for this, i was just
> > curious about the am335x-evm test failures.
> > 
> > >
> > >
> > >>As a user of a am335x-evm and a BeagleBoard Black, I would like to
> > >>know more about test failure for the EVM.
> > >
> > >There are some issues with the boot sequence of an automated test - looks
> > >like it's trying to load a wrong kernel image, I'll look into it later.
> > >Otherwise, the latest Dylan build works and boots fine for me on am335x-evm
> > >when loaded manually on SD card.

So, the issue with am335x-evm tests failining was identified as a bug in the 
test automation framework and our System Test engineers are working on the 
fix. For more details:

http://arago-project.org/pipermail/opentest/2013-July/002031.html


> > >>As well, I'm considering moving from Arago/Danny (kernel 3.2) to
> > >>Arago/Dylan (kernel 3.8?). I would like to know if there are any
> > >>plan to use Dylan for the next stable Arago.
> > >
> > >Actually, Arago/Danny has been using kernel 3.8 for quite some time now - we
> > >already had couple internal releases with it. You would need to specifically
> > >request AM-SDK branding to get 3.2 kernel, as the default is 3.8 in Danny and
> > >in Dylan. The only change Dylan brings is to update the underlying Yocto
> > >framework with all the user-space apps to the latest versions.
> > 
> > Yes, that's right, Arago/Danny already use kernel 3.8. My mistake!
> > To be more precise, my question was related to QA stuff. For now,
> > build and test automation are still done with Arago/Danny, any plan
> > to switch to or add Arago/Dylan config?
> 
> Yes, indeed - that's the next step. I still need to finish the devkit portion 
> of our SDK, but otherwise everything seems to be getting ready to switch the 
> nightly builds and tests to using Dylan.
> 
> 
> > On the side, any plan to add beaglebone and/or beaglebone-black to
> > the list of machines used by your continuous integration systems?
> 
> Starting with kernel 3.8, the only difference between AM335 EVM, EVM-SK and 
> Beaglebone is in the devtree. When we build for am335x-evm, we copy all the 
> DTBs, so the same images can be used on SK or Beaglebone. No need to build for 
> those separately!
> 
> From a run-time testing perspective, those are obviously different tests on 
> actual boards - I would need to check the board farm for proper setup. BTW, 
> current nightly tests are sent to our internal board farm, which is shared. I 
> am working on setting up my own personal board farm - I do have all the 
> boards, I just need to whip our automation software in shape, which is not an 
> easy task...
> 
> 
> > >>Also, do you think it is conceivable to hope for a working Qt5 with
> > >>TI OpenGL stuff?
> > >
> > >It's in the plans. Prabu was able to get it built after some massaging, but
> > >there are still few issues. Also, we would need to make sure the fallback
> > >mechanism works for legacy devices w/o GLES, since Qt5 requires it...
> > 
> > Interesting! What I found so far:
> >  - https://github.com/prabindh/qt-configs
> >  - http://e2e.ti.com/search/default.aspx#q=qt5&g=29&sc=forum
> >  - and of course https://github.com/meta-qt5/meta-qt5, which depends
> > on oe master :(
> > 
> > What I would like to achieve by the next months is to provide an
> > {arago|angstrom|poxy}-danny-qt5 SDK and custom rootfs to the dev
> > guys. Will see how it goes!
> 
> Let us know how it goes. And patches are welcome, as usual!
> 
> -- 
> Denys
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Re: [nightly] Core TISDK 2013.06 build 2013-07-21_01-01-44

[Christian Gagneraud]

On 23/07/13 18:02, Denys Dmytriyenko wrote:
> On Tue, Jul 23, 2013 at 04:43:54PM +1200, Christian Gagneraud wrote:
>> On 23/07/13 15:15, Denys Dmytriyenko wrote:
>>> Christian,
>>>
>>> On Tue, Jul 23, 2013 at 02:26:24PM +1200, Christian Gagneraud wrote:
>>>> Hi there,
>>>>
>>>> I have been looking at these test/build reports recently, is there a
>>>> more detail report available somewhere?
>>>
>>> Yes, but detailed reports are not yet published externally - it's on my
>>> "to do" list.
>>
>> Good to hear, thanks! I have no strong needs for this, i was just
>> curious about the am335x-evm test failures.
>>
>>>
>>>
>>>> As a user of a am335x-evm and a BeagleBoard Black, I would like to
>>>> know more about test failure for the EVM.
>>>
>>> There are some issues with the boot sequence of an automated test - looks
>>> like it's trying to load a wrong kernel image, I'll look into it later.
>>> Otherwise, the latest Dylan build works and boots fine for me on am335x-evm
>>> when loaded manually on SD card.
>>>
>>>
>>>> As well, I'm considering moving from Arago/Danny (kernel 3.2) to
>>>> Arago/Dylan (kernel 3.8?). I would like to know if there are any
>>>> plan to use Dylan for the next stable Arago.
>>>
>>> Actually, Arago/Danny has been using kernel 3.8 for quite some time now - we
>>> already had couple internal releases with it. You would need to specifically
>>> request AM-SDK branding to get 3.2 kernel, as the default is 3.8 in Danny and
>>> in Dylan. The only change Dylan brings is to update the underlying Yocto
>>> framework with all the user-space apps to the latest versions.
>>
>> Yes, that's right, Arago/Danny already use kernel 3.8. My mistake!
>> To be more precise, my question was related to QA stuff. For now,
>> build and test automation are still done with Arago/Danny, any plan
>> to switch to or add Arago/Dylan config?
>
> Yes, indeed - that's the next step. I still need to finish the devkit portion
> of our SDK, but otherwise everything seems to be getting ready to switch the
> nightly builds and tests to using Dylan.

I like it! :)

>
>
>> On the side, any plan to add beaglebone and/or beaglebone-black to
>> the list of machines used by your continuous integration systems?
>
> Starting with kernel 3.8, the only difference between AM335 EVM, EVM-SK and
> Beaglebone is in the devtree. When we build for am335x-evm, we copy all the
> DTBs, so the same images can be used on SK or Beaglebone. No need to build for
> those separately!

I did a build overnight using MACHINE=am335x-evm and yes I'm getting the 
DTBs for the evm, the evmsk and the bone (which supports both white and 
black, through the concept of capes if I'm not wrong).

I managed to boot the EVM from SD-Card (core-image-minimal with 
poky+meta-ti+meta-qt5/Dylan), the only manual thing I had to do so far 
was to rename uImage-am335x-evm.dtb to am335x-evm.dtb, because u-boot 
was expecting it this way.

My deployment on the SD-Card is done with:
cp u-boot.img MLO u-boot-spl.bin uImage $BOOTMNT
tar -C $ROOTMNT -xzvf core-image-minimal-am335x-evm.tar.gz
tar -C $BOOTMNT -xzvf modules--3.8.13-r0-am335x-evm-20130723061944.tgz
umount $ROOTMNT&
sudo cp -a uImage* $ROOTMNT/boot
umount $BOOTMNT&
wait

Unfortunately the modules tarball has no shortcut link, and the name 
contains a double '-' as something was missing:
christiaga@krys-red:~/projects/yocto/poky-ti-qt5/build/tmp/deploy/images$ ls 
-1 *--*
modules--3.8.13-r0-am335x-evm-20130723061944.tgz
uImage--3.8.13-r0-am335x-bone-20130723061944.dtb
uImage--3.8.13-r0-am335x-evm-20130723061944.bin
uImage--3.8.13-r0-am335x-evm-20130723061944.dtb
uImage--3.8.13-r0-am335x-evmsk-20130723061944.dtb

Not such a big deal though.


>
>  From a run-time testing perspective, those are obviously different tests on
> actual boards - I would need to check the board farm for proper setup. BTW,
> current nightly tests are sent to our internal board farm, which is shared. I
> am working on setting up my own personal board farm - I do have all the
> boards, I just need to whip our automation software in shape, which is not an
> easy task...

How much hardware is needed to setup a personal farm? I would be 
interested to have automated build and target test execution.
I started to have a look at tisdk-build-scripts and other stuff like 
jerkins, and having a "test farm" here is definitely on my radar.

>
>
>>>> Also, do you think it is conceivable to hope for a working Qt5 with
>>>> TI OpenGL stuff?
>>>
>>> It's in the plans. Prabu was able to get it built after some massaging, but
>>> there are still few issues. Also, we would need to make sure the fallback
>>> mechanism works for legacy devices w/o GLES, since Qt5 requires it...
>>
>> Interesting! What I found so far:
>>   - https://github.com/prabindh/qt-configs
>>   - http://e2e.ti.com/search/default.aspx#q=qt5&g=29&sc=forum
>>   - and of course https://github.com/meta-qt5/meta-qt5, which depends
>> on oe master :(

Actually meta-qt5 has a Dylan branch as well.

>>
>> What I would like to achieve by the next months is to provide an
>> {arago|angstrom|poxy}-danny-qt5 SDK and custom rootfs to the dev
>> guys. Will see how it goes!
>
> Let us know how it goes. And patches are welcome, as usual!

So far, I built a rootfs with Qt5 libs, the road is still long, long...

Regards,
Chris