yocto 1.6 - beaglebone black - cape manager

yocto 1.6 - beaglebone black - cape manager

[tomek82221 Gazeta.pl]

Hi
I'm build yocto 1.6, My hardware is beaglebone black I successfull
build system image. But I can't see cape manager.
I need them to use SPI - enable spidev -
http://elinux.org/BeagleBone_Black_Enable_SPIDEV .
What do i do to build yocto with a cape manager?

regards tt

Re: yocto 1.6 - beaglebone black - cape manager

[Diego Sueiro]

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

Hi Gazeta,

On Thu, Sep 4, 2014 at 5:48 PM, tomek82221 Gazeta.pl <tomek82221@gazeta.pl>
wrote:

> Hi
> I'm build yocto 1.6, My hardware is beaglebone black I successfull
> build system image. But I can't see cape manager.
> I need them to use SPI - enable spidev -
> http://elinux.org/BeagleBone_Black_Enable_SPIDEV .
> What do i do to build yocto with a cape manager?
>

As far as I know, you have to use meta-beagleboard
<https://github.com/beagleboard/meta-beagleboard> (almost 1 year without
any new commit) as your BSP layer to get capemanager support with Yocto.
Take a look here
<https://github.com/beagleboard/meta-beagleboard/blob/dylan/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb>.
The kernel version is 3.8.

Here we have good news of having capemanager support on mainline:
http://beagleboard.org/blog/2014-08-27-device-tree-overlay-support-lands-upstream/

Here you have a beaglebord.org linux repo with capemanager support:
https://github.com/beagleboard
I don't know if there is any WIP to get this kernel compiled by Yocto/OE.


Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br
<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/

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

Re: yocto 1.6 - beaglebone black - cape manager

[tomek82221 Gazeta.pl]

Can I use kernel version 3.8, meta-beagleboard as BSP layer in Yocto 1.6 ?
Here - https://www.yoctoproject.org/downloads/core/daisy16 is "Linux
kernel 3.14 and 3.10 LTSI "

I build yocto with
BBLAYERS ?= " \
  /home/fil/Pulpit/yocto/poky/meta \
  /home/fil/Pulpit/yocto/poky/meta-yocto \
  /home/fil/Pulpit/yocto/poky/meta-beagleboard/common-bsp \
  /home/fil/Pulpit/yocto/poky/meta-openembedded/meta-oe \
  "

have some errors:

ERROR: QA Issue: linux-mainline: Files/directories were installed but
not shipped
  /lib/firmware/sb16
  /lib/firmware/korg
  /lib/firmware/sb16/mulaw_main.csp
  /lib/firmware/sb16/alaw_main.csp
  /lib/firmware/sb16/ima_adpcm_init.csp
  /lib/firmware/sb16/ima_adpcm_capture.csp
  /lib/firmware/sb16/ima_adpcm_playback.csp
  /lib/firmware/korg/k1212.dsp
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa
ERROR: Logfile of failure stored in:
/home/fil/Pulpit/yocto/poky/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-mainline/3.8.13-r23a/temp/log.do_package.6509
NOTE: recipe linux-mainline-3.8.13-r23a: task do_package: Failed
ERROR: Task 88 (/home/fil/Pulpit/yocto/poky/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb,
do_package) failed with exit code '1'


2014-09-05 0:02 GMT+02:00 Diego Sueiro <diego.sueiro@gmail.com>:
> Hi Gazeta,
>
> On Thu, Sep 4, 2014 at 5:48 PM, tomek82221 Gazeta.pl <tomek82221@gazeta.pl>
> wrote:
>>
>> Hi
>> I'm build yocto 1.6, My hardware is beaglebone black I successfull
>> build system image. But I can't see cape manager.
>> I need them to use SPI - enable spidev -
>> http://elinux.org/BeagleBone_Black_Enable_SPIDEV .
>> What do i do to build yocto with a cape manager?
>
>
> As far as I know, you have to use meta-beagleboard (almost 1 year without
> any new commit) as your BSP layer to get capemanager support with Yocto.
> Take a look here. The kernel version is 3.8.
>
> Here we have good news of having capemanager support on mainline:
> http://beagleboard.org/blog/2014-08-27-device-tree-overlay-support-lands-upstream/
>
> Here you have a beaglebord.org linux repo with capemanager support:
> https://github.com/beagleboard
> I don't know if there is any WIP to get this kernel compiled by Yocto/OE.
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/

Re: yocto 1.6 - beaglebone black - cape manager

[Diego Sueiro]

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

Hi Chris,

On Mon, Sep 8, 2014 at 2:28 PM, tomek82221 Gazeta.pl <tomek82221@gazeta.pl>
wrote:

> Can I use kernel version 3.8, meta-beagleboard as BSP layer in Yocto 1.6 ?
>
Yes you can.

Here - https://www.yoctoproject.org/downloads/core/daisy16 is "Linux
> kernel 3.14 and 3.10 LTSI "
>
> I build yocto with
> BBLAYERS ?= " \
>   /home/fil/Pulpit/yocto/poky/meta \
>   /home/fil/Pulpit/yocto/poky/meta-yocto \
>   /home/fil/Pulpit/yocto/poky/meta-beagleboard/common-bsp \
>   /home/fil/Pulpit/yocto/poky/meta-openembedded/meta-oe \
>   "
>
> have some errors:
>
> ERROR: QA Issue: linux-mainline: Files/directories were installed but
> not shipped
>   /lib/firmware/sb16
>   /lib/firmware/korg
>   /lib/firmware/sb16/mulaw_main.csp
>   /lib/firmware/sb16/alaw_main.csp
>   /lib/firmware/sb16/ima_adpcm_init.csp
>   /lib/firmware/sb16/ima_adpcm_capture.csp
>   /lib/firmware/sb16/ima_adpcm_playback.csp
>   /lib/firmware/korg/k1212.dsp
> ERROR: QA run found fatal errors. Please consider fixing them.
> ERROR: Function failed: do_package_qa
> ERROR: Logfile of failure stored in:
>
> /home/fil/Pulpit/yocto/poky/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-mainline/3.8.13-r23a/temp/log.do_package.6509
> NOTE: recipe linux-mainline-3.8.13-r23a: task do_package: Failed
> ERROR: Task 88
> (/home/fil/Pulpit/yocto/poky/meta-beagleboard/common-bsp/recipes-kernel/linux/
> linux-mainline_3.8.bb,
> do_package) failed with exit code '1'
>

To solve this you can use a bbappend setting:

INSANE_SKIP_${PN} += "installed-vs-shipped"



Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br
<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/

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

Re: yocto 1.6 - beaglebone black - cape manager

[tomek82221 Gazeta.pl]

ok, but where i can add INSANE_SKIP_${PN} += "installed-vs-shipped"
in meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb ?
or create meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bbappend
?

thanks for your help



2014-09-09 2:38 GMT+02:00 Diego Sueiro <diego.sueiro@gmail.com>:
> Hi Chris,
>
> On Mon, Sep 8, 2014 at 2:28 PM, tomek82221 Gazeta.pl <tomek82221@gazeta.pl>
> wrote:
>>
>> Can I use kernel version 3.8, meta-beagleboard as BSP layer in Yocto 1.6 ?
>
> Yes you can.
>
>> Here - https://www.yoctoproject.org/downloads/core/daisy16 is "Linux
>> kernel 3.14 and 3.10 LTSI "
>>
>> I build yocto with
>> BBLAYERS ?= " \
>>   /home/fil/Pulpit/yocto/poky/meta \
>>   /home/fil/Pulpit/yocto/poky/meta-yocto \
>>   /home/fil/Pulpit/yocto/poky/meta-beagleboard/common-bsp \
>>   /home/fil/Pulpit/yocto/poky/meta-openembedded/meta-oe \
>>   "
>>
>> have some errors:
>>
>> ERROR: QA Issue: linux-mainline: Files/directories were installed but
>> not shipped
>>   /lib/firmware/sb16
>>   /lib/firmware/korg
>>   /lib/firmware/sb16/mulaw_main.csp
>>   /lib/firmware/sb16/alaw_main.csp
>>   /lib/firmware/sb16/ima_adpcm_init.csp
>>   /lib/firmware/sb16/ima_adpcm_capture.csp
>>   /lib/firmware/sb16/ima_adpcm_playback.csp
>>   /lib/firmware/korg/k1212.dsp
>> ERROR: QA run found fatal errors. Please consider fixing them.
>> ERROR: Function failed: do_package_qa
>> ERROR: Logfile of failure stored in:
>>
>> /home/fil/Pulpit/yocto/poky/build/tmp/work/beaglebone-poky-linux-gnueabi/linux-mainline/3.8.13-r23a/temp/log.do_package.6509
>> NOTE: recipe linux-mainline-3.8.13-r23a: task do_package: Failed
>> ERROR: Task 88
>> (/home/fil/Pulpit/yocto/poky/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb,
>> do_package) failed with exit code '1'
>
>
> To solve this you can use a bbappend setting:
>
> INSANE_SKIP_${PN} += "installed-vs-shipped"
>
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/

