MantisBT - Issues

0007319: [FSIMX6*] Check if we can implement the check_fb_name feature again

Thu, 16 Jul 2026 15:22:52 +0000

The check_fb implementation has been removed from the upstream kernel.
We used this framework to be able to drive multiple display backlights
independently, mainly for i.MX6.
See commit 668e3068a0d5eb3813b8f1dfd2b87da5932d8840

For now we just remove this feature, and test if we have to reimplement
it in later releases

Git commit:
ecf1f351b85243a54623101d0bd4dd13d9b59b03

0007318: [FSIMX6SX] Test auxiliary_core driver

Thu, 16 Jul 2026 15:06:20 +0000

The auxiliary_core has been updated to build again, but not tested yet.

Git commit: f09e89bd4bfcf09a12f19b2d56e024654f0f36bd

0007217: Add latest Windows 11 IoT Updates up to KB5083769 (April 14, 2026)

Thu, 16 Jul 2026 10:48:23 +0000

Search for update delivers:

Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.449.204.0) - Current Channel (Broad)
2026-04 Security Update (KB5083769) (26100.8246)
2026-04 .NET Framework Security Update (KB5082420)
Update for Windows Security platform - KB5007651 (Version 10.0.29554.1001)

Download and install all Updates.

0007315: imx93: uart receive timeout

Thu, 16 Jul 2026 10:09:02 +0000

If the received UART message is shorter than the configured IMX_LPUART_WATER_RXWATER_OFF threshold of 40 bytes, the receive interrupt is not triggered and the RX operation times out. Therefore, the RX watermark must be reduced.

0007207: Add CAN-MU Bridge KMDF driver

Thu, 16 Jul 2026 10:00:39 +0000

Add a KMDF driver for Windows IoT to enable communication with the M33 core (running FreeRTOS) via the i.MX93 CAN-MU bridge (A55 ? M33 using MU1 and shared memory).

Architecture:
User-space application
| DeviceIoControl
v
KMDF driver
|
v
Message Unit (MU1) + shared memory
|
v
M33 core (FreeRTOS, CAN bridge)

0007314: PCOM93: Add additional I/O pins and SPI support to Rhproxy

Thu, 16 Jul 2026 09:55:17 +0000

Add additional I/O pins and SPI support to Rhproxy fpr Picocom93

0007208: Add support for CAN-MU Bridge

Thu, 16 Jul 2026 09:50:18 +0000

Both cores must access the same memory region, so the memory mapping needs to be adjusted in the UEFI.
Additionally, a new DSDT ACPI table must be created in the UEFI for the new device “CAN-MU Bridge.”

0007242: dynamic boot logo

Thu, 16 Jul 2026 09:48:33 +0000

Currently, using a custom boot logo requires building a dedicated UEFI image. This means that every individual customer would need their own custom UEFI build.

This should be avoided. To achieve this, the U-Boot environment should store the eMMC location (block number) and the size of the logo in two variables: logoblock and logosize.

These values are then passed to the UEFI through the existing fs_boardinfo mechanism. The UEFI can then read the logo from the eMMC inside the LogoDxe driver and display it instead of the default F&S logo.

If no logo is found, or if the .bmp logo file is invalid (for example, it must use 24 bpp), the system shall always fall back to the default F&S logo.

