Hi! I'm a new Yocto user trying to develop a fork of Chirpstack's Gateway OS for Raspberry Pi based LoRaWAN gateways. Although I have successfully modified and added new recipes, I'm struggling with a

#raspberrypi

Yeah it works. I have yet to test the image on my raspberry pi Monday in the office. But I finished the build. I will tested Monday and i will tell you. I have a warning : image-1.0-r0 do_rootfs: The

#av1 #armv6 #raspberrypi #neon

Please try applying below patch to aom recipe in meta-openembedded repo https://lists.openembedded.org/g/openembedded-devel/topic/meta_multimedia_patch_aom/80743335?p=,,,20,0,0,0::recentpostdate%2Fsti

#av1 #armv6 #raspberrypi #neon

Sorry to annoying you with my question but how do i find where HAVE_NEON is set ? Best regards, Safouane

#av1 #armv6 #raspberrypi #neon

Well we do not enable neon for this tune but aom still seems to want it so I would suggest to look at the build and see if it’s disabling neon and have HAVE_NEON is not set properly

#av1 #armv6 #raspberrypi #neon

I have an erreur: | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:525:24: note: called from here | 525 | cons

#av1 #armv6 #raspberrypi #neon

can you try adding EXTRA_OECMAKE += "-DHAVE_NEON=0" and see if that helps ? for whatever reason set_aom_detect_var is enabling it where as default should be 0 <maaloulsafouane@...> wrote:

#av1 #armv6 #raspberrypi #neon

I succed in removing callconvention-hard from TUNE_FEATURES ? But i have the same problem. I am pretty sure that i get get it working if i add neon to the TUNE_FEATURES. Something like this TUNE_FEATU

#av1 #armv6 #raspberrypi #neon

https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES https://www.yoctoproject.org/docs/current/mega-manua

#av1 #armv6 #raspberrypi #neon

Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ? Best regards, Safouane

#av1 #armv6 #raspberrypi #neon

Here is an interesting reading for you, for me also: https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html What I am getting from this reading is that you need to try with the follo

#av1 #armv6 #raspberrypi #neon

#av1 #armv6 #raspberrypi #neon

#av1 #armv6 #raspberrypi #neon

So, what is your MACHINE variable set to? Maybe knowing that, somebody can help. Zee

#av1 #armv6 #raspberrypi #neon

Hello folks, I have an issue integrating av1 in yocto. I get the compile error "compiling simd-neon.h requires -mfpu=neon or equivalent". The problem is that i use armv6 (raspberrypi zero w) so i can'

#av1 #armv6 #raspberrypi #neon

Hello folks, i am trying to compile my image but we could see that i am missing neon fpu in my image. I can't use this feature because i have a raspberry pi zero w and i have armv6 on this raspberrypi

#raspberrypi #neon #yocto #armv6

Hello Team, I need to use High availability cluster in my project. I'm generating OS for Rpi using Ycot. I'm using dunfell poky version 3.1.3. I'm adding ntp tzdata pacemaker haveged and crmsh command

#dunfell #raspberrypi #yocto

Dear all, I have 4 different topics on which I can't find a correct answer on internet. I am developing a new system base on the Raspberrypi CM3+ with our custom board. I am using Yocto with the meta-

#raspberrypi #rpi #cm3 #dunfell #kernel

Hi Team, I've built OS for rpi3 using dunfell yocto. I've also generated SDK for the same, for that I've added these info in my local.conf file- TOOLCHAIN_TARGET_TASK_append = " python3-dev kernel-dev

#dunfell #raspberrypi #sdk

Hi, You should try a clean-up and then retry to build the package. I wrongly thought that that this error: ```Exception: KeyError: 'getpwuid(): uid not found: 1000'``` was due to the fact that I was w

#yocto #raspberrypi