Re: yocto 1.6 - beaglebone black - cape manager

[Diego Sueiro]

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

On Tue, Sep 9, 2014 at 12:53 PM, tomek82221 Gazeta.pl <tomek82221@gazeta.pl>
wrote:

> ok, but where i can add INSANE_SKIP_${PN} += "installed-vs-shipped"
> in meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb
> ?
> or create
> meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bbappend
> ?
>
> thanks for your help
>

Both will work.


Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br
<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/

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

Re: yocto 1.6 - beaglebone black - cape manager

[TakkTakk]

yocto buit with INSANE_SKIP_${PN} += "installed-vs-shipped" with no error.
then i copied:
cp MLO /media/boot/MLO
cp u-boot-beaglebone.img /media/boot/u-boot.img
sudo tar -xvf core-image-base-beaglebone.tar.gz -C /media/root/

then, inserted microSD card to Beaglebone Black and bbb not boot. 4
led lit steadily and nothing happens. I have cable hdmi connected to
monitor.

then i did
$ cp uImage /media/boot
$ mkdir /media/boot/dtbs
$ cp uImage-am335x-boneblack.dtb /media/boot/dtbs/am335x-boneblack.dtb

$ cp uEnv.txt /media/boot

uEnv.txt from here
http://www.embarcados.com.br/beaglebone-black-yocto/ but i changed
zImage to uImage and still I can not boot the SD Card on the Beagle.
All four LEDs stay lit steadily.
What am i doing wrong?


2014-09-09 19:28 GMT+02:00 Diego Sueiro <diego.sueiro@gmail.com>:
>
> On Tue, Sep 9, 2014 at 12:53 PM, tomek82221 Gazeta.pl <tomek82221@gazeta.pl>
> wrote:
>>
>> ok, but where i can add INSANE_SKIP_${PN} += "installed-vs-shipped"
>> in meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb
>> ?
>> or create
>> meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bbappend
>> ?
>>
>> thanks for your help
>
>
> Both will work.
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/



-- 
TakTak

Re: yocto 1.6 - beaglebone black - cape manager

[Maciej Borzecki]

On 09/10 18:39, TakkTakk wrote:
> yocto buit with INSANE_SKIP_${PN} += "installed-vs-shipped" with no error.
> then i copied:
> cp MLO /media/boot/MLO
> cp u-boot-beaglebone.img /media/boot/u-boot.img
> sudo tar -xvf core-image-base-beaglebone.tar.gz -C /media/root/
>
> then, inserted microSD card to Beaglebone Black and bbb not boot. 4
> led lit steadily and nothing happens. I have cable hdmi connected to
> monitor.
>
> then i did
> $ cp uImage /media/boot
> $ mkdir /media/boot/dtbs
> $ cp uImage-am335x-boneblack.dtb /media/boot/dtbs/am335x-boneblack.dtb
>
> $ cp uEnv.txt /media/boot
>
> uEnv.txt from here
> http://www.embarcados.com.br/beaglebone-black-yocto/ but i changed
> zImage to uImage and still I can not boot the SD Card on the Beagle.
> All four LEDs stay lit steadily.
> What am i doing wrong?

Can you list the layers enabled in your build and post serial console
output?

Issues that I've seen so far:
- SD card layout (even block count of boot partition, try checking
meta-ti archive for my posts)
- uboot not restoring partition sizes (but I've only seen it on meta-ti
master, Peter Bigot posted a patch that fixed the problem, AFAIK the
patch should already be meta-ti, affected uboot 2014.07)
- kernel overwriting device tree in mem,
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6165 but apparently
it's already fixed in master & 1.6.1

>
>
> 2014-09-09 19:28 GMT+02:00 Diego Sueiro <diego.sueiro@gmail.com>:
> >
> > On Tue, Sep 9, 2014 at 12:53 PM, tomek82221 Gazeta.pl <tomek82221@gazeta.pl>
> > wrote:
> >>
> >> ok, but where i can add INSANE_SKIP_${PN} += "installed-vs-shipped"
> >> in meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb
> >> ?
> >> or create
> >> meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bbappend
> >> ?
> >>
> >> thanks for your help
> >
> >
> > Both will work.
> >
> >
> > Regards,
> >
> > --
> > *dS
> > Diego Sueiro
> >
> > Administrador do Embarcados
> > www.embarcados.com.br
> >
> > /*long live rock 'n roll*/
>
>
>
> --
> TakTak
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--
Maciej Borzęcki
Senior Software Developer at Open-RnD Sp. z o.o., Poland
www.open-rnd.pl
mobile: +48 889 117 365, fax: +48 42 657 9079


Niniejsza wiadomość wraz z załącznikami może
zawierać chronione prawem lub poufne informacje i została
wysłana wyłącznie do wiadomości i użytku osób, do których
została zaadresowana. Jeśli wiadomość została otrzymana
przypadkowo zabrania się jej kopiowania lub rozsyłania do osób
trzecich. W takim przypadku uprasza się o natychmiastowe
zniszczenie wiadomości oraz poinformowanie nadawcy o
zaistniałej sytuacji za pomocą wiadomości zwrotnej.
Dziękujemy.

This message, including any attachments hereto,
may contain privileged or confidential information and is sent
solely for the attention and use of the intended addressee(s).
If you are not an intended addressee, you may neither use this
message nor copy or deliver it to anyone. In such case, you
should immediately destroy this message and kindly notify the
sender by reply email. Thank you.

Re: yocto 1.6 - beaglebone black - cape manager

[TakkTakk]

Layers :
BBLAYERS ?= " \
  /home/fil/Pulpit/yocto/poky/meta \
  /home/fil/Pulpit/yocto/poky/meta-yocto \
  /home/fil/Pulpit/yocto/poky/meta-beagleboard/common-bsp \
  /home/fil/Pulpit/yocto/poky/meta-openembedded/meta-oe \
  /home/fil/Pulpit/yocto/poky/meta-beagleboard/meta-beagleboard-extras \
  /home/fil/Pulpit/yocto/poky/meta-hello \
  "

I can't open serial console.

