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-276Feature RequestProvide a mechanism to write at a specific offset from the end of the eMMC partitionColibri iMX7, Apalis iMX6, Colibri iMX6, Apalis TK1, Apalis T30, Apalis iMX8FlashLowNo

Description: Provide a mechanism for raw files which allows to write at a specific offset from the end of the partition. This is useful to handle WinCE Config Block which is located at the end of the eMMC boot partition. Because eMMC boot partition sizes can vary the offset from the beginning depends on the exact product and product version.

Workaround: Use the wrapup.sh script to dd the configblock (or any other file) with a calculated offset from the end of the partition. For example: ... IMAGE_FOLDER=$4 ... OFFSET=$(($(cat /sys/block/mmcblk0boot0/size)-17)) echo "Writing configblock.bin to offset ${OFFSET}" dd if=${IMAGE_FOLDER}/configblock.bin of=/dev/mmcblk0boot0 count=16 seek=$OFFSET This also makes sure that the static config block does not get accidentally overwritten in case configblock.bin is too long. Note that this only works for images read from a local media, since only then configblock.bin is simply available in $IMAGE_FOLDER.