With the switch to using Bash as command line interpreter, the default
/etc/inputrc configuration file for readline doesn't allow the use of
some keys which are common.
This commit enables them to not change the user experience with previous
DEY versions.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5623
The suspend script has conflicts with the suspend from bash, then
we decided to rename our custom suspend script to standby and create
a symlink called suspend to maintain backward compatibility.
https://jira.digi.com/browse/DEL-5622
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Sync defconfig to enable command 'chvt' because the xserver-nodm
init script requires this command in the stop process to swicth
the foreground virtual terminal after stopping the xserver.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Sync defconfig to enable command 'command' because /etc/profile
of base-files requires this command to be available. If it is not
available the following message is output during login on a image
using busybox.
-sh: command: not found
(From OE-Core rev: e41c90b852167bbcb434da57b84280e855acae33)
https://jira.digi.com/browse/DEL-5632
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This saves ~4MB of space and is not required for device detection.
https://jira.digi.com/browse/DEL-5613
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This tool was only needed for old kernels, newer kernels use the hardware
random number generator themselves.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This variable and all its references were removed in Yocto 2.4
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This class no longer exists, it has been merged with images_types.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
NetworkManager was experiencing an unexpected behavior managing
the network interfaces on a supend/resume process, then to avoid
this undesired behavior the suspend script will stop and restart
the NetworkManager service.
https://jira.digi.com/browse/DEL-5351
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
NetworkManager will be restarted on the suspend script so this workaround is not needed
This reverts commit b3ae030fce.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
With these changes we tell NM to not manage the wireless interfaces before
unloading the wireless module. This was causing some unexpected behavior that
crashed NetworkManager.
Signed-off-by: Sebastian Pastor <sebastian.pastor@digi.com>
https://jira.digi.com/browse/DEL-5351https://jira.digi.com/browse/DEL-4571
virtwlans script creates an additional interface on startup for QCA6564 chip.
The created interface purpose is for ap mode, so specify its type on creation.
https://jira.digi.com/browse/DEL-5290
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This commit modifies different recipes to support the new platform
ccimx6qpsbc and adapt it to maintain the support to ccimx6sbc.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Turns out that the busybox' fdisk applet is also able to parse the GPT
partition tables. This saves around 0.5 MiB of space.
https://jira.digi.com/browse/DEL-4565
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
wlan1 is the interface used for SoftAP, so use that one instead. This also
matches with the 'Network bridging' chapter of the documentation.
https://jira.digi.com/browse/DEL-4823
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
The bridge example uses the wireless interface and it assumes that it is
initialized, so it must be placed after it.
https://jira.digi.com/browse/DEL-4823
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
The supplicant support for a bridge was not being managed,
then the bridge was failing when the softap was configured
with an encryption. With this change we launch a supplicant
instance with the bridge support after checking that the
/etc/network/interfaces contains the required parameters.
https://jira.digi.com/browse/DEL-4454
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
We need to pass different log levels depending on the message, so they
appear in the console, so generalize the 'log' function.
https://jira.digi.com/browse/DEL-4682
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Busybox's init enabled at build time collide with 'sysvinit' package.
This does not seem a problem when using RPM package manager, but using
IPK instead, the build is broken at image creation time:
Collected errors:
* check_data_file_clashes: Package sysvinit wants to install file <...>/rcS
But that file is already provided by package * busybox
https://jira.digi.com/browse/DEL-4573
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
No applet has been enabled or disabled, just the defconfig file has been
refreshed for the current busybox version 1.24.x
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
As we are using kernel's DEVTMPFS, using udev-cache on top of it does
not add much advantage. Disabling it has the extra advantage of avoiding
writing the udev-cache tarball under '/etc' (which probably won't work
on a read-only system).
https://jira.digi.com/browse/DEL-3780
Signed-off-by: Javier Viguera <javier.viguera@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>
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>
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>
The readlink command on a real file was expanding to nothing and then
the '/etc/resolv.conf' file was not being updated with the nameservers.
With this change we only run the 'readlink' link command after checking
that the file is actually a symbolic link.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Added a post-installation script to disable the wireless interfaces on
module variants without wireless support.
This fixes following messages on boot:
wlan: driver load failure
modprobe: can't load module wlan (extra/wlan.ko): No such device
...
https://jira.digi.com/browse/DEL-3781
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This 'sed' command was used in the past, when DHCP or MANUAL was
configured in the '/etc/network/interfaces' (for cellular). This is no
longer true as we always configure the interface with a custom (manual)
script.
This was breaking the rest of interfaces when configured to use 'dhcp':
iface eth0 inet manual
umanualc_opts -S -b >/dev/null &
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The recovery init checks if the configured update package exists and it is valid
before setting a new key and/or formatting the rootfs partition.
This change avoids getting non-booting devices after performing a firmware
update with a non-existing or invalid update package.
https://jira.digi.com/browse/DEL-3959
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
- The Bluetooth daemon was always executed before setting up the
hardware, generating several problems specifically in the CCIMX6SBC.
This was causing the Bluetooth driver to override the Bluetooth name
and alias, as well as avoiding any host function on Bluetooth profiles.
Only pairing and ping was working, as well as client profile sides.
- This change also fixes some issues in the CCIMX6UL platforms with the
Bluetooth daemon failing to perform several bluetoothctl operations.
https://jira.digi.com/browse/DEL-4000https://jira.digi.com/browse/DEL-4015
Signed-off-by: David Escalona <david.escalona@digi.com>
If the volume is not found, the partition cannot be wiped since it is attached.
Remove 'update' UBI device in:
* mdev automount script if volume is not found
* recovery init script before formatting 'update' partition
https://jira.digi.com/browse/DEL-3962
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
This commit adds mdev support into the recovery ramdisk to
mount/unmount storage devices for the firmware up tool.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3692
udhcpc's '-n' option means 'Exit if lease is not obtained'.
We want to keep udhcp client alive if lease is not obtained, so when it is
possible, an IP is assigned.
https://jira.digi.com/browse/DEL-3821
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
udhcpc options added to 'network/interfaces':
* '-S' to log to syslog too.
* Redirect the output to '/dev/null' not to show messages of the tool running
in background (for example when executing 'ifup').
* '&' to send the udhcp client to background.
https://jira.digi.com/browse/DEL-3821
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
- Instead of trying to generate the TrustFence keys in this recipe
when they are not present, depend on the 'virtual/kernel' to
ensure they are already generated. This solves a concurrency problem
when two recipes try to generate TrustFence keys at the same time.
https://jira.digi.com/browse/DEL-3913
Signed-off-by: David Escalona <david.escalona@digi.com>
Allowing to boot a non-encrypted rootfs when encryption is enable is a security
hole: if an attacker can somehow write (offline) to the media, he could flash a
custom unencrypted rootfs and break into the system.
If the system is configured to use encryption, only encrypted rootfs will boot.
Trying to boot a non-encrypted rootfs will fail and power off the device.
https://jira.digi.com/browse/DEL-3829
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
The recovery ramdisk already contains functionality for encrypted rootfs
installation. The goal is to centralize all this functionality in the recovery
ramdisk.
https://jira.digi.com/browse/DEL-3829
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
For CC6UL, when setting a new key, an "enc" flag must be added to the rootfs in
the "mtdparts" U-Boot variable.
After that a reboot is needed, so the recovery command must be modified to
remove the encryption key and proceed with the rest of commands in the next
boot.
When updating the firmware, a format of the rootfs partition is always
performed, independently if a new encryption key has just been configured.
In case only the encryption key is being configured, we also need to reboot to
format the rootfs properly.
https://jira.digi.com/browse/DEL-3685
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
This commit verifies that the wlan1 interface is not already created
and will skip creating the virtual interface if it already exist.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3917
This commit changes the concurrent mode script to enable always the
AP interface through the wireless device but will warn the use
if the virtual MAC addresses used are the default once.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3900
The flash_eraseall busybox utility is not used in the ccimx6 and ccimx6ul
platforms. Its corresponding patch (and the library it depends on) can be
removed from the busybox recipe.
https://jira.digi.com/browse/DEL-1320
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit adds the wireless concurrent mode as a default
configuration to the CC6UL machine.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3818
- While trying to update the system using signed swupdate packages, the
swupdate binary requires a new parameter (-k) to specify the location
of the public key that will be used to verify the update package. At
the moment there is no way to check if a package is signed or not, so
we asume that the existence of the public key in the recovery initramfs
is enough to determine that we want to update the system using signed
packages.
https://jira.digi.com/browse/DEL-3775
Signed-off-by: David Escalona <david.escalona@digi.com>
- The swupdate binary included in the recovery partition when the
images to build are trustfence enabled performs a verification
of the swupdate package. For this verification to suceed, it is
mandatory to provide to the swupdate binary the public key that
will be used to verify the swupdate package. This public key must be
included in the recovery initramfs only when 'TRUSTFENCE_SIGN=1'.
https://jira.digi.com/browse/DEL-3772
Signed-off-by: David Escalona <david.escalona@digi.com>
This recipe is expected to create just an initramfs image, so force the
image FSTYPE with a python anonymous function, so there is no way to
change/append/override it from any other configuration file.
This prevents build failures due to circular dependences if for example
you add:
IMAGE_FSTYPES_append = " recovery.vfat"
to your project's local.conf.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The LICENSE is added through the packagegroup bbclass and the checksums
were outdated making the build fail with:
The LIC_FILES_CHKSUM does not match for poky/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58
https://jira.digi.com/browse/DEL-3451
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add critical section in suspend script to avoid that more than
one instance can be executed concurrently. This happens, for
instance, when the power button key is pressed while the system
is resuming, causing issues on the wifi interface.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3694
According to NXP i.MX Linux Reference Manual:
The full CAAM function is exclusive with the Mega/Fast mix off feature
in DSM. If CAAM is enabled, the Mega/Fast mix off feature needs to be
disabled, and the user should
"echo enabled > /sys/bus/platform/devices/2100000.aips-bus/2100000.caam/2101000.jr0/power/wakeup"
after the kernel boots up, and then Mega/Fast mix will keep the power
on in DSM.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3636
Add critical section in suspend script to avoid that more than
one instance can be executed concurrently. This happens, for
instance, when the power button key is pressed while the system
is resumming, causing issues on the wifi interface.
https://jira.digi.com/browse/DEL-3431
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
We have seen corner cases (e.g. when the partition to format has already
some corrupted UBI metadata) where ubiformat stops and ask the user for
confirmation to do the format. We cannot have such interactivity in the
recovery ramdisk so use the '-y' argument to assume yes for all
questions.
Also use the '-q' (quiet) parameter instead of the '/dev/null'
redirections to remove command's output.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit adds a wpa supplicant P2P configuration file and configures
the p2p0 interface automatically at pre-up.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
For the moment the cloudconnector is provided only as static library, so
the recipe can be simplified.
https://jira.digi.com/browse/DEL-3523
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Instead of using a hardcoded path to the SWU update package, just get
the filename and search the file in the different mounted partitions
(giving priority to the internal 'update' partition over other external
media).
https://jira.digi.com/browse/DEL-3466
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
For block devices we can get the filesystem in the partition using the
'blkid' command.
This cleans up some warnings on mounting:
EXT4-fs (sda2): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (sda2): couldn't mount as ext2 due to feature incompatibilities
EXT4-fs (mmcblk0p4): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (mmcblk0p4): couldn't mount as ext2 due to feature incompatibilities
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
"i" variable in the nested loop is expanded to the absolute path
of the device, so prepending it with the ${device} results in
"/dev/sda/dev/sda1" for a 'sda1' partition.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
recovery-utils allows to configure recovery commands and reboot into
recovery mode.
Internal recovery-utils.git SHA1: 5555d4c736e3
https://jira.digi.com/browse/DEL-3358
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is a clone from the original psplash recipe init script
but with the added fix:
@@ -25,5 +25,7 @@
read rotation < /etc/rotation
fi
-/usr/bin/psplash --angle $rotation &
+if [ -c "${FBDEV:-/dev/fb0}" ]; then
+ /usr/bin/psplash --angle $rotation &
+fi
which avoids running the application when there is no framebuffer
in the system. This prevents the following error message during
boot:
Error opening /dev/fb0: No such file or directory
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2747
- Include psplash package in the recovery initramfs recipe.
- Start psplash in the recovery init.
- Add new methods to communicate with psplash from the init script.
- Show psplash progress information from the init script.
- Start progress binary to update psplash during a firmware update.
https://jira.digi.com/browse/DEL-3356
Signed-off-by: David Escalona <david.escalona@digi.com>
- Added a 5 seconds delay before mounting external disks so they have
time to be recognized in the system.
- Check if UBI volume is mounted before formatting it.
- Check if eMMC block device exists before formatting it.
Signed-off-by: David Escalona <david.escalona@digi.com>
- This recipe generates the recovery ramdisk image with the contents of the
recovery ramdisk tree (recovery-initramfs) and other packages.
Signed-off-by: David Escalona <david.escalona@digi.com>
Bringing the Bluetooth interface down and up during suspend
is not needed and it even showed problems on the Starter Board
where the Bluetooth interface does not come up again after
having been brought down in suspend.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3416https://jira.digi.com/browse/DEL-3081
Separately add 'dey-gstreamer' to ccimx6ulsbc platform.
This platform does not have 'accel-video' but we want gstreamer
for using it with video/camera.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2358
Remove preventive delays during the removal of Bluetooth and Wireless
interfaces. Tests revealed they are not needed.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The loading of the wireless module without proper arguments does nothing.
Besides, if the interface was down before going to suspend, there is no
need for the wireless module to be loaded.
The wireless module will be loaded nevertheless (with proper arguments)
when the interface is brought up.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3241
The suspend script was unloading the wireless module driver *only* if the
interface 'wlan0' was previously up. If the interface is down the module
does not unload and the system fails to suspend.
This patch removes the module always if it appears in the list of loaded
modules.
While on it, move the unloading of wireless after the unloading of
Bluetooth, to be in line with the reversed order in which they are loaded
on the resume_interfaces() call.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3241
Use the static binary from the tarball, which should be common across
different platforms and operating systems.
https://jira.digi.com/browse/DEL-3261
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The u-boot header is required for U-Boot to boot the image in secure boot.
The cpio.gz.u-boot.tf image gets signed and encrpyted if required.
https://jira.digi.com/browse/DEL-3242
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
Hector Palacios
Arturo Buzarra
Isaac Hermida
Jose Diaz de Grenu
Sebastian Pastor
Mike Engel
Tatiana Leon
Javier Viguera
David Escalona
Gabriel Valcazar
Pedro Perez de Heredia
Alex Gonzalez