ArmadeusWiki - User contributions [en]

EMMC OPOS93

2026-01-30T14:24:48Z

SebastienSz: /* Boot1 partition layout */

[[Category: eMMC]]

= OPOS93 eMMC layout =

By default, the 8GB eMMC on [[OPOS93]] module has 4 physical/hardware partitions:

{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:80px;background:orange;" align="center" | Boot0
| style="width:80px;background:orange;" align="center" | Boot1
| style="background:red;" | RPMB
| style="width:500px;background:green;color:white;" align="center" | User Data
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS93 eMMC partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot name || Size || Comment
|----------------
|boot0 || mmc dev 0 1 || 4 MBytes || U-Boot is installed on this partition
|----------------
|boot1 || mmc dev 0 2 || 4 MBytes || U-Boot env is installed on this partition
|----------------
|rpmb || mmc dev 0 3 || 4 MBytes || Not used
|----------------
|User Data || mmc dev 0 0 || remaining space (~7,3 GBytes) || Kernel, device tree and rootfs
|----------------
|}

== Boot0 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:150px;background:orange;color:white;" align="center" | opos93-u-boot.bin
| style="width:300px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot0''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot0 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 1.3 MiB || Boot image (opos93-u-boot.bin) containing U-Boot, ATF, etc...
|----------------
||| || || Free
|----------------
|}

== Boot1 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:50px;background:orange;color:white;" align="center" | U-Boot env
| style="width:50px;background:orange;color:white;" align="center" | U-Boot redundant env
| style="width:200px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot1''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot1 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 128 KiB || U-Boot environment
|----------------
|256 || 128 KiB || 128 KiB || U-Boot redundant environment
|----------------
||| || || Free
|----------------
|}

== RPMB partition layout ==
* Not used !

== User Data partition layout ==

There are 3 partitions on the "User Data" physical partition:
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:50px;background:white;color:black;" align="center" | ...
| style="width:200px;background:green;color:white;" align="center" | Failsafe/Update (primary)
| style="width:200px;background:green;color:white;" align="center" | Default Rootfs (primary)
| style="width:600px;background:green;color:white;" align="center" | Home/Data (primary)
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS93 eMMC User data partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot device || Linux device || Offset (bytes) || Offset (sectors/blocs) || Size || Comment
|----------------
|MBR || NA || NA || 0 || 0 || 512 bytes (1 block) || Master Boot Record + some spare space ( -> Don't touch it :-) )
|----------------
|Failsafe || mmc 0:1 || /dev/mmcblk0p1 || 1M || 2048 (0x800) || 512 MBytes (1048576 sectors) || system/rootfs to restore your board in case of problem or setup a safe update mechanism (ext4 formatted)
|----------------
|Rootfs || mmc 0:2 || /dev/mmcblk0p2 || || 1050624 (0x10800) || 512 MBytes (1048576 sectors) || the default booted rootfs is on this partition (ext4 formatted)
|----------------
|Home/Data || mmc 0:3 || /dev/mmcblk0p3 || || 2099200 (0x200800) || Rest of space: ~6,3 GBytes (13208542 sectors) || HOME can be stored on this partition (ext4 formatted)
|----------------
|}

* By default, when flashed from U-Boot, rootfs and boot are only occupying the size of the .ext4 images used during flashing. If you want to increase the rootfs/boot size to all available free space then, after Linux has booted, use the following commands:
<pre class="apf">
# resize2fs /dev/mmcblk0p2 # for Rootfs
</pre>

* Or with ''apf-config'' command:
<pre class="apf">
# apf-config
</pre>
* In menu:
<pre class="config">
| 1 Expand Filesystem(s) OS can then use all eMMC/SD space |
</pre>

Rootfs/Boot will then be extended to all the "Rootfs"/"Boot" eMMC partitions space.

==Tips==
* Commands to partition ''User Data'' from fdisk on Host PC with [[U-Boot UMS on APF & OPOS|U-Boot UMS]]. '''Check /dev/sdc is the eMMC of your OPOS93 device otherwise you may destroy your PC partition table !!!''':
<pre class=host>
$ sudo echo -e 'size=512MiB,type=0x83\nsize=512MiB,type=0x83\ntype=0x83' | sfdisk /dev/sdc

$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc1
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc2
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc3

</pre>

==Links==
* [http://fr.slideshare.net/linaroorg/intro-to-emmc http://fr.slideshare.net/linaroorg/intro-to-emmc]
* https://fr.wikipedia.org/wiki/Master_boot_record ou http://poloastucien.free.fr/mbr_fat_secteurs_boot_h.html

EMMC OPOS93

2026-01-30T14:23:37Z

SebastienSz: /* Boot0 partition layout */

[[Category: eMMC]]

= OPOS93 eMMC layout =

By default, the 8GB eMMC on [[OPOS93]] module has 4 physical/hardware partitions:

{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:80px;background:orange;" align="center" | Boot0
| style="width:80px;background:orange;" align="center" | Boot1
| style="background:red;" | RPMB
| style="width:500px;background:green;color:white;" align="center" | User Data
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS93 eMMC partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot name || Size || Comment
|----------------
|boot0 || mmc dev 0 1 || 4 MBytes || U-Boot is installed on this partition
|----------------
|boot1 || mmc dev 0 2 || 4 MBytes || U-Boot env is installed on this partition
|----------------
|rpmb || mmc dev 0 3 || 4 MBytes || Not used
|----------------
|User Data || mmc dev 0 0 || remaining space (~7,3 GBytes) || Kernel, device tree and rootfs
|----------------
|}

== Boot0 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:150px;background:orange;color:white;" align="center" | opos93-u-boot.bin
| style="width:300px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot0''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot0 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 1.3 MiB || Boot image (opos93-u-boot.bin) containing U-Boot, ATF, etc...
|----------------
||| || || Free
|----------------
|}

== Boot1 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:50px;background:orange;color:white;" align="center" | U-Boot env
| style="width:100px;background:white;color:black;" align="center" | ...
| style="width:50px;background:orange;color:white;" align="center" | U-Boot redundant env
| style="width:100px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot1''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot1 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 128 KiB || U-Boot environment
|----------------
|256 || 128 KiB || 128 KiB || U-Boot redundant environment
|----------------
||| || || Free
|----------------
|}

== RPMB partition layout ==
* Not used !

== User Data partition layout ==

There are 3 partitions on the "User Data" physical partition:
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:50px;background:white;color:black;" align="center" | ...
| style="width:200px;background:green;color:white;" align="center" | Failsafe/Update (primary)
| style="width:200px;background:green;color:white;" align="center" | Default Rootfs (primary)
| style="width:600px;background:green;color:white;" align="center" | Home/Data (primary)
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS93 eMMC User data partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot device || Linux device || Offset (bytes) || Offset (sectors/blocs) || Size || Comment
|----------------
|MBR || NA || NA || 0 || 0 || 512 bytes (1 block) || Master Boot Record + some spare space ( -> Don't touch it :-) )
|----------------
|Failsafe || mmc 0:1 || /dev/mmcblk0p1 || 1M || 2048 (0x800) || 512 MBytes (1048576 sectors) || system/rootfs to restore your board in case of problem or setup a safe update mechanism (ext4 formatted)
|----------------
|Rootfs || mmc 0:2 || /dev/mmcblk0p2 || || 1050624 (0x10800) || 512 MBytes (1048576 sectors) || the default booted rootfs is on this partition (ext4 formatted)
|----------------
|Home/Data || mmc 0:3 || /dev/mmcblk0p3 || || 2099200 (0x200800) || Rest of space: ~6,3 GBytes (13208542 sectors) || HOME can be stored on this partition (ext4 formatted)
|----------------
|}

* By default, when flashed from U-Boot, rootfs and boot are only occupying the size of the .ext4 images used during flashing. If you want to increase the rootfs/boot size to all available free space then, after Linux has booted, use the following commands:
<pre class="apf">
# resize2fs /dev/mmcblk0p2 # for Rootfs
</pre>

* Or with ''apf-config'' command:
<pre class="apf">
# apf-config
</pre>
* In menu:
<pre class="config">
| 1 Expand Filesystem(s) OS can then use all eMMC/SD space |
</pre>

Rootfs/Boot will then be extended to all the "Rootfs"/"Boot" eMMC partitions space.

==Tips==
* Commands to partition ''User Data'' from fdisk on Host PC with [[U-Boot UMS on APF & OPOS|U-Boot UMS]]. '''Check /dev/sdc is the eMMC of your OPOS93 device otherwise you may destroy your PC partition table !!!''':
<pre class=host>
$ sudo echo -e 'size=512MiB,type=0x83\nsize=512MiB,type=0x83\ntype=0x83' | sfdisk /dev/sdc

$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc1
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc2
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc3

</pre>

==Links==
* [http://fr.slideshare.net/linaroorg/intro-to-emmc http://fr.slideshare.net/linaroorg/intro-to-emmc]
* https://fr.wikipedia.org/wiki/Master_boot_record ou http://poloastucien.free.fr/mbr_fat_secteurs_boot_h.html

EMMC OPOS93

2026-01-30T14:19:17Z

SebastienSz: Created page with "Category: eMMC = OPOS93 eMMC layout = By default, the 8GB eMMC on OPOS93 module has 4 physical/hardware partitions: {| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions" |---------------- | style="width:80px;background:orange;" align="center" | Boot0 | style="width:80px;background:orange;" align="center" | Boot1 | style="background:red;" | RPMB | style="width:500px;background:green;color:white;" align="center" | User Data |} {| bord..."

[[Category: eMMC]]

= OPOS93 eMMC layout =

By default, the 8GB eMMC on [[OPOS93]] module has 4 physical/hardware partitions:

{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:80px;background:orange;" align="center" | Boot0
| style="width:80px;background:orange;" align="center" | Boot1
| style="background:red;" | RPMB
| style="width:500px;background:green;color:white;" align="center" | User Data
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS93 eMMC partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot name || Size || Comment
|----------------
|boot0 || mmc dev 0 1 || 4 MBytes || U-Boot is installed on this partition
|----------------
|boot1 || mmc dev 0 2 || 4 MBytes || U-Boot env is installed on this partition
|----------------
|rpmb || mmc dev 0 3 || 4 MBytes || Not used
|----------------
|User Data || mmc dev 0 0 || remaining space (~7,3 GBytes) || Kernel, device tree and rootfs
|----------------
|}

== Boot0 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:10px;background:white;color:black;" align="center" | ...
| style="width:40px;background:orange;color:white;" align="center" | SPL
| style="width:100px;background:white;color:black;" align="center" | ...
| style="width:150px;background:orange;color:white;" align="center" | IMG
| style="width:150px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot0''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot0 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 1.3 MiB || Boot image (opos93-u-boot.bin) containing U-Boot, ATF, etc...
|----------------
||| || || Free
|----------------
|}

== Boot1 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:50px;background:orange;color:white;" align="center" | U-Boot env
| style="width:100px;background:white;color:black;" align="center" | ...
| style="width:50px;background:orange;color:white;" align="center" | U-Boot redundant env
| style="width:100px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot1''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot1 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 128 KiB || U-Boot environment
|----------------
|256 || 128 KiB || 128 KiB || U-Boot redundant environment
|----------------
||| || || Free
|----------------
|}

== RPMB partition layout ==
* Not used !

== User Data partition layout ==

There are 3 partitions on the "User Data" physical partition:
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS93 eMMC partitions"
|----------------
| style="width:50px;background:white;color:black;" align="center" | ...
| style="width:200px;background:green;color:white;" align="center" | Failsafe/Update (primary)
| style="width:200px;background:green;color:white;" align="center" | Default Rootfs (primary)
| style="width:600px;background:green;color:white;" align="center" | Home/Data (primary)
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS93 eMMC User data partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot device || Linux device || Offset (bytes) || Offset (sectors/blocs) || Size || Comment
|----------------
|MBR || NA || NA || 0 || 0 || 512 bytes (1 block) || Master Boot Record + some spare space ( -> Don't touch it :-) )
|----------------
|Failsafe || mmc 0:1 || /dev/mmcblk0p1 || 1M || 2048 (0x800) || 512 MBytes (1048576 sectors) || system/rootfs to restore your board in case of problem or setup a safe update mechanism (ext4 formatted)
|----------------
|Rootfs || mmc 0:2 || /dev/mmcblk0p2 || || 1050624 (0x10800) || 512 MBytes (1048576 sectors) || the default booted rootfs is on this partition (ext4 formatted)
|----------------
|Home/Data || mmc 0:3 || /dev/mmcblk0p3 || || 2099200 (0x200800) || Rest of space: ~6,3 GBytes (13208542 sectors) || HOME can be stored on this partition (ext4 formatted)
|----------------
|}

* By default, when flashed from U-Boot, rootfs and boot are only occupying the size of the .ext4 images used during flashing. If you want to increase the rootfs/boot size to all available free space then, after Linux has booted, use the following commands:
<pre class="apf">
# resize2fs /dev/mmcblk0p2 # for Rootfs
</pre>

* Or with ''apf-config'' command:
<pre class="apf">
# apf-config
</pre>
* In menu:
<pre class="config">
| 1 Expand Filesystem(s) OS can then use all eMMC/SD space |
</pre>

Rootfs/Boot will then be extended to all the "Rootfs"/"Boot" eMMC partitions space.

==Tips==
* Commands to partition ''User Data'' from fdisk on Host PC with [[U-Boot UMS on APF & OPOS|U-Boot UMS]]. '''Check /dev/sdc is the eMMC of your OPOS93 device otherwise you may destroy your PC partition table !!!''':
<pre class=host>
$ sudo echo -e 'size=512MiB,type=0x83\nsize=512MiB,type=0x83\ntype=0x83' | sfdisk /dev/sdc

$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc1
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc2
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc3

</pre>

