150 Comentários

Beaglebone Black + Qt5 + Yocto – Parte 1

Beaglebone Black Qt Creator
Este post faz parte da série Beaglebone Black + Qt5 + Yocto. Leia também os outros posts da série:

Nesta série de artigos sobre o uso do Yocto Project veremos como criar uma distribuição Linux embarcado com o Qt5 para a Beaglebone Black usando seu acelerador gráfico SGX530. Na segunda parte veremos como gerar um SDK e integrá-lo ao QtCreator para que possamos desenvolver e compilar aplicações para o nosso target. Se você ainda não teve contato com o Yocto, sugiro que faça o tutorial do Henrique Rossi sobre Beaglebone Black + Yocto.

Preparando o Host

O Yocto Project suporta oficialmente as seguintes distribuições GNU/Linux como ambiente de construção:

  • Ubuntu 12.04, 13.10 e 14.04;
  • Fedora 19 e 20;
  • CentOS 6.4 e 6.5;
  • Debian 7.0, 7.1, 7.2, 7.3 e 7.4;
  • openSUSE 12.2, 12.3 e 13.1.

Para que ele execute no Host alguns pacotes necessitam ser instalados.

Ubuntu e Debian:

Fedora:

openSUSE:

CentOS:

Montando o Ambiente de construção

Vamos criar os diretórios e baixar os fontes necessários:

Note que estamos usando a versão “daisy” do Yocto Project. E baixamos também o layer meta-ti  que possui o BSP (Board Support Package) com os fontes necessários (u-boot, kernel, drivers para o acelerador gráfico, etc.) para rodar a nossa distribuição na Beaglebone Black. Além disso iremos utilizar os layers meta-qt5  (que possuem as receitas para compilar o Qt5), meta-openembedded (com aplicativos adicionais) e o meta-embarcados (com as customizações necessárias para gerarmos a imagem de testes).

Agora vamos configurar o ambiente para gerarmos os artefatos de software:

Edite o arquivo ~/yocto/build-daisy/conf/bblayers.conf para que fique da seguinte maneira:

O arquivo bblayers.conf configura quais serão as camadas a serem consideradas pelo sistema de build.

Adicione as seguintes variáveis no começo do arquivo ~/yocto/build-daisy/conf/local.conf:

Note que configuramos nossa machine como sendo a beaglebone (serve tanto para a white como a black), mudamos o diretório de download para podermos reutilizar os fontes baixados em outros projetos e usaremos o gerenciador de pacotes ipk (ele é mais indicado para sistemas embarcados porque não exige muitos recursos para funcionar).

Gerando a imagem

Depois de baixado os fontes e ter configurado o sistema de build , vamos gerar uma imagem com diversos aplicativos de demostração (qt5-image-demo) do Qt5 (no momento de escrita desse artigo a versão do Qt utilizada é a 5.3.2).

Esta é a configuração de build que foi utilizada:

Gravando a imagem

Este procedimento é praticamente o mesmo utilizado no tutorial do Henrique mencionado no começo deste post. 

Para a gravação das imagens no microSD card, o mesmo deve ser particionado e formatado de acordo o padrão aceito pelo placa. Para isso foi criado um script, que pode ser obtido com os seguintes comandos:

Insira um microSD card no computador PC ou notebook (sistema host) e descubra qual o device node criado pelo sistema operacional. Tente um dos seguintes comandos:

Caso, por exemplo, o device node criado seja /dev/sdb, use o seguinte comando:

Assim que o processo de particionamento e formatação terminar, duas partições no microSD card são criadas:

  • boot (FAT32);
  • rootfs (ext4).

Execute a “montagem” dessas duas partições no sistema de arquivos do sistema host. Caso esse faça uso da distribuição Ubuntu, basta remover e inserir novamente o dispositivo no seu conector. Dado que, por exemplo, os pontos de montagem criados sejam /media/boot e /media/rootfs, a imagem gerada anteriormente é copiada da seguinte forma para o microSD :

Testando a imagem

Remova o microSD do computador e insira-o na BBB, conecte-a a uma TV por um cabo HDMI, e a um mouse através do conector USB da placa. Você precisará acessar o sistema via conexão serial. Para fazer a conexão entre o HOST e a BBB siga os passos da seção “Configuring Serial Communication” do tutorial da Timesys.

NOTA:

Se você tiver instalado algum outro sistema operacional no eMMC da BBB energize a placa pressionando a switch que fica próxima ao slot do microSD. Isso fará com que o processador busque o MLO e u-boot que estão contidos no microSD ao invés do eMMC.

Abaixo segue o log da serial depois do boot do sistema: 

Vamos rodar o Qt5 Cinematic Experience que é um exemplo bastante interessante que visa explorar diversos recursos usando aceleração gráfica por hardware. Para isso faça o login como root e execute o programa: 

Note que subimos o aplicativo com a opção “-platform eglfs”, isso configura o Qt para utilizar o OpenGL através do pluging EGLFS.

A figura 1 mostra um screenshot do Qt5 Cinematic Experience.

Qt5 Cinematics Experience
Figura 1 – Qt5 Cinematics Experience

Agora vamos rodar o exemplo do QtSmartHome:

A figura 2 mostra um screenshot do QtSmartHome:

Figura 2 - Qt Smart Home
Figura 2 – Qt Smart Home

Agora vamos rodar o exemplo Qt5EveryWhereDemo:

A figura 3 mostra um screenshot do Qt5EveryWhereDemo:

Figura 3 - Qt5 Every Where Demo
Figura 3 – Qt5 Every Where Demo

Aproveite para explorar os diversos exemplos presentes no caminho /usr/share/qt5 e lembre-se de sempre passar a opção “-platform eglfs” quando carregar os programas.

Dicas e Truques

Para remover o cursor piscante na tela rode o comando:

Para desabilitar o desligamento da saída de vídeo rode o comando:

A aceleração gráfica tem uma melhor performance na resolução HD (1280×720) e caso sua TV ou monitor seja FULL-HD (1920×1080) você pode alterar a resolução para HD com os seguintes comandos:

O que vem por aí

Na próxima parte veremos como gerar uma toolchain com o Qt5 para ser integrada a IDE QtCreator para desenvolvimento e compilação das aplicações Qt.

Saiba mais

