Uploaded image for project: 'Mender'
  1. Mender
  2. MEN-5051

Proposal to make Mender compatible with the NXP UUU tool

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Environment:
      NXP i.MX8m Variscite DART
    • Days in progress:
      0

      Description

      I Would like to propose allowing Mender to support both CONFIG_ENV_IS_IN_MMC and CONFIG_ENV_IS_NOWHERE at the same time on u-boot SPL builds. 

      The NXP UUU tool, which is loading its initial u-boot image into RAM needs to have CONFIG_ENV_IS_NOWHERE defined to work. When the image that the UUU tool flashes to the eMMC runs it will automatically use the CONFIG_ENV_IS_IN_MMC option and search for the environment on the eMMC.

      It is not clear why the Mender team has chosen to restrict the usage, dual definition of both CONFIG_ENV_IS_IN_MMC and CONFIG_ENV_IS_NOWHERE for its auto configuration option?

      The Mender build with both options enabled has been tested, and appears to work with no adverse effects on the primary Mender functions.

      The following link provides more explanation of the issue and proposed solution:

      https://hub.mender.io/t/spl-not-booting-into-main-u-boot-when-loading-using-nxps-uuu-tool-and-mender-uboot-is-enabled/4042/6

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Ossian Ossian Riday
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Zendesk Support