2014-09-10 20:33 GMT+02:00 Maciej Borzecki <maciej.borzecki@open-rnd.pl>:
> On 09/10 18:39, TakkTakk wrote:
>> yocto buit with INSANE_SKIP_${PN} += "installed-vs-shipped" with no error.
>> then i copied:
>> cp MLO /media/boot/MLO
>> cp u-boot-beaglebone.img /media/boot/u-boot.img
>> sudo tar -xvf core-image-base-beaglebone.tar.gz -C /media/root/
>>
>> then, inserted microSD card to Beaglebone Black and bbb not boot. 4
>> led lit steadily and nothing happens. I have cable hdmi connected to
>> monitor.
>>
>> then i did
>> $ cp uImage /media/boot
>> $ mkdir /media/boot/dtbs
>> $ cp uImage-am335x-boneblack.dtb /media/boot/dtbs/am335x-boneblack.dtb
>>
>> $ cp uEnv.txt /media/boot
>>
>> uEnv.txt from here
>> http://www.embarcados.com.br/beaglebone-black-yocto/ but i changed
>> zImage to uImage and still I can not boot the SD Card on the Beagle.
>> All four LEDs stay lit steadily.
>> What am i doing wrong?
>
> Can you list the layers enabled in your build and post serial console
> output?
>
> Issues that I've seen so far:
> - SD card layout (even block count of boot partition, try checking
> meta-ti archive for my posts)
> - uboot not restoring partition sizes (but I've only seen it on meta-ti
> master, Peter Bigot posted a patch that fixed the problem, AFAIK the
> patch should already be meta-ti, affected uboot 2014.07)
> - kernel overwriting device tree in mem,
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=6165 but apparently
> it's already fixed in master & 1.6.1
>
>>
>>
>> 2014-09-09 19:28 GMT+02:00 Diego Sueiro <diego.sueiro@gmail.com>:
>> >
>> > On Tue, Sep 9, 2014 at 12:53 PM, tomek82221 Gazeta.pl <tomek82221@gazeta.pl>
>> > wrote:
>> >>
>> >> ok, but where i can add INSANE_SKIP_${PN} += "installed-vs-shipped"
>> >> in meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb
>> >> ?
>> >> or create
>> >> meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bbappend
>> >> ?
>> >>
>> >> thanks for your help
>> >
>> >
>> > Both will work.
>> >
>> >
>> > Regards,
>> >
>> > --
>> > *dS
>> > Diego Sueiro
>> >
>> > Administrador do Embarcados
>> > www.embarcados.com.br
>> >
>> > /*long live rock 'n roll*/
>>
>>
>>
>> --
>> TakTak
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
> --
> Maciej Borzęcki
> Senior Software Developer at Open-RnD Sp. z o.o., Poland
> www.open-rnd.pl
> mobile: +48 889 117 365, fax: +48 42 657 9079
>
>
> Niniejsza wiadomość wraz z załącznikami może
> zawierać chronione prawem lub poufne informacje i została
> wysłana wyłącznie do wiadomości i użytku osób, do których
> została zaadresowana. Jeśli wiadomość została otrzymana
> przypadkowo zabrania się jej kopiowania lub rozsyłania do osób
> trzecich. W takim przypadku uprasza się o natychmiastowe
> zniszczenie wiadomości oraz poinformowanie nadawcy o
> zaistniałej sytuacji za pomocą wiadomości zwrotnej.
> Dziękujemy.
>
> This message, including any attachments hereto,
> may contain privileged or confidential information and is sent
> solely for the attention and use of the intended addressee(s).
> If you are not an intended addressee, you may neither use this
> message nor copy or deliver it to anyone. In such case, you
> should immediately destroy this message and kindly notify the
> sender by reply email. Thank you.



-- 
TakTak

Re: yocto 1.6 - beaglebone black - cape manager

[Diego Sueiro]

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

TakTak,

On Wed, Sep 10, 2014 at 1:39 PM, TakkTakk <tomek82221@gazeta.pl> wrote:

> yocto buit with INSANE_SKIP_${PN} += "installed-vs-shipped" with no error.
> then i copied:
> cp MLO /media/boot/MLO
> cp u-boot-beaglebone.img /media/boot/u-boot.img
> sudo tar -xvf core-image-base-beaglebone.tar.gz -C /media/root/
>
> then, inserted microSD card to Beaglebone Black and bbb not boot. 4
> led lit steadily and nothing happens. I have cable hdmi connected to
> monitor.
>
> then i did
> $ cp uImage /media/boot
> $ mkdir /media/boot/dtbs
> $ cp uImage-am335x-boneblack.dtb /media/boot/dtbs/am335x-boneblack.dtb
>
> $ cp uEnv.txt /media/boot
>
> uEnv.txt from here
> http://www.embarcados.com.br/beaglebone-black-yocto/ but i changed
> zImage to uImage and still I can not boot the SD Card on the Beagle.
> All four LEDs stay lit steadily.
> What am i doing wrong?
>

Do you have another image installed on eMMC? If yes try to power up the
board with sdcard inserted and the switch S2 pressed (near sdcard slot).


Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br
<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/

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

Re: yocto 1.6 - beaglebone black - cape manager

[TakkTakk]

Yes I have ubuntu on eMMC, when i don't press S2 ubuntu will be boot.
When i press switch S2 yocto don't boot and LED USR0 , USR1, USR2,
USR3 stay lit steadily.
I boot yocto 1.6 (but without layer meta-beagleboard) on sdcard and
everything was ok.

2014-09-11 11:19 GMT+02:00 Diego Sueiro <diego.sueiro@gmail.com>:
> TakTak,
>
> On Wed, Sep 10, 2014 at 1:39 PM, TakkTakk <tomek82221@gazeta.pl> wrote:
>>
>> yocto buit with INSANE_SKIP_${PN} += "installed-vs-shipped" with no error.
>> then i copied:
>> cp MLO /media/boot/MLO
>> cp u-boot-beaglebone.img /media/boot/u-boot.img
>> sudo tar -xvf core-image-base-beaglebone.tar.gz -C /media/root/
>>
>> then, inserted microSD card to Beaglebone Black and bbb not boot. 4
>> led lit steadily and nothing happens. I have cable hdmi connected to
>> monitor.
>>
>> then i did
>> $ cp uImage /media/boot
>> $ mkdir /media/boot/dtbs
>> $ cp uImage-am335x-boneblack.dtb /media/boot/dtbs/am335x-boneblack.dtb
>>
>> $ cp uEnv.txt /media/boot
>>
>> uEnv.txt from here
>> http://www.embarcados.com.br/beaglebone-black-yocto/ but i changed
>> zImage to uImage and still I can not boot the SD Card on the Beagle.
>> All four LEDs stay lit steadily.
>> What am i doing wrong?
>
>
> Do you have another image installed on eMMC? If yes try to power up the
> board with sdcard inserted and the switch S2 pressed (near sdcard slot).
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/

Re: yocto 1.6 - beaglebone black - cape manager

[Diego Sueiro]

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

On Thu, Sep 11, 2014 at 10:24 AM, TakkTakk <tomek82221@gazeta.pl> wrote:

> Yes I have ubuntu on eMMC, when i don't press S2 ubuntu will be boot.
> When i press switch S2 yocto don't boot and LED USR0 , USR1, USR2,
> USR3 stay lit steadily.
> I boot yocto 1.6 (but without layer meta-beagleboard) on sdcard and
> everything was ok.
>

Without the console serial cable (on UART0) is hard to guess what's going
wrong.

What is your o uEnv.txt content and the files inside the FAT partition?


Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br
<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/

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

Re: yocto 1.6 - beaglebone black - cape manager

[TakkTakk]

i build core-image-base
My uEnv.txt content :

kernel_file=uImage
console=ttyO0,115200n8
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext4 rootwait

loaduimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}

mmcargs=setenv bootargs console=${console} root=${mmcroot}
rootfstype=${mmcrootfstype} ${optargs}
uenvcmd=run loaduimage; run loadfdt; run mmcargs; bootz ${loadaddr} - ${fdtaddr}

optargs=quiet drm.debug=7 capemgr.enable_partno=BB-UART4
--------------------------------------

files inside the FAT partition:
uEnv.txt
uImage
u-boot.img
MLO
dtbs/am335x-boneblack.dtb



2014-09-12 11:55 GMT+02:00 Diego Sueiro <diego.sueiro@gmail.com>:
>
> On Thu, Sep 11, 2014 at 10:24 AM, TakkTakk <tomek82221@gazeta.pl> wrote:
>>
>> Yes I have ubuntu on eMMC, when i don't press S2 ubuntu will be boot.
>> When i press switch S2 yocto don't boot and LED USR0 , USR1, USR2,
>> USR3 stay lit steadily.
>> I boot yocto 1.6 (but without layer meta-beagleboard) on sdcard and
>> everything was ok.
>
>
> Without the console serial cable (on UART0) is hard to guess what's going
> wrong.
>
> What is your o uEnv.txt content and the files inside the FAT partition?
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/