Beaglebone Black + Qt Embedded + Yocto – parte 1

Desvendando Yocto Project – Primeiros passos

BeagleBone Black + Yocto

Referências

http://beagleboard.org/Products/BeagleBone%20Black
http://en.wikipedia.org/wiki/PowerVR#Series_5
http://qt-project.org/wiki/Category:Tools::QtCreator
http://qt-project.org/doc/qt-4.8/qt-embedded-linux.html
http://en.wikipedia.org/wiki/Graphics_processing_unit
http://blog.qt.digia.com/blog/2011/05/09/thoughts-about-qt-5/
http://elinux.org/Beagleboard:BeagleBone_Black_Serial
https://linuxlink.timesys.com/docs/gsg/beaglebone_black

Outros artigos da série

Beaglebone Black + Qt5 + Yocto – Parte 2 >>
Licença Creative Commons Esta obra está licenciada com uma Licença Creative Commons Atribuição-CompartilhaIgual 4.0 Internacional.

Receba os melhores conteúdos sobre sistemas eletrônicos embarcados, dicas, tutoriais e promoções.

Beaglebone Black » Beaglebone Black + Qt5 + Yocto - Parte 1
Comentários:
Notificações
Notificar
guest
150 Comentários
recentes
antigos mais votados
Inline Feedbacks
View all comments
Premjith
Premjith
29/07/2019 02:33

Is there any way to do this build with 4.14 kernel, this build is bind to 3.14 kernel ? Thanks

Gabriel Habib
Gabriel Habib
27/10/2015 11:51

Sueiro, eu gostaria de entender um pouco mais sobre a questao do Yocto, falaste sobre conectar um mause na USB da mesma, fiquei me perguntando como eu faria para por exemplo, adicionar um touch screen via USB. Em qual parte do cozimento eu defino isso?

Diego Sueiro
Diego Sueiro
Reply to  Gabriel Habib
28/10/2015 08:03

Gabriel,

Este tipo de característica é manipulada pelo Yocto através da variável MACHINE_FEATURES:

http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-features-machine

Gabriel Habib
Gabriel Habib
14/10/2015 16:12

Muitos Warnings pos o bitbake 🙁

WARNING: Failed to fetch URL http://zlib.net/pigz/pigz-2.3.1.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://ftp.astron.com/pub/file/file-5.16.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://ftp.debian.org/debian/pool/main/b/base-passwd/base-passwd_3.5.29.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://sourceware.org/pub/libffi/libffi-3.0.13.tar.gz, attempting MIRRORS if available

Sera que existe algo mais atualizado que esse tutorial?

obrigado!!!

Diego Sueiro
Diego Sueiro
Reply to  Gabriel Habib
14/10/2015 16:18

Não que eu saiba.
Recebeu algum erro?

Gabriel Habib
Gabriel Habib
Reply to  Diego Sueiro
14/10/2015 16:37

Diego Sueiro, muito obrigado pela atencao, nao sabia que voces eram tao atenciosos dessa maneira.

Bem, ate o momento nenhum erro, porem estou achando estranho que o processo esteja demorando tanto, eu rodei o comando bitbake e ate o momento ja foram 8 horas ( 760 de 2581 ), fiquei imaginando que poderia ser por contas desses warnings.

Diego Sueiro
Diego Sueiro
Reply to  Gabriel Habib
14/10/2015 17:12

Olá Gabriel,

A primeira vez que você roda o construção da imagem demora um pouco mesmo.
O Yocto vai baixar uma infinidade de código e compilar as ferramentas do host.
Dependendo da configuração da tua máquina esse processo será bastante lento.

Gabriel Habib
Gabriel Habib
Reply to  Diego Sueiro
14/10/2015 17:19

Obrigado! vou ficar no aguardo!

Martin Beaudet
erakis
07/04/2015 16:20

Hi Diego I tried following your instructions but using poky dizzy version and Qt 5.3.2 but I’m getting a compile error. Here is my configuration : http://pastebin.com/jnvKJCDD And here is the compilation error : http://pastebin.com/i3np03Ey The problem seem to an internal compiler error while compiling QtTools module recpipes. Could it be the internal compiler of Yocto toolchain being not enough recent ? Also, you mention that using Yocto Dizzy 1.7 will not correctly handle 3d hardware on Beaglebone, does it mean we have to wait for meta-ti release their dizzy version ? Thank for sharing your work with us, it… Leia mais »

Diego Sueiro
Diego Sueiro
Reply to  erakis
08/04/2015 06:33

