This commit adds the different OS version that have been used
to build DEY.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-4984
Tweaked to maintain some recipes' revisions to AUTOREV instead of the
fixed SHA1s from the tag.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* Device Cloud has been renamed to Remote Manager.
* Removed "Data points" known issue (fixed in CloudConnector)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This was fixed in U-Boot:
4aad9fd041f11de66bf5eb0137c49dbd450c4388
Also move TrustFence (TM) limitation which affect all platforms to a common section.
https://jira.digi.com/browse/DEL-3134
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
When encryption is enabled, the signed U-Boot image will be used for the uSD.
This allows the uSD image to boot the device and recover it from the U-Boot
console, which is its main purpose. Nevertheless, the uSD image will not be
able to boot Linux.
https://jira.digi.com/browse/DEL-2877
This reverts commit 2e13e194d9.
U-Boot version dub-2015.04-r4.5 may report running on
Starter Board version 1 even when your Starter Board is
version 2. In that case Ethernet does not work in U-Boot.
More recent versions of U-Boot fix this issue.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This reverts commit b8f50680e5.
The support to read and write to an encrypted environment has been added, so
there is no need to exclude the u-boot-fw-utils anymore.
https://jira.digi.com/browse/DEL-2836
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
* Add known issues for CC6UL.
* Refer to online documentation for interface and feature list.
* Add uSD encrypted image boot limitation.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
* Add trademark to TrustFence (TM) for consistency.
* Remove CC6UL non-wireless variant from supported products
* Added a note to check the online documentation for an updated known
issues and limitations list.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
enabled
There is currently no support on fw_printenv/fw_setenv to access an
encrypted environment.
This commit removes the package if U-Boot environment encryption is
enabled to avoid environment corruption on access.
It also documents the issue as a known issue.
https://jira.digi.com/browse/DEL-2625
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
By default, on closed devices you cannot revoke any key. To do so, it is
required to compile a U-Boot which instructs the HAB not to set the sticky
bit which write protects that field in the OCOTP controller.
This patch introduces a Yocto macro which allows to configure U-Boot in
that way.
In the ConnectCore 6, the value of this settings is ignored, because HAB never
sets the sticky bit which write protects that field.
https://jira.digi.com/browse/DUB-665
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
Isaac Hermida
Francisco Gil
Tatiana Leon
Mike Engel
Alex Gonzalez
Javier Viguera
Arturo Buzarra
Salvador Penalva
Diaz de Grenu, Jose
Hector Palacios