-- 
TakTak

Re: yocto 1.6 - beaglebone black - cape manager

[Diego Sueiro]

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

On Fri, Sep 12, 2014 at 6:59 PM, TakkTakk <tomek82221@gazeta.pl> wrote:

> i build core-image-base
> My uEnv.txt content :
>
> kernel_file=uImage
> console=ttyO0,115200n8
> mmcroot=/dev/mmcblk0p2 rw
> mmcrootfstype=ext4 rootwait
>
> loaduimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
> loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
>
> mmcargs=setenv bootargs console=${console} root=${mmcroot}
> rootfstype=${mmcrootfstype} ${optargs}
> uenvcmd=run loaduimage; run loadfdt; run mmcargs; bootz ${loadaddr} -
> ${fdtaddr}
>

I think that the problem is the "bootz" command. This command is used to
boot zImage kernel. Change it to "bootm" and don't forget to keep the S2
switch pressed.
But again. With a console serial cable is easier to find what is going
wrong.


>
> optargs=quiet drm.debug=7 capemgr.enable_partno=BB-UART4
> --------------------------------------
>
> files inside the FAT partition:
> uEnv.txt
> uImage
> u-boot.img
> MLO
> dtbs/am335x-boneblack.dtb
>



Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br
<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/

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

Re: yocto 1.6 - beaglebone black - cape manager

[TakkTakk]

ok, i changed "bootz" to "bootm" and i kept S2 swith pressed.
Yocto not booting, two leds D2, D3 is shining.

Serial console output:

U-Boot SPL 2013.04-dirty (Sep 09 2014 - 21:38:22)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2013.04-dirty (Sep 09 2014 - 21:38:22)

I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
527 bytes read in 4 ms (127.9 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
reading uImage
4368264 bytes read in 499 ms (8.3 MiB/s)
reading /dtbs/am335x-boneblack.dtb
29192 bytes read in 10 ms (2.8 MiB/s)
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-3.8.13
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4368200 Bytes = 4.2 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   Loading Kernel Image ... OK
OK
   Using Device Tree in place at 80f80000, end 80f8a207

Starting kernel ...

Uncompressing Linux... done, booting the kernel.




2014-09-13 11:26 GMT+02:00 Diego Sueiro <diego.sueiro@gmail.com>:
>
> On Fri, Sep 12, 2014 at 6:59 PM, TakkTakk <tomek82221@gazeta.pl> wrote:
>>
>> i build core-image-base
>> My uEnv.txt content :
>>
>> kernel_file=uImage
>> console=ttyO0,115200n8
>> mmcroot=/dev/mmcblk0p2 rw
>> mmcrootfstype=ext4 rootwait
>>
>> loaduimage=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
>> loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
>>
>> mmcargs=setenv bootargs console=${console} root=${mmcroot}
>> rootfstype=${mmcrootfstype} ${optargs}
>> uenvcmd=run loaduimage; run loadfdt; run mmcargs; bootz ${loadaddr} -
>> ${fdtaddr}
>
>
> I think that the problem is the "bootz" command. This command is used to
> boot zImage kernel. Change it to "bootm" and don't forget to keep the S2
> switch pressed.
> But again. With a console serial cable is easier to find what is going
> wrong.
>
>>
>>
>> optargs=quiet drm.debug=7 capemgr.enable_partno=BB-UART4
>> --------------------------------------
>>
>> files inside the FAT partition:
>> uEnv.txt
>> uImage
>> u-boot.img
>> MLO
>> dtbs/am335x-boneblack.dtb
>
>
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/



-- 
TakTak

Re: yocto 1.6 - beaglebone black - cape manager

[Diego Sueiro]

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

Takk,

On Wed, Sep 24, 2014 at 5:20 PM, TakkTakk <tomek82221@gazeta.pl> wrote:

> ok, i changed "bootz" to "bootm" and i kept S2 swith pressed.
> Yocto not booting, two leds D2, D3 is shining.
>
> Serial console output:
>
> U-Boot SPL 2013.04-dirty (Sep 09 2014 - 21:38:22)
> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> SoftConn)
> musb-hdrc: MHDRC RTL version 2.0
> musb-hdrc: setup fifo_mode 4
> musb-hdrc: 28/31 max ep, 16384/16384 memory
> USB Peripheral mode controller at 47401000 using PIO, IRQ 0
> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> SoftConn)
> musb-hdrc: MHDRC RTL version 2.0
> musb-hdrc: setup fifo_mode 4
> musb-hdrc: 28/31 max ep, 16384/16384 memory
> USB Host mode controller at 47401800 using PIO, IRQ 0
> OMAP SD/MMC: 0
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2013.04-dirty (Sep 09 2014 - 21:38:22)
>
> I2C:   ready
> DRAM:  512 MiB
> WARNING: Caches not enabled
> NAND:  No NAND device found!!!
> 0 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> *** Warning - readenv() failed, using default environment
>
> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> SoftConn)
> musb-hdrc: MHDRC RTL version 2.0
> musb-hdrc: setup fifo_mode 4
> musb-hdrc: 28/31 max ep, 16384/16384 memory
> USB Peripheral mode controller at 47401000 using PIO, IRQ 0
> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> SoftConn)
> musb-hdrc: MHDRC RTL version 2.0
> musb-hdrc: setup fifo_mode 4
> musb-hdrc: 28/31 max ep, 16384/16384 memory
> USB Host mode controller at 47401800 using PIO, IRQ 0
> Net:   <ethaddr> not set. Validating first E-fuse MAC
> cpsw, usb_ether
> Hit any key to stop autoboot:  0
> gpio: pin 53 (gpio 53) value is 1
> mmc0 is current device
> micro SD card found
> mmc0 is current device
> gpio: pin 54 (gpio 54) value is 1
> SD/MMC found on device 0
> reading uEnv.txt
> 527 bytes read in 4 ms (127.9 KiB/s)
> Loaded environment from uEnv.txt
> Importing environment from mmc ...
> Running uenvcmd ...
> reading uImage
> 4368264 bytes read in 499 ms (8.3 MiB/s)
> reading /dtbs/am335x-boneblack.dtb
> 29192 bytes read in 10 ms (2.8 MiB/s)
> ## Booting kernel from Legacy Image at 80200000 ...
>    Image Name:   Linux-3.8.13
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    4368200 Bytes = 4.2 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
> ## Flattened Device Tree blob at 80f80000
>    Booting using the fdt blob at 0x80f80000
>    Loading Kernel Image ... OK
> OK
>    Using Device Tree in place at 80f80000, end 80f8a207
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>

Hummm. That's strange.
I don't know if kernel 3.8.13 populate the serial debug interface as ttyO0
or ttyS0.

I think you can remove your uEnv.txt file from FAT partition and powerup
the board by pressing the boot switch,
The u-boot from meta-beagleboard doesn't need any extra configuration.


Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br
<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/

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

Re: yocto 1.6 - beaglebone black - cape manager

[Maciej Borzecki]

