Build failed with agl-sota for rpi3

Description

 I tried to build an image with the agl-sota functionnality:

repo init -b guppy -m guppy_7.0.1.xml -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo.git repo sync git clone --branch rocko https://www.github.com/advancedtelematic/meta-updater-raspberrypi.git source meta-agl/scripts/aglsetup.sh -m raspberrypi3 agl-demo agl-appfw-smack agl-sota

I ensure that ${METADIR}/meta-updater-raspberrypi is added at BBLAYERS  in bblayers.conf, then I run

bitbake agl-demo-platform

Build fails with the following error:

ERROR: create-combined-dtb-1.0.0-r1 do_compile: Function failed: do_compile (log file is located at /media/sebastien/18b81cab-7f1d-4519-823f-adc569b21d87/AGL/workspace-agl/build/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/create-combined-dtb/1.0.0-r1/temp/log.do_compile.4872) ERROR: Logfile of failure stored in: /media/sebastien/18b81cab-7f1d-4519-823f-adc569b21d87/AGL/workspace-agl/build/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/create-combined-dtb/1.0.0-r1/temp/log.do_compile.4872 Log data follows: | DEBUG: Executing shell function do_compile | Couldn't open blob from '/media/sebastien/18b81cab-7f1d-4519-823f-adc569b21d87/AGL/workspace-agl/build/tmp/deploy/images/raspberrypi3/uImage-bcm2710-rpi-3-b-plus.dtb': No such file or directory | | Failed to read base blob /media/sebastien/18b81cab-7f1d-4519-823f-adc569b21d87/AGL/workspace-agl/build/tmp/deploy/images/raspberrypi3/uImage-bcm2710-rpi-3-b-plus.dtb | input = /media/sebastien/18b81cab-7f1d-4519-823f-adc569b21d87/AGL/workspace-agl/build/tmp/deploy/images/raspberrypi3/uImage-bcm2710-rpi-3-b-plus.dtb | output = uImage-bcm2710-rpi-3-b+vc4+ft5406.dtb | overlay[0] = /media/sebastien/18b81cab-7f1d-4519-823f-adc569b21d87/AGL/workspace-agl/build/tmp/deploy/images/raspberrypi3/rpi-ft5406.dtbo | overlay[1] = /media/sebastien/18b81cab-7f1d-4519-823f-adc569b21d87/AGL/workspace-agl/build/tmp/deploy/images/raspberrypi3/uImage-vc4-kms-v3d.dtbo | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at /media/sebastien/18b81cab-7f1d-4519-823f-adc569b21d87/AGL/workspace-agl/build/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/create-combined-dtb/1.0.0-r1/temp/log.do_compile.4872) ERROR: Task (/media/sebastien/18b81cab-7f1d-4519-823f-adc569b21d87/AGL/workspace-agl/meta-agl/meta-agl-bsp/meta-raspberrypi/recipes-kernel/create-combined-dtb/create-combined-dtb_1.0.0.bb:do_compile) failed with exit code '1'

The file uImage-bcm2710-rpi-3-b-plus.dtb is indeed missing.

Please find in the attachements the content of  the workspace-agl/build/tmp/deploy/images/raspberrypi3/ directory given by "ls -l".

What I could see so far is that meta-updater sets KERNEL_IMAGETYPE to "fitImage", then linux-raspberrypi recipe creates dtb files with a "zImage" prefix (is it the expected behavior?) and eventually create-combined-dtb task is looking for dtb files with a "uImage" prefix.

 

Any advice?

PS: build without agl-sota option runs successfully. 

 

Environment

None

Attachments

3

Activity

Walt Miner 
September 6, 2019 at 8:36 PM

Close for Halibut 8.0.1 release

Leon Anavi 
September 5, 2019 at 3:36 PM

Hi,

The fixes have been merged in master and halibut branches. I have added notes about SOTA in the AGL wiki article for Raspberry Pi.

Best regards,
Leon

Leon Anavi 
August 30, 2019 at 5:46 PM
(edited)

Hi ,

Thank you for the help to figure out this issue. I have submitted a patch to master that adds 'cma=256M' to OSTREE_KERNEL_ARGS. With this fix weston works and the home screen appears for images with enabled agl-sota feature on Raspberry Pi 3 B and B+.

Best regards,
Leon

Jan-Simon Moeller 
August 30, 2019 at 1:44 PM
(edited)

Yep, kernel args are missing 'cma=256M'

 

See the dmesg vs  e.g. https://lava.automotivelinux.org/scheduler/job/7016#L262

Jan-Simon Moeller 
August 30, 2019 at 1:42 PM

Gut feeling: dtb or kernel arg differences.

Fixed

Details

Assignee

Reporter

Labels

Contract ID

Hardware Platform(s) Affected

Raspberry Pi 3

Components

Priority

Created August 5, 2019 at 8:41 AM
Updated September 19, 2019 at 12:07 PM
Resolved September 5, 2019 at 3:36 PM

Flag notifications