Re: [yocto] Modify target 'march' for RISCV VisionFive 2

I'm using a KAS setup ( https://github.com/OOHehir/build-riscv/blob/main/poky-qt-visionfive2.yml ) & added the following line: TUNE_CCARGS = "-march=rv64imafdc_zicsr_zifencei_zihintpause" It seems to have resulted in a successful build of qtbase (following rebuilds of gcc etc) I imagine

Re: [yocto] Modify target 'march' for RISCV VisionFive 2

t 6, 2023 at 9:44 AM Electronic Consult > wrote: > > > > Hello all, > > > > I'd like to try building Qt6 for the RISCV VisionFive 2 board. My first > attempt returns the error (full error at the bottom): > > > > Error: unrecognized opcode `pause', exten

[yocto] Modify target 'march' for RISCV VisionFive 2

Hello all, I'd like to try building Qt6 for the RISCV VisionFive 2 board. My first attempt returns the error (full error at the bottom): Error: unrecognized opcode `pause', extension ` *zihintpause* ' required It seems I need to append _zihintpause to the target march. Currently

Re: [yocto] [meta-raspberrypi] vc4-fkms-v3d vs. vc4-kms-v3d

Manuel, Most of what you require should be here: https://github.com/OOHehir/meta-test The key bits to enabling EGLFS seem to be: PACKAGECONFIG:remove:rpi = "x11 wayland" PACKAGECONFIG:append:rpi = " examples accessibility eglfs gles2 gbm linuxfb tslib libinput" I found I wasn't getting any

Re: [yocto] [meta-raspberrypi] vc4-fkms-v3d vs. vc4-kms-v3d

Hello folks, I'm in the same situation as Manuel (RPi4, official touchscreen) & have come to a similar conclusion. I had issues getting a graphics output on the screen until I used: VC4DTBO = "vc4-fkms-v3d-pi4" With this I can get both console output & graphics. I used the attached kas file

Re: [yocto] [meta-raspberrypi] [meta-qt6] Building qt6 on rpi4

Looks like I've got a solution. My qtbase_git.bbappend now contains: DISTRO_FEATURES:remove:rpi = " x11 wayland" PACKAGECONFIG:append:rpi = " accessibility eglfs fontconfig gles2 linuxfb tslib gbm" & this now results in an output of bitbake -v -c configure qtbase EGL

[yocto] [meta-raspberrypi] [meta-qt6] Building qt6 on rpi4

Hello all, I'm using: Kirkstone meta-raspberry meta-qt6 (v6.5) >From this post from Qt they suggest the correct graphics setup for a RPi4 should be: *With the Raspberry Pi 4 example, we expect that EGL, OpenGL ES and EGLFS GBM are all reported

Re: [yocto] Autotools build failure #kirkstone #autotools

Martin, Thanks for the pointer, I manged to get the recipe working with your help. For anyone else looking at this the issue was resolved with this ( https://github.com/linux4sam/meta-atmel/pull/247/commits/353dcfe62bbc4b6a10eb5926b7c87cc2f4774a1b ). Hope it helps someone else! Owen

[yocto] Autotools build failure #kirkstone #autotools

Hello all, I'm moving my build from Dunfell to Kirkstone & an issue with gstreamer1.0-plugins-hantro ( https://github.com/linux4sam/meta-atmel/tree/kirkstone/recipes-multimedia/gstreamer1.0-plugins ) has cropped up. This recipe inherits autotools-brokensep. During the build I initially got:

Re: [yocto] [meta-raspberrypi] - problem adding meta-qt6 SDK #sdk

Hello again, For anyone looking at this I managed to get the qt6 SDK added to an image based on poky using: inherit core-image TOOLCHAIN_HOST_TASK += "\ nativesdk-packagegroup-qt6-toolchain-host \ " Seems obvious now! Hope this helps other! Owen -=-=-=-=-=-=-=-=-=-=-=- Links: You receive

[yocto] [meta-raspberrypi] - problem adding meta-qt6 SDK #qt #sdk

Hello all, I'm using dunfell with meta-raspberrypi & meta-qt6 ( https://code.qt.io/yocto/meta-qt6.git ), v6.2.24 under the open-source license. I've successfully built a simple qt6 application with the setup but now trying to build the SDK to support Qt6 development on the RPi. As per Qt

Re: [yocto] Correct build folder location

As an update for anyone looking at this.. I managed to get the raspberry pi build going. It seems after running source oe-init-build-env rpi-build the local.conf from meta-atmel was copied into the rpi-build folder. This local.conf amongst other things had DISTRO ?= "poky-atmel" Which was

[yocto] Correct build folder location

Hello all, I'm using Dunfell & up to know I've being using meta-atmel to build images. I'd like to now add the capability to build images using meta-raspberrypi but I'm having issues with the source oe-init-build-env step, it keeps pulling in the meta-atmel shell environment. My folder layout is

[yocto] No SSH access after removing debug_tweaks

Hello all, I'm trying to add a root password to add some security to ssh access. I plan also to enable/ disable the ssh via GUI. I'm using meta-atmel on a dunfell build. I've added: INHERIT += "extrausers" EXTRA_USERS_PARAMS = "usermod -p $(openssl passwd mypassword) root" And commented out:

[yocto] AWS S3 bucket access from a C++ application?

Hello all, I have a device on which the main application is a C++ based GUI. I'm working on implementing an A/B update strategy using swupdate with the firmware being hosted on a AWS S3 bucket. The user needs to be able to use the GUI to check for updates & if available apply them (I can

[yocto] fw_env.config - finding the location of uboot.env

Hello all, I'm in the process of implementing an A/B update strategy on an SD card using swupdate & the tools provided by libubootenv-bin. The issue is finding the location of uboot.env to (manually) configure etc/fw_env.config. I've tried so far include checking the default env location config

[yocto] Setting recipe PACKAGECONFIG with in a Bash script?

Hello, I've searched & can't seem to find an answer for this but I'm sure it must have come up before. I'd like to automate the generating of images using Bash & create similar recipes but with different PACKAGECONFIG's. How does one do that? It would be something like: #! /bin/bash source

[yocto] Resistive touchscreen calibration for libinput

Hello all, Apologies if this is the incorrect group to post to, I haven't posted previously. I'm working with an Atmel/ Microchip SAMA5D4 Xplained board & a resistive touchscreen. I'm using a GUI framework that has issues dealing with evdev & tslib so looks like I need to find a screen