On Thursday 25 of September 2014 09:18:07 Diego Sueiro wrote:
> Takk,
> 
> On Wed, Sep 24, 2014 at 5:20 PM, TakkTakk <tomek82221@gazeta.pl> wrote:
> > ok, i changed "bootz" to "bootm" and i kept S2 swith pressed.
> > Yocto not booting, two leds D2, D3 is shining.
> > 
> > Serial console output:
> > 
> > U-Boot SPL 2013.04-dirty (Sep 09 2014 - 21:38:22)
> > musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> > SoftConn)
> > musb-hdrc: MHDRC RTL version 2.0
> > musb-hdrc: setup fifo_mode 4
> > musb-hdrc: 28/31 max ep, 16384/16384 memory
> > USB Peripheral mode controller at 47401000 using PIO, IRQ 0
> > musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> > SoftConn)
> > musb-hdrc: MHDRC RTL version 2.0
> > musb-hdrc: setup fifo_mode 4
> > musb-hdrc: 28/31 max ep, 16384/16384 memory
> > USB Host mode controller at 47401800 using PIO, IRQ 0
> > OMAP SD/MMC: 0
> > reading u-boot.img
> > reading u-boot.img
> > 
> > 
> > U-Boot 2013.04-dirty (Sep 09 2014 - 21:38:22)
> > 
> > I2C:   ready
> > DRAM:  512 MiB
> > WARNING: Caches not enabled
> > NAND:  No NAND device found!!!
> > 0 MiB
> > MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> > *** Warning - readenv() failed, using default environment
> > 
> > musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> > SoftConn)
> > musb-hdrc: MHDRC RTL version 2.0
> > musb-hdrc: setup fifo_mode 4
> > musb-hdrc: 28/31 max ep, 16384/16384 memory
> > USB Peripheral mode controller at 47401000 using PIO, IRQ 0
> > musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> > SoftConn)
> > musb-hdrc: MHDRC RTL version 2.0
> > musb-hdrc: setup fifo_mode 4
> > musb-hdrc: 28/31 max ep, 16384/16384 memory
> > USB Host mode controller at 47401800 using PIO, IRQ 0
> > Net:   <ethaddr> not set. Validating first E-fuse MAC
> > cpsw, usb_ether
> > Hit any key to stop autoboot:  0
> > gpio: pin 53 (gpio 53) value is 1
> > mmc0 is current device
> > micro SD card found
> > mmc0 is current device
> > gpio: pin 54 (gpio 54) value is 1
> > SD/MMC found on device 0
> > reading uEnv.txt
> > 527 bytes read in 4 ms (127.9 KiB/s)
> > Loaded environment from uEnv.txt
> > Importing environment from mmc ...
> > Running uenvcmd ...
> > reading uImage
> > 4368264 bytes read in 499 ms (8.3 MiB/s)
> > reading /dtbs/am335x-boneblack.dtb
> > 29192 bytes read in 10 ms (2.8 MiB/s)
> > ## Booting kernel from Legacy Image at 80200000 ...
> > 
> >    Image Name:   Linux-3.8.13
> >    Image Type:   ARM Linux Kernel Image (uncompressed)
> >    Data Size:    4368200 Bytes = 4.2 MiB
> >    Load Address: 80008000
> >    Entry Point:  80008000
> >    Verifying Checksum ... OK
> > 
> > ## Flattened Device Tree blob at 80f80000
> > 
> >    Booting using the fdt blob at 0x80f80000
> >    Loading Kernel Image ... OK
> > 
> > OK
> > 
> >    Using Device Tree in place at 80f80000, end 80f8a207
> > 
> > Starting kernel ...
> > 
> > Uncompressing Linux... done, booting the kernel.
> 
> Hummm. That's strange.
> I don't know if kernel 3.8.13 populate the serial debug interface as ttyO0
> or ttyS0.

You could try console=ttyS0 or console=ttyO0 in kernel command line.
 
> 
> I think you can remove your uEnv.txt file from FAT partition and powerup
> the board by pressing the boot switch,
> The u-boot from meta-beagleboard doesn't need any extra configuration.


> 
> 
> Regards,
> 
> --
> *dS
> Diego Sueiro
> 
> Administrador do Embarcados
> www.embarcados.com.br
> <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail
> &utm_campaign=Assinatura%20Email%20Diego>
> 
> /*long live rock 'n roll*/

-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you.

Re: yocto 1.6 - beaglebone black - cape manager

[TakkTakk]

ok, I removed uEnv.txt, pressed the boot switch.
Starting kernel ... and hang.
why - "Image Name:   Linux-3.14.0-yocto-standard " ?

U-Boot SPL 2013.04-dirty (Sep 09 2014 - 21:38:22)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2013.04-dirty (Sep 09 2014 - 21:38:22)

I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
** Unable to read file uEnv.txt **
gpio: pin 55 (gpio 55) value is 1
4985736 bytes read in 957 ms (5 MiB/s)
gpio: pin 56 (gpio 56) value is 1
24868 bytes read in 92 ms (263.7 KiB/s)
Booting from mmc ...
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.14.0-yocto-standard
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4985672 Bytes = 4.8 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   XIP Kernel Image ... OK
OK
   Using Device Tree in place at 80f80000, end 80f89123

Starting kernel ...

2014-09-25 14:18 GMT+02:00 Diego Sueiro <diego.sueiro@gmail.com>:
> Takk,
>
> On Wed, Sep 24, 2014 at 5:20 PM, TakkTakk <tomek82221@gazeta.pl> wrote:
>>
>> ok, i changed "bootz" to "bootm" and i kept S2 swith pressed.
>> Yocto not booting, two leds D2, D3 is shining.
>>
>> Serial console output:
>>
>> U-Boot SPL 2013.04-dirty (Sep 09 2014 - 21:38:22)
>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
>> SoftConn)
>> musb-hdrc: MHDRC RTL version 2.0
>> musb-hdrc: setup fifo_mode 4
>> musb-hdrc: 28/31 max ep, 16384/16384 memory
>> USB Peripheral mode controller at 47401000 using PIO, IRQ 0
>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
>> SoftConn)
>> musb-hdrc: MHDRC RTL version 2.0
>> musb-hdrc: setup fifo_mode 4
>> musb-hdrc: 28/31 max ep, 16384/16384 memory
>> USB Host mode controller at 47401800 using PIO, IRQ 0
>> OMAP SD/MMC: 0
>> reading u-boot.img
>> reading u-boot.img
>>
>>
>> U-Boot 2013.04-dirty (Sep 09 2014 - 21:38:22)
>>
>> I2C:   ready
>> DRAM:  512 MiB
>> WARNING: Caches not enabled
>> NAND:  No NAND device found!!!
>> 0 MiB
>> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
>> *** Warning - readenv() failed, using default environment
>>
>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
>> SoftConn)
>> musb-hdrc: MHDRC RTL version 2.0
>> musb-hdrc: setup fifo_mode 4
>> musb-hdrc: 28/31 max ep, 16384/16384 memory
>> USB Peripheral mode controller at 47401000 using PIO, IRQ 0
>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
>> SoftConn)
>> musb-hdrc: MHDRC RTL version 2.0
>> musb-hdrc: setup fifo_mode 4
>> musb-hdrc: 28/31 max ep, 16384/16384 memory
>> USB Host mode controller at 47401800 using PIO, IRQ 0
>> Net:   <ethaddr> not set. Validating first E-fuse MAC
>> cpsw, usb_ether
>> Hit any key to stop autoboot:  0
>> gpio: pin 53 (gpio 53) value is 1
>> mmc0 is current device
>> micro SD card found
>> mmc0 is current device
>> gpio: pin 54 (gpio 54) value is 1
>> SD/MMC found on device 0
>> reading uEnv.txt
>> 527 bytes read in 4 ms (127.9 KiB/s)
>> Loaded environment from uEnv.txt
>> Importing environment from mmc ...
>> Running uenvcmd ...
>> reading uImage
>> 4368264 bytes read in 499 ms (8.3 MiB/s)
>> reading /dtbs/am335x-boneblack.dtb
>> 29192 bytes read in 10 ms (2.8 MiB/s)
>> ## Booting kernel from Legacy Image at 80200000 ...
>>    Image Name:   Linux-3.8.13
>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>    Data Size:    4368200 Bytes = 4.2 MiB
>>    Load Address: 80008000
>>    Entry Point:  80008000
>>    Verifying Checksum ... OK
>> ## Flattened Device Tree blob at 80f80000
>>    Booting using the fdt blob at 0x80f80000
>>    Loading Kernel Image ... OK
>> OK
>>    Using Device Tree in place at 80f80000, end 80f8a207
>>
>> Starting kernel ...
>>
>> Uncompressing Linux... done, booting the kernel.
>
>
> Hummm. That's strange.
> I don't know if kernel 3.8.13 populate the serial debug interface as ttyO0
> or ttyS0.
>
> I think you can remove your uEnv.txt file from FAT partition and powerup the
> board by pressing the boot switch,
> The u-boot from meta-beagleboard doesn't need any extra configuration.
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/



