MantisBT - Issues

0007346: Improve fsimx8mm in Buildroot

Wed, 02 Sep 2026 06:51:53 +0000

- Imprive defconfigs
- Improve new weston-current recipe and weston config
- Improve devicetree list
- Improve wayland displayconfiguration

0006737: Removable Packages

Mon, 31 Aug 2026 12:41:50 +0000

In addition to Features on Demand and Legacy Optional Components, Windows IoT Enterprise LTSC enables removal of more feature packages. So remove all unnecessary packages.

See:
https://learn.microsoft.com/en-us/windows/iot/iot-enterprise/optimize/removable-packages?tabs=LTSC2021

0006738: Disable unnecessary Services

Mon, 31 Aug 2026 12:41:27 +0000

The Windows operating system includes many system services that are configured to start automatically, start manually or are disabled by default.
Some services might not be required for specific fixed function devices and can be disabled, freeing up memory.

Reference:
https://learn.microsoft.com/en-us/windows/iot/iot-enterprise/optimize/services

NOTICE:
A service that is documented as "OK to disable" actually disables the Ethernet/LAN functionality on our board!!

0006103: Can't turn off test_signing/testmode

Fri, 28 Aug 2026 14:54:02 +0000

The Windows operating system is currently in Test Mode (allowing the use of unsigned drivers). If you switch to normal mode with unsigned drivers installed, the OS may fail to boot properly, resulting in an endless blue screen.

Therefore, before transitioning back to normal mode, it is necessary to sign the unsigned drivers!

It is also possible to have the drivers signed directly in VisualStudio when compiling them:
https://learn.microsoft.com/en-us/windows-hardware/drivers/develop/signing-a-driver-for-public-release

0006057: Get board name from UBoot and store in Registry

Fri, 28 Aug 2026 14:32:13 +0000

Write information from fs_deviceinfo in UBoot into the Windows Registry. Add values for boardname, ...
Implement this like in WinCE.

0007342: Get board name from UBoot and store in Registry

Thu, 27 Aug 2026 09:10:51 +0000

Get board name from UBoot and store in Registry. Nboot, uboot and uefi version. Like in WinCE

0007313: PCOM93 wrong PCB Revision

Tue, 25 Aug 2026 06:12:32 +0000

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

0007340: ETH_A_LED inverted, add to Hardware Documentation

Mon, 24 Aug 2026 16:33:59 +0000

As this is noted as well in the Hardware Documention for the PicoCoreMX8MMr2, this must be added as well for PicoCoreMX8MMr4.
This is a hardware configuration of the Realtek Phy, which cannot be changed.

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

Thu, 20 Aug 2026 14:28:44 +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.

0007332: [BOOT_MODE] Configure Pull-Ups and Pull-Downs for FERT4

Mon, 10 Aug 2026 14:18:26 +0000

Currently, all Pull-Ups and Pull-Downs for the BOOT_MODE pins are set (R155 - R161). Define a valid BOOT_MODE for FERT4.

0007315: imx93: uart receive timeout

Tue, 28 Jul 2026 08:42:26 +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.

0007327: Wrong PCB Name

Mon, 27 Jul 2026 07:00:12 +0000

"aStoneMX8MP ... Rev 1.20" should be "aStoneMX8MPr2 ... Rev 1.00"

0007325: Update poky layer to 5.0.16 to fix builderror on Ubuntu Docker with tar version 1.34+dfsg-1build4

Wed, 22 Jul 2026 13:42:18 +0000

Description:
The tar version 1.34+dfsg-1build4 now uses openat2 for syscalls. This infects the pseudo package from poky layer.
Version 5.0.16 has the fix for the pseudo layer, which avoids openat2 for syscalls.
The earliest this fails is the packagecopy step from the linux-libc-headers recipe.

Affected releases:
- fsimx93-Y2025.08.1
- fsimx8mp-Y2025.12

Fix on Ubuntu Docker (Downgrade to tar version 1.34+dfsg-1build3):
RUN apt -y --allow-downgrades install tar=1.34+dfsg-1build3

References:
Yocto Fix - https://git.openembedded.org/openembedded-core/commit/?h=scarthgap&id=a872357343b29530d05823368cfc8863a798412d
Ubuntu Fix - https://community.nxp.com/t5/S32G/Compilation-failure-occurs-with-BSP46-paired-with-linux-libc/m-p/2396719/highlight/true#M16650
Error Output - https://community.nxp.com/t5/S32G/Compilation-failure-occurs-with-BSP46-paired-with-linux-libc/m-p/2392809/highlight/true#M16572

0007321: WIFI: Voltage divider for WAKE_HOST does not work on W3 / W5

Mon, 20 Jul 2026 14:13:01 +0000

WL_WAKE_HOST and BT_WAKE_HOST are Outputs of the Wifi Module.
A volatge divider from 3.3 to 1.8V does not work.

0007320: Correct RTC_XTALI Connection

Mon, 20 Jul 2026 13:53:26 +0000

RTC_XTALI of CPU is sourced by RTC and PMIC at the same time
Remove CLK_32K_OUT from PMIC, leave Pin 29 of PMIC open.
R127 and R128 can be removed (Y1 dircetly on the CPU does not work)
R160 can be removed and bridged.
RTC_XTALI should only sourced by INTAn from the RTC

0005870: Reset generator does not work with PMIC reset logic

Mon, 20 Jul 2026 05:31:44 +0000

on PicoCoreMX8MP/MPr2 the reset signal is routed to PMIC_RST_B. This pin is not intended to be used with a reset generator, but with a push button. A low on the pin is only deteced when the PMIC is running and after a debounce time. When used with a reset generator, the PMIC starts and after the debonce time detects a low on RST_B and resets again.
On PicoCoreMX6UL100 a reset generator is used and no addition reset generator is needed.
On PicoCoreMX8MM/MX the signal is routed to PWRON_B. This pin is used with a push button.

The reset generator must be removed and a push button must be used instead.

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.

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.

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.