Instead of having one kernel recipe with two hashes, it makes more sense
and is easier to maintain two recipes with the same name but different
versions. The shared part is in an include file.
Each machine then chooses which version it wants to use with
PREFERRED_VERSION variable.
BugzID: 79987
It happens that a soft reset is failing and blocking the chip in a state
where it always times out. The only wait to get out of this is to hard
reset the bluetooth chip.
BugzID: 77171
Detecting if the mac address must be inverted means doing two resets of
the chip in a short period when the mac must be inverted.
These two resets is sometimes letting the BT chip in a state where it
does not answer for more than a minute.
Also fixes getopts string: options -w and -b don't have arguments.
BugzID: 77171
settin mac address of bt and wlan is now triggered in two separated
services.
BugzID: 77171
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
added several enhancements to the mac-address-set script:
- splittet wlan and bt address setting (use -w / -b options)
- fixed upper and lower case problem with vcu1 addresses
- fixed hexadecimal support with vcu2 addresses
- added testify support (incl. log_test function)
BugzID: 77171
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
adding a unit test script which uses testify framework to test the
mac-address-set script for vuc1 and vcu2.
BugzID: 77171
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
if a device is never getting ready on startup sequence, the wait_on()
function runs forever. with this patch it aborts after 10 seconds.
BugzID: 77171
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
If NetworkManager starts before, it may change the mac address for
scanning and store the chip mac address. When finaly using a static mac
address (for an established connection or AP) it will restore the chip
address instead of our address.
BugzID: 77171
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
After an overall refactoring this script now does:
* Wait on devices being ready before changing the address
* Handle errors when setting wlan or bluetooth mac address
* Handle different MAC address schemes
* Handle different behaviors when setting wlan mac:
On HW21, the address must be set while the interface is down, but on
HW23 it must be set while the interface is up and if it is down, no
error is thrown, so the modified address is checked.
* Handle different behaviors while setting BT mac:
On HW21, the address must be given with the bytes in reverse order.
We therefore first try with the right order and check the address and
retry with the reversed address if it failed.
BugzID: 77171
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
hw23: Force wpa-supplicant and hostapd versions
meta-netmodule-wlan provides modified versions of these tools, but they
seem to not work properly on HW23. Since this HW is anyway not supported
in meta-netmodule-wlan, we force the usage of latest stable version.
BugzID: 77173
Co-authored-by: Patrick Zysset <patrick.zysset@netmodule.com>
Reviewed-on: https://git.netmodule.intranet/yoctoproject/meta-netmodule-bsp/pulls/111
Co-Authored-By: Alexandre Bard <alexandre.bard@netmodule.com>
Co-Committed-By: Alexandre Bard <alexandre.bard@netmodule.com>
those files reside now in the repository itself, thus the recipe
needed to be adapted
BugzID: 75350
Signed-off-by: Marc Mattmueller <marc.mattmueller@netmodule.com>
With this change we are building the same kernel config for all
hardwares belonging to the same platform. The configs only differ from
one or two drivers which are enabled or not and they are anyway not
loaded as long as the devicetree is not matching.
But having only one config for several hardwares is reducing maintenance
(like enabling or disabling kernel security features) and also reducing
build time when building for different machines.
BugzID: 75223
The two "ifs" are covering cases where the fitImage is not used and we
don't support this case.
And as the Module.symvers comment says, this has been fixed upstream in
kernel.bbclass.
BugzID: 75220
Our u-boot-nm.inc was just a copy of an outdated u-boot.inc.
I now changed the u-boot-nm.inc file to be a common configuration file
for our u-boot recipes.
BugzID: 75187
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
ATM the system state framework only works properly if we have the da9063
with working ignition.
BugzID: 74987
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
These values are out of date with the real kernel versions and may be
misleading. Since we have only one version of the kernel, we can remove
them and "git" will be used as default value.
BugzID: 74959
These symlinks were required for compatibility with NRSW u-boot.
Since we are now using fitimage, the name of the devicetree is not
relevant since it is directly part of the fitimage.
BugzID: 74958
Instead of rewriting the full fitimage_assemble, we can just append to
the part generating the kernel entry, therefore reducing the duplicated
code.
BugzID: 74530
With this approach, we just need to change a machine.conf file to add
advanced-gnss to machine_feature in machine.conf to enable gnss-mgr,
force gpsd to start with 115200 bitrate and to disable gpsd service
because it will be started by gnss-mgr.
BugzID: 74458
And also reduce the number of created artifacts and simplify do_deploy.
The rm commands are not required. bitbake is smart enough to remove the
old deployed artifacts of a recipe.
BugzID: 74357
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
This will bring pciutils automatically to all machines:
- all armada machines
- all am33x machines
- imx8 hw23
BugzID: 73589
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
and remove the machine feature on hw26 since it is derived from hw21
machine config.
BugzID: 73593
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>
In order to pull in some chip specific firmware / drivers or tool there
are also one specific wifi feature per wifi chip:
- ath-wifi for atheros chips
- ti-wifi for TI chips
- ublox-wifi for u-blox chips
BugzID: 75593
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>