You're not saying what the configure file is and where is it. Can you show that?
Help arrives quicker if we can reproduce the problem or at least see
your setup exactly.
Does log.do_rootfs for your image say which version of wpa supplicant
gets installed?
Alex
On Wed, 12 Feb 2025 at 20:57, John
Alexander,
Thanks for your reply.
I've attached my new configure file that lives in:
poky/meta-raspberrypi/conf/machine
Mea Culpa: I created this configure file and am using the MACHINE ??=
"raspberrypi0-64-wf.conf" in my local.conf file.
Since the raspberrypi Zero support does not work out o
And I'm now adding the recipe file that I created (sorry, should have been in
the previous message). I just copied the original recipe file. Pretty sure that
isn't how it's supposed to be done but I'm going backwards in version, not
forwards. Not sure how that would be handled.
And for good mea
Sure, but do you still have a problem? I'm not certain after reading
your messages.
Alex
On Thu, 13 Feb 2025 at 16:09, John via lists.yoctoproject.org
wrote:
>
> And I'm now adding the recipe file that I created (sorry, should have been in
> the previous message). I just copied the original rec
Hello,
I'm trying to build the gcc toolchain with Yocto.
I'm currently building it with `bitbake meta-toolchain -c populate_sdk`
and then running the installer
`tmp/deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-5.2.999.sh`.
gcc and g++ work fine, but gfortran doesn't, g
So, I added "dhcpcd" to this line in my local.conf file:
>
> IMAGE_INSTALL:append = " linux-firmware-bcm43430 bluez5 i2c-tools
> wpa-supplicant dhcpcd"
>
and voila, I have my wpa_supplicant v2.9 installed so any ideas why this
worked?
And with that, I ran the wpa_supplicant and I now have
And now I have a working raspberrypi Zero 2 W with wifi (comes up
automatically) and probably a working Bluetooth (not of importance to me right
now but there appears to be an interface for it).
With the addition of the dhcpcd s/w shown above I had a working wpa-supplicant
as it replaced the 2.
Hi all,
I am wanting to debug on my target with gdb, so added the debug symbols by
adding the -dbg to the IMAGE_INSTALL variable.
This does indeed get the debug symbols onto the target, but no source code.
After reading the information on the PACKAGE_DEBUG_SPLIT_STYLE I realised that
it default
Yes
Cheers!!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#64803): https://lists.yoctoproject.org/g/yocto/message/64803
Mute This Topic: https://lists.yoctoproject.org/mt/49982/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe:
Hi all,
I read through the conversation & I thought I'd suggest the following below. I
am not sure of this suggestion but I hope it lays well with the requirements.
I suggest we divide the repo management into two repos: a Contributors Repo &
Non-contributors' Repo.
1. Have the main repo be part
*(presuming "users" means-> non-contributors which means no PRs & therefore no
need to manage PR in the user repo)*
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#64807): https://lists.yoctoproject.org/g/yocto/message/64807
Mute This Topic: https:/
11 matches
Mail list logo