-- 
TakTak

Re: yocto 1.6 - beaglebone black - cape manager

[Maciej Borzecki]

On Friday 26 of September 2014 15:17:52 TakkTakk wrote:
> ok, I removed uEnv.txt, pressed the boot switch.
> Starting kernel ... and hang.
> why - "Image Name:   Linux-3.14.0-yocto-standard " ?

I'd recommend switching to current master (what is to be 1.7 soon), skipping 
meta-beaglebone for now and build core-image-minimal. Then prepare SD card 
image either manually or with wic and try booting that. I'm doing such builds 
every couple of days, so far without too many problems.

Once you get that working, add meta-beaglebone layer, handpick kernel/u-boot 
versions if needed, add whatever extra packages you need. Best if you do it 
step by step.

> 
> U-Boot SPL 2013.04-dirty (Sep 09 2014 - 21:38:22)
> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> SoftConn) musb-hdrc: MHDRC RTL version 2.0
> musb-hdrc: setup fifo_mode 4
> musb-hdrc: 28/31 max ep, 16384/16384 memory
> USB Peripheral mode controller at 47401000 using PIO, IRQ 0
> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> SoftConn) musb-hdrc: MHDRC RTL version 2.0
> musb-hdrc: setup fifo_mode 4
> musb-hdrc: 28/31 max ep, 16384/16384 memory
> USB Host mode controller at 47401800 using PIO, IRQ 0
> OMAP SD/MMC: 0
> reading u-boot.img
> reading u-boot.img
> 
> 
> U-Boot 2013.04-dirty (Sep 09 2014 - 21:38:22)
> 
> I2C:   ready
> DRAM:  512 MiB
> WARNING: Caches not enabled
> NAND:  No NAND device found!!!
> 0 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> *** Warning - readenv() failed, using default environment
> 
> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> SoftConn)
> musb-hdrc: MHDRC RTL version 2.0
> musb-hdrc: setup fifo_mode 4
> musb-hdrc: 28/31 max ep, 16384/16384 memory
> USB Peripheral mode controller at 47401000 using PIO, IRQ 0
> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> SoftConn)
> musb-hdrc: MHDRC RTL version 2.0
> musb-hdrc: setup fifo_mode 4
> musb-hdrc: 28/31 max ep, 16384/16384 memory
> USB Host mode controller at 47401800 using PIO, IRQ 0
> Net:   <ethaddr> not set. Validating first E-fuse MAC
> cpsw, usb_ether
> Hit any key to stop autoboot:  0
> gpio: pin 53 (gpio 53) value is 1
> mmc0 is current device
> micro SD card found
> mmc0 is current device
> gpio: pin 54 (gpio 54) value is 1
> SD/MMC found on device 0
> reading uEnv.txt
> ** Unable to read file uEnv.txt **
> gpio: pin 55 (gpio 55) value is 1
> 4985736 bytes read in 957 ms (5 MiB/s)
> gpio: pin 56 (gpio 56) value is 1
> 24868 bytes read in 92 ms (263.7 KiB/s)
> Booting from mmc ...
> ## Booting kernel from Legacy Image at 80007fc0 ...
>    Image Name:   Linux-3.14.0-yocto-standard
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    4985672 Bytes = 4.8 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
> ## Flattened Device Tree blob at 80f80000
>    Booting using the fdt blob at 0x80f80000
>    XIP Kernel Image ... OK
> OK
>    Using Device Tree in place at 80f80000, end 80f89123
> 
> Starting kernel ...
> 
> 2014-09-25 14:18 GMT+02:00 Diego Sueiro <diego.sueiro@gmail.com>:
> > Takk,
> > 
> > On Wed, Sep 24, 2014 at 5:20 PM, TakkTakk <tomek82221@gazeta.pl> wrote:
> >> ok, i changed "bootz" to "bootm" and i kept S2 swith pressed.
> >> Yocto not booting, two leds D2, D3 is shining.
> >> 
> >> Serial console output:
> >> 
> >> U-Boot SPL 2013.04-dirty (Sep 09 2014 - 21:38:22)
> >> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> >> SoftConn)
> >> musb-hdrc: MHDRC RTL version 2.0
> >> musb-hdrc: setup fifo_mode 4
> >> musb-hdrc: 28/31 max ep, 16384/16384 memory
> >> USB Peripheral mode controller at 47401000 using PIO, IRQ 0
> >> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> >> SoftConn)
> >> musb-hdrc: MHDRC RTL version 2.0
> >> musb-hdrc: setup fifo_mode 4
> >> musb-hdrc: 28/31 max ep, 16384/16384 memory
> >> USB Host mode controller at 47401800 using PIO, IRQ 0
> >> OMAP SD/MMC: 0
> >> reading u-boot.img
> >> reading u-boot.img
> >> 
> >> 
> >> U-Boot 2013.04-dirty (Sep 09 2014 - 21:38:22)
> >> 
> >> I2C:   ready
> >> DRAM:  512 MiB
> >> WARNING: Caches not enabled
> >> NAND:  No NAND device found!!!
> >> 0 MiB
> >> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> >> *** Warning - readenv() failed, using default environment
> >> 
> >> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> >> SoftConn)
> >> musb-hdrc: MHDRC RTL version 2.0
> >> musb-hdrc: setup fifo_mode 4
> >> musb-hdrc: 28/31 max ep, 16384/16384 memory
> >> USB Peripheral mode controller at 47401000 using PIO, IRQ 0
> >> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx,
> >> SoftConn)
> >> musb-hdrc: MHDRC RTL version 2.0
> >> musb-hdrc: setup fifo_mode 4
> >> musb-hdrc: 28/31 max ep, 16384/16384 memory
> >> USB Host mode controller at 47401800 using PIO, IRQ 0
> >> Net:   <ethaddr> not set. Validating first E-fuse MAC
> >> cpsw, usb_ether
> >> Hit any key to stop autoboot:  0
> >> gpio: pin 53 (gpio 53) value is 1
> >> mmc0 is current device
> >> micro SD card found
> >> mmc0 is current device
> >> gpio: pin 54 (gpio 54) value is 1
> >> SD/MMC found on device 0
> >> reading uEnv.txt
> >> 527 bytes read in 4 ms (127.9 KiB/s)
> >> Loaded environment from uEnv.txt
> >> Importing environment from mmc ...
> >> Running uenvcmd ...
> >> reading uImage
> >> 4368264 bytes read in 499 ms (8.3 MiB/s)
> >> reading /dtbs/am335x-boneblack.dtb
> >> 29192 bytes read in 10 ms (2.8 MiB/s)
> >> ## Booting kernel from Legacy Image at 80200000 ...
> >> 
> >>    Image Name:   Linux-3.8.13
> >>    Image Type:   ARM Linux Kernel Image (uncompressed)
> >>    Data Size:    4368200 Bytes = 4.2 MiB
> >>    Load Address: 80008000
> >>    Entry Point:  80008000
> >>    Verifying Checksum ... OK
> >> 
> >> ## Flattened Device Tree blob at 80f80000
> >> 
> >>    Booting using the fdt blob at 0x80f80000
> >>    Loading Kernel Image ... OK
> >> 
> >> OK
> >> 
> >>    Using Device Tree in place at 80f80000, end 80f8a207
> >> 
> >> Starting kernel ...
> >> 
> >> Uncompressing Linux... done, booting the kernel.
> > 
> > Hummm. That's strange.
> > I don't know if kernel 3.8.13 populate the serial debug interface as ttyO0
> > or ttyS0.
> > 
> > I think you can remove your uEnv.txt file from FAT partition and powerup
> > the board by pressing the boot switch,
> > The u-boot from meta-beagleboard doesn't need any extra configuration.
> > 
> > 
> > Regards,
> > 
> > --
> > *dS
> > Diego Sueiro
> > 
> > Administrador do Embarcados
> > www.embarcados.com.br
> > 
> > /*long live rock 'n roll*/

