The LPDDR4 retention code is executed as part of the suspend/resume process.
When resuming, this code writes to a register that doesn't exist on the
i.MX8MN, causing the system to freeze before control is returned to Linux.
Add a patch that introduces a compile-time check for the SoC type to avoid
performing the write operation on the i.MX8MN.
https://jira.digi.com/browse/DEL-6914
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The Cortex-M7 uses the UART4 as debug console, and it is
shared with the Cortex-A53. This commit disables it for the
ConnectCore 8M Nano DVK board to avoid conflicts.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
For the i.MX8M processors, the do_deploy support is provided by
the upstream recipe firmware-imx-8m.
https://jira.digi.com/browse/DEL-6911
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Update file:
- fakeboar_US.bin (f74a835871d9c12f116312ff54927b39)
This file was generated by calibrating 10 CC8X SOMs (version 0x4) and merging
their resulting BDF files into a Golden file. Target powers table is also
updated to improve performance on 2.4GHz band.
Reference calibration file is:
- bdwlan30.bin (8a558fa38dacee7038f04c1b10ec69a5)
located at 'cnss_proc/wlan/fw/target/pcie_dst/qc6174/' from tag r10007.1 on
qca6574au-le-2-2-1_qca_oem repo.
https://jira.digi.com/browse/DEL-6852
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
(cherry picked from commit a332ff445f)
This imx-seco recipe manages now the NXP IMX SECO firmware, it was removed
from the firmware-imx recipe.
https://jira.digi.com/browse/DEL-6823
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Rename board data file loaded on qca6574 wireless chips to 'fakeboar_US.bin'.
A symlink named 'fakeboar.bin' will be created by 'qualcomm.sh' selecting
either this file or the WorlWide variant: 'fakeboar_World.bin'.
- fakeboard_US.bin (e1db4a300b58776f8abd8588beadc09e)
https://jira.digi.com/browse/DEL-6773
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Digi Embedded Yocto 2.6-r2.2
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Update file:
- fakeboar.bin (e1db4a300b58776f8abd8588beadc09e)
This file was generated by calibrating several CC8X SOMs and SBCs and
merging their resulting BDF files into a Golden file.
Reference calibration file is:
- bdwlan30.bin (8a558fa38dacee7038f04c1b10ec69a5)
located at 'cnss_proc/wlan/fw/target/pcie_dst/qc6174/' from tag r10007.1 on
qca6574au-le-2-2-1_qca_oem repo.
https://jira.digi.com/browse/DEL-6736
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Update file:
- fakeboar.bin (3e558869e3943da08899abd881455bc6)
This file was generated by calibrating several CC8X SOMs and merging
their resulting BDF files.
Reference calibration file is:
- bdwlan30.bin (8a558fa38dacee7038f04c1b10ec69a5)
located at 'cnss_proc/wlan/fw/target/pcie_dst/qc6174/' from tag r10007.1 on
qca6574au-le-2-2-1_qca_oem repo.
https://jira.digi.com/browse/DEL-6736
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Latest release r10007.1 updates the following files from qca6574au-le-2-2-1_qca_oem
repo at meta_build/firmware/pcie/:
- qwlan30.bin -> qwlan30.bin (60ac4486fba393294b590f86117f5539)
- utf30.bin -> utf.bin (c15794509d8a8435d4244fea699d99b3)
and the following files from meta_build/firmware/sdio/:
- qwlan30.bin -> qwlan30.bin (4421b30ca259ab73bbfa79df807e0b47)
- utf30.bin -> utf30.bin (b2651762aa1d620349593905efab326b)
Update Bluetooth firmware from qca6574au-le-2-2-1_qca_oem repo at
cnss_proc_1/btfm_proc/bt/wcss/bsp/rom/build/SCAQBAF/Test_Files/Linux/
- rampatch_tlv_3.2.tlv -> rampatch_tlv_3.2.tlv (72d28614afd0abe5846c1758099282e3)
- nvm_tlv_3.2.bin -> nvm_tlv_3.2.bin (3de46ea023570b86cabb9502b92a1fed)
Note: nvm_tlv_3.2.bin based on original md5sum
a97cdfe80e8109cf3574f74cd3c73fc7 but changed byte at
offset 0x36 from 0x82 to 0x02 (IBS).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6725
Remove our .bbappend, which was wrongly making this recipe compatible with the
imx8. Directly port NXP's recipe (v5.4.39), which is newer than the one in
meta-freescale (v5.4.38).
https://jira.digi.com/browse/DEL-6722
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Change the license type from "MIT" to "Proprietary". This change was taken
from the imx-sc-firmware recipe.
https://jira.digi.com/browse/DEL-6722
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Otherwise, users that are behind corporate firewalls might not be able to
obtain the package sources.
https://jira.digi.com/browse/DEL-6663
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The 'soc_type' variable was already set by fastboot to "imx8qxp"
so the U-Boot board code that was setting this to just "8qxp" has
been changed to set it to "imx8qxp".
Update the scripts accordingly.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DUB-901
This commit fixes two issues:
- Comparison clause uses only one equal sign
- Fix soc_type for Dual variants because the supported soc types
for the imx8 processor are: 8qm, 8qxp, and 8dx
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
These images were broken in many ways, including ethernet not working and Linux
not booting. For now, revert back to the build command that was used in
DEY-2.6-r1.
https://jira.digi.com/browse/DEL-6677
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
After the recent changes to generate the bootable artifacts, these are
now formed using the ${MACHINE} variable rather than the string in
${UBOOT_CONFIG} array, so the underscores must be changed with dashes.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The existing loops were iterating through all RAM_CONFIGS, but
they must only iterate over those that match the RAM size on the
platform's UBOOT_CONFIG.
This commit adds a Python class 'boot-artifacts' to get the list of matching
combinations of RAM_CONFIGS and UBOOT_CONFIG so that the iteration
is easier to do than nesting loops inside one another.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
The recipe was creating a variable with the value of another one from
the main recipe, just to refer to the bootable artifact prefix.
We can now use instead the new UBOOT_PREFIX variable.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Similar to the way the u-boot recipe does, create a symlink to the default
bootable artifact.
Since they are overwritten on every loop, this requires that the default
RAM configuration is set the last on the list of RAM_CONFIGS (same
convention than the one used on UBOOT_CONFIGS).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
With the rework to support variants, the machine name (actually the
UBOOT_CONFIG) was removed from the filename. Re-add it using
${MACHINE_NAME} which is more appropriate than the ${UBOOT_CONFIG} which
contains the RAM size (now present in ${ramc}).
While on it, remove one of the two symlinks on DEPLOYDIR. Only one makes
sense.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
Now the U-Boot binaries contain the RAM frequency and bus width, not just
only the RAM size.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
There are several U-Boot binaries, depending on RAM size, at the moment:
- u-boot.bin-ccimx8x_sbc_pro512MB
- u-boot.bin-ccimx8x_sbc_pro1GB
- u-boot.bin-ccimx8x_sbc_pro2GB
and several SCFW files, depending on frequency, size, bus width, at the
moment:
- scfw_tcm.bin-1.2GHz_512B_16bit
- scfw_tcm.bin-1.2GHz_1GB_16bit
- scfw_tcm.bin-1.2GHz_1GB_32bit
- scfw_tcm.bin-1.2GHz_2GB_32bit
From these, we need to combine those that match the RAM size, to produce
bootable images for the different variants.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
Gabriel Valcazar
Arturo Buzarra
Francisco Gil
Gonzalo Ruiz
Hector Palacios
Mike Engel