Known Issues

Table of Contents

• SDK 2.1.0 and 3.0.0 compatibility information
• The touch input may seem to not work
• The rotary encoder may produce 2 events for each detent
• Rotary encoder glitches and jumps intermittently
• Filesystem overlays
• Windows Antivirus interference
• Bluetooth startup delay

SDK 2.1.0 and 3.0.0 compatibility information

Important

Update files, recovery files and flash files are NOT compatible between 2.1.0 and 3.0.0.

In order to use 3.0.0, you must flash your device with a 3.0.0 flash image. After that you can create and use updates and recovery files normally.

Any updates or recovery files created with 2.1.0 will not work on a 3.0.0 image, they must be generated with SDK 3.0.0.

For more info see Upgrading from 2.1.0 to 3.0.0: Important Compatibility Information.

The touch input may seem to not work

If your unit is affected by the touch input issue, please try the steps outlined in Pre-production hardware touch input issues with recent OS images.

The rotary encoder may produce 2 events for each detent

For the rotary encoder issue, please see Pre-production rotary encoder produces two events for each detent for a fix.

If you encounter any other issues, please contact support.

Rotary encoder glitches and jumps intermittently

Some D7 v5 boards have a known issue with the rotary encoder glitching or producing multiple jumps in the software on a single step turn. This is a known hardware issue that has been fixed on D7 v6 boards and upwards. Refer to Board Version to identify your board version.

Note: This is a hardware issue and the fixes described in Pre-production rotary encoder produces two events for each detent will not work.

Filesystem overlays

The system image makes use of filesystem overlays for system configuration, primarily /etc directory. see Overlays for details.

In certain scenarios — particularly when mixing release and development updates — there is a risk of inadvertently enabling root access on release images. The following sequence of steps can lead to this situation:

• The device is running a release image.
• A developer applies a development image update.
• While running the development image, credential files are modified (e.g., setting a user password, adding a new user, etc.).
• A release image update is then applied.

After these steps, it will be possible to log in as the root user on a release image. This scenario is expected to occur only during the development cycle on development devices. Production devices must never run development images to prevent this risk.

Important

Never use development images in production devices.

Windows Antivirus interference

On Windows, some antivirus programs might falsely flag up and block the tools packaged in the SDK and applications built using the compilers shipped in the SDK. If you encounter silent failures from SDK tools or from applications you have compiled, it may help to temporarily disable the antivirus or to add the SDK folder to an exclusion list.

Bluetooth startup delay

Currently the Bluetooth module present on the D7 takes approximately 60 seconds to initialise. If you are writing an application that requires Bluetooth, please take that into consideration.