Martin, Note that I used the dizzy branch for meta-qt5 and daisy branch for the others. Unfortunately I don’t have enough time now to build in the same configuration as you. You can try ti use the same configuration as me and try to reproduce the issue, but do this delete your “tmp” folder. You can also try to send an e-mail to openembedded-devel mailing list (http://lists.openembedded.org/mailman/listinfo/openembedded-devel) asking for some help on this. Where did I mention that using Yocto Dizzy 1.7 will not correctly handle 3d hardware on Beaglebone? Actually I didn’t tested it yet. Sorry for not helping… Leia mais »

Martin Beaudet
erakis
Reply to  Diego Sueiro
08/04/2015 12:29

Hi Diego, First of all thank for you quick response. I have sent detail of the problem to the Yocto and OpenEmbedded list. Hope they will find what wrong. Maybe I misread about Hardware Acceleration, I’m not talking Spanish so I translated your instructions to English that is my second language. I’m talking french. I though I was read that using the Dizzy version was using a kernel that is not handling correctly all the beaglebone hardware. Do we still need to use your meta-bbb if we use meta-yocoto-bsp ? Is Dizzy offering GPU hardware acceleration (qt over elgfs ?)… Leia mais »

Diego Sueiro
Diego Sueiro
Reply to  erakis
08/04/2015 12:41

Martin,

The hardware graphics acceleration comes from meta-ti, so you have to it instead of meta-yocto-bsp (which doesn’t provides the hw accel).

I used Daisy because Dizzy was not available when I wrote the article. But the main differences are related to the package versions.

The meta-bbb is needed to correct set libgles libraries and configure qt-base package.

Did you tried to use all layers on daisy branch and only meta-qt5 on dizzy branch?

Martin Beaudet
erakis
Reply to  Diego Sueiro
08/04/2015 12:56

No I did not tried, but I will now.

But will I applied some changes on your meta-embarcados ?
Will I have to rename 5.3.% to 5.4.% on this file (meta-embarcados/meta-bbb/recipes-qt/qt5/qtbase_5.3.%.bbappend) ?

Best regards,

Diego Sueiro
Diego Sueiro
Reply to  erakis
08/04/2015 13:00

Martin,

Since meta-qt5 on dizzy branch uses qt-5.3.2 you don’t have to change the filename.

Martin Beaudet
erakis
Reply to  Diego Sueiro
08/04/2015 13:26

Oups sorry, I was talking abou the “otavio/master” branch of meta-qt5 ?

Because I would like to use Qt5.4 or newest if possible.

Diego Sueiro
Diego Sueiro
Reply to  erakis
08/04/2015 13:37

In this case you will have to rename this recipe.

Martin Beaudet
erakis
Reply to  Diego Sueiro
08/04/2015 17:04

I tried with your advise —————————————————————– Build Configuration: BB_VERSION = “1.22.0” BUILD_SYS = “x86_64-linux” NATIVELSBSTRING = “Ubuntu-14.10” TARGET_SYS = “arm-poky-linux-gnueabi” MACHINE = “beaglebone” DISTRO = “poky” DISTRO_VERSION = “1.6.2” TUNE_FEATURES = “armv7a vfp thumb neon callconvention-hard cortexa8” TARGET_FPU = “vfp-neon” meta meta-yocto = “daisy:02e603e48c6e0b0492f596890adadf6590fa692c” meta-oe = “daisy:d3d14d3fcca7fcde362cf0b31411dc4eea6d20aa” meta-ti = “daisy:d63fd7691e99f9d8dfb9704f634a970b8e44dffd” meta-qt5 = “otavio/master:d02ea33262489f6892db857f9674d14a08f7ca54” meta-embarcados meta-bbb = “daisy:60ea816afabce0ab85a974a6c8b60683ccdab4bc” ——————————————————————– But I get error while fetching Qt from (qt.gitorious.org/qt/qt3d) —————————————————– ERROR: Function failed: Fetcher failure for URL: ‘git://qt.gitorious.org/qt/qt3d.git;branch=dev’. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /home/test/poky/beaglebone/tmp/work/cortexa8t2hf-vfp-neon-poky-linux-gnueabi/qt3d/5.4.0+gitAUTOINC+8a9723d742-r0/temp/log.do_fetch.27984 ERROR: Task 284 (/home/test/poky/beaglebone/../meta-qt5/recipes-qt/qt5/qt3d_git.bb, do_fetch) failed with exit code ‘1’… Leia mais »

Martin Beaudet
erakis
Reply to  erakis
08/04/2015 23:20

I finally succeed with this configuration :

Build Configuration:
BB_VERSION = “1.22.0”
BUILD_SYS = “x86_64-linux”
NATIVELSBSTRING = “Ubuntu-14.10”
TARGET_SYS = “arm-poky-linux-gnueabi”
MACHINE = “beaglebone”
DISTRO = “poky”
DISTRO_VERSION = “1.6.2”
TUNE_FEATURES = “armv7a vfp thumb neon callconvention-hard cortexa8”
TARGET_FPU = “vfp-neon”
meta
meta-yocto = “daisy:02e603e48c6e0b0492f596890adadf6590fa692c”
meta-oe = “daisy:d3d14d3fcca7fcde362cf0b31411dc4eea6d20aa”
meta-ti = “daisy:3a95559c124d3ce8c076b3fae5859435977d1ac2”
meta-qt5 = “master:87235825459d376bf4537c9523eb2496e15893aa”
meta-embarcados
meta-bbb = “daisy:60ea816afabce0ab85a974a6c8b60683ccdab4bc”.

But no success with yocto dizzy 🙁 Hope you will have some time to test it. If you find some time to test it, please post me a message here.

Best regards,

Diego Sueiro
Diego Sueiro
Reply to  erakis
10/04/2015 08:56

Martin,

Why are you using otavio/master branch for meta-qt5? I realized that it is not up to date with Qt repo source URL. Please use master branch instead.

I’m going to investigate the libgles error.

Martin Beaudet
erakis
Reply to  Diego Sueiro
13/04/2015 09:27

Hi Diego, I realize too so I decide to use the master branch. I though I have to use the same branch as yocto (daisy) to get less trouble. But I got a successful build using the master branch. Now I’m having another problem with the LCD (Topway : LMT070DICFWD). I’m using your qt5-image-demo layer. I used the dtb-rebuilder of Robert C Nelson (https://github.com/RobertCNelson/dtb-rebuilder/tree/3.14-ti), build the file (am335x-bone-4dcape-70t.dts) to dtb. I have copy this file to the /boot partition and then add the following to the uEnv.txt (dtb=am335x-bone-4dcape-70t.dtb). When Beaglebone booting I notice this error in console tilcdc 4830e000.lcdc: No… Leia mais »

Diego Sueiro
Diego Sueiro
Reply to  erakis
13/04/2015 09:53

Martin,

The TI’s kernel doesn’t have the “capemgr” and “bone-pinmux-helper” support, and I don’t think that this dts is going to work.

You can try to create a kernel recipe for Robert’s kernel and use it instead of TI’s kernel, or you can use am335x-evmsk.dts as a reference to create the am335x-bone-4dcape-70t.dts :
http://git.ti.com/ti-linux-kernel/ti-linux-kernel/blobs/ti-linux-3.14.y/arch/arm/boot/dts/am335x-evmsk.dts

Martin Beaudet
erakis
Reply to  Diego Sueiro
13/04/2015 11:15

I guess that cape manager is not implemented in the meta-ti as it is specific too BEAGLEBONE ? Maybe I misread but DTS is only required with kernel > 3.10 ? The meta-ti kernel is 3.14 so it is not supposed to handle the dts ? Is the cape manager is only available to kernel <=3.8 ? Anyway I don't think I will need the cape manager. Unless you tell me that I NEED the cape manager to get my LCD working ? If there no need of the cape manager, why my LCD is not working ? It is… Leia mais »

Diego Sueiro
Diego Sueiro
Reply to  erakis
13/04/2015 11:26

Martin,

The capemgr is implemented by beagleboard community and that’s why it is not presented on the TI’s kernel. The same applies to bone-pinmux-helper.

I think that on this case the problem is related to the bone-pinmux-helper. If you look at the dtsi files included on the am335x-bone-4dcape-70t.dts it invokes the pinmux-helper and since it’s not implemented on TI’s kernel, its not going to work.

All the ARM kernels above 3.8 suppose to work only with device-tree implementation.

you can use am335x-evmsk.dts as a reference to create the am335x-bone-4dcape-70t.dts :
http://git.ti.com/ti-linux-kernel/ti-linux-kernel/blobs/ti-linux-3.14.y/arch/arm/boot/dts/am335x-evmsk.dts

Martin Beaudet
erakis
Reply to  Diego Sueiro
13/04/2015 12:26

Diego, First thank you for you patience. I’ll come to understand… I took a look to the Robert Nelson config (https://github.com/beagleboard/linux/blob/3.14/arch/arm/configs/bb.org_defconfig) and then I notice this flag : CONFIG_BEAGLEBONE_PINMUX_HELPER=y If I well understand, the uBoot is supporting reading the DTB file but the ti kernel can’t handle it. Is it right ? Some other question to help me understand : 1) Robert C Nelson kernel is a fork of the meta-ti kernel ? 2) But he add patch and different kernel configuration to support more specific uses of the beaglebone, right ? As probably the cape manager (pixmux, dts). 3)… Leia mais »

Diego Sueiro
Diego Sueiro
Reply to  erakis
13/04/2015 13:28

Martin, Checkout my answers bellow: If I well understand, the uBoot is supporting reading the DTB file but the ti kernel can’t handle it. Is it right ? Diego: No, both kernel (from Robert and TI) and u-boot supports the DTB. As I told you before all the ARM kernels above 3.8 suppose to work only with device-tree implementation. 1) Robert C Nelson kernel is a fork of the meta-ti kernel ? Diego: I do think so. 2) But he add patch and different kernel configuration to support more specific uses of the beaglebone, right ? As probably the cape… Leia mais »

Martin Beaudet
erakis
Reply to  Diego Sueiro
13/04/2015 15:19

Diego, Nice, now I understand. So I have 2 options : The first one is keeping the yocto + meta-ti and trying to find how works the DTS to get my LCD working without pixmux (based on am335x-evmsk.dts from TI) ? I think that the road will be really long because I really don’t understand much about the device tree. The am335x-evmsk.dts is a based configuration ? I need to add HDMI + LCD cape functionality according the schematic of the beaglebone black ? The second one could be using yocto + meta-ti + applying patch from Robert C Nelson… Leia mais »

Diego Sueiro
Diego Sueiro
Reply to  erakis
14/04/2015 06:30

Martin, The dts to get LCD working is not to difficult to implement. It’s just a matter of inserting and adjusting the “panel” parameter. This values you can copy from Robert’s dts. There is a lots of materials explaining the device tree and how to use it. Yes, you can apply the Robert’s patches to get the bone-pinmux-helper on TI’s kernel (but I don’t if it is going to be applied cleanly), or you can create a kernel recipe to build the Robert’s kernel. I didn’t looked at the code, but I think that the bone-pinumux-helper is on the top… Leia mais »

Martin Beaudet
erakis
Reply to  Diego Sueiro
14/04/2015 14:59

Hi Diego, Thank you again for supporting me, it’s very nice. Ok I will try to adapt the DTS. What I have learn from now is that I have to based my DTS from the TI starter kit (http://git.ti.com/ti-linux-kernel/ti-linux-kernel/blobs/ti-linux-3.14.y/arch/arm/boot/dts/am335x-evmsk.dts) Now when looking to Robert C Nelson dts, I saw the following files that could help me : https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-evmsk.dts (Starter kit) https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-lcd7-01-00a3.dtsi (Recipes to get LCD + touchscreen) Now each part : https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-bl-gpio1-18.dtsi (Backlight) https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-panel-800×480.dtsi (LCD) https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-bone-ti-tscadc-4-wire.dtsi (TouchScreen) What I have to do is to append or merge this to my am335x-evmsk.dts ? I produce my final DTS by helping me… Leia mais »

Diego Sueiro
Diego Sueiro
Reply to  erakis
14/04/2015 15:46

Martin,

Glad to hear that you got it working.

To include your custom dts you will have to create a bbappend file for the kernel recipe (for example: meta-embarcados/meta-bbb/recipes-kernel/linux/linux-ti-staging_3.14.bbappend). With the following content:
http://pastebin.com/swJAQNMY

Put your am335-custom-dts.dts file on the following path: meta-embarcados/meta-bbb/recipes-kernel/linux/linux-ti-staging/am335-custom-dts.dts

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
20/04/2015 22:44

HI Diego,
I am following your tutorial to get “qt5-image-demo” working on TI AM335x EVM Kit.
I have added a kernel recipe to use am335x-evm.dts file.
Wanted to know whether I need a recipe for u-boot or not ?
If yes, then how to do so ?
Also, if I want to use latest meta-qt5 (master) instead of dizzy, what shall I change in my qt5 recipe ?
I am new to Yocto so any explanation to above questions will be highly appreciated.
Thanks

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
21/04/2015 06:46

Ankur,

You don’t have to create kernel, u-boot or other recipes to build to am335x-evm. You just have to set your machine in the local.conf file. Make sure that you have:
MACHINE = “am335x-evm”

If you want to use meta-qt5 in “master” branch I suggest you to use all the other branches on “master” too, this way you are going to minimize software compatibility problems.
Note that meta-embarcados is only developed to work with “daisy” and “dizzy” branch of meta-qt5.

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
21/04/2015 07:24

Hi Diego,

Thanks for your response.
If I don’t use meta-embarcados, will I still get graphic acceleration ?

As you said in comments above, meta-bbb is needed for libgles and qt5

Ankur Tyagi
Ankur Tyagi
Reply to  Ankur Tyagi
21/04/2015 08:09

Diego,

I added PACKAGECONFIG_append_pn-qtbase = ” tslib” in my local.conf but during device booting stage, it doesn’t ask for TS calibration. I also cannot find ts_calibrate in rootfs

How to enable that ?

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
21/04/2015 09:48

Ankur,

To get ts_calibrate installed add the following on your IMAGE_INSTALL variable:
tslib-calibrate

I don’t kown if it’s going to be launched at the first boot. You can take this recipe as reference to achieve this:
http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-extras/recipes-graphics/tslib/ts-calibrate-init_1.0.bb;hb=master

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
21/04/2015 10:22

Hi Diego,

Thanks for your response.

I have now done following changes and re-launched above steps:
1) MACHINE = “am335x-evm”
2) created am335x-evm.conf in meta-bbb

