Angstrom-lxde-image no deploy package found after build

Technical Support
, , , ,
1

Hello,

I’m constructing a system that has some preset requirements. Below are some of the references I have looked at to fix this issue. I am having an issue building the angstrom-lxde-image package. Much like console and qt-x11, I would like to be able to open the package and flash to my target.

repo init -u Index of /toradex-bsp-platform.git -b fcba09744c6f1aeb7339d175fe3a633f6978a5b0

any known reason this may be happening? I started with a new VM. the first build didn’t have anything in the build file either.

2

Hi

Could you elaborate a little more what you are doing and what along the way does not work as you expected.

Please also compare with our main page about how to set up OE and to build here.

Is there a specific reason why you want to setup your layer versions to that specific commit in the manifest: fcba09744c6f1aeb7339d175fe3a633f6978a5b0?

Max

3

Hey Max,

I’m not entirely sure why this particular repo issued to be totally honest. We are incorporating ROS and QT into our image all for subsea navigation.

I follow the main page, until the repo, then I use the one I was given. I don’t see many differences aside from the meta-files. Our repo uses meta-fsl-arm and the linux2.7 uses meta freescale. That was the primary error I saw when I attempted a repo sync with the 2.7 image. From what I understand the version of ROS we are running, and up until recently we were using qt4. I have upgraded out project to qt5. The original project was focused on qtwebkit and displaying with frame buffers – primary reason for this was image speed, and overall processing. Having worked those issues out programatically, we can go back to full or partial Desktop Image.

All of the other methods to building images work well. it is only the LXDE image that does not produce the package. I will be attempting the qt-x11-image soon to see if that will work for us. We really would like the full DT environment. It adds a sense of comfortability with the client, as well as troubleshooting in the future.

4

Here are a couple new issues the system has come up with.

Im running a “new” build now… on the 2.7

WARNING: keybinder: No generic license file exists for: X11 in any provider
WARNING: The license listed X11 was not in the licenses collected for recipe keybinder
WARNING: The license listed X11 was not in the licenses collected for recipe keybinder
WARNING: [log_check] angstrom-lxde-image: found a warning message in the logfile (keyword 'WARNING:'):
[log_check] WARNING: The license listed X11 was not in the licenses collected for recipe keybinder

WARNING: [log_check] angstrom-lxde-image: found a warning message in the logfile (keyword 'WARNING:'):
[log_check] WARNING: The license listed X11 was not in the licenses collected for recipe keybinder

WARNING: [log_check] In line: [Collected errors:
]
WARNING: [log_check] angstrom-lxde-image: found an error message in the logfile (keyword 'Collected errors'):
[log_check] Collected errors:

ERROR: 
Collected errors:

 * satisfy_dependencies_for: Cannot satisfy the following dependencies for gvfs-gdu-volume-monitor-dev:

 * 	avahi-daemon (= 0.6.31-r11.0) * 	libavahi-core7 (= 0.6.31-r11.0) * 	libavahi-client3 (= 0.6.31-r11.0) * 

 * opkg_install_cmd: Cannot install package gvfs-gdu-volume-monitor-dev.

