Building BSP ended up with no "deploy/images" directory

Technical Support
,
1

Hello,

This article states that the BSP build will end up with an archive output inside build/deploy/images/${MACHINE}/.

Everything went properly (without errors), but I do not have the “images” folder.

vmetodiev@vmetodiev:~/oe-core/build/deploy$ ls -la
total 20
drwxrwxr-x 4 vmetodiev vmetodiev 4096 Jan 30 19:53 .
drwxrwxr-x 7 vmetodiev vmetodiev 4096 Jan 30 19:55 ..
-rw-rw-r-- 1 vmetodiev vmetodiev    2 Jan 29 20:41 abi_version
drwxr-xr-x 9 vmetodiev vmetodiev 4096 Jan 30 18:21 ipk
drwxrwxr-x 2 vmetodiev vmetodiev 4096 Jan 30 19:53 sdk

Could you please advise what has happened?

2

Hi @vmetodiev,

I recommend you try find . -name "images in the build directory.

Let me know if you found it.

Best Regards
Kevin

3

Hi Kevin,

I looked at the results from find . -name ‘images’ but the results are a bit overwhelming for copy-paste.

Nevertheless, I think I managed to find something relevant:

vmetodiev@vmetodiev:~/oe-core/build$ tree | tee | grep 'Image'
│       └── tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6
│           └── Reference-Multimedia-Image

vmetodiev@vmetodiev:~/oe-core/build$ sudo updatedb

vmetodiev@vmetodiev:~/oe-core/build$ locate Reference-Multimedia-Image
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/files-in-sdk.txt
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/host
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/sdk-info.txt
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/target
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/host/depends.dot
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/host/installed-package-names.txt
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/host/installed-package-sizes.txt
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/host/installed-packages.txt
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/target/depends.dot
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/target/installed-package-names.txt
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/target/installed-package-sizes.txt
/home/vmetodiev/oe-core/build/buildhistory/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6/Reference-Multimedia-Image/target/installed-packages.txt
/home/vmetodiev/oe-core/build/deploy/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6-toolchain-5.5.0.host.manifest
/home/vmetodiev/oe-core/build/deploy/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6-toolchain-5.5.0.sh
/home/vmetodiev/oe-core/build/deploy/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6-toolchain-5.5.0.target.manifest
/home/vmetodiev/oe-core/build/deploy/sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6-toolchain-5.5.0.testdata.json
/home/vmetodiev/oe-core/build/tmp/work/apalis_imx6-tdx-linux-gnueabi/tdx-reference-multimedia-image/1.0-r0/x86_64-deploy-tdx-reference-multimedia-image-populate-sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6-toolchain-5.5.0.host.manifest
/home/vmetodiev/oe-core/build/tmp/work/apalis_imx6-tdx-linux-gnueabi/tdx-reference-multimedia-image/1.0-r0/x86_64-deploy-tdx-reference-multimedia-image-populate-sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6-toolchain-5.5.0.sh
/home/vmetodiev/oe-core/build/tmp/work/apalis_imx6-tdx-linux-gnueabi/tdx-reference-multimedia-image/1.0-r0/x86_64-deploy-tdx-reference-multimedia-image-populate-sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6-toolchain-5.5.0.target.manifest
/home/vmetodiev/oe-core/build/tmp/work/apalis_imx6-tdx-linux-gnueabi/tdx-reference-multimedia-image/1.0-r0/x86_64-deploy-tdx-reference-multimedia-image-populate-sdk/tdx-xwayland-glibc-x86_64-Reference-Multimedia-Image-armv7at2hf-neon-apalis-imx6-toolchain-5.5.0.testdata.json

However, the location ‘buildhistory’ does not sound quite opitimistic to me…
What do you think?

4

Hi @vmetodiev

can you please send us the output of “tree -d” in your work directory, so that we can have a look at it.

Best Regards
Kevin

5

Hi,

Well, I executed the requested command and redirected the stdout to a file. However, the file is huge…

vmetodiev@vmetodiev:/tmp$ ls -larts --human | grep txt
 73M -rw-rw-r--  1 vmetodiev vmetodiev  73M Feb  8 19:32 treed.txt
6

Hi @vmetodiev ,

I guess you might have launched the command a bit too high up in your file structure.

Did you do the command in this directory /home/vmetodiev/oe-core/ ?

I did it on my end too and the file is around 300kBytes large.

Best Regards
Kevin

7

Hi @kevin.tx,

Well, I forgot to tell you that the initial command that I executed was:

bitbake <image> -c populate_sdk

I have now started the build again, from scratch, with only:

bitbake <image>

Best Regards,
Varban

8

Hi @vmetodiev !

Please, let us know the result.

Best regards,

9

Hello @henrique.tx,

I managed to compille and flash the image. However, I have two questions before finishing the thread:

  1. The image starts a sample video library application… not quite industrial vision, IMO… How can I replace this with my QT app (if possible, using the Wayland backend).
  2. What are the default SSH credentials?

Best regards!

10

Hi @vmetodiev ,

Glad to hear that you managed to compile it.

  1. The sample video library application you see is actually using wayland. You can kill this application by entering killall Qt5_CinematicExperience
    For more information about how to implement Qt on our modules you can follow this link

https://developer-next.toradex.com/linux-bsp/how-to/gui/

  1. You can see the SSH credentials here

Best Regards
Kevin

11

Hi @kevin.tx ,

I managed to SSH, thanks a lot for the directions!

One last question - what is the name of the systemd service that launches the Qt5_CinematicExperience?

12

Hi @vmetodiev ,

Great, glad to hear that SSH worked.

The name of the system service should be wayland.

Best Regards
Kevin

13

Hi again @kevin.tx

Managed to find it:

root@apalis-imx6-10618783:~# systemctl list-units | tee | grep way
wayland-app-launch.service loaded active running Start a wayland application

Thank you very much for your support. We can close this thread!

Best regards,
Varban

14

Hi @vmetodiev ,

Glad that it worked.

Best Regards
Kevin