bitbake qt5-image-demo on going, lets wait for results 🙂

Ankur Tyagi
Ankur Tyagi
Reply to  Ankur Tyagi
21/04/2015 11:28

It compiled and created a package.

But when I boot my Am335x Kit and try to run qt5 smart home demo, it fails with error “libGLESv2.so No such file or directory”

I missed bundling of these in file system. Can you please help ?

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
21/04/2015 11:33

Did you included “libgles-omap3” and “omap3-sgx-modules” packages on your IMAGE_INSTALL?

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
21/04/2015 11:43

hmm, I checked that in file meta-embarcados/meta-bbb/recipes-qt/packagegroups/packagegroup-qt5.bbappend, they are added only for beaglebone Machine. Now I have created another entry for am335x-evm Machine.

Let’ see how it goes.

thanks

Ankur Tyagi
Ankur Tyagi
Reply to  Ankur Tyagi
21/04/2015 12:08

It’s working with above change.

I added tslib-calibrate in IMAGE_INSTALL inside qt5-image-demo.bb but still no success.

What else can I do ?

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
21/04/2015 12:15

The ts_calibrate binary were installed?
Did you tried to create a recipe for the tool to be launched on the first boot as I told you before?

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
21/04/2015 12:18

no ts_calibrate binary on target

Ankur Tyagi
Ankur Tyagi
Reply to  Ankur Tyagi
21/04/2015 20:48

