2019-11-19 12:09 PM
STM32CubeIDE: Version: 1.1.0
STM32MP1 FW Package:
I built a custom and default device tree for A7, and fails to compile because of a syntax error (same line in both cases)
| NOTE: make -j 12 HOSTCC=gcc -isystem/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/usr/include -O2 -pipe -L/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/usr/lib -L/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/lib -Wl,-rpath-link,/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/lib -Wl,-rpath,/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/usr/lib -Wl,-rpath,/repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/recipe-sysroot-native/lib -Wl,-O1 HOSTCPP=gcc -E stm32mp157c-m4_afe-mx.dtb
| GEN ./Makefile
| scripts/kconfig/conf --syncconfig Kconfig
| CC scripts/mod/empty.o
| CC scripts/mod/devicetable-offsets.s
| MKELF scripts/mod/elfconfig.h
| HOSTCC scripts/mod/modpost.o
| HOSTCC scripts/mod/sumversion.o
| HOSTCC scripts/mod/file2alias.o
| HOSTLD scripts/mod/modpost
| DTC arch/arm/boot/dts/stm32mp157c-m4_afe-mx.dtb
| Error: /repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work-shared/stm32mp1-m4_afe/kernel-source/arch/arm/boot/dts/stm32mp157c-m4_afe-mx.dts:113.23-24 syntax error
| FATAL ERROR: Unable to parse input tree
| scripts/Makefile.lib:293: recipe for target 'arch/arm/boot/dts/stm32mp157c-m4_afe-mx.dtb' failed
| make[3]: *** [arch/arm/boot/dts/stm32mp157c-m4_afe-mx.dtb] Error 1
| arch/arm/Makefile:343: recipe for target 'stm32mp157c-m4_afe-mx.dtb' failed
| make[2]: *** [stm32mp157c-m4_afe-mx.dtb] Error 2
| Makefile:146: recipe for target 'sub-make' failed
| make[1]: *** [sub-make] Error 2
| Makefile:24: recipe for target '__sub-make' failed
| make: *** [__sub-make] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /repo/build-openstlinuxweston-stm32mp1-m4_afe/tmp-glibc/work/stm32mp1_m4_afe-openstlinux_weston-linux-gnueabi/linux-stm32mp/4.19-r0/temp/log.do_compile.10586)
ERROR: Task (/repo/layers/meta-st/meta-st-stm32mp/recipes-kernel/linux/linux-stm32mp_4.19.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 695 tasks of which 614 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
Summary: 1 task failed:
/repo/layers/meta-st/meta-st-stm32mp/recipes-kernel/linux/linux-stm32mp_4.19.bb:do_compile
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
Inspecting the files the error should be on
led {
compatible = "gpio-leds";
blue {
label = "heartbeat";
gpios = <&gpiod 11 GPIO_ACTIVE_HIGH>; // This line is 113
linux,default-trigger = "heartbeat";
default-state = "off";
};
};
I tried removing that line and section, but other similar errors happen later on the code, any ideas what could be the issue ?
Regards !
Solved! Go to Solution.
2019-11-20 12:23 AM
Hi @Sebastian Sepulveda
Please confirm you are using distribution package from Release Openstlinux-4.19-thud-mp1-19-10-09
Can you please share you complete dts file ?
Thx
Olivier
2019-11-20 12:23 AM
Hi @Sebastian Sepulveda
Please confirm you are using distribution package from Release Openstlinux-4.19-thud-mp1-19-10-09
Can you please share you complete dts file ?
Thx
Olivier
2019-11-20 05:54 AM
Oliver,
I was using openstlinux-4.19-thud-mp1-19-02-20. I'll update to 19-10-09 and report back
2019-11-20 08:58 AM
@Community member
Thanks, with suggested release the build worked without errors.
Regards !