-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you.

Re: yocto 1.6 - beaglebone black - cape manager

[Andreas Galauner]

On 26.09.2014 15:17, TakkTakk wrote:
> ok, I removed uEnv.txt, pressed the boot switch.
> Starting kernel ... and hang.
> why - "Image Name:   Linux-3.14.0-yocto-standard " ?

I don't have a solution to your problem, but I can at least assure to
you that you are not alone ;)

I'm facing the same problem. I have a Beaglebone Black Rev. A6 which
boots fine with Yocto 1.6 (no meta-beaglebone) and kernel 3.14.
On another newer board with Rev. B it hangs after "Starting Kernel". I
have no idea why.

According to the elinux.org wiki the difference between Revision A and B
is mainly another Version of the SoC (AM3358BZCZ100 in Rev. B and
AM3359AZCZ100 in Rev. A).

Did you manage to fix your problem by now?

- Andy

Re: yocto 1.6 - beaglebone black - cape manager

[TakkTakk]

No Andreas. I could not solve the problem.

2014-09-29 11:15 GMT+02:00 Andreas Galauner <andreas@galauner.de>:
> On 26.09.2014 15:17, TakkTakk wrote:
>> ok, I removed uEnv.txt, pressed the boot switch.
>> Starting kernel ... and hang.
>> why - "Image Name:   Linux-3.14.0-yocto-standard " ?
>
> I don't have a solution to your problem, but I can at least assure to
> you that you are not alone ;)
>
> I'm facing the same problem. I have a Beaglebone Black Rev. A6 which
> boots fine with Yocto 1.6 (no meta-beaglebone) and kernel 3.14.
> On another newer board with Rev. B it hangs after "Starting Kernel". I
> have no idea why.
>
> According to the elinux.org wiki the difference between Revision A and B
> is mainly another Version of the SoC (AM3358BZCZ100 in Rev. B and
> AM3359AZCZ100 in Rev. A).
>
> Did you manage to fix your problem by now?
>
> - Andy
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
TakTak

Re: yocto 1.6 - beaglebone black - cape manager

[Maciej Borzecki]

On Wednesday 01 of October 2014 22:36:48 TakkTakk wrote:
> No Andreas. I could not solve the problem.
Using meta-yocto-bsp, revisions:
meta-yocto-bsp    = "master:8ac8eca2e3bd8c78e2b31ea974930ed0243258a3"
meta-oe           = "master:28e26a9b0ad37d0c92ba42b2727215eef1edf5a2"
MACHINE = "beaglebone"

Enabled layers:
  ${TOPDIR}/../poky/meta \
  ${TOPDIR}/../poky/meta-yocto \
  ${TOPDIR}/../poky/meta-yocto-bsp \
  ${TOPDIR}/../meta-openembedded/meta-oe \

The kernel is Linux-3.14.17-yocto-standard.

Image built with wic like this:
wic create -e core-image-minimal sdimage-bootpart

-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you.

Re: yocto 1.6 - beaglebone black - cape manager

[Denys Dmytriyenko]

On Thu, Sep 04, 2014 at 07:02:13PM -0300, Diego Sueiro wrote:
> > I'm build yocto 1.6, My hardware is beaglebone black I successfull
> > build system image. But I can't see cape manager.
> > I need them to use SPI - enable spidev -
> > http://elinux.org/BeagleBone_Black_Enable_SPIDEV .
> > What do i do to build yocto with a cape manager?
> 
> As far as I know, you have to use meta-beagleboard
> <https://github.com/beagleboard/meta-beagleboard> (almost 1 year without
> any new commit) as your BSP layer to get capemanager support with Yocto.
> Take a look here
> <https://github.com/beagleboard/meta-beagleboard/blob/dylan/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb>.
> The kernel version is 3.8.
> 
> Here we have good news of having capemanager support on mainline:
> http://beagleboard.org/blog/2014-08-27-device-tree-overlay-support-lands-upstream/
> 
> Here you have a beaglebord.org linux repo with capemanager support:
> https://github.com/beagleboard
> I don't know if there is any WIP to get this kernel compiled by Yocto/OE.

Hi,

[I was asked to provide additional comments to this topic - I'm the maintainer 
of meta-ti and the author of BeagleBone Black support in meta-yocto-bsp]

I see that Diego has pretty much covered all the basics above. I'll just add 
few clarifications and details...


There are few different OE/Yocto BSPs for BeagleBone Black:

1. meta-yocto-bsp provides "reference" BSPs for each of the supported 
architectures. One for ARM (BeagleBone Black), one for MIPS, PPC and x86.
The keyword is "reference", as it is based on the mainline kernel/bootloader 
and does not support any advanced features or anything not in the upstream 
mainline kernel - e.g. no capes, no power management, no hardware 
acceleration, no 3D, no PRU, etc. The purpose of this BSP is to have some 
basic out-of-box experience for the select hardware platforms within Poky to 
evaluate the Yocto Project and OpenEmbedded framework, but not the specific 
hardware platforms. For proper and more comprehensive HW support users are 
directed to the corresponding official BSPs - meta-intel, meta-ti, meta-fsl 
(ARM, PPC), meta-amd, etc. etc.

2. meta-ti is the official Texas Instruments BSP that provides the latest WIP 
"staging" kernel and bootloader with most of the advanced features and 
peripheral support for the wider range of latest TI platforms, including 
BeagleBone Black. Most of the work in the "staging" area is being upstreamed, 
so it eventually appears in the mainline kernel and u-boot. It doesn't support 
capes on BBB, at least not yet - see below.

3. meta-beagleboard (now defunct) was a split-off from meta-ti few years ago 
to concentrate on the development of the BeagleBoard and BeagleBone specifics, 
such as capes. At the time it was based on 3.8 kernel and had large patchsets 
to add device tree overlays and cape management, among other things. Although, 
meta-beagleboard seems to be dead now, the work on the devtree overlays and 
cape manager has continued, thanks to Pantelis Antoniou - see the blog post on 
beagleboard.org, linked by Diego above.


The plan always was for meta-ti and meta-beagleboard to meet upstream, hence 
meta-ti will eventually have all the necessary pieces to support capes, once 
it lands upstream. Meanwhile, TI now concentrates on supporting all the other 
advanced features and upstreaming everything to mainline.

BTW, the kernel repo from Robert Nelson (the last link from Diego above) is 
now based on the TI "staging" kernel, i.e. the one provided by meta-ti, plus 
some additional patches not yet accepted upstream. I might look into adding a 
recipe to meta-ti to pull in that tree, but haven't decided yet...


If there are any questions remain, please find me on meta-ti mailing list at 
meta-ti@yoctoproject.org. Thanks.

-- 
Denys

Re: yocto 1.6 - beaglebone black - cape manager

[Gary Thomas]