Hi Diego,

I made a clean build with all above changes intact i.e

1) MACHINE = am335x-evm
2) Added entry for am335x-evm MACHINE in qt5 packagegroup recipe
3) created am335x-evm.conf file
4) tslib-calibrate added in IMAGE_INSTALL in qt5-image-demo.bb

With this, I am able to build image for AM335x-EVM Kit.

Once the card bootsup, export following:

export QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS=”rotate=180″
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/touchscreen0
export TSLIB_PLUGINDIR=/usr/lib/ts

And demo runs smooth 🙂

Many thanks for your support, really appreciate it.

Now I am trying to build meta-qt “master” and might bug you again 🙂
cheers

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
21/04/2015 21:27

Ankur,

Thanks for the feedback. Glad to know that you managed to get it working.

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
12/05/2015 18:45

Hi Diego,

Above steps doesn’t include qtwebkit. How can I include qtwebkit ?

thanks
Ankur

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
12/05/2015 19:07

Ankur,

On the file “meta-embarcados / recipes-core / images / qt5-image-demo.bb” put “qtwebkit” in IMAGE_INSTALL variable.

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
12/05/2015 22:58

Thanks Diego, I want to use latest qt-5.4, so I am using meta-qt5 “master”. When I issue bitbake, I get this error : [email protected]:~/poky-yocto/build-daisy$ bitbake qt5-image-demo NOTE: Error during finalise of /home/ankur/poky-yocto/build-daisy/../poky-daisy/meta-qt5/recipes-qt/qt5/qtmultimedia_git.bb | ETA: 00:01:09 ERROR: ExpansionError during parsing /home/ankur/poky-yocto/build-daisy/../poky-daisy/meta-qt5/recipes-qt/qt5/qtmultimedia_git.bb: Failure expanding variable qmake5_base_do_configure: ExpansionError: Failure expanding variable EXTRA_QMAKEVARS_PRE, expression was ${@bb.utils.contains(‘PACKAGECONFIG’, ‘alsa’, ”, ‘CONFIG+=done_config_alsa’, d)} ${@bb.utils.contains(‘PACKAGECONFIG’, ‘pulseaudio’, ”, ‘CONFIG+=done_config_pulseaudio’, d)} ${@bb.utils.contains(‘PACKAGECONFIG’, ‘openal’, ”, ‘CONFIG+=done_config_openal’, d)} ${@bb.utils.contains(‘PACKAGECONFIG’, ‘gstreamer’, ‘GST_VERSION=1.0’, ”, d)} ${@bb.utils.contains(‘PACKAGECONFIG’, ‘gstreamer010’, ‘GST_VERSION=0.10’, ”, d)} ${@bb.utils.contains_any(‘PACKAGECONFIG’, ‘gstreamer gstreamer010’, ”, ‘CONFIG+=done_config_gstreamer’, d)} which triggered exception AttributeError: ‘module’ object has no attribute ‘contains_any’ I then started to use bitbake “master” branch,… Leia mais »

Ankur Tyagi
Ankur Tyagi
Reply to  Ankur Tyagi
13/05/2015 02:45

I reverted back to meta-qt “dizzy” but I am getting this error : [email protected]:~/poky-yocto/build-daisy$ bitbake -k qt5-image-demo Parsing recipes: 100% |######################################################################################################################################################################| ETA: 00:00:00 Parsing of 1515 .bb files complete (0 cached, 1515 parsed). 1941 targets, 198 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo) NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg ERROR: Nothing PROVIDES ‘ruby-native’ (but /home/ankur/poky-yocto/build-daisy/../poky-daisy/meta-qt5/recipes-qt/qt5/qtwebkit_5.3.2.bb DEPENDS on or otherwise requires it). Close matches: db-native bc-native byacc-native NOTE: Runtime target ‘qtwebkit’ is unbuildable, removing… Missing or unbuildable dependency chain was: [‘qtwebkit’, ‘ruby-native’] ERROR: Nothing… Leia mais »

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
13/05/2015 06:39

Ankur,

Mixing layers in different branches is not a good practice and can be error prone, as you are having now.

Try to use meta-embarcados in “daisy” branch and all the others in “fido” and see what happens.

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
13/05/2015 07:56

Hi Diego,
Sure, will try all others in “fido”.
What about error coming when I included “qtwidget” ? As stated in comment below.
thanks

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
13/05/2015 08:06

Ankur,

It seems to be related to Qt multimedia, and I didn’t had time to investigate this.
Maybe using fido branch this error will not be raised

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
14/05/2015 01:05

