ICOP tech wiki - User contributions [en]

Developers Guide-YOCTO

2025-12-24T10:02:45Z

Joec:

<table style="padding:15px; background-color: #0055a5; color: white; width:100%; font-size:25px; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Developers Guide
</td></tr></table>

<table style="background-color: #F0F0FF; width:100%;">
<tr>
<td style="width:250px; padding:5px 25px 5px 25px;">
[[File:Yocto.png|frameless|标题|連結=Special:FilePath/Yocto.png]]
</td>
<td style="padding:20px 30px 0px 0px; vertical-align:top; font-size:22px;">
=='''<big>Yocto Project</big>'''==
Yocto project is a framework for creating a Linux distributions for embedded devices. It's layering mechanism makes it easy to add Linux to new target devices highly customized for a particular platform; it can include custom start-up scripts, software packages built with a high degree of optimization for a particular architecture, and different user interfaces from full Gnome desktop to a simple a serial console.

This release is based on [https://source.codeaurora.org/external/imx NXP BSP] layer for Yocto framework.
<br /></td></tr></table>
<div style="overflow:hidden; padding-top:20px; min-width:1000px; margin-top:-33px;">
<div style="width:100%;">
<p></p><p><br />
</p>

<div style="width:48%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table><table style="padding:10px; background-color: #4f9df2; color: white; font-size:19px; width:100%; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Test and Use
</td></tr></table>

<table style="background-color: #d7e4f2; width:100%; height:740px;">
<tr>
<td></td>
<td style="padding-left: 4%; padding-right: 4%; vertical-align:top; max-width:100%;"><b><big>Test and use an Interface</big></b><div style="width:100%;"><div style="width:50%; float: left;"><ul><li><big>[[PN8M-090T-Bluetooth A2DP|Bluetooth A2DP]]</big></li><li><big>[[PN8M-090T-Ethernet|Ethernet]]</big></li><li><big>[[PN8M-090T-UART|UART]]</big></li><li><big>[[PN8M-090T-WiFi|WiFi]]</big></li><li><big>[[PN8M-090T-SPK-OUT|SPK-OUT]]</big></li></ul></div>
</td></tr>
<tr>
<td></td>
</tr></table>

</div>

<div style="width:47%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table><table style="padding:10px; background-color: #4f9df2; color: white; font-size:19px; width:100%; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Techni<span class="plainlinks"></span>cal Resource
</td></tr></table>
<table style="background-color: #d7e4f2; width:100%; height:740px;">

<tr>
<td></td>
<td style="padding-left: 4%; padding-right: 4%; vertical-align:top; max-width:100%;"><ul>
<li> [[Recipe for building Yocto Linux for PN8M-090T|<big>Recipe for building Yocto Linux for PN8M-090T</big>]]
</li>
<li> <big>[[Recovery the Yocto in the eMMC under UBOOT mode-PN9M-090T|Recovery the Yocto in the eMMC under UBOOT mode]]</big>
</li>
<li> <big>[[How to set up time zone in Yocto-PN8M-090T|How to set up time zone in Yocto]]</big>
</li>
<li> <big>[[How to check storages contents in Yocto-PN8M-090T|How to check storages contents in Yocto]]</big>
</li>
<li> [[Resovling Terminal frozen after closing chromium--no--sandbox|<big></big>]]<big>[[Chromium--no-sandbox-PN8M-090T|Resovling Terminal frozen after closing chromium--no--sandbox]]</big>
</li>
<li> [[Resovling Terminal frozen after closing chromium--no--sandbox|<big></big>]]<big>[[Chromium-Youtube-soundcutting-PN8M-090T|Resovling cutting sound in Chromium&Youtube]]</big>
</li>
<li> [[Resovling Terminal frozen after closing chromium--no--sandbox|<big></big>]]<big>[[PCI7600G LTE module setting|PCI7600G MINI PCI-E 4G Module driver setting]]</big>
</li>
</ul><ul>
<li><big>[[Run a modbus RTU example on NX8MM-35]]</big>
</li>
<li><big>[[Change the boot image of the system on i.MX series devices]]</big>
</li>
<li><big>[[How to test the SPI bus on NX8MM-35]]</big>
</li>
</ul>
</td></tr>
<tr>
<td></td>
<td style="padding:0px 10px 10px 0px; height:100px;"><div class="floatright"></div>
</td></tr></table>

</div>

<div style="width:45%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table>

How to test the SPI bus on NX8MM-35

2025-12-24T10:01:03Z

Joec:

How to test the SPI bus on NX8MM-35

2025-12-24T09:57:35Z

Joec:

=How to test the SPI bus on NX8MM-35=

This article will tell you how to test the SPI bus on the NX8MM-35 in Yocto Linux.

The SPI bus is an optional feature supported on ICOP's NX8MM-35, and it shares functionality with UART3 on the board.
In the tips below, we will provide the guide step by step.

==Tools you need:==

#NX8MM-35[https://www.icop.com.tw/product/NX8MM-35 (Find it here)]
#Yocto Linux 4.0:I[https://ftp.icop.com.tw/share/x4hhQ1rp Image] [https://wiki.icop.com.tw/product/index.php/How_to_Restore_Yocto_Linux_4.0_to_the_eMMC_on_NX8MM-35 / Guide]
#USB to micro USB cable for restoring image.
#SPI Testing file (Put it in a USB disk): [https://ftp.icop.com.tw/share/8NdTKZ-H link]
#A testing wire to test SPI bus self-transmitting.

[[File:PNG2PNM.png|border|frameless|600x600px]]
==Switching the UART3 to SPI bus on NX8MM-35.==

On NX8MM-35, the UART3 and SPI bus can be switched by modifying the resistor on the board.
Please follow the image below and use the soldering iron to move the 0 ohm resistor to the correct location.
[[File:PNG2PNM.png|border|frameless|600x600px]]

2. pnmquant 224 to change the color to 224 colors
<pre>
pnmquant 224 linuxlogo.pnm>linuxlogo224.pnm
</pre>
[[File:PNM224.png|border|frameless|600x600px]]

3. pnmtoplainpnm to change the file to change the .pnm file to .ppm file.
<pre>
pnmtoplainpnm linuxlogo224.pnm>logo_linux_clut224.ppm
</pre>
[[File:PNM2PPM.png|frameless|600x600px]]

By the steps above, we can change the PNG file to 224 colors .ppm file.

==2. Replace the old boot image and build the image file==

In this case, we assume the user already know how to build a image file by recipe, and already has the recipe file.
If the recipe file is not implemented, check [[Recipe for building Yocto4.0 Linux for PN8M-090T|here]] for an example.

1. Copy the logo_linux_clut224.ppm to the logo file.
<pre>
cp logo_linux_clut224.ppm kernel-source/drivers/video/logo
</pre>
kernel-source/drivers/video/logo is the relative location, in this case, the exact location is:
<pre>
/home/user/imx-yocot-bsp/build-dmp/tmp/work-sahred/dm421/kernel-source/drivers/video/logo
</pre>
[[File:CPPPM2LOGO2.png|frameless|600x600px]]

The exact location will be diffrerent based on the user's setting.

2. After replaced the logo file, run bitbake command below to compile linux-imx in the recipe after created the image setup environment. (Check step 7 ~9 [[Recipe for building Yocto4.0 Linux for PN8M-090T|here]] for setup environment.)
<pre>
bitbake -c compile -f linux-imx
</pre>

[[File:Bitbakecompile.png|frameless|600x600px]]

3. Generate the image file by bitbake
<pre>
bitbake imx-yocto-multimedia
</pre>

[[File:Bitbakeimage.png|frameless|600x600px]]

In this case, we use imx-yocto-multimedia, the user can decide which kind of image they would like to generate; the detailed information is as below:
{| class="wikitable"
!Image Name!!Target
|-
|core-image-minimal||A compact image that enables the device to boot with minimal functionality.
|-
|core-image-base||A console-only image that ensures full compatibility with the target device's hardware.
|-
|core-image-sato||An image featuring the Sato mobile environment, providing a visual style and mobile applications such as a terminal, editor, and file manager. It utilizes the Sato theme and includes Pimlico applications.
|-
|imx-image-core||An i.MX-based image containing i.MX test applications, designed for Wayland backends. This image is used in daily core testing for i.MX devices.
|-
|fsl-image-machine-test||An i.MX core image from the FSL Community, providing a console-only environment with no GUI interface.
|-
|imx-image-multimedia||An i.MX image with a graphical user interface (GUI), but without any Qt content.
|-
|imx-image-full||An open-source Qt 5-based image that incorporates machine learning features. These images are designed specifically for i.MX SoCs with hardware graphics support and are incompatible with the i.MX 6UltraLite, i.MX 6UltraLiteLite, i.MX 6SLL, and i.MX7Dual models.
|}
Reference: [https://www.nxp.com/doc/IMX_YOCTO_PROJECT_USERS_GUIDE NXP's i.MX Yocto Project User's Guide]

4. Restore the image you've built to the device

*Check How to install the image file by UUU. in the [[Recipe for building Yocto4.0 Linux for PN8M-090T|Recipe guide]]
*Use the UUU to restore image ([[How to Restore Yocto Linux 4.0 to the eMMC on PN8M-090T|Image restore guide]])

5. After restored the image to the device, you will see the boot image when booting the device

[[File:Bootimage.jpg|frameless|600x600px]]

File:Testimage.jpg

2025-12-24T09:56:46Z

Joec:

File:Boardoutlinewithwire.jpg

2025-12-24T09:56:36Z

Joec:

File:NX8MM-35C SPI UART3 switch.png

2025-12-24T09:56:25Z

Joec:

File:Testingwire.jpg

2025-12-24T09:56:02Z

Joec:

How to test the SPI bus on NX8MM-35

2025-12-24T09:54:56Z

Joec: Created page with "=How to test the SPI bus on NX8MM-35= This article will tell you how to test the SPI bus on the NX8MM-35 in Yocto Linux. The SPI bus is an optional feature supported on ICOP..."

=How to test the SPI bus on NX8MM-35=

This article will tell you how to test the SPI bus on the NX8MM-35 in Yocto Linux.

The SPI bus is an optional feature supported on ICOP's NX8MM-35, and it shares functionality with UART3 on the board.
In the tips below, we will provide the guide step by step.

==Tools you need:==

#NX8MM-35[https://www.icop.com.tw/product/NX8MM-35 (Find it here)]
#Yocto Linux 4.0:I[https://ftp.icop.com.tw/share/x4hhQ1rp Image] [https://wiki.icop.com.tw/product/index.php/How_to_Restore_Yocto_Linux_4.0_to_the_eMMC_on_NX8MM-35 / Guide]
#USB to micro USB cable for restoring image.
#SPI Testing file (Put it in a USB disk): [https://ftp.icop.com.tw/share/8NdTKZ-H link]
#A testing wire to test SPI bus self-transmitting.

==1. Making a ppm image file with 224 colors==

First, prepare a custom boot image and convert it to a Linux-compatible PPM file (the image should be saved with a .ppm extension in ASCII format and have a maximum of 224 colors).
Please follow the steps below to change the image to the correct format:

1. Using pngtopnm to change the .png file to .pnm file.
<pre>
pngtopnm xxxx.png>linuxlogo.pnm
</pre>
(xxxx=your file name)

[[File:PNG2PNM.png|border|frameless|600x600px]]

2. pnmquant 224 to change the color to 224 colors
<pre>
pnmquant 224 linuxlogo.pnm>linuxlogo224.pnm
</pre>
[[File:PNM224.png|border|frameless|600x600px]]

3. pnmtoplainpnm to change the file to change the .pnm file to .ppm file.
<pre>
pnmtoplainpnm linuxlogo224.pnm>logo_linux_clut224.ppm
</pre>
[[File:PNM2PPM.png|frameless|600x600px]]

By the steps above, we can change the PNG file to 224 colors .ppm file.

==2. Replace the old boot image and build the image file==

In this case, we assume the user already know how to build a image file by recipe, and already has the recipe file.
If the recipe file is not implemented, check [[Recipe for building Yocto4.0 Linux for PN8M-090T|here]] for an example.

1. Copy the logo_linux_clut224.ppm to the logo file.
<pre>
cp logo_linux_clut224.ppm kernel-source/drivers/video/logo
</pre>
kernel-source/drivers/video/logo is the relative location, in this case, the exact location is:
<pre>
/home/user/imx-yocot-bsp/build-dmp/tmp/work-sahred/dm421/kernel-source/drivers/video/logo
</pre>
[[File:CPPPM2LOGO2.png|frameless|600x600px]]

The exact location will be diffrerent based on the user's setting.

2. After replaced the logo file, run bitbake command below to compile linux-imx in the recipe after created the image setup environment. (Check step 7 ~9 [[Recipe for building Yocto4.0 Linux for PN8M-090T|here]] for setup environment.)
<pre>
bitbake -c compile -f linux-imx
</pre>

[[File:Bitbakecompile.png|frameless|600x600px]]

3. Generate the image file by bitbake
<pre>
bitbake imx-yocto-multimedia
</pre>

[[File:Bitbakeimage.png|frameless|600x600px]]

In this case, we use imx-yocto-multimedia, the user can decide which kind of image they would like to generate; the detailed information is as below:
{| class="wikitable"
!Image Name!!Target
|-
|core-image-minimal||A compact image that enables the device to boot with minimal functionality.
|-
|core-image-base||A console-only image that ensures full compatibility with the target device's hardware.
|-
|core-image-sato||An image featuring the Sato mobile environment, providing a visual style and mobile applications such as a terminal, editor, and file manager. It utilizes the Sato theme and includes Pimlico applications.
|-
|imx-image-core||An i.MX-based image containing i.MX test applications, designed for Wayland backends. This image is used in daily core testing for i.MX devices.
|-
|fsl-image-machine-test||An i.MX core image from the FSL Community, providing a console-only environment with no GUI interface.
|-
|imx-image-multimedia||An i.MX image with a graphical user interface (GUI), but without any Qt content.
|-
|imx-image-full||An open-source Qt 5-based image that incorporates machine learning features. These images are designed specifically for i.MX SoCs with hardware graphics support and are incompatible with the i.MX 6UltraLite, i.MX 6UltraLiteLite, i.MX 6SLL, and i.MX7Dual models.
|}
Reference: [https://www.nxp.com/doc/IMX_YOCTO_PROJECT_USERS_GUIDE NXP's i.MX Yocto Project User's Guide]

4. Restore the image you've built to the device

* Check How to install the image file by UUU. in the [[Recipe for building Yocto4.0 Linux for PN8M-090T|Recipe guide]]
* Use the UUU to restore image ([[How to Restore Yocto Linux 4.0 to the eMMC on PN8M-090T|Image restore guide]])

5. After restored the image to the device, you will see the boot image when booting the device

[[File:Bootimage.jpg|frameless|600x600px]]

Developers Guide-YOCTO

2025-09-04T06:25:42Z

Joec:

<table style="padding:15px; background-color: #0055a5; color: white; width:100%; font-size:25px; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Developers Guide
</td></tr></table>

<table style="background-color: #F0F0FF; width:100%;">
<tr>
<td style="width:250px; padding:5px 25px 5px 25px;">
[[File:Yocto.png|frameless|标题|連結=Special:FilePath/Yocto.png]]
</td>
<td style="padding:20px 30px 0px 0px; vertical-align:top; font-size:22px;">
=='''<big>Yocto Project</big>'''==
Yocto project is a framework for creating a Linux distributions for embedded devices. It's layering mechanism makes it easy to add Linux to new target devices highly customized for a particular platform; it can include custom start-up scripts, software packages built with a high degree of optimization for a particular architecture, and different user interfaces from full Gnome desktop to a simple a serial console.

This release is based on [https://source.codeaurora.org/external/imx NXP BSP] layer for Yocto framework.
<br /></td></tr></table>
<div style="overflow:hidden; padding-top:20px; min-width:1000px; margin-top:-33px;">
<div style="width:100%;">
<p></p><p><br />
</p>

<div style="width:48%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table><table style="padding:10px; background-color: #4f9df2; color: white; font-size:19px; width:100%; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Test and Use
</td></tr></table>

<table style="background-color: #d7e4f2; width:100%; height:740px;">
<tr>
<td></td>
<td style="padding-left: 4%; padding-right: 4%; vertical-align:top; max-width:100%;"><b><big>Test and use an Interface</big></b><div style="width:100%;"><div style="width:50%; float: left;"><ul><li><big>[[PN8M-090T-Bluetooth A2DP|Bluetooth A2DP]]</big></li><li><big>[[PN8M-090T-Ethernet|Ethernet]]</big></li><li><big>[[PN8M-090T-UART|UART]]</big></li><li><big>[[PN8M-090T-WiFi|WiFi]]</big></li><li><big>[[PN8M-090T-SPK-OUT|SPK-OUT]]</big></li></ul></div>
</td></tr>
<tr>
<td></td>
</tr></table>

</div>

<div style="width:47%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table><table style="padding:10px; background-color: #4f9df2; color: white; font-size:19px; width:100%; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Techni<span class="plainlinks"></span>cal Resource
</td></tr></table>
<table style="background-color: #d7e4f2; width:100%; height:740px;">

<tr>
<td></td>
<td style="padding-left: 4%; padding-right: 4%; vertical-align:top; max-width:100%;"><ul>
<li> [[Recipe for building Yocto Linux for PN8M-090T|<big>Recipe for building Yocto Linux for PN8M-090T</big>]]
</li>
<li> <big>[[Recovery the Yocto in the eMMC under UBOOT mode-PN9M-090T|Recovery the Yocto in the eMMC under UBOOT mode]]</big>
</li>
<li> <big>[[How to set up time zone in Yocto-PN8M-090T|How to set up time zone in Yocto]]</big>
</li>
<li> <big>[[How to check storages contents in Yocto-PN8M-090T|How to check storages contents in Yocto]]</big>
</li>
<li> [[Resovling Terminal frozen after closing chromium--no--sandbox|<big></big>]]<big>[[Chromium--no-sandbox-PN8M-090T|Resovling Terminal frozen after closing chromium--no--sandbox]]</big>
</li>
<li> [[Resovling Terminal frozen after closing chromium--no--sandbox|<big></big>]]<big>[[Chromium-Youtube-soundcutting-PN8M-090T|Resovling cutting sound in Chromium&Youtube]]</big>
</li>
<li> [[Resovling Terminal frozen after closing chromium--no--sandbox|<big></big>]]<big>[[PCI7600G LTE module setting|PCI7600G MINI PCI-E 4G Module driver setting]]</big>
</li>
</ul><ul>
<li><big>[[Run a modbus RTU example on NX8MM-35]]</big>
</li>
<li><big>[[Change the boot image of the system on i.MX series devices]]</big>
</li>
</ul>
</td></tr>
<tr>
<td></td>
<td style="padding:0px 10px 10px 0px; height:100px;"><div class="floatright"></div>
</td></tr></table>

</div>

<div style="width:45%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table>

Change the boot image of the system on i.MX series devices

2025-09-04T06:24:52Z

Joec:

=Change the boot image of the system on i.MX series devices=

This article will tell you how to change the title logo / photo of the system for i.MX series device.

In standard image that ICOP provided; no matter it's Yocto Linux or Android, the title logo / photo is always the linux logo, but this can be changed by simple steps.

In the tips below, we will provide the guide step by step.

==Tools you need:==

#i.MX series products like [https://www.icop.com.tw/product/NX8MM-35 NX8MM-35] / [https://www.icop.com.tw/product/PN8M-090T-8A PN8M-090T] / [https://www.icop.com.tw/product/EBOX-IMX8MM EBOX-IMX8MM]
##In this tips, we use PN8M-090T as an example.
#Yocto Linux 4.0:Recipe (Find the recipe file from our [[Main Page|Wiki]])
#Image file of your logo / photo
#Operating system for building the image: Ubuntu 22.04 or after

==1. Making a ppm image file with 224 colors==

First, prepare a custom boot image and convert it to a Linux-compatible PPM file (the image should be saved with a .ppm extension in ASCII format and have a maximum of 224 colors).
Please follow the steps below to change the image to the correct format:

1. Using pngtopnm to change the .png file to .pnm file.
<pre>
pngtopnm xxxx.png>linuxlogo.pnm
</pre>
(xxxx=your file name)

[[File:PNG2PNM.png|border|frameless|600x600px]]

2. pnmquant 224 to change the color to 224 colors
<pre>
pnmquant 224 linuxlogo.pnm>linuxlogo224.pnm
</pre>
[[File:PNM224.png|border|frameless|600x600px]]

3. pnmtoplainpnm to change the file to change the .pnm file to .ppm file.
<pre>
pnmtoplainpnm linuxlogo224.pnm>logo_linux_clut224.ppm
</pre>
[[File:PNM2PPM.png|frameless|600x600px]]

By the steps above, we can change the PNG file to 224 colors .ppm file.

==2. Replace the old boot image and build the image file==

In this case, we assume the user already know how to build a image file by recipe, and already has the recipe file.
If the recipe file is not implemented, check [[Recipe for building Yocto4.0 Linux for PN8M-090T|here]] for an example.

1. Copy the logo_linux_clut224.ppm to the logo file.
<pre>
cp logo_linux_clut224.ppm kernel-source/drivers/video/logo
</pre>
kernel-source/drivers/video/logo is the relative location, in this case, the exact location is:
<pre>
/home/user/imx-yocot-bsp/build-dmp/tmp/work-sahred/dm421/kernel-source/drivers/video/logo
</pre>
[[File:CPPPM2LOGO2.png|frameless|600x600px]]

The exact location will be diffrerent based on the user's setting.

2. After replaced the logo file, run bitbake command below to compile linux-imx in the recipe after created the image setup environment. (Check step 7 ~9 [[Recipe for building Yocto4.0 Linux for PN8M-090T|here]] for setup environment.)
<pre>
bitbake -c compile -f linux-imx
</pre>

[[File:Bitbakecompile.png|frameless|600x600px]]

3. Generate the image file by bitbake
<pre>
bitbake imx-yocto-multimedia
</pre>

[[File:Bitbakeimage.png|frameless|600x600px]]

In this case, we use imx-yocto-multimedia, the user can decide which kind of image they would like to generate; the detailed information is as below:
{| class="wikitable"
!Image Name!!Target
|-
|core-image-minimal||A compact image that enables the device to boot with minimal functionality.
|-
|core-image-base||A console-only image that ensures full compatibility with the target device's hardware.
|-
|core-image-sato||An image featuring the Sato mobile environment, providing a visual style and mobile applications such as a terminal, editor, and file manager. It utilizes the Sato theme and includes Pimlico applications.
|-
|imx-image-core||An i.MX-based image containing i.MX test applications, designed for Wayland backends. This image is used in daily core testing for i.MX devices.
|-
|fsl-image-machine-test||An i.MX core image from the FSL Community, providing a console-only environment with no GUI interface.
|-
|imx-image-multimedia||An i.MX image with a graphical user interface (GUI), but without any Qt content.
|-
|imx-image-full||An open-source Qt 5-based image that incorporates machine learning features. These images are designed specifically for i.MX SoCs with hardware graphics support and are incompatible with the i.MX 6UltraLite, i.MX 6UltraLiteLite, i.MX 6SLL, and i.MX7Dual models.
|}
Reference: [https://www.nxp.com/doc/IMX_YOCTO_PROJECT_USERS_GUIDE NXP's i.MX Yocto Project User's Guide]

4. Restore the image you've built to the device

* Check How to install the image file by UUU. in the [[Recipe for building Yocto4.0 Linux for PN8M-090T|Recipe guide]]
* Use the UUU to restore image ([[How to Restore Yocto Linux 4.0 to the eMMC on PN8M-090T|Image restore guide]])

5. After restored the image to the device, you will see the boot image when booting the device

[[File:Bootimage.jpg|frameless|600x600px]]

Change the boot image of the system on i.MX series devices

2025-09-04T06:20:03Z

Joec:

=Change the boot image of the system on i.MX series devices=

This article will tell you how to change the title logo / photo of the system for i.MX series device.
In standard image that ICOP provided; no matter it's Yocto Linux or Android, the title logo / photo is always the linux logo, but this can be changed by simple steps.
In the tips below, we will provide the guide step by step.

==Tools you need:==

#i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
##In this tips, we use PN8M-090T as an example.
#Yocto Linux 4.0:Recipe (Find the recipe file from our Wiki)
#Image file of your logo / photo
#Operating system for building the image: Ubuntu 22.04 or after

==1. Making a ppm image file with 224 colors==

First, prepare a custom boot image and convert it to a Linux-compatible PPM file (the image should be saved with a .ppm extension in ASCII format and have a maximum of 224 colors).
Please follow the steps below to change the image to the correct format:

1. Using pngtopnm to change the .png file to .pnm file.
<pre>
pngtopnm xxxx.png>linuxlogo.pnm
</pre>
(xxxx=your file name)

[[File:PNG2PNM.png|border|frameless|600x600px]]

2. pnmquant 224 to change the color to 224 colors
<pre>
pnmquant 224 linuxlogo.pnm>linuxlogo224.pnm
</pre>
[[File:PNM224.png|border|frameless|600x600px]]

3. pnmtoplainpnm to change the file to change the .pnm file to .ppm file.
<pre>
pnmtoplainpnm linuxlogo224.pnm>logo_linux_clut224.ppm
</pre>
[[File:PNM2PPM.png|frameless|600x600px]]

By the steps above, we can change the PNG file to 224 colors .ppm file.

==2. Replace the old boot image and build the image file==

In this case, we assume the user already know how to build a image file by recipe, and already has the recipe file.
If the recipe file is not implemented, check here for an example.

1. Copy the logo_linux_clut224.ppm to the logo file.
<pre>
cp logo_linux_clut224.ppm kernel-source/drivers/video/logo
</pre>
kernel-source/drivers/video/logo is the relative location, in this case, the exact location is:
<pre>
/home/user/imx-yocot-bsp/build-dmp/tmp/work-sahred/dm421/kernel-source/drivers/video/logo
</pre>
[[File:CPPPM2LOGO2.png|frameless|600x600px]]

The exact location will be diffrerent based on the user's setting.

2. After replaced the logo file, run bitbake command below to compile linux-imx in the recipe after created the image setup environment. (Check step 7 ~9 here for setup environment.)
<pre>
bitbake -c compile -f linux-imx
</pre>

[[File:Bitbakecompile.png|frameless|600x600px]]

3. Generate the image file by bitbake
<pre>
bitbake imx-yocto-multimedia
</pre>

[[File:Bitbakeimage.png|frameless|600x600px]]

In this case, we use imx-yocto-multimedia, the user can decide which kind of image they would like to generate; the detailed information is as below:
{| class="wikitable"
!Image Name!!Target
|-
|core-image-minimal||A compact image that enables the device to boot with minimal functionality.
|-
|core-image-base||A console-only image that ensures full compatibility with the target device's hardware.
|-
|core-image-sato||An image featuring the Sato mobile environment, providing a visual style and mobile applications such as a terminal, editor, and file manager. It utilizes the Sato theme and includes Pimlico applications.
|-
|imx-image-core||An i.MX-based image containing i.MX test applications, designed for Wayland backends. This image is used in daily core testing for i.MX devices.
|-
|fsl-image-machine-test||An i.MX core image from the FSL Community, providing a console-only environment with no GUI interface.
|-
|imx-image-multimedia||An i.MX image with a graphical user interface (GUI), but without any Qt content.
|-
|imx-image-full||An open-source Qt 5-based image that incorporates machine learning features. These images are designed specifically for i.MX SoCs with hardware graphics support and are incompatible with the i.MX 6UltraLite, i.MX 6UltraLiteLite, i.MX 6SLL, and i.MX7Dual models.
|}
Reference: NXP's i.MX Yocto Project User's Guide

4. Restore the image you've built to the device
Check How to install the image file by UUU. in the Recipe guide
Use the UUU to restore image (Image restore guide)

5. After restored the image to the device, you will see the boot image when booting the device

[[File:Bootimage.jpg|frameless|600x600px]]

Change the boot image of the system on i.MX series devices

2025-09-04T06:19:33Z

Joec:

=Change the boot image of the system on i.MX series devices=

This article will tell you how to change the title logo / photo of the system for i.MX series device.
In standard image that ICOP provided; no matter it's Yocto Linux or Android, the title logo / photo is always the linux logo, but this can be changed by simple steps.
In the tips below, we will provide the guide step by step.

==Tools you need:==

# i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
## In this tips, we use PN8M-090T as an example.
# Yocto Linux 4.0:Recipe (Find the recipe file from our Wiki)
# Image file of your logo / photo
# Operating system for building the image: Ubuntu 22.04 or after

==1. Making a ppm image file with 224 colors==

First, prepare a custom boot image and convert it to a Linux-compatible PPM file (the image should be saved with a .ppm extension in ASCII format and have a maximum of 224 colors).
Please follow the steps below to change the image to the correct format:

1. Using pngtopnm to change the .png file to .pnm file.
<pre>
pngtopnm xxxx.png > linuxlogo.pnm
</pre>
(xxxx = your file name)

[[File:PNG2PNM.png|frameless|600x600px|link=File:PNG2PNM.png|Convert PNG to PNM]]

2. pnmquant 224 to change the color to 224 colors
<pre>
pnmquant 224 linuxlogo.pnm > linuxlogo224.pnm
</pre>

[[File:PNM224.png|frameless|600x600px|link=File:PNM224.png|Reduce color to 224]]

3. pnmtoplainpnm to change the file to change the .pnm file to .ppm file.
<pre>
pnmtoplainpnm linuxlogo224.pnm > logo_linux_clut224.ppm
</pre>

[[File:PNM2PPM.png|frameless|600x600px|link=File:PNM2PPM.png|Convert PNM to PPM]]

By the steps above, we can change the PNG file to 224 colors .ppm file.

==2. Replace the old boot image and build the image file==

In this case, we assume the user already know how to build an image file by recipe, and already has the recipe file.
If the recipe file is not implemented, check here for an example.

1. Copy the logo_linux_clut224.ppm to the logo file.
<pre>
cp logo_linux_clut224.ppm kernel-source/drivers/video/logo
</pre>
kernel-source/drivers/video/logo is the relative location, in this case, the exact location is:
<pre>
/home/user/imx-yocto-bsp/build-dmp/tmp/work-shared/dm421/kernel-source/drivers/video/logo
</pre>

[[File:CPPPM2LOGO2.png|frameless|600x600px|link=File:CPPPM2LOGO2.png|Copy the PPM logo to kernel source]]

The exact location will be different based on the user's setting.

2. After replaced the logo file, run bitbake command below to compile linux-imx in the recipe after created the image setup environment. (Check step 7 ~9 here for setup environment.)
<pre>
bitbake -c compile -f linux-imx
</pre>

[[File:Bitbakecompile.png|frameless|600x600px|link=File:Bitbakecompile.png|Compile linux-imx with bitbake]]

3. Generate the image file by bitbake
<pre>
bitbake imx-yocto-multimedia
</pre>

[[File:Bitbakeimage.png|frameless|600x600px|link=File:Bitbakeimage.png|Generate image file with bitbake]]

In this case, we use imx-yocto-multimedia, the user can decide which kind of image they would like to generate; the detailed information is as below:

{| class="wikitable"
! Image Name !! Target
|-
| core-image-minimal || A compact image that enables the device to boot with minimal functionality.
|-
| core-image-base || A console-only image that ensures full compatibility with the target device's hardware.
|-
| core-image-sato || An image featuring the Sato mobile environment, providing a visual style and mobile applications such as a terminal, editor, and file manager. It utilizes the Sato theme and includes Pimlico applications.
|-
| imx-image-core || An i.MX-based image containing i.MX test applications, designed for Wayland backends. This image is used in daily core testing for i.MX devices.
|-
| fsl-image-machine-test || An i.MX core image from the FSL Community, providing a console-only environment with no GUI interface.
|-
| imx-image-multimedia || An i.MX image with a graphical user interface (GUI), but without any Qt content.
|-
| imx-image-full || An open-source Qt 5-based image that incorporates machine learning features. These images are designed specifically for i.MX SoCs with hardware graphics support and are incompatible with the i.MX 6UltraLite, i.MX 6UltraLiteLite, i.MX 6SLL, and i.MX7Dual models.
|}

Reference: NXP's i.MX Yocto Project User's Guide

4. Restore the image you've built to the device
Check How to install the image file by UUU. in the Recipe guide.
Use the UUU to restore image (Image restore guide).

5. After restored the image to the device, you will see the boot image when booting the device.

[[File:Bootimage.jpg|frameless|600x600px|link=File:Bootimage.jpg|Boot image on device]]

Change the boot image of the system on i.MX series devices

2025-09-04T06:18:32Z

Joec:

=Change the boot image of the system on i.MX series devices=

This article will tell you how to change the title logo / photo of the system for i.MX series device.
In standard image that ICOP provided; no matter it's Yocto Linux or Android, the title logo / photo is always the linux logo, but this can be changed by simple steps.
In the tips below, we will provide the guide step by step.

==Tools you need:==

#i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
##In this tips, we use PN8M-090T as an example.
#Yocto Linux 4.0:Recipe (Find the recipe file from our Wiki)
#Image file of your logo / photo
#Operating system for building the image: Ubuntu 22.04 or after

==1. Making a ppm image file with 224 colors==

First, prepare a custom boot image and convert it to a Linux-compatible PPM file (the image should be saved with a .ppm extension in ASCII format and have a maximum of 224 colors).
Please follow the steps below to change the image to the correct format:

1. Using pngtopnm to change the .png file to .pnm file.
<pre>
pngtopnm xxxx.png>linuxlogo.pnm
</pre>
(xxxx=your file name)

[[File:PNG2PNM.png|border|frameless|600x600px]]

2. pnmquant 224 to change the color to 224 colors
<pre>
pnmquant 224 linuxlogo.pnm>linuxlogo224.pnm
</pre>
[[File:PNM224.png|border|frameless|600x600px]]

3. pnmtoplainpnm to change the file to change the .pnm file to .ppm file.
<pre>
pnmtoplainpnm linuxlogo224.pnm>logo_linux_clut224.ppm
</pre>
[[File:PNM2PPM.png|frameless|600x600px]]

By the steps above, we can change the PNG file to 224 colors .ppm file.

==2. Replace the old boot image and build the image file==

In this case, we assume the user already know how to build a image file by recipe, and already has the recipe file.
If the recipe file is not implemented, check here for an example.

1. Copy the logo_linux_clut224.ppm to the logo file.
<pre>
cp logo_linux_clut224.ppm kernel-source/drivers/video/logo
</pre>
kernel-source/drivers/video/logo is the relative location, in this case, the exact location is:
<pre>
/home/user/imx-yocot-bsp/build-dmp/tmp/work-sahred/dm421/kernel-source/drivers/video/logo
</pre>
[[File:CPPPM2LOGO2.png|frameless|600x600px]]

The exact location will be diffrerent based on the user's setting.

2. After replaced the logo file, run bitbake command below to compile linux-imx in the recipe after created the image setup environment. (Check step 7 ~9 here for setup environment.)
<pre>
bitbake -c compile -f linux-imx
</pre>

[[File:Bitbakecompile.png|frameless|600x600px]]

3. Generate the image file by bitbake
<pre>
bitbake imx-yocto-multimedia
</pre>

[[File:Bitbakeimage.png|frameless|600x600px]]

In this case, we use imx-yocto-multimedia, the user can decide which kind of image they would like to generate; the detailed information is as below:
{| class="wikitable"
!Image Name!!Target
|-
|core-image-minimal||A compact image that enables the device to boot with minimal functionality.
|-
|core-image-base||A console-only image that ensures full compatibility with the target device's hardware.
|-
|core-image-sato||An image featuring the Sato mobile environment, providing a visual style and mobile applications such as a terminal, editor, and file manager. It utilizes the Sato theme and includes Pimlico applications.
|-
|imx-image-core||An i.MX-based image containing i.MX test applications, designed for Wayland backends. This image is used in daily core testing for i.MX devices.
|-
|fsl-image-machine-test||An i.MX core image from the FSL Community, providing a console-only environment with no GUI interface.
|-
|imx-image-multimedia||An i.MX image with a graphical user interface (GUI), but without any Qt content.
|-
|imx-image-full||An open-source Qt 5-based image that incorporates machine learning features. These images are designed specifically for i.MX SoCs with hardware graphics support and are incompatible with the i.MX 6UltraLite, i.MX 6UltraLiteLite, i.MX 6SLL, and i.MX7Dual models.
|}
Reference: NXP's i.MX Yocto Project User's Guide

4. Restore the image you've built to the device
Check How to install the image file by UUU. in the Recipe guide
Use the UUU to restore image (Image restore guide)

5. After restored the image to the device, you will see the boot image when booting the device

[[File:Bootimage.jpg|frameless|600x600px]]

Change the boot image of the system on i.MX series devices

2025-09-04T06:18:15Z

Joec:

=Change the boot image of the system on i.MX series devices=

This article will tell you how to change the title logo / photo of the system for i.MX series device.
In standard image that ICOP provided; no matter it's Yocto Linux or Android, the title logo / photo is always the linux logo, but this can be changed by simple steps.
In the tips below, we will provide the guide step by step.

==Tools you need:==

# i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
## In this tips, we use PN8M-090T as an example.
# Yocto Linux 4.0:Recipe (Find the recipe file from our Wiki)
# Image file of your logo / photo
# Operating system for building the image: Ubuntu 22.04 or after

==1. Making a ppm image file with 224 colors==

First, prepare a custom boot image and convert it to a Linux-compatible PPM file (the image should be saved with a .ppm extension in ASCII format and have a maximum of 224 colors).
Please follow the steps below to change the image to the correct format:

1. Using pngtopnm to change the .png file to .pnm file.
<pre>
pngtopnm xxxx.png > linuxlogo.pnm
</pre>
(xxxx = your file name)

[[File:PNG2PNM.png|thumb|frameless|600x600px|Convert PNG to PNM]]

2. pnmquant 224 to change the color to 224 colors
<pre>
pnmquant 224 linuxlogo.pnm > linuxlogo224.pnm
</pre>

[[File:PNM224.png|thumb|frameless|600x600px|Reduce color to 224]]

3. pnmtoplainpnm to change the file to change the .pnm file to .ppm file.
<pre>
pnmtoplainpnm linuxlogo224.pnm > logo_linux_clut224.ppm
</pre>

[[File:PNM2PPM.png|thumb|frameless|600x600px|Convert PNM to PPM]]

By the steps above, we can change the PNG file to 224 colors .ppm file.

==2. Replace the old boot image and build the image file==

In this case, we assume the user already know how to build an image file by recipe, and already has the recipe file.
If the recipe file is not implemented, check here for an example.

1. Copy the logo_linux_clut224.ppm to the logo file.
<pre>
cp logo_linux_clut224.ppm kernel-source/drivers/video/logo
</pre>
kernel-source/drivers/video/logo is the relative location, in this case, the exact location is:
<pre>
/home/user/imx-yocto-bsp/build-dmp/tmp/work-shared/dm421/kernel-source/drivers/video/logo
</pre>

[[File:CPPPM2LOGO2.png|thumb|frameless|600x600px|Copy the PPM logo to kernel source]]

The exact location will be different based on the user's setting.

2. After replaced the logo file, run bitbake command below to compile linux-imx in the recipe after created the image setup environment. (Check step 7 ~9 here for setup environment.)
<pre>
bitbake -c compile -f linux-imx
</pre>

[[File:Bitbakecompile.png|thumb|frameless|600x600px|Compile linux-imx with bitbake]]

3. Generate the image file by bitbake
<pre>
bitbake imx-yocto-multimedia
</pre>

[[File:Bitbakeimage.png|thumb|frameless|600x600px|Generate image file with bitbake]]

In this case, we use imx-yocto-multimedia, the user can decide which kind of image they would like to generate; the detailed information is as below:

{| class="wikitable"
! Image Name !! Target
|-
| core-image-minimal || A compact image that enables the device to boot with minimal functionality.
|-
| core-image-base || A console-only image that ensures full compatibility with the target device's hardware.
|-
| core-image-sato || An image featuring the Sato mobile environment, providing a visual style and mobile applications such as a terminal, editor, and file manager. It utilizes the Sato theme and includes Pimlico applications.
|-
| imx-image-core || An i.MX-based image containing i.MX test applications, designed for Wayland backends. This image is used in daily core testing for i.MX devices.
|-
| fsl-image-machine-test || An i.MX core image from the FSL Community, providing a console-only environment with no GUI interface.
|-
| imx-image-multimedia || An i.MX image with a graphical user interface (GUI), but without any Qt content.
|-
| imx-image-full || An open-source Qt 5-based image that incorporates machine learning features. These images are designed specifically for i.MX SoCs with hardware graphics support and are incompatible with the i.MX 6UltraLite, i.MX 6UltraLiteLite, i.MX 6SLL, and i.MX7Dual models.
|}

Reference: NXP's i.MX Yocto Project User's Guide

4. Restore the image you've built to the device
Check How to install the image file by UUU. in the Recipe guide.
Use the UUU to restore image (Image restore guide).

5. After restored the image to the device, you will see the boot image when booting the device.

[[File:Bootimage.jpg|thumb|frameless|600x600px|Boot image on device]]

Change the boot image of the system on i.MX series devices

2025-09-04T06:16:36Z

Joec:

=Change the boot image of the system on i.MX series devices=

This article will tell you how to change the title logo / photo of the system for i.MX series device.
In standard image that ICOP provided; no matter it's Yocto Linux or Android, the title logo / photo is always the linux logo, but this can be changed by simple steps.
In the tips below, we will provide the guide step by step.

==Tools you need:==

#i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
##In this tips, we use PN8M-090T as an example.
#Yocto Linux 4.0:Recipe (Find the recipe file from our Wiki)
#Image file of your logo / photo
#Operating system for building the image: Ubuntu 22.04 or after

==1. Making a ppm image file with 224 colors==

First, prepare a custom boot image and convert it to a Linux-compatible PPM file (the image should be saved with a .ppm extension in ASCII format and have a maximum of 224 colors).
Please follow the steps below to change the image to the correct format:

1. Using pngtopnm to change the .png file to .pnm file.
<pre>
pngtopnm xxxx.png>linuxlogo.pnm
</pre>
(xxxx=your file name)

[[File:PNG2PNM.png|border|frameless|600x600px]]

2. pnmquant 224 to change the color to 224 colors
<pre>
pnmquant 224 linuxlogo.pnm>linuxlogo224.pnm
</pre>
[[File:PNM224.png|border|frameless|600x600px]]

3. pnmtoplainpnm to change the file to change the .pnm file to .ppm file.
<pre>
pnmtoplainpnm linuxlogo224.pnm>logo_linux_clut224.ppm
</pre>
[[File:PNM2PPM.png|frameless|600x600px]]

By the steps above, we can change the PNG file to 224 colors .ppm file.

==2. Replace the old boot image and build the image file==

In this case, we assume the user already know how to build a image file by recipe, and already has the recipe file.
If the recipe file is not implemented, check here for an example.

1. Copy the logo_linux_clut224.ppm to the logo file.
<pre>
cp logo_linux_clut224.ppm kernel-source/drivers/video/logo
</pre>
kernel-source/drivers/video/logo is the relative location, in this case, the exact location is:
<pre>
/home/user/imx-yocot-bsp/build-dmp/tmp/work-sahred/dm421/kernel-source/drivers/video/logo
</pre>
[[File:CPPPM2LOGO2.png|frameless|600x600px]]

The exact location will be diffrerent based on the user's setting.

2. After replaced the logo file, run bitbake command below to compile linux-imx in the recipe after created the image setup environment. (Check step 7 ~9 here for setup environment.)
<pre>
bitbake -c compile -f linux-imx
</pre>

[[File:Bitbakecompile.png|frameless|600x600px]]

3. Generate the image file by bitbake
<pre>
bitbake imx-yocto-multimedia
</pre>

[[File:Bitbakeimage.png|frameless|600x600px]]

In this case, we use imx-yocto-multimedia, the user can decide which kind of image they would like to generate; the detailed information is as below:
{| class="wikitable"
!Image Name!!Target
|-
|core-image-minimal||A compact image that enables the device to boot with minimal functionality.
|-
|core-image-base||A console-only image that ensures full compatibility with the target device's hardware.
|-
|core-image-sato||An image featuring the Sato mobile environment, providing a visual style and mobile applications such as a terminal, editor, and file manager. It utilizes the Sato theme and includes Pimlico applications.
|-
|imx-image-core||An i.MX-based image containing i.MX test applications, designed for Wayland backends. This image is used in daily core testing for i.MX devices.
|-
|fsl-image-machine-test||An i.MX core image from the FSL Community, providing a console-only environment with no GUI interface.
|-
|imx-image-multimedia||An i.MX image with a graphical user interface (GUI), but without any Qt content.
|-
|imx-image-full||An open-source Qt 5-based image that incorporates machine learning features. These images are designed specifically for i.MX SoCs with hardware graphics support and are incompatible with the i.MX 6UltraLite, i.MX 6UltraLiteLite, i.MX 6SLL, and i.MX7Dual models.
|}
Reference: NXP's i.MX Yocto Project User's Guide

4. Restore the image you've built to the device
Check How to install the image file by UUU. in the Recipe guide
Use the UUU to restore image (Image restore guide)

5. After restored the image to the device, you will see the boot image when booting the device

[[File:Bootimage.jpg|frameless|600x600px]]

File:Bootimage.jpg

2025-09-04T06:16:25Z

Joec:

Bootimage

File:Bitbakeimage.png

2025-09-04T06:16:03Z

Joec:

Bitbakeimage

File:Bitbakecompile.png

2025-09-04T06:15:23Z

Joec:

Bitbakecompile

File:CPPPM2LOGO2.png

2025-09-04T06:14:55Z

Joec:

CPPPM2LOGO2

File:PNM2PPM.png

2025-09-04T06:14:24Z

Joec:

PNM2PPM

File:PNM224.png

2025-09-04T06:13:49Z

Joec:

PNM224

File:PNG2PNM.png

2025-09-04T06:13:03Z

Joec:

PNG2PNM

Change the boot image of the system on i.MX series devices

2025-09-04T06:07:55Z

Joec:

=Change the boot image of the system on i.MX series devices=

This article will tell you how to change the title logo / photo of the system for i.MX series device.
In standard image that ICOP provided; no matter it's Yocto Linux or Android, the title logo / photo is always the linux logo, but this can be changed by simple steps.
In the tips below, we will provide the guide step by step.

==Tools you need:==

#i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
##In this tips, we use PN8M-090T as an example.
#Yocto Linux 4.0:Recipe (Find the recipe file from our Wiki)
#Image file of your logo / photo
#Operating system for building the image: Ubuntu 22.04 or after

==1. Making a ppm image file with 224 colors==

First, prepare a custom boot image and convert it to a Linux-compatible PPM file (the image should be saved with a .ppm extension in ASCII format and have a maximum of 224 colors).
Please follow the steps below to change the image to the correct format:

1. Using pngtopnm to change the .png file to .pnm file.
<pre>
pngtopnm xxxx.png>linuxlogo.pnm
</pre>
(xxxx=your file name)
2. pnmquant 224 to change the color to 224 colors
<pre>
pnmquant 224 linuxlogo.pnm>linuxlogo224.pnm
</pre>
3. pnmtoplainpnm to change the file to change the .pnm file to .ppm file.
<pre>
pnmtoplainpnm linuxlogo224.pnm>logo_linux_clut224.ppm
</pre>
By the steps above, we can change the PNG file to 224 colors .ppm file.

==2. Replace the old boot image and build the image file==

In this case, we assume the user already know how to build a image file by recipe, and already has the recipe file.
If the recipe file is not implemented, check here for an example.

1. Copy the logo_linux_clut224.ppm to the logo file.
<pre>
cp logo_linux_clut224.ppm kernel-source/drivers/video/logo
</pre>
kernel-source/drivers/video/logo is the relative location, in this case, the exact location is:
<pre>
/home/user/imx-yocot-bsp/build-dmp/tmp/work-sahred/dm421/kernel-source/drivers/video/logo
</pre>
The exact location will be diffrerent based on the user's setting.

2. After replaced the logo file, run bitbake command below to compile linux-imx in the recipe after created the image setup environment. (Check step 7 ~9 here for setup environment.)
<pre>
bitbake -c compile -f linux-imx
</pre>

3. Generate the image file by bitbake
<pre>
bitbake imx-yocto-multimedia
</pre>

In this case, we use imx-yocto-multimedia, the user can decide which kind of image they would like to generate; the detailed information is as below:
{| class="wikitable"
! Image Name !! Target
|-
| core-image-minimal || A compact image that enables the device to boot with minimal functionality.
|-
| core-image-base || A console-only image that ensures full compatibility with the target device's hardware.
|-
| core-image-sato || An image featuring the Sato mobile environment, providing a visual style and mobile applications such as a terminal, editor, and file manager. It utilizes the Sato theme and includes Pimlico applications.
|-
| imx-image-core || An i.MX-based image containing i.MX test applications, designed for Wayland backends. This image is used in daily core testing for i.MX devices.
|-
| fsl-image-machine-test || An i.MX core image from the FSL Community, providing a console-only environment with no GUI interface.
|-
| imx-image-multimedia || An i.MX image with a graphical user interface (GUI), but without any Qt content.
|-
| imx-image-full || An open-source Qt 5-based image that incorporates machine learning features. These images are designed specifically for i.MX SoCs with hardware graphics support and are incompatible with the i.MX 6UltraLite, i.MX 6UltraLiteLite, i.MX 6SLL, and i.MX7Dual models.
|}
Reference: NXP's i.MX Yocto Project User's Guide

4. Restore the image you've built to the device
Check How to install the image file by UUU. in the Recipe guide
Use the UUU to restore image (Image restore guide)

5. After restored the image to the device, you will see the boot image when booting the device

Change the boot image of the system on i.MX series devices

2025-09-04T06:00:52Z

Joec: Created page with "=Change the boot image of the system on i.MX series devices= This article will tell you how to change the title logo / photo of the system for i.MX series device. In standard..."

=Change the boot image of the system on i.MX series devices=

This article will tell you how to change the title logo / photo of the system for i.MX series device.
In standard image that ICOP provided; no matter it's Yocto Linux or Android, the title logo / photo is always the linux logo, but this can be changed by simple steps.
In the tips below, we will provide the guide step by step.

==Tools you need:==

#i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
##In this tips, we use PN8M-090T as an example.
#Yocto Linux 4.0:Recipe (Find the recipe file from our Wiki)
#Image file of your logo / photo
#Operating system for building the image: Ubuntu 22.04 or after

==Making a ppm image file with 224 colors==

First, prepare a custom boot image and convert it to a Linux-compatible PPM file (the image should be saved with a .ppm extension in ASCII format and have a maximum of 224 colors).
Please follow the steps below to change the image to the correct format:

#Using pngtopnm to change the .png file to .pnm file.
<pre>
pngtopnm xxxx.png>linuxlogo.pnm
</pre>
(xxxx=your file name)
#pnmquant 224 to change the color to 224 colors
<pre>
pnmquant 224 linuxlogo.pnm>linuxlogo224.pnm
</pre>
#pnmtoplainpnm to change the file to change the .pnm file to .ppm file.
==Tools you need:==

#i.MX series products like [https://www.icop.com.tw/product/NX8MM-35 NX8MM-35] / [https://www.icop.com.tw/product/PN8M-090T-8A PN8M-090T] / [https://www.icop.com.tw/product/EBOX-IMX8MM EBOX-IMX8MM]
#*In this tips, we use NX8MM-35 as an example.
#Yocto Linux 4.0 sample image with libmodbus: [[How to Restore Yocto Linux 4.0 to the eMMC on NX8MM-35|Image / Guide]]
#*In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
#Modbus test tool sample code file: [https://ftp.icop.com.tw/share/3OlMT72K Download link]
#NX8MM-35 with the test fixture connectoing 2xRS485.

[[File:NX8MM-35485485.png|frameless]]

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

[[File:Step1-1gcc modbus.png|frameless]]

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
[[File:Step1-2 cdmodbus.png|frameless]]

Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

[[File:NX8MM-35485485.png|frameless]]

2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
[[File:Step2-1 modbusserver.png|frameless]]

2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
[[File:Step2-2 modbusclient.png|frameless]]

After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

[[File:Step2-3complete.png|frameless]]

Developers Guide-YOCTO

2025-08-29T08:38:00Z

Joec:

<table style="padding:15px; background-color: #0055a5; color: white; width:100%; font-size:25px; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Developers Guide
</td></tr></table>

<table style="background-color: #F0F0FF; width:100%;">
<tr>
<td style="width:250px; padding:5px 25px 5px 25px;">
[[File:Yocto.png|frameless|标题|連結=Special:FilePath/Yocto.png]]
</td>
<td style="padding:20px 30px 0px 0px; vertical-align:top; font-size:22px;">
=='''<big>Yocto Project</big>'''==
Yocto project is a framework for creating a Linux distributions for embedded devices. It's layering mechanism makes it easy to add Linux to new target devices highly customized for a particular platform; it can include custom start-up scripts, software packages built with a high degree of optimization for a particular architecture, and different user interfaces from full Gnome desktop to a simple a serial console.

This release is based on [https://source.codeaurora.org/external/imx NXP BSP] layer for Yocto framework.
<br /></td></tr></table>
<div style="overflow:hidden; padding-top:20px; min-width:1000px; margin-top:-33px;">
<div style="width:100%;">
<p></p><p><br />
</p>

<div style="width:48%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table><table style="padding:10px; background-color: #4f9df2; color: white; font-size:19px; width:100%; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Test and Use
</td></tr></table>

<table style="background-color: #d7e4f2; width:100%; height:740px;">
<tr>
<td></td>
<td style="padding-left: 4%; padding-right: 4%; vertical-align:top; max-width:100%;"><b><big>Test and use an Interface</big></b><div style="width:100%;"><div style="width:50%; float: left;"><ul><li><big>[[PN8M-090T-Bluetooth A2DP|Bluetooth A2DP]]</big></li><li><big>[[PN8M-090T-Ethernet|Ethernet]]</big></li><li><big>[[PN8M-090T-UART|UART]]</big></li><li><big>[[PN8M-090T-WiFi|WiFi]]</big></li><li><big>[[PN8M-090T-SPK-OUT|SPK-OUT]]</big></li></ul></div>
</td></tr>
<tr>
<td></td>
</tr></table>

</div>

<div style="width:47%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table><table style="padding:10px; background-color: #4f9df2; color: white; font-size:19px; width:100%; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Techni<span class="plainlinks"></span>cal Resource
</td></tr></table>
<table style="background-color: #d7e4f2; width:100%; height:740px;">

<tr>
<td></td>
<td style="padding-left: 4%; padding-right: 4%; vertical-align:top; max-width:100%;"><ul>
<li> [[Recipe for building Yocto Linux for PN8M-090T|<big>Recipe for building Yocto Linux for PN8M-090T</big>]]
</li>
<li> <big>[[Recovery the Yocto in the eMMC under UBOOT mode-PN9M-090T|Recovery the Yocto in the eMMC under UBOOT mode]]</big>
</li>
<li> <big>[[How to set up time zone in Yocto-PN8M-090T|How to set up time zone in Yocto]]</big>
</li>
<li> <big>[[How to check storages contents in Yocto-PN8M-090T|How to check storages contents in Yocto]]</big>
</li>
<li> [[Resovling Terminal frozen after closing chromium--no--sandbox|<big></big>]]<big>[[Chromium--no-sandbox-PN8M-090T|Resovling Terminal frozen after closing chromium--no--sandbox]]</big>
</li>
<li> [[Resovling Terminal frozen after closing chromium--no--sandbox|<big></big>]]<big>[[Chromium-Youtube-soundcutting-PN8M-090T|Resovling cutting sound in Chromium&Youtube]]</big>
</li>
<li> [[Resovling Terminal frozen after closing chromium--no--sandbox|<big></big>]]<big>[[PCI7600G LTE module setting|PCI7600G MINI PCI-E 4G Module driver setting]]</big>
</li>
</ul><ul>
<li><big>[[Run a modbus RTU example on NX8MM-35]]</big>
</li>
</ul>
</td></tr>
<tr>
<td></td>
<td style="padding:0px 10px 10px 0px; height:100px;"><div class="floatright"></div>
</td></tr></table>

</div>

<div style="width:45%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table>

Run a modbus RTU example on NX8MM-35

2025-08-29T08:36:36Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.

We used [https://libmodbus.org/ libmodbus] to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==

#Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
#Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
#Multiple Communication Modes:
##Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
##Modbus ASCII: Uses human-readable ASCII characters for serial communication.
##Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

==Common Uses of Modbus:==

Monitoring and control of industrial equipment.

SCADA (Supervisory Control and Data Acquisition) systems.

Energy meters, temperature sensors, and other field devices

==Tools you need:==

#i.MX series products like [https://www.icop.com.tw/product/NX8MM-35 NX8MM-35] / [https://www.icop.com.tw/product/PN8M-090T-8A PN8M-090T] / [https://www.icop.com.tw/product/EBOX-IMX8MM EBOX-IMX8MM]
#*In this tips, we use NX8MM-35 as an example.
#Yocto Linux 4.0 sample image with libmodbus: [[How to Restore Yocto Linux 4.0 to the eMMC on NX8MM-35|Image / Guide]]
#*In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
#Modbus test tool sample code file: [https://ftp.icop.com.tw/share/3OlMT72K Download link]
#NX8MM-35 with the test fixture connectoing 2xRS485.

[[File:NX8MM-35485485.png|frameless]]

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

[[File:Step1-1gcc modbus.png|frameless]]

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
[[File:Step1-2 cdmodbus.png|frameless]]

Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

[[File:NX8MM-35485485.png|frameless]]

2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
[[File:Step2-1 modbusserver.png|frameless]]

2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
[[File:Step2-2 modbusclient.png|frameless]]

After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

[[File:Step2-3complete.png|frameless]]

Run a modbus RTU example on NX8MM-35

2025-08-29T08:36:14Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.

We used [https://libmodbus.org/ libmodbus] to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==

#Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
#Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
#Multiple Communication Modes:
##Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
##Modbus ASCII: Uses human-readable ASCII characters for serial communication.
##Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

==Common Uses of Modbus:==

Monitoring and control of industrial equipment.

SCADA (Supervisory Control and Data Acquisition) systems.

Energy meters, temperature sensors, and other field devices

==Tools you need:==

#i.MX series products like [https://www.icop.com.tw/product/NX8MM-35 NX8MM-35] / [https://www.icop.com.tw/product/PN8M-090T-8A PN8M-090T] / [https://www.icop.com.tw/product/EBOX-IMX8MM EBOX-IMX8MM]
#*In this tips, we use NX8MM-35 as an example.
#Yocto Linux 4.0 sample image with libmodbus: [[How to Restore Yocto Linux 4.0 to the eMMC on NX8MM-35|Image / Guide]]
#*In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
#Modbus test tool sample code file: [https://ftp.icop.com.tw/share/3OlMT72K Download link]
#NX8MM-35 with the test fixture connectoing 2xRS485.

[[File:NX8MM-35485485.png|frameless]]

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

[[File:Step1-1gcc modbus.png|frameless]]

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
[[File:Step1-2 cdmodbus.png|frameless]]

Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

[[File:NX8MM-35485485.png|frameless]]
2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
[[File:Step2-1 modbusserver.png|frameless]]

2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
[[File:Step2-2 modbusclient.png|frameless]]

After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

[[File:Step2-3complete.png|frameless]]

Run a modbus RTU example on NX8MM-35

2025-08-29T08:36:03Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.

We used [https://libmodbus.org/ libmodbus] to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==

#Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
#Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
#Multiple Communication Modes:
##Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
##Modbus ASCII: Uses human-readable ASCII characters for serial communication.
##Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

==Common Uses of Modbus:==

Monitoring and control of industrial equipment.

SCADA (Supervisory Control and Data Acquisition) systems.

Energy meters, temperature sensors, and other field devices

==Tools you need:==

#i.MX series products like [https://www.icop.com.tw/product/NX8MM-35 NX8MM-35] / [https://www.icop.com.tw/product/PN8M-090T-8A PN8M-090T] / [https://www.icop.com.tw/product/EBOX-IMX8MM EBOX-IMX8MM]
#*In this tips, we use NX8MM-35 as an example.
#Yocto Linux 4.0 sample image with libmodbus: [[How to Restore Yocto Linux 4.0 to the eMMC on NX8MM-35|Image / Guide]]
#*In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
#Modbus test tool sample code file: [https://ftp.icop.com.tw/share/3OlMT72K Download link]
#NX8MM-35 with the test fixture connectoing 2xRS485. [[File:NX8MM-35485485.png|frameless]]

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

[[File:Step1-1gcc modbus.png|frameless]]

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
[[File:Step1-2 cdmodbus.png|frameless]]

Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

[[File:NX8MM-35485485.png|frameless]]
2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
[[File:Step2-1 modbusserver.png|frameless]]

2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
[[File:Step2-2 modbusclient.png|frameless]]

After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

[[File:Step2-3complete.png|frameless]]

Run a modbus RTU example on NX8MM-35

2025-08-29T08:35:20Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.

We used [https://libmodbus.org/ libmodbus] to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==

#Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
#Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
#Multiple Communication Modes:
##Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
##Modbus ASCII: Uses human-readable ASCII characters for serial communication.
##Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

==Common Uses of Modbus:==

Monitoring and control of industrial equipment.

SCADA (Supervisory Control and Data Acquisition) systems.

Energy meters, temperature sensors, and other field devices

==Tools you need:==

#i.MX series products like [https://www.icop.com.tw/product/NX8MM-35 NX8MM-35] / [https://www.icop.com.tw/product/PN8M-090T-8A PN8M-090T] / [https://www.icop.com.tw/product/EBOX-IMX8MM EBOX-IMX8MM]
#*In this tips, we use NX8MM-35 as an example.
#Yocto Linux 4.0 sample image with libmodbus: [[How to Restore Yocto Linux 4.0 to the eMMC on NX8MM-35|Image / Guide]]
#*In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
#Modbus test tool sample code file: [https://ftp.icop.com.tw/share/3OlMT72K Download link]
#NX8MM-35 with the test fixture connectoing 2xRS485 [[File:NX8MM-35485485.png|alt=|frameless]]

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

[[File:Step1-1gcc modbus.png|frameless]]

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
[[File:Step1-2 cdmodbus.png|frameless]]

Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

[[File:NX8MM-35485485.png|frameless]]
2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
[[File:Step2-1 modbusserver.png|frameless]]

2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
[[File:Step2-2 modbusclient.png|frameless]]

After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

[[File:Step2-3complete.png|frameless]]

Run a modbus RTU example on NX8MM-35

2025-08-29T08:34:58Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.

We used [https://libmodbus.org/ libmodbus] to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==

#Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
#Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
#Multiple Communication Modes:
##Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
##Modbus ASCII: Uses human-readable ASCII characters for serial communication.
##Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

==Common Uses of Modbus:==

Monitoring and control of industrial equipment.

SCADA (Supervisory Control and Data Acquisition) systems.

Energy meters, temperature sensors, and other field devices

==Tools you need:==

#i.MX series products like [https://www.icop.com.tw/product/NX8MM-35 NX8MM-35] / [https://www.icop.com.tw/product/PN8M-090T-8A PN8M-090T] / [https://www.icop.com.tw/product/EBOX-IMX8MM EBOX-IMX8MM]
#*In this tips, we use NX8MM-35 as an example.
#Yocto Linux 4.0 sample image with libmodbus: [[How to Restore Yocto Linux 4.0 to the eMMC on NX8MM-35|Image / Guide]]
#*In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
#Modbus test tool sample code file: [https://ftp.icop.com.tw/share/3OlMT72K Download link]
#NX8MM-35 with the test fixture connectoing 2xRS485[[File:NX8MM-35485485.png|left|frameless]]<br />

<br />

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

[[File:Step1-1gcc modbus.png|frameless]]

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
[[File:Step1-2 cdmodbus.png|frameless]]

Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

[[File:NX8MM-35485485.png|frameless]]
2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
[[File:Step2-1 modbusserver.png|frameless]]

2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
[[File:Step2-2 modbusclient.png|frameless]]

After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

[[File:Step2-3complete.png|frameless]]

File:Step2-3complete.png

2025-08-29T08:34:15Z

Joec:

File:Step2-2 modbusclient.png

2025-08-29T08:33:35Z

Joec:

File:Step2-1 modbusserver.png

2025-08-29T08:32:52Z

Joec:

File:Step1-2 cdmodbus.png

2025-08-29T08:31:47Z

Joec:

File:NX8MM-35485485.png

2025-08-29T08:29:53Z

Joec:

Run a modbus RTU example on NX8MM-35

2025-08-29T08:29:16Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.

We used [https://libmodbus.org/ libmodbus] to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==

#Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
#Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
#Multiple Communication Modes:
##Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
##Modbus ASCII: Uses human-readable ASCII characters for serial communication.
##Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

==Common Uses of Modbus:==

Monitoring and control of industrial equipment.

SCADA (Supervisory Control and Data Acquisition) systems.

Energy meters, temperature sensors, and other field devices

==Tools you need:==

#i.MX series products like [https://www.icop.com.tw/product/NX8MM-35 NX8MM-35] / [https://www.icop.com.tw/product/PN8M-090T-8A PN8M-090T] / [https://www.icop.com.tw/product/EBOX-IMX8MM EBOX-IMX8MM]
#*In this tips, we use NX8MM-35 as an example.
#Yocto Linux 4.0 sample image with libmodbus: [[How to Restore Yocto Linux 4.0 to the eMMC on NX8MM-35|Image / Guide]]
#*In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
#Modbus test tool sample code file: [https://ftp.icop.com.tw/share/3OlMT72K Download link]
#NX8MM-35 with the test fixture connectoing 2xRS485

<br />

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

Run a modbus RTU example on NX8MM-35

2025-08-29T08:26:34Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.

We used libmodbus to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==

#Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
#Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
#Multiple Communication Modes:
##Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
##Modbus ASCII: Uses human-readable ASCII characters for serial communication.
##Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

==Common Uses of Modbus:==

Monitoring and control of industrial equipment.

SCADA (Supervisory Control and Data Acquisition) systems.

Energy meters, temperature sensors, and other field devices

==Tools you need:==

# i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
#* In this tips, we use NX8MM-35 as an example.
# Yocto Linux 4.0 sample image with libmodbus: Image / Guide
#* In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
# Modbus test tool sample code file: Download link
# NX8MM-35 with the test fixture connectoing 2xRS485

<br />

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

Run a modbus RTU example on NX8MM-35

2025-08-29T08:25:03Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.

We used libmodbus to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==

#Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
#Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
#Multiple Communication Modes:
##Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
##Modbus ASCII: Uses human-readable ASCII characters for serial communication.
##Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

==Common Uses of Modbus:==

Monitoring and control of industrial equipment.

SCADA (Supervisory Control and Data Acquisition) systems.

Energy meters, temperature sensors, and other field devices

==Tools you need:==

i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
In this tips, we use NX8MM-35 as an example.

Yocto Linux 4.0 sample image with libmodbus: Image / Guide

In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.

Modbus test tool sample code file: Download link

NX8MM-35 with the test fixture connectoing 2xRS485

<br />

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

Run a modbus RTU example on NX8MM-35

2025-08-29T08:24:29Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.

We used libmodbus to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==

# Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
# Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
# Multiple Communication Modes:
## Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
## Modbus ASCII: Uses human-readable ASCII characters for serial communication.
## Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

==Common Uses of Modbus:==

Monitoring and control of industrial equipment.

SCADA (Supervisory Control and Data Acquisition) systems.

Energy meters, temperature sensors, and other field devices

==Tools you need:==

i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
In this tips, we use NX8MM-35 as an example.
Yocto Linux 4.0 sample image with libmodbus: Image / Guide
In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
Modbus test tool sample code file: Download link
NX8MM-35 with the test fixture connectoing 2xRS485

<br />

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

Run a modbus RTU example on NX8MM-35

2025-08-29T08:24:16Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.

We used libmodbus to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==

# Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
# Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
# Multiple Communication Modes:
## Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
## Modbus ASCII: Uses human-readable ASCII characters for serial communication.
## Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

Common Uses of Modbus:

Monitoring and control of industrial equipment.

SCADA (Supervisory Control and Data Acquisition) systems.

Energy meters, temperature sensors, and other field devices

==Tools you need:==

i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
In this tips, we use NX8MM-35 as an example.
Yocto Linux 4.0 sample image with libmodbus: Image / Guide
In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
Modbus test tool sample code file: Download link
NX8MM-35 with the test fixture connectoing 2xRS485

<br />

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

File:Step1-1gcc modbus.png

2025-08-29T08:20:07Z

Joec:

Run a modbus RTU example on NX8MM-35

2025-08-29T08:17:15Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.
We used libmodbus to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==
Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
Multiple Communication Modes:
Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
Modbus ASCII: Uses human-readable ASCII characters for serial communication.
Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

Common Uses of Modbus:
Monitoring and control of industrial equipment.
SCADA (Supervisory Control and Data Acquisition) systems.
Energy meters, temperature sensors, and other field devices

==Tools you need:==

i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
In this tips, we use NX8MM-35 as an example.
Yocto Linux 4.0 sample image with libmodbus: Image / Guide
In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
Modbus test tool sample code file: Download link
NX8MM-35 with the test fixture connectoing 2xRS485

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

1.1 Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

1.2 Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

2. Start to perform Modbus RTU testing on NX8MM-35

2.1 Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
2.2 Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

Run a modbus RTU example on NX8MM-35

2025-08-29T08:16:14Z

Joec:

=Run a modbus RTU example on NX8MM-35=

This article will tell you how to run a modbus RTU example on NX8MM-35.
We used libmodbus to utilize the modbus function via 2x RS485 (1 modbus server & 1 modbus client on the same SBC) on NX8MM-35 under Yocto in this tips.

==Key Features of Modbus:==
Master-Slave (Client-Server) Architecture: A master (client) device initiates communication, while slave (server) devices respond.
Simple and Open Protocol: Easy to implement and widely supported in industrial systems.
Multiple Communication Modes:
Modbus RTU (Remote Terminal Unit): Uses binary data format over serial communication (RS-232, RS-485).
Modbus ASCII: Uses human-readable ASCII characters for serial communication.
Modbus TCP/IP: Runs over Ethernet, allowing faster and more flexible networking.

Common Uses of Modbus:
Monitoring and control of industrial equipment.
SCADA (Supervisory Control and Data Acquisition) systems.
Energy meters, temperature sensors, and other field devices

==Tools you need:==

i.MX series products like NX8MM-35 / PN8M-090T / EBOX-IMX8MM
In this tips, we use NX8MM-35 as an example.
Yocto Linux 4.0 sample image with libmodbus: Image / Guide
In the default recipe, you will need to add "libmodbus-dev" to IMAGE_INSTALL:append in local.conf before you build your own image.
Modbus test tool sample code file: Download link
NX8MM-35 with the test fixture connectoing 2xRS485

==Procedure:==
1. Boot up the board and compile the modbus test tool
First, boot up the board, and plug in a USB disk which contains the modbus test tool sample code file and open the terminal.

Access the USB disk and input the code below:
<pre>
$ gcc modbus_test_v2.c -o modbus_test_v2 -lmodbus
</pre>

Move the compiled application to the your appointed file in the system and access it (In this case, we make a file called modbustest.)
<pre>
$ mv modbus_test_v2 /modbustest
$ cd /modbustest
</pre>
Use the command below to check the function description:
<pre>
$ /.modbus_test_v2

Usage: ./modbus_test_v2 [-s|-c] [-r gpio_index] serial_port
-s : server
-c : client
-r : rts-gpios : dm446c rts-gpios numbers: ttymxc0=128, ttymxc3=9
</pre>
We use COM1 (ttymxc0/GPIO128) and COM4 (ttymxc3/GPIO9) on the NX8MM-35 for RS-485 communication, performing point-to-point Modbus RTU testing between the two ports.
(Be sure to short J39 to switch the COM port to RS485 mode.)

2. Start to perform Modbus RTU testing on NX8MM-35
Open another terminal and input command below to set COM4 to server mode:
<pre>
./modbus_test_v2 -s -r 9 /dev/ttymxc3
</pre>
Use the existing terminal to set COM1 to client mode and send the signal to server(COM4)
<pre>
./modbus_test_v2 -c -r 128 /dev/ttymxc0
</pre>
After executing the command above, the server (COM4) successfully receives the Modbus RTU signal from the client (COM1), marking the completion of the test.

Run a modbus RTU example on NX8MM-35

2025-08-29T08:11:55Z

Joec:

Run a modbus RTU example on NX8MM-35

2025-08-29T08:11:09Z

Joec: Created blank page

Main Page

2025-07-16T08:32:02Z

Joec:

==NXP Series==
<table class="wikitable" style="width: 100%; height: auto; border-color: #ffffff">
<tr>
<td colspan="4" style="background-color:#105aa2; color:white; font-weight:bold">
<p style="text-align: center;"><b>Hardware Device</b></p>
</td>
</tr>
<tr style="vertical-align: top;text-align:center">
<td style="width: 25%;">[[File:Imx8-168.png|alt=|center|frameless|100x100px|link=[[NX8MMINI-D168]]]]<br><b><big>[[NX8MMINI-D168]]</big></b></td>
<td style="width: 25%;">[[File:IMx8M_front_2.jpg|alt=|center|frameless|100x100px|link=[[EBOX-IMX8MM]]]]<br><b><big>[[EBOX-IMX8MM|EBOX-IMX8MM]]</big></b></td>
<td style="width: 25%;">[[File:PN8M090T-3.png|alt=|center|frameless|108x108px|link=[[IMX8MMINI-PPC]]]]<br><b>[[IMX8MMINI-PPC|<big>PN8M-090T</big>]]</b></td>
<td style="width: 25%;">[[File:Nx8mm-35 front homer1.png|alt=|center|frameless|86x86px|link=[[NX8MM-35]]]]<br><b><big>[[NX8MM-35]]</big></b></td>
</tr>
</table>

<p><br /></p>
<table class="wikitable" style="width: 100%; height: auto; border-color: #ffffff">
<tr>
<td colspan="4" style="background-color:#105aa2; color:white; font-weight:bold">
<p style="text-align: center;"><b>Hardware Device</b></p>
</td>
</tr>
<tr style="vertical-align: top;text-align:center">
<td style="width: 25%;">[[File:NX8MP-SMARC.png|alt=|center|frameless|120x120px|link=[[NX8MP-SMARC]]]]<br><b><big>[[NX8MP-SMARC]]</big></b></td>
<td style="width: 25%;">[[File:IBPC-NX8MP.png|alt=|center|frameless|108x108px]]<br><b><big>IBPC-NX8MP</big></b></td>
<td style="width: 25%;">[[File:PN8M090T-3.png|alt=|center|frameless|108x108px]]<br><b><big>PN8MP-090T</big></b></td>
<td style="width: 25%;">[[File:Nx8mm-35 front homer1.png|alt=|center|frameless|86x86px]]<br><b><big>NX8MP-SBC</big></b></td>
</tr>
</table>

<p><br /></p>
==Vortex86 Series==

{| class="wikitable" style="width:100%; text-align:center; border:1px solid black; border-collapse:collapse;"

! colspan="1" style="background-color:#105aa2; color:white; font-weight:bold;" |Hardware Device
! colspan="3" style="background-color:#105aa2; color:white; font-weight:bold;" ! |Software Support
|-
| style="width: 40%" |[[Vortex86DX]]|| style="width: 20%" |[[Vortex86DX: Windows|Windows]]|| style="width: 20%" |[[Vortex86DX: Linux|Linux]]|| style="width: 20%" |[[Vortex86DX: DOS|DOS]]
|-
|[[Vortex86DX2]]||[[Vortex86DX2: Windows|Windows]]||[[Vortex86DX2: Linux|Linux]]||[[Vortex86DX2: DOS|DOS]]
|-
|[[Vortex86DX3]]||[[Vortex86DX3: Windows|Windows]]||[[Vortex86DX3: Linux|Linux]]||[[Vortex86DX3: DOS|DOS]]
|-
|[[Vortex86EX]]||[[Vortex86EX: Windows|Windows]]||[[Vortex86EX: Linux|Linux]]||[[Vortex86EX: DOS|DOS]]
|-
|[[Vortex86EX2]]||[[Vortex86EX2: Windows|Windows]]||[[Vortex86EX2: Linux|Linux]]||[[Vortex86EX2: DOS|DOS]]
|}

==Vortex86DX3 Series==
{| class="wikitable" style="width:100%; text-align:center; border:0px solid black; border-collapse:collapse;"

! colspan="3" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |System on module
|-
! style="width:10%;background-color:white;" |[[File:SOM304D3.png|alt=|center|frameless|70x70px|link=[[SOM304D3]]]]<br>'''SOM304D3'''
! style="width:10%;background-color:white;" |[[File:VDX3-ETX.png|alt=|center|frameless|70x70px|link=[[VDX3-ETX-V2]]]]<br>'''VDX3-ETX-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-Q7.png|alt=|center|frameless|70x70px|link=[[VDX3-Q7]]]]<br>'''VDX3-Q7'''
|-
! colspan="7" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |Embbedded Board
|-
! style="width:10%;background-color:white;" |[[File:VDX3-6754S-V2.png|alt=|center|frameless|70x70px|link=[[VDX3-6754S-V2]]]]<br>'''VDX3-6754S-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-6754-V2.png|alt=|center|frameless|70x70px|link=[[VDX3-6754-V2]]]]<br>'''VDX3-6754-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-6755.png|alt=|center|frameless|70x70px|link=[[VDX3-6755]]]]<br>'''VDX3-6755'''
! style="width:10%;background-color:white;" |[[File:VDX3-6726.png|alt=|center|frameless|70x70px|link=[[VDX3-6726-V2]]]]<br>'''VDX3-6726-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-PCI.png|alt=|center|frameless|70x70px|link=[[VDX3-PCI]]]]<br>'''VDX3-PCI'''
! style="width:10%;background-color:white;" |[[File:VDX3-6724.png|alt=|center|frameless|70x70px|link=[[VDX3-6724-V2]]]]<br>'''VDX3-6724-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-EITX.png|alt=|center|frameless|70x70px|link=[[VDX3-EITX]]]]<br>'''VDX3-EITX'''
|-
! colspan="6" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |EBOX-3350/EBOX-3352
|-
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3-RCA.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3-RCA]]]]<br>'''EBOX-335xDX3-RCA'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3 w Wide Temperature.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/Wide Temperature]]]]<br>'''EBOX-335xDX3<br>w/Wide Temperature'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3 w Wide Temperature.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/1G LAN]]]]<br>'''EBOX-335xDX3<br>w/1G LAN'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3]]]]<br>'''EBOX-335xDX3'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/1G LAN & Wide Temperature]]]]<br>'''EBOX-335xDX3<br>w/1G LAN & Wide Temperature'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3 wRS232 x2.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/RS232 x2]]]]<br>'''EBOX-335xDX3 w/RS232 x2'''
|-
! colspan="8" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |EBOX-3360/EBOX-3362
|-
! style="width:10%;background-color:white;" |[[File:EB-336x w HDMI EB-336x w8-bit GPIO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/HDMI]]]]<br>'''EB-336x w/HDMI'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS232 EB-336x w 4G LTE EB-336x w RS422.png|alt=|center|frameless|70x70px|link=[[EB-336x w/4G LTE]]]]<br>'''EB-336x w/4G LTE'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS232 EB-336x w 4G LTE EB-336x w RS422.png|alt=|center|frameless|70x70px|link=[[EB-336x w/RS232]]]]<br>'''EB-336x w/RS232'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS485.png|alt=|center|frameless|70x70px|link=[[EB-336x w/RS485]]]]<br>'''EB-336x w/RS485'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS232 EB-336x w 4G LTE EB-336x w RS422.png|alt=|center|frameless|70x70px|link=[[EB-336x w/RS422]]]]<br>'''EB-336x w/RS422'''
! style="width:10%;background-color:white;" |[[File:EB-336x w HDMI EB-336x w8-bit GPIO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/8-bit GPIO]]]]<br>'''EB-336x w/8-bit GPIO'''
! style="width:10%;background-color:white;" |[[File:EB-336x w Legacy IO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/Multi LAN]]]]<br>'''EB-336x w/Multi LAN'''
! style="width:10%;background-color:white;" |[[File:EB-336x w Legacy IO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/Legacy I/O]]]]<br>'''EB-336x w/Legacy I/O'''
|}

Main Page

2025-07-16T08:20:20Z

Joec:

==NXP Series==
<table class="wikitable" style="width: 100%; height: auto; border-color: #ffffff">
<tr>
<td colspan="4" style="background-color:#105aa2; color:white; font-weight:bold">
<p style="text-align: center;"><b>Hardware Device</b></p>
</td>
</tr>
<tr style="vertical-align: top;text-align:center">
<td style="width: 25%;">[[File:Imx8-168.png|alt=|center|frameless|100x100px|link=[[NX8MMINI-D168]]]]<br><b><big>[[NX8MMINI-D168]]</big></b></td>
<td style="width: 25%;">[[File:IMx8M_front_2.jpg|alt=|center|frameless|100x100px|link=[[EBOX-IMX8MM]]]]<br><b><big>[[EBOX-IMX8MM|EBOX-IMX8MM]]</big></b></td>
<td style="width: 25%;">[[File:PN8M090T-3.png|alt=|center|frameless|108x108px|link=[[IMX8MMINI-PPC]]]]<br><b>[[IMX8MMINI-PPC|<big>PN8M-090T</big>]]</b></td>
<td style="width: 25%;">[[File:Nx8mm-35 front homer1.png|alt=|center|frameless|86x86px|link=[[NX8MM-35]]]]<br><b><big>[[NX8MM-35]]</big></b></td>
</tr>
</table>

<p><br /></p>
<table class="wikitable" style="width: 100%; height: auto; border-color: #ffffff">
<tr>
<td colspan="4" style="background-color:#105aa2; color:white; font-weight:bold">
<p style="text-align: center;"><b>Hardware Device</b></p>
</td>
</tr>
<tr style="vertical-align: top;text-align:center">
<td style="width: 25%;">[[File:NX8MP-SMARC.png|alt=|center|frameless|120x120px|link=[[NX8MP-SMARC]]]]<br><b><big>[[NX8MP-SMARC]]</big></b></td>
<td style="width: 25%;">[[File:IBPC-NX8MP.png|alt=|center|frameless|108x108px]]<br><b><big>IBPC-NX8MP</big></b></td>
<td style="width: 25%;">[[File:PN8M090T-3.png|alt=|center|frameless|108x108px|link=[[IMX8MMINI-PPC]]]]<br><b><big>PN8MP-090T</big></b></td>
<td style="width: 25%;">[[File:Nx8mm-35 front homer1.png|alt=|center|frameless|86x86px|link=[[NX8MM-35]]]]<br><b><big>NX8MP-SBC</big></b></td>
</tr>
</table>

<p><br /></p>
==Vortex86 Series==

{| class="wikitable" style="width:100%; text-align:center; border:1px solid black; border-collapse:collapse;"

! colspan="1" style="background-color:#105aa2; color:white; font-weight:bold;" |Hardware Device
! colspan="3" style="background-color:#105aa2; color:white; font-weight:bold;" ! |Software Support
|-
| style="width: 40%" |[[Vortex86DX]]|| style="width: 20%" |[[Vortex86DX: Windows|Windows]]|| style="width: 20%" |[[Vortex86DX: Linux|Linux]]|| style="width: 20%" |[[Vortex86DX: DOS|DOS]]
|-
|[[Vortex86DX2]]||[[Vortex86DX2: Windows|Windows]]||[[Vortex86DX2: Linux|Linux]]||[[Vortex86DX2: DOS|DOS]]
|-
|[[Vortex86DX3]]||[[Vortex86DX3: Windows|Windows]]||[[Vortex86DX3: Linux|Linux]]||[[Vortex86DX3: DOS|DOS]]
|-
|[[Vortex86EX]]||[[Vortex86EX: Windows|Windows]]||[[Vortex86EX: Linux|Linux]]||[[Vortex86EX: DOS|DOS]]
|-
|[[Vortex86EX2]]||[[Vortex86EX2: Windows|Windows]]||[[Vortex86EX2: Linux|Linux]]||[[Vortex86EX2: DOS|DOS]]
|}

==Vortex86DX3 Series==
{| class="wikitable" style="width:100%; text-align:center; border:0px solid black; border-collapse:collapse;"

! colspan="3" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |System on module
|-
! style="width:10%;background-color:white;" |[[File:SOM304D3.png|alt=|center|frameless|70x70px|link=[[SOM304D3]]]]<br>'''SOM304D3'''
! style="width:10%;background-color:white;" |[[File:VDX3-ETX.png|alt=|center|frameless|70x70px|link=[[VDX3-ETX-V2]]]]<br>'''VDX3-ETX-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-Q7.png|alt=|center|frameless|70x70px|link=[[VDX3-Q7]]]]<br>'''VDX3-Q7'''
|-
! colspan="7" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |Embbedded Board
|-
! style="width:10%;background-color:white;" |[[File:VDX3-6754S-V2.png|alt=|center|frameless|70x70px|link=[[VDX3-6754S-V2]]]]<br>'''VDX3-6754S-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-6754-V2.png|alt=|center|frameless|70x70px|link=[[VDX3-6754-V2]]]]<br>'''VDX3-6754-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-6755.png|alt=|center|frameless|70x70px|link=[[VDX3-6755]]]]<br>'''VDX3-6755'''
! style="width:10%;background-color:white;" |[[File:VDX3-6726.png|alt=|center|frameless|70x70px|link=[[VDX3-6726-V2]]]]<br>'''VDX3-6726-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-PCI.png|alt=|center|frameless|70x70px|link=[[VDX3-PCI]]]]<br>'''VDX3-PCI'''
! style="width:10%;background-color:white;" |[[File:VDX3-6724.png|alt=|center|frameless|70x70px|link=[[VDX3-6724-V2]]]]<br>'''VDX3-6724-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-EITX.png|alt=|center|frameless|70x70px|link=[[VDX3-EITX]]]]<br>'''VDX3-EITX'''
|-
! colspan="6" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |EBOX-3350/EBOX-3352
|-
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3-RCA.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3-RCA]]]]<br>'''EBOX-335xDX3-RCA'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3 w Wide Temperature.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/Wide Temperature]]]]<br>'''EBOX-335xDX3<br>w/Wide Temperature'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3 w Wide Temperature.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/1G LAN]]]]<br>'''EBOX-335xDX3<br>w/1G LAN'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3]]]]<br>'''EBOX-335xDX3'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/1G LAN & Wide Temperature]]]]<br>'''EBOX-335xDX3<br>w/1G LAN & Wide Temperature'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3 wRS232 x2.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/RS232 x2]]]]<br>'''EBOX-335xDX3 w/RS232 x2'''
|-
! colspan="8" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |EBOX-3360/EBOX-3362
|-
! style="width:10%;background-color:white;" |[[File:EB-336x w HDMI EB-336x w8-bit GPIO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/HDMI]]]]<br>'''EB-336x w/HDMI'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS232 EB-336x w 4G LTE EB-336x w RS422.png|alt=|center|frameless|70x70px|link=[[EB-336x w/4G LTE]]]]<br>'''EB-336x w/4G LTE'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS232 EB-336x w 4G LTE EB-336x w RS422.png|alt=|center|frameless|70x70px|link=[[EB-336x w/RS232]]]]<br>'''EB-336x w/RS232'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS485.png|alt=|center|frameless|70x70px|link=[[EB-336x w/RS485]]]]<br>'''EB-336x w/RS485'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS232 EB-336x w 4G LTE EB-336x w RS422.png|alt=|center|frameless|70x70px|link=[[EB-336x w/RS422]]]]<br>'''EB-336x w/RS422'''
! style="width:10%;background-color:white;" |[[File:EB-336x w HDMI EB-336x w8-bit GPIO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/8-bit GPIO]]]]<br>'''EB-336x w/8-bit GPIO'''
! style="width:10%;background-color:white;" |[[File:EB-336x w Legacy IO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/Multi LAN]]]]<br>'''EB-336x w/Multi LAN'''
! style="width:10%;background-color:white;" |[[File:EB-336x w Legacy IO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/Legacy I/O]]]]<br>'''EB-336x w/Legacy I/O'''
|}

Main Page

2025-07-16T08:20:00Z

Joec:

==NXP Series==
<table class="wikitable" style="width: 100%; height: auto; border-color: #ffffff">
<tr>
<td colspan="4" style="background-color:#105aa2; color:white; font-weight:bold">
<p style="text-align: center;"><b>Hardware Device</b></p>
</td>
</tr>
<tr style="vertical-align: top;text-align:center">
<td style="width: 25%;">[[File:Imx8-168.png|alt=|center|frameless|100x100px|link=[[NX8MMINI-D168]]]]<br><b><big>[[NX8MMINI-D168]]</big></b></td>
<td style="width: 25%;">[[File:IMx8M_front_2.jpg|alt=|center|frameless|100x100px|link=[[EBOX-IMX8MM]]]]<br><b><big>[[EBOX-IMX8MM|EBOX-IMX8MM]]</big></b></td>
<td style="width: 25%;">[[File:PN8M090T-3.png|alt=|center|frameless|108x108px|link=[[IMX8MMINI-PPC]]]]<br><b>[[IMX8MMINI-PPC|<big>PN8M-090T</big>]]</b></td>
<td style="width: 25%;">[[File:Nx8mm-35 front homer1.png|alt=|center|frameless|86x86px|link=[[NX8MM-35]]]]<br><b><big>[[NX8MM-35]]</big></b></td>
</tr>
</table>

<p><br /></p>
<table class="wikitable" style="width: 100%; height: auto; border-color: #ffffff">
<tr>
<td colspan="4" style="background-color:#105aa2; color:white; font-weight:bold">
<p style="text-align: center;"><b>Hardware Device</b></p>
</td>
</tr>
<tr style="vertical-align: top;text-align:center">
<td style="width: 25%;">[[File:NX8MP-SMARC.png|alt=|center|frameless|120x120px|link=[[NX8MP-SMARC]]]<br><b><big>[[NX8MP-SMARC]]</big></b></td>
<td style="width: 25%;">[[File:IBPC-NX8MP.png|alt=|center|frameless|108x108px]]<br><b><big>IBPC-NX8MP</big></b></td>
<td style="width: 25%;">[[File:PN8M090T-3.png|alt=|center|frameless|108x108px|link=[[IMX8MMINI-PPC]]]]<br><b><big>PN8MP-090T</big></b></td>
<td style="width: 25%;">[[File:Nx8mm-35 front homer1.png|alt=|center|frameless|86x86px|link=[[NX8MM-35]]]]<br><b><big>NX8MP-SBC</big></b></td>
</tr>
</table>

<p><br /></p>
==Vortex86 Series==

{| class="wikitable" style="width:100%; text-align:center; border:1px solid black; border-collapse:collapse;"

! colspan="1" style="background-color:#105aa2; color:white; font-weight:bold;" |Hardware Device
! colspan="3" style="background-color:#105aa2; color:white; font-weight:bold;" ! |Software Support
|-
| style="width: 40%" |[[Vortex86DX]]|| style="width: 20%" |[[Vortex86DX: Windows|Windows]]|| style="width: 20%" |[[Vortex86DX: Linux|Linux]]|| style="width: 20%" |[[Vortex86DX: DOS|DOS]]
|-
|[[Vortex86DX2]]||[[Vortex86DX2: Windows|Windows]]||[[Vortex86DX2: Linux|Linux]]||[[Vortex86DX2: DOS|DOS]]
|-
|[[Vortex86DX3]]||[[Vortex86DX3: Windows|Windows]]||[[Vortex86DX3: Linux|Linux]]||[[Vortex86DX3: DOS|DOS]]
|-
|[[Vortex86EX]]||[[Vortex86EX: Windows|Windows]]||[[Vortex86EX: Linux|Linux]]||[[Vortex86EX: DOS|DOS]]
|-
|[[Vortex86EX2]]||[[Vortex86EX2: Windows|Windows]]||[[Vortex86EX2: Linux|Linux]]||[[Vortex86EX2: DOS|DOS]]
|}

==Vortex86DX3 Series==
{| class="wikitable" style="width:100%; text-align:center; border:0px solid black; border-collapse:collapse;"

! colspan="3" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |System on module
|-
! style="width:10%;background-color:white;" |[[File:SOM304D3.png|alt=|center|frameless|70x70px|link=[[SOM304D3]]]]<br>'''SOM304D3'''
! style="width:10%;background-color:white;" |[[File:VDX3-ETX.png|alt=|center|frameless|70x70px|link=[[VDX3-ETX-V2]]]]<br>'''VDX3-ETX-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-Q7.png|alt=|center|frameless|70x70px|link=[[VDX3-Q7]]]]<br>'''VDX3-Q7'''
|-
! colspan="7" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |Embbedded Board
|-
! style="width:10%;background-color:white;" |[[File:VDX3-6754S-V2.png|alt=|center|frameless|70x70px|link=[[VDX3-6754S-V2]]]]<br>'''VDX3-6754S-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-6754-V2.png|alt=|center|frameless|70x70px|link=[[VDX3-6754-V2]]]]<br>'''VDX3-6754-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-6755.png|alt=|center|frameless|70x70px|link=[[VDX3-6755]]]]<br>'''VDX3-6755'''
! style="width:10%;background-color:white;" |[[File:VDX3-6726.png|alt=|center|frameless|70x70px|link=[[VDX3-6726-V2]]]]<br>'''VDX3-6726-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-PCI.png|alt=|center|frameless|70x70px|link=[[VDX3-PCI]]]]<br>'''VDX3-PCI'''
! style="width:10%;background-color:white;" |[[File:VDX3-6724.png|alt=|center|frameless|70x70px|link=[[VDX3-6724-V2]]]]<br>'''VDX3-6724-V2'''
! style="width:10%;background-color:white;" |[[File:VDX3-EITX.png|alt=|center|frameless|70x70px|link=[[VDX3-EITX]]]]<br>'''VDX3-EITX'''
|-
! colspan="6" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |EBOX-3350/EBOX-3352
|-
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3-RCA.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3-RCA]]]]<br>'''EBOX-335xDX3-RCA'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3 w Wide Temperature.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/Wide Temperature]]]]<br>'''EBOX-335xDX3<br>w/Wide Temperature'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3 w Wide Temperature.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/1G LAN]]]]<br>'''EBOX-335xDX3<br>w/1G LAN'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3]]]]<br>'''EBOX-335xDX3'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/1G LAN & Wide Temperature]]]]<br>'''EBOX-335xDX3<br>w/1G LAN & Wide Temperature'''
! style="width:10%;background-color:white;" |[[File:EBOX-335xDX3 wRS232 x2.png|alt=|center|frameless|70x70px|link=[[EBOX-335xDX3 w/RS232 x2]]]]<br>'''EBOX-335xDX3 w/RS232 x2'''
|-
! colspan="8" style="height:50px; background-color:#105aa2; color:white; font-weight:bold;" ! |EBOX-3360/EBOX-3362
|-
! style="width:10%;background-color:white;" |[[File:EB-336x w HDMI EB-336x w8-bit GPIO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/HDMI]]]]<br>'''EB-336x w/HDMI'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS232 EB-336x w 4G LTE EB-336x w RS422.png|alt=|center|frameless|70x70px|link=[[EB-336x w/4G LTE]]]]<br>'''EB-336x w/4G LTE'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS232 EB-336x w 4G LTE EB-336x w RS422.png|alt=|center|frameless|70x70px|link=[[EB-336x w/RS232]]]]<br>'''EB-336x w/RS232'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS485.png|alt=|center|frameless|70x70px|link=[[EB-336x w/RS485]]]]<br>'''EB-336x w/RS485'''
! style="width:10%;background-color:white;" |[[File:EB-336x w RS232 EB-336x w 4G LTE EB-336x w RS422.png|alt=|center|frameless|70x70px|link=[[EB-336x w/RS422]]]]<br>'''EB-336x w/RS422'''
! style="width:10%;background-color:white;" |[[File:EB-336x w HDMI EB-336x w8-bit GPIO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/8-bit GPIO]]]]<br>'''EB-336x w/8-bit GPIO'''
! style="width:10%;background-color:white;" |[[File:EB-336x w Legacy IO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/Multi LAN]]]]<br>'''EB-336x w/Multi LAN'''
! style="width:10%;background-color:white;" |[[File:EB-336x w Legacy IO.png|alt=|center|frameless|70x70px|link=[[EB-336x w/Legacy I/O]]]]<br>'''EB-336x w/Legacy I/O'''
|}

NX8MP-SMARC

2025-07-16T08:18:01Z

Joec:

<p align="right"><table style="padding:15px; background-color: #e3e0e0; color: black; width:100%; font-size:25px; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>NX8MP-SMARC
</td>

</tr>
</table><br /><table style="background-color: #ffffff; width:100%;">
<tr>
<td style="width:250px; padding:5px 25px 5px 25px;">
[[File:NX8MP-SMARC.png|alt=|frameless]]</td>
<td style="padding:20px 30px 0px 0px; vertical-align:top; font-size:17px;">
<h2>
<b><big>Features</big></b>
</h2>

#<p style="text-align: justify; line-height: 2;"> NXP i.MX8M Plus Quad, 4 x Cortex-A53 1.6GHz </p>
#<p style="text-align: justify; line-height: 2;"> Display: HDMI / Dual-Channel LVDS </p>
#<p style="text-align: justify; line-height: 2;"> I/O:4xUART/5xUSB/2xGLAN/5xI2C/SPI/PCIe/14-bit GPIO/I2S/MIPI-CSIx2 </p>
#<p style="text-align: justify; line-height: 2;"> Optional interface: WiFi/BT / TPM </p>
#<p style="text-align: justify; line-height: 2;"> RAM: 4/8 GB LPDDR4 </p>
#<p style="text-align: justify; line-height: 2;"> Standard SMARC 2.1 System on Module </p>
#<p style="text-align: justify; line-height: 2;"> Working temp.: -20° to 70° C or -40° to 85° C (Optional) </p><p style="text-align: justify; line-height: 2;"> </p>

<br />
<li>Join the [http://community.nxp.com/community/imx/content professional technical forum] about NXP i.MX 8M series
</li>
<li>[https://wiki.icop.com.tw/product/images/3/35/NX8MP-Smarc-RTL_module_block_diagram.jpg Block diagram]</li>
<li>[https://wiki.icop.com.tw/product/images/4/4c/NX8MP-SMARC_datasheet.pdf Datasheet]</li><li>[[ODM OEM|ODM/OEM project]]
</li>
</td>
</tr>
</table>

<div style="width:100%; margin-top: 50px;">
<p><br /></p>
<div style="width:30%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table style="padding:10px; background-color: #e3e0e0; color: black; width:100%; font-size:20px; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Specifications
</td>
</tr>
</table>
<table class="wikitable" style="font-size: 14px;">
<tr>
<td><p><b>CPU</b></p></td>
<td><p>NXP i.MX8M Plus Quad, </p><p>4 x Cortex-A53 1.6GHz</p></td>
</tr>
<tr>
<td><p><b>Memory</b></p></td>
<td><p>4/8 GB LPDDR4</p></td>
</tr>
<tr>
<td><p><b>GPU</b></p></td>
<td><p>GC7000UL for 3D engine / </p><p>GC520L for 2D engine</p></td>
</tr>
<tr>
<td><p><b>Display</b></p></td>
<td><p>HDMI: up to 3840 x 2160p30</p>LVDS: Dual-LVDS 24-bit maximum resolution up to 1920 x 1200 @ 60Hz
</td>
</tr>
<tr>
<td><p><b>Storage</b></p></td>
<td><p>On board eMMC 16~128GB (MLC)</p><p>SDIO</p></td>
</tr>
<tr>
<td><p><b>Network</b></p></td>
<td><p>Ethernet: 10/100/1000 Mbps x2</p></td>
</tr>
<tr>
<td><p><b>RTC</b></p></td>
<td><p>PCF8563TS/5</p></td>
</tr>
<tr>
<td><p><b>I2C</b></p></td>
<td><p>×5</p></td>
</tr>
<tr>
<td><p><b>SPI</b></p></td>
<td><p>×1</p></td>
</tr>
<tr>
<td><p><b>UARTs</b></p></td>
<td><p>×4</p></td>
</tr>
<tr>
<td><p><b>USB</b></p></td>
<td><p>5xUSB </p><p>(Incl. USB3.0x2 / 2.0x2 / 2.0OTGx1)</p></td>
</tr>
<tr>
<td><p><b>BUS</b></p></td>
<td><p>PCIe</p></td>
</tr>
<tr>
<td><p><b>Audio</b></p></td>
<td><p>I2S</p></td>
</tr>
<tr>
<td><p><b>Temperature Range</b></p></td>
<td><p>-20° to 70° C or</p>
<p>-40° to 85° C (Optional)</p>
</td>
</tr>
<tr>
<td><p><b>Dimensions</b></p></td>
<td><p>82.00mm × 50.00mm</p></td>
</tr>
</table>
</div>
<div style="width:30%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table> <table style="padding:10px; background-color: #0055a5; color: white; font-size:19px; width:100%; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Yocto
</td>
</tr>
</table>
<table style="background-color: #e3e0e0; width:100%; height: 100px;">
<tr>
<td></td>
<td style="padding-left: 4%; padding-right: 4%; vertical-align:top; max-width:100%;">
<p></p></td>
</tr>
</table>
</div>
<div style="width:30%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table> <table style="padding:10px; background-color: #0055a5; color: white; font-size:19px; width:100%; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Android
</td>
</tr>
</table>
<table style="background-color: #e3e0e0; width:100%; height:100px;">
<tr>
<td></td>
<td style="padding-left: 4%; padding-right: 4%; vertical-align:top; max-width:100%;">
<p></p></td>
</tr>
</table>

</div>
</div>

NX8MP-SMARC

2025-07-16T08:16:46Z

Joec:

<p align="right"><table style="padding:15px; background-color: #e3e0e0; color: black; width:100%; font-size:25px; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>NX8MP-SMARC
</td>

</tr>
</table><br /><table style="background-color: #ffffff; width:100%;">
<tr>
<td style="width:250px; padding:5px 25px 5px 25px;">
[[File:NX8MP-SMARC.png|alt=|frameless]]</td>
<td style="padding:20px 30px 0px 0px; vertical-align:top; font-size:17px;">
<h2>
<b><big>Features</big></b>
</h2>

#<p style="text-align: justify; line-height: 2;"> NXP i.MX8M Plus Quad, 4 x Cortex-A53 1.6GHz </p>
#<p style="text-align: justify; line-height: 2;"> Display: HDMI / Dual-Channel LVDS </p>
#<p style="text-align: justify; line-height: 2;"> I/O:4xUART/5xUSB/2xGLAN/5xI2C/SPI/PCIe/14-bit GPIO/I2S/MIPI-CSIx2 </p>
#<p style="text-align: justify; line-height: 2;"> Optional interface: WiFi/BT / TPM </p>
#<p style="text-align: justify; line-height: 2;"> RAM: 4/8 GB LPDDR4 </p>
#<p style="text-align: justify; line-height: 2;"> Standard SMARC 2.1 System on Module </p>
#<p style="text-align: justify; line-height: 2;"> Working temp.: -20° to 70° C or -40° to 85° C (Optional) </p><p style="text-align: justify; line-height: 2;"> </p>

<br />
<li>Join the [http://community.nxp.com/community/imx/content professional technical forum] about NXP i.MX 8M series
</li>
<li>[https://wiki.icop.com.tw/product/images/3/35/NX8MP-Smarc-RTL_module_block_diagram.jpg Block diagram]</li>
<li>[https://wiki.icop.com.tw/product/images/4/4c/NX8MP-SMARC_datasheet.pdf Datasheet]</li><li>[[ODM OEM|ODM/OEM project]]
</li>
</td>
</tr>
</table>

<div style="width:100%; margin-top: 50px;">
<p><br /></p>
<div style="width:30%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table style="padding:10px; background-color: #e3e0e0; color: black; width:100%; font-size:20px; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Specifications
</td>
</tr>
</table>
<table class="wikitable" style="font-size: 14px;">
<tr>
<td><p><b>CPU</b></p></td>
<td><p>NXP i.MX8M Plus Quad, </p><p>4 x Cortex-A53 1.6GHz</p></td>
</tr>
<tr>
<td><p><b>Memory</b></p></td>
<td><p>4/8 GB LPDDR4</p></td>
</tr>
<tr>
<td><p><b>GPU</b></p></td>
<td><p>GC7000UL for 3D engine / </p><p>GC520L for 2D engine</p></td>
</tr>
<tr>
<td><p><b>Display</b></p></td>
<td><p>HDMI: up to 3840 x 2160p30</p>LVDS: Dual-LVDS 24-bit maximum resolution up to 1920 x 1200 @ 60Hz
</td>
</tr>
<tr>
<td><p><b>Storage</b></p></td>
<td><p>On board eMMC 16~128GB (MLC)</p><p>SDIO</p></td>
</tr>
<tr>
<td><p><b>Network</b></p></td>
<td><p>Ethernet: 10/100/1000 Mbps x2</p></td>
</tr>
<tr>
<td><p><b>RTC</b></p></td>
<td><p>PCF8563TS/5</p></td>
</tr>
<tr>
<td><p><b>I2C</b></p></td>
<td><p>×5</p></td>
</tr>
<tr>
<td><p><b>SPI</b></p></td>
<td><p>×1</p></td>
</tr>
<tr>
<td><p><b>UARTs</b></p></td>
<td><p>×4</p></td>
</tr>
<tr>
<td><p><b>USB</b></p></td>
<td><p>5xUSB </p><p>(Incl. USB3.0x2 / 2.0x2 / 2.0OTGx1)</p></td>
</tr>
<tr>
<td><p><b>BUS</b></p></td>
<td><p>PCIe</p></td>
</tr>
<tr>
<td><p><b>Audio</b></p></td>
<td><p>I2S</p></td>
</tr>
<tr>
<td><p><b>Temperature Range</b></p></td>
<td><p>-20° to 70° C or</p>
<p>-40° to 85° C (Optional)</p>
</td>
</tr>
<tr>
<td><p><b>Dimensions</b></p></td>
<td><p>82.00mm × 50.00mm</p></td>
</tr>
</table>
</div>
<div style="width:30%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table> <table style="padding:10px; background-color: #0055a5; color: white; font-size:19px; width:100%; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Yocto
</td>
</tr>
</table>
<table style="background-color: #e3e0e0; width:100%; height: 100px;">
<tr>
<td></td>
<td style="padding-left: 4%; padding-right: 4%; vertical-align:top; max-width:100%;">
<p><b><big>Sumo (kernel 4.14.98)</big></b></p>
<p><br /></p>
<p><big><b>Development</b></big></p>
<ul>
<li><b>[[How to Restore Yocto Linux to the eMMC on EBOX-IMX8MM|EBOX-IMX8MM eMMC image]]</b></li>
<li><b>[[How to Restore Yocto Linux to the eMMC on PN8M-090T|PN8M-090T eMMC image]]</b></li><li><b>[[How to Restore Yocto Linux to the eMMC on NX8MM-35|NX8MM-35 eMMC image]]</b>
</li>
</ul>
<p><br /></p>
<p><b><big>[http://www.nxp.com/design/software/embedded-software/i-mx-software:IMX-SW Software and Development Tool]</big></b></p>
</td>
</tr>
</table>
</div>
<div style="width:30%; float:left; padding:0px 2% 0px 0px; display:inline-block;">
<table> <table style="padding:10px; background-color: #0055a5; color: white; font-size:19px; width:100%; border-top-left-radius:5px; border-top-right-radius:5px;">
<tr>
<td>Android
</td>
</tr>
</table>
<table style="background-color: #e3e0e0; width:100%; height:100px;">
<tr>
<td></td>
<td style="padding-left: 4%; padding-right: 4%; vertical-align:top; max-width:100%;">
<p><b><big>Pie 9.0 (kernel 4.14.98)</big></b></p>
<p><br /></p>
<p><big><b>Development</b></big></p>
<ul>
<li><b>[[How to Restore Android9 OS to the eMMC on EBOX-IMX8MM|EBOX-IMX8MM eMMC image]]</b></li>
<li><b>[[How to Restore Android9 OS to the eMMC on PN8M-090T|PN8M-090T eMMC image]]</b><li><b>[[How to Restore Android9 OS to the eMMC on NX8MM-35|NX8MM-35 eMMC image]]</b></p>
</ul>
<p><br /></p>
<p><b><big>[http://www.nxp.com/design/software/embedded-software/i-mx-software:IMX-SW Software and Development Tool]</big></b></p>
</td>
</tr>
</table>

</div>
</div>