amer1.0-plugins-good-videofilter-dev.


ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/bot/oe-core/build/tmp-glibc/work/apalis_imx6-angstrom-linux-gnueabi/angstrom-lxde-image/V2.6.1-r0/temp/log.do_rootfs.29962
ERROR: Task 7 (/home/bot/oe-core/build/../layers/meta-toradex-demos/recipes-images/images/angstrom-lxde-image.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 9402 tasks of which 9101 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
No currently running tasks (9402 of 9407)

Summary: 1 task failed:
  /home/bot/oe-core/build/../layers/meta-toradex-demos/recipes-images/images/angstrom-lxde-image.bb, do_rootfs
Summary: There were 7 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
5

Seems like the same issue in the “updated” build. However this time, none of the images have a kernel that will run.

Everything appears normal… Just stops running.

start to finish in u-boot::

Apalis iMX6 #              

U-Boot 2015.04+fslc+g46aa70c (Aug 22 2017 - 03:34:56)

CPU:   Freescale i.MX6Q rev1.5 at 792 MHz
CPU:   Temperature 43 C
Reset cause: POR
I2C:   ready
DRAM:  2 GiB
force_idle_bus: sda=0 scl=1 sda.gp=0x9a scl.gp=0x9b
force_idle_bus: failed to clear bus, sda=0 scl=1
PMIC: device id: 0x10, revision id: 0x11
PMIC: programmed
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
auto-detected panel HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
Model: Toradex Apalis iMX6 Quad 2GB IT V1.1A, Serial# 04875670
Net:   using PHY at 7
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot:  0 
Apalis iMX6 # run setupdate
MMC: no card present
** Bad device mmc 1 **
reading flash_blk.img
710 bytes read in 14 ms (48.8 KiB/s)
## Executing script at 12000000
reading apalis_imx6/flash_blk.img
3978 bytes read in 20 ms (193.4 KiB/s)
## Executing script at 12000000
enter "run update" or "run update_it" to update the entire module
Apalis iMX6 # run update_it
reading apalis_imx6/u-boot.imx-it
322560 bytes read in 37 ms (8.3 MiB/s)
switch to partitions #1, OK
mmc0(part 1) is current device

MMC write: dev # 0, block # 2, count 630 ... 630 blocks written: OK
Fuse 0, 5:     5072
Fast boot mode already fused, no need to fuse
reading apalis_imx6/mbr.bin
512 bytes read in 17 ms (29.3 KiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 0, count 1 ... 1 blocks written: OK
reading apalis_imx6/boot.vfat
16777216 bytes read in 784 ms (20.4 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 8192, count 32768 ... 32768 blocks written: OK
reading apalis_imx6/uImage
4945368 bytes read in 249 ms (18.9 MiB/s)
writing uImage
4945368 bytes written
reading apalis_imx6/imx6q-apalis-eval.dtb
48453 bytes read in 29 ms (1.6 MiB/s)
writing imx6q-apalis-eval.dtb
48453 bytes written
reading apalis_imx6/root.ext3
67108864 bytes read in 3080 ms (20.8 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 40960, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3091 ms (20.7 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 172032, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3098 ms (20.7 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 303104, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3108 ms (20.6 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 434176, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3119 ms (20.5 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 565248, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3126 ms (20.5 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 696320, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3136 ms (20.4 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 827392, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3147 ms (20.3 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 958464, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3153 ms (20.3 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 1089536, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3163 ms (20.2 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 1220608, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3174 ms (20.2 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 1351680, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3180 ms (20.1 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 1482752, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3191 ms (20.1 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 1613824, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3202 ms (20 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 1744896, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3209 ms (19.9 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 1875968, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3220 ms (19.9 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 2007040, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3230 ms (19.8 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 2138112, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3236 ms (19.8 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 2269184, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3247 ms (19.7 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 2400256, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
67108864 bytes read in 3257 ms (19.6 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 2531328, count 131072 ... 131072 blocks written: OK
reading apalis_imx6/root.ext3
** apalis_imx6/root.ext3 shorter than offset + len **
2097152 bytes read in 309 ms (6.5 MiB/s)
switch to partitions #0, OK
mmc0(part 0) is current device

MMC write: dev # 0, block # 2662400, count 4096 ... 4096 blocks written: OK
resetting ...


U-Boot 2015.04+fslc+g46aa70c (Aug 22 2017 - 03:34:56)

CPU:   Freescale i.MX6Q rev1.5 at 792 MHz
CPU:   Temperature 59 C
Reset cause: WDOG
I2C:   ready
DRAM:  2 GiB
force_idle_bus: sda=0 scl=1 sda.gp=0x9a scl.gp=0x9b
force_idle_bus: failed to clear bus, sda=0 scl=1
PMIC: device id: 0x10, revision id: 0x11
PMIC: programmed
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
auto-detected panel HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
Model: Toradex Apalis iMX6 Quad 2GB IT V1.1A, Serial# 04875670
Net:   using PHY at 7
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot:  0 
Booting from internal eMMC chip...
reading imx6q-apalis-eval.dtb
48453 bytes read in 18 ms (2.6 MiB/s)
reading uImage
4945368 bytes read in 143 ms (33 MiB/s)
## Booting kernel from Legacy Image at 11000000 ...
   Image Name:   Linux-3.14.52-v2.6.1b1+g3894f6d
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4945304 Bytes = 4.7 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 12000000
   Booting using the fdt blob at 0x12000000
   Loading Kernel Image ... OK
   Using Device Tree in place at 12000000, end 1200ed44

Starting kernel ...
6

Hi

Are you sure that you really checked out the layers for one of our 2.7 releases?
At least this path suggests otherwise:

ERROR: Logfile of failure stored in: /home/bot/oe-core/build/tmp-glibc/work/apalis_imx6-angstrom-linux-gnueabi/angstrom-lxde-image/V2.6.1-r0/temp/log.do_rootfs.29962

Also it seems rather strange that when building the package gvfs-gdu-volume-monitor-dev package that that build should have recorded a dependency on avahi version 0.6.31-r11.0 but no package providing that is now available.

So it would be interesting to see what layers you configured in what version. E.g. the beginning of a bitbake output which outputs some essential configuration settings and all configured layers with their associated git hash.

Max