Hi Diego,

I followed these two procedures with no success so far

1) kept all branches as “daisy” and add “qtwebkit” in IMAGE_INSTALL variable. This gave error qtwebkit-dev not found
2) update all to “fido” , meta-qt to “master” and kept meta-embarcados and meta-ti in “diasy” (no fido for meta-ti) and this gave me error :

Parsing recipes: 100% |#############################################################| Time: 00:01:28
Parsing of 1677 .bb files complete (0 cached, 1677 parsed). 2155 targets, 356 skipped, 0 masked, 0 errors.
ERROR: No recipes available for:
/home/ankur/poky-yocto/build-fido/../poky-fido/meta-embarcados/meta-bbb/recipes-qt/qt5/qtbase_5.3.%.bbappend

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
[email protected]:~/poky-yocto/build-fido$

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
14/05/2015 08:20

Ankur,

For the second scenario, please rename the recipe “meta-embarcados/meta-bbb/recipes-qt/qt5/qtbase_5.3.%.bbappend” to
“meta-embarcados/meta-bbb/recipes-qt/qt5/qtbase_%.bbappend”

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
14/05/2015 18:56

After renaming, i get these errors : [email protected]:~/poky-yocto/build-fido$ mv /home/ankur/poky-yocto/build-fido/../poky-fido/meta-embarcados/meta-bbb/recipes-qt/qt5/qtbase_5.3.%.bbappend /home/ankur/poky-yocto/build-fido/../poky-fido/meta-embarcados/meta-bbb/recipes-qt/qt5/qtbase_%.bbappend [email protected]:~/poky-yocto/build-fido$ vim ../changes/0001-am335x-evm-changes.patch [email protected]:~/poky-yocto/build-fido$ bitbake -k qt5-image-demo Loading cache: 100% |########################################################################################################################################################################| ETA: 00:00:00 Loaded 2156 entries from dependency cache. Parsing recipes: 100% |######################################################################################################################################################################| Time: 00:00:00 Parsing of 1677 .bb files complete (1675 cached, 2 parsed). 2155 targets, 356 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo) NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg ERROR: Nothing PROVIDES ‘ruby-native’ (but /home/ankur/poky-yocto/build-fido/../poky-fido/meta-qt5/recipes-qt/qt5/qtwebkit_5.4.1.bb DEPENDS on or otherwise requires it). Close matches: db-native bc-native byacc-native NOTE: Runtime target ‘qtwebkit’… Leia mais »

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
14/05/2015 20:10

Ankur,

You need to add meta-ruby:

http://layers.openembedded.org/layerindex/recipe/5212/

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
18/05/2015 02:04

Hi Diego, So finally I have this configuration: Build Configuration: BB_VERSION = “1.26.0” BUILD_SYS = “i686-linux” NATIVELSBSTRING = “Ubuntu-14.04” TARGET_SYS = “arm-poky-linux-gnueabi” MACHINE = “am335x-evm” DISTRO = “poky” DISTRO_VERSION = “1.8” TUNE_FEATURES = “arm armv7a vfp thumb neon callconvention-hard cortexa8” TARGET_FPU = “vfp-neon” meta-embarcados meta-bbb = “daisy:d8e5d8f728a51db44750d4f43d66d51c89dd8a20” meta-ti = “daisy:efc3f4a7687c0ba959dca2b75a99ba8efac94507” meta-qt5 = “master:bb20ed60fc596098940f18bd2418a8bdc866bec3” meta-ruby meta-oe = “fido:5b0305d9efa4b5692cd942586fb7aa92dba42d59” meta meta-yocto = “fido:e2e522a6ede3165f63ad81c72f8ac6d3903f8296” I added – meta-ruby in bblayers.conf – qtwebkit, qtwebkit-examples in IMAGE_INSTALL When I issue bitbake qt5-image-demo, during last step i get this error : Configuring qt3d-examples. Configuring packagegroup-qt5-base. Collected errors: * opkg_install_cmd: Cannot install package qtwebkit-examples. ERROR: Function failed:… Leia mais »

Ankur Tyagi
Ankur Tyagi
Reply to  Ankur Tyagi
18/05/2015 02:36

Diego,

I figured out what the problem was.

its qtwebit-examples-examples, not qtwebkit-examples.

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
21/04/2015 09:24

Ankur,

You can try to use meta-bbb on daisy branch and see if it works.

But basically, meta-bbb set some packages on beaglebone.conf:
PREFERRED_VERSION_libgles-omap3 = “5.01.01.01”
PREFERRED_PROVIDER_virtual/egl = “libgles-omap3”
PREFERRED_PROVIDER_virtual/libgles1 = “libgles-omap3”
PREFERRED_PROVIDER_virtual/libgles2 = “libgles-omap3”

And forces the installations of “libgles-omap3” and “omap3-sgx-modules” packages via meta-embarcados/meta-bbb/recipes-qt/packagegroups/packagegroup-qt5.bbappend.

Ankur Tyagi
Ankur Tyagi
Reply to  Diego Sueiro
21/04/2015 09:34

Hi Diego,

In case if I set MACHINE = “am335x-evm”, then I doubt beaglebone.conf will be used. Correct ?

So even if I stay on “daisy” branch, unless I use MACHINE = “beaglebone”, meta-bbb won’t work.

Is my understanding correct ?

If yes, then I have to create am335x-evm.conf to get egl packages for it.

Diego Sueiro
Diego Sueiro
Reply to  Ankur Tyagi
21/04/2015 09:41

Ankur,

Yes you are right. In this case you have to create a am335x-evm.conf file.
Use meta-ti/tree/conf/machine/am335x-evm.conf as a reference.

Qasem Taheri
Qasem
21/03/2015 18:34

hi Thanks for this tutorial.

i m from iran , We can not do these steps

