When bringing down the wireless interface used for hostapd, the messages
overlap:
# ifdown wlan1
Stopping HOSTAP Daemon: stopped /usr/sbin/hostapd (pid 569)
hostapd.
Adding the 'quiet' option to start-stop-daemon command fixes the
cosmetic issue.
# ifdown wlan1
Stopping HOSTAP Daemon: hostapd.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is required to be able to use the whole RootFS partition which is
512 MiB in the 0x04 CC6UL SOM variant.
The old value only allowed to manage partitions of up to 256 MiB, this new
value allows for up to 1 GiB (assuming 128 KiB erase block size).
https://jira.digi.com/browse/DEL-4567
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
As the platform data is only separated by spaces, the data is assigned
to the incorrect variable:
ccardimx28js variants: -
ccardimx28js targets: e w wb web web1 dey-image-qt
After this commit:
ccardimx28js variants: - e w wb web web1
ccardimx28js targets: dey-image-qt
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
"glibc-gconv" packages are GLIBC library specific, so add the proper
override to fix the build of the package using other C libraries (e.g.
MUSL).
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
If the IOExpander is not programmed but the kernel is running its driver,
the following messages will appear when running sysinfo:
cat: can't open '/sys/devices/platform/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-006e/hw_version': No such file or directory
cat: can't open '/sys/devices/platform/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-006e/fw_version': No such file or directory
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
Now the suspend script brings down all the wireless interfaces that are
managed by ifupdown command (in the '/etc/network/interfaces' file) and
then unloads the wireless driver.
On resume the script triggers an event so udev reloads the wireless
driver and then brings up the interfaces that were brought down on
suspend.
https://jira.digi.com/browse/DEL-4288
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
At the point this script is run (from udev) the system log is not yet
available, so use the kernel log buffer instead.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use the same udev script that loads the qualcomm wireless module to
create the 'wlan1' virtual interface.
https://jira.digi.com/browse/DEL-4453
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The cellular interface is now managed by NetworkManager, so there is no
need for this custom script.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Udev comes with a bunch of generic rules for the hardware. One of them:
/lib/udev/rules.d/80-drivers.rules
is able to load the qualcomm wireless module.
At the same time our new rule is needed, so it prepares the firmware
before the module is loaded.
Both rules running collide with following error message:
udevd[181]: '/etc/udev/scripts/qualcomm.sh' [184] terminated by signal 1 (Hangup)
So to fix this, we rename the specific rule so it's parsed later, and
then we use the hard assignation '=' instead of '+=' to override the
values that come from the previous parsed rule.
Also clean-up a bit the 'qualcomm.sh' script and the modprobe file,
given that now we know the standard drivers rule won't run for this
interface.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit removes the interfaces that are managed by Networkmanager
from the /etc/network/interfaces entry.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
NetworkManager is not able to detect and manage the wireless interface
until is actually created, so let udev load the kernel module and create
the interface on boot.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
So the package can be compiled in a non-X11 graphical system.
https://jira.digi.com/browse/DEL-4289
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* Disabled: dnsmasq and netconfig
* Enabled: cellular related options and connectivity check
https://jira.digi.com/browse/DEL-4289
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The new fw-4.bin (v3.4.0.236) with md5sum e2fc33daba2c35fe2c4f62492a44f8b6
was used to pass RED (Radio Equipment Directive) certification on the CC6
module.
https://jira.digi.com/browse/DEL-4512
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This script allows to create certificates (Root CA and Greengrass Core
device) and also register a GG Core device Thing.
It's expected to be used before building images with Greengrass core, so
the certificates and the proper configuration can be done in the
firmware.
https://jira.digi.com/browse/DEL-4274
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This will allow to create user helper scripts that are available (in the
PATH) when building DEY projects.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
If values are provided in the local.conf, the package will have the
'config.json' file preconfigured.
https://jira.digi.com/browse/DEL-4274
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Rename the class so it's not specific to the C version of the AWS IoT
Device SDK, and can be used for anything related with AWS IOT (for
example Greengrass).
https://jira.digi.com/browse/DEL-4274
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This avoids the following errors:
ERROR: dey-examples-opengles-1.0-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary
and when cleaning:
ERROR: dey-examples-opengles-1.0-r0 do_configure: oe_runmake failed
| make: *** No rule to make target 'clean'. Stop.
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
This recipe allows to generate the swu update package to be used with SWUpdate.
The package can be generated using:
bitbake dey-image-aws-swu
https://jira.digi.com/browse/DEL-4304
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
In the recovery images we are using a custom init so we are not executing
any post-installation that is required for a correct rootfs setup, so call
all the post installation scripts from our custom init.
The package installation could be ipk, rpm or deb, so call to the
*postint folder.
Given that the recovery rootfs is a ramdisk, there is no need to remove the
post installation scripts.
https://jira.digi.com/browse/DEL-4430
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Javier Viguera
Diaz de Grenu, Jose
Arturo Buzarra
Alex Gonzalez
Mike Engel
Sebastian Pastor
Tatiana Leon
Isaac Hermida