==Links==
* [http://fr.slideshare.net/linaroorg/intro-to-emmc http://fr.slideshare.net/linaroorg/intro-to-emmc]
* https://fr.wikipedia.org/wiki/Master_boot_record ou http://poloastucien.free.fr/mbr_fat_secteurs_boot_h.html

Secure boot on OPOS93

2024-10-07T16:21:57Z

SebastienSz:

= Introduction =

This document is a quick how-to boot a signed boot firmware on the OPOS93 SoM. It summarizes the documents provided by NXP:

* [https://www.nxp.com/doc/an12312 AN12312]
* https://github.com/nxp-imx/uboot-imx/blob/lf-6.1.22-2.0.0/doc/imx/ahab/introduction_ahab.txt
* https://github.com/nxp-imx/uboot-imx/blob/lf-6.6.36-2.1.0/doc/imx/ahab/guides/mx8ulp_9x_secure_boot.txt

= Requirements =

== IMX CST TOOL ==

* Download the [https://www.nxp.com/webapp/Download?colCode=IMX_CST_TOOL_NEW IMX CST TOOL] and unarchive it:

<pre class="host">
tar xf IMX_CST_TOOL_NEW.tgz
</pre>

== imx-mkimage ==

* Checkout the imx-mkimage:

<pre class="host">
git clone -b lf-6.6.36-2.1.0 https://github.com/nxp-imx/imx-mkimage.git
</pre>

== Latest Armadeus U-Boot ==

* Make sure you have the latest Armadeus U-Boot installed on you OPOS93 SoM. It must have the '''ahab_status''' commands:

<pre class="code">
BIOS> ahab_status
Lifecycle: 0x00000008, OEM Open
...
</pre>

If the command is not available on your OPOS93 SoM, update to the latest Armadeus U-Boot.

= Generating a PKI tree =

* To generate your PKI tree, go to the CST TOOL directory and use the script '''ahab_pki_tree.sh''':

<pre class="host">
$ cd cst-3.4.1/
$ ./keys/ahab_pki_tree.sh
...
Do you want to use an existing CA key (y/n)?: n
Do you want to use Elliptic Curve Cryptography (y/n)?: y
Enter length for elliptic curve to be used for PKI tree:
Possible values p256, p384, p521: p384
Enter the digest algorithm to use: sha384
Enter PKI tree duration (years): 5
Do you want the SRK certificates to have the CA flag set? (y/n)?: y
</pre>

= Generating SRK Table and SRK Hash =

* Generate the SRK Table and SRK Hash with '''srktool''':

<pre class="host">
$ cd crts/
$ ../linux64/bin/srktool -a -d sha256 -s sha384 -t SRK_1_2_3_4_table.bin \
-e SRK_1_2_3_4_fuse.bin -f 1 -c \
SRK1_sha384_secp384r1_v3_usr_crt.pem,\
SRK2_sha384_secp384r1_v3_usr_crt.pem,\
SRK3_sha384_secp384r1_v3_usr_crt.pem,\
SRK4_sha384_secp384r1_v3_usr_crt.pem
</pre>

* Regenerate the SRK HASH (SRK_1_2_3_4_fuse.bin) by using SHA256 with SRK_1_2_3_4_table.bin:

<pre class="host">
$ openssl dgst -binary -sha256 SRK_1_2_3_4_table.bin > SRK_1_2_3_4_fuse.bin
</pre>

* Check if the hash in the SRK_1_2_3_4_fuse.bin is correct:

<pre class="host">
$ hexdump -C SRK_1_2_3_4_fuse.bin
0000000 db2959f2 90dfc39c 53394566 e0b75829
0000020 85e6f3b1 af00983d e5e804fe 7a451024

$ sha256sum SRK_1_2_3_4_table.bin
db2959f290dfc39c53394566e0b7582985e6f3b1af00983de5e804fe7a451024 SRK_1_2_3_4_table.bin
</pre>

= Signing the boot image =

* From the images directory of the Armadeus BSP, copy the files needed to generate a boot image (SPL, U-Boot proper, ATF) into the i.MX93 directory of the imx-mkimage tool:

<pre class="host">
$ cp <path to BSP Armadeus>/images/u-boot.bin <path to imx-mkimage>/iMX93/
$ cp <path to BSP Armadeus>/images/u-boot-spl.bin <path to imx-mkimage>/iMX93/
$ cp <path to BSP Armadeus>/images/bl31.bin <path to imx-mkimage>/iMX93/
$ cp <path to BSP Armadeus>/images/lpddr4* <path to imx-mkimage>/iMX93/
$ cp <path to BSP Armadeus>/images/ahab-container.img <path to imx-mkimage>/iMX93/mx93a1-ahab-container.img
</pre>

== Signing ATF + U-Boot proper Image container ==

* Generate the u-boot-atf-container.img file:

<pre class="host">
$ cd <path to imx-mkimage>
$ make SOC=iMX9 u-boot-atf-container.img
</pre>

* Note the offset the imx-mkimage tool outputs:

<pre class="host">
CST: CONTAINER 0 offset: 0x0
CST: CONTAINER 0: Signature Block: offset is at 0x110
Offsets = 0x0 0x110
</pre>

* A CSF description file is needed to sign the u-boot-atf-container.img file. You can download it [https://github.com/nxp-imx/uboot-imx/raw/refs/tags/lf-6.6.36-2.1.0/doc/imx/ahab/csf_examples/csf_uboot_atf.txt here]. In this file, update the offset you previously noted and the eventually the name and path of the keys:

<pre class="host">
...
Source = "../crts/SRK1_sha384_secp384r1_v3_ca_crt.pem"
...
[Authenticate Data]
# Binary to be signed generated by mkimage
File = "u-boot-atf-container.img"
# Offsets = Container header Signature block
Offsets = 0x0 0x110
</pre>

* Sign the u-boot-atf-container.img with the CST TOOL:

<pre class="host">
$ cd <path to CST TOOL>
$ ./linux64/bin/cst -i ~/Downloads/csf_uboot_atf.txt -o signed-u-boot-atf-container.img
</pre>

* Replace the u-boot-atf-container.img file with the signed-u-boot-atf-container.img file in the iMX93 directory of the imx-mkimage tool:

<pre class="host">
$ cp signed-u-boot-atf-container.img <path to imx-mkimage>/iMX93/u-boot-atf-container.img
</pre>

== Signing the boot image ==

* Generate the flash.bin file:

<pre class="host">
$ cd <path to imx-mkimage>
$ make SOC=iMX9 flash_singleboot
</pre>

* Note the offset the imx-mkimage tool outputs:

<pre class="host">
CST: CONTAINER 0 offset: 0x400
CST: CONTAINER 0: Signature Block: offset is at 0x490
Offsets = 0x400 0x490
</pre>

* Another CSF description file is needed to sign the flash.bin file. You can download it [https://github.com/nxp-imx/uboot-imx/raw/refs/tags/lf-6.6.36-2.1.0/doc/imx/ahab/csf_examples/csf_boot_image.txt here]. In this file, update the offset you previously noted and the eventually the name of the keys:

<pre class="host">
...
Source = "../crts/SRK1_sha384_secp384r1_v3_ca_crt.pem"
...
[Authenticate Data]
# Binary to be signed generated by mkimage
File = "/home/sszy/development/imx-mkimage/iMX93/flash.bin"
# Offsets = Container header Signature block (printed out by mkimage)
Offsets = 0x400 0x490
</pre>

* Sign the flash.bin file with the CST TOOL:

<pre class="host">
$ cd <path to CST TOOL>
$ ./linux64/bin/cst -i ~/Downloads/csf_boot_image.txt -o signed-flash.bin
</pre>

= Flashing U-Boot =

* On your computer, copy the signed boot image into the root directory of your tftp server:

<pre class="host">
cp flash-signed.bin /tftproot/opos93-u-boot.bin
</pre>

* On your OPOS93, update U-Boot as usual:

<pre class="code">
BIOS> run update_uboot
</pre>

= Burning SRK hash into the fuses =

* On your host computer, dump the SRK hash:

<pre class="host">
$ od -t x4 SRK_1_2_3_4_fuse.bin
0000000 db2959f2 90dfc39c 53394566 e0b75829
0000020 85e6f3b1 af00983d e5e804fe 7a451024
</pre>

* On the OPOS93, on U-Boot, burn the SRK hash into the fuses.
'''Obviously, don't burn these values but the ones the previous command outputs with your keys !'''

<pre class="host">
BIOS> fuse prog 16 0 0xdb2959f2
BIOS> fuse prog 16 1 0x90dfc39c
BIOS> fuse prog 16 2 0x53394566
BIOS> fuse prog 16 3 0xe0b75829
BIOS> fuse prog 16 4 0x85e6f3b1
BIOS> fuse prog 16 5 0xaf00983d
BIOS> fuse prog 16 6 0xe5e804fe
BIOS> fuse prog 16 7 0x7a451024
</pre>

= Checking =

* Power off / on the board, and stop the boot into U-Boot. Run the ahab_status command. If everything is ok, there should be no AHAB events:

<pre class="code">
BIOS> ahab_status
Lifecycle: 0x00000008, OEM Open

No Events Found!
</pre>

= Closing the OPOS93 =

{{Warning|Before closing your OPOS93, make sure everything is ok (double or triple check...), there is no AHAB events and you are able to boot a signed image. A missigned boot image on a closed OPOS93 will make your OPOS93 unrecoverable !}}

* To close your OPOS93, run the '''ahab_close''' command:

<pre class="host">
BIOS> ahab_close
</pre>

* Reboot and check with the '''ahab_status''' command:

<pre class="host">
BIOS> ahab_status
Lifecycle: 0x00000020, OEM Closed

No Events Found!
</pre>

Secure boot on OPOS93

2024-10-07T16:21:34Z

SebastienSz: Created page with "= Introduction = This document is a quick how-to boot a signed boot firmware on the OPOS93 SoM. It summarizes the documents provided by NXP: * [https://www.nxp.com/doc/an12312 AN12312] * https://github.com/nxp-imx/uboot-imx/blob/lf-6.1.22-2.0.0/doc/imx/ahab/introduction_ahab.txt * https://github.com/nxp-imx/uboot-imx/blob/lf-6.6.36-2.1.0/doc/imx/ahab/guides/mx8ulp_9x_secure_boot.txt = Requirements = == IMX CST TOOL == * Download the [https://www.nxp.com/webapp/Down..."

= Introduction =

This document is a quick how-to boot a signed boot firmware on the OPOS93 SoM. It summarizes the documents provided by NXP:

* [https://www.nxp.com/doc/an12312 AN12312]
* https://github.com/nxp-imx/uboot-imx/blob/lf-6.1.22-2.0.0/doc/imx/ahab/introduction_ahab.txt
* https://github.com/nxp-imx/uboot-imx/blob/lf-6.6.36-2.1.0/doc/imx/ahab/guides/mx8ulp_9x_secure_boot.txt

= Requirements =

== IMX CST TOOL ==

* Download the [https://www.nxp.com/webapp/Download?colCode=IMX_CST_TOOL_NEW IMX CST TOOL] and unarchive it:

<pre class="host">
tar xf IMX_CST_TOOL_NEW.tgz
</pre>

== imx-mkimage ==

* Checkout the imx-mkimage:

<pre class="host">
git clone -b lf-6.6.36-2.1.0 https://github.com/nxp-imx/imx-mkimage.git
</pre>

== Latest Armadeus U-Boot ==

* Make sure you have the latest Armadeus U-Boot installed on you OPOS93 SoM. It must have the '''ahab_status''' commands:

<pre class="code">
BIOS> ahab_status
Lifecycle: 0x00000008, OEM Open
...
</pre>

If the command is not available on your OPOS93 SoM, update to the latest Armadeus U-Boot.

= Generating a PKI tree =

* To generate your PKI tree, go to the CST TOOL directory and use the script '''ahab_pki_tree.sh''':

<pre class="host">
$ cd cst-3.4.1/
$ ./keys/ahab_pki_tree.sh
...
Do you want to use an existing CA key (y/n)?: n
Do you want to use Elliptic Curve Cryptography (y/n)?: y
Enter length for elliptic curve to be used for PKI tree:
Possible values p256, p384, p521: p384
Enter the digest algorithm to use: sha384
Enter PKI tree duration (years): 5
Do you want the SRK certificates to have the CA flag set? (y/n)?: y
</pre>

= Generating SRK Table and SRK Hash =

* Generate the SRK Table and SRK Hash with '''srktool''':

<pre class="host">
$ cd crts/
$ ../linux64/bin/srktool -a -d sha256 -s sha384 -t SRK_1_2_3_4_table.bin \
-e SRK_1_2_3_4_fuse.bin -f 1 -c \
SRK1_sha384_secp384r1_v3_usr_crt.pem,\
SRK2_sha384_secp384r1_v3_usr_crt.pem,\
SRK3_sha384_secp384r1_v3_usr_crt.pem,\
SRK4_sha384_secp384r1_v3_usr_crt.pem
</pre>

* Regenerate the SRK HASH (SRK_1_2_3_4_fuse.bin) by using SHA256 with SRK_1_2_3_4_table.bin:

<pre class="host">
$ openssl dgst -binary -sha256 SRK_1_2_3_4_table.bin > SRK_1_2_3_4_fuse.bin
</pre>

* Check if the hash in the SRK_1_2_3_4_fuse.bin is correct:

<pre class="host">
$ hexdump -C SRK_1_2_3_4_fuse.bin
0000000 db2959f2 90dfc39c 53394566 e0b75829
0000020 85e6f3b1 af00983d e5e804fe 7a451024

$ sha256sum SRK_1_2_3_4_table.bin
db2959f290dfc39c53394566e0b7582985e6f3b1af00983de5e804fe7a451024 SRK_1_2_3_4_table.bin
</pre>

= Signing the boot image =

* From the images directory of the Armadeus BSP, copy the files needed to generate a boot image (SPL, U-Boot proper, ATF) into the i.MX93 directory of the imx-mkimage tool:

<pre class="host">
$ cp <path to BSP Armadeus>/images/u-boot.bin <path to imx-mkimage>/iMX93/
$ cp <path to BSP Armadeus>/images/u-boot-spl.bin <path to imx-mkimage>/iMX93/
$ cp <path to BSP Armadeus>/images/bl31.bin <path to imx-mkimage>/iMX93/
$ cp <path to BSP Armadeus>/images/lpddr4* <path to imx-mkimage>/iMX93/
$ cp <path to BSP Armadeus>/images/ahab-container.img <path to imx-mkimage>/iMX93/mx93a1-ahab-container.img
</pre>

== Signing ATF + U-Boot proper Image container ==

* Generate the u-boot-atf-container.img file:

<pre class="host">
$ cd <path to imx-mkimage>
$ make SOC=iMX9 u-boot-atf-container.img
</pre>

* Note the offset the imx-mkimage tool outputs:

<pre class="host">
CST: CONTAINER 0 offset: 0x0
CST: CONTAINER 0: Signature Block: offset is at 0x110
Offsets = 0x0 0x110
</pre>

* A CSF description file is needed to sign the u-boot-atf-container.img file. You can download one [https://github.com/nxp-imx/uboot-imx/raw/refs/tags/lf-6.6.36-2.1.0/doc/imx/ahab/csf_examples/csf_uboot_atf.txt here]. In this file, update the offset you previously noted and the eventually the name and path of the keys:

<pre class="host">
...
Source = "../crts/SRK1_sha384_secp384r1_v3_ca_crt.pem"
...
[Authenticate Data]
# Binary to be signed generated by mkimage
File = "u-boot-atf-container.img"
# Offsets = Container header Signature block
Offsets = 0x0 0x110
</pre>

* Sign the u-boot-atf-container.img with the CST TOOL:

<pre class="host">
$ cd <path to CST TOOL>
$ ./linux64/bin/cst -i ~/Downloads/csf_uboot_atf.txt -o signed-u-boot-atf-container.img
</pre>

* Replace the u-boot-atf-container.img file with the signed-u-boot-atf-container.img file in the iMX93 directory of the imx-mkimage tool:

<pre class="host">
$ cp signed-u-boot-atf-container.img <path to imx-mkimage>/iMX93/u-boot-atf-container.img
</pre>

== Signing the boot image ==

* Generate the flash.bin file:

<pre class="host">
$ cd <path to imx-mkimage>
$ make SOC=iMX9 flash_singleboot
</pre>

* Note the offset the imx-mkimage tool outputs:

<pre class="host">
CST: CONTAINER 0 offset: 0x400
CST: CONTAINER 0: Signature Block: offset is at 0x490
Offsets = 0x400 0x490
</pre>

* Another CSF description file is needed to sign the flash.bin file. You can download it [https://github.com/nxp-imx/uboot-imx/raw/refs/tags/lf-6.6.36-2.1.0/doc/imx/ahab/csf_examples/csf_boot_image.txt here]. In this file, update the offset you previously noted and the eventually the name of the keys:

<pre class="host">
...
Source = "../crts/SRK1_sha384_secp384r1_v3_ca_crt.pem"
...
[Authenticate Data]
# Binary to be signed generated by mkimage
File = "/home/sszy/development/imx-mkimage/iMX93/flash.bin"
# Offsets = Container header Signature block (printed out by mkimage)
Offsets = 0x400 0x490
</pre>

* Sign the flash.bin file with the CST TOOL:

<pre class="host">
$ cd <path to CST TOOL>
$ ./linux64/bin/cst -i ~/Downloads/csf_boot_image.txt -o signed-flash.bin
</pre>

= Flashing U-Boot =

* On your computer, copy the signed boot image into the root directory of your tftp server:

<pre class="host">
cp flash-signed.bin /tftproot/opos93-u-boot.bin
</pre>

* On your OPOS93, update U-Boot as usual:

<pre class="code">
BIOS> run update_uboot
</pre>

= Burning SRK hash into the fuses =

* On your host computer, dump the SRK hash:

<pre class="host">
$ od -t x4 SRK_1_2_3_4_fuse.bin
0000000 db2959f2 90dfc39c 53394566 e0b75829
0000020 85e6f3b1 af00983d e5e804fe 7a451024
</pre>

* On the OPOS93, on U-Boot, burn the SRK hash into the fuses.
'''Obviously, don't burn these values but the ones the previous command outputs with your keys !'''

<pre class="host">
BIOS> fuse prog 16 0 0xdb2959f2
BIOS> fuse prog 16 1 0x90dfc39c
BIOS> fuse prog 16 2 0x53394566
BIOS> fuse prog 16 3 0xe0b75829
BIOS> fuse prog 16 4 0x85e6f3b1
BIOS> fuse prog 16 5 0xaf00983d
BIOS> fuse prog 16 6 0xe5e804fe
BIOS> fuse prog 16 7 0x7a451024
</pre>

= Checking =

* Power off / on the board, and stop the boot into U-Boot. Run the ahab_status command. If everything is ok, there should be no AHAB events:

<pre class="code">
BIOS> ahab_status
Lifecycle: 0x00000008, OEM Open

No Events Found!
</pre>

= Closing the OPOS93 =

{{Warning|Before closing your OPOS93, make sure everything is ok (double or triple check...), there is no AHAB events and you are able to boot a signed image. A missigned boot image on a closed OPOS93 will make your OPOS93 unrecoverable !}}

* To close your OPOS93, run the '''ahab_close''' command:

<pre class="host">
BIOS> ahab_close
</pre>

* Reboot and check with the '''ahab_status''' command:

<pre class="host">
BIOS> ahab_status
Lifecycle: 0x00000020, OEM Closed

No Events Found!
</pre>

OPOS93 PINOUT

2024-02-08T09:59:08Z

SebastienSz:

[[Category: PINOUT]]

= J1 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX93 pad name !! OPOS93 pad name !! Pin !! Pin !! OPOS93 pad name !! i.MX93 pad name !! GPIO !! Comments
|-
|| || || || GND || 1 || 80 || GND || || ||
|-
|| || || || POR_B || 2 || 79 || WDG || WDOG_ANY || GPIO1_IO15 ||
|-
|| || || || ONOFF || 3 || 78 || GND || || ||
|-
|| || || || GND || 4 || 77 || USB2_DN || USB2_DN || ||
|-
|| || || USB2_ID || USB2_ID || 5 || 76 || USB2_DP || USB2_DP || ||
|-
|| || || || GND || 6 || 75 || GND || || ||
|-
|| +1V8 || || ADC_IN2 || ADC_IN2 || 7 || 74 || ADC_IN0 || ADC_IN0 || || +1V8
|-
|| +1V8 || || ADC_IN3 || ADC_IN3 || 8 || 73 || ADC_IN1 || ADC_IN1 || || +1V8
|-
|| || || || GND || 9 || 72 || GND || || ||
|-
|| || GPIO1_IO02 || I2C2_SCL || I2C2_SCL || 10 || 71 || I2C1_SCL || I2C1_SCL || GPIO1_IO00 ||
|-
|| || GPIO1_IO03 || I2C2_SDA || I2C2_SDA || 11 || 70 || I2C1_SDA || I2C1_SDA || GPIO1_IO01 ||
|-
|| || GPIO1_IO06 || UART2_RXD || UART2_RXD || 12 || 69 || UART1_RXD || UART1_RXD || GPIO1_IO04 ||
|-
|| || GPIO1_IO05 || UART2_TXD || UART2_TXD || 13 || 68 || UART1_RXD || UART1_TXD || ||
|-
|| || || || GND || 14 || 67 || GND || || ||
|-
|| || GPIO1_IO12 || SAI1_TXC || SAI1_TXC || 15 || 66 || PDM_CLK || PDM_CLK || GPIO1_IO08 ||
|-
|| || GPIO1_IO11 || SAI1_TXFS || SAI1_TXFS || 16 || 65 || PDM_BIT_STREAM1 || PDM_BIT_STREAM1 || GPIO1_IO10 ||
|-
|| || GPIO1_IO14 || SAI1_RXD0 || SAI1_RXD0 || 17 || 64 || PDM_BIT_STREAM0 || PDM_BIT_STREAM0 || GPIO1_IO09 ||
|-
|| || GPIO1_IO13 || SAI1_TXD0 || SAI1_TXD0 || 18 || 63 || GND || || ||
|-
|| || || || GND || 19 || 62 || GND || || ||
|-
|| || GPIO2_IO00 || GPIO_IO00 || GPIO2_IO00 || 20 || 61 || GPIO2_IO02 || GPIO_IO02 || GPIO2_IO02 ||
|-
|| || GPIO2_IO01 || GPIO_IO01 || GPIO2_IO01 || 21 || 60 || GPIO2_IO03 || GPIO_IO03 || GPIO2_IO03 ||
|-
|| || GPIO2_IO04 || GPIO_IO04 || GPIO2_IO04 || 22 || 59 || GPIO2_IO06 || GPIO_IO06 || GPIO2_IO06 ||
|-
|| || GPIO2_IO05 || GPIO_IO05 || GPIO2_IO05 || 23 || 58 || GPIO2_IO07 || GPIO_IO07 || GPIO2_IO07 ||
|-
|| || GPIO2_IO08 || GPIO_IO08 || GPIO2_IO08 || 24 || 57 || GPIO2_IO10 || GPIO_IO10 || GPIO2_IO10 ||
|-
|| || GPIO2_IO09 || GPIO_IO09 || GPIO2_IO09 || 25 || 56 || GPIO2_IO11 || GPIO_IO11 || GPIO2_IO11 ||
|-
|| || GPIO2_IO12 || GPIO_IO12 || GPIO2_IO12 || 26 || 55 || GPIO2_IO14 || GPIO_IO14 || GPIO2_IO14 ||
|-
|| || GPIO2_IO13 || GPIO_IO13 || GPIO2_IO13 || 27 || 54 || GPIO2_IO15 || GPIO_IO15 || GPIO2_IO15 ||
|-
|| || GPIO2_IO16 || GPIO_IO16 || GPIO2_IO16 || 28 || 53 || GPIO2_IO18 || GPIO_IO18 || GPIO2_IO18 ||
|-
|| || GPIO2_IO17 || GPIO_IO17 || GPIO2_IO17 || 29 || 52 || GPIO2_IO19 || GPIO_IO19 || GPIO2_IO19 ||
|-
|| || GPIO2_IO20 || GPIO_IO20 || GPIO2_IO20 || 30 || 51 || GPIO2_IO22 || GPIO_IO22 || GPIO2_IO22 ||
|-
|| || GPIO2_IO21 || GPIO_IO21 || GPIO2_IO21 || 31 || 50 || GPIO2_IO23 || GPIO_IO23 || GPIO2_IO23 ||
|-
|| || || || GND || 32 || 49 || GND || || ||
|-
|| || GPIO3_IO05 || SD2_DAT2 || SD2_DAT2 || 33 || 48 || GPIO2_24 || GPIO_IO24 || GPIO2_IO24 ||
|-
|| || GPIO3_IO05 || SD2_DAT3 || SD2_DAT3 || 34 || 47 || GPIO2_25 || GPIO_IO25 || GPIO2_IO25 ||
|-
|| || GPIO3_IO02 || SD2_CMD || SD2_CMD || 35 || 46 || GPIO2_26 || GPIO_IO26 || GPIO2_IO26 ||
|-
|| || GPIO3_IO01 || SD2_CLK || SD2_CLK || 37 || 45 || GPIO2_27 || GPIO_IO27 || GPIO2_IO27 ||
|-
|| || GPIO3_IO03 || SD2_DAT0 || SD2_DAT0 || 37 || 44 || GPIO2_28 || GPIO_IO28 || GPIO2_IO28 ||
|-
|| || GPIO3_IO04 || SD2_DAT1 || SD2_DAT1 || 38 || 43 || GPIO2_29 || GPIO_IO29 || GPIO2_IO29 ||
|-
|| || || || GND || 38 || 43 || GND || || ||
|-
||/!\ Do Not Use /!\ || || || 0V8_SOC || 40 || 41 || VDD_1V8 || || || 100mA maximum !
|-
|}

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX93 pad name !! OPOS93 pad name !! Pin !! Pin !! OPOS93 pad name !! i.MX93 pad name !! GPIO !! Comments
|-
|| || || || GND || 1 || 80 || GND || || ||
|-
|| || || || MIPI_DSI_D0N || 2 || 79 || LVDS_D0N || || ||
|-
|| || || || MIPI_DSI_D0P || 3 || 78 || LVDS_D0P || || ||
|-
|| || || || MIPI_DSI_D1N || 4 || 77 || LVDS_D1N || || ||
|-
|| || || || MIPI_DSI_D1P || 5 || 76 || LVDS_D1P || || ||
|-
|| || || || GND || 6 || 75 || GND || || ||
|-
|| || || || MIPI_DSI_CLKN || 7 || 74 || LVDS_CLKN || || ||
|-
|| || || || MIPI_DSI_CLKP || 8 || 73 || LVDS_CLKP || || ||
|-
|| || || || GND || 9 || 72 || GND || || ||
|-
|| || || || MIPI_DSI_D2N || 10 || 71 || LVDS_D2N || || ||
|-
|| || || || MIPI_DSI_D2P || 11 || 70 || LVDS_D2P || || ||
|-
|| || || || MIPI_DSI_D3N || 12 || 69 || LVDS_D3N || || ||
|-
|| || || || MIPI_DSI_D3P || 13 || 68 || LVDS_D3P || || ||
|-
|| || || || GND || 14 || 67 || GND || || ||
|-
|| || || || NVCC_DRAM_1V1 || 15 || 66 || USB1_DP || || ||
|-
|| || || USB1_ID || USB1_ID || 16 || 65 || USB1_DN || || ||
|-
|| 1V8 max || GPIO4_IO14 || ENET2_MDC || ENET2_MDC || 17 || 64 || GND || || ||
|-
|| 1V8 max || GPIO4_IO15 || ENET2_MDIO || ENET2_MDIO || 18 || 63 || ENET2_RXD0 || ENET2_RD0 || GPIO4_IO24 || 1V8 max
|-
|| || || || GND || 19 || 62 || ENET2_RXD1 || ENET2_RD1 || GPIO4_IO25 || 1V8 max
|-
|| || || MIPI_CSI_D0N || MIPI_CSI_D0N || 20 || 61 || ENET2_RDX2 || ENET2_RD2 || GPIO4_IO26 || 1V8 max
|-
|| || || MIPI_CSI_D0P || MIPI_CSI_D0P || 21 || 60 || ENET2_RXD3 || ENET2_RD3 || GPIO4_IO27 || 1V8 max
|-
|| || || MIPI_CSI_D1N || MIPI_CSI_D1N || 22 || 59 || ENET2_RXEN || ENET2_RX_CTL || GPIO4_IO22 || 1V8 max
|-
|| || || MIPI_CSI D1P || MIPI_CSI_D1P || 23 || 58 || ENET2_RXC || ENET2_RXC || GPIO4_IO23 || 1V8 max
|-
|| || || MIPI_CSI_CLKN || MIPI_CSI_CLKN || 24 || 57 || ENET2_TXD0 || ENET2_TD0 || GPIO4_IO19 || 1V8 max
|-
|| || || MIPI_CSI_CLKP || MIPI_CSI_CLKP || 25 || 56 || ENET2_TXD1 || ENET2_TD1 || GPIO4_IO18 || 1V8 max
|-
|| || || || GND || 26 || 55 || ENET2_TXD2 || ENET2_TD2 || GPIO4_IO17 || 1V8 max
|-
|| || || || ETH1_TRXN3 || 27 || 54 || ENET2_TXD3 || ENET2_TD3 || GPIO4_IO16 || 1V8 max
|-
|| || || || ETH1_TRXP3 || 28 || 53 || ENET2_TXEN || ENET2_TX_CTL || GPIO4_IO20 || 1V8 max
|-
|| || || || GND || 29 || 52 || ENET2_TXC || ENET2_TXC || GPIO4_IO21 || 1V8 max
|-
|| || || || ETH1_TRXN2 || 30 || 51 || GND || || ||
|-
|| || || || ETH1_TRXP2 || 31 || 50 || VDD_3V3 || || || Output +3V3. Should be used to power external peripheral / buffer
|-
|| || || || GND || 32 || 49 || VDD_3V3 || || || Output +3V3. Should be used to power external peripheral / buffer
|-
|| || || || ETH1_TRXN1 || 33 || 48 || VIN || || || Input power supply +3V3.
|-
|| || || || ETH1_TRXP1 || 34 || 47 || VIN || || || Input power supply +3V3.
|-
|| || || || GND || 35 || 46 || VIN || || || Input power supply +3V3.
|-
|| || || || ETH1_TRXN0 || 36 || 45 || VIN || || || Input power supply +3V3.
|-
|| || || || ETH1_TRXP0 || 37 || 44 || VIN || || || Input power supply +3V3.
|-
|| || || || GND || 38 || 43 || VIN || || || Input power supply +3V3.
|-
|| Active high 3V3 || || || ENET1_ACT || 39 || 42 || VIN || || || Input power supply +3V3.
|-
|| Active high 3V3 || || || ENET1_100M || 40 || 41 || VIN || || || Input power supply +3V3.
|-
|}

OPOS93 PINOUT

2024-02-07T13:22:37Z

SebastienSz: Created page with "Category: PINOUT = J1 connector = {| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;" ! Comments !! GPIO !! i.MX93 pad n..."

Santek ST070015

2023-02-17T08:53:36Z

SebastienSz:

== Introduction ==
800x480 7" TFT LCD, proposed as default LCD module on [[APF27Dev]] / [[APF28Dev]] / [[APF51Dev]] / [[APF6Dev]] / [[OPOS6UL]], since start of year 2014.

=Description=
{{Note| '''The Santek ST070015 replaces the [[Chimei_LW700|LW700_adapt]] board.'''}}

This adapter board allows you to connect a [http://www.armadeus.com/english/products-peripherals-st0700_adapt.html LCD] to your DevFull. 
The following table summarizes the possibilities to connect the LQW700AT and the Touchscreen to your development board:

{| border="1" cellpadding="5" cellspacing="0" summary="Connection table"
|- style="background:#efefef;"
! ''' ''' || '''OPOS6ULDEV'''
|----------------
| '''TFT usage''' || flat cable (1) connected between TFT_J21 of the OPOS6ULDev and X5 of the LCD_Adapt [[Image:ST0700_Adapt_to_OPOS6ULDev.jpg|Connection between OPOS6ULDev and ST070015_Adapt]]
|----------------
| '''Touchscreen usage''' || All touchscreen signal are provided by main flat cable.
|-
|}
== Links ==
* [http://www.armadeus.com/english/products-peripherals-st0700_adapt.html Description of armadeus ST070015_adapt]

OPOS8MM PINOUT

2021-12-09T14:04:21Z

SebastienSz: /* J2 connector */ Fix GPIOs on pin 49 and 48

[[Category: PINOUT]]

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07 ||
|-
|| || || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08 ||
|-
|| || || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06 ||
|-
|| || || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09 ||
|-
|| || || || GND || 5 || 66 || GND || || ||
|-
|| || || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11 ||
|-
|| || || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12 ||
|-
|| || || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10 ||
|-
|| || || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13 ||
|-
|| || || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || || ||
|-
|| || || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23 ||
|-
|| || || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24 ||
|-
|| || || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22 ||
|-
|| || || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25 ||
|-
|| || || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19 ||
|-
|| || || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18 ||
|-
|| || || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17 ||
|-
|| || || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16 ||
|-
|| || || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21 ||
|-
|| || || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20 ||
|-
|| || || || GND || 21 || 50 || GND || || ||
|-
|| || || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO27 ||
|-
|| || || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO26 ||
|-
|| || || MIPI_CSI_D3_N || CSI_D3_N || 24 || style="background: yellow;" | 47 || style="background: yellow;" | UART4_TXD || style="background: yellow;" | UART4_TXD || style="background: yellow;" | GPIO5_IO29 || style="background: yellow;" rowspan="2" | Default debug UART in Armadeus BSP.
|-
|| || || MIPI_CSI_D3_P || CSI_D3_P || 25 || style="background: yellow;" | 46 || style="background: yellow;" | UART4_RXD || style="background: yellow;" | UART4_RXD || style="background: yellow;" | GPIO5_IO28
|-
|| || || || GND || 26 || 45 || GND || || ||
|-
|| || || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN || ||
|-
|| || || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP || ||
|-
|| || || || GND || 29 || 42 || USB1_ID || USB1_ID || ||
|-
|| || || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS || ||
|-
|| || || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || || ||
|-
|| || || || GND || 32 || 39 || USB2_DN || USB2_DN || ||
|-
|| || || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP || ||
|-
|| || || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID || ||
|-
|| || || || GND || 35 || 36 || RTC_VDD || || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 70 || VIN || || ||
|-
|| || || || VIN || 2 || 69 || VIN || || ||
|-
|| || || || VIN || 3 || 68 || VIN || || ||
|-
|| || || || VIN || 4 || 67 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip. || GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29
|-
|| || GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| || GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| || GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| || GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| || GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| || GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| || GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| || GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| || GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| || GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| || GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| || GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| || GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| || GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| || GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| || GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| || GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| || GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || || GND || 30 || 41 || GND || || ||
|-
|| || GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| || GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || || GND || 33 || 38 || GND || || ||
|-
|| || || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-06-11T09:53:51Z

SebastienSz:

[[Category: PINOUT]]

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07 ||
|-
|| || || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08 ||
|-
|| || || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06 ||
|-
|| || || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09 ||
|-
|| || || || GND || 5 || 66 || GND || || ||
|-
|| || || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11 ||
|-
|| || || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12 ||
|-
|| || || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10 ||
|-
|| || || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13 ||
|-
|| || || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || || ||
|-
|| || || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23 ||
|-
|| || || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24 ||
|-
|| || || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22 ||
|-
|| || || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25 ||
|-
|| || || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19 ||
|-
|| || || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18 ||
|-
|| || || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17 ||
|-
|| || || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16 ||
|-
|| || || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21 ||
|-
|| || || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20 ||
|-
|| || || || GND || 21 || 50 || GND || || ||
|-
|| || || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26 ||
|-
|| || || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27 ||
|-
|| || || MIPI_CSI_D3_N || CSI_D3_N || 24 || style="background: yellow;" | 47 || style="background: yellow;" | UART4_TXD || style="background: yellow;" | UART4_TXD || style="background: yellow;" | GPIO5_IO29 || style="background: yellow;" rowspan="2" | Default debug UART in Armadeus BSP.
|-
|| || || MIPI_CSI_D3_P || CSI_D3_P || 25 || style="background: yellow;" | 46 || style="background: yellow;" | UART4_RXD || style="background: yellow;" | UART4_RXD || style="background: yellow;" | GPIO5_IO28
|-
|| || || || GND || 26 || 45 || GND || || ||
|-
|| || || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN || ||
|-
|| || || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP || ||
|-
|| || || || GND || 29 || 42 || USB1_ID || USB1_ID || ||
|-
|| || || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS || ||
|-
|| || || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || || ||
|-
|| || || || GND || 32 || 39 || USB2_DN || USB2_DN || ||
|-
|| || || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP || ||
|-
|| || || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID || ||
|-
|| || || || GND || 35 || 36 || RTC_VDD || || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 70 || VIN || || ||
|-
|| || || || VIN || 2 || 69 || VIN || || ||
|-
|| || || || VIN || 3 || 68 || VIN || || ||
|-
|| || || || VIN || 4 || 67 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip. || GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29
|-
|| || GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| || GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| || GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| || GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| || GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| || GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| || GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| || GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| || GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| || GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| || GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| || GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| || GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| || GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| || GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| || GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| || GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| || GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || || GND || 30 || 41 || GND || || ||
|-
|| || GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| || GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || || GND || 33 || 38 || GND || || ||
|-
|| || || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MP PINOUT

2021-06-01T07:20:48Z

SebastienSz: /* J4 connector */

= J3 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MP pad name !! OPOS8MP pad name !! Pin !! Pin !! OPOS8MP pad name !! i.MX8MP pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 120 || VIN || || ||
|-
|| || || || VIN || 2 || 119 || VIN || || ||
|-
|| || || || GND || 3 || 118 || VIN || || ||
|-
|| || || || GND || 4 || 117 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 116 || SYS_RST_B || || ||
|-
|| || || || NVCC_SVNS_1V8 || 6 || 115 || UART2_TXD || UART2_TXD || ||
|-
|| || || || GND || 7 || 114 || UART2_RXD || UART2_RXD || ||
|-
|rowspan="2" | Not available on OPOS8MP SoM with Bluetooth chip. || GPIO5_22 || UART1_RXD || UART1_RXD || 8 || 113 || UART4_RXD || UART4_RXD || GPIO5_28 || rowspan="2" | Default debug UART in Armadeus BSP.
|-
|| GPIO5_23 || UART4_TXD || UART4_TXD || 9 || 112 || UART4_TXD || UART4_TXD || GPIO5_29
|-
|| || GPIO5_26 || UART3_RXD || UART3_RXD || 10 || 111 || I2C2_SDA || I2C2_SDA || GPIO5_17 ||
|-
|| || GPIO5_27 || UART3_TXD || UART3_TXD || 11 || 110 || I2C2_SCL || I2C2_SCL || GPIO5_16 ||
|-
|| || GPIO5_19 || I2C3_SDA || I2C3_SDA || 12 || 109 || GND || || ||
|-
|| || GPIO5_18 || I2C3_SCL || I2C3_SCL || 13 || 108 || UART1_RTS || SAI2_RXD0 || GPIO4_23 || Not available on OPOS8MP SoM with Bluetooth chip.
|-
|| || GPIO5_21 || I2C4_SDA || I2C4_SDA || 14 || 107 || SAI2_RXFS || SAI2_RXFS || GPIO4_21 ||
|-
|| || GPIO5_20 || I2C4_SCL || I2C4_SCL || 15 || 106 || SAI2_RXC || SAI2_RXC || GPIO4_22 ||
|-
|| || || || GND || 16 || 105 || SAI2_TXD0 || SAI2_TXD0 || GPIO4_26 ||
|-
|| || GPIO4_3 || SAI1_RXD1 || SAI1_RXD1 || 17 || 104 || UART1_CTS || SAI2_TXFS || GPIO4_24 || Not available on OPOS8MP SoM with Bluetooth chip.
|-
|| || GPIO4_2 || SAI1_RXD0 || SAI1_RXD0 || 18 || 103 || SAI2_TXC || SAI2_TXC || GPIO4_25 ||
|-
|| || GPIO4_20 || SAI1_MCLK || SAI1_MCLK || 19 || 102 || SAI2_MCLK || SAI2_MCLK || GPIO4_27 ||
|-
|| || GPIO4_18 || SAI1_TXD6 || SAI1_TXD6 || 20 || 101 || SAI3_RXD || SAI3_RXD || GPIO4_30 ||
|-
|| || GPIO4_19 || SAI1_TXD7 || SAI1_TXD7 || 21 || 100 || SAI3_RXFS || SAI3_RXFS || GPIO4_28 ||
|-
|| || GPIO3_24 || SAI5_RXD3 || SAI5_RXD3 || 22 || 99 || SAI3_RXC || SAI3_RXC || GPIO4_29 ||
|-
|| || GPIO3_23 || SAI5_RXD2 || SAI5_RXD2 || 23 || 98 || SAI3_TXD || SAI3_TXD || GPIO5_1 ||
|-
|| || GPIO3_22 || SAI5_RXD1 || SAI5_RXD1 || 24 || 97 || SAI3_TXFS || SAI3_TXFS || GPIO4_31 ||
|-
|| || GPIO3_21 || SAI5_RXD0 || SAI5_RXD0 || 25 || 96 || SAI3_TXC || SAI3_TXC || GPIO5_0 ||
|-
|| || GPIO3_19 || SAI5_RXFS || SAI5_RXFS || 26 || 95 || SAI3_MCLK || SAI3_MCLK || GPIO5_2 ||
|-
|| || GPIO3_20 || SAI5_RXC || SAI5_RXC || 27 || 94 || GND || || ||
|-
|| || GPIO3_25 || SAI5_MCLK || SAI5_MCLK || 28 || 93 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_10 ||
|-
|| || GPIO5_3 || SPDIF_TX || SPDIF_TX || 29 || 92 || ECSPI2_SS0 || ECSPI2_SCLK || GPIO5_13 ||
|-
|| || GPIO5_4 || SPDIF_TX || SPDIF_TX || 30 || 91 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_12 ||
|-
|| || GPIO5_5 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 31 || 90 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_11 ||
|-
|| || || || GND || 32 || 89 || GND || || ||
|-
|| || GPIO5_6 || ECSPI1_SCLK || ECSPI1_SCLK || 33 || 88 || HDMI_TXC_N || || ||
|-
|| || GPIO5_9 || ECSPI1_SS0 || ECSPI1_SS0 || 34 || 87 || HDMI_TXC_P || || ||
|-
|| || GPIO5_12 || ECSPI1_MISO || ECSPI1_MISO || 35 || 86 || GND || || ||
|-
|| || GPIO5_11 || ECSPI1_MOSI || ECSPI1_MOSI || 36 || 85 || HDMI_TX0_N || || ||
|-
|| || GPIO2_12 || SD2_CD_B || SD2_CD_B || 37 || 84 || HDMI_TX0_P || || ||
|-
|| || GPIO2_15 || SD2_DAT0 || SD2_DAT0 || 38 || 83 || GND || || ||
|-
|| || GPIO2_16 || SD2_DAT1 || SD2_DAT1 || 39 || 82 || HDMI_TX1_N || || ||
|-
|| || GPIO2_14 || SD2_CMD || SD2_CMD || 40 || 81 || HDMI_TX1_P || || ||
|-
|| || || || GND || 41 || 80 || GND || || ||
|-
|| || GPIO2_13 || SD2_CLK || SD2_CLK || 42 || 79 || HDMI_CEC || HDMI_CEC || GPIO3_28 ||
|-
|| || || || GND || 43 || 78 || HDMI_DDC_SCL || HDMI_DDC_SCL || GPIO3_26 ||
|-
|| || GPIO_2_18 || SD2_DAT3 || SD2_DAT3 || 44 || 77 || HDMI_DDC_SDA || HDMI_DDC_SDA || GPIO3_27 ||
|-
|| || GPIO_2_17 || SD2_DAT2 || SD2_DAT2 || 45 || 76 || HDMI_HDP || HDMI_HDP || GPIO3_26 ||
|-
|| || || || GND || 46 || 75 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_A || 47 || 74 || ETH_TXRXP_A || || ||
|-
|| || || || ETH_QOS_TXRXM_A || 48 || 73 || ETH_TXRXM_A || || ||
|-
|| || || || GND || 49 || 72 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_B || 50 || 74 || ETH_TXRXP_B || || ||
|-
|| || || || ETH_QOS_TXRXM_B || 51 || 71 || ETH_TXRXM_B || || ||
|-
|| || || || GND || 52 || 69 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_C || 53 || 68 || ETH_TXRXP_B || || ||
|-
|| || || || ETH_QOS_TXRXM_C || 54 || 67 || ETH_TXRXM_B || || ||
|-
|| || || || GND || 55 || 66 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_D || 56 || 65 || ETH_TXRXP_C || || ||
|-
|| || || || ETH_QOS_TXRXM_D || 57 || 64 || ETH_TXRXM_C || || ||
|-
|| || || || GND || 58 || 63 || GND || || ||
|-
|| || || || ETH_QOS_ACTIVITY# || 59 || 62 || ETH_ACTIVITY# || || ||
|-
|| || || || ETH_QOS_LINK# || 60 || 61 || ETH_LINK# || || ||
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MP pad name !! OPOS8MP pad name !! Pin !! Pin !! OPOS8MP pad name !! i.MX8MP pad name !! GPIO !! Comments
|-
|| || || USB1_RX_N || USB1_RX_N || 1 || 120 || GPIO1_IO15 || GPIO1_IO15 || GPIO1_15 ||
|-
|| || || USB1_RX_P || USB1_RX_P || 2 || 119 || GPIO1_IO14 || GPIO1_IO14 || GPIO1_14 ||
|-
|| || || || GND || 3 || 118 || GPIO1_IO13 || GPIO1_IO13 || GPIO1_13 ||
|-
|| || || USB1_TX_N || USB1_TX_N || 4 || 117 || GPIO1_IO12 || GPIO1_IO12 || GPIO1_12 ||
|-
|| || || USB1_TX_P || USB1_TX_P || 5 || 116 || GPIO1_IO11 || GPIO1_IO11 || GPIO1_11 ||
|-
|| || || || GND || 6 || 115 || GPIO1_IO10 || GPIO1_IO10 || GPIO1_10 ||
|-
|| || || USB2_RX_N || USB2_RX_N || 7 || 114 || GPIO1_IO09 || GPIO1_IO09 || GPIO1_9 ||
|-
|| || || USB2_RX_P || USB2_RX_P || 8 || 113 || GPIO1_IO08 || GPIO1_IO08 || GPIO1_8 ||
|-
|| || || || GND || 9 || 112 || GPIO1_IO07 || GPIO1_IO07 || GPIO1_7 ||
|-
|| || || USB2_TX_N || USB2_TX_N || 10 || 111 || GPIO1_IO06 || GPIO1_IO06 || GPIO1_6 ||
|-
|| || || USB2_TX_P || USB2_TX_P || 11 || 110 || GPIO1_IO05 || GPIO1_IO05 || GPIO1_5 ||
|-
|| || || || GND || 12 || 109 || GPIO1_IO04 || GPIO1_IO04 || GPIO1_4 ||
|-
|| || || PCIE_RX_N || PCIE_RX_N || 13 || 108 || GPIO1_IO01 || GPIO1_IO01 || GPIO1_1 ||
|-
|| || || PCIE_RX_P || PCIE_RX_P || 14 || 107 || GPIO1_IO00 || GPIO1_IO00 || GPIO1_0 ||
|-
|| || || || GND || 15 || 106 || GND || || ||
|-
|| || || PCIE_TX_N || PCIE_TX_N || 16 || 105 || USB1_ID || USB1_ID || ||
|-
|| || || PCIE_TX_P || PCIE_TX_P || 17 || 104 || USB1_VBUS || USB1_VBUS || ||
|-
|| || || || GND || 18 || 103 || USB1_DN || USB1_DN || ||
|-
|| || || PCIE_CLK_N || PCIE_CLK_N || 19 || 102 || USB1_DP || USB1_DP || ||
|-
|| || || PCIE_CLK_P || PCIE_CLK_P || 20 || 101 || GND || || ||
|-
|| || || || GND || 21 || 100 || USB2_ID || USB2_ID || ||
|-
|| || || DSI_DO_P || DSI_DO_P || 22 || 99 || USB2_VBUS || USB2_VBUS || ||
|-
|| || || DSI_DO_N || DSI_DO_N || 23 || 98 || USB2_DN || USB2_DN || ||
|-
|| || || DSI_D1_P || DSI_D1_P || 24 || 97 || USB2_DP || USB2_DP || ||
|-
|| || || DSI_D1_N || DSI_D1_N || 25 || 96 || GND || || ||
|-
|| || || || GND || 26 || 95 || BOOT_MODE0 || BOOT_MODE0 || ||
|-
|| || || DSI_CLK_P || DSI_CLK_P || 27 || 94 || JTAG_TDO || JTAG_TDO || ||
|-
|| || || DSI_CLK_N || DSI_CLK_N || 28 || 93 || JTAG_TMS || JTAG_TMS || ||
|-
|| || || || GND || 29 || 92 || JTAG_TDI || JTAG_TDI || ||
|-
|| || || DSI_D2_P || DSI_D2_P || 30 || 91 || JTAG_TCK || JTAG_TCK || ||
|-
|| || || DSI_D2_N || DSI_D2_N || 31 || 90 || ONOFF || ONOFF || ||
|-
|| || || DSI_D3_P || DSI_D3_P || 32 || 89 || PMIC_ON_REQ || || ||
|-
|| || || DSI_D3_N || DSI_D3_N || 33 || 38 || POR_B || POR_B || ||
|-
|| || || || GND || 34 || 87 || GND || || ||
|-
|| || || CSI2_D3_P || CSI2_D3_P || 35 || 86 || CSI1_D0_P || CSI1_D0_P || ||
|-
|| || || CSI2_D3_N || CSI2_D3_N || 36 || 85 || CSI1_D0_N || CSI1_D0_N || ||
|-
|| || || CSI2_D2_P || CSI2_D2_P || 37 || 84 || CSI1_D1_P || CSI1_D1_P || ||
|-
|| || || CSI2_D2_N || CSI2_D2_N || 38 || 83 || CSI1_D1_N || CSI1_D1_N || ||
|-
|| || || || GND || 39 || 82 || GND || || ||
|-
|| || || CSI2_CLK_P || CSI2_CLK_P || 40 || 81 || CSI1_CLK_P || CSI1_CLK_P || ||
|-
|| || || CSI2_CLK_N || CSI2_CLK_N || 41 || 80 || CSI1_CLK_N || CSI1_CLK_N || ||
|-
|| || || || GND || 42 || 79 || GND || || ||
|-
|| || || CSI2_D1_P || CSI2_D1_P || 43 || 78 || CSI1_D2_P || CSI1_D2_P || ||
|-
|| || || CSI2_D1_N || CSI2_D1_N || 44 || 77 || CSI1_D2_N || CSI1_D2_N || ||
|-
|| || || CSI2_D0_P || CSI2_D0_P || 45 || 76 || CSI1_D3_P || CSI1_D3_P || ||
|-
|| || || CSI2_D0_N || CSI2_D0_N || 46 || 75 || CSI1_D3_N || CSI1_D3_N || ||
|-
|| || || || GND || 47 || 74 || GND || || ||
|-
|| || || LVDS1_D0_P || LVDS1_D0_P || 48 || 73 || LVDS0_D0_P || LVDS0_D0_P || ||
|-
|| || || LVDS1_D0_N || LVDS1_D0_N || 49 || 73 || LVDS0_D0_N || LVDS0_D0_N || ||
|-
|| || || LVDS1_D1_P || LVDS1_D1_P || 50 || 71 || LVDS0_D1_P || LVDS0_D1_P || ||
|-
|| || || LVDS1_D1_N || LVDS1_D1_N || 51 || 70 || LVDS0_D1_N || LVDS0_D1_N || ||
|-
|| || || || GND || 52 || 69 || GND || || ||
|-
|| || || LVDS1_CLK_P || LVDS1_CLK_P || 53 || 68 || LVDS0_CLK_P || LVDS0_CLK_P || ||
|-
|| || || LVDS1_CLK_N || LVDS1_CLK_N || 54 || 67 || LVDS0_CLK_N || LVDS0_CLK_N || ||
|-
|| || || || GND || 55 || 66 || GND || || ||
|-
|| || || LVDS1_D2_P || LVDS1_D2_P || 56 || 65 || LVDS0_D2_P || LVDS0_D2_P || ||
|-
|| || || LVDS1_D2_N || LVDS1_D2_N || 57 || 64 || LVDS0_D2_N || LVDS0_D2_N || ||
|-
|| || || LVDS1_D3_P || LVDS1_D3_P || 58 || 63 || LVDS0_D3_P || LVDS0_D3_P || ||
|-
|| || || LVDS1_D3_N || LVDS1_D3_N || 59 || 62 || LVDS0_D3_N || LVDS0_D3_N || ||
|-
|| || || || GND || 60 || 61 || GND || || ||
|}

OPOS8MP PINOUT

2021-06-01T07:19:48Z

SebastienSz: /* J3 connector */

= J3 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MP pad name !! OPOS8MP pad name !! Pin !! Pin !! OPOS8MP pad name !! i.MX8MP pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 120 || VIN || || ||
|-
|| || || || VIN || 2 || 119 || VIN || || ||
|-
|| || || || GND || 3 || 118 || VIN || || ||
|-
|| || || || GND || 4 || 117 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 116 || SYS_RST_B || || ||
|-
|| || || || NVCC_SVNS_1V8 || 6 || 115 || UART2_TXD || UART2_TXD || ||
|-
|| || || || GND || 7 || 114 || UART2_RXD || UART2_RXD || ||
|-
|rowspan="2" | Not available on OPOS8MP SoM with Bluetooth chip. || GPIO5_22 || UART1_RXD || UART1_RXD || 8 || 113 || UART4_RXD || UART4_RXD || GPIO5_28 || rowspan="2" | Default debug UART in Armadeus BSP.
|-
|| GPIO5_23 || UART4_TXD || UART4_TXD || 9 || 112 || UART4_TXD || UART4_TXD || GPIO5_29
|-
|| || GPIO5_26 || UART3_RXD || UART3_RXD || 10 || 111 || I2C2_SDA || I2C2_SDA || GPIO5_17 ||
|-
|| || GPIO5_27 || UART3_TXD || UART3_TXD || 11 || 110 || I2C2_SCL || I2C2_SCL || GPIO5_16 ||
|-
|| || GPIO5_19 || I2C3_SDA || I2C3_SDA || 12 || 109 || GND || || ||
|-
|| || GPIO5_18 || I2C3_SCL || I2C3_SCL || 13 || 108 || UART1_RTS || SAI2_RXD0 || GPIO4_23 || Not available on OPOS8MP SoM with Bluetooth chip.
|-
|| || GPIO5_21 || I2C4_SDA || I2C4_SDA || 14 || 107 || SAI2_RXFS || SAI2_RXFS || GPIO4_21 ||
|-
|| || GPIO5_20 || I2C4_SCL || I2C4_SCL || 15 || 106 || SAI2_RXC || SAI2_RXC || GPIO4_22 ||
|-
|| || || || GND || 16 || 105 || SAI2_TXD0 || SAI2_TXD0 || GPIO4_26 ||
|-
|| || GPIO4_3 || SAI1_RXD1 || SAI1_RXD1 || 17 || 104 || UART1_CTS || SAI2_TXFS || GPIO4_24 || Not available on OPOS8MP SoM with Bluetooth chip.
|-
|| || GPIO4_2 || SAI1_RXD0 || SAI1_RXD0 || 18 || 103 || SAI2_TXC || SAI2_TXC || GPIO4_25 ||
|-
|| || GPIO4_20 || SAI1_MCLK || SAI1_MCLK || 19 || 102 || SAI2_MCLK || SAI2_MCLK || GPIO4_27 ||
|-
|| || GPIO4_18 || SAI1_TXD6 || SAI1_TXD6 || 20 || 101 || SAI3_RXD || SAI3_RXD || GPIO4_30 ||
|-
|| || GPIO4_19 || SAI1_TXD7 || SAI1_TXD7 || 21 || 100 || SAI3_RXFS || SAI3_RXFS || GPIO4_28 ||
|-
|| || GPIO3_24 || SAI5_RXD3 || SAI5_RXD3 || 22 || 99 || SAI3_RXC || SAI3_RXC || GPIO4_29 ||
|-
|| || GPIO3_23 || SAI5_RXD2 || SAI5_RXD2 || 23 || 98 || SAI3_TXD || SAI3_TXD || GPIO5_1 ||
|-
|| || GPIO3_22 || SAI5_RXD1 || SAI5_RXD1 || 24 || 97 || SAI3_TXFS || SAI3_TXFS || GPIO4_31 ||
|-
|| || GPIO3_21 || SAI5_RXD0 || SAI5_RXD0 || 25 || 96 || SAI3_TXC || SAI3_TXC || GPIO5_0 ||
|-
|| || GPIO3_19 || SAI5_RXFS || SAI5_RXFS || 26 || 95 || SAI3_MCLK || SAI3_MCLK || GPIO5_2 ||
|-
|| || GPIO3_20 || SAI5_RXC || SAI5_RXC || 27 || 94 || GND || || ||
|-
|| || GPIO3_25 || SAI5_MCLK || SAI5_MCLK || 28 || 93 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_10 ||
|-
|| || GPIO5_3 || SPDIF_TX || SPDIF_TX || 29 || 92 || ECSPI2_SS0 || ECSPI2_SCLK || GPIO5_13 ||
|-
|| || GPIO5_4 || SPDIF_TX || SPDIF_TX || 30 || 91 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_12 ||
|-
|| || GPIO5_5 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 31 || 90 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_11 ||
|-
|| || || || GND || 32 || 89 || GND || || ||
|-
|| || GPIO5_6 || ECSPI1_SCLK || ECSPI1_SCLK || 33 || 88 || HDMI_TXC_N || || ||
|-
|| || GPIO5_9 || ECSPI1_SS0 || ECSPI1_SS0 || 34 || 87 || HDMI_TXC_P || || ||
|-
|| || GPIO5_12 || ECSPI1_MISO || ECSPI1_MISO || 35 || 86 || GND || || ||
|-
|| || GPIO5_11 || ECSPI1_MOSI || ECSPI1_MOSI || 36 || 85 || HDMI_TX0_N || || ||
|-
|| || GPIO2_12 || SD2_CD_B || SD2_CD_B || 37 || 84 || HDMI_TX0_P || || ||
|-
|| || GPIO2_15 || SD2_DAT0 || SD2_DAT0 || 38 || 83 || GND || || ||
|-
|| || GPIO2_16 || SD2_DAT1 || SD2_DAT1 || 39 || 82 || HDMI_TX1_N || || ||
|-
|| || GPIO2_14 || SD2_CMD || SD2_CMD || 40 || 81 || HDMI_TX1_P || || ||
|-
|| || || || GND || 41 || 80 || GND || || ||
|-
|| || GPIO2_13 || SD2_CLK || SD2_CLK || 42 || 79 || HDMI_CEC || HDMI_CEC || GPIO3_28 ||
|-
|| || || || GND || 43 || 78 || HDMI_DDC_SCL || HDMI_DDC_SCL || GPIO3_26 ||
|-
|| || GPIO_2_18 || SD2_DAT3 || SD2_DAT3 || 44 || 77 || HDMI_DDC_SDA || HDMI_DDC_SDA || GPIO3_27 ||
|-
|| || GPIO_2_17 || SD2_DAT2 || SD2_DAT2 || 45 || 76 || HDMI_HDP || HDMI_HDP || GPIO3_26 ||
|-
|| || || || GND || 46 || 75 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_A || 47 || 74 || ETH_TXRXP_A || || ||
|-
|| || || || ETH_QOS_TXRXM_A || 48 || 73 || ETH_TXRXM_A || || ||
|-
|| || || || GND || 49 || 72 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_B || 50 || 74 || ETH_TXRXP_B || || ||
|-
|| || || || ETH_QOS_TXRXM_B || 51 || 71 || ETH_TXRXM_B || || ||
|-
|| || || || GND || 52 || 69 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_C || 53 || 68 || ETH_TXRXP_B || || ||
|-
|| || || || ETH_QOS_TXRXM_C || 54 || 67 || ETH_TXRXM_B || || ||
|-
|| || || || GND || 55 || 66 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_D || 56 || 65 || ETH_TXRXP_C || || ||
|-
|| || || || ETH_QOS_TXRXM_D || 57 || 64 || ETH_TXRXM_C || || ||
|-
|| || || || GND || 58 || 63 || GND || || ||
|-
|| || || || ETH_QOS_ACTIVITY# || 59 || 62 || ETH_ACTIVITY# || || ||
|-
|| || || || ETH_QOS_LINK# || 60 || 61 || ETH_LINK# || || ||
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MP pad name !! OPOS8MP pad name !! Pin !! Pin !! OPOS8MP pad name !! i.MX8MP pad name !! GPIO !! Comments
|-
|| || || USB1_RX_N || USB1_RX_N || 1 || 120 || GPIO1_IO15 || GPIO1_IO15 || GPIO1_15 ||
|-
|| || || USB1_RX_P || USB1_RX_P || 2 || 119 || GPIO1_IO14 || GPIO1_IO14 || GPIO1_14 ||
|-
|| || || || GND || 3 || 118 || GPIO1_IO13 || GPIO1_IO13 || GPIO1_13 ||
|-
|| || || USB1_TX_N || USB1_TX_N || 4 || 117 || GPIO1_IO12 || GPIO1_IO12 || GPIO1_12 ||
|-
|| || || USB1_TX_P || USB1_TX_P || 5 || 116 || GPIO1_IO11 || GPIO1_IO11 || GPIO1_11 ||
|-
|| || || || GND || 6 || 115 || GPIO1_IO10 || GPIO1_IO10 || GPIO1_10 ||
|-
|| || || USB2_RX_N || USB2_RX_N || 7 || 114 || GPIO1_IO09 || GPIO1_IO09 || GPIO1_9 ||
|-
|| || || USB2_RX_P || USB2_RX_P || 8 || 113 || GPIO1_IO08 || GPIO1_IO08 || GPIO1_8 ||
|-
|| || || || GND || 9 || 112 || GPIO1_IO07 || GPIO1_IO07 || GPIO1_7 ||
|-
|| || || USB2_TX_N || USB2_TX_N || 10 || 111 || GPIO1_IO06 || GPIO1_IO06 || GPIO1_6 ||
|-
|| || || USB2_TX_P || USB2_TX_P || 11 || 110 || GPIO1_IO05 || GPIO1_IO05 || GPIO1_5 ||
|-
|| || || || GND || 12 || 109 || GPIO1_IO04 || GPIO1_IO04 || GPIO1_4 ||
|-
|| || || PCIE_RX_N || PCIE_RX_N || 13 || 108 || GPIO1_IO01 || GPIO1_IO01 || GPIO1_1 ||
|-
|| || || PCIE_RX_P || PCIE_RX_P || 14 || 107 || GPIO1_IO00 || GPIO1_IO00 || GPIO1_0 ||
|-
|| || || || GND || 15 || 106 || GND || || ||
|-
|| || || PCIE_TX_N || PCIE_TX_N || 16 || 105 || USB1_ID || USB1_ID || ||
|-
|| || || PCIE_TX_P || PCIE_TX_P || 17 || 104 || USB1_VBUS || USB1_VBUS || ||
|-
|| || || || GND || 18 || 103 || USB1_DN || USB1_DN || ||
|-
|| || || PCIE_CLK_N || PCIE_CLK_N || 19 || 102 || USB1_DP || USB1_DP || ||
|-
|| || || PCIE_CLK_P || PCIE_CLK_P || 20 || 101 || GND || || ||
|-
|| || || || GND || 21 || 100 || USB2_ID || USB2_ID || ||
|-
|| || || DSI_DO_P || DSI_DO_P || 22 || 99 || USB2_VBUS || USB2_VBUS || ||
|-
|| || || DSI_DO_N || DSI_DO_N || 23 || 98 || USB2_DN || USB2_DN || ||
|-
|| || || DSI_D1_P || DSI_D1_P || 24 || 97 || USB2_DP || USB2_DP || ||
|-
|| || || DSI_D1_N || DSI_D1_N || 25 || 96 || GND || || ||
|-
|| || || || GND || 26 || 95 || BOOT_MODE0 || BOOT_MODE0 || ||
|-
|| || || DSI_CLK_P || DSI_CLK_P || 27 || 94 || JTAG_TDO || JTAG_TDO || ||
|-
|| || || DSI_CLK_N || DSI_CLK_N || 28 || 93 || JTAG_TMS || JTAG_TMS || ||
|-
|| || || || GND || 29 || 92 || JTAG_TDI || JTAG_TDI || ||
|-
|| || || DSI_D2_P || DSI_D2_P || 30 || 91 || JTAG_TCK || JTAG_TCK || ||
|-
|| || || DSI_D2_N || DSI_D2_N || 31 || 90 || ONOFF || ONOFF || ||
|-
|| || || DSI_D3_P || DSI_D3_P || 32 || 89 || PMIC_ON_REQ || || ||
|-
|| || || DSI_D3_N || DSI_D3_N || 33 || 38 || POR_B || POR_B || ||
|-
|| || || || GND || 34 || 87 || GND || || ||
|-
|| || || CSI2_D3_P || CSI2_D3_P || 35 || 86 || CSI1_D0_P || CSI1_D0_P || ||
|-
|| || || CSI2_D3_N || CSI2_D3_N || 36 || 85 || CSI1_D0_N || CSI1_D0_N || ||
|-
|| || || CSI2_D2_P || CSI2_D2_P || 37 || 84 || CSI1_D1_P || CSI1_D1_P || ||
|-
|| || || CSI2_D2_N || CSI2_D2_N || 38 || 83 || CSI1_D1_N || CSI1_D1_N || ||
|-
|| || || || GND || 39 || 82 || GND || || ||
|-
|| || || CSI2_CLK_P || CSI2_CLK_P || 40 || 81 || CSI1_CLK_P || CSI1_CLK_P || ||
|-
|| || || CSI2_CLK_N || CSI2_CLK_N || 41 || 80 || CSI1_CLK_N || CSI1_CLK_N || ||
|-
|| || || || GND || 42 || 79 || GND || || ||
|-
|| || || CSI2_D1_P || CSI2_D1_P || 43 || 78 || CSI1_D2_P || CSI1_D2_P || ||
|-
|| || || CSI2_D1_N || CSI2_D1_N || 44 || 77 || CSI1_D2_N || CSI1_D2_N || ||
|-
|| || || CSI2_D0_P || CSI2_D0_P || 45 || 76 || CSI1_D3_P || CSI1_D3_P || ||
|-
|| || || CSI2_D0_N || CSI2_D0_N || 46 || 75 || CSI1_D3_N || CSI1_D3_N || ||
|-
|| || || || GND || 47 || 74 || GND || || ||
|-
|| || || LVDS1_D0_P || LVDS1_DO_P || 48 || 73 || LVDS0_D0_P || LVDS0_D0_P || ||
|-
|| || || LVDS1_D0_N || LVDS1_DO_N || 49 || 73 || LVDS0_D0_N || LVDS0_D0_N || ||
|-
|| || || LVDS1_D1_P || LVDS1_D1_P || 50 || 71 || LVDS0_D1_P || LVDS0_D1_P || ||
|-
|| || || LVDS1_D1_N || LVDS1_D1_N || 51 || 70 || LVDS0_D1_N || LVDS0_D1_N || ||
|-
|| || || || GND || 52 || 69 || GND || || ||
|-
|| || || LVDS1_CLK_P || LVDS1_CLK_P || 53 || 68 || LVDS0_CLK_P || LVDS0_CLK_P || ||
|-
|| || || LVDS1_CLK_N || LVDS1_CLK_N || 54 || 67 || LVDS0_CLK_N || LVDS0_CLK_N || ||
|-
|| || || || GND || 55 || 66 || GND || || ||
|-
|| || || LVDS1_D2_P || LVDS1_D2_P || 56 || 65 || LVDS0_D2_P || LVDS0_D2_P || ||
|-
|| || || LVDS1_D2_N || LVDS1_D2_N || 57 || 64 || LVDS0_D2_N || LVDS0_D2_N || ||
|-
|| || || LVDS1_D3_P || LVDS1_D3_P || 58 || 63 || LVDS0_D3_P || LVDS0_D3_P || ||
|-
|| || || LVDS1_D3_N || LVDS1_D3_N || 59 || 62 || LVDS0_D3_N || LVDS0_D3_N || ||
|-
|| || || || GND || 60 || 61 || GND || || ||
|}

OPOS8MP PINOUT

2021-06-01T06:39:31Z

SebastienSz: /* J4 connector */

= J3 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MP pad name !! OPOS8MP pad name !! Pin !! Pin !! OPOS8MP pad name !! i.MX8MP pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 120 || VIN || || ||
|-
|| || || || VIN || 2 || 119 || VIN || || ||
|-
|| || || || GND || 3 || 118 || VIN || || ||
|-
|| || || || GND || 4 || 117 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 116 || SYS_RST_B || || ||
|-
|| || || || NVCC_SVNS_1V8 || 6 || 115 || UART2_TXD || UART2_TXD || ||
|-
|| || || || GND || 7 || 114 || UART2_RXD || UART2_RXD || ||
|-
|rowspan="2" | Not available on OPOS8MP SoM with Bluetooth chip. || GPIO5_22 || UART1_RXD || UART1_RXD || 8 || 113 || UART4_RXD || UART4_RXD || GPIO5_28 || rowspan="2" | Default debug UART in Armadeus BSP.
|-
|| GPIO5_23 || UART1_TXD || UART1_TXD || 9 || 112 || UART1_TXD || UART1_TXD || GPIO5_29
|-
|| || GPIO5_26 || UART3_RXD || UART3_RXD || 10 || 111 || I2C2_SDA || I2C2_SDA || GPIO5_17 ||
|-
|| || GPIO5_27 || UART3_TXD || UART3_TXD || 11 || 110 || I2C2_SCL || I2C2_SCL || GPIO5_16 ||
|-
|| || GPIO5_19 || I2C3_SDA || I2C3_SDA || 12 || 109 || GND || || ||
|-
|| || GPIO5_18 || I2C3_SCL || I2C3_SCL || 13 || 108 || UART1_RTS || SAI2_RXD0 || GPIO4_23 || Not available on OPOS8MP SoM with Bluetooth chip.
|-
|| || GPIO5_21 || I2C4_SDA || I2C4_SDA || 14 || 107 || SAI2_RXFS || SAI2_RXFS || GPIO4_21 ||
|-
|| || GPIO5_20 || I2C4_SCL || I2C4_SCL || 15 || 106 || SAI2_RXC || SAI2_RXC || GPIO4_22 ||
|-
|| || || || GND || 16 || 105 || SAI2_TXD0 || SAI2_TXD0 || GPIO4_26 ||
|-
|| || GPIO4_3 || SAI1_RXD1 || SAI1_RXD1 || 17 || 104 || UART1_CTS || SAI2_TXFS || GPIO4_24 || Not available on OPOS8MP SoM with Bluetooth chip.
|-
|| || GPIO4_2 || SAI1_RXD0 || SAI1_RXD0 || 18 || 103 || SAI2_TXC || SAI2_TXC || GPIO4_25 ||
|-
|| || GPIO4_20 || SAI1_MCLK || SAI1_MCLK || 19 || 102 || SAI2_MCLK || SAI2_MCLK || GPIO4_27 ||
|-
|| || GPIO4_18 || SAI1_TXD6 || SAI1_TXD6 || 20 || 101 || SAI3_RXD || SAI3_RXD || GPIO4_30 ||
|-
|| || GPIO4_19 || SAI1_TXD7 || SAI1_TXD7 || 21 || 100 || SAI3_RXFS || SAI3_RXFS || GPIO4_28 ||
|-
|| || GPIO3_24 || SAI5_RXD3 || SAI5_RXD3 || 22 || 99 || SAI3_RXC || SAI3_RXC || GPIO4_29 ||
|-
|| || GPIO3_23 || SAI5_RXD2 || SAI5_RXD2 || 23 || 98 || SAI3_TXD || SAI3_TXD || GPIO5_1 ||
|-
|| || GPIO3_22 || SAI5_RXD1 || SAI5_RXD1 || 24 || 97 || SAI3_TXFS || SAI3_TXFS || GPIO4_31 ||
|-
|| || GPIO3_21 || SAI5_RXD0 || SAI5_RXD0 || 25 || 96 || SAI3_TXC || SAI3_TXC || GPIO5_0 ||
|-
|| || GPIO3_19 || SAI5_RXFS || SAI5_RXFS || 26 || 95 || SAI3_MCLK || SAI3_MCLK || GPIO5_2 ||
|-
|| || GPIO3_20 || SAI5_RXC || SAI5_RXC || 27 || 94 || GND || || ||
|-
|| || GPIO3_25 || SAI5_MCLK || SAI5_MCLK || 28 || 93 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_10 ||
|-
|| || GPIO5_3 || SPDIF_TX || SPDIF_TX || 29 || 92 || ECSPI2_SS0 || ECSPI2_SCLK || GPIO5_13 ||
|-
|| || GPIO5_4 || SPDIF_TX || SPDIF_TX || 30 || 91 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_12 ||
|-
|| || GPIO5_5 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 31 || 90 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_11 ||
|-
|| || || || GND || 32 || 89 || GND || || ||
|-
|| || GPIO5_6 || ECSPI1_SCLK || ECSPI1_SCLK || 33 || 88 || HDMI_TXC_N || || ||
|-
|| || GPIO5_9 || ECSPI1_SS0 || ECSPI1_SS0 || 34 || 87 || HDMI_TXC_P || || ||
|-
|| || GPIO5_12 || ECSPI1_MISO || ECSPI1_MISO || 35 || 86 || GND || || ||
|-
|| || GPIO5_11 || ECSPI1_MOSI || ECSPI1_MOSI || 36 || 85 || HDMI_TX0_N || || ||
|-
|| || GPIO2_12 || SD2_CD_B || SD2_CD_B || 37 || 84 || HDMI_TX0_P || || ||
|-
|| || GPIO2_15 || SD2_DAT0 || SD2_DAT0 || 38 || 83 || GND || || ||
|-
|| || GPIO2_16 || SD2_DAT1 || SD2_DAT1 || 39 || 82 || HDMI_TX1_N || || ||
|-
|| || GPIO2_14 || SD2_CMD || SD2_CMD || 40 || 81 || HDMI_TX1_P || || ||
|-
|| || || || GND || 41 || 80 || GND || || ||
|-
|| || GPIO2_13 || SD2_CLK || SD2_CLK || 42 || 79 || HDMI_CEC || HDMI_CEC || GPIO3_28 ||
|-
|| || || || GND || 43 || 78 || HDMI_DDC_SCL || HDMI_DDC_SCL || GPIO3_26 ||
|-
|| || GPIO_2_18 || SD2_DAT3 || SD2_DAT3 || 44 || 77 || HDMI_DDC_SDA || HDMI_DDC_SDA || GPIO3_27 ||
|-
|| || GPIO_2_17 || SD2_DAT2 || SD2_DAT2 || 45 || 76 || HDMI_HDP || HDMI_HDP || GPIO3_26 ||
|-
|| || || || GND || 46 || 75 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_A || 47 || 74 || ETH_TXRXP_A || || ||
|-
|| || || || ETH_QOS_TXRXM_A || 48 || 73 || ETH_TXRXM_A || || ||
|-
|| || || || GND || 49 || 72 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_B || 50 || 74 || ETH_TXRXP_B || || ||
|-
|| || || || ETH_QOS_TXRXM_B || 51 || 71 || ETH_TXRXM_B || || ||
|-
|| || || || GND || 52 || 69 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_C || 53 || 68 || ETH_TXRXP_B || || ||
|-
|| || || || ETH_QOS_TXRXM_C || 54 || 67 || ETH_TXRXM_B || || ||
|-
|| || || || GND || 55 || 66 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_D || 56 || 65 || ETH_TXRXP_C || || ||
|-
|| || || || ETH_QOS_TXRXM_D || 57 || 64 || ETH_TXRXM_C || || ||
|-
|| || || || GND || 58 || 63 || GND || || ||
|-
|| || || || ETH_QOS_ACTIVITY# || 59 || 62 || ETH_ACTIVITY# || || ||
|-
|| || || || ETH_QOS_LINK# || 60 || 61 || ETH_LINK# || || ||
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MP pad name !! OPOS8MP pad name !! Pin !! Pin !! OPOS8MP pad name !! i.MX8MP pad name !! GPIO !! Comments
|-
|| || || USB1_RX_N || USB1_RX_N || 1 || 120 || GPIO1_IO15 || GPIO1_IO15 || GPIO1_15 ||
|-
|| || || USB1_RX_P || USB1_RX_P || 2 || 119 || GPIO1_IO14 || GPIO1_IO14 || GPIO1_14 ||
|-
|| || || || GND || 3 || 118 || GPIO1_IO13 || GPIO1_IO13 || GPIO1_13 ||
|-
|| || || USB1_TX_N || USB1_TX_N || 4 || 117 || GPIO1_IO12 || GPIO1_IO12 || GPIO1_12 ||
|-
|| || || USB1_TX_P || USB1_TX_P || 5 || 116 || GPIO1_IO11 || GPIO1_IO11 || GPIO1_11 ||
|-
|| || || || GND || 6 || 115 || GPIO1_IO10 || GPIO1_IO10 || GPIO1_10 ||
|-
|| || || USB2_RX_N || USB2_RX_N || 7 || 114 || GPIO1_IO09 || GPIO1_IO09 || GPIO1_9 ||
|-
|| || || USB2_RX_P || USB2_RX_P || 8 || 113 || GPIO1_IO08 || GPIO1_IO08 || GPIO1_8 ||
|-
|| || || || GND || 9 || 112 || GPIO1_IO07 || GPIO1_IO07 || GPIO1_7 ||
|-
|| || || USB2_TX_N || USB2_TX_N || 10 || 111 || GPIO1_IO06 || GPIO1_IO06 || GPIO1_6 ||
|-
|| || || USB2_TX_P || USB2_TX_P || 11 || 110 || GPIO1_IO05 || GPIO1_IO05 || GPIO1_5 ||
|-
|| || || || GND || 12 || 109 || GPIO1_IO04 || GPIO1_IO04 || GPIO1_4 ||
|-
|| || || PCIE_RX_N || PCIE_RX_N || 13 || 108 || GPIO1_IO01 || GPIO1_IO01 || GPIO1_1 ||
|-
|| || || PCIE_RX_P || PCIE_RX_P || 14 || 107 || GPIO1_IO00 || GPIO1_IO00 || GPIO1_0 ||
|-
|| || || || GND || 15 || 106 || GND || || ||
|-
|| || || PCIE_TX_N || PCIE_TX_N || 16 || 105 || USB1_ID || USB1_ID || ||
|-
|| || || PCIE_TX_P || PCIE_TX_P || 17 || 104 || USB1_VBUS || USB1_VBUS || ||
|-
|| || || || GND || 18 || 103 || USB1_DN || USB1_DN || ||
|-
|| || || PCIE_CLK_N || PCIE_CLK_N || 19 || 102 || USB1_DP || USB1_DP || ||
|-
|| || || PCIE_CLK_P || PCIE_CLK_P || 20 || 101 || GND || || ||
|-
|| || || || GND || 21 || 100 || USB2_ID || USB2_ID || ||
|-
|| || || DSI_DO_P || DSI_DO_P || 22 || 99 || USB2_VBUS || USB2_VBUS || ||
|-
|| || || DSI_DO_N || DSI_DO_N || 23 || 98 || USB2_DN || USB2_DN || ||
|-
|| || || DSI_D1_P || DSI_D1_P || 24 || 97 || USB2_DP || USB2_DP || ||
|-
|| || || DSI_D1_N || DSI_D1_N || 25 || 96 || GND || || ||
|-
|| || || || GND || 26 || 95 || BOOT_MODE0 || BOOT_MODE0 || ||
|-
|| || || DSI_CLK_P || DSI_CLK_P || 27 || 94 || JTAG_TDO || JTAG_TDO || ||
|-
|| || || DSI_CLK_N || DSI_CLK_N || 28 || 93 || JTAG_TMS || JTAG_TMS || ||
|-
|| || || || GND || 29 || 92 || JTAG_TDI || JTAG_TDI || ||
|-
|| || || DSI_D2_P || DSI_D2_P || 30 || 91 || JTAG_TCK || JTAG_TCK || ||
|-
|| || || DSI_D2_N || DSI_D2_N || 31 || 90 || ONOFF || ONOFF || ||
|-
|| || || DSI_D3_P || DSI_D3_P || 32 || 89 || PMIC_ON_REQ || || ||
|-
|| || || DSI_D3_N || DSI_D3_N || 33 || 38 || POR_B || POR_B || ||
|-
|| || || || GND || 34 || 87 || GND || || ||
|-
|| || || CSI2_D3_P || CSI2_D3_P || 35 || 86 || CSI1_D0_P || CSI1_D0_P || ||
|-
|| || || CSI2_D3_N || CSI2_D3_N || 36 || 85 || CSI1_D0_N || CSI1_D0_N || ||
|-
|| || || CSI2_D2_P || CSI2_D2_P || 37 || 84 || CSI1_D1_P || CSI1_D1_P || ||
|-
|| || || CSI2_D2_N || CSI2_D2_N || 38 || 83 || CSI1_D1_N || CSI1_D1_N || ||
|-
|| || || || GND || 39 || 82 || GND || || ||
|-
|| || || CSI2_CLK_P || CSI2_CLK_P || 40 || 81 || CSI1_CLK_P || CSI1_CLK_P || ||
|-
|| || || CSI2_CLK_N || CSI2_CLK_N || 41 || 80 || CSI1_CLK_N || CSI1_CLK_N || ||
|-
|| || || || GND || 42 || 79 || GND || || ||
|-
|| || || CSI2_D1_P || CSI2_D1_P || 43 || 78 || CSI1_D2_P || CSI1_D2_P || ||
|-
|| || || CSI2_D1_N || CSI2_D1_N || 44 || 77 || CSI1_D2_N || CSI1_D2_N || ||
|-
|| || || CSI2_D0_P || CSI2_D0_P || 45 || 76 || CSI1_D3_P || CSI1_D3_P || ||
|-
|| || || CSI2_D0_N || CSI2_D0_N || 46 || 75 || CSI1_D3_N || CSI1_D3_N || ||
|-
|| || || || GND || 47 || 74 || GND || || ||
|-
|| || || LVDS1_D0_P || LVDS1_DO_P || 48 || 73 || LVDS0_D0_P || LVDS0_D0_P || ||
|-
|| || || LVDS1_D0_N || LVDS1_DO_N || 49 || 73 || LVDS0_D0_N || LVDS0_D0_N || ||
|-
|| || || LVDS1_D1_P || LVDS1_D1_P || 50 || 71 || LVDS0_D1_P || LVDS0_D1_P || ||
|-
|| || || LVDS1_D1_N || LVDS1_D1_N || 51 || 70 || LVDS0_D1_N || LVDS0_D1_N || ||
|-
|| || || || GND || 52 || 69 || GND || || ||
|-
|| || || LVDS1_CLK_P || LVDS1_CLK_P || 53 || 68 || LVDS0_CLK_P || LVDS0_CLK_P || ||
|-
|| || || LVDS1_CLK_N || LVDS1_CLK_N || 54 || 67 || LVDS0_CLK_N || LVDS0_CLK_N || ||
|-
|| || || || GND || 55 || 66 || GND || || ||
|-
|| || || LVDS1_D2_P || LVDS1_D2_P || 56 || 65 || LVDS0_D2_P || LVDS0_D2_P || ||
|-
|| || || LVDS1_D2_N || LVDS1_D2_N || 57 || 64 || LVDS0_D2_N || LVDS0_D2_N || ||
|-
|| || || LVDS1_D3_P || LVDS1_D3_P || 58 || 63 || LVDS0_D3_P || LVDS0_D3_P || ||
|-
|| || || LVDS1_D3_N || LVDS1_D3_N || 59 || 62 || LVDS0_D3_N || LVDS0_D3_N || ||
|-
|| || || || GND || 60 || 61 || GND || || ||
|}

OPOS8MP PINOUT

2021-05-31T16:02:30Z

SebastienSz: Created page with "= J3 connector = {| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;" ! Comments !! GPIO !! i.MX8MP pad name !! OPOS8MP pad n..."

= J3 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MP pad name !! OPOS8MP pad name !! Pin !! Pin !! OPOS8MP pad name !! i.MX8MP pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 120 || VIN || || ||
|-
|| || || || VIN || 2 || 119 || VIN || || ||
|-
|| || || || GND || 3 || 118 || VIN || || ||
|-
|| || || || GND || 4 || 117 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 116 || SYS_RST_B || || ||
|-
|| || || || NVCC_SVNS_1V8 || 6 || 115 || UART2_TXD || UART2_TXD || ||
|-
|| || || || GND || 7 || 114 || UART2_RXD || UART2_RXD || ||
|-
|rowspan="2" | Not available on OPOS8MP SoM with Bluetooth chip. || GPIO5_22 || UART1_RXD || UART1_RXD || 8 || 113 || UART4_RXD || UART4_RXD || GPIO5_28 || rowspan="2" | Default debug UART in Armadeus BSP.
|-
|| GPIO5_23 || UART1_TXD || UART1_TXD || 9 || 112 || UART1_TXD || UART1_TXD || GPIO5_29
|-
|| || GPIO5_26 || UART3_RXD || UART3_RXD || 10 || 111 || I2C2_SDA || I2C2_SDA || GPIO5_17 ||
|-
|| || GPIO5_27 || UART3_TXD || UART3_TXD || 11 || 110 || I2C2_SCL || I2C2_SCL || GPIO5_16 ||
|-
|| || GPIO5_19 || I2C3_SDA || I2C3_SDA || 12 || 109 || GND || || ||
|-
|| || GPIO5_18 || I2C3_SCL || I2C3_SCL || 13 || 108 || UART1_RTS || SAI2_RXD0 || GPIO4_23 || Not available on OPOS8MP SoM with Bluetooth chip.
|-
|| || GPIO5_21 || I2C4_SDA || I2C4_SDA || 14 || 107 || SAI2_RXFS || SAI2_RXFS || GPIO4_21 ||
|-
|| || GPIO5_20 || I2C4_SCL || I2C4_SCL || 15 || 106 || SAI2_RXC || SAI2_RXC || GPIO4_22 ||
|-
|| || || || GND || 16 || 105 || SAI2_TXD0 || SAI2_TXD0 || GPIO4_26 ||
|-
|| || GPIO4_3 || SAI1_RXD1 || SAI1_RXD1 || 17 || 104 || UART1_CTS || SAI2_TXFS || GPIO4_24 || Not available on OPOS8MP SoM with Bluetooth chip.
|-
|| || GPIO4_2 || SAI1_RXD0 || SAI1_RXD0 || 18 || 103 || SAI2_TXC || SAI2_TXC || GPIO4_25 ||
|-
|| || GPIO4_20 || SAI1_MCLK || SAI1_MCLK || 19 || 102 || SAI2_MCLK || SAI2_MCLK || GPIO4_27 ||
|-
|| || GPIO4_18 || SAI1_TXD6 || SAI1_TXD6 || 20 || 101 || SAI3_RXD || SAI3_RXD || GPIO4_30 ||
|-
|| || GPIO4_19 || SAI1_TXD7 || SAI1_TXD7 || 21 || 100 || SAI3_RXFS || SAI3_RXFS || GPIO4_28 ||
|-
|| || GPIO3_24 || SAI5_RXD3 || SAI5_RXD3 || 22 || 99 || SAI3_RXC || SAI3_RXC || GPIO4_29 ||
|-
|| || GPIO3_23 || SAI5_RXD2 || SAI5_RXD2 || 23 || 98 || SAI3_TXD || SAI3_TXD || GPIO5_1 ||
|-
|| || GPIO3_22 || SAI5_RXD1 || SAI5_RXD1 || 24 || 97 || SAI3_TXFS || SAI3_TXFS || GPIO4_31 ||
|-
|| || GPIO3_21 || SAI5_RXD0 || SAI5_RXD0 || 25 || 96 || SAI3_TXC || SAI3_TXC || GPIO5_0 ||
|-
|| || GPIO3_19 || SAI5_RXFS || SAI5_RXFS || 26 || 95 || SAI3_MCLK || SAI3_MCLK || GPIO5_2 ||
|-
|| || GPIO3_20 || SAI5_RXC || SAI5_RXC || 27 || 94 || GND || || ||
|-
|| || GPIO3_25 || SAI5_MCLK || SAI5_MCLK || 28 || 93 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_10 ||
|-
|| || GPIO5_3 || SPDIF_TX || SPDIF_TX || 29 || 92 || ECSPI2_SS0 || ECSPI2_SCLK || GPIO5_13 ||
|-
|| || GPIO5_4 || SPDIF_TX || SPDIF_TX || 30 || 91 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_12 ||
|-
|| || GPIO5_5 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 31 || 90 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_11 ||
|-
|| || || || GND || 32 || 89 || GND || || ||
|-
|| || GPIO5_6 || ECSPI1_SCLK || ECSPI1_SCLK || 33 || 88 || HDMI_TXC_N || || ||
|-
|| || GPIO5_9 || ECSPI1_SS0 || ECSPI1_SS0 || 34 || 87 || HDMI_TXC_P || || ||
|-
|| || GPIO5_12 || ECSPI1_MISO || ECSPI1_MISO || 35 || 86 || GND || || ||
|-
|| || GPIO5_11 || ECSPI1_MOSI || ECSPI1_MOSI || 36 || 85 || HDMI_TX0_N || || ||
|-
|| || GPIO2_12 || SD2_CD_B || SD2_CD_B || 37 || 84 || HDMI_TX0_P || || ||
|-
|| || GPIO2_15 || SD2_DAT0 || SD2_DAT0 || 38 || 83 || GND || || ||
|-
|| || GPIO2_16 || SD2_DAT1 || SD2_DAT1 || 39 || 82 || HDMI_TX1_N || || ||
|-
|| || GPIO2_14 || SD2_CMD || SD2_CMD || 40 || 81 || HDMI_TX1_P || || ||
|-
|| || || || GND || 41 || 80 || GND || || ||
|-
|| || GPIO2_13 || SD2_CLK || SD2_CLK || 42 || 79 || HDMI_CEC || HDMI_CEC || GPIO3_28 ||
|-
|| || || || GND || 43 || 78 || HDMI_DDC_SCL || HDMI_DDC_SCL || GPIO3_26 ||
|-
|| || GPIO_2_18 || SD2_DAT3 || SD2_DAT3 || 44 || 77 || HDMI_DDC_SDA || HDMI_DDC_SDA || GPIO3_27 ||
|-
|| || GPIO_2_17 || SD2_DAT2 || SD2_DAT2 || 45 || 76 || HDMI_HDP || HDMI_HDP || GPIO3_26 ||
|-
|| || || || GND || 46 || 75 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_A || 47 || 74 || ETH_TXRXP_A || || ||
|-
|| || || || ETH_QOS_TXRXM_A || 48 || 73 || ETH_TXRXM_A || || ||
|-
|| || || || GND || 49 || 72 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_B || 50 || 74 || ETH_TXRXP_B || || ||
|-
|| || || || ETH_QOS_TXRXM_B || 51 || 71 || ETH_TXRXM_B || || ||
|-
|| || || || GND || 52 || 69 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_C || 53 || 68 || ETH_TXRXP_B || || ||
|-
|| || || || ETH_QOS_TXRXM_C || 54 || 67 || ETH_TXRXM_B || || ||
|-
|| || || || GND || 55 || 66 || GND || || ||
|-
|| || || || ETH_QOS_TXRXP_D || 56 || 65 || ETH_TXRXP_C || || ||
|-
|| || || || ETH_QOS_TXRXM_D || 57 || 64 || ETH_TXRXM_C || || ||
|-
|| || || || GND || 58 || 63 || GND || || ||
|-
|| || || || ETH_QOS_ACTIVITY# || 59 || 62 || ETH_ACTIVITY# || || ||
|-
|| || || || ETH_QOS_LINK# || 60 || 61 || ETH_LINK# || || ||
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MP pad name !! OPOS8MP pad name !! Pin !! Pin !! OPOS8MP pad name !! i.MX8MP pad name !! GPIO !! Comments
|-
|| || || USB1_RX_N || USB1_RX_N || 1 || 120 || GPIO1_IO15 || GPIO1_IO15 || GPIO1_15 ||
|-
|| || || USB1_RX_P || USB1_RX_P || 2 || 119 || GPIO1_IO14 || GPIO1_IO14 || GPIO1_14 ||
|-
|| || || || GND || 3 || 118 || GPIO1_IO13 || GPIO1_IO13 || GPIO1_13 ||
|-
|| || || USB1_TX_N || USB1_TX_N || 4 || 117 || GPIO1_IO12 || GPIO1_IO12 || GPIO1_12 ||
|-
|| || || USB1_TX_P || USB1_TX_P || 5 || 116 || GPIO1_IO11 || GPIO1_IO11 || GPIO1_11 ||
|-
|| || || || GND || 6 || 115 || GPIO1_IO10 || GPIO1_IO10 || GPIO1_10 ||
|-
|| || || USB2_RX_N || USB2_RX_N || 7 || 114 || GPIO1_IO09 || GPIO1_IO09 || GPIO1_9 ||
|-
|| || || USB2_RX_P || USB2_RX_P || 8 || 113 || GPIO1_IO08 || GPIO1_IO08 || GPIO1_8 ||
|-
|| || || || GND || 9 || 112 || GPIO1_IO07 || GPIO1_IO07 || GPIO1_7 ||
|-
|| || || USB2_TX_N || USB2_TX_N || 10 || 111 || GPIO1_IO06 || GPIO1_IO06 || GPIO1_6 ||
|-
|| || || USB2_TX_P || USB2_TX_P || 11 || 110 || GPIO1_IO05 || GPIO1_IO05 || GPIO1_5 ||
|-
|| || || || GND || 12 || 109 || GPIO1_IO04 || GPIO1_IO04 || GPIO1_4 ||
|-
|| || || PCIE_RX_N || PCIE_RX_N || 13 || 108 || GPIO1_IO01 || GPIO1_IO01 || GPIO1_1 ||
|-
|| || || PCIE_RX_P || PCIE_RX_P || 14 || 107 || GPIO1_IO00 || GPIO1_IO00 || GPIO1_0 ||
|-
|| || || || GND || 15 || 106 || GND || || ||
|-
|| || || PCIE_TX_N || PCIE_TX_N || 16 || 105 || USB1_ID || USB1_ID || ||
|-
|| || || PCIE_TX_P || PCIE_TX_P || 17 || 104 || USB1_VBUS || USB1_VBUS || ||
|-
|| || || || GND || 18 || 103 || USB1_DN || USB1_DN || ||
|-
|| || || PCIE_CLK_N || PCIE_CLK_N || 19 || 102 || USB1_DP || USB1_DP || ||
|-
|| || || PCIE_CLK_P || PCIE_CLK_P || 20 || 101 || GND || || ||
|-
|| || || || GND || 21 || 100 || USB2_ID || USB2_ID || ||
|-
|| || || DSI_DO_P || DSI_DO_P || 22 || 99 || USB2_VBUS || USB2_VBUS || ||
|-
|| || || DSI_DO_N || DSI_DO_N || 23 || 98 || USB2_DN || USB2_DN || ||
|-
|| || || DSI_D1_P || DSI_D1_P || 24 || 97 || USB2_DP || USB2_DP || ||
|-
|| || || DSI_D1_N || DSI_D1_N || 25 || 96 || GND || || ||
|-
|| || || || GND || 26 || 95 || BOOT_MODE0 || BOOT_MODE0 || ||
|-
|| || || DSI_CLK_P || DSI_CLK_P || 27 || 94 || JTAG_TDO || JTAG_TDO || ||
|-
|| || || DSI_CLK_N || DSI_CLK_N || 28 || 93 || JTAG_TMS || JTAG_TMS || ||
|-
|| || || || GND || 29 || 92 || JTAG_TDI || JTAG_TDI || ||
|-
|| || || DSI_D2_P || DSI_D2_P || 30 || 91 || JTAG_TCK || JTAG_TCK || ||
|-
|| || || DSI_D2_N || DSI_D2_N || 31 || 90 || ONOFF || ONOFF || ||
|-
|| || || DSI_D3_P || DSI_D3_P || 32 || 89 || PMIC_ON_REQ || || ||
|-
|| || || DSI_D3_N || DSI_D3_N || 33 || 38 || POR_B || POR_B || ||
|-
|| || || || GND || 34 || 87 || GND || || ||
|-
|| || || CSI2_D3_P || CSI2_D3_P || 35 || 86 || CSI1_D0_P || CSI1_D0_P || ||
|-
|| || || CSI2_D3_N || CSI2_D3_N || 36 || 85 || CSI1_D0_N || CSI1_D0_N || ||
|-
|| || || CSI2_D2_P || CSI2_D2_P || 37 || 84 || CSI1_D1_P || CSI1_D1_P || ||
|-
|| || || CSI2_D2_N || CSI2_D2_N || 38 || 83 || CSI1_D1_N || CSI1_D1_N || ||
|-
|| || || || GND || 39 || 82 || GND || || ||
|-
|| || || CSI2_CLK_P || CSI2_CLK_P || 40 || 81 || CSI1_CLK_P || CSI1_CLK_P || ||
|-
|| || || CSI2_CLK_N || CSI2_CLK_N || 41 || 80 || CSI1_CLK_N || CSI1_CLK_N || ||
|-
|| || || || GND || 42 || 79 || GND || || ||
|-
|| || || CSI2_D1_P || CSI2_D1_P || 43 || 78 || CSI1_D2_P || CSI1_D2_P || ||
|-
|| || || CSI2_D1_N || CSI2_D1_N || 44 || 77 || CSI1_D2_N || CSI1_D2_N || ||
|-
|| || || CSI2_D0_P || CSI2_D0_P || 45 || 76 || CSI1_D3_P || CSI1_D3_P || ||
|-
|| || || CSI2_D0_N || CSI2_D0_N || 46 || 75 || CSI1_D3_N || CSI1_D3_N || ||
|-
|| || || || GND || 47 || 74 || GND || || ||
|-
|| || || LVDS1_DO_P || LVDS1_DO_P || 48 || 73 || LVDS0_DO_P || LVDS0_DO_P || ||
|-
|| || || LVDS1_DO_N || LVDS1_DO_N || 49 || 73 || LVDS0_DO_N || LVDS0_DO_N || ||
|-
|| || || LVDS1_D1_P || LVDS1_D1_P || 50 || 71 || LVDS0_D1_P || LVDS0_D1_P || ||
|-
|| || || LVDS1_D1_N || LVDS1_D1_N || 51 || 70 || LVDS0_D1_N || LVDS0_D1_N || ||
|-
|| || || || GND || 52 || 69 || GND || || ||
|-
|| || || LVDS1_CLK_P || LVDS1_CLK_P || 53 || 68 || LVDS0_CLK_P || LVDS0_CLK_P || ||
|-
|| || || LVDS1_CLK_N || LVDS1_CLK_N || 54 || 67 || LVDS0_CLK_N || LVDS0_CLK_N || ||
|-
|| || || || GND || 55 || 66 || GND || || ||
|-
|| || || LVDS1_D2_P || LVDS1_D2_P || 56 || 65 || LVDS0_D2_P || LVDS0_D2_P || ||
|-
|| || || LVDS1_D2_N || LVDS1_D2_N || 57 || 64 || LVDS0_D2_N || LVDS0_D2_N || ||
|-
|| || || LVDS1_D3_P || LVDS1_D3_P || 58 || 63 || LVDS0_D3_P || LVDS0_D3_P || ||
|-
|| || || LVDS1_D3_N || LVDS1_D3_N || 59 || 62 || LVDS0_D3_N || LVDS0_D3_N || ||
|-
|| || || || GND || 60 || 61 || GND || || ||
|}

U-Boot UMS on APF & OPOS

2021-05-21T13:23:30Z

SebastienSz: /* Links */ add link the the OPOS8MM eMMC data partition page

This page gather instructions for using U-Boot's USB Mass Storage gadget mode (or UMS) usage on [[APF6]] and [[OPOS6UL]](NANO). This mode allows you to flash rootfs images bigger than the available module RAM, ex: > 200MBytes on the [[OPOS6UL]](NANO). Indeed ''run update_rootfs'' script uses RAM to store images while uploading from TFTP, which can be short for big rootfs. UMS also allows you to backup your rootfs on your Host.

* First, keep your USB debug cable and connect a second USB cable on [[APF6_Dev]] or [[OPOS6ULDev]]'s OTG port.
* Under U-Boot type:
<pre class="apf">
BIOS> ums 0 mmc 0
UMS: disk start sector: 0x0, count: 0x760000
|
</pre>
* On your Host computer you should see the [[eMMC]] partition like a standard USB key.
<pre class="host">
$ dmesg | tail
[...]
[26828.348088] sd 13:0:0:0: [sdc] Mode Sense: 0f 00 00 00
[26828.348395] sd 13:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[26828.354177] sdc: sdc1 sdc2
[26828.356782] sd 13:0:0:0: [sdc] Attached SCSI disk
</pre>

Here the device is ''/dev/sdc'' and all partitions have been automounted by the Host:

<pre class="host">
[26830.002168] EXT4-fs (sdc1): mounting ext2 file system using the ext4 subsystem
[26830.054358] EXT4-fs (sdc2): mounting ext2 file system using the ext4 subsystem
[26830.078638] EXT4-fs (sdc2): warning: mounting unchecked fs, running e2fsck is recommended
[26830.114382] EXT4-fs (sdc2): mounted filesystem without journal. Opts: (null)
[26830.135564] EXT4-fs (sdc1): warning: mounting unchecked fs, running e2fsck is recommended
[26830.268450] EXT4-fs (sdc1): mounted filesystem without journal. Opts: (null)
</pre>
{{Warning| Before doing the following procedure, be sure that your device name is correct. '''You can erase all your Host datas if you do it wrong !!!'''}}
* The rootfs is under the sdc2 and is named "ROOTFS". On your debian/ubuntu Host it might be auto-mounted under ''/media/usb1'', if no other USB key is present on system and if you activated auto-mounting.
<pre class="host">
$ ls /media/usb1/
bin boot dev etc home init lib lib32 linuxrc lost+found media mnt opt proc root run sbin sys tmp usr var
</pre>

* To flash entire rootfs, first erase all files on this partition:
<pre class="host">
$ sudo umount /media/usb1 (if partition is auto-mounted)
$ sudo mkfs.ext4 -L ROOTFS -O ^64bit,^metadata_csum,uninit_bg /dev/sdc2
</pre>

==Update your rootfs==
* Then, you have 2 methods to update your rootfs:
{| class="wikitable"
|-
! tar method !! dd method
|-
|
* Then mount it under an arbitrary directory:
<pre class="host">
$ sudo mkdir /tmp/rootfs
$ sudo mount /dev/sdc2 /tmp/rootfs
</pre>

* Untar the archive generated by your bsp (in ''buildroot/output/images/'')
<pre class="host">
$ make shell_env
$ . armadeus_env.sh
$ sudo tar -xvf $ARMADEUS_ROOTFS_TAR -C /tmp/rootfs
</pre>
* then umount the filesystem:
<pre class="host">
$ sudo umount /tmp/rootfs/
$ sync
</pre>
||
* One alternative way to untaring is to use ''dd'':
<pre class="host">
$ sudo dd if=/tftpboot/xxx-rootfs.ext4 of=/dev/sdc2
</pre>
(replace xxx with the name of your module)
|}

* Once finished, you can kill the U-Boot's USB gadget process with a Ctrl-C:
<pre class="apf">
BIOS> ums 0 mmc 0
UMS: disk start sector: 0x0, count: 0x760000
CTRL+C - Operation aborted
BIOS>
</pre>

==Backup your rootfs==
<pre class="host">
$ sudo dd if=/dev/sdc2 of=/home/xxx/rootfs_xxx.ext4 (takes time ;-) )
</pre>

* check if it succeed:
<pre class="host">
$ sudo mount -o loop /home/xxx/rootfs_xxx.ext4 /media/mmc/
$ ls /media/mmc/boot/
</pre>

==Troubleshots==
* UMS was reported not working on Windows 7/8 hosts with Virtual Box Ubuntu 15.04 emulated machines...

==Links==
* [[EMMC_OPOS6UL#User_Data_partition_layout|OPOS6UL eMMC Data partition]]
* [[EMMC_OPOS8MM#User_Data_partition_layout|OPOS8MM eMMC Data partition]]

[[Category:U-Boot]]

WPA supplicant

2021-02-25T08:43:27Z

SebastienSz: use -D nl80211 instead of wext

When dealing with "strong" encryption of Wi-Fi networks, you have to setup a WPA or WPA2 configuration.
To handle the requirements of these protocols during association, a userspace daemon is needed: it is called a "WPA supplicant".
The most used one on Linux is ''wpa_supplicant''; we will see here how to install and configure it.

{{Note|''wpa_supplicant'' is also able to handle WEP or unencrypted connections}}

==Installation==
* Done by default if your board supports Wi-Fi connectivity. Otherwise:
<pre class="host">
$ make menuconfig
</pre>

<pre class="config">
Package Selection for the target --->
Networking --->
[*] wpa_supplicant
[ ] Enable WPA with EAP
[*] Install wpa_cli binary
[*] Install wpa_passphrase binary
</pre>

EAP is only needed if you plan to use WPA in Enterprise mode == with a Radius server.

==Usage==
''wpa_supplicant'' needs a configuration file in ''/etc/wpa_supplicant.conf''.
For your convience a generic ''/etc/wpa_supplicant.conf'' is already installed in the Armadeus BSP (releases > 5.2).
Here is an example (WPA pre-shared key (TKIP)):
<pre class="host">
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
update_config=1
network={
ssid="''SSID''"
scan_ssid=1 # only if ssid is hidden
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
psk="''PASSPHRASE''"
}
</pre>
You can adapt ''/etc/wpa_supplicant.conf'' manually.
* If your key needs to be encrypted, use the ''wpa_passphrase'' tool to add your network (SSID/PASSPHRASE) automatically:
<pre class="apf">
# wpa_passphrase "mynetworkSSID" "mynetworkPASSPHRASE" >> /etc/wpa_supplicant.conf
</pre>
* Be sure to have your Wi-Fi chipset driver loaded:
<pre class="apf">
# modprobe libertas_sdio
or
# modprobe wlcore_sdio
or
# modprobe rt73usb
# modprobe rt2800_usb
# modprobe zd1211rw
# modprobe rtl8187
# modprobe r8712u
...
</pre>
* Bring up the wireless interface:
<pre class="apf">
# ip link set dev wlan0 up
</pre>
or (as you prefer):
<pre class="apf">
# ifconfig wlan0 up
</pre>
* Then you can create the Wi-Fi connection with WPA Supplicant:
<pre class="apf">
# wpa_supplicant -Dnl80211 -i wlan0 -c /etc/wpa_supplicant.conf -B
# wpa_cli -B -a /etc/wpa_supplicant/wpa_cli-action.sh
# /etc/wpa_supplicant/wpa_cli-action.sh wlan0 CONNECTED # to force ip renewal if needed
</pre>
* Then you can check your Wi-Fi interface is available:
<pre class="apf">
# iwconfig wlan0
wlan0 IEEE 802.11abgn ESSID:"xxxx_xxxx"
Mode:Managed Frequency:5.2 GHz Access Point: 00:xx:xx:xx:xx:xx
Bit Rate=24 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=29/70 Signal level=-81 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:xx
inet addr:192.168.0.20 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: 2a01:e35:2e35:f60:219:88ff:fe15:4237/64 Scope:Global
inet6 addr: fe80::219:88ff:fe15:4237/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14238 (13.9 KiB) TX bytes:2797 (2.7 KiB)
</pre>

==Automate things at startup==
===Standard method===
* In default BSP you have a ''/etc/init.d/S40Network'' script which will automatically starts all network interfaces configured in ''/etc/network/interfaces''.
* All you have to do is to add your Wi-Fi interface configuration in ''/etc/network/interfaces'', like for example on [[OPOS6UL]]:
<pre class="apf">
auto wlan0
iface wlan0 inet dhcp
pre-up modprobe brcmfmac
pre-up sleep 3
pre-up wpa_supplicant -Dwext -i wlan0 -c /etc/wpa_supplicant.conf -B
</pre>

===Other methods===
* You can also choose to use a custom startup script. Here is an init script example, to adapt to your Wi-Fi driver (update WIFIDRIVERS in the source) and to place into ''/etc/init.d/S61wifi'' (do not forget to give it execution rigths with ''chmod a+x /etc/init.d/S61wifi''):
<source lang="bash">
#!/bin/sh
#
# Starts Wi-Fi services
#
# do not forget to update your wpa_supplicant configuration
# wpa_passphrase "mynetworrssid" "mynetworkpassphrase" >> /etc/wpa_supplicant.conf
#
export WIFIDRIVERS=libertas_sdio
case "$1" in
start)
echo "Starting Wi-Fi"
modprobe $WIFIDRIVERS
ip link set dev wlan0 up
wpa_supplicant -Dwext -i wlan0 -c /etc/wpa_supplicant.conf -B
wpa_cli -B -a /etc/wpa_supplicant/wpa_cli-action.sh
;;

stop)
echo "Stoping Wi-Fi"
wpa_cli -i wlan0 disconnect
wpa_cli -i wlan0 terminate
ip link set dev wlan0 down
rmmod -a $WIFIDRIVERS
;;

restart)
$0 stop
sleep 1
$0 start
;;

*)
echo "Usage: $0 {start|stop|restart}"
exit 1
;;
esac

exit 0

</source>

==Stop it==
To stop WPA Supplicant daemon and switch off the connexion, you can use this command:
<pre class="apf">
# wpa_cli terminate
</pre>
or by using the S61wifi script here above:

<pre class="apf">
# /etc/init.d/S61wifi stop
</pre>

==Links==
* [http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/README wpa_supplicant README]
* [http://hostap.epitest.fi/wpa_supplicant/ wpa_supplicant Webpage]

[[Category:Wireless]]
[[Category:Security]]
[[Category:WiFi]]
[[Category:Network]]

OPOS8MM PINOUT

2021-02-22T08:50:59Z

SebastienSz: /* J2 connector */

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07 ||
|-
|| || || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08 ||
|-
|| || || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06 ||
|-
|| || || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09 ||
|-
|| || || || GND || 5 || 66 || GND || || ||
|-
|| || || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11 ||
|-
|| || || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12 ||
|-
|| || || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10 ||
|-
|| || || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13 ||
|-
|| || || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || || ||
|-
|| || || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23 ||
|-
|| || || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24 ||
|-
|| || || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22 ||
|-
|| || || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25 ||
|-
|| || || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19 ||
|-
|| || || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18 ||
|-
|| || || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17 ||
|-
|| || || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16 ||
|-
|| || || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21 ||
|-
|| || || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20 ||
|-
|| || || || GND || 21 || 50 || GND || || ||
|-
|| || || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26 ||
|-
|| || || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27 ||
|-
|| || || MIPI_CSI_D3_N || CSI_D3_N || 24 || style="background: yellow;" | 47 || style="background: yellow;" | UART4_TXD || style="background: yellow;" | UART4_TXD || style="background: yellow;" | GPIO5_IO29 || style="background: yellow;" rowspan="2" | Default debug UART in Armadeus BSP.
|-
|| || || MIPI_CSI_D3_P || CSI_D3_P || 25 || style="background: yellow;" | 46 || style="background: yellow;" | UART4_RXD || style="background: yellow;" | UART4_RXD || style="background: yellow;" | GPIO5_IO28
|-
|| || || || GND || 26 || 45 || GND || || ||
|-
|| || || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN || ||
|-
|| || || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP || ||
|-
|| || || || GND || 29 || 42 || USB1_ID || USB1_ID || ||
|-
|| || || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS || ||
|-
|| || || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || || ||
|-
|| || || || GND || 32 || 39 || USB2_DN || USB2_DN || ||
|-
|| || || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP || ||
|-
|| || || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID || ||
|-
|| || || || GND || 35 || 36 || RTC_VDD || || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 70 || VIN || || ||
|-
|| || || || VIN || 2 || 69 || VIN || || ||
|-
|| || || || VIN || 3 || 68 || VIN || || ||
|-
|| || || || VIN || 4 || 67 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip. || GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29
|-
|| || GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| || GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| || GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| || GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| || GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| || GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| || GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| || GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| || GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| || GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| || GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| || GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| || GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| || GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| || GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| || GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| || GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| || GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || || GND || 30 || 41 || GND || || ||
|-
|| || GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| || GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || || GND || 33 || 38 || GND || || ||
|-
|| || || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-22T08:38:08Z

SebastienSz: /* J2 connector */

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07 ||
|-
|| || || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08 ||
|-
|| || || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06 ||
|-
|| || || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09 ||
|-
|| || || || GND || 5 || 66 || GND || || ||
|-
|| || || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11 ||
|-
|| || || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12 ||
|-
|| || || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10 ||
|-
|| || || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13 ||
|-
|| || || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || || ||
|-
|| || || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23 ||
|-
|| || || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24 ||
|-
|| || || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22 ||
|-
|| || || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25 ||
|-
|| || || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19 ||
|-
|| || || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18 ||
|-
|| || || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17 ||
|-
|| || || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16 ||
|-
|| || || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21 ||
|-
|| || || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20 ||
|-
|| || || || GND || 21 || 50 || GND || || ||
|-
|| || || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26 ||
|-
|| || || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27 ||
|-
|| || || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29 || rowspan="2" | Default debug UART in Armadeus BSP.
|-
|| || || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28
|-
|| || || || GND || 26 || 45 || GND || || ||
|-
|| || || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN || ||
|-
|| || || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP || ||
|-
|| || || || GND || 29 || 42 || USB1_ID || USB1_ID || ||
|-
|| || || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS || ||
|-
|| || || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || || ||
|-
|| || || || GND || 32 || 39 || USB2_DN || USB2_DN || ||
|-
|| || || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP || ||
|-
|| || || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID || ||
|-
|| || || || GND || 35 || 36 || RTC_VDD || || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 70 || VIN || || ||
|-
|| || || || VIN || 2 || 69 || VIN || || ||
|-
|| || || || VIN || 3 || 68 || VIN || || ||
|-
|| || || || VIN || 4 || 67 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip. || GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29
|-
|| || GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| || GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| || GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| || GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| || GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| || GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| || GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| || GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| || GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| || GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| || GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| || GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| || GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| || GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| || GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| || GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| || GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| || GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || || GND || 30 || 41 || GND || || ||
|-
|| || GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| || GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || || GND || 33 || 38 || GND || || ||
|-
|| || || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-22T08:34:29Z

SebastienSz: /* J2 connector */

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07 ||
|-
|| || || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08 ||
|-
|| || || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06 ||
|-
|| || || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09 ||
|-
|| || || || GND || 5 || 66 || GND || || ||
|-
|| || || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11 ||
|-
|| || || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12 ||
|-
|| || || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10 ||
|-
|| || || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13 ||
|-
|| || || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || || ||
|-
|| || || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23 ||
|-
|| || || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24 ||
|-
|| || || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22 ||
|-
|| || || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25 ||
|-
|| || || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19 ||
|-
|| || || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18 ||
|-
|| || || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17 ||
|-
|| || || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16 ||
|-
|| || || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21 ||
|-
|| || || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20 ||
|-
|| || || || GND || 21 || 50 || GND || || ||
|-
|| || || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26 ||
|-
|| || || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27 ||
|-
|| || || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29 ||
|-
|| || || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28 ||
|-
|| || || || GND || 26 || 45 || GND || || ||
|-
|| || || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN || ||
|-
|| || || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP || ||
|-
|| || || || GND || 29 || 42 || USB1_ID || USB1_ID || ||
|-
|| || || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS || ||
|-
|| || || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || || ||
|-
|| || || || GND || 32 || 39 || USB2_DN || USB2_DN || ||
|-
|| || || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP || ||
|-
|| || || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID || ||
|-
|| || || || GND || 35 || 36 || RTC_VDD || || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 70 || VIN || || ||
|-
|| || || || VIN || 2 || 69 || VIN || || ||
|-
|| || || || VIN || 3 || 68 || VIN || || ||
|-
|| || || || VIN || 4 || 67 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip. || GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29
|-
|| || GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| || GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| || GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| || GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| || GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| || GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| || GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| || GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| || GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| || GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| || GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| || GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| || GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| || GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| || GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| || GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| || GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| || GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || || GND || 30 || 41 || GND || || ||
|-
|| || GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| || GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || || GND || 33 || 38 || GND || || ||
|-
|| || || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-22T08:29:28Z

SebastienSz: /* J4 connector */

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO
|-
|| || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07
|-
|| || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08
|-
|| || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06
|-
|| || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09
|-
|| || || GND || 5 || 66 || GND || ||
|-
|| || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11
|-
|| || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12
|-
|| || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10
|-
|| || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13
|-
|| || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || ||
|-
|| || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23
|-
|| || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24
|-
|| || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22
|-
|| || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25
|-
|| || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19
|-
|| || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18
|-
|| || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17
|-
|| || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16
|-
|| || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21
|-
|| || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20
|-
|| || || GND || 21 || 50 || GND || ||
|-
|| || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26
|-
|| || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27
|-
|| || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29
|-
|| || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28
|-
|| || || GND || 26 || 45 || GND || ||
|-
|| || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN ||
|-
|| || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP ||
|-
|| || || GND || 29 || 42 || USB1_ID || USB1_ID ||
|-
|| || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS ||
|-
|| || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || ||
|-
|| || || GND || 32 || 39 || USB2_DN || USB2_DN ||
|-
|| || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP ||
|-
|| || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID ||
|-
|| || || GND || 35 || 36 || RTC_VDD || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments !! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 70 || VIN || || ||
|-
|| || || || VIN || 2 || 69 || VIN || || ||
|-
|| || || || VIN || 3 || 68 || VIN || || ||
|-
|| || || || VIN || 4 || 67 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip. || GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29
|-
|| || GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| || GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| || GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| || GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| || GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| || GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| || GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| || GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| || GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| || GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| || GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| || GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| || GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| || GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| || GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| || GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| || GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| || GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || || GND || 30 || 41 || GND || || ||
|-
|| || GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| || GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || || GND || 33 || 38 || GND || || ||
|-
|| || || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-22T08:28:56Z

SebastienSz: /* J4 connector */

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO
|-
|| || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07
|-
|| || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08
|-
|| || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06
|-
|| || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09
|-
|| || || GND || 5 || 66 || GND || ||
|-
|| || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11
|-
|| || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12
|-
|| || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10
|-
|| || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13
|-
|| || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || ||
|-
|| || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23
|-
|| || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24
|-
|| || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22
|-
|| || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25
|-
|| || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19
|-
|| || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18
|-
|| || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17
|-
|| || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16
|-
|| || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21
|-
|| || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20
|-
|| || || GND || 21 || 50 || GND || ||
|-
|| || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26
|-
|| || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27
|-
|| || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29
|-
|| || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28
|-
|| || || GND || 26 || 45 || GND || ||
|-
|| || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN ||
|-
|| || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP ||
|-
|| || || GND || 29 || 42 || USB1_ID || USB1_ID ||
|-
|| || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS ||
|-
|| || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || ||
|-
|| || || GND || 32 || 39 || USB2_DN || USB2_DN ||
|-
|| || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP ||
|-
|| || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID ||
|-
|| || || GND || 35 || 36 || RTC_VDD || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! Comments ! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || || VIN || 1 || 70 || VIN || || ||
|-
|| || || || VIN || 2 || 69 || VIN || || ||
|-
|| || || || VIN || 3 || 68 || VIN || || ||
|-
|| || || || VIN || 4 || 67 || VIN || || ||
|-
|| || || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip. || GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29
|-
|| || GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| || GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| || GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| || GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| || GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| || GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| || GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| || GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| || GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| || GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| || GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| || GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| || GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| || GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| || GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| || GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| || GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| || GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || || GND || 30 || 41 || GND || || ||
|-
|| || GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| || GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || || GND || 33 || 38 || GND || || ||
|-
|| || || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-18T09:53:29Z

SebastienSz: /* J4 connector */

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO
|-
|| || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07
|-
|| || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08
|-
|| || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06
|-
|| || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09
|-
|| || || GND || 5 || 66 || GND || ||
|-
|| || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11
|-
|| || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12
|-
|| || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10
|-
|| || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13
|-
|| || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || ||
|-
|| || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23
|-
|| || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24
|-
|| || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22
|-
|| || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25
|-
|| || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19
|-
|| || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18
|-
|| || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17
|-
|| || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16
|-
|| || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21
|-
|| || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20
|-
|| || || GND || 21 || 50 || GND || ||
|-
|| || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26
|-
|| || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27
|-
|| || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29
|-
|| || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28
|-
|| || || GND || 26 || 45 || GND || ||
|-
|| || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN ||
|-
|| || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP ||
|-
|| || || GND || 29 || 42 || USB1_ID || USB1_ID ||
|-
|| || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS ||
|-
|| || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || ||
|-
|| || || GND || 32 || 39 || USB2_DN || USB2_DN ||
|-
|| || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP ||
|-
|| || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID ||
|-
|| || || GND || 35 || 36 || RTC_VDD || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || VIN || 1 || 70 || VIN || || ||
|-
|| || || VIN || 2 || 69 || VIN || || ||
|-
|| || || VIN || 3 || 68 || VIN || || ||
|-
|| || || VIN || 4 || 67 || VIN || || ||
|-
|| || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29
|-
|| GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || GND || 30 || 41 || GND || || ||
|-
|| GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || GND || 33 || 38 || GND || || ||
|-
|| || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-18T09:53:06Z

SebastienSz: /* J4 connector */

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO
|-
|| || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07
|-
|| || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08
|-
|| || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06
|-
|| || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09
|-
|| || || GND || 5 || 66 || GND || ||
|-
|| || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11
|-
|| || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12
|-
|| || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10
|-
|| || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13
|-
|| || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || ||
|-
|| || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23
|-
|| || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24
|-
|| || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22
|-
|| || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25
|-
|| || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19
|-
|| || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18
|-
|| || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17
|-
|| || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16
|-
|| || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21
|-
|| || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20
|-
|| || || GND || 21 || 50 || GND || ||
|-
|| || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26
|-
|| || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27
|-
|| || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29
|-
|| || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28
|-
|| || || GND || 26 || 45 || GND || ||
|-
|| || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN ||
|-
|| || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP ||
|-
|| || || GND || 29 || 42 || USB1_ID || USB1_ID ||
|-
|| || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS ||
|-
|| || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || ||
|-
|| || || GND || 32 || 39 || USB2_DN || USB2_DN ||
|-
|| || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP ||
|-
|| || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID ||
|-
|| || || GND || 35 || 36 || RTC_VDD || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || VIN || 1 || 70 || VIN || || ||
|-
|| || || VIN || 2 || 69 || VIN || || ||
|-
|| || || VIN || 3 || 68 || VIN || || ||
|-
|| || || VIN || 4 || 67 || VIN || || ||
|-
|| || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29 ||
|-
|| GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || GND || 30 || 41 || GND || || ||
|-
|| GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || GND || 33 || 38 || GND || || ||
|-
|| || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-18T09:44:41Z

SebastienSz: /* J4 connector */

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO
|-
|| || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07
|-
|| || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08
|-
|| || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06
|-
|| || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09
|-
|| || || GND || 5 || 66 || GND || ||
|-
|| || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11
|-
|| || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12
|-
|| || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10
|-
|| || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13
|-
|| || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || ||
|-
|| || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23
|-
|| || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24
|-
|| || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22
|-
|| || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25
|-
|| || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19
|-
|| || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18
|-
|| || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17
|-
|| || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16
|-
|| || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21
|-
|| || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20
|-
|| || || GND || 21 || 50 || GND || ||
|-
|| || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26
|-
|| || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27
|-
|| || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29
|-
|| || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28
|-
|| || || GND || 26 || 45 || GND || ||
|-
|| || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN ||
|-
|| || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP ||
|-
|| || || GND || 29 || 42 || USB1_ID || USB1_ID ||
|-
|| || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS ||
|-
|| || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || ||
|-
|| || || GND || 32 || 39 || USB2_DN || USB2_DN ||
|-
|| || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP ||
|-
|| || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID ||
|-
|| || || GND || 35 || 36 || RTC_VDD || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || VIN || 1 || 70 || VIN || || ||
|-
|| || || VIN || 2 || 69 || VIN || || ||
|-
|| || || VIN || 3 || 68 || VIN || || ||
|-
|| || || VIN || 4 || 67 || VIN || || ||
|-
|| || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30
|-
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29 ||
|-
|| GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || GND || 30 || 41 || GND || || ||
|-
|| GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || GND || 33 || 38 || GND || || ||
|-
|| || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-18T09:44:34Z

SebastienSz: /* J2 connector */

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none; text-align:center;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO
|-
|| || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07
|-
|| || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08
|-
|| || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06
|-
|| || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09
|-
|| || || GND || 5 || 66 || GND || ||
|-
|| || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11
|-
|| || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12
|-
|| || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10
|-
|| || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13
|-
|| || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || ||
|-
|| || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23
|-
|| || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24
|-
|| || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22
|-
|| || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25
|-
|| || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19
|-
|| || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18
|-
|| || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17
|-
|| || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16
|-
|| || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21
|-
|| || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20
|-
|| || || GND || 21 || 50 || GND || ||
|-
|| || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26
|-
|| || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27
|-
|| || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29
|-
|| || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28
|-
|| || || GND || 26 || 45 || GND || ||
|-
|| || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN ||
|-
|| || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP ||
|-
|| || || GND || 29 || 42 || USB1_ID || USB1_ID ||
|-
|| || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS ||
|-
|| || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || ||
|-
|| || || GND || 32 || 39 || USB2_DN || USB2_DN ||
|-
|| || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP ||
|-
|| || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID ||
|-
|| || || GND || 35 || 36 || RTC_VDD || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || VIN || 1 || 70 || VIN || || ||
|-
|| || || VIN || 2 || 69 || VIN || || ||
|-
|| || || VIN || 3 || 68 || VIN || || ||
|-
|| || || VIN || 4 || 67 || VIN || || ||
|-
|| || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30
|-
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29 ||
|-
|| GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || GND || 30 || 41 || GND || || ||
|-
|| GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || GND || 33 || 38 || GND || || ||
|-
|| || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-18T09:43:13Z

SebastienSz:

= J2 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO
|-
|| || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07
|-
|| || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08
|-
|| || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06
|-
|| || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09
|-
|| || || GND || 5 || 66 || GND || ||
|-
|| || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11
|-
|| || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12
|-
|| || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10
|-
|| || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13
|-
|| || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || ||
|-
|| || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23
|-
|| || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24
|-
|| || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22
|-
|| || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25
|-
|| || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19
|-
|| || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18
|-
|| || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17
|-
|| || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16
|-
|| || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21
|-
|| || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20
|-
|| || || GND || 21 || 50 || GND || ||
|-
|| || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26
|-
|| || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27
|-
|| || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29
|-
|| || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28
|-
|| || || GND || 26 || 45 || GND || ||
|-
|| || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN ||
|-
|| || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP ||
|-
|| || || GND || 29 || 42 || USB1_ID || USB1_ID ||
|-
|| || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS ||
|-
|| || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || ||
|-
|| || || GND || 32 || 39 || USB2_DN || USB2_DN ||
|-
|| || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP ||
|-
|| || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID ||
|-
|| || || GND || 35 || 36 || RTC_VDD || ||
|-
|}

= J4 connector =

{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || VIN || 1 || 70 || VIN || || ||
|-
|| || || VIN || 2 || 69 || VIN || || ||
|-
|| || || VIN || 3 || 68 || VIN || || ||
|-
|| || || VIN || 4 || 67 || VIN || || ||
|-
|| || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || GND || 7 || 64 || GND || || ||
|- style="background: yellow;"
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM SoM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30
|-
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29 ||
|-
|| GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || GND || 30 || 41 || GND || || ||
|-
|| GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || GND || 33 || 38 || GND || || ||
|-
|| || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-18T09:35:54Z

SebastienSz:

{| class="wikitable"
|+ J2 connector
|-
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO
|-
|| || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07
|-
|| || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08
|-
|| || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06
|-
|| || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09
|-
|| || || GND || 5 || 66 || GND || ||
|-
|| || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11
|-
|| || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12
|-
|| || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10
|-
|| || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13
|-
|| || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || ||
|-
|| || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23
|-
|| || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24
|-
|| || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22
|-
|| || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25
|-
|| || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19
|-
|| || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18
|-
|| || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17
|-
|| || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16
|-
|| || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21
|-
|| || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20
|-
|| || || GND || 21 || 50 || GND ||
|-
|| || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26
|-
|| || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27
|-
|| || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29
|-
|| || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28
|-
|| || GND || 26 || 45 || GND || ||
|-
|| || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN ||
|-
|| || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP ||
|-
|| || || GND || 29 || 42 || USB1_ID || USB1_ID ||
|-
|| || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS ||
|-
|| || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || ||
|-
|| || GND || 32 || 39 || USB2_DN || USB2_DN ||
|-
|| || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP ||
|-
|| || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID ||
|-
|| || GND || 35 || 36 || RTC_VDD || ||
|-
|}

{| class="wikitable"
|+ J4 connector
|-
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO !! Comments
|-
|| || || VIN || 1 || 70 || VIN || || ||
|-
|| || || VIN || 2 || 69 || VIN || || ||
|-
|| || || VIN || 3 || 68 || VIN || || ||
|-
|| || || VIN || 4 || 67 || VIN || || ||
|-
|| || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || || ||
|-
|| || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || || ||
|-
|| || || GND || 7 || 64 || GND || ||
|- style="background: yellow;"
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30 || rowspan="2" | Not available on OPOS8MM with Bluetooth chip.
|- style="background: yellow;"
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30
|-
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29 ||
|-
|| GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15 ||
|-
|| GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14 ||
|-
|| GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13 ||
|-
|| GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12 ||
|-
|| GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11 ||
|-
|| GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10 ||
|-
|| GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09 ||
|-
|| GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08 ||
|-
|| GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07 ||
|-
|| GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06 ||
|-
|| GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05 ||
|-
|| GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04 ||
|-
|| GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01 ||
|-
|| || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00 ||
|-
|| GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || || ||
|-
|| GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || || ||
|-
|| GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || || ||
|-
|| GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || || ||
|-
|| || || GND || 28 || 43 || ETH_TXRXM_C || || ||
|-
|| GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || || ||
|-
|| || || GND || 30 || 41 || GND || || ||
|-
|| GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || || ||
|-
|| GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || || ||
|-
|| || || GND || 33 || 38 || GND || || ||
|-
|| || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || || ||
|-
|| || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || || ||
|}

OPOS8MM PINOUT

2021-02-18T09:21:41Z

SebastienSz: Created page with "{| class="wikitable" |+ J2 connector |- ! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO |- || || MIPI_DSI_D0_N ||..."

{| class="wikitable"
|+ J2 connector
|-
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO
|-
|| || MIPI_DSI_D0_N || DSI_D0_N || 1 || 70 || ECSPI1_MOSI || ECSPI1_MOSI || GPIO5_IO07
|-
|| || MIPI_DSI_D0_P || DSI_D0_P || 2 || 69 || ECSPI1_MISO || ECSPI1_MISO || GPIO5_IO08
|-
|| || MIPI_DSI_D1_N || DSI_D1_N || 3 || 68 || ECSPI1_SCLK || ECSPI1_SCLK || GPIO5_IO06
|-
|| || MIPI_DSI_D1_P || DSI_D1_P || 4 || 67 || ECSPI1_SS0 || ECSPI1_SS0 || GPIO5_IO09
|-
|| || || GND || 5 || 66 || GND || ||
|-
|| || MIPI_DSI_CLK_N || DSI_CLK_N || 6 || 65 || ECSPI2_MOSI || ECSPI2_MOSI || GPIO5_IO11
|-
|| || MIPI_DSI_CLK_P || DSI_CLK_P || 7 || 64 || ECSPI2_MISO || ECSPI2_MISO || GPIO5_IO12
|-
|| || || GND || 8 || 63 || ECSPI2_SCLK || ECSPI2_SCLK || GPIO5_IO10
|-
|| || MIPI_DSI_D2_N || DSI_D2_N || 9 || 62 || ECSPI2_SS0 || ECSPI2_SS0 || GPIO5_IO13
|-
|| || MIPI_DSI_D2_P || DSI_D2_P || 10 || 61 || GND || ||
|-
|| || MIP_DSI_D3_N || DSI_D3_N || 11 || 60 || ECSPI3_MOSI || UART1_TXD || GPIO5_IO23
|-
|| || MIPI_DSI_D3_P || DSI_D3_P || 12 || 59 || ECSPI3_MISO || UART2_RXD || GPIO5_IO24
|-
|| || || GND || 13 || 58 || ECSPI3_SCLK || UART1_RXD || GPIO5_IO22
|-
|| || MIPI_CSI_D0_N || CSI_D0_N || 14 || 57 || ECSPI3_SS0 || UART2_TXD || GPIO5_IO25
|-
|| || MIPI_CSI_D0_P || CSI_D0_P || 15 || 56 || I2C3_SDA || I2C3_SDA || GPIO5_IO19
|-
|| || MIPI_CSI_D1_N || CSI_D1_N || 16 || 55 || I2C3_SCL || I2C3_SCL || GPIO5_IO18
|-
|| || MIPI_CSI_D1_P || CS_D1_P || 17 || 54 || I2C2_SDA || I2C2_SDA || GPIO5_IO17
|-
|| || || GND || 18 || 53 || I2C2_SCL || I2C2_SCL || GPIO5_IO16
|-
|| || MIPI_CSI_CLK_P || CSI_CLK_P || 19 || 52 || I2C4_SDA || I2C4_SDA || GPIO5_IO21
|-
|| || MIPICSI_CLK_N || CSI_CLK_N || 20 || 51 || I2C4_SCL || I2C4_SCL || GPIO5_IO20
|-
|| || || GND || 21 || 50 || GND ||
|-
|| || MIPI_CSI_D2_N || CSI_D2_N || 22 || 49 || UART3_TXD || UART3_TXD || GPIO5_IO26
|-
|| || MIPI_CSI_D2_P || CSI_D2_P || 23 || 48 || UART3_RXD || UART3_RXD || GPIO5_IO27
|-
|| || MIPI_CSI_D3_N || CSI_D3_N || 24 || 47 || UART4_TXD || UART4_TXD || GPIO5_IO29
|-
|| || MIPI_CSI_D3_P || CSI_D3_P || 25 || 46 || UART4_RXD || UART4_RXD || GPIO5_IO28
|-
|| || GND || 26 || 45 || GND || ||
|-
|| || PCIE_RXN_N || PCIE_RXN_N || 27 || 44 || USB1_DN || USB1_DN ||
|-
|| || PCIE_RXN_P || PCIE_RXN_P || 28 || 43 || USB1_DP || USB1_DP ||
|-
|| || || GND || 29 || 42 || USB1_ID || USB1_ID ||
|-
|| || PCIE_TXN_N || PCIE_TXN_N || 30 || 41 || USB_VBUS || USB{1,2}_VBUS ||
|-
|| || PCIE_TXN_P || PCIE_TXN_P || 31 || 40 || GND || ||
|-
|| || GND || 32 || 39 || USB2_DN || USB2_DN ||
|-
|| || PCIE_CLK_N || PCIE_CLK_N || 33 || 38 || USB2_DP || USB2_DP ||
|-
|| || PCIE_CLK_P || PCIE_CLK_P || 34 || 37 || USB2_ID || USB2_ID ||
|-
|| || GND || 35 || 36 || RTC_VDD || ||
|-
|}

{| class="wikitable"
|+ J4 connector
|-
! GPIO !! i.MX8MM pad name !! OPOS8MM pad name !! Pin !! Pin !! OPOS8MM pad name !! i.MX8MM pad name !! GPIO
|-
|| || || VIN || 1 || 70 || VIN || ||
|-
|| || || VIN || 2 || 69 || VIN || ||
|-
|| || || VIN || 3 || 68 || VIN || ||
|-
|| || || VIN || 4 || 67 || VIN || ||
|-
|| || || VDD_3V3 || 5 || 66 || NVCC_SNVS_1V8 || ||
|-
|| || ONOFF || ONOFF || 6 || 65 || SYS_RST_B || ||
|-
|| || || GND || 7 || 64 || GND ||
|-
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30
|-
|| GPIO5_IO00 || SAI3_TXC || UART2_TX || 8 || 63 || UART2_RTS || SAI3_RXD || GPIO4_IO30
|-
|| GPIO4_IO31 || SAI3_TXFS || UART2_RX || 9 || 62 || UART2_CTS || SAI3_RXC || GPIO4_IO29
|-
|| GPIO4_IO21 || SAI2_RXFS || UART1_TX || 10 || 61 || GPIO1_15 || GPIO1_15 || GPIO1_15
|-
|| GPIO4_IO22 || SAI2_RXC || UART1_RX || 11 || 60 || GPIO1_14 || GPIO1_14 || GPIO1_14
|-
|| GPIO4_IO23 || SAI2_RXD0 || UART1_RTS || 12 || 59 || GPIO1_13 || GPIO1_13 || GPIO1_13
|-
|| GPIO4_IO24 || SAI2_TXFS || UART1_CTS || 13 || 58 || GPIO1_12 || GPIO1_12 || GPIO1_12
|-
|| GPIO5_IO05 || SPDIF_EXT_CLK || SPDIF_EXT_CLK || 14 || 57 || GPIO1_11 || GPIO1_11 || GPIO1_11
|-
|| GPIO5_IO03 || SPDIF_TX || SPDIF_TX || 15 || 56 || GPIO1_10 || GPIO1_10 || GPIO1_10
|-
|| GPIO5_IO04 || SPDIF_RX || SPDIF_RX || 16 || 55 || GPIO1_09 || GPIO1_09 || GPIO1_09
|-
|| GPIO3_IO24 || SAI5_RXD3 || SAI5_RXD3 || 17 || 54 || GPIO1_08 || GPIO1_08 || GPIO1_08
|-
|| GPIO3_IO23 || SAI5_RXD2 || SAI5_RXD2 || 18 || 53 || GPIO1_07 || GPIO1_07 || GPIO1_07
|-
|| GPIO3_IO22 || SAI5_RXD1 || SAI5_RXD1 || 19 || 52 || GPIO1_06 || GPIO1_06 || GPIO1_06
|-
|| GPIO3_IO21 || SAI5_RXD0 || SAI5_RXD0 || 20 || 51 || GPIO1_05 || GPIO1_05 || GPIO1_05
|-
|| GPIO3_IO20 || SAI5_RXC || SAI5_RXC || 21 || 50 || GPIO1_04 || GPIO1_04 || GPIO1_04
|-
|| GPIO3_IO25 || SAI5_MCLK || SAI5_MCLK || 22 || 49 || GPIO1_01 || GPIO1_01 || GPIO1_01
|-
|| || BOOT_MODE0 || BOOT_MODE0 || 23 || 48 || GPIO1_00 || GPIO1_00 || GPIO1_00
|-
|| GPIO2_IO12 || SD2_CD_B || SD2_CD_B || 24 || 47 || GND || ||
|-
|| GPIO2_IO15 || SD2_DATA0 || SD2_DATA0 || 25 || 46 || ETH_TXRXM_D || ||
|-
|| GPIO2_IO16 || SD2_DATA1 || SD2_DATA1 || 26 || 45 || ETH_TXRXP_D || ||
|-
|| GPIO2_IO14 || SD2_CMD || SD2_CMD || 27 || 44 || GND || ||
|-
|| || || GND || 28 || 43 || ETH_TXRXM_C || ||
|-
|| GPIO2_IO13 || SD2_CLK || SD2_CLK || 29 || 42 || ETH_TXRXP_C || ||
|-
|| || || GND || 30 || 41 || GND || ||
|-
|| GPIO2_IO18 || SD2_DATA3 || SD2_DATA3 || 31 || 40 || ETH_TXRXM_B || ||
|-
|| GPIO2_IO17 || SD2_DATA2 || SD2_DATA2 || 32 || 39 || ETH_TXRXP_B || ||
|-
|| || || GND || 33 || 38 || GND || ||
|-
|| || || ETH_ACTIVITY || 34 || 37 || ETH_TXRXM_A || ||
|-
|| || || ETH_LINK# || 35 || 36 || ETH_TXRXP_A || ||
|}

Bluetooth

2020-12-07T08:34:08Z

SebastienSz: Add OPOS8MM to bring up section

This page will give you all the informations needed to have a running Bluetooth configuration on your Armadeus board.

==Hardware==
First you have to get a compatible hardware. Currently there are 6 solutions:
* You have an [[OPOS8MM]] or an [[OPOS6UL]] board with the Wi-Fi/Bluetooth chip integrated.
* You have an [[APF6]] board with the Wi-Fi/Bluetooth chip integrated. The chip is on the [[APF6]] Dual and Quad boards by default.
* You have an [[APF51Dev]] board, then you're a lucky man because Bluetooth is integrated on the board ;-)
* If you have an [[APF27Dev]], then you can get a [[Wireless extension board]] with Wi-Fi/Bluetooth option from Armadeus Systems
* Otherwise: get a cheap USB<->Bluetooth adapter (requires an USB Host port) or a RS232<->Bluetooth adapter

===Tested USB adapters===
{| border="1" cellpadding="5" cellspacing="0" summary="Supported USB<->Bluetooth dongle"
|- style="background:#efefef;"
!'''Model''' || colspan="2" | '''Status APF9328 / APF27''' ||'''Chipset''' || '''Comments'''
|----------------
|'''BELKIN - Mini Bluetooth Adapter''' [[Image:Belkin_Mini_Bluetooth.jpg]] || style="background:#ffff00;" | TBT || style="background:#ff0000;" | KO || Product: BLUETOOTH USB +EDR ADAPTER v2.1 UHE Manufacturer: Broadcom Corp
|| # hciconfig hci1 up piscan
btusb_submit_intr_urb: hci1 urb c3bdac40 submission failed (28) 
Can't init device hci1: Input/output error (5)

|----------------
|'''TRUST - Bluetooth 2.1 USB Adapter''' [[Image:Trust_Small_Bluetooth.jpg]] || style="background:#ffff00;" | TBT || style="background:#ff0000;" | KO || Product: BCM2046B1 Manufacturer: Broadcom || # hciconfig hci1 up piscan
btusb_submit_intr_urb: hci1 urb c3bdac40 submission failed (28) 
Can't init device hci1: Input/output error (5)
|----------------
|'''[http://www.rueducommerce.fr/Peripheriques-Reseaux-wifi/Adaptateur-USB-Bluetooth/Adaptateur-USB-Bluetooth/RUEDUCOMMERCE/2848164-Mini-adaptateur-USB-Bluetooth-portee-100m-19x15x5-39-mm.htm RUEDUCOMMERCE - Mini adaptateur USB Bluetooth'''] [[Image:RDC_USB_Bluetooth.jpg]]|| style="background:#ffff00;" | TBT || style="background:#00ff00;" | OK || Manufacturer: Cambridge Silicon Radio ||
|----------------
|'''GIGABYTE - GN-BTD01''' [[Image:Gigabyte_gn-btd01.jpg]]|| style="background:#ffff00;" | TBT || style="background:#00ff00;" | OK || Manufacturer: Cambridge Silicon Radio || Bluetooth 1.1 ?
|----------------
|'''BELKIN - F8T003 v2''' || style="background:#ffff00;" | TBT || style="background:#00ff00;" | OK || Manufacturer: Cambridge Silicon Radio ||
|----------------
|'''D-LINK - DBT-122''' || style="background:#ffff00;" | TBT || style="background:#00ff00;" | OK || Product: BCM2035 Manufacturer: Broadcom ||
|----------------
|}
 

==Software==
Bluetooth Linux stack is divided into several parts:
* kernel drivers
* userland libraries/daemon (bluez)

===Driver installation===
* (Done by default on [[APF27]], [[APF51]], [[APF6]] and [[OPOS6UL]])
<pre class="host">
$ make linux-menuconfig
</pre>
<pre class="config">
[*] Networking support --->
<M> Bluetooth subsystem support --->
--- Bluetooth subsystem support
<M> L2CAP protocol support
<M> SCO links support
<M> RFCOMM protocol support
[*] RFCOMM TTY support
<M> BNEP protocol support
[ ] Multicast filter support (NEW)
[ ] Protocol filter support (NEW)
<M> HIDP protocol support
Bluetooth device drivers --->
<M> HCI USB driver
< > HCI SDIO driver (NEW)
<M> HCI UART driver
[*] UART (H4) protocol support
[*] BCSP protocol support
[ ] HCILL protocol support (NEW)
< > HCI BCM203x USB driver (NEW)
< > HCI BPA10x USB driver (NEW)
< > HCI BlueFRITZ! USB driver (NEW)
< > HCI VHCI (Virtual HCI device) driver (NEW)
</pre>
<pre class="host">
$ make
</pre>

===Bluez installation===
(Done by default on [[APF51]], [[APF6]] and [[OPOS6UL]])
<pre class="host">
$ make menuconfig
</pre>
<pre class="config">
Package Selection for the target --->
...
[*] XML handling --->
[*] libxml2
...
[*] Hardware handling --->
[*] dbus
XML library to use (libxml2)
...
Networking applications --->
[*] bluez
[*] bluez-utils
</pre>
<pre class="host">
$ make
</pre>

==Custom Bring up (each hardware may have a different init sequence)==

===OPOS8MM===

OPOS8MM has a Bluetooth chip connected to the i.MX8MM UART2 (''/dev/ttymxc2'').

* Start the Bluetooth deamon
<pre class="apf">
# /usr/libexec/bluetooth/bluetoothd &
#
</pre>

* Power on the chip.
<pre class="apf">
# gpioset 2 16=1
</pre>

* Attach the chip.
<pre class="apf">
# btattach -B /dev/ttymxc1 -P bcm -S 921600 &
Attaching Primary controller to /dev/ttymxc1
Switched line discipline from 0 to 15
Device index 0 attached
Bluetooth: hci0: BCM: chip id 107
Bluetooth: hci0: BCM: features 0x2f
Bluetooth: hci0: BCM4345C0
Bluetooth: hci0: BCM4345C0 (003.001.025) build 0000
Bluetooth: hci0: BCM4345C0 (003.001.025) build 0127 # this message takes few seconds to appear
#
</pre>

* [[Bluetooth#Common Bring up|Go to "Common Bring up" section]]

===OPOS6UL===
{| border="1" cellpadding="5" cellspacing="0" summary="put summary here"
|- style="background:#efefef;" align="center"
! width="50%" | OPOS6UL !! width="50%" | OPOS6ULNANO
|-
| OPOS6UL has a CM-43438 chip (based on BCM43438), connected to the i.MX6UL UART8 (''/dev/ttymxc7'')
| OPOS6ULNANO has a Murata module with CYM4343 chipset, connected to the i.MX6UL UART3 (''/dev/ttymxc2'')
|-
| <pre class="apf"># export BTRESET=42</pre> <pre class="apf"># export BTDEV=/dev/ttymxc7</pre>
| <pre class="apf"># export BTRESET=99</pre> <pre class="apf"># export BTDEV=/dev/ttymxc2</pre>
|}

* Start the bluetooth deamon and attach your chipset to the kernel bluez UART driver:
<pre class="apf">
# /usr/libexec/bluetooth/bluetoothd &
#
</pre>

* Wake up the chip
<pre class="apf">
# echo $BTRESET > /sys/class/gpio/export
# echo out > /sys/class/gpio/gpio$BTRESET/direction
# echo 0 > /sys/class/gpio/gpio$BTRESET/value
# sleep 1
# echo 1 > /sys/class/gpio/gpio$BTRESET/value
# sleep 1
</pre>

* Attach the chip. Before running the following command, be sure that the file ''/etc/firmware/BCM43430A1.hcd'' exists (if not, it can be obtained (wget) [https://github.com/OpenELEC/misc-firmware/blob/master/firmware/brcm/BCM43430A1.hcd here ?] or [https://aur.archlinux.org/cgit/aur.git/plain/BCM43430A1.hcd?h=pi-bluetooth here]) !
<pre class="apf">
# hciattach -t 30 $BTDEV bcm43xx 921600 flow
bcm43xx_init
Set Controller UART speed to 921600 bit/s
Flash firmware /etc/firmware/BCM43430A1.hcd
Set Controller UART speed to 921600 bit/s
Device setup complete
#
</pre>
* To choose bluetooth MAC address, add it to ''hciattach'' command
<pre class="apf">
# hciattach -t 30 $BTDEV bcm43xx 921600 flow bdaddr 11:22:33:44:55:66
</pre>
* [[Bluetooth#Common Bring up|Go to "Common Bring up" section]]

===APF6===
* APF6 has a jorjin chip connected to the i.MX6 UART2 (ttymxc1)

* Start the bluetooth deamon and attach your chipset to the kernel bluez UART driver:
<pre class="apf">
# /usr/sbin/bluetoothd
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP socket layer initialized
</pre>

or if you are using BlueZ 5
<pre class="apf">
# /usr/libexec/bluetooth/bluetoothd &
</pre>

* Wake up the chip
<pre class="apf">
# export BTRESET=43
# echo $BTRESET > /sys/class/gpio/export
# echo out > /sys/class/gpio/gpio$BTRESET/direction
# echo 0 > /sys/class/gpio/gpio$BTRESET/value
# sleep 1
# echo 1 > /sys/class/gpio/gpio$BTRESET/value
# sleep 1
</pre>

* Attach the chip. Before running the following command, be sure that the file ''/lib/firmware/TIInit_7.6.15.bts'' exists ! You can download it [https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_7.6.15.bts here] (click on the 'Raw' button)
<pre class="apf">
# /usr/sbin/hciattach -s 115200 ttymxc1 texas 115200
Found a Texas Instruments' chip!
Firmware file : /lib/firmware/TIInit_7.6.15.bts
Loaded BTS script version 1
Device setup complete

#
</pre>

* [[Bluetooth#Common Bring up|Go to "Common Bring up" section]]

===APF51Dev===
* [[APF51Dev]] has a CSR BlueCore 4 chipset connected to the i.MX51 UART3 (ttymxc1)

* On recent kernel using device tree, you have to "wake up" the chip:
<pre class="apf">
# export BTRESET=60
# echo $BTRESET > /sys/class/gpio/export
# echo out > /sys/class/gpio/gpio$BTRESET/direction
# echo 0 > /sys/class/gpio/gpio$BTRESET/value
# sleep 1
# echo 1 > /sys/class/gpio/gpio$BTRESET/value
# sleep 1
</pre>

* Start the bluetooth deamon and attach your chipset to the kernel bluez UART driver:
<pre class="apf">
# /usr/sbin/bluetoothd
# /usr/sbin/hciattach -s 115200 ttymxc1 csr 115200

CSR build ID 0x00-0x37
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
</pre>

* [[Bluetooth#Common Bring up|Go to "Common Bring up" section]]

===APF27Dev + APW===
* [[Wireless extension board|APW]] has a CSR BlueCore 4 chipset connected to the i.MX27 serial port ttySMX5 (UART6)
* Reset it:
<pre class="apf">
# source /usr/bin/gpio_helpers.sh
# gpio_mode PB14 1
# gpio_set_value PB14 0; sleep 1; gpio_set_value PB14 1; sleep 1
</pre>
* Attach it to the kernel bluez UART driver:
<pre class="apf">
# /usr/sbin/hciattach -s 921600 ttySMX5 csr 921600
</pre>
* [[Bluetooth#Common Bring up|Go to "Common Bring up" section]]

===USB module===
* Make sure your hardware is connected to the APF. '''If using an USB dongle''', load corresponding driver:
<pre class="apf">
# modprobe btusb
Bluetooth: Core ver 2.14
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: Generic Bluetooth USB driver ver 0.4
usbcore: registered new interface driver btusb
</pre>

==Common Bring up==
* Now that your hardware Bluetooth interface is up, check if it was correctly detected by BlueZ:
<pre class="apf">
# hciconfig
hci0: Type: USB or UART
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
</pre>
* If interface is DOWN, bring it up:
<pre class="apf">
# hciconfig hci0 up piscan
</pre>
* Check your Bluetooth device is correctly initialized:
<pre class="apf">
# hcitool dev
Devices:
hci0 00:10:60:D1:92:0F
</pre>
* From Bluez5, everything can now be done with ''bluetoohctl'' interactive command:
<pre class="apf">
# bluetoothctl
[NEW] Controller 5C:F3:70:34:D6:66 BlueZ 5.43 [default]
[bluetooth]# power on
Changing power on succeeded
[CHG] Controller 5C:F3:70:34:D6:66 Powered: yes

[bluetooth]# scan on
Discovery started
[CHG] Controller 5C:F3:70:34:D6:66 Discovering: yes

[bluetooth]# agent on
Agent registered
</pre>

==Usage==
===Scanning network===
* To get surrounding devices addresses and names:
<pre class="apf">
# hcitool scan
Scanning ...
</pre>
* To get surrounding devices addresses and classes:
<pre class="apf">
# hcitool inq
Inquiring ...
</pre>

===Get info on a given device===
<pre class="apf">
# hcitool info 00:19:0E:xx:xx:xx
...
</pre>

===Pinging other devices===
<pre class="apf">
# l2ping 00:19:0E:xx:xx:xx
Ping: 00:19:0E:xx:xx:xx from 00:19:88:xx:xx:xx (data size 44) ...
44 bytes from 00:19:0E:xx:xx:xx id 0 time 38.05ms
44 bytes from 00:19:0E:xx:xx:xx id 1 time 37.09ms
...
</pre>
Here 00:19:0E:xx:xx:xx is the Bluetooth MAC address of the Host.

===Change advertising name===
* to change your module's name on Bluetooth network:
<pre class="apf">
# hciconfig hci0 name ARMADEUS
</pre>
* From bluez5, you can also specify advertising name in ''/etc/bluetooth/main.conf'' file (%h = hostname, %d = device number):
<pre class="apf">
[General]
Name = OPOS
</pre>
or specify it from ''bluetoothctl'' tool:
<pre class="apf">
# bluetoothctl
[bluetooth]# system-alias OPOSxxx
</pre>

==Advanced usages: Setup a Terminal between a PC and your APF through Bluetooth==
===On the APF===
* the first step is to create the corresponding node for the future connection:
<pre class="apf">
# mknod /dev/rfcomm0 c 216 0
</pre>
* then, listen to an incoming connection, on the ''rfcomm0'' (here channel 7 is chosen):
<pre class="apf">
# rfcomm -i hci0 listen /dev/rfcomm0 7 &
</pre>
{{Note|If RFCOMM protocol is not built statically in your kernel, you might need to load it before use with: <pre class="apf"># modprobe rfcomm </pre>}}

{{Note|If you plan to connect from your smartphone, don't specify a channel number as most apps will try to connect to channel 1: <pre class="apf"># rfcomm -i hci0 listen /dev/rfcomm0 &</pre>}}
* and the last step, when the connection is open, is to connect a terminal (through getty) to the device ''/dev/rfcomm0'':
<pre class="apf">
# getty 38400 /dev/rfcomm0
</pre>

===On your Host PC===
* after the two first steps on the APF, you need to connect the PC to the APF with the same channel (7):
<pre class="host">
$ rfcomm connect 0 00:19:88:2B:xx:xx 7 (replace 00:19:88:2B:xx:xx with the Bluetooth @ of your APF)
</pre>
* and configure ''minicom'' (''$HOME/.minirc.dfl''):
pu port /dev/rfcomm0
pu baudrate 38400
pu bits 8
pu parity N
pu stopbits 1
* when ''getty'' is running on the APF/OPOS, you could you connect with ''minicom'':
<pre class="host">
$ minicom -o
</pre>
* it could be a good idea to create an additional user account for remotely login through Bluetooth, by following [[Adding_users|these instructions]].

===On your Android smartphone===
You can also setup a serial terminal connection between your OPOS and your Android smartphone. Procedure is quite similar to the one above for PC, except:
* install "BlueTerm" or "Serial Bluetooth Terminal" app on your smartphone
* if using bluez-5, launch bluetooth daemon in compatibility mode:
<pre class="apf">
# bluetoothctl --version
bluetoothctl: 5.54
# /usr/libexec/bluetooth/bluetoothd --compat &
</pre>
* use sdptool to add RFCOMM profile to Bluetooth stack:
<pre class="apf">
# sdptool add SP
</pre>
* connect your app to right Bluetooth device... that's it ;-) (you may have to configure your app in terminal mode, with no echo and extended receive buffer)

==Advanced usages: Using a Bluetooth keyboard on your APF==
The only thing needed after having a Bluetooth correctly configured is to use this command :
<pre class="apf">
# hidd --connect keyboard_bdaddr
</pre>

==Advanced usages: Controlling your board from an android device (using rfcomm)==

===With your own App===
The following section shows how to send commands to the board from an android device via Bluetooth. The goal is to control the two LEDs present on the board. An [[APF51Dev]] and a Samsung Galaxy Tab 2 are used in this example.

On the APF:

* Enable the SPP profile. Here, it is using the channel 1.
<pre class="apf">
# sdptool add --channel=1 SP
Serial Port service registered
#
</pre>

* Listen incoming connections on the channel 1. The script ''serial-server.sh'' is located in ''demos/android/android_remote_controller''.
<pre class="apf">
# rfcomm listen hci0 1 ./serial-server.sh {}
Waiting for connection on channel 1
</pre>

On the android device:

* Deploy the app on your device. The app is available [ftp://ftp2.armadeus.com/armadeusw/apf-remote-controller.tar.gz here as source] or [ftp://ftp2.armadeus.com/armadeusw/apf-remote-controller.apk here as apk].
* Start the app.
* Enjoy :-)

===With Bluetooth Electronics App===
* This application from [http://www.keuwl.com/apps/bluetoothelectronics/ keuwl.com], can be found on Google store and is very practical to design control panel on your Android device and make then control your Bluetooh device). It is generally used with Arduino and HC-06 Bluetooth module but we will see it works perfectly on APF/OPOS SoM.
* Bluetooth Electronics uses RFCOMM to talk with device and so communication can be seen as a serial port
* Again, use ''rfcomm'' command line tool to listen for your Android device connection:
<pre class="apf">
[bluetooth]# power on
...
# rfcomm -i hci0 listen /dev/rfcomm0 &
</pre>
* Discover/pair/connect the APF/OPOS SoM from Bluetooth Electronics app
* Then configure ''/dev/rfcomm0'' created by rfcomm:
<pre class="apf">
# stty -F /dev/rfcomm0 raw -echo -echoe -echok 9600
</pre>
* and use this new serial port from your application...
* here a sample application is given; it runs on [[OPOS6UL]] and allows to light on/off the user LED, get processor temperature, get CPU usage and send text to LCD from Bluetooth Electronics panel. Serial protocol is very simple and can be guessed from [https://sourceforge.net/p/armadeus/code/ci/master/tree/target/demos/android/bluetooth-electronics/opos6ul-server.py source code].

[[File:Bluetooth_Electronics.png]]

==Advanced usages: Others==
* [[TCP/IP with Bluetooth]]
* [[OBEX]] transfers
* [[Wiimote]]

{{Note|On iOS, it is '''not''' possible to use standard Bluetooth devices that are not registered through [https://developer.apple.com/programs/mfi/ MFi Program]. The only way to communicate with your modules is to have a Bluetooth Low Energy interface and corresponding iOS software}}

==Bluetooth Low Energy (BLE)==
* This protocol enhancement for low energy networks is only available on [[APF6]], [[OPOS6UL]] and [[OPOS6UL_NANO]] modules with corresponding Wi-Fi+BLE hardware option.

* To scan for BLE devices (''hci0'' interface should be up):
<pre class="apf">
# hcitool hci0 lescan
</pre>

* Most operations can then be done with ''bluetoothctl'':
<pre class="apf">
# bluetoothctl
</pre>

===APF/OPOS as BLE device===
* Most of the job consist in developing a GATT server implementing desired functionalities/characteristics. Some examples are given in Bluez sources. For example (''python'' is needed and ''bluetoothd'' should have been launched with ''--experimental'' option):
<pre class="apf">
# hciconfig hci0 up
# /root/example-gatt-server
# hciconfig hci0 leadv (to start BLE Advertising)
</pre>
* You can then use ''BLE Scanner'' or ''LightBlue'' Android/iOS app.
* For "iBeacon" stuff, [http://www.wadewegner.com/2014/05/create-an-ibeacon-transmitter-with-the-raspberry-pi/ this tutorial] may serve as a starting example.

==Links==
* http://www.bluez.org/
* http://www.hanscees.com/bluezhowto.html
* [http://doc.ubuntu-fr.org/bluetooth_materiel-soutenu Dongle USB<->Bluetooth supportés sous Ubuntu]
* [http://www.unixgarden.com/index.php/comprendre/bluetooth-installation-et-utilisation GLMF n°88 - Bluetooth, installation et utilisation]
* [http://www.unixgarden.com/index.php/embarque/communication-de-donnees-et-d’images-issues-de-la-carte-fox-par-bluetooth GLMF n°95 - Communication de données et d'images issues de la carte Fox par Bluetooth]

[[Category:Wireless]]
[[Category:Bluetooth]]

EMMC OPOS8MM

2020-10-14T07:32:03Z

SebastienSz: /* User Data partition layout */

[[Category: eMMC]]

= OPOS8MM eMMC layout =

By default, the 4GB eMMC on [[OPOS8MM]] module has 4 physical/hardware partitions:

{| border="1" cellpadding="10" cellspacing="0" summary="OPOS8MM eMMC partitions"
|----------------
| style="width:80px;background:orange;" align="center" | Boot0
| style="width:80px;background:orange;" align="center" | Boot1
| style="background:red;" | RPMB
| style="width:500px;background:green;color:white;" align="center" | User Data
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS8MM eMMC partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot name || Size || Comment
|----------------
|boot0 || mmc dev 0 1 || 2MBytes || U-Boot is installed on this partition
|----------------
|boot1 || mmc dev 0 2 || 2MBytes || U-Boot env is installed on this partition
|----------------
|rpmb || mmc dev 0 3 || 512KBytes || Not used
|----------------
|User Data || mmc dev 0 0 || remaining space (~3,7GBytes) || Kernel, device tree and rootfs
|----------------
|}

== Boot0 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS8MM eMMC partitions"
|----------------
| style="width:10px;background:white;color:black;" align="center" | ...
| style="width:40px;background:orange;color:white;" align="center" | SPL
| style="width:100px;background:white;color:black;" align="center" | ...
| style="width:150px;background:orange;color:white;" align="center" | IMG
| style="width:150px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot0''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot0 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
||| || || Free
|----------------
|0x42 || 33 KiB (0x8400) || 215 KiB || U-Boot SPL (opos8mm-u-boot.spl)
|----------------
||| || || Free
|----------------
|0x300 || 384 KiB (0x6000) || ~700 KiB || U-Boot IMG (opos8mm-u-boot.itb)
|----------------
||| || || Free
|----------------
|}

== Boot1 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS8MM eMMC partitions"
|----------------
| style="width:50px;background:orange;color:white;" align="center" | U-Boot env
| style="width:100px;background:white;color:black;" align="center" | ...
| style="width:50px;background:orange;color:white;" align="center" | U-Boot redundant env
| style="width:100px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot1''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot1 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 16 KiB || U-Boot environment
|----------------
||| || || Free
|----------------
||| || 16 KiB || U-Boot redundant environment
|----------------
||| || || Free
|----------------
|}

== RPMB partition layout ==
* Not used !

== User Data partition layout ==

There are 3 partitions on the "User Data" physical partition:
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS8MM eMMC partitions"
|----------------
| style="width:50px;background:white;color:black;" align="center" | ...
| style="width:200px;background:green;color:white;" align="center" | Failsafe/Update (primary)
| style="width:200px;background:green;color:white;" align="center" | Default Rootfs (primary)
| style="width:600px;background:green;color:white;" align="center" | Home/Data (primary)
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS8MM eMMC User data partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot device || Linux device || Offset (bytes) || Offset (sectors/blocs) || Size || Comment
|----------------
|MBR || NA || NA || 0 || 0 || 512 bytes (1 block) || Master Boot Record + some spare space ( -> Don't touch it :-) )
|----------------
|Failsafe || mmc 0:1 || /dev/mmcblk0p1 || 1M || 2048 (0x800) || 512 MBytes (1048576 sectors) || system/rootfs to restore your board in case of problem or setup a safe update mechanism (ext4 formatted)
|----------------
|Rootfs || mmc 0:2 || /dev/mmcblk0p2 || || 1050624 (0x10800) || 512 MBytes (1048576 sectors) || the default booted rootfs is on this partition (ext4 formatted)
|----------------
|Home/Data || mmc 0:3 || /dev/mmcblk0p3 || || 2099200 (0x200800) || Rest of space: ~2,7 GBytes (5634048 sectors) || HOME can be stored on this partition (ext4 formatted)
|----------------
|}

* By default, when flashed from U-Boot, rootfs and boot are only occupying the size of the .ext4 images used during flashing. If you want to increase the rootfs/boot size to all available free space then, after Linux has booted, use the following commands:
<pre class="apf">
# resize2fs /dev/mmcblk0p2 # for Rootfs
</pre>

* Or with ''apf-config'' command:
<pre class="apf">
# apf-config
</pre>
* In menu:
<pre class="config">
| 1 Expand Filesystem(s) OS can then use all eMMC/SD space |
</pre>

Rootfs/Boot will then be extended to all the "Rootfs"/"Boot" eMMC partitions space.

==Tips==
* Commands to partition ''User Data'' from fdisk on Host PC with [[U-Boot UMS on APF & OPOS|U-Boot UMS]]. '''Check /dev/sdc is your OPOS8MM device otherwise you may destroy your PC partition table !!!''':
<pre class=host>
$ sudo echo -e 'size=512MiB,type=0x83\nsize=512MiB,type=0x83\ntype=0x83' | sfdisk /dev/sdc

$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc1
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc2
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc3

</pre>

==Links==
* [http://fr.slideshare.net/linaroorg/intro-to-emmc http://fr.slideshare.net/linaroorg/intro-to-emmc]
* https://fr.wikipedia.org/wiki/Master_boot_record ou http://poloastucien.free.fr/mbr_fat_secteurs_boot_h.html

EMMC OPOS8MM

2020-10-13T15:25:37Z

SebastienSz: Created page with "Category: eMMC = OPOS8MM eMMC layout = By default, the 4GB eMMC on OPOS8MM module has 4 physical/hardware partitions: {| border="1" cellpadding="10" cellspacing="0"..."

[[Category: eMMC]]

= OPOS8MM eMMC layout =

By default, the 4GB eMMC on [[OPOS8MM]] module has 4 physical/hardware partitions:

{| border="1" cellpadding="10" cellspacing="0" summary="OPOS8MM eMMC partitions"
|----------------
| style="width:80px;background:orange;" align="center" | Boot0
| style="width:80px;background:orange;" align="center" | Boot1
| style="background:red;" | RPMB
| style="width:500px;background:green;color:white;" align="center" | User Data
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS8MM eMMC partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot name || Size || Comment
|----------------
|boot0 || mmc dev 0 1 || 2MBytes || U-Boot is installed on this partition
|----------------
|boot1 || mmc dev 0 2 || 2MBytes || U-Boot env is installed on this partition
|----------------
|rpmb || mmc dev 0 3 || 512KBytes || Not used
|----------------
|User Data || mmc dev 0 0 || remaining space (~3,7GBytes) || Kernel, device tree and rootfs
|----------------
|}

== Boot0 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS8MM eMMC partitions"
|----------------
| style="width:10px;background:white;color:black;" align="center" | ...
| style="width:40px;background:orange;color:white;" align="center" | SPL
| style="width:100px;background:white;color:black;" align="center" | ...
| style="width:150px;background:orange;color:white;" align="center" | IMG
| style="width:150px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot0''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot0 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
||| || || Free
|----------------
|0x42 || 33 KiB (0x8400) || 215 KiB || U-Boot SPL (opos8mm-u-boot.spl)
|----------------
||| || || Free
|----------------
|0x300 || 384 KiB (0x6000) || ~700 KiB || U-Boot IMG (opos8mm-u-boot.itb)
|----------------
||| || || Free
|----------------
|}

== Boot1 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS8MM eMMC partitions"
|----------------
| style="width:50px;background:orange;color:white;" align="center" | U-Boot env
| style="width:100px;background:white;color:black;" align="center" | ...
| style="width:50px;background:orange;color:white;" align="center" | U-Boot redundant env
| style="width:100px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot1''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot1 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 16 KiB || U-Boot environment
|----------------
||| || || Free
|----------------
||| || 16 KiB || U-Boot redundant environment
|----------------
||| || || Free
|----------------
|}

== RPMB partition layout ==
* Not used !

== User Data partition layout ==

There are 3 partitions on the "User Data" physical partition:
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS8MM eMMC partitions"
|----------------
| style="width:50px;background:white;color:black;" align="center" | ...
| style="width:100px;background:green;color:white;" align="center" | Failsafe/Update (primary)
| style="width:600px;background:green;color:white;" align="center" | Default Rootfs (primary)
| style="width:600px;background:green;color:white;" align="center" | Home/Data (primary)
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS8MM eMMC User data partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot device || Linux device || Offset (bytes) || Offset (sectors/blocs) || Size || Comment
|----------------
|MBR || NA || NA || 0 || 0 || 512 bytes (1 block) || Master Boot Record + some spare space ( -> Don't touch it :-) )
|----------------
|Failsafe || mmc 0:1 || /dev/mmcblk0p1 || 1M || 2048 (0x800) || 512 MBytes (1048576 sectors) || system/rootfs to restore your board in case of problem or setup a safe update mechanism (ext4 formatted)
|----------------
|Rootfs || mmc 0:2 || /dev/mmcblk0p2 || || 1050624 (0x10800) || 512 MBytes (1048576 sectors) || the default booted rootfs is on this partition (ext4 formatted)
|----------------
|Home/Data || mmc 0:3 || /dev/mmcblk0p3 || || 2099200 (0x200800) || Rest of space: ~2,7 GBytes (5634048 sectors) || HOME can be stored on this partition (ext4 formatted)
|----------------
|}

* By default, when flashed from U-Boot, rootfs and boot are only occupying the size of the .ext4 images used during flashing. If you want to increase the rootfs/boot size to all available free space then, after Linux has booted, use the following commands:
<pre class="apf">
# resize2fs /dev/mmcblk0p2 # for Rootfs
</pre>

* Or with ''apf-config'' command:
<pre class="apf">
# apf-config
</pre>
* In menu:
<pre class="config">
| 1 Expand Filesystem(s) OS can then use all eMMC/SD space |
</pre>

Rootfs/Boot will then be extended to all the "Rootfs"/"Boot" eMMC partitions space.

==Tips==
* Commands to partition ''User Data'' from fdisk on Host PC with [[U-Boot UMS on APF & OPOS|U-Boot UMS]]. '''Check /dev/sdc is your OPOS8MM device otherwise you may destroy your PC partition table !!!''':
<pre class=host>
$ sudo echo -e 'size=512MiB,type=0x83\nsize=512MiB,type=0x83\ntype=0x83' | sfdisk /dev/sdc

$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc1
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc2
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc3

</pre>

==Links==
* [http://fr.slideshare.net/linaroorg/intro-to-emmc http://fr.slideshare.net/linaroorg/intro-to-emmc]
* https://fr.wikipedia.org/wiki/Master_boot_record ou http://poloastucien.free.fr/mbr_fat_secteurs_boot_h.html

Linux Debug

2019-05-03T08:31:09Z

SebastienSz: /* Observing systems clocks */

Tips to do debugging under Linux.

==Introduction==

On this page, you will find usefull informations for debugging your Linux kernel/drivers.

==Testing your custom Linux kernel before flashing it==

You can test a linux kernel you've generated without having to reflash your board and destroy your currently working image.
Indeed Linux kernel images can be loaded and started from SDRAM with U-Boot:
<pre class="apf">
BIOS> run download_kernel
MAC: 00:1e:ac:00:00:02
operating at 100M full duplex mode
Using dm9000 device
TFTP from server 192.168.0.104; our IP address is 192.168.0.10
Filename 'apf9328-linux.bin'.
Load address: 0x8000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
########
done
Bytes transferred = 1703940 (1a0004 hex)
BIOS> bootm
## Booting kernel from Legacy Image at 08000000 ...
</pre>

==Changing processor registers from Linux user space with imxregs==

This tool allows you to access i.MX registers from Linux userspace/console. This way you can debug your driver or access i.MX hardware functionnalities directly from Linux console.

In recent releases (>= 3.0) you should find this tool in ''/usr/bin/'' on your board.

===Unlock registers access===
{{Note | On [[APF51]]/[[APF28]]/[[OPOS6UL]] you don't have to explicitly unlock registers in U-Boot to access them under Linux, like explained just above}}

* To use it, you must clear i.MX PAR_1 & PAR_2 registers (registers access rights) '''before''' launching Linux kernel, so in U-Boot type (example here is for APF9328):
<pre class="apf">
BIOS> mw.l 0x00200008 0
BIOS> mw.l 0x00210008 0
</pre>
* on APF27:
<pre class="apf">
BIOS> mw 10000008 0
BIOS> mw 10020008 0
</pre>

If you use it frequently, a small script ''unlock_regs'' has been defined in U-Boot, and you can call it before booting your board:
<pre class="apf">
BIOS> run unlock_regs
BIOS> boot
</pre>

===Usage===
* Then in Linux console/terminal, launch ''imxregs'' like that:
<pre class="apf">
# imxregs REGISTER_NAME (give it the register name as printed in i.MX Ref Manual or just the begining of the name)
</pre>
or
<pre class="apf">
# imxregs (to dump all supported registers)
</pre>

===Examples===
* Show OCR1 registers of each GPIO Port:
<pre class="apf">
# imxregs OCR1
</pre>

* Write 0x00000123 to OCR1_D register:
<pre class="apf">
# imxregs OCR1_D 123
</pre>

==Changing FPGA IP's registers from Linux user space==

See [[FPGA_register|fpgaregs]] tool.

==Using DebugFS==
DebugFS is a in-kernel filesystem, similar to procfs or sysfs, that allows Linux driver to easily communicate debug informations to user space. Full documentation: http://lxr.linux.no/linux+v2.6.32/Documentation/filesystems/debugfs.txt or http://www.linuxtopia.org/online_books/linux_kernel/kernel_configuration/ch09s07.html
===Mounting it===
<pre class="apf">
# mount -t debugfs none /sys/kernel/debug
</pre>
===Showing already allocated GPIOs===
<pre class="apf">
# cat /sys/kernel/debug/gpio
GPIOs 0-31, gpio-0:
gpio-5 (LCD ) in lo
gpio-6 (LCD ) in lo
gpio-7 (LCD ) in lo
gpio-8 (LCD ) in lo
....
</pre>

===Showing clock tree===

<pre class="config">
Device Drivers --->
Common Clock Framework --->
[*] DebugFS representation of clock tree

| Creates a directory hierarchy in debugfs for visualizing the clk
| tree structure. Each directory contains read-only members
| that export information specific to that clk node: clk_rate,
| clk_flags, clk_prepare_count, clk_enable_count & clk_notifier_count.
</pre>

all clocks are availables under ''/sys/kernel/debug/clk'':
<pre class="apf">
# mount -t debugfs none /sys/kernel/debug/
# cat /sys/kernel/debug/clk/clk_summary
</pre>

==Tracers==
* http://lxr.linux.no/#linux+v3.0.22/Documentation/trace/ftrace.txt#L1016

===Function profiler===
<pre class="host">
$ make linux-menuconfig
</pre>

<pre class="config">
Kernel hacking --->
[*] Tracers --->
[*] Kernel Function Tracer
...
[*] Kernel function profiler

This option enables the kernel function profiler. A file is created
in debugfs called function_profile_enabled which defaults to zero.
When a 1 is echoed into this file profiling begins, and when a
zero is entered, profiling stops. A "functions" file is created in
the trace_stats directory; this file shows the list of functions that
have been hit and their counters.
</pre>

==Observing system clocks==

You can "export" and observe some clocks:
* On OPOS6UL/L: signal CLKO1 is available on pad JTAG_TMS (pin 7 of J36) and signal CLKO2 is available on pad JTAG_TDO (pin 13 of J36).

Example on OPOS6UL/L:

Mux CLKO1 and CLKO2 signals on JTAG_TMS and JTAG_DO:
<pre>
# devmem 0x20E0048 32 3
# devmem 0x20E004C 32 3
</pre>

Export ARM clock (divided by 8) on CLKO2:
<pre>
# devmem 0x20C4060 32 0x1EA0001
</pre>

See the reference manual of the OPOS6UL/L for the others clocks "exportable".

==Links==
* http://www-users.cs.umn.edu/~boutcher/kprobes/
* http://tree.celinuxforum.org/CelfPubWiki/PatchArchive

Linux Debug

2019-05-03T08:30:54Z

SebastienSz:

Tips to do debugging under Linux.

==Introduction==

On this page, you will find usefull informations for debugging your Linux kernel/drivers.

==Testing your custom Linux kernel before flashing it==

You can test a linux kernel you've generated without having to reflash your board and destroy your currently working image.
Indeed Linux kernel images can be loaded and started from SDRAM with U-Boot:
<pre class="apf">
BIOS> run download_kernel
MAC: 00:1e:ac:00:00:02
operating at 100M full duplex mode
Using dm9000 device
TFTP from server 192.168.0.104; our IP address is 192.168.0.10
Filename 'apf9328-linux.bin'.
Load address: 0x8000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
########
done
Bytes transferred = 1703940 (1a0004 hex)
BIOS> bootm
## Booting kernel from Legacy Image at 08000000 ...
</pre>

==Changing processor registers from Linux user space with imxregs==

This tool allows you to access i.MX registers from Linux userspace/console. This way you can debug your driver or access i.MX hardware functionnalities directly from Linux console.

In recent releases (>= 3.0) you should find this tool in ''/usr/bin/'' on your board.

===Unlock registers access===
{{Note | On [[APF51]]/[[APF28]]/[[OPOS6UL]] you don't have to explicitly unlock registers in U-Boot to access them under Linux, like explained just above}}

* To use it, you must clear i.MX PAR_1 & PAR_2 registers (registers access rights) '''before''' launching Linux kernel, so in U-Boot type (example here is for APF9328):
<pre class="apf">
BIOS> mw.l 0x00200008 0
BIOS> mw.l 0x00210008 0
</pre>
* on APF27:
<pre class="apf">
BIOS> mw 10000008 0
BIOS> mw 10020008 0
</pre>

If you use it frequently, a small script ''unlock_regs'' has been defined in U-Boot, and you can call it before booting your board:
<pre class="apf">
BIOS> run unlock_regs
BIOS> boot
</pre>

===Usage===
* Then in Linux console/terminal, launch ''imxregs'' like that:
<pre class="apf">
# imxregs REGISTER_NAME (give it the register name as printed in i.MX Ref Manual or just the begining of the name)
</pre>
or
<pre class="apf">
# imxregs (to dump all supported registers)
</pre>

===Examples===
* Show OCR1 registers of each GPIO Port:
<pre class="apf">
# imxregs OCR1
</pre>

* Write 0x00000123 to OCR1_D register:
<pre class="apf">
# imxregs OCR1_D 123
</pre>

==Changing FPGA IP's registers from Linux user space==

See [[FPGA_register|fpgaregs]] tool.

==Using DebugFS==
DebugFS is a in-kernel filesystem, similar to procfs or sysfs, that allows Linux driver to easily communicate debug informations to user space. Full documentation: http://lxr.linux.no/linux+v2.6.32/Documentation/filesystems/debugfs.txt or http://www.linuxtopia.org/online_books/linux_kernel/kernel_configuration/ch09s07.html
===Mounting it===
<pre class="apf">
# mount -t debugfs none /sys/kernel/debug
</pre>
===Showing already allocated GPIOs===
<pre class="apf">
# cat /sys/kernel/debug/gpio
GPIOs 0-31, gpio-0:
gpio-5 (LCD ) in lo
gpio-6 (LCD ) in lo
gpio-7 (LCD ) in lo
gpio-8 (LCD ) in lo
....
</pre>

===Showing clock tree===

<pre class="config">
Device Drivers --->
Common Clock Framework --->
[*] DebugFS representation of clock tree

| Creates a directory hierarchy in debugfs for visualizing the clk
| tree structure. Each directory contains read-only members
| that export information specific to that clk node: clk_rate,
| clk_flags, clk_prepare_count, clk_enable_count & clk_notifier_count.
</pre>

all clocks are availables under ''/sys/kernel/debug/clk'':
<pre class="apf">
# mount -t debugfs none /sys/kernel/debug/
# cat /sys/kernel/debug/clk/clk_summary
</pre>

==Tracers==
* http://lxr.linux.no/#linux+v3.0.22/Documentation/trace/ftrace.txt#L1016

===Function profiler===
<pre class="host">
$ make linux-menuconfig
</pre>

<pre class="config">
Kernel hacking --->
[*] Tracers --->
[*] Kernel Function Tracer
...
[*] Kernel function profiler

This option enables the kernel function profiler. A file is created
in debugfs called function_profile_enabled which defaults to zero.
When a 1 is echoed into this file profiling begins, and when a
zero is entered, profiling stops. A "functions" file is created in
the trace_stats directory; this file shows the list of functions that
have been hit and their counters.
</pre>

==Observing systems clocks==

You can "export" and observe some clocks:
* On OPOS6UL/L: signal CLKO1 is available on pad JTAG_TMS (pin 7 of J36) and signal CLKO2 is available on pad JTAG_TDO (pin 13 of J36).

Example on OPOS6UL/L:

Mux CLKO1 and CLKO2 signals on JTAG_TMS and JTAG_DO:
<pre>
# devmem 0x20E0048 32 3
# devmem 0x20E004C 32 3
</pre>

Export ARM clock (divided by 8) on CLKO2:
<pre>
# devmem 0x20C4060 32 0x1EA0001
</pre>

See the reference manual of the OPOS6UL/L for the others clocks "exportable".

==Links==
* http://www-users.cs.umn.edu/~boutcher/kprobes/
* http://tree.celinuxforum.org/CelfPubWiki/PatchArchive

U-Boot UMS on APF & OPOS

2019-03-25T08:05:29Z

SebastienSz:

EMMC OPOS6UL

2019-03-25T08:04:56Z

SebastienSz: /* Tips */

[[Category: eMMC]]

= OPOS6UL eMMC layout =

By default, the 4GB eMMC on [[OPOS6UL]] module has 4 physical/hardware partitions:

{| border="1" cellpadding="10" cellspacing="0" summary="OPOS6UL eMMC partitions"
|----------------
| style="width:80px;background:orange;" align="center" | Boot0
| style="width:80px;background:orange;" align="center" | Boot1
| style="background:red;" | RPMB
| style="width:500px;background:green;color:white;" align="center" | User Data
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS6UL eMMC partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot name || Size || Comment
|----------------
|boot0 || mmc dev 0 1 || 4MBytes || U-Boot is installed on this partition
|----------------
|boot1 || mmc dev 0 2 || 4MBytes || Not used
|----------------
|rpmb || mmc dev 0 3 || 512KBytes || Not used
|----------------
|User Data || mmc dev 0 0 || remaining space (~3,7GBytes) || Kernel, device tree and rootfs
|----------------
|}

== Boot0 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS6UL eMMC partitions"
|----------------
| style="width:10px;background:white;color:black;" align="center" | .
| style="width:40px;background:orange;color:white;" align="center" | SPL
| style="width:150px;background:orange;color:white;" align="center" | IMG
| style="width:100px;background:white;color:black;" align="center" | ...
| style="width:30px;background:orange;color:white;" align="center" | ENV1
| style="width:150px;background:white;color:black;" align="center" | ...
| style="width:30px;background:orange;color:white;" align="center" | ENV2
| style="width:150px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot0''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot0 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 1 KB (0x400) || Free
|----------------
|0x02 || 1 KB (0x400) || 68 KB || U-Boot SPL (opos6ul-u-boot.spl)
|----------------
|0x8a || 69 KB (0x11400) || 512 KB || U-Boot IMG (opos6ul-u-boot.img)
|----------------
||| || || Free
|----------------
|0x800 (2048) || 1024 KB (0x100000) || 10 KB (0x2800) || U-Boot environment
|----------------
||| || || Free
|----------------
|0xc00 (3072) || 1536 KB (0x180000) || 10 KB (0x2800) || Redundant U-Boot environment
|----------------
||| || || Free
|----------------
|}

== Boot1 partition layout ==
* Not used !

== RPMB partition layout ==
* Not used !

== User Data partition layout ==

There are 3 partitions on the "User Data" physical partition:
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS6UL eMMC partitions"
|----------------
| style="width:50px;background:white;color:black;" align="center" | ...
| style="width:100px;background:green;color:white;" align="center" | Failsafe/Update (primary)
| style="width:600px;background:green;color:white;" align="center" | Default Rootfs (primary)
| style="width:600px;background:green;color:white;" align="center" | Home/Data (primary)
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS6UL eMMC User data partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot device || Linux device || Offset (bytes) || Offset (sectors/blocs) || Size || Comment
|----------------
|MBR || NA || NA || 0 || 0 || 512 bytes (1 block) || Master Boot Record + some spare space ( -> Don't touch it :-) )
|----------------
|Failsafe || mmc 0:1 || /dev/mmcblk0p1 || 1M || 2048 (0x800) || 128MBytes (262144 sectors) || system/rootfs to restore your board in case of problem or setup a safe update mechanism (ext4 formatted)
|----------------
|Rootfs || mmc 0:2 || /dev/mmcblk0p2 || || 264192 (0x40800) || 2GBytes (4194304 sectors) || the default booted rootfs is on this partition (ext4 formatted)
|----------------
|Home/Data || mmc 0:3 || /dev/mmcblk0p3 || || 4458496 (0x440800) || Rest of space: ~1,5GBytes (3176448 sectors) || HOME can be stored on this partition (ext4 formatted)
|----------------
|}

* By default, when flashed from U-Boot, rootfs and boot are only occupying the size of the .ext4 images used during flashing. If you want to increase the rootfs/boot size to all available free space then, after Linux has booted, use the following commands:
<pre class="apf">
# resize2fs /dev/mmcblk0p2 # for Rootfs
</pre>

* Or with ''apf-config'' command:
<pre class="apf">
# apf-config
</pre>
* In menu:
<pre class="config">
| 1 Expand Filesystem(s) OS can then use all eMMC/SD space |
</pre>

Rootfs/Boot will then be extended to all the "Rootfs"/"Boot" eMMC partitions space.

==Tips==
* Commands to partition ''User Data'' from fdisk on Host PC with [[U-Boot UMS on APF & OPOS|U-Boot UMS]]. '''Check /dev/sdc is your OPOS6UL device otherwise you may destroy your PC partition table !!!''':
<pre class=host>
$ sudo fdisk /dev/sdc
n
p
1
2048
+128M
n
p
2
264192
+2G
n
p
3
4458496
7634943
w

$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc1
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc2
$ sudo mkfs.ext4 -O ^64bit,^metadata_csum,uninit_bg /dev/sdc3

</pre>

==Links==
* [http://fr.slideshare.net/linaroorg/intro-to-emmc http://fr.slideshare.net/linaroorg/intro-to-emmc]
* https://fr.wikipedia.org/wiki/Master_boot_record ou http://poloastucien.free.fr/mbr_fat_secteurs_boot_h.html

OPOS6ULDev used with an OPOS6UL NANO

2018-11-07T11:06:04Z

SebastienSz: /* Errata */

[[Category: OPOS6UL_NANO]]

{{Under_Construction}}

==Description==
The Armadeus System's standard development board/baseboard for the [[OPOS6UL]] module, the [[OPOS6ULDev]], can also be used to evaluate [[OPOS6UL_NANO]] SoM. For this you will require a SODIMM adapter... and accept some limitations due to the lack of GPIOs on [[OPOS6UL_NANO]] modules, compared to [[OPOS6UL]]. Consider this usage as temporary, until [[OPOS6UL_NANO]] get the development board it deserves... Don't hesitate to do some lobby to Armadeus Systems hardware team ;-)...

[[Image:OPOS6UL_Dev_with_NANO.jpg]]

==Errata==
* On [[OPOS6UL_Dev]] boards with hardware revision <= 1.2, the USB ports won't be powered unless you do an hardware modification. This modification consist of forcing to 3.3V, the 2 signals USB_OTG1_PWR & USB_OTG2_PWR on U3/AP2152 chip.

==Resources==

* [[Datasheet#OPOS6ULDev | Datasheet and schematics]]
* [http://www.opossom.com/english/products-development_boards-opos6ul_dev.html Product page on Armadeus Systems website]

==Feature list==
{{Note|
* You can't use CAN interfaces of [[OPOS6ULDev]]. CAN buses might be output on LCD connector but will require an additional PHY.
* 2nd Ethernet port is not available.
* You won't see anything on LCD unless you force LCD Backlight pin to Logic 1.
* RPi connector connected buses are different of the ones when using an OPOS6UL SOM.
}}

{| border="0" cellpadding="5" cellspacing="5" summary="Hardware add-ons by functionalities"
|----------------
|- style="background:#f4f4f4; color:black; -moz-border-radius:18px;"
|

===Audio===
* [[S/PDIF]]: audio in/out
* [[ALSA]]

===Video Out===
* [[LCD]]
* [[FrameBuffer]]

===Video In===
*[[Camera interface]]
||
===User Input===
* [[Tslib|Touchscreen]]

===Wired communication===
* [[Uart|UART]]
* [[SPI]]
* [[I2C]]
* [[USB Host]]
* [[USB_OTG]]
* [[USB_Gadget]]
* [[OneWire_GPIO_bus_Master|1-wire]]

||

===Wireless communication===
* [[Wifi|Wi-Fi usage on Linux]]
* [[Bluetooth|Bluetooth usage on Linux]]

===Other===
* [[I.MX6UL_internal_ADC|ADC]]
* [[GPIOlib]]
* [[JTAG]]

|}

==Connectors==
* RPi compatible connector (J3):
{| class="wikitable" border="1" cellpadding="5" summary="RPi compatible connector of OPOS6ULDev with NANO SoM"
|- style="background:#efefef;"
! Linux GPIO or device !! i.M6UL Mux !! wiringPi N° !! RPi name !! Function !! J3 Pin !! J3 Pin !! Function !! RPi name !! wiringPi N° !! i.M6UL Mux !! Linux GPIO or device
|-
| - || || || || '''3.3V''' || style="color:yellow;background:black;" align=center | '''1''' || style="color:yellow;background:black;" align=center | '''2''' || '''5V''' || || || || -
|-
| i2c-1 || UART5_RX_DATA || || SDA1 || I2C data|| style="color:yellow;background:black;" align=center | '''3''' || style="color:yellow;background:black;" align=center | '''4''' || '''5V''' || || || || -
|-
| i2c-1 || UART5_TX_DATA || || SCL1 || I2C clock || style="color:yellow;background:black;" align=center | '''5''' || style="color:yellow;background:black;" align=center | '''6''' || '''GND''' || || || || -
|-
| gpio9 || GPIO1_IO09__GPIO1_IO09 || 7 || GPIO7 || GPIO / AIN9 || style="color:yellow;background:black;" align=center | '''7''' || style="color:yellow;background:black;" align=center | '''8''' || UART Tx || TxD || || UART2_TX_DATA__UART2_DCE_TX || ttymxc1
|-
| || || || || '''GND''' || style="color:yellow;background:black;" align=center | '''9''' || style="color:yellow;background:black;" align=center | '''10''' || UART Rx || RxD || || UART2_RX_DATA__UART2_DCE_RX || ttymxc1
|-
| gpio113 || CSI_MCLK__GPIO4_IO17 || 0 || GPIO0 || GPIO || style="color:yellow;background:black;" align=center | '''11''' || style="color:yellow;background:black;" align=center | '''12''' || GPIO / AIN8 || GPIO1 || || GPIO1_IO08__GPIO1_IO08 || gpio8
|-
| gpio114 || CSI_PIXCLK__GPIO4_IO18 || || GPIO2 || GPIO || style="color:yellow;background:black;" align=center | '''13''' || style="color:yellow;background:black;" align=center | '''14''' || '''GND''' || || || ||
|-
| gpio122 || CSI_DATA05__GPIO4_IO26 || || GPIO3 || GPIO || style="color:yellow;background:black;" align=center | '''15''' || style="color:yellow;background:black;" align=center | '''16''' || GPIO || GPIO4 || 4 || CSI_VSYNC__GPIO4_IO19 || gpio115
|-
| || || || || '''3,3V''' || style="color:yellow;background:black;" align=center | '''17''' || style="color:yellow;background:black;" align=center | '''18''' || GPIO || GPIO5 || 5 || CSI_HSYNC__GPIO4_IO20 || gpio116
|-
| spidev1.x || CSI_DATA02__ECSPI2_MOSI || || || SPI MOSI || style="color:yellow;background:black;" align=center | '''19''' || style="color:yellow;background:black;" align=center | '''20''' || '''GND''' || || || ||
|-
| spidev1.x || CSI_DATA03__ECSPI2_MISO || || || SPI MISO || style="color:yellow;background:black;" align=center | '''21''' || style="color:yellow;background:black;" align=center | '''22''' || GPIO || GPIO6 || 6 || CSI_DATA07__GPIO4_IO28 || gpio124
|-
| spidev1.x || CSI_DATA00__ECSPI2_SCLK || || || SPI CLK || style="color:yellow;background:black;" align=center | '''23''' || style="color:yellow;background:black;" align=center | '''24''' || SPI_CS0 || || || CSI_DATA01__GPIO4_IO22 || spidev1.0
|-
| || || || || '''GND''' || style="color:yellow;background:black;" align=center | '''25''' || style="color:yellow;background:black;" align=center | '''26''' || NC || || || ||
|-
| i2c-0 || UART4_RX_DATA__I2C1_SDA || || || I2C Data || style="color:yellow;background:black;" align=center | '''27''' || style="color:yellow;background:black;" align=center | '''28''' || I2C clock || || || UART4_TX_DATA__I2C1_SCL || i2c-0
|-
| || || || || NC || style="color:yellow;background:black;" align=center | '''29''' || style="color:yellow;background:black;" align=center | '''30''' || '''GND''' || || || ||
|-
| || || || || NC || style="color:yellow;background:black;" align=center | '''31''' || style="color:yellow;background:black;" align=center | '''32''' || NC || || || ||
|-
| || || || || NC || style="color:yellow;background:black;" align=center | '''33''' || style="color:yellow;background:black;" align=center | '''34''' || '''GND''' || || || ||
|-
| || || || || NC || style="color:yellow;background:black;" align=center | '''35''' || style="color:yellow;background:black;" align=center | '''36''' || NC || || || ||
|-
| || || || || NC || style="color:yellow;background:black;" align=center | '''37''' || style="color:yellow;background:black;" align=center | '''38''' || NC || || || ||
|-
| || || || || '''GND''' || style="color:yellow;background:black;" align=center | '''39''' || style="color:yellow;background:black;" align=center | '''40''' || NC || || || ||
|}

==Tested RPi shields/hats==
* [[Dragino Lora/GPS HAT]]... TO BE RETESTED !!!!

==Tips==
===Bootstrap===
* [[Bootstrap]] jumpers are '''not''' connected to [[OPOS6UL_NANO]] and so not useful with this SoM

===U-Boot===
* Use OPOS6ULDev "User" LED in U-Boot scripts:
** ON: <pre class="apf"> BIOS> gpio set 3 </pre>
** OFF: <pre class="apf"> BIOS> gpio clear 3 </pre>

===Linux===
* to activate login in Framebuffer console, please uncomment ''/etc/inittab'' line 35 this way:
<pre class="apf">
# Set up a getty on LCD
tty1::respawn:/sbin/getty 38400 tty1
</pre>

=Links=
* RaspberryPi is a registered trademark of RaspberryPi Foundation.

[[Category:DevelopmentBoards]]
[[Category:Hardware]]

GIT

2018-09-17T12:19:22Z

SebastienSz: /* U-Boot */

[[Category: U-Boot]]
[[Category: BSP]]
[[Category: GIT]]
[[Category: Buildroot]]

We have migrated our Source Code Management tool to GIT scm since some time now (Armadeus software release 3.1 was the last one available under SVN management tool).
This page aims to help you to use our new GIT tool.

==Install GIT==

*Install the following packages if needed:
<pre class="host">
git-core gitk git-gui
</pre>
* If you want to send us patches through email, you will need to install these additional packages:
<pre class="host">
git-email
</pre>
In that case you may need to install/configure ''sendmail'' or ''postfix'' or ''exim'' mail server ([http://www.au.debian.org/releases/stable/s390/ch08s05.html.en]).

==How to use GIT (for everyone)==
===Tutorials===
# [http://git-scm.com/course/svn.html GIT-SVN Crash course ]
# [http://www.kernel.org/pub/software/scm/git/docs/everyday.html Everyday GIT With 20 Commands Or So]
# [http://git-scm.com GIT website]

===Basics===
* Update your repository to the latest version on SF:
<pre class="host>
$ git pull
</pre>

==How to use GIT (Developers)==
*Get the Armadeus GIT/SF repository in the ''armadeus'' directory (will be created):
{{Note| This is the '''Read Only''' method for people wanting to get the latest features. You won't be able to "push" your modifications directly (send us a patch instead).}}
<pre class="host">
$ git clone git://git.code.sf.net/p/armadeus/code armadeus
</pre>

* Before beginning to do your modifications don't forget to update your view:
<pre class="host">
$ git pull
</pre>

*If you have modified some armadeus files and want to revert few files only
<pre class="host">
$ git checkout path_to_file
</pre>

*If you have modified some armadeus files and want to revert all your changes
<pre class="host">
$ git clean -dfx
$ make apf9328_defconfig or make apf27_defconfig
</pre>

*If ''git pull'' fails with an error: "Untracked working tree file '{SOMEFILE}'"
<pre class="host">
$ rm -rf {SOMEFILE}
$ git pull
</pre>

===Providing modifications===
Developers wanting to propose their development should provide us a patch against the latest GIT revision available.
The process to follow is:
* Have a working view, let's call it armadeus
* update your it:
<pre class="host">
$ git pull
</pre>
====Quick way====
* do your modifications
* test them ;-)
* do a patch:
<pre class="host">
$ git diff > my_changes.patch
</pre>
* send it on the armadeus-forum mailing list with your usual mail client
====Clean way====
* create a branch for your work (here ''my_work''):
<pre class="host">
$ git branch
* master
$ git branch my_work
</pre>
* make it the working branch:
<pre class="host">
$ git checkout my_work
Switched to branch 'my_work'
$ git branch
master
* my_work
</pre>
* do a commit for each unitary change
<pre class="host">
$ git add xxx/xxx/xxx
$ git commit -m "blah blah blah"
</pre>
* when work is finished, ask git to generate signed patches (''0001-toto.patch'', ''0002-toto.patch'', one for each commit....):
<pre class="host">
$ git format-patch -M master..my_work -s
</pre>
* then you can send them to the armadeus-forum mailing list (if james.bond@007.com can send mail to this list):
<pre class="host">
$ git send-email --from=james.bond@007.com --to=armadeus-forum@lists.sourceforge.net --smtp-server=smtp.xxx.xx 0001-toto.patch 0002-toto.patch
</pre>
* if your work is accepted, you can rebase your branch and then delete it ?:
TBDJB
http://elinux.org/Git_usage

==How to use GIT (Armadeus integrators)==
* Get the GIT/SF repository in Read/Write mode (for integrators only) in the ''armadeus'' directory (will be created):
<pre class="host">
$ git clone ssh://USER@git.code.sf.net/p/armadeus/code armadeus
</pre>
* Before the first commit, define your global personnal data:
<pre class="host>
$ git config --global user.name "James Bond"
$ git config --global user.email "james.bond@007.com"
</pre>
* If you want colors:
<pre class="host>
$ git config --global color.diff auto
$ git config --global color.status auto
$ git config --global color.branch auto
</pre>
* Update your repository to the latest version on SF:
<pre class="host>
$ git pull
</pre>
* Do your changes and commit to your '''local''' repository (here add ''fileorpath''):
<pre class="host>
$ git add fileorpath
$ git commit -m 'Explain what I changed'
or
$ git commit -a -m 'Explain what I changed' (if you have local modifications (=not versioned files) and wants GIT to ignore them)
</pre>
* Commit someone else work's:
<pre class="host>
$ git commit -m "Message..." --author "FirstName Name <email@address.com>"
</pre>
* Update your repository to the latest version on SF:
<pre class="host>
$ git pull
</pre>
* Push your changes to SF:
<pre class="host>
$ git push
</pre>
* Tag a revision:
<pre class="host>
$ git tag -m "Creates TAG for Armadeus 3.1 release" release-3.1
$ git push --tags origin master
</pre>
===Commit with someone else identity===
<pre class="host>
$ git commit --author "Firstname Lastname <email@address.com>"
</pre>

== Links ==

=== U-Boot ===
For the OPOS6UL, OPOS6UL_Nano and the OPOS6UL_SP boards, Armadeus BSP will download U-Boot from specific [https://sourceforge.net/p/armadeus/u-boot/ci/master/tree/ armadeus uboot git] :
<pre>
git clone git://git.code.sf.net/p/armadeus/u-boot armadeus-u-boot
</pre>

U-Boot Splash Screen

2018-03-15T07:15:08Z

SebastienSz: /* Installation */

=Introduction=
On this page you will learn how to activate LCD support in U-Boot and display a Splash Screen at boot.
{{Note|The following instructions have only be tested on [[OPOS6UL]].}}

=Installation=
* Save your image as BMP file (in Gimp use Run-Length (RLE) encoding, no alpha channel and no color informations (compatibility options). If the RLE option is grayed out, go to Image > Mode and select Indexed...)
* Activate LCD in U-Boot (here ST0700):
<pre class="apf">
BIOS> setenv videomode video=ctfb:x:800,y:480,depth:18,pclk:33033,le:8,ri:4,up:2,lo:4,hs:64,vs:4,sync:0,vmode:0
</pre>

=Test it=
<pre class="apf">
BIOS> tftpboot ${loadaddr} xxx.bmp
BIOS> bmp info ${loadaddr}
Image size : 296 x 72
Bits per pixel: 8
Compression : 0
</pre>

<pre class="apf">
BIOS> bmp display ${loadaddr} 100 50
</pre>

=Deploy it=
* Here we assume that logo is stored in ''/boot'' directory of rootfs eMMC partition as ''logo.bmp'':
<pre class="apf">
BIOS> setenv splashimage 0x80000000
BIOS> setenv splashfile /boot/logo.bmp
BIOS> setenv splashsource mmc_fs
</pre>

=Continuity with Linux Boot Logo=
* If you want Linux to keep your U-Boot Logo during boot process, then some tweaks are needed:
** define CONFIG_SYS_MEM_TOP_HIDE in U-Boot configuration file, here we reserve 2MBytes: <source lang="c">#define CONFIG_SYS_MEM_TOP_HIDE (2 << 20)</source>
* Force framebuffer RAM address in U-Boot LCD driver ([[OPOS6UL]] has 256MBytes (0x10000000) RAM starting at physical 0x80000000):<source lang="diff">@@ -197,8 +197,8 @@
panel.memSize = mode.xres * mode.yres * panel.gdfBytesPP;

/* Allocate framebuffer */
- fb = memalign(ARCH_DMA_MINALIGN,
- roundup(panel.memSize, ARCH_DMA_MINALIGN));
+ fb = (void *)0x8fe00000; /*memalign(ARCH_DMA_MINALIGN,
+ roundup(panel.memSize, ARCH_DMA_MINALIGN));*/
if (!fb) {
printf("MXSFB: Error allocating framebuffer!\n");
return NULL;
</source>

* Tell Linux to not print cursor on Framebuffer and to not use last 2M of RAM: <pre class="apf">BIOS> setenv extrabootargs vt.global_cursor_default=0 mem=248M</pre>

* Force framebuffer RAM address to same value in Linux LCD driver: <source lang="diff">@@ -825,17 +824,18 @@
var->vmode = FB_VMODE_NONINTERLACED;

/* Memory allocation for framebuffer */
+#define FORCED_FB_ADDR 0x8fe00000
fb_size = SZ_2M;
- fb_virt = dma_alloc_wc(dev, PAGE_ALIGN(fb_size), &fb_phys, GFP_KERNEL);
+ fb_virt = ioremap_wc(FORCED_FB_ADDR, fb_size);
if (!fb_virt)
return -ENOMEM;

+ fb_phys = FORCED_FB_ADDR;
fb_info->fix.smem_start = fb_phys;
fb_info->screen_base = fb_virt;
fb_info->screen_size = fb_info->fix.smem_len = fb_size;

- if (mxsfb_restore_mode(host, vmode))
- memset(fb_virt, 0, fb_size);
+ mxsfb_restore_mode(host, vmode);

return 0;
}</source>
* Remove following options of your Linux config file:
<source lang="diff">-CONFIG_FRAMEBUFFER_CONSOLE=y
-CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
-CONFIG_FONTS=y
-CONFIG_FONT_8x8=y
-CONFIG_FONT_8x16=y</source>

* Reflash all that on your board and... That's it ! ;-)

=Links=
* http://www.denx.de/wiki/DULG/UBootSplashScreen

[[Category:Boot Logo]]

EMMC OPOS6UL

2017-09-15T09:49:26Z

SebastienSz: /* Boot0 partition layout */

[[Category: eMMC]]

= OPOS6UL eMMC layout =

By default, the 4GB eMMC on [[OPOS6UL]] module has 4 physical/hardware partitions:

{| border="1" cellpadding="10" cellspacing="0" summary="OPOS6UL eMMC partitions"
|----------------
| style="width:80px;background:orange;" align="center" | Boot0
| style="width:80px;background:orange;" align="center" | Boot1
| style="background:red;" | RPMB
| style="width:500px;background:green;color:white;" align="center" | User Data
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS6UL eMMC partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot name || Size || Comment
|----------------
|boot0 || mmc dev 0 1 || 4MBytes || U-Boot is installed on this partition
|----------------
|boot1 || mmc dev 0 2 || 4MBytes || Not used
|----------------
|rpmb || mmc dev 0 3 || 512KBytes || Not used
|----------------
|User Data || mmc dev 0 0 || remaining space (~3,7GBytes) || Kernel, device tree and rootfs
|----------------
|}

== Boot0 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS6UL eMMC partitions"
|----------------
| style="width:10px;background:white;color:black;" align="center" | .
| style="width:40px;background:orange;color:white;" align="center" | SPL
| style="width:150px;background:orange;color:white;" align="center" | IMG
| style="width:100px;background:white;color:black;" align="center" | ...
| style="width:30px;background:orange;color:white;" align="center" | ENV1
| style="width:150px;background:white;color:black;" align="center" | ...
| style="width:30px;background:orange;color:white;" align="center" | ENV2
| style="width:150px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk0boot0''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot0 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 1 KB (0x400) || Free
|----------------
|0x02 || 1 KB (0x400) || 68 KB || U-Boot SPL (opos6ul-u-boot.spl)
|----------------
|0x8a || 69 KB (0x11400) || 512 KB || U-Boot IMG (opos6ul-u-boot.img)
|----------------
||| || || Free
|----------------
|0x800 (2048) || 1024 KB (0x100000) || 10 KB (0x2800) || U-Boot environment
|----------------
||| || || Free
|----------------
|0xc00 (3072) || 1536 KB (0x180000) || 10 KB (0x2800) || Redundant U-Boot environment
|----------------
||| || || Free
|----------------
|}

== Boot1 partition layout ==
* Not used !

== RPMB partition layout ==
* Not used !

== User Data partition layout ==

There are 3 partitions on the "User Data" physical partition:
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS6UL eMMC partitions"
|----------------
| style="width:50px;background:white;color:black;" align="center" | ...
| style="width:100px;background:green;color:white;" align="center" | Failsafe/Update (primary)
| style="width:600px;background:green;color:white;" align="center" | Default Rootfs (primary)
| style="width:600px;background:green;color:white;" align="center" | Home/Data (primary)
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS6UL eMMC User data partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot device || Linux device || Offset (bytes) || Offset (sectors/blocs) || Size || Comment
|----------------
|MBR || NA || NA || 0 || 0 || 512 bytes (1 block) || Master Boot Record + some spare space ( -> Don't touch it :-) )
|----------------
|Failsafe || mmc 0:1 || /dev/mmcblk0p1 || 1M || 2048 (0x800) || 128MBytes (262144 sectors) || system/rootfs to restore your board in case of problem or setup a safe update mechanism (ext4 formatted)
|----------------
|Rootfs || mmc 0:2 || /dev/mmcblk0p2 || || 264192 (0x40800) || 2GBytes (4194304 sectors) || the default booted rootfs is on this partition (ext4 formatted)
|----------------
|Home/Data || mmc 0:3 || /dev/mmcblk0p3 || || 4458496 (0x440800) || Rest of space: ~1,5GBytes (3176448 sectors) || HOME can be stored on this partition (ext4 formatted)
|----------------
|}

* By default, when flashed from U-Boot, rootfs and boot are only occupying the size of the .ext4 images used during flashing. If you want to increase the rootfs/boot size to all available free space then, after Linux has booted, use the following commands:
<pre class="apf">
# resize2fs /dev/mmcblk0p2 # for Rootfs
</pre>

* Or with ''apf-config'' command:
<pre class="apf">
# apf-config
</pre>
* In menu:
<pre class="config">
| 1 Expand Filesystem(s) OS can then use all eMMC/SD space |
</pre>

Rootfs/Boot will then be extended to all the "Rootfs"/"Boot" eMMC partitions space.

==Tips==
* Commands to partition ''User Data'' from fdisk on Host PC with [[U-Boot UMS on APF & OPOS|U-Boot UMS]]. '''Check /dev/sdc is your OPOS6UL device otherwise you may destroy your PC partition table !!!''':
<pre class=host>
$ sudo fdisk /dev/sdc
n
p
1
2048
+128M
n
p
2
264192
+2G
n
p
3
4458496
7634943
w

$ sudo mkfs.ext4 -O ^64bit /dev/sdc1
$ sudo mkfs.ext4 -O ^64bit /dev/sdc2
$ sudo mkfs.ext4 -O ^64bit /dev/sdc3

</pre>

==Links==
* [http://fr.slideshare.net/linaroorg/intro-to-emmc http://fr.slideshare.net/linaroorg/intro-to-emmc]
* https://fr.wikipedia.org/wiki/Master_boot_record ou http://poloastucien.free.fr/mbr_fat_secteurs_boot_h.html

Network File System configuration

2017-06-20T06:49:46Z

SebastienSz: /* NFS server on your development Host */

==Introduction==

On this page, you will find usefull informations to configure NFS ([[wikipedia:Network_File_System_(protocol)|Network File System]]) on your Host and your Target.

==NFS server on your development Host==

===Installation===
* On Fedora, NFS is part of your distribution so you normally don't need to install it.
* On Ubuntu/Kubuntu:
$ sudo apt-get install nfs-kernel-server
* On OpenSUSE:
$ sudo zypper install yast2-nfs-server
* On Gentoo:
# emerge -av nfs-utils

You can also take a look at the [https://wiki.gentoo.org/wiki/Nfs-utils gentoo wiki]
===Configuration===
====/etc/exports====
* You have to declare the directory where you're going to store the files you want to share accross the network. For that you have to modify the '''/etc/exports''' file with (for example):
<pre class="host">
$ sudo vim /etc/exports
</pre>
and add it (at the end of the file):
<source lang="bash">
...
# Directory for Armadeus:
/local/export 192.168.0.0/255.255.255.0(ro,no_root_squash,sync)
...
</source>
:In that case your Host will authorize all client from the subnet 192.168.*.* to access ''/local/export'' in '''read only''' mode. If you want read/write access from your APF to your exported dir, then replace ''ro'' with ''rw''. 
* In order to use the same folder through TFTP and NFS, using the default U-Boot scripts for example, it recommended to export your /tftpboot folder as well:
<source lang="bash">
...
# Directory for Armadeus:
/local/export 192.168.0.0/255.255.255.0(ro,no_root_squash,sync)
/tftpboot 192.168.0.0/255.255.255.0(ro,no_root_squash,sync)
...
</source>
* If not existing, create your export directory (for example):
<pre class="host">
$ sudo mkdir -p /local/export
$ sudo chown -R $USER:$GROUP /local/export/
</pre>

====/etc/hosts====
* You have to declare your APF/OPOS board in the PC hosts list, to fully support NFS access from U-Boot. For such purpose you have to update the ''/etc/hosts'' file with your preferred editor (as root):
<pre class="host">
$ sudo vim /etc/hosts
</pre>
and add the IP address of your board after the localhost definition for example :
<source lang="bash">
127.0.0.1 localhost
192.168.0.10 apf
...
</source>

====Restart of NFS server====
{| border="1" cellpadding="5" cellspacing="0" summary="Restart of NFS server depending on your distribution"
|- style="background:#efefef;"
! '''On Fedora''' || '''On Ubuntu/Kubuntu/debian''' || '''On OpenSUSE''' || '''On Gentoo'''
|-

|<pre class="host">
# /sbin/service nfs restart
</pre>
Next time you boot, you can check your NFS server status with:
<pre class="host">
# /sbin/service nfs status
</pre>
and if not started then:
<pre class="host">
# /sbin/service nfs start
</pre>

|| <pre class="host">
$ sudo /etc/init.d/nfs-kernel-server restart
</pre>
Next time you boot, you can check your NFS server status with:
''System Settings->System services''
|| <pre class="host">
# /etc/init.d/nfsserver restart
</pre>

|| <pre class="host">
# /etc/init.d/nfs restart
</pre>
|}

==NFS usage on your Armadeus board==

===Mount the NFS partition manually ===
* check if mount point is existing (for example we will take ''/mnt/nfs''):
<pre class="apf">
# ls /mnt
</pre>
* if not existing, create the mount point:
<pre class="apf">
# mkdir -p /mnt/nfs
</pre>
* mount it (for example):
<pre class="apf">
# mount -t nfs 192.168.0.2:/local/export /mnt/nfs
</pre>
Here 192.168.0.2 is your Host IP address and ''/local/export'' the name of your Host directory you want to mount.

{{Note| On some nfs server (for exemple with debian wheezy) there is a warning when we mount nfs partition. But the filesystem is mounted :
<pre class="apf">
# mount /mnt/nfs/
svc: failed to register lockdv1 RPC service (errno 97).
</pre>
}}

===Mount the NFS partition automatically at each boot from FLASH===

* login to your Armadeus board as root
* open the '''/etc/fstab''' file and add this line:
<host-ip>:/<path-to-shared-folder> /mnt/<path-to-mount-folder> nfs hard,intr,rsize=8192,wsize=8192 0 0
example:
192.168.0.2:/local/export /mnt/nfs nfs hard,intr,rsize=8192,wsize=8192 0 0
* check your modification:
<pre class="apf">
# mount /mnt/nfs
</pre>
* reboot your board
<pre class="apf">
# reboot
</pre>
* and enjoy the result
<pre class="apf">
# df
# ls /mnt/nfs
</pre>
When you have a problem, verify that the NFS server is running on the host:
<pre class="host">
$ /etc/init.d/nfs-kernel-server status
</pre>
or
<pre class="host">
$ /sbin/service nfs status
</pre>

===Boot from NFS===
This boot procedure is usefull to test a modified rootfs and/or a linux kernel keeping safe the original flash memory content of your board.
* on your Host, expand generated rootfs image to your NFS export dir (for example if your NFS export dir is ''/tftpboot'' on your Host) and you want to boot on it using the U-Boot script nfsboot:
<pre class=host>
$ make shell_env
$ source armadeus_env.sh
$ sudo mkdir -p /tftpboot/$ARMADEUS_BOARD_NAME-root/boot
$ sudo tar xvf $ARMADEUS_ROOTFS_TAR -C /tftpboot/$ARMADEUS_BOARD_NAME-root
</pre>
* The copy of the Linux kernel to the NFS ''/boot'' folder, makes possible to also download it with NFS when booting the board:
<pre class=host>
$ sudo cp $ARMADEUS_BINARIES/$ARMADEUS_BOARD_NAME-linux.bin /tftpboot/$ARMADEUS_BOARD_NAME-root/boot/
</pre>
* With recent (3.10+) kernels, you also have to copy the Device Tree blobs:
<pre class=host>
$ sudo mkdir -p /tftpboot/$ARMADEUS_BOARD_NAME-root/boot/dtbs
$ sudo cp $ARMADEUS_BINARIES/*.dtb /tftpboot/$ARMADEUS_BOARD_NAME-root/boot/dtbs/
</pre>

* On your board, in U-Boot, check if the ''rootpath'' envt variable is set accordingly:
<pre class="apf">
BIOS> printenv rootpath
</pre>
* If not, then set it (by default U-boot is configured to use the following path ''/tftpboot/apfXXXX-root'') where apfXXXX may be apf9328, apf27, apf28, apf51, apf6:
<pre class="apf">
BIOS> setenv rootpath /tftpboot/${board_name}-root
</pre>
* save it:
<pre class="apf">
BIOS> saveenv
</pre>
* then boot with:
<pre class="apf">
BIOS> run nfsboot
</pre>

===Summary of the required Packages:===
* portmap (Buildroot)
* nfs (busybox)
* nfs support (Linux, activated by default in Armadeus configuration)

==Troubleshooting==

===RPC: Program not registered===
* If ''nfsd'' and ''mountd'' daemons are not running on your Host, then you will get a message like:
<pre class="apf">
mount: RPC: Program not registered
</pre>
* In that case, restart the NFS service on your Host (see [[Network_File_System_configuration#Restart_of_NFS_server|above]]).

===Portmap===
* To successfully mount a NFS drive, ''portmap'' daemon should be running on your APF, if not, system will hang during some minutes when you launch the mount !!
To check if ''portmap'' is running, look at the running processes:
<pre class="apf">
# ps faux
</pre>
If portmap is not listed, then launch it manually:
<pre class="apf">
# /etc/init.d/S13portmap
</pre>

===Connection refused===
* If you get this on your APF when trying to mount:
<pre class="apf">
mount: mounting 192.168.0.2:/local/export on /mnt/nfs/ failed: Connection refused
</pre>
* then your kernel might need some extra options:
<pre class="apf">
mount -o port=2049,nolock,proto=tcp 192.168.0.2:/local/export /mnt/nfs/
</pre>

==NFS Server under Windows==
For those who want to use the NFS service on Windows, a small and FREE NFS server is available [http://www.freedownloadscenter.com/Utilities/Misc__Utilities/nfsAxe.html here].

==Links==
* http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.8.

[[Category:Network]]

Network File System configuration

2017-06-20T06:39:18Z

SebastienSz: /* NFS server on your development Host */ Gentoo

==Introduction==

On this page, you will find usefull informations to configure NFS ([[wikipedia:Network_File_System_(protocol)|Network File System]]) on your Host and your Target.

==NFS server on your development Host==

===Installation===
* On Fedora, NFS is part of your distribution so you normally don't need to install it.
* On Ubuntu/Kubuntu:
$ sudo apt-get install nfs-kernel-server
* On OpenSUSE:
$ sudo zypper install yast2-nfs-server
* On Gentoo:
# emerge -av nfs-utils
===Configuration===
====/etc/exports====
* You have to declare the directory where you're going to store the files you want to share accross the network. For that you have to modify the '''/etc/exports''' file with (for example):
<pre class="host">
$ sudo vim /etc/exports
</pre>
and add it (at the end of the file):
<source lang="bash">
...
# Directory for Armadeus:
/local/export 192.168.0.0/255.255.255.0(ro,no_root_squash,sync)
...
</source>
:In that case your Host will authorize all client from the subnet 192.168.*.* to access ''/local/export'' in '''read only''' mode. If you want read/write access from your APF to your exported dir, then replace ''ro'' with ''rw''. 
* In order to use the same folder through TFTP and NFS, using the default U-Boot scripts for example, it recommended to export your /tftpboot folder as well:
<source lang="bash">
...
# Directory for Armadeus:
/local/export 192.168.0.0/255.255.255.0(ro,no_root_squash,sync)
/tftpboot 192.168.0.0/255.255.255.0(ro,no_root_squash,sync)
...
</source>
* If not existing, create your export directory (for example):
<pre class="host">
$ sudo mkdir -p /local/export
$ sudo chown -R $USER:$GROUP /local/export/
</pre>

====/etc/hosts====
* You have to declare your APF/OPOS board in the PC hosts list, to fully support NFS access from U-Boot. For such purpose you have to update the ''/etc/hosts'' file with your preferred editor (as root):
<pre class="host">
$ sudo vim /etc/hosts
</pre>
and add the IP address of your board after the localhost definition for example :
<source lang="bash">
127.0.0.1 localhost
192.168.0.10 apf
...
</source>

====Restart of NFS server====
{| border="1" cellpadding="5" cellspacing="0" summary="Restart of NFS server depending on your distribution"
|- style="background:#efefef;"
! '''On Fedora''' || '''On Ubuntu/Kubuntu/debian''' || '''On OpenSUSE''' || '''On Gentoo'''
|-

|<pre class="host">
# /sbin/service nfs restart
</pre>
Next time you boot, you can check your NFS server status with:
<pre class="host">
# /sbin/service nfs status
</pre>
and if not started then:
<pre class="host">
# /sbin/service nfs start
</pre>

|| <pre class="host">
$ sudo /etc/init.d/nfs-kernel-server restart
</pre>
Next time you boot, you can check your NFS server status with:
''System Settings->System services''
|| <pre class="host">
# /etc/init.d/nfsserver restart
</pre>

|| <pre class="host">
# /etc/init.d/nfs restart
</pre>
|}

==NFS usage on your Armadeus board==

===Mount the NFS partition manually ===
* check if mount point is existing (for example we will take ''/mnt/nfs''):
<pre class="apf">
# ls /mnt
</pre>
* if not existing, create the mount point:
<pre class="apf">
# mkdir -p /mnt/nfs
</pre>
* mount it (for example):
<pre class="apf">
# mount -t nfs 192.168.0.2:/local/export /mnt/nfs
</pre>
Here 192.168.0.2 is your Host IP address and ''/local/export'' the name of your Host directory you want to mount.

{{Note| On some nfs server (for exemple with debian wheezy) there is a warning when we mount nfs partition. But the filesystem is mounted :
<pre class="apf">
# mount /mnt/nfs/
svc: failed to register lockdv1 RPC service (errno 97).
</pre>
}}

===Mount the NFS partition automatically at each boot from FLASH===

* login to your Armadeus board as root
* open the '''/etc/fstab''' file and add this line:
<host-ip>:/<path-to-shared-folder> /mnt/<path-to-mount-folder> nfs hard,intr,rsize=8192,wsize=8192 0 0
example:
192.168.0.2:/local/export /mnt/nfs nfs hard,intr,rsize=8192,wsize=8192 0 0
* check your modification:
<pre class="apf">
# mount /mnt/nfs
</pre>
* reboot your board
<pre class="apf">
# reboot
</pre>
* and enjoy the result
<pre class="apf">
# df
# ls /mnt/nfs
</pre>
When you have a problem, verify that the NFS server is running on the host:
<pre class="host">
$ /etc/init.d/nfs-kernel-server status
</pre>
or
<pre class="host">
$ /sbin/service nfs status
</pre>

===Boot from NFS===
This boot procedure is usefull to test a modified rootfs and/or a linux kernel keeping safe the original flash memory content of your board.
* on your Host, expand generated rootfs image to your NFS export dir (for example if your NFS export dir is ''/tftpboot'' on your Host) and you want to boot on it using the U-Boot script nfsboot:
<pre class=host>
$ make shell_env
$ source armadeus_env.sh
$ sudo mkdir -p /tftpboot/$ARMADEUS_BOARD_NAME-root/boot
$ sudo tar xvf $ARMADEUS_ROOTFS_TAR -C /tftpboot/$ARMADEUS_BOARD_NAME-root
</pre>
* The copy of the Linux kernel to the NFS ''/boot'' folder, makes possible to also download it with NFS when booting the board:
<pre class=host>
$ sudo cp $ARMADEUS_BINARIES/$ARMADEUS_BOARD_NAME-linux.bin /tftpboot/$ARMADEUS_BOARD_NAME-root/boot/
</pre>
* With recent (3.10+) kernels, you also have to copy the Device Tree blobs:
<pre class=host>
$ sudo mkdir -p /tftpboot/$ARMADEUS_BOARD_NAME-root/boot/dtbs
$ sudo cp $ARMADEUS_BINARIES/*.dtb /tftpboot/$ARMADEUS_BOARD_NAME-root/boot/dtbs/
</pre>

* On your board, in U-Boot, check if the ''rootpath'' envt variable is set accordingly:
<pre class="apf">
BIOS> printenv rootpath
</pre>
* If not, then set it (by default U-boot is configured to use the following path ''/tftpboot/apfXXXX-root'') where apfXXXX may be apf9328, apf27, apf28, apf51, apf6:
<pre class="apf">
BIOS> setenv rootpath /tftpboot/${board_name}-root
</pre>
* save it:
<pre class="apf">
BIOS> saveenv
</pre>
* then boot with:
<pre class="apf">
BIOS> run nfsboot
</pre>

===Summary of the required Packages:===
* portmap (Buildroot)
* nfs (busybox)
* nfs support (Linux, activated by default in Armadeus configuration)

==Troubleshooting==

===RPC: Program not registered===
* If ''nfsd'' and ''mountd'' daemons are not running on your Host, then you will get a message like:
<pre class="apf">
mount: RPC: Program not registered
</pre>
* In that case, restart the NFS service on your Host (see [[Network_File_System_configuration#Restart_of_NFS_server|above]]).

===Portmap===
* To successfully mount a NFS drive, ''portmap'' daemon should be running on your APF, if not, system will hang during some minutes when you launch the mount !!
To check if ''portmap'' is running, look at the running processes:
<pre class="apf">
# ps faux
</pre>
If portmap is not listed, then launch it manually:
<pre class="apf">
# /etc/init.d/S13portmap
</pre>

===Connection refused===
* If you get this on your APF when trying to mount:
<pre class="apf">
mount: mounting 192.168.0.2:/local/export on /mnt/nfs/ failed: Connection refused
</pre>
* then your kernel might need some extra options:
<pre class="apf">
mount -o port=2049,nolock,proto=tcp 192.168.0.2:/local/export /mnt/nfs/
</pre>

==NFS Server under Windows==
For those who want to use the NFS service on Windows, a small and FREE NFS server is available [http://www.freedownloadscenter.com/Utilities/Misc__Utilities/nfsAxe.html here].

==Links==
* http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.8.

[[Category:Network]]

I.MX6UL internal ADC

2017-05-18T09:52:19Z

SebastienSz:

== Introduction ==

This description uses Linux kernel >= 4.8.

i.MX6UL (processor of [[OPOS6UL]] has an integrated 12 bits 16 channels Analog to Digital Converter.

Only channels 0-6 may be used to generic conversions and channels 2, 3, 4, 5 are used for the touchscreen on [[OPOS6ULDev]].

* Channel 1 is available on J21 pin 40 of [[OPOS6ULDev]] (AIN1/YNLR: muxed with touchscreen)
* Channel 2 is available on J21 pin 38 of [[OPOS6ULDev]] (AIN2/YPLL: muxed with touchscreen)
* Channel 3 is available on J21 pin 39 of [[OPOS6ULDev]] (AIN3/XNUR: muxed with touchscreen)
* Channel 4 is available on J21 pin 37 of [[OPOS6ULDev]] (AIN4/XPUL: muxed with touchscreen)
* Channel 8 is available on J3 pin 12 of [[OPOS6ULDev]] (AIN8)
* Channel 9 is available on J3 pin 7 of [[OPOS6ULDev]] (AIN9)

== Driver ==
Driver is by default included if you choose an [[OPOS6UL]] as target.

Otherwise, you can select it that way:

<pre class="host">
[ ] $ make linux-menuconfig
</pre>

<pre class="config">
Device Drivers --->
...
<*> Industrial I/O support --->
...
Analog to digital converters
...
<*> Freescale vf610 ADC driver
</pre>

Then compile the distribution :
<pre class="host">
[ ] $ make linux && make
</pre>

== Use it ==

=== Read channels value ===

<pre class="apf">
# cd /sys/bus/iio/devices/iio:device0
# ls
buffer in_voltage5_raw
current_timestamp_clock in_voltage6_raw
dev in_voltage7_raw
in_conversion_mode in_voltage8_raw
in_temp_input in_voltage9_raw
in_voltage0_raw in_voltage_sampling_frequency
in_voltage10_raw in_voltage_scale
in_voltage11_raw name
in_voltage12_raw of_node
in_voltage13_raw power
in_voltage14_raw sampling_frequency_available
in_voltage15_raw scan_elements
in_voltage1_raw subsystem
in_voltage2_raw trigger
in_voltage3_raw uevent
in_voltage4_raw
</pre>

To read ADC value just «cat» the corresponding input file:
<pre class="apf">
# cat in_voltage1_raw for channel 1 (ADC1_IN1)
4095
</pre>

All values are not converted (ie. directly show the register content). To have the mV value, you must do: value_mV = read_value * 3300/4095

==AsDevices==
* You can access this device from your C/C++ application using ''as_adc_xxx_iio'' functions from [[AsDevices]]
* ''target/demos/oscillo'' is a "good" example to start with...

==Links==
* http://www.at91.com/linux4sam/bin/view/Linux4SAM/IioAdcDriver

[[Category:Linux drivers]]
[[Category:Analog to Digital Converter]]
[[Category:Industrial Input Output]]

LinuxInstall

2017-05-05T11:32:01Z

SebastienSz: /* Get Armadeus software */ Don't use buildroot-update branch anymore

<noinclude>
<big>How-To install Armadeus Software Development Kit (SDK) on Linux systems. This SDK is currently based on the (excellent) [http://buildroot.net/ Buildroot].</big>
</noinclude>

The installation was successfully tested on the following distributions:
* Debian Lenny (5.0), Squeeze (6.0.x), Wheezy (7.2), Jessie (8.0)
* X/KUbuntu Edgy Eft (6.10), Gutsy Gibbon (7.10), Hardy Heron (8.04) & Jaunty Jackalope (9.04)
* Ubuntu Lucid Lynx (10.04) (32 & 64bits), 12.04 LTS (32 & 64bits), 13.10 (32 & 64bits), 14.04 & 15.04.
* Mandriva 2006
* Fedora Core 3 & 4, Fedora 10, Laughlin (14)
* Red Hat Enterprise 5.2
* Gentoo 10.0 (32 & 64 bits)
* SuSE 10.1, OpenSUSE 11.3 - 12.3

'''The installation may fail on:'''
* Ubuntu Karmic Koala (9.10): tslib fails to build

'''APF28 requirements:'''
* APF28 board requires a Linux distribution with (GNU) tar version 1.20 or later to compile the Linux Kernel - Please update or upgrade your Linux distribution.

==Prerequisites for Linux installation==
{{Note|From here we assume that your Linux system has a ''make'' version '''greater or equal to''' 3.81. To check it:
<pre class="host">
$ make -v
GNU Make 3.81
...
</pre>
}}
For armadeus up to 3.4, make should be '''strictly''' make-3.81 (make-3.82 is too strict). A Fedora (14 and 15) -specific solution can be found later; other recent distributions such as mageia1 also have make-3.82, and a generic solution, based on configure&& make&& sudo make install can be used to install make-3.81 (which can be retrieved from http://ftp.gnu.org/gnu/make/make-6.81.tar.gz) in /usr/local/bin (and , according to one's PATH, make 3-81 can be invoked directly or as /usr/local/bin/make).

Depending on your distribution, some additional packages are required:

===Debian/Ubuntu based systems===
[[Ubuntu/Debian installation prerequisites]]

===Mandriva based systems===
[[Mandriva installation prerequisites]]

===RPM-based systems (RedHat, Fedora, CentOS)===
[[RedHat/Fedora installation prerequisites]]

===OpenSuse based systems===
[[OpenSuse installation prerequisites]]

===Gentoo based systems===
[[Gentoo installation prerequisites]]

==Get Armadeus software==
* '''If you are a "careful" user''', then download [https://sourceforge.net/projects/armadeus/files/ the latest stable installation tarball from SourceForge] and detar it wherever you want:
<pre class="host">
$ tar xjvf armadeus-6.0.tar.bz2
</pre>
* '''If you want the latest snapshot or if you have an [[OPOS6UL]]''', the whole development tree can be checked out from our [[GIT]] repository.
<pre class="host">
$ git clone git://git.code.sf.net/p/armadeus/code armadeus
</pre>

* depending on your previous choice, a directory named ''armadeus/'' or ''armadeus-6.0/'' will be created on your hard-disk and will contain all the files you need.

'''Remarks''':
* '''Do not use spaces''' in the directory name !
* '''Do not use a directory path beginning with /usr.''' It is a known bug of Buildroot (until BR2012.11, at 2012-12).
* GIT write/push accesses are limited to the integrators ([[User:JulienB|JulienB]], [[User:SebastienSz|SebastienSz]], [[User:Jorasse|Jorasse]], [[User:FabienM|FabienM]], [[User:SebastienR|SebastienR]])

==Configure SDK/BSP options==
{{Note|If you are new to Armadeus and have troubles compiling armadeus-5.x/armadeus-6.x using the following instructions, you may find some hints here: [[Releases]]}}
*Go to the directory where you put the Armadeus sources:
<pre class="host">
$ cd armadeus/ (or armadeus-6.0/)
</pre>
*The first time you compile an Armadeus distribution you have to specify the target (here the [[APF9328]]) to work with.
<pre class="host">
$ make apf9328_defconfig
</pre>
This command reloads the default configuration to support your target and automatically start a Buildroot's configuration menu.

* Current valid default configurations are:
<pre class="host">
apf9328_defconfig apf27_defconfig pps_defconfig apf28_defconfig apf51_defconfig pps51_defconfig apf6_defconfig apf6legacy_defconfig opos6ul_defconfig
</pre>

For PPS boards, please see [[APF27_PPS]] or [[PPS51]] Wiki pages, as these boards have specific build.

* After some downloads, you will get the Buildroot configuration interface:

{{Note|If you ever made changes during the following steps, at any time, you can reload the default configuration with:
$ make xxx_defconfig (xxx depending on your module name)}}

[[Image:Menuconfig3.png]] 
*If you are not familiar with Buildroot here are some tips:
*# you can move the highlighted item with the "up"/"down" arrow keys
*# with the "left"/"right" arrow keys you can choose between "Select", "Exit" or "Help" buttons
*# "space"/"enter":
*#* selects the currently highlighted item if you are on the "Select" button
*#* go back in previous menu if you are on "Exit" button
*#* show you some Help for current item if you are on "Help" button
*# for more Help about Buildroot commands, select "Help" in the main configuration screen

* Update the memory configuration of your board ('''if needed'''; by default BSP is configured for the minimal memory configuration available on the corresponding board):

:In menu:
:<pre class="config">System configuration ---> [*] Armadeus Device Support ---></pre>

:you can check and change the quantity of RAM available on your Armadeus board:
:[[Image:Build_config_memory.png]]
:For [[APF9328]] the memory can be either 16 or 32MiB (be sure to select 1 RAM chip)
:For [[APF27]] it could be either 64MiB or 128MiB (2 x 64MiB) (in that case be sure to select 2 chips of 64MiB instead of 1 chip of 128MiB).
:For [[APF51]] it could be either 256MiB or 512MiB (2x256MiB) (in such case be sure to select 2 chips of 256MiB instead of 1 chip of 512).
:For [[APF28]] The memory can be 128, 256, 512 or 1024MiB (be sure to select 1 RAM chip).
:For [[APF6]]/[[APF6SP]] The memory can be 512 Mbytes or 1Gbytes with ram chip size of 512Mbytes.
:For [[OPOS6UL]] The memory size is automatically detected so you don't care ;-)

* You may decrease the compilation time by increasing the number of parallel jobs running simultaneously on your system (the result is not guaranteed). This option is located in:
:<pre class="config">Build Options ---> (0) Number of jobs to run simultaneously</pre>
0 means that Buildroot will try to guess automatically how much parallel jobs it can launch.

* During the SDK/BSP build, a lot of software archives are downloaded from Internet. The downloaded files are put by default in the ''armadeus/downloads/'' directory. '''If you have several views or plan to build the toolchain several times''', we advise you to put all the downloaded files in ''/local/downloads'' (for example). This is done by configuring Buildroot to use this directory for all your views. Nevertheless, Buildroot will be downloaded separately for each build environment you set up.
:<pre class="config">Build options ---> (...) Download dir</pre>
:[[Image:Build_config_download.png]]
{{Note|Of course, ''/local/downloads'' should exists on your system and you should have writing rights on it !}}
* In recent Buildroot you can also use the following method:
export BR2_DL_DIR=/local/downloads

* After the build, we advise you to copy all the files in ''downloads/'' / ''/local/downloads'' on a removable medium, in case you want to install the development tools on other systems, without to have to reload all the archives.

* Now, Exit the configuration tool and save your configuration

* You can come back to this configuration menu, by typing (your changes will be kept):
<pre class="host">
make menuconfig
</pre>

==Launch build==
$ make
The toolchain and the full distribution are automatically built. During this procedure, several files are downloaded from Internet. 
'''Please wait for a while.... it takes at least one hour for the first run!''' 
By default, the downloaded files/tarball are put in the ''armadeus/downloads/'' directory. Please see the previous chapter to know how to optimize that if you plan to build several views or want to build faster.

==Enjoy the result==
The generated binary files can be found in the subdirectory ''buildroot/output/images'':
*''apf9328-u-boot.brec'' (only on [[APF9328]]): BRecord image that can be used with the bootstrap, if U-Boot is not installed or not working (see [[BootLoader]] page)
*''xxx-u-boot.bin'': U-Boot image file to be used with U-Boot itself, (see [[BootLoader#Update_U-Boot | updating U-Boot]])
*''xxx-linux.bin'': Linux image to use with U-Boot, (see [[Target_Software_Installation#Linux_kernel_installation | updating Linux]])
*''xxx-rootfs.jffs2'': JFFS2 filesystem/rootfs image to use with U-Boot, (see [[Target_Software_Installation#Linux_rootfs_installation | updating rootfs]])
*''xxx-rootfs.ubi'' (not supported on [[APF9328]]): [[UBIFS|UBI]] filesystem/rootfs image to use with U-Boot, (see [[Target_Software_Installation#Linux_rootfs_installation | updating rootfs]])
*''xxx-rootfs.ext4'': EXT4 filesystem/rootfs image to use with U-Boot, (on [[APF6]] and [[OPOS6UL]])
*''xxx-rootfs.tar'': for an NFS/MMC based rootfs, (see [[Network_Configuration#Boot_from_NFS | Booting from NFS]] & [[MultiMediaCard#Booting_from_MMC.2FSD | Booting from a MMC/SD]])

'''Please note the new naming convention of binary files and directories (since Armadeus 4.0)'''

*''buildroot/output/build'': contains all the build results for target root filesystem, Linux, Busybox and U-Boot...
*''buildroot/output/toolchain/'': cross compilation toolchain's build dir. Binaries usable for cross-compilation are in ''buildroot/output/host/usr/bin''.
*''buildroot/output/target/'': target filessytem before generating rootfs images

More information is available in the [http://buildroot.uclibc.org/buildroot.html Buildroot's documentation]

* Note: Previous versions (3.x) of Armadeus SDK stored the generated binary files at a different place: '' ''buildroot/binaries/XX/'' (where XX was the name of your board).

<noinclude>

You then copy the binary image to your server directory:
<pre class="host">
$ cp buildroot/output/images/* /tftpboot
</pre>

==To keep your local copy/repository up-to-date with the armadeus GIT repository==
<pre class="host">
$ git pull
</pre>
This will update your working directory to the latest release.

Note: if "git pull" fails because a directory or a file already exists, then do:
$ rm -rf <this-directory/file>
$ git pull

You can do a:
$ make apfXX_defconfig
to have the latest features automatically activated.

You have to do a '''make''' to rebuild binary files and then upload the binary files to your target.

Note: if definitively everything goes wrong while it worked before the last update.
You can apply the following procedure (all your modifications in buildroot will be lost):
$ rm -rf buildroot/
$ rm Makefile
$ git pull
$ make apfXX_defconfig
$ make
$ cp buildroot/output/images/* /tftpboot

Enjoy!
</noinclude>

I.MX6UL internal ADC

2017-04-25T14:47:43Z

SebastienSz: /* Introduction */ pin 12 and 9 are on J3

== Introduction ==

This description uses Linux kernel >= 4.8.

i.MX6UL (processor of [[OPOS6UL]] has an integrated 12 bits 16 channels Analog to Digital Converter.

Only channels 0-6 may be used to generic conversions and channels 2, 3, 4, 5 are used for the touchscreen on [[OPOS6ULDev]].

* Channel 1 is available on J21 pin 40 of [[OPOS6ULDev]] (AIN1/YNLR: muxed with touchscreen)
* Channel 2 is available on J21 pin 38 of [[OPOS6ULDev]] (AIN2/YPLL: muxed with touchscreen)
* Channel 3 is available on J21 pin 39 of [[OPOS6ULDev]] (AIN3/XNUR: muxed with touchscreen)
* Channel 4 is available on J21 pin 37 of [[OPOS6ULDev]] (AIN4/XPUL: muxed with touchscreen)
* Channel 8 is available on J3 pin 12 of [[OPOS6ULDev]] (AIN8)
* Channel 9 is available on J3 pin 9 of [[OPOS6ULDev]] (AIN9)

== Driver ==
Driver is by default included if you choose an [[OPOS6UL]] as target.

Otherwise, you can select it that way:

<pre class="host">
[ ] $ make linux-menuconfig
</pre>

<pre class="config">
Device Drivers --->
...
<*> Industrial I/O support --->
...
Analog to digital converters
...
<*> Freescale vf610 ADC driver
</pre>

Then compile the distribution :
<pre class="host">
[ ] $ make linux && make
</pre>

== Use it ==

=== Read channels value ===

<pre class="apf">
# cd /sys/bus/iio/devices/iio:device0
# ls
buffer in_voltage5_raw
current_timestamp_clock in_voltage6_raw
dev in_voltage7_raw
in_conversion_mode in_voltage8_raw
in_temp_input in_voltage9_raw
in_voltage0_raw in_voltage_sampling_frequency
in_voltage10_raw in_voltage_scale
in_voltage11_raw name
in_voltage12_raw of_node
in_voltage13_raw power
in_voltage14_raw sampling_frequency_available
in_voltage15_raw scan_elements
in_voltage1_raw subsystem
in_voltage2_raw trigger
in_voltage3_raw uevent
in_voltage4_raw
</pre>

To read ADC value just «cat» the corresponding input file:
<pre class="apf">
# cat in_voltage1_raw for channel 1 (ADC1_IN1)
4095
</pre>

All values are not converted (ie. directly show the register content). To have the mV value, you must do: value_mV = read_value * 3300/4095

==AsDevices==
* You can access this device from your C/C++ application using ''as_adc_xxx_iio'' functions from [[AsDevices]]
* ''target/demos/oscillo'' is a "good" example to start with...

==Links==
* http://www.at91.com/linux4sam/bin/view/Linux4SAM/IioAdcDriver

[[Category:Linux drivers]]
[[Category:Analog to Digital Converter]]
[[Category:Industrial Input Output]]

MultiMediaCard

2017-04-03T07:31:27Z

SebastienSz: /* Prepare your card */

Instructions to use the MultiMediaCard (MMC/SD) on your Armadeus board

==Introduction==

You can use standard MMC/SD/miniSD/microSD cards with your Armadeus board:
* with an APF9328 DevLight V1, you must have [[MMC/SD | the corresponding connector attached to your development board.]] and use an adaptor for miniSD and microSD,
* with an APF9328 DevLight V2, you can use the onboard microSD connector,
* with an [[APF9328DevFull]], you can use the MMC/SD onboard connector and an adaptor for miniSD and microSD,
* with an [[APF27Dev]], an [[APF28Dev]], an [[APF51Dev]] or an [[APF6Dev]], you can use the onboard microSD connector.

All needed drivers are included in the standard Armadeus Linux image.

==Card insertion==
You should see something like that on the Linux console:
<pre class="apf">
# imx-mmc imx-mmc.0: card inserted
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SD card at address 01b0
mmcblk0: mmc0:01b0 SD512 500224KiB
mmcblk0: p1
</pre>

==Mounting the MMC/SD from Linux==

* Just mount the MMC like you will do on your PC:
<pre class="apf">
# mount /dev/mmcblk0p1 /media/mmc (on all APF *except* APF6)
</pre>
<pre class="apf">
# mount /dev/mmcblk1p1 /media/mmc (on APF6)
</pre>
* Then, you can access the MMC's files from the ''/media/mmc'' directory. Filesystem should be automagically detected.
* Of course if you have several partitions on your MMC/SD they will be named p1/p2/p3...
* If you have problems with vfat code page, [[MultiMediaCard#VFAT_Code_Page|include the missing code page into the kernel]].

==Booting from MMC/SD==
When your rootfs is too big to be put on the APF Flash, you can always use a MMC/SD like a Hard Drive and boot from it (this is possible because standard Armadeus kernel is compiled with the MMC driver built in).

===Prepare your card===
* On your APF board (to avoid to crash your Host HD), create a good partition table on MMC (X is the id of the device, for example 1 on [[APF6]]):
<pre class="apf">
# /sbin/fdisk /dev/mmcblkX

Delete all existing partion with 'd'
Create a primary partion: 'n' then 'p' then '1' then 2x'ENTER'
Change bootflag to Linux: 't' then '83'
Save partition table: 'w'
(To quit without saving: 'm')
</pre>
* If your APF has the ''mkfs'' tools, then format your MMC:
<pre class="apf">
# mkfs.ext4 -O ^64bit /dev/mmcblkXp1
</pre>
* Otherwise, on your PC, format your MMC with Ext2 or Ext3/4 filesystems (booting on FAT is bad :-) ):
<pre class="host">
$ sudo mkfs.ext2 /dev/sdX1 (replace X with your MMC reader drive letter, if your Laptop has an integrated
MMC reader then use mmcblk0p1 instead of sdX1)
</pre>
* If not automatically detected/mounted by your distribution, mount your MMC/SD on your Host filesystem (for example in ''/media/mmc''):
<pre class="host">
$ sudo mkdir -p /media/mmc
$ sudo mount /dev/sdX1 /media/mmc (replace X with your MMC reader drive letter, if your Laptop has an integrated
MMC reader then use mmcblk0p1 instead of sdX1)
</pre>

===Put your rootfs and Linux kernel on the MMC/SD===
* Buildroot should be configured by default to generate a tar-ed rootfs, '''if not''' (no *.tar in ''buildroot/output/images/'') then you can activate it with:
<pre class="host">
$ make menuconfig
</pre>

<pre class="config">
Filesystem images --->
...
[*] tar the root filesystem
Compression method (no compression) --->
() other random options to pass to tar
...
</pre>

<pre class="host">
$ make
</pre>
* Then you have to uncompress the tar-ed rootfs to the MMC/SD card (mounted as ''/media/mmc'' on your PC in the following instructions).
{{Note | The APF51 (with U-Boot version older than 2013.04) and the APF9328 do not load the kernel from the SD card but use the one in Flash instead. }}
<pre class="host">
$ make shell_env
$ source armadeus_env.sh
$ sudo tar xvf $ARMADEUS_ROOTFS_TAR -C /media/mmc
</pre>
* You can also copy the Linux kernel to the rootfs ''/boot'' folder and dtb files for recent kernel supporting it:
<pre class="host">
$ sudo mkdir -p /media/mmc/boot/dtbs
$ sudo cp $ARMADEUS_BINARIES/$ARMADEUS_BOARD_NAME-linux.bin /media/mmc/boot/
$ sudo cp $ARMADEUS_BINARIES/*.dtb /media/mmc/boot/dtbs/
</pre>
* Then umount your MMC/SD from your PC:
<pre class="host">
$ sudo umount /media/mmc
</pre>

===Boot===
* Insert the MMC/SD/microSD in the corresponding slot of your Armadeus board and then under U-Boot do:
<pre class="apf">
BIOS> run mmcboot
</pre>
* if you want to automatically boot from SD at each startup, modify the ''bootcmd'' U-Boot macro:
<pre class="apf">
BIOS> setenv bootcmd run mmcboot
BIOS> saveenv
</pre>
(default bootcmd when you receive your board is ''run jffsboot'' = boot from FLASH)

==Performances==
* [[MMC/SD#Supported_Cards| Show tested cards performances]]

==Troubleshots==
===VFAT Code Page===
If you encounter this message (or something similar):
Unable to load NLS charset cp437
FAT: codepage cp437 not found
you have to add the charset to the supported kernel ones:
$ make linux-menuconfig
<pre class="config">
File systems --->
-*- Native language support --->
<*> Codepage 437 (United States, Canada)
...
<*> NLS ISO 8859-1 (Latin 1; Western European Languages)
...
</pre>

==U-Boot usage==
SD cards can also be used with U-Boot.
The following commands are useful:
* Scan the MMC:
<pre class="apf">
BIOS> mmc rescan
</pre>
* List the MMC content:
<pre class="apf">
BIOS> fatls mmc 0
</pre>
* Load the file xxx.bin in RAM:
<pre class="apf">
BIOS> fatload mmc 0 ${loadaddr} xxx.bin
</pre>

==Links==

* http://en.wikipedia.org/wiki/MultiMedia_Card

[[Category:MassStorage]]

EMMC OPOS6UL

2017-04-03T07:29:46Z

SebastienSz: /* Tips */

= OPOS6UL eMMC layout =

By default, the 4GB eMMC on [[OPOS6UL]] module has 4 physical/hardware partitions:

{| border="1" cellpadding="10" cellspacing="0" summary="OPOS6UL eMMC partitions"
|----------------
| style="width:80px;background:orange;" align="center" | Boot0
| style="width:80px;background:orange;" align="center" | Boot1
| style="background:red;" | RPMB
| style="width:500px;background:green;color:white;" align="center" | User Data
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS6UL eMMC partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot name || Size || Comment
|----------------
|boot0 || mmc dev 0 1 || 4MBytes || U-Boot is installed on this partition
|----------------
|boot1 || mmc dev 0 2 || 4MBytes || Not used
|----------------
|rpmb || mmc dev 0 3 || 512KBytes || Not used
|----------------
|User Data || mmc dev 0 0 || remaining space (~3,7GBytes) || Kernel, device tree and rootfs
|----------------
|}

== Boot0 partition layout ==
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS6UL eMMC partitions"
|----------------
| style="width:10px;background:white;color:black;" align="center" | .
| style="width:40px;background:orange;color:white;" align="center" | SPL
| style="width:150px;background:orange;color:white;" align="center" | IMG
| style="width:100px;background:white;color:black;" align="center" | ...
| style="width:30px;background:orange;color:white;" align="center" | ENV1
| style="width:150px;background:white;color:black;" align="center" | ...
| style="width:30px;background:orange;color:white;" align="center" | ENV2
| style="width:150px;background:white;color:black;" align="center" | ...
|}

* Linux device: ''/dev/mmcblk2boot0''
{| border="1" cellpadding="5" cellspacing="0" summary="Boot0 partition detail"
|- style="background:#efefef;" align="center"
! Offset (blocks) || Offset (bytes) || Size (bytes) || Comment
|----------------
|0 || 0 || 1 KB (0x400) || Free
|----------------
|0x02 || 1 KB (0x400) || 68 KB || U-Boot SPL (apf6-u-boot.spl)
|----------------
|0x8a || 69 KB (0x11400) || 512 KB || U-Boot IMG (apf6-u-boot.img)
|----------------
||| || || Free
|----------------
|0x800 (2048) || 1024 KB (0x100000) || 10 KB (0x2800) || U-Boot environment
|----------------
||| || || Free
|----------------
|0xc00 (3072) || 1536 KB (0x180000) || 10 KB (0x2800) || Redundant U-Boot environment
|----------------
||| || || Free
|----------------
|}

== Boot1 partition layout ==
* Not used !

== RPMB partition layout ==
* Not used !

== User Data partition layout ==

There are 3 partitions on the "User Data" physical partition:
{| border="1" cellpadding="10" cellspacing="0" summary="OPOS6UL eMMC partitions"
|----------------
| style="width:50px;background:white;color:black;" align="center" | ...
| style="width:100px;background:green;color:white;" align="center" | Failsafe/Update (primary)
| style="width:600px;background:green;color:white;" align="center" | Default Rootfs (primary)
| style="width:600px;background:green;color:white;" align="center" | Home/Data (primary)
|}

{| border="1" cellpadding="5" cellspacing="0" summary="OPOS6UL eMMC User data partitions details"
|- style="background:#efefef;" align="center"
!Name || U-Boot device || Linux device || Offset (bytes) || Offset (sectors/blocs) || Size || Comment
|----------------
|MBR || NA || NA || 0 || 0 || 512 bytes (1 block) || Master Boot Record + some spare space ( -> Don't touch it :-) )
|----------------
|Failsafe || mmc 0:1 || /dev/mmcblk0p1 || 1M || 2048 (0x800) || 128MBytes (262144 sectors) || system/rootfs to restore your board in case of problem or setup a safe update mechanism (ext4 formatted)
|----------------
|Rootfs || mmc 0:2 || /dev/mmcblk0p2 || || 264192 (0x40800) || 2GBytes (4194304 sectors) || the default booted rootfs is on this partition (ext4 formatted)
|----------------
|Home/Data || mmc 0:3 || /dev/mmcblk0p3 || || 4458496 (0x440800) || Rest of space: ~1,5GBytes (3176448 sectors) || HOME can be stored on this partition (ext4 formatted)
|----------------
|}

* By default, when flashed from U-Boot, rootfs and boot are only occupying the size of the .ext4 images used during flashing. If you want to increase the rootfs/boot size to all available free space then, after Linux has booted, use the following commands:
<pre class="apf">
# resize2fs /dev/mmcblk0p2 # for Rootfs
</pre>

* Or with ''apf-config'' command:
<pre class="apf">
# apf-config
</pre>
* In menu:
<pre class="config">
| 1 Expand Filesystem(s) OS can then use all eMMC/SD space |
</pre>

Rootfs/Boot will then be extended to all the "Rootfs"/"Boot" eMMC partitions space.

==Tips==
* Commands to partition ''User Data'' from fdisk on Host PC with [[U-Boot UMS on APF & OPOS|U-Boot UMS]]. '''Check /dev/sdc is your OPOS6UL device otherwise you may destroy your PC partition table !!!''':
<pre class=host>
$ sudo fdisk /dev/sdc
n
p
1
2048
+128M
n
p
2
264192
+2G
n
p
3
4458496
7634943
w

$ sudo mkfs.ext4 -O ^64bit /dev/sdc1
$ sudo mkfs.ext4 -O ^64bit /dev/sdc2
$ sudo mkfs.ext4 -O ^64bit /dev/sdc3

</pre>

==Links==
* [http://fr.slideshare.net/linaroorg/intro-to-emmc http://fr.slideshare.net/linaroorg/intro-to-emmc]
* https://fr.wikipedia.org/wiki/Master_boot_record ou http://poloastucien.free.fr/mbr_fat_secteurs_boot_h.html

U-Boot UMS on APF & OPOS

2017-04-03T07:28:36Z

SebastienSz:

Infos for U-Boot's USB Mass Storage gadget mode (or UMS) usage on [[APF6]] and [[OPOS6UL]]. This mode allows you to flash rootfs bigger than the available module RAM, ex: > 200MBytes on the [[OPOS6UL]]. Indeed ''run update_rootfs'' script uses RAM to store images while uploading from TFTP, which can be short for big rootfs.

* First, keep your USB debug cable and connect a second USB cable on [[APF6_Dev]] or [[OPOS6ULDev]]'s OTG port.
* Under U-Boot type:
<pre class="apf">
BIOS> ums 0 mmc 0
UMS: disk start sector: 0x0, count: 0x760000
|
</pre>
* On your Host computer you should see the [[eMMC]] partition like a standard USB key.
<pre class="host">
$ dmesg | tail
[...]
[26828.348088] sd 13:0:0:0: [sdc] Mode Sense: 0f 00 00 00
[26828.348395] sd 13:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[26828.354177] sdc: sdc1 sdc2
[26828.356782] sd 13:0:0:0: [sdc] Attached SCSI disk
</pre>

Here the device is ''/dev/sdc'' and all partitions have been automounted by the Host:

<pre class="host">
[26830.002168] EXT4-fs (sdc1): mounting ext2 file system using the ext4 subsystem
[26830.054358] EXT4-fs (sdc2): mounting ext2 file system using the ext4 subsystem
[26830.078638] EXT4-fs (sdc2): warning: mounting unchecked fs, running e2fsck is recommended
[26830.114382] EXT4-fs (sdc2): mounted filesystem without journal. Opts: (null)
[26830.135564] EXT4-fs (sdc1): warning: mounting unchecked fs, running e2fsck is recommended
[26830.268450] EXT4-fs (sdc1): mounted filesystem without journal. Opts: (null)
</pre>
{{Warning| Before doing the following procedure, be sure that your device name is correct. '''You can erase all your Host datas if you do it wrong !!!'''}}
* The rootfs is under the sdc2 and is named "rootfs". In debian/ubuntu it might be auto-mounted under ''/media/usb1'', if no other USB key is present on system and if you activated auto-mounting.
<pre class="host">
$ ls /media/usb1/
bin boot dev etc home init lib lib32 linuxrc lost+found media mnt opt proc root run sbin sys tmp usr var
</pre>

* To flash entire rootfs, first erase all files on this partition:
<pre class="host">
$ sudo umount /media/usb1 (if partition is auto-mounted)
$ sudo mkfs.ext4 -L ROOTFS -O ^64bit /dev/sdc2
</pre>

* Then, you have 2 methods to update your rootfs:
{| class="wikitable"
|-
! tar method !! dd method
|-
|
* Then mount it under an arbitrary directory:
<pre class="host">
$ sudo mkdir /tmp/rootfs
$ sudo mount /dev/sdc2 /tmp/rootfs
</pre>

* Untar the archive generated by your bsp (in ''buildroot/output/images/'')
<pre class="host">
$ make shell_env
$ . armadeus_env.sh
$ sudo tar -xvf $ARMADEUS_ROOTFS_TAR -C /tmp/rootfs
</pre>
* then umount the filesystem:
<pre class="host">
$ sudo umount /tmp/rootfs/
$ sync
</pre>
||
* One alternative way to untaring is to use ''dd'':
<pre class="host">
$ sudo dd if=/tftpboot/xxx-rootfs.ext4 of=/dev/sdc2
</pre>
(replace xxx with the name of your module)
|}

* Once finished, you can kill the U-Boot's USB gadget process with a Ctrl-C:
<pre class="apf">
BIOS> ums 0 mmc 0
UMS: disk start sector: 0x0, count: 0x760000
CTRL+C - Operation aborted
BIOS>
</pre>

[[Category:U-Boot]]

Bluetooth

2017-02-13T16:44:50Z

SebastienSz: /* Custom Bring up (each hardware may have a different init sequence) */

Bluetooth

2017-02-13T16:44:33Z

SebastienSz: /* Custom Bring up (each hardware may have a different init sequence) */

Qt

2016-10-26T12:01:45Z

SebastienSz: /* Launching you Qt application */

= Introduction =

This page will summarize the process to build, install and use Qt on your APF board. It will focus on Qt5.

= Compiling Qt =

Select Qt5 from the BuildRoot menuconfig
<pre class="config">
Target packages --->
Graphic libraries and applications (graphic/text) --->
[*] Qt5 --->
</pre>

Under the Qt5 submenu, you can select the features and Qt modules you need. The most important ones are described below.

Select the following option to accept de free license of Qt. If you don't select the option here, the building of Qt will stop and ask you to accept it.
<pre class="config">
[*] Approve free license
</pre>

To dispaly UI you will need the gui module and the widgets module. You need to select de graphical platform you want. For example linuxfb for the framebuffer. You can also set the default graphical platform here instead of passing to your Qt application with the -platform parameter.
<pre class="config">
[*] gui module
[*] widgets module
-*- linuxfb support
...
(linuxfb) Default graphical platform
</pre>

To support the touchscreen, enable Tslib support.
<pre class="config">
[*] Enable Tslib support
</pre>

You can then select the Qt modules you need. For example:

* '''qt5xmlpatterns''' if you need to read or write XML files.
* '''qt5serialport''' if you need to use UARTs from you Qt application

= Compiling your Qt application =

Once Qt is compiled, you need to compile and deploy your application. You can do this from Qt Creator. You need to create a "Kit" for your APF board. See the Qt Creator [http://doc.qt.io/qtcreator/index.html documentation] You will need the following informations:
* The debugger path is '''buildroot/output/host/usr/bin/arm-linux-gnueabihf-gdb'''
* The compiler path is '''buildroot/output/host/usr/bin/arm-linux-gnueabihf-g++'''
* The qmake paths is '''buildroot/output/host/usr/bin/qmake'''

= Launching your Qt application =
If you want to use the tslib you need to active it first
<pre class="apf">
export QT_QPA_FB_TSLIB=1 # for the framebuffer backend
export QT_QPA_EGLFS_TSLIB=1 # for openGL backend
</pre>

and specify the input device

<pre class="apf">
export TSLIB_TSDEVICE=/dev/input/event0
</pre>

<pre class="apf">
# ./flightinfo -plaform linuxfb
</pre>

The Qt Embedded [http://doc.qt.io/qt-5.6/embedded-linux.html documentation] describes all the options you can pass to the Qt framework.