Because ,TI site (git://git.yoctoproject.org/meta-ti) Blocked ip my counter and we can’t download driver for yocto project

plzzzzzzzzz If possible for you ,share this files

qt5-image-demo (beaglebone Black and Raspberry PI B )

my email : [email protected]

mercccccccccccccccccccc

Diego Sueiro
Diego Sueiro
Reply to  Qasem
22/03/2015 06:40

Qasem,

This repo (meta-ti) is hosted by Yocto Project, not TI. You could download this repository?

What driver are you talking about?
You can clone meta-ti from here too: git://arago-project.org/git/meta-ti.git

Regards

Qasem Taheri
Qasem
Reply to  Diego Sueiro
22/03/2015 13:30

Hi
When yocto project is downloading Graphics_SDK_setuplinux_hardfp_5_01_01_01.bin the 403 forbidden is thrown in do_fetch state indeed. It would be appreciated if you could share beaglebone black and raspberry pi B images via dropbox or google drive.
Unfortunatly we have many access limitation to the resources which be hosted in usa.

Regards

Diego Sueiro
Diego Sueiro
Reply to  Qasem
23/03/2015 08:49
Ramesh Devaraj
Ramesh Devaraj
24/02/2015 09:06

Hi Diego,

I came across this thread in yocto mailing list https://lists.yoctoproject.org/pipermail/yocto/2014-April/019335.html which is the exact issue i am getting while running weston from bbb (yocto based). And I see that no solution was given so far. How did you fix this ?

Thanks,
Ramesh

Diego Sueiro
Diego Sueiro
Reply to  Ramesh Devaraj
24/02/2015 10:02

Ramesh,

No didn’t managed to get this working and I did not investigate a lot.

Sorry.

Grangsang Sotyaramadhani
Grangsang Sotyaramadhani
11/02/2015 02:31

Dear Diego, I am from Indonesia. I am interested to your project in building qt5 image for Pi. I have followed all the steps above and success. Now I am trying to build qt5 image for “a13 allwinner/olinuxino a13” using meta-sunxi and everything got failed. Could you help me to solve my problem?

Thank you
Best regards.

Diego Sueiro
Diego Sueiro
Reply to  Grangsang Sotyaramadhani
11/02/2015 05:53

Hi Grangsang,

What kind of errors?
Send me your bblayers.conf and local.conf files (use pastebin).

Grangsang Sotyaramadhani
Grangsang Sotyaramadhani
Reply to  Diego Sueiro
11/02/2015 06:47

Hi Diego,

Thank you for your reply.

here are bblayers.conf and local.conf

http://pastebin.com/raw.php?i=NssYfg8Z

http://pastebin.com/FLYHRnTw

please help me.

Best regards.

Diego Sueiro
Diego Sueiro
Reply to  Grangsang Sotyaramadhani
11/02/2015 07:25

Please,

Send me the erros messages too. (via pastebin)

Grangsang Sotyaramadhani
Grangsang Sotyaramadhani
Reply to  Diego Sueiro
11/02/2015 07:42

Sorry Diego, I forget to send you the error log.

Here is the last error I got after I try to force adding “vc-graphics”

http://pastebin.com/raw.php?i=cRmLm6H9

I don’t really sure what is actually wrong. I think I am wrong for forcing your “meta-rpi” to be used with meta sunxi.

Grangsang Sotyaramadhani
Grangsang Sotyaramadhani
Reply to  Diego Sueiro
11/02/2015 06:52

It seems that the error caused by the eglfs

Grangsang Sotyaramadhani
Grangsang Sotyaramadhani
Reply to  Diego Sueiro
11/02/2015 07:06

Here are my another configuration that also give an error output:

http://pastebin.com/raw.php?i=VHDncvvj

http://pastebin.com/raw.php?i=EDv9FX1r

once again, thank you so much.

Ramesh Devaraj
Ramesh Devaraj
20/01/2015 06:12

Olá Diego,

quando eu emitir “Qt5_CinematicExperience -platform eglfs” Eu estou recebendo mensagem como

“Could not initialize egl display
Aborted ”

Não tenho a certeza por que, também eu estou usando uma TV HDMI como um display.

– Ramesh

Diego Sueiro
Diego Sueiro
Reply to  Ramesh Devaraj
20/01/2015 06:17

Ramesh,

Please make sure that your local repo of meta-ti is updated.
If it’s already updated, please send me the result of “lsmod” command.

Ramesh Devaraj
Ramesh Devaraj
Reply to  Diego Sueiro
20/01/2015 08:34

Hello Deigo,

I tried to checkout latest version of the sources and build fresh, but now i am seeing this error while doing ‘bitbake -k qt5-image-demo’
“ERROR: Nothing RPROVIDES ‘packagegroup-qt5’
ERROR: No eligible RPROVIDERs exist for ‘packagegroup-qt5′”

Diego Sueiro
Diego Sueiro
Reply to  Ramesh Devaraj
21/01/2015 11:19

Ramesh,

All repos are on daisy branch? Except meta-qt5 that should be at dizzy branch.

Please send me your Build Configuration info which is printed out when you run bitbake command.

Christian Schultz
Xultz
09/01/2015 18:31

Olá, eu segui o tutorial, gravei o cartão SSD, e ao dar boot na placa, ele informa o seguinte erro:
File not found /boot/uImage
Olhando na partição rootfs do cartão, não tem o arquivo uImage, somente um chamado zImage. Eu errei alguma coisa na configuração? Ou devo simplesmente renomear o arquivo?

Obrigado

Diego Sueiro
Diego Sueiro
Reply to  Xultz
09/01/2015 18:52

Xultz,

Siga as instruções descritas na nota da seção Testando a imagem.

Christian Schultz
Xultz
Reply to  Diego Sueiro
09/01/2015 21:59

Olá, consegui resolver o problema seguindo as instruções do tutorial do Henrique. Ao copiar o arquivo uEnv.txt, o mesmo instrui o u-boot a carregar um arquivo do tipo zImage. Porém ele espera que esteja na partição de boot, e copiei os dois arquivos conforme o tutorial informa, e a placa bootou certinho. Não consegui rodar a aplicação pelo mesmo problema do Lucas Lui Motta, vou seguir as instruções citadas abaixo e tentar novamente.

Diego Sueiro
Diego Sueiro
Reply to  Xultz
10/01/2015 04:57

Xultz,

Atualize sua cópia do repositório da meta-ti pois esse problema já foi resolvido.

Victor Fernandez
Victor Fernandez
09/01/2015 12:05

Olá Diego, muito obrigado por este artigo. Eu espero que você possa me ajudar.
Segui todos os passos para gerar a imagem mas eu tenho alguns erros:

Diego Sueiro
Diego Sueiro
Reply to  Victor Fernandez
09/01/2015 12:23

Victor,

Mude a versão do kernel com os comandos:
“cd ~/yocto/poky-daisy/meta-ti; git checkout 31348244882a8defb640af75119ba275d9915f09”

E construa a imagem novamente.

Victor Fernandez
Victor Fernandez
Reply to  Diego Sueiro
09/01/2015 12:52

Olá Diego,

Depois de fazer o checkout, eu tenho esta resposta, mas eu não entendo.

Não obstante, eu posso construir a imagem novamente?.
Para construir novamente a imagen não é necessário eliminar alguns dos arquivos gerados pela construção anterio, ou só é necessário fazer:
cd ~/yocto
. poky-daisy/oe-init-build-env build-daisy
bitbake qt5-image-demo

Diego Sueiro
Diego Sueiro
Reply to  Victor Fernandez
09/01/2015 13:02

Victor,

Não precisa fazer nada.
Pode executar os comandos que vc mencionou.

Victor Fernandez
Victor Fernandez
Reply to  Diego Sueiro
10/01/2015 05:53

Olá Diego,

Depois de constuir a imagem novamente eu não tinha erros mas eu tive vários “Warnings”: http://pastebin.com/eh3tLhAx.

É necessário reconstruir a imagem ou eu posso gravar o cartão SSD?

Outra questão que eu tenho, ¿esta imagem funciona em uma placa com LCD7 CAPE?

muito obrigado pela vossa ajuda.

Diego Sueiro
Diego Sueiro
Reply to  Victor Fernandez
10/01/2015 06:20

Victor,

Não precisa se preocupar com esses warnings.

Vc terá que alterar o Device Tree com as configurações necessárias para o funcionamento do LCD.

Segue como referência:
https://github.com/beagleboard/linux/blob/3.14/arch/arm/boot/dts/am335x-bone-lcd7-01-00a3.dts

Note que existem vários includes também.

Se você não estiver muito familiarizado com Device Tree essa tarefa será um tanto árdua. 🙁

Victor Fernandez
Victor Fernandez
Reply to  Diego Sueiro
11/01/2015 16:33

Olá Diego,

Eu não tenho nenhuma experiência com Device Tree e eu não sei por onde começar.

Eu procurei todo dia na internet, mas não encontrou nada claro. Por favor, você pode me guiar?.

Muito obrigado pela sua paciência

Diego Sueiro
Diego Sueiro
Reply to  Victor Fernandez
11/01/2015 19:19

Victor,

Comece com os artigos do Sergio Prado sobre o tema:
http://sergioprado.org/?s=Device+Tree+

Na presentação dele sobre Linux Device Drivers no Seminário Programação para Sistemas Embarcados 2014 tem uma parte sobre Device Tree:
http://embarcados.com.br/apresentacoes-seminario-programacao-para-sistemas-embarcados-2014/

Victor Fernandez
Victor Fernandez
Reply to  Diego Sueiro
13/01/2015 16:33

Olá Diego,

Eu não sou capaz alterar o Device Tree com as configurações necessárias para o funcionamento do LCD. Esta é uma tarefa impossível para mim

Eu encontrei este LCD com “Ubuntu with Kernel 3.15, 3.17, 3.18 support” http://elinux.org/Nh7Cape

Pode ser compatível com Kernel 3.14.25 de Yocto?.

Obrigado.

Diego Sueiro
Diego Sueiro
Reply to  Victor Fernandez
13/01/2015 19:14

Victor,

Sim ele será compatível sem problemas.

Infelizmente não tenho um exemplar desse comigo para fazer as alterações necessárias e testar.

Não desista meu amigo. Você vai conseguir. 😉

Diego Sueiro
Diego Sueiro
Reply to  Diego Sueiro
14/01/2015 07:19

Victor, Como não sei qual a versão da cape LCD7 que você está usando, compilei esses dois dtbs disponíveis: https://github.com/beagleboard/linux/blob/3.14/arch/arm/boot/dts/am335x-bone-lcd7-01-00a3.dts https://github.com/beagleboard/linux/blob/3.14/arch/arm/boot/dts/am335x-bone-lcd7-01-00a2.dts Baixe os dtbs nesses links: https://drive.google.com/file/d/0Byvkmnfcr5auV1hyMkNhcHk4cnM/view?usp=sharing https://drive.google.com/file/d/0Byvkmnfcr5auZk01STVua2pUOWM/view?usp=sharing Agora você tem que apontar o dtb que o bootloader deve carregar. Para isso insira o cartão uSD no computador e copie os dtbs para a pasta /boot do uSD e crie um link simbólico para o arquivo am335x-boneblack.dtb. Siga esses comandos (altere o caminho do ponto de montagem o uSD): “sudo cp am335x-boneblack-lcd7-01-00a2.dtb /media/rootfs/boot” “sudo cp am335x-boneblack-lcd7-01-00a3.dtb /media/rootfs/boot” “cd /media/rootfs/boot” (digite o comando abaixo para usar a versão a3 da cape)… Leia mais »

Victor Fernandez
Victor Fernandez
Reply to  Diego Sueiro
15/01/2015 16:21

Muito, muito obrigado.

Eu tenho a cape LCD7 versâo A3. Eu fiz o que você me disse mas o display ainda não funciona. Agora, também não tenho salida HDMI.

Eu tenho no /media/pc2/rootfs/boot http://pastebin.com/5pEuh69v
Eu tenho no /media/pc2/boot http://pastebin.com/9QmdHrJS

Abraços.

Diego Sueiro
Diego Sueiro
Reply to  Victor Fernandez
15/01/2015 16:30

Victor,

Esse dtb eu compilei do repositório do projeto beagleboard (veja o link que mandei anteriormente).
Porém o kernel compilado é do repositório da Texas. Então pode ser que eles sejam incompatíveis. 🙁

Vc terá que criar o dts do LCD e compilar o dtb com o kernel da Texas.

No meu comentário anterior eu listei o comando para voltar ao dtb original, pois o LCD e a saída HDMI não funcionam ao mesmo tempo.

Talvez você goste:

Séries



Outros da Série

Menu

WEBINAR
 
Porque o RTOS não faz o que eu quero?

Data: 28/10 às 19:30h - Apoio: Mouser Electronics
 
INSCREVA-SE AGORA »



 
close-link