MantisBT - Issues

0007095: U27 does not activate after Boot

Thu, 11 Jun 2026 16:18:05 +0000

There is an additional pull up neccesary between U28 RESET# and U27 OE, so that the SPI and UART Signals that run through U27 are gated through between the B2B Connector and the Processor.

0007030: Signal mapping for touch signals at U24 is wrong.

Thu, 11 Jun 2026 16:17:22 +0000

Signal mapping for touch signals at U24 is wrong.

U24 Y+ is connected to X-
U24 X- is connected to Y-
U24 Y- is connected to Y+

0007061: Exchange I2C_INT_SCL and I2C_INT_SDA on CPU pads

Thu, 11 Jun 2026 14:38:57 +0000

I2C_INT_SDA (LPI2C3_SDA) must be on pad GPIO_IO28 and
I2C_INT_SCL (LPI2C3_SCL) must be on pad GPIO_IO29.

Refer to imx93-pinfunc.h:
#define MX93_PAD_GPIO_IO28__LPI2C3_SDA 0x0080 0x0230 0x03E4 0x11 0x1
#define MX93_PAD_GPIO_IO29__LPI2C3_SCL 0x0084 0x0234 0x03E0 0x11 0x1

0007246: Under special conditions GT911 driver does not recognize a touch up event.

Mon, 01 Jun 2026 05:24:19 +0000

Under special conditions GT911 driver does not recognize a touch up event.
TODO: add the driver to image. According change.log is is already added since version 1.3 this is wrong!

0007156: Under special conditions write EBoot from Operating System may fail

Wed, 27 May 2026 04:46:38 +0000

Under special conditions write EBoot from Operating System may fail:
there must be bad blocks in the EBootloader memory area and at least one bad must be locate in the first four blocks.

0006640: Replace kernel IOCtl by FMD IOCtl in ddk_psd

Wed, 27 May 2026 04:46:38 +0000

Replace kernel IOCtl by FMD IOCtl (via Firmware driver) in ddk_psd.

0006619: Add IOCTLs for write kernel and PSD

Wed, 27 May 2026 04:46:38 +0000

Add IOCTLs for write kernel and PSD.

0006618: Add IOCTLs for write kernel and PSD

Wed, 27 May 2026 04:46:38 +0000

Add IOCTLs for write kernel and PSD,

0007244: DTS:FSIMX93: Fix M33 support Decleration

Tue, 19 May 2026 16:28:37 +0000

- Remove cm33: lable decleration in pcom93 dtsi, already provided in imx93.dtsi
- enable mu1 and mu2 only with SUPPROT_M33.

0007243: dynamic boot logo

Tue, 19 May 2026 13:40:25 +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.

0007242: dynamic boot logo

Tue, 19 May 2026 13:39:54 +0000

0007241: Change J12 from FH41-28S-0.5SH(05) to SFW15R-1STE1LF

Fri, 15 May 2026 08:45:43 +0000

Change J12 from FH41-28S-0.5SH(05) to SFW15R-1STE1LF.

0006499: Ethernet LED Link is inverted

Wed, 13 May 2026 12:49:07 +0000

LED Link is expected to lights up if there is an internet connection or is otherwise off. However, it is exactly the opposite. Although there is no connection, the LED lights up. When a connection is established, the LED goes out.

LED ACT works fine.

0005374: Change Net Name of ETH_A_LED

Wed, 13 May 2026 12:46:47 +0000

Change Net Name of ETH_A_LED: Set all Net Names to "ETH_A_LED". To not have multiple Names on the Net (RGMII_LED_ACT)

0005375: Check if ETH_A_LED is connected to the right pin

Wed, 13 May 2026 12:44:04 +0000

Check if ETH_A_LED is connected to the right pin.
Should it be connected to LED2?

0007170: Support for MAYA W4 Module

Wed, 13 May 2026 07:50:18 +0000

The design does not support the Maya W4 Module.

0007232: Bootselect does not work correctly

Fri, 08 May 2026 12:08:55 +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.

0006215: Increase delay after HW reset for Realtek Phy to 100ms

Tue, 05 May 2026 11:00:05 +0000

The Realtek Phy needs a minimum of 72ms before the Phy registers can be accessed.
Adding a buffer for the additional rise time of the 1.0V, we get a delay of 100ms that we should use.

0007229: Adjust serial message output for PicoCOM1 (WCE6/WEC7 only)

Thu, 30 Apr 2026 10:26:55 +0000

Adjust serial message output for PicoCOM1.
Debugport on PicoCOM1 is COM3: else alway COM1:

0006695: NetDCUMX93: CAN_B is not working

Fri, 24 Apr 2026 10:41:25 +0000

Although the NetDCU MX93 JTAG pins PAD_DAP_TDI and PAD_DAP_TDO_TRACESWO have been remapped to CAN2, the CAN interface is not working.
No signal is coming from the CPU.

0007224: Change order of wdog example steps

Wed, 22 Apr 2026 07:50:16 +0000

When the A Core is in Linux the wdog status registers can only be read if the WDOG has been initialized. Change the reading of the status flags to after initialization.

Commit ID: e4cea59d207339c640934a3cfcf42c3cb13181b3

0007223: Add support for building and cleaning all examples

Wed, 22 Apr 2026 07:48:57 +0000

build_freertos.sh allows building all examples at once or selecting a single example to build.
clean_all.sh cleans all example build outputs in one step.

Commit ID: c6a81f37eb9e092661211a9014676f1bcf5badc2

0007222: Modify the examples for use with SEGGER J-Link

Wed, 22 Apr 2026 07:47:32 +0000

Modify the XML files to allow importing the repository into VS Code and running it with SEGGER J-Link.

ef9a22c022fe5ef0b67a0aaefd4d1930ab50f15e

0007221: Rename base XML File

Wed, 22 Apr 2026 07:45:47 +0000

Its name was derieved from the NXP development Board. It is now based on our product names.

Commit ID: 3c894d654850bb02b54451c544741f330fe573bc

0007220: Add Board support in the new git

Wed, 22 Apr 2026 07:43:51 +0000

Add PicoCoreMX8MM and PicoCoreMX8MX support
ab584b5d6b1f82b963b90f35dbb68c1d7e6437d2

Add osm8mm support
d75bf9adf6f7d537a8979a28a55cbe6877784b23