u-boot 2025.01 fails with exit 137 after including fastboot menuconfig options

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

u-boot 2025.01 fails with exit 137 after including fastboot menuconfig options

134件の閲覧回数
edwardtyrrell
Senior Contributor I

Hi All,

Frustrating issue after adding fastboot options to u-boot build via bitbake u-boot-fslc -c menuconfig. One the build is set in motion the host machine grinds to a halt then errors with:      ......recipes-bsp/u-boot/u-boot-fslc_2025.01.bb:do_compile) failed with exit code '137'

I've tried a number of possible fixes i.e limiting build threads, other CONFIGs but nothing works. Apparently its a memory consumption issue to do with config files? U-boot is small in comparison and typically takes under a minute to build, adding the FB options in it takes 4-5 minutes before it crashes the build.

Build machine is Ubuntu 22.04, Yocto 6.12.20, u-boot 2025.01 

Thanks!

 

0 件の賞賛
返信
1 返信

76件の閲覧回数
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello,

Exit code 137 specifically signifies termination by SIGKILL (signal 9), as 128 + 9 = 137. SIGKILL is a non-catchable, non-ignorable signal that forces a process to terminate immediately. During the compilation process of U-Boot, especially in environments with limited resources (e.g., virtual machines, containers, or embedded systems with constrained memory), the build process might exceed available memory, leading to its termination by the 137 error.

 

Regards

0 件の賞賛
返信