Search by Tags

Toradex Easy Installer Issue Tracker

 

The following table contains known issues, scheduled bug fixes, and feature improvements for the Toradex Easy Installer. The tickets are split in two major states:

  • Submitted (open): new features and bug fixes for Toradex Easy Installer versions that have not yet been released. They may be scheduled for a specific release version; not planned; or in our backlog. All of them have one of the following states:
    • Known Issue: a bug or unexpected behavior that has been reported and pending a fix. Once fixed, the status will transition to Fixed.
    • Feature Request: a new feature that may be added to a future release. Once released, the status will transition to New Feature.
  • Released (closed): new features and bug fixes for BSP versions that have already been released. All of them have one of the following states:
    • Fixed: a bug that has been fixed and released.
    • New Feature: something that didn't exist before and was added to a new release.

Any schedules are not guaranteed but reflect the current planning. The planning could be shifted due to priority changes.
Issues that are scheduled for a specific version will be integrated into the mentioned version of the BSP.

We will update this table continuously in order to always provide the latest state of our development plan.

Clear Filter
Issue #StatusSubjectModuleSubsystemSeveritySubmitted for Mainline

Not Planned
TEI-282Known IssueOnly 256MB of RAM Available When Installing BSP V2.6 Directly From Toradex Easy Installer U-Boot Due to Missing patch_ddr_size CommandColibri iMX6BootloaderLowNo

Description: During installation of BSP V2.6 directly from the Toradex Easy Installer U-Boot the following error message is shown but otherwise ignored by the installation procedure: Unknown command 'patch_ddr_size' - try 'help' As a consequence only 256MB of RAM will be available.

Workaround: Just manually execute the patch_ddr_size command once U-Boot from BSP V2.6 is installed. For existing production programming scenarios we do recommend to first separately update just U-Boot only (e.g. doing run setupdate; run update_uboot; reset) in order to make sure any further production programming scripting will proceed as before.