Hello -
I’m attempting to get Bluetooth support onto Mangoh Red with WP7702.
My attempts to build from the packages that Sierra provides have not been successful.
Can anyone provide Yocto configuration files appropriate for this, with or without the Bluetooth support?
Out-of-the box, this is not set to build for WP7702. I run the top-level Makefile, and it creates a default local.conf for Yocto which specifies:
MACHINE ??= “qemux86”
This is not appropriate.
The best instructions so far seem to be this, but I am blocked by the missing configuration information.
Hi
We wont be able to support Bluetooth on Red.
However, we are able to support Bluetooth on Yellow. Today we are able to discover and connect to TI sensor tag on Yellow. What use case are u looking at?
Thanks Asyal -
How about providing local.conf and other config information we’d need to reproduce the current released build?
I was very surprised to find that the 3 gb packages I downloaded from Sierra were not set up out of the box.
Thanks
Hi @gjames,
After downloading the source tar-ball, you will need to run one of the Makefile targets to create
your build directory. Usually, it is “make image_bin”. Then you should get a local.conf created under
build_bin/conf. Then try your bluetooth enhancements. Please note that Red Bluetooth is
not supported as @asyal mentioned above.
Hi Zahid -
I have run make image_bin and it does produce
build_bin/conf/local.conf
but this local.conf is setting
MACHINE ??= “qemux86”
Do I need an argument to ‘make image_bin’ to specify the target hardware? What is the target hardware or MACHINE for mangoh Red?
If you can share the configuration files and commands used to build your released system images, that would clear this up. I have not found a good source for that information. Also, I am new to Yocto, so any step-by-step guide that is written specifically for the Mangoh Red would be very helpful.
I see these instructions
but they do not explain the local.conf MACHINE= setting, so I do not know what to use, and qemux86 is the Yocto default for their x86 emulator target.
Hi @gjames,
After I do a “make image_bin” in the local.conf I get something like the following: #MACHINE ?= “qemuarm”
.
.
.
#This sets the default machine to be qemux86 if no other machine is selected:
MACHINE = “swi-mdm9x28-wp”
The last setting is the target machine. I suggest you start from scratch by doing a
make clean and then an image_bin. In regards to Yocto I suggest you read the manuals: https://www.yoctoproject.org/docs/
before you continue. Btw, I also don’t do any other configuration or commands besides
image_bin to get an initial build. bitbake is for later.
Lastly, I am unsure about the wiki page referenced - the writer will be back on Tuesday.
Also, in the wiki page the module referenced is wp85 & you are on a wp77.
Hi gjames,
I just did a external download from the source tarball you mentioned above. After untar a
“make image_bin” does generate the correct local.conf. If “make clean” and them image_bin
does not fix your target, you must have some incorrect Yocto settings in your environment
space. As I mentioned above, please go through the Yocto guides (a quick start exists also).
Thanks Zahid -
Good news. I got the VM image from Sierra and tried again from there. With the tarball for WP77xx that I mentioned before, I got MACHINE = “swi-mdm9x28-wp” without any fuss. This is great.
Before, I had tried from a machine booting direct to Ubuntu, not from the Sierra VM, and that gave me the qemux86.
Yep - I understand the different settings / commands for the online instructions vs for my own WP77xx module, and will be tweaking the steps to suit my hardware. I’m trying the instructions as they are now, just to see that they work. Then I’ll alter them for my module.
The following command from the instructions fails:
bitbake linux-yocto -c kernel_configme -f
WARNING: Layer swi-wp-bin should set LAYERSERIES_COMPAT_swi-wp-bin in its conf/layer.conf file to list the core layer names it is compatible with.
WARNING: Layer swi-wp-bin should set LAYERSERIES_COMPAT_swi-wp-bin in its conf/layer.conf file to list the core layer names it is compatible with.
Loading cache: 100% |#######################################################################################| Time: 0:00:00
Loaded 3087 entries from dependency cache.
Parsing recipes: 100% |#####################################################################################| Time: 0:00:02
Parsing of 2169 .bb files complete (2168 cached, 1 parsed). 3088 targets, 338 skipped, 0 masked, 0 errors.
WARNING: No bb files matched BBFILE_PATTERN_swi-mdm9xxx-bin ‘^/home/mangoh/yocto_mdm9x06_02.32.02.00/meta-swi-extras/meta-swi-mdm9xxx-bin/’
ERROR: Nothing PROVIDES ‘linux-yocto’
linux-yocto was skipped: incompatible with machine swi-mdm9x28-wp (not in COMPATIBLE_MACHINE)
linux-yocto was skipped: incompatible with machine swi-mdm9x28-wp (not in COMPATIBLE_MACHINE)
linux-yocto was skipped: incompatible with machine swi-mdm9x28-wp (not in COMPATIBLE_MACHINE)
@gjames as mentioned above, “Also, in the wiki page the module referenced is wp85 & you are on a wp77”. Thus, please read through the Yocto manuals. The bitbake interface makes no sense to use
unless you read the Yocto manuals. For example, listtasks will show you that the wp77 has no
task that performs configme. I suggest you spend some time on the manuals before forging ahead.
Also, you are doing commands from that wiki page meant for the wp85 target and you are
on the wp77 target - thus, I’m not sure you should be basing your unmodified work on the wp77
from instruction for the wp85. Lastly, I’m unsure of the VM status of things I run native usually.
For serious development, esp. with Yocto build times, VM use maybe problematic.