On 2014-10-06 13:43, Denys Dmytriyenko wrote:
> On Thu, Sep 04, 2014 at 07:02:13PM -0300, Diego Sueiro wrote:
>>> I'm build yocto 1.6, My hardware is beaglebone black I successfull
>>> build system image. But I can't see cape manager.
>>> I need them to use SPI - enable spidev -
>>> http://elinux.org/BeagleBone_Black_Enable_SPIDEV .
>>> What do i do to build yocto with a cape manager?
>>
>> As far as I know, you have to use meta-beagleboard
>> <https://github.com/beagleboard/meta-beagleboard> (almost 1 year without
>> any new commit) as your BSP layer to get capemanager support with Yocto.
>> Take a look here
>> <https://github.com/beagleboard/meta-beagleboard/blob/dylan/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb>.
>> The kernel version is 3.8.
>>
>> Here we have good news of having capemanager support on mainline:
>> http://beagleboard.org/blog/2014-08-27-device-tree-overlay-support-lands-upstream/
>>
>> Here you have a beaglebord.org linux repo with capemanager support:
>> https://github.com/beagleboard
>> I don't know if there is any WIP to get this kernel compiled by Yocto/OE.
>
> Hi,
>
> [I was asked to provide additional comments to this topic - I'm the maintainer
> of meta-ti and the author of BeagleBone Black support in meta-yocto-bsp]
>
> I see that Diego has pretty much covered all the basics above. I'll just add
> few clarifications and details...
>
>
> There are few different OE/Yocto BSPs for BeagleBone Black:
>
> 1. meta-yocto-bsp provides "reference" BSPs for each of the supported
> architectures. One for ARM (BeagleBone Black), one for MIPS, PPC and x86.
> The keyword is "reference", as it is based on the mainline kernel/bootloader
> and does not support any advanced features or anything not in the upstream
> mainline kernel - e.g. no capes, no power management, no hardware
> acceleration, no 3D, no PRU, etc. The purpose of this BSP is to have some
> basic out-of-box experience for the select hardware platforms within Poky to
> evaluate the Yocto Project and OpenEmbedded framework, but not the specific
> hardware platforms. For proper and more comprehensive HW support users are
> directed to the corresponding official BSPs - meta-intel, meta-ti, meta-fsl
> (ARM, PPC), meta-amd, etc. etc.
>
> 2. meta-ti is the official Texas Instruments BSP that provides the latest WIP
> "staging" kernel and bootloader with most of the advanced features and
> peripheral support for the wider range of latest TI platforms, including
> BeagleBone Black. Most of the work in the "staging" area is being upstreamed,
> so it eventually appears in the mainline kernel and u-boot. It doesn't support
> capes on BBB, at least not yet - see below.
>
> 3. meta-beagleboard (now defunct) was a split-off from meta-ti few years ago
> to concentrate on the development of the BeagleBoard and BeagleBone specifics,
> such as capes. At the time it was based on 3.8 kernel and had large patchsets
> to add device tree overlays and cape management, among other things. Although,
> meta-beagleboard seems to be dead now, the work on the devtree overlays and
> cape manager has continued, thanks to Pantelis Antoniou - see the blog post on
> beagleboard.org, linked by Diego above.
>
>
> The plan always was for meta-ti and meta-beagleboard to meet upstream, hence
> meta-ti will eventually have all the necessary pieces to support capes, once
> it lands upstream. Meanwhile, TI now concentrates on supporting all the other
> advanced features and upstreaming everything to mainline.
>
> BTW, the kernel repo from Robert Nelson (the last link from Diego above) is
> now based on the TI "staging" kernel, i.e. the one provided by meta-ti, plus
> some additional patches not yet accepted upstream. I might look into adding a
> recipe to meta-ti to pull in that tree, but haven't decided yet...

Which, if any, of these choices is suitable for accelerated graphics?
Which device(s) will that choice support?  HDMI, LCD cape, ???
Can accelerated graphics, e.g. SGX, be supported by QT5?  If so, what
additional magic needs to be done?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: yocto 1.6 - beaglebone black - cape manager

[Denys Dmytriyenko]

On Mon, Oct 06, 2014 at 02:57:08PM -0600, Gary Thomas wrote:
> On 2014-10-06 13:43, Denys Dmytriyenko wrote:
> >On Thu, Sep 04, 2014 at 07:02:13PM -0300, Diego Sueiro wrote:
> >>>I'm build yocto 1.6, My hardware is beaglebone black I successfull
> >>>build system image. But I can't see cape manager.
> >>>I need them to use SPI - enable spidev -
> >>>http://elinux.org/BeagleBone_Black_Enable_SPIDEV .
> >>>What do i do to build yocto with a cape manager?
> >>
> >>As far as I know, you have to use meta-beagleboard
> >><https://github.com/beagleboard/meta-beagleboard> (almost 1 year without
> >>any new commit) as your BSP layer to get capemanager support with Yocto.
> >>Take a look here
> >><https://github.com/beagleboard/meta-beagleboard/blob/dylan/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb>.
> >>The kernel version is 3.8.
> >>
> >>Here we have good news of having capemanager support on mainline:
> >>http://beagleboard.org/blog/2014-08-27-device-tree-overlay-support-lands-upstream/
> >>
> >>Here you have a beaglebord.org linux repo with capemanager support:
> >>https://github.com/beagleboard
> >>I don't know if there is any WIP to get this kernel compiled by Yocto/OE.
> >
> >Hi,
> >
> >[I was asked to provide additional comments to this topic - I'm the maintainer
> >of meta-ti and the author of BeagleBone Black support in meta-yocto-bsp]
> >
> >I see that Diego has pretty much covered all the basics above. I'll just add
> >few clarifications and details...
> >
> >
> >There are few different OE/Yocto BSPs for BeagleBone Black:
> >
> >1. meta-yocto-bsp provides "reference" BSPs for each of the supported
> >architectures. One for ARM (BeagleBone Black), one for MIPS, PPC and x86.
> >The keyword is "reference", as it is based on the mainline kernel/bootloader
> >and does not support any advanced features or anything not in the upstream
> >mainline kernel - e.g. no capes, no power management, no hardware
> >acceleration, no 3D, no PRU, etc. The purpose of this BSP is to have some
> >basic out-of-box experience for the select hardware platforms within Poky to
> >evaluate the Yocto Project and OpenEmbedded framework, but not the specific
> >hardware platforms. For proper and more comprehensive HW support users are
> >directed to the corresponding official BSPs - meta-intel, meta-ti, meta-fsl
> >(ARM, PPC), meta-amd, etc. etc.
> >
> >2. meta-ti is the official Texas Instruments BSP that provides the latest WIP
> >"staging" kernel and bootloader with most of the advanced features and
> >peripheral support for the wider range of latest TI platforms, including
> >BeagleBone Black. Most of the work in the "staging" area is being upstreamed,
> >so it eventually appears in the mainline kernel and u-boot. It doesn't support
> >capes on BBB, at least not yet - see below.
> >
> >3. meta-beagleboard (now defunct) was a split-off from meta-ti few years ago
> >to concentrate on the development of the BeagleBoard and BeagleBone specifics,
> >such as capes. At the time it was based on 3.8 kernel and had large patchsets
> >to add device tree overlays and cape management, among other things. Although,
> >meta-beagleboard seems to be dead now, the work on the devtree overlays and
> >cape manager has continued, thanks to Pantelis Antoniou - see the blog post on
> >beagleboard.org, linked by Diego above.
> >
> >
> >The plan always was for meta-ti and meta-beagleboard to meet upstream, hence
> >meta-ti will eventually have all the necessary pieces to support capes, once
> >it lands upstream. Meanwhile, TI now concentrates on supporting all the other
> >advanced features and upstreaming everything to mainline.
> >
> >BTW, the kernel repo from Robert Nelson (the last link from Diego above) is
> >now based on the TI "staging" kernel, i.e. the one provided by meta-ti, plus
> >some additional patches not yet accepted upstream. I might look into adding a
> >recipe to meta-ti to pull in that tree, but haven't decided yet...
> 
> Which, if any, of these choices is suitable for accelerated graphics?
> Which device(s) will that choice support?  HDMI, LCD cape, ???
> Can accelerated graphics, e.g. SGX, be supported by QT5?  If so, what
> additional magic needs to be done?

If you are asking about BeagleBone Black specifically, then meta-ti does 
provide accelerated GLES 3D graphics for SGX over HDMI. On other devices, 
built-in LCD is also supported, but not LCD cape, due to reasons above.
SGX is basically supported on Qt5, but there are some pieces missing, for 
which there is work either in progress or planned - for more details I'd 
recommend moving the discussion to meta-ti or meta-arago lists.

-- 
Denys