Posts by fs-support_PG
-
-
Hello,
as you can see from the Device Tree the the VBUS power is controlled via hardware by the USB_OTG_PWR pin, not the GPIO pin:
https://github.com/FSEmbedded/…oot/dts/efusa9x.dts#L1825
https://github.com/FSEmbedded/…sa9x.dts#L1200C7-L1200C11
https://github.com/FSEmbedded/…boot/dts/efusa9x.dts#L513
The pinmux is not at GPIO, so you cannot control it with the GPIO commands.
I am nor sure, why the USB_OTG_PWR keeps the power when unloading the driver.
However, you can try to switch to the GPIO implementation by commenting/uncommenting the respective lines in the device tree I posted.
Your F&S Support Team
-
Hello,
We added an example on how to use the etnaviv driver with an efusa9 some releases ago.
Hower, this might differ a little, depending on which display and board type is used.
to activate the etnaviv driver, there are several steps, that need to be done.
1. Use the fsimx6_etnaviv_defconfig
https://github.com/FSEmbedded/…/fsimx6_etnaviv_defconfig
2. Make some adjustments to the Device Tree: See
https://github.com/FSEmbedded/…t/dts/efusa9q-etnaviv.dts
3. Make some adjustments to the Buildroot defconfig
https://github.com/FSEmbedded/…iv_experimental_defconfig
However the Buildroot has not been fully tested with the B2024.04 release, so there could be some issues here.
Mostly, you need to make sure that the Mesa driver has the etnaviv config activated.
Your log indicates, that the main issue seems to be your display.
There is an example in the device tree on how to use a LVDS display. Maybe you can try to adapt this to your Device Tree?
https://github.com/FSEmbedded/…s/efusa9q-etnaviv.dts#L52
https://github.com/FSEmbedded/…s/efusa9q-etnaviv.dts#L98
Your F&S Support Team
-
Did you try this?
from https://community.nxp.com/t5/i…put-messed-up/m-p/1778606
Maybe also with fb0?
I don' see the IPU warnings as an acute issue. These may occur on high system load and maybe loading both displays causes a lot of load.
If they do not occur regular, i think you can ignore them for nor.
You can also try to reduce the resolution of your HDMI display if possible. This should cause less load.
You can also contact us directly by mail if you need support via meeting.
Your F&S Support Team
-
Could you try to change
to
?
I don't see any entry for RGB888 in
https://github.com/FSEmbedded/…/mxc/mxc_ipuv3_fb.c#L3138
Your F&S Support Team
-
What PIX_FMT and DATA_WIDTH is your Diplay using?
https://github.com/FSEmbedded/…ts/F%2BS/efusa9dl.dts#L77
Is it RGB or BGR? The color seems to change from Yellow to turquoise.
This suggests that the red and blue channels are swapped.
Your F&S Support Team
-
Hello,
we did not notice any color change, when enabling the clone-mode on any display.
However, I thing it is important to unblank the HDMI display before starting weston with the clone mode.
Is this done correctly?
Your F&S Support Team
-
Hello,
please test the following:
Set fb0 to lvds and fb1 to hdmi in your device tree
Boot your board and run the following commands:
This should open a weston instance, that mirrors the framebuffer from /dev/fb0 to /dev/fb1.
It worked in our tests with fsimx6-Y2024.04
Your F&S Support Team
-
Hello,
I think the main issue here is, that NXPs i.MX6 i GPU Vivante driver does not support DRM, but only the deprecated framebuffer-backend.
And I don't think the will support DRM for i.MX6 in the future.
https://github.com/nxp-imx/met…/imx-base-extend.inc#L107
One approach would be, to switch to the open source Etnaviv driver, which supports the DRM backend.
Another would be to try to use the same framebuffer for both outputs. This however would require the displays to support the same resolution.
Would this be an option?
Your F&S Support Team
-
Hello,
please try to use the fsimx8_defconfig. We are trying to crate a common defconfig for fsimx8mm/mn/mp.
You can check which defconfig we are using in the Yocto Kernel recipe
https://github.com/FSEmbedded/…inux/linux-fus_6.6.bb#L16
Your F&S Support Team
-
I can confrim, that it does not work without the HW fix on the BBDSI. It does not get any link
Display MoreCode- imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges:
- imx6q-pcie 33800000.pcie: IO 0x001ff80000..0x001ff8ffff -> 0x0000000000
- imx6q-pcie 33800000.pcie: MEM 0x0018000000..0x001fefffff -> 0x0018000000
- imx6q-pcie 33800000.pcie: iATU: unroll T, 4 ob, 4 ib, align 64K, limit 16G
- imx6q-pcie 33800000.pcie: Phy link never came up
- imx6q-pcie 33800000.pcie: Phy link never came up
- imx6q-pcie 33800000.pcie: PCI host bridge to bus 0000:00
- pci_bus 0000:00: root bus resource [bus 00-ff]
- pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
- pci_bus 0000:00: root bus resource [mem 0x18000000-0x1fefffff]
- pci 0000:00:00.0: [16c3:abcd] type 01 class 0x060400
- pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x000fffff]
- pci 0000:00:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]
- pci 0000:00:00.0: supports D1
- pci 0000:00:00.0: PME# supported from D0 D1 D3hot D3cold
- pci 0000:00:00.0: BAR 0: assigned [mem 0x18000000-0x180fffff]
- pci 0000:00:00.0: BAR 6: assigned [mem 0x18100000-0x1810ffff pref]
- pci 0000:00:00.0: PCI bridge to [bus 01-ff]
- pci_bus 0000:00: resource 4 [io 0x0000-0xffff]
- pci_bus 0000:00: resource 5 [mem 0x18000000-0x1fefffff]
With the fix it loads it gets the connection and loads the driver
Display MoreCode- imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges:
- imx6q-pcie 33800000.pcie: IO 0x001ff80000..0x001ff8ffff -> 0x0000000000
- imx6q-pcie 33800000.pcie: MEM 0x0018000000..0x001fefffff -> 0x0018000000
- imx6q-pcie 33800000.pcie: iATU: unroll T, 4 ob, 4 ib, align 64K, limit 16G
- imx6q-pcie 33800000.pcie: PCIe Gen.1 x1 link up
- imx6q-pcie 33800000.pcie: PCIe Gen.2 x1 link up
- imx6q-pcie 33800000.pcie: Link up, Gen2
- imx6q-pcie 33800000.pcie: PCIe Gen.2 x1 link up
- imx6q-pcie 33800000.pcie: PCI host bridge to bus 0000:00
- pci_bus 0000:00: root bus resource [bus 00-ff]
- pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
- pci_bus 0000:00: root bus resource [mem 0x18000000-0x1fefffff]
- pci 0000:00:00.0: [16c3:abcd] type 01 class 0x060400
- pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x000fffff]
- pci 0000:00:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]
- pci 0000:00:00.0: supports D1
- pci 0000:00:00.0: PME# supported from D0 D1 D3hot D3cold
- pci 0000:01:00.0: [1b21:0612] type 00 class 0x010601
- pci 0000:01:00.0: reg 0x10: [io 0x0000-0x0007]
- pci 0000:01:00.0: reg 0x14: [io 0x0000-0x0003]
- pci 0000:01:00.0: reg 0x18: [io 0x0000-0x0007]
- pci 0000:01:00.0: reg 0x1c: [io 0x0000-0x0003]
- pci 0000:01:00.0: reg 0x20: [io 0x0000-0x001f]
- pci 0000:01:00.0: reg 0x24: [mem 0x00000000-0x000001ff]
- pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
- pci 0000:00:00.0: BAR 0: assigned [mem 0x18000000-0x180fffff]
- pci 0000:00:00.0: BAR 14: assigned [mem 0x18100000-0x181fffff]
- pci 0000:00:00.0: BAR 15: assigned [mem 0x18200000-0x182fffff pref]
- pci 0000:00:00.0: BAR 6: assigned [mem 0x18300000-0x1830ffff pref]
- pci 0000:00:00.0: BAR 13: assigned [io 0x1000-0x1fff]
- pci 0000:01:00.0: BAR 6: assigned [mem 0x18200000-0x1820ffff pref]
- pci 0000:01:00.0: BAR 5: assigned [mem 0x18100000-0x181001ff]
- pci 0000:01:00.0: BAR 4: assigned [io 0x1000-0x101f]
- pci 0000:01:00.0: BAR 0: assigned [io 0x1020-0x1027]
- pci 0000:01:00.0: BAR 2: assigned [io 0x1028-0x102f]
- pci 0000:01:00.0: BAR 1: assigned [io 0x1030-0x1033]
- pci 0000:01:00.0: BAR 3: assigned [io 0x1034-0x1037]
- pci 0000:00:00.0: PCI bridge to [bus 01-ff]
- pci 0000:00:00.0: bridge window [io 0x1000-0x1fff]
- pci 0000:00:00.0: bridge window [mem 0x18100000-0x181fffff]
- pci 0000:00:00.0: bridge window [mem 0x18200000-0x182fffff pref]
- pci_bus 0000:00: resource 4 [io 0x0000-0xffff]
- pci_bus 0000:00: resource 5 [mem 0x18000000-0x1fefffff]
- pci_bus 0000:01: resource 0 [io 0x1000-0x1fff]
- pci_bus 0000:01: resource 1 [mem 0x18100000-0x181fffff]
- pci_bus 0000:01: resource 2 [mem 0x18200000-0x182fff
We added the capacities on the BBDSI on these lanes:
Could you check your fix again?
-
Hello,
Worked with Kernel 5.15 and Kernel 6.6;
- DELOCK 95265 Gigabit LAN Mini PCIe Card
- DELOCK 95243 Delock Mini PCIe Karte > 4 x Seriell RS-232
Worked only with Kernel 6.6:
- DELOCK 95233 SATA Mini PCIe Card
So it still does not work with any card for you?
Your F&S Support Team
-
There is a bug in fsimx8mm-Y2025.04-pre, which does not allow the Linux Kernel to build.
Please use fsimx8mm-Y2025.04.1-pre instead.
https://github.com/FSEmbedded/…e/fsimx8mm-Y2025.04.1-pre
Your F&S Support Team
-
Hello,
a pre-release for fsimx8mm has been uploaded
F&S i.MX8M-Mini Yocto Pre Release 2025.04 (fsimx8mm-Y2025.04-pre)
Your F&S Support Team
-
F&S i.MX8M-Mini Yocto Pre Release 2025.04 (fsimx8mm-Y2025.04-pre)
==============================================================
This is a pre-release, so no binaries will be delivered.
Please download the sources from
https://github.com/FSEmbedded/…ree/fsimx8mm-Y2025.04-pre
Please see the file
doc/FSiMX8MM_FirstSteps_eng.pdf
for a description of how everything is installed and used. This doc
sub-directory also contains other documentation, for example about the
hardware of the boards and the starter kits.
This is a major pre-release for all F&S boards and modules based on the
i.MX8M-Mini CPU (Solo, Dual and Quad), i.e. PicoCoreMX8MM(r2)-LPDDR4,
PicoCoreMX8MM-DDR3L, OSM8MM. More boards may be added to this family
in the future.
All these boards can work with software that is created from this release
package.
Please note that Yocto releases use a 'Y' for the version number. The
version counting is independent form other releases.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! Attention !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This is a pre-release and not suitable for production!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! Attention !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This pre release is based on NXP lf-6.6.52-2.2.0 release.
Here are some highlights of this release.
1. New Linux Kernel based on lf-6.6.52-2.2.0 with patchleve 6.6.69
The F&S Kernel is now based on the linux-fslc kernel.
https://github.com/Freescale/linux-fslc/
The fslc kernel has LTS updates for the NXP release versions, so security
fixes can be applied more easily.
2. Old bootloader U-Boot 2021.04
In the final release, the bootloader will be based on version 2024.04.
3. New Yocto version 5.0 Scarthgap
Updating Yocto to Version 5.0.8 Scarthgap.
The meta-fus layer is now based on meta-freescale and not meta-imx.
meta-freescale offers better long time support and more stable releases,
while meta-imx supports the newest features but is not as stable and
suitable for production.
The meta-imx layers are still downloaded for reference, but not included
into the build.
If you need features from them, please consider adding the changes to your
own meta-layer.
4. New Docker based building system
The F&S releases now support Docker containers as default building machines.
By using the Docker environment, the build process can be executed on any Linux host,
as long as the Docker is installed.
Starting FS_Development_Machine-Fedora-40_V0.2 Docker will be pre-installed and the
development machines will not support support building the releases directly anymore.
If you do not want to use Docker, please check the Dockerfile for the dependencies.
https://github.com/FSEmbedded/docker-fus/
1.Download manifest repository
git clone -b fsimx8mm-Y2025.04-pre https://github.com/FSEmbedded/releases-fus.git
2. Prepare Yocto-Build environment
Run setup-yocto to prepare your Yocto-Build environment. The script will read the repo manifest.xml
file and syncs all repositories that are needed for Yocto.
cd releases-fus/
./setup-yocto <yocto-buildir>
3. Prepare Docker-Environment
The ./setup-yocto script is capable of setting up a Docker environment in which the bitbake program
can be executed for the Yocto system. This command will open a docker shell, where you can execute
all yocto commands as usual.
./setup-yocto --docker
=========================================================================
The following list shows the most noticeable changes in this release in
more detail since our last release for this platform. Please note that the
source code is also used for other platforms. This is why you will
also find references to other CPU types and F&S boards here in the
change log.
u-boot-v2021.04-fs0.1-pre
-----------------------------------------------
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
linux-v6.6.69-fs0.5-pre
-----------------------------------------------
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
- Update fsimx8 boards to Kernel 6.6
meta-fus-yocto-5.0.8-fs0.1-pre
-----------------------------------------------
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
- Update fsimx8 boards to Yocto 5.0
- Use Kernel and U-Boot version specific recipes
atf-5.15.71-fsimx8mp-2024.07
-----------------------------------------
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
(no changes)
firmware-imx-8.10.1 ddr synopsys
-------------------------------------------
(no changes)
Examples
--------
(no changes)
Documentation
-------------
- Update to version 1.9 of FSiMX8MM_FirstSteps_eng.pdf
- Update to version 0.22 of LinuxOnFSBoards_eng.pdf
Please download the hardware documentation directly from our website.
Then you always have the newest version.
-
Hello,
unfortunately we could not find a solution with the current release.
We just uploaded a net pre-releasebased on Yocto 5.0 for fsimx8mp
F&S i.MX8M-Plus Yocto Pre-Release 2025.03 (fsimx8mp-Y2025.03-pre)
There where some changes in the pcie drivers here. Could you test if it makes any difference?
Your F&S Support Team
-
F&S i.MX8M-Plus Yocto Pre Release 2025.03 (fsimx8mp-Y2025.03-pre)
This is a pre-release, so no binaries will be delivered.
Please download the sources from
https://github.com/FSEmbedded/…ree/fsimx8mp-Y2025.03-pre
Please see the file
doc/FSiMX8MP_FirstSteps_eng.pdf
for a description of how everything is installed and used. This doc
sub-directory also contains other documentation, for example about the
hardware of the boards and the starter kits.
This is a major pre-release for all F&S boards and modules based on the
i.MX8M-Plus CPU (Solo, Dual and Quad), i.e. PicoCoreMX8MP(r2), armStoneMX8MP,
efusmx8mp or SMARCMX8MP (FSSMMX8MP). More boards may be added to this family
in the future.
All these boards can work with software that is created from this release
package.
Please note that Yocto releases use a 'Y' for the version number. The
version counting is independent form other releases.
The release consists of the following files and directories:
Readme-yocto-f+s.txt Release notes (this text)
setup-yocto Script to download and install the Yocto release
fs-release-manifest.xml Release Manifest, containing the used versions
binaries/ Precompiled images (full names)
sdcard/ Precompiled images (names as expected by
install script)
doc/ Hardware and software manuals, schematics
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! Attention !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This is a pre-release and not suitable for production!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! Attention !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This pre release is based on NXP lf-6.6.52-2.2.0 release.
Here are some highlights of this release.
1. New Linux Kernel based on lf-6.6.52-2.2.0 with patchleve 6.6.69
The F&S Kernel is now based on the linux-fslc kernel.
https://github.com/Freescale/linux-fslc/
The fslc kernel has LTS updates for the NXP release versions, so security
fixes can be applied more easily.
2. Old bootloader U-Boot 2021.04
In the final release, the bootloader will be based on version 2024.04.
3. New Yocto version 5.0 Scarthgap
Updating Yocto to Version 5.0.4 Scarthgap.
The meta-fus layer is now based on meta-freescale and not meta-imx.
meta-freescale offers better long time support and more stable releases,
while meta-imx supports the newest features but is not as stable and
suitable for production.
The meta-imx layers are still downloaded for reference, but not included
into the build.
If you need features from them, please consider adding the changes to your
own meta-layer.
4. New Docker based building system
The F&S releases now support Docker containers as default building machines.
By using the Docker environment, the build process can be executed on any Linux host,
as long as the Docker is installed.
Starting FS_Development_Machine-Fedora-40_V0.2 Docker will be pre-installed and the
development machines will not support support building the releases directly anymore.
If you do not want to use Docker, please check the Dockerfile for the dependencies.
https://github.com/FSEmbedded/docker-fus/
1.Download manifest repository
git clone -b fsimx8mp-Y2025.03-pre https://github.com/FSEmbedded/releases-fus.git
2. Prepare Yocto-Build environment
Run setup-yocto to prepare your Yocto-Build environment. The script will read the repo manifest.xml
file and syncs all repositories that are needed for Yocto.
cd releases-fus/
./setup-yocto <yocto-buildir>
3. Prepare Docker-Environment
The ./setup-yocto script is capable of setting up a Docker environment in which the bitbake program
can be executed for the Yocto system. This command will open a docker shell, where you can execute
all yocto commands as usual.
./setup-yocto --docker
=========================================================================
The following list shows the most noticeable changes in this release in
more detail since our last release for this platform. Please note that the
source code is also used for other platforms. This is why you will
also find references to other CPU types and F&S boards here in the
change log.
u-boot-v2021.04-fs0.1-pre
-----------------------------------------------
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
linux-v6.6.69-fs0.4-pre
-----------------------------------------------
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
- Update fsimx8 boards to Kernel 6.6
meta-fus-yocto-5.0.4-fs0.3-pre
-----------------------------------------------
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
- Update fsimx8 boards to Yocto 5.0
- Use Kernel and U-Boot version specific recipes
atf-5.15.71-fsimx8mp-2024.07
-----------------------------------------
Supported boards: PicoCoreMX8MP PicoCoreMX8MPr2 armStonemx8MP
efusmx8mp SMARCMX8MP
(no changes)
firmware-imx-8.10.1 ddr synopsys
-------------------------------------------
(no changes)
Examples
--------
(no changes)
Documentation
-------------
- Update to version 1.6 of FSiMX8MP_FirstSteps_eng.pdf
- Update to version 0.19 of LinuxOnFSBoards_eng.pdf
Please download the hardware documentation directly from our website.
Then you always have the newest version.
-
Hello,
we are currently working on a pre-release for fsimx8mm and fsimx8mp, which we are aiming to upload in the next two weeks.
A pre-release for fsimx6/ul/sx will take more time and is currently not in progress.
However, the Kernel from the fsimx93 pre-release should at least build with all fsimx defconfigs, so you could try to compile it four your boards.
https://github.com/FSEmbedded/…tree/fsimx93-Y2025.02-pre
Your F&S Support Team
-
Hello,
are you using the F&S Development Machine or your own building machine?
Please make sure, that your building machine has the command crc32 acailable.
Your F&S Support Team
-
Hello,
we where able to reproduce the problem on a PicoCoremx8MP with a SATA-PCIE card. Other PCIE cards seem to work.
We are currently investigating the cause.
Your F&S Support Team