0007209: imx93: Add support pca9634 (7/10" FS Display)

Thu, 16 Jul 2026 09:46:03 +0000

On the new ADP-LVDS1/LVDS2 hardware revision 1.20, all LED outputs of the PCA9634 must be configured as open-drain. This configuration is already implemented in the display driver for the 8MP platform, but now also needs to be applied to the i.MX93.

0007313: PCOM93 wrong PCB Revision

Thu, 16 Jul 2026 09:42:21 +0000

The BOT side of the PCOM93 is labeled as Rev1.10 and 1.00 (see picture)

0007232: Bootselect does not work correctly

Wed, 15 Jul 2026 12:25:37 +0000

Observation:
Board does not enter serial download mode when holding bootselect button continuously.

Issue:
U8 LVC1G240 is powered by fixed 1,8V instead of V_PTA_E (3,3V/1,8V)

Solution:
Using V_PTA_E voltage seems not to be the solution.
The device is now recognized in the Device Manager as faulty. Previously, it was not detected at all.

0007312: Insufficient pull-down voltage on COL0,2,4,6

Wed, 15 Jul 2026 11:21:14 +0000

The Push-Pull level shifter U9 has an internal output resistance of approximately 4 kOhm. Combined with the external 4.7 kOhm pull-up resistors, this forms a voltage divider that prevents the affected signals from being pulled down sufficiently. The low level only reaches approximately 1.6 V.

0007311: Update fsimx6ul to Yocto 5.0

Tue, 14 Jul 2026 13:45:31 +0000

Update layer to support fsimx6ul boards

0007309: Change Wifi to MAYA-W Series

Fri, 10 Jul 2026 07:32:44 +0000

Change from AzureWave to ublox MAYA W Series.
W2, W3, W4 and W5 should work

0006477: [FSIMX6UL] Touch calibration for TSC is not applied correctly

Wed, 08 Jul 2026 09:50:43 +0000

The udev rule for the touch calibration is not applied correctly, because the driver name has changed.
Also the calibration values seem to be inverted with newer diplays so this has to be reevaluated

0007308: Make changes to silex recipes and patch handling

Wed, 08 Jul 2026 09:49:29 +0000

- Fetch FW with wget, not from file
- Path kernel from buildroot, without silex branch

0007307: Increase Buildroot patch level and fix merge errors

Wed, 08 Jul 2026 09:46:45 +0000

- Increase to buildroot 2025.02.15
- Fix merge errors
- Fix Westen verison detection

0007306: Do changes for fsimx6ul Buildroot release

Wed, 08 Jul 2026 09:43:25 +0000

- Improve defconfig
- Fix gstreamer recipes

0007305: Fix lonthium driver definitions for picocoremx6ul100

Wed, 08 Jul 2026 09:38:12 +0000

In the common fsimx6 defconfig, the lonthium driver was not activated,
also the F&S version of the driver does not work for 6ul on the current
revision. Since the mainline driver works use this one for now.

0007304: Fix fsimx6ul clock definitions

Wed, 08 Jul 2026 09:35:28 +0000

In commit 28c6ef0739ca9a1cbbcd41c4222075ff28440365 we added better clock
behaviour regarding the ethernet clock. NXP fixed the problem themselves by
now. This caused broken code that does not boot anymore.

Fix this by removing our code regarding this change.

0007303: Fix reassignment of WLAN configs

Wed, 08 Jul 2026 09:33:47 +0000

There where two configs that were reassigned causing warning, fix these.

0007302: Fix gpio name decleration for picocoremx6ul

Wed, 08 Jul 2026 09:31:52 +0000

The nodes where in the wrong location causing the dtb not beeing
buildable.

Fix fsimx6ul devicetrees after merges und location change

Past changes of the i.MX6UL devicetrees have not been done correctly.
There have been three main problems:

1) A gpio-line-nmaes node was written into the wrong location
2) The includes between fus/imx6ul(l).dtsi and nxp/imximx6ul(l).dtsi have been tangled
3) A reserved-memory node was inside of he cpu node

Fix these three errors

0007301: Add GPIO-line-names to all devicetrees

Wed, 08 Jul 2026 09:27:45 +0000

Add GPIO-line-names to all devicetrees

0007300: Fix 'unbalanced disables for vddsoc' for fsimx6sx

Wed, 08 Jul 2026 09:22:57 +0000

Since the last release for fsimx6sx, based on the Kernel 5.15, the enabling and disabling of power domains has been made more strict. This now causes a warning on fsimx6sx Boards whos rocessors are not equipped with a GPU. This happend because of an oversight in a change we made in NXPs GPC driver (075f6df04ebd297cd89a83cfb8c799e7f29b4d2f).

In the function imx6_pm_domain_power_on it correctly handles these CPUs with the following lines:

if (genpd->flags & PGC_DOMAIN_FLAG_NO_PU)
return -EBUSY;

The flag 'PGC_DOMAIN_FLAG_NO_PU' is se by the driver if the devicetree has the 'no-gpu' flag, which we set if neccessary in the U-Boot after evaluating the CPU type. This is neccessary as GPU-less Board will not boot otherwise.

The function imx6_pm_domain_power_off has not been patched in the earlier change, as the warning was not shown. Add the same code snippet into this function to fix this behaviour.

0007299: Unify i.MX6/SX/UL Architecture defconfigs

Wed, 08 Jul 2026 09:19:28 +0000

Add a single defconfig that works for all three architectures