Posts by fs-support_KM

Hello,

the GPIO Reference Card is now updated.

Thank you for the update on your situation.

Your F&S Support Team

Hello,

you can check the GPIO Reference Card for the PicoCOMA9X. The pin J1-63 is shared between the pads LCD_HSYNC and LCD_B2.

Otherwise, it seems that there currently is an error in the Reference Card for the signals LCD_B3 to LCD_B6 that the gpio numbers are off about one IO.

The correct mapping should be as followed, but I will check that again:

J1-63: LCD_HSYNC (GPIO3_IO26 -> gpio# 90) and LCD_B2 (GPIO3_IO01 -> gpio# 65)

J1-54: LCD_B3 (GPIO3_IO02 -> gpio# 66)

J1-55: LCD_B4 (GPIO3_IO03 -> gpio# 67)

J1-56: LCD_B5 (GPIO3_IO04 -> gpio# 68)

J1-57: LCD_B6 (GPIO3_IO05 -> gpio# 69)

If your tests are successful with the updated mapping, please reply shortly.

Your F&S Support Team

Hello,

a software reset will cause the CPU to pull the WDOG_B of the external PMIC. The PMIC will then pull the POR for the CPU, so the reset cause in perspective of the CPU will always be POR.

A way to distinguish a "real" POR from a SW-Reset would be to access the RESETSRC (0x29) register of the PMIC. You can look up the register in the datasheet for the BD71847 under chapter "3.3.10 Reset Source Indicators". If you need that value in the RootFS, you could read that register in UBoot and set the reset_cause for bdinfo to that value under board/F+S/common/fs_fdt_common.c.

After Power-On:

After SW-Reset (UBoot or Linux):

A HW-Reset can't be distinguished from a Power-On though. I hope the information helps.

Your F&S Support Team

Hello,

the second case [2] with the reboot at shutdown / poweroff is related to the post. Thank you for referencing it.

The commit for the ATF is pushed on our Github and will be in the upcoming release: Fix poweroff command and ON/OFF button in imx_system_off() · FSEmbedded/atf-fus@2465c76 · GitHub

The first case [1] is currently unknown and I can't reproduce it. I am trying it with the release fsimx8mp-2023.09. Do you use a baseboard of your own or are you using a starterkit of ours? If you are using a starterkit the revision of it would be good to know too.

Your F&S Support Team

Hello,

can you check whether the crc32 binary is present? You can do this with the command "which crc32".

We had a release version, where we included a crc-check in our bootloader-images, but didn't throw an error if the crc32 binary was not present.

This might be the issue in your Ubuntu host machine. The crc32 command should be in the "libarchive-zip-perl" package under Ubuntu.

Your F&S Support Team

Hello,

please communicate in English for this Forum, as others might need a solution for the same issue.

Translated question:

Quote

I would like to boot my Yocto image from SD-Card.

There is no bootloader image in the SD-Card. Do I need a U-Boot specific to the board and should the U-Boot image be in a partition of the SD-Card?

Our boards usually boot from the onboard eMMC, so the U-Boot image for the early startup is in the Bootpartition from the eMMC.

If you want to boot your Yocto root filesystem and/or the Linux kernel with Device-Tree from the SD-Card, you can do so by entering some commands in U-Boot:

If you just want to boot your Yocto rootFS, you can leave out the commands run .kernel_mmc and run .fdt_mmc.

If you want to set the boot medium to the eMMC again, you can do this with the same commands, just with setenv mmcdev 0.

The U-Boot expects on the boot medium a FAT partition, which includes Device-Trees and the kernel image, and an ext4 partition, which contains the root filesystem. It may be that you need to edit the environments in the U-Boot, if your SD-Card has another partiton layout.

I hope I could clarify the boot process for you.

Your F&S Support Team

Hello,

to investigate why the touchscreen is not responding, we will need some additional information:

• Boardvariant (V3I / V4)
• The release you are currently using (e.g. fsimx6ul-B2022.04)
• Type of the display (RGB / LVDS)

Your F&S Support Team

Hello,

the i.MX 93 does not support hardware acceleration for OpenGL. The Pixel Pipeline (PXP) only provides hardware acceleration for basic 2D conversion, e.g. scaling, color space conversion, rotation and composite alpha blending and color key.

These functions are provided for the G2D driver and will be called for the usage of Wayland/Weston.

Your F&S Support Team

Hello,

it seems you did receive special NBoot+UBoot for a DRAM with 4GB. In our official release these changes are not present yet as they complicate the standard memory layout significantly. This is also the cause why the UBoot currently sees 0 Bytes for the DRAM.

Please contact us for this case directly through our support E-Mail address.

Your F&S Support Team

Hello,

in the following thread you will find the fix for the yocto-download script on older Fedora Machines:

Fix for repo tool on older F&S Development Machines - Linux and Applications - (fs-net.de)

Your F&S Support Team

Hello,

in the following thread you will find the fix for the yocto-download script on older Fedora Machines:

Fix for repo tool on older F&S Development Machines - Linux and Applications - (fs-net.de)

Your F&S Support Team

Error Report

Our yocto-download script uses the repo tool to get all the yocto-layers and sources necessary for a successful build.

The repo tool recently changed, so that our yocto-download script breaks on older Fedora Machines with the following error:

Solution

The fix for this issue is fairly simple. The default python version must be set to python3. This can be done with the following command:

python3 should already be present, but you can check this with ll /usr/bin/python*. In case it is not present, it can be installed with the package manager via sudo dnf install python3.

Your F&S Support Team

Hello,

could you try to use the version 7 of VirtualBox? In our "ReadMe.txt" for the virtual machine with Fedora, there is a note that there are problems with audio on version 6. The error message also refers to an audio entry, so the upgrade to version 7 might already fix it.

Your F&S Support Team

Hello,

there is a new release v1.1.6 for the Recovery Tool: Recovery Tool - Linux and Applications - (fs-net.de)

This version also includes the firmware files from the release fsimx8mp-Y2023.09.

The announcement moved to the general "Linux and Applications" board.

Your F&S Support Team

Recovery Tool for i.MX8 series (v1.1.6)

Description:

The Recovery Tool for the i.MX8 series provides a simple way to restore the firmware on the board up to a working U-Boot. The tool and a description, how to use it, can be accessed in the download section in "My F&S" under "BOARD_NAME/Linux/Recovery Tool/". The tool comes packed with the current latest NBoot and U-Boot from the release of the architechture. Firmware from another release can be applied by removing the NBoot and U-Boot from the folder and exchanging them with the ones from the target release.

ATTENTION: You should never have multiple NBoot and U-Boot files in the folder of the Recovery Tool!

Changes since v1.1.5;

• Fix parsing of new NBoot
• Add form and handling for boardrevision
• Add checkbox to keep CMD for UUU open
• Add simple and expert mode

Supported boards:

• armStoneMX8MP, efusMX8MP, PicoCoreMX8MP, PicoCoreMX8MPr2
• PicoCoreMX8MM-DDR3L, PicoCoreMX8MM-LPDDR4, PicoCoreMX8MMr2-LPDDR4

Releases for included firmware binaries:

• fsimx8mm-Y2023.10
• fsimx8mp-Y2023.09

Your F&S Support Team

Hello,

Currently the tool is only available for Windows. We have a Linux port planned, but it will take some time until a prototype is ready for usage.

If Windows is completely out of question and you need a solution now, you can send an E-Mail with the required release and the serial number of your board to our support address. The context, that a recovery tool is needed, should be also clear in the mail.

Your F&S Support Team

It is possible to shut down the ethernet link with "ifconfig eth0 down". That way, the PHY should power down and disable further communication.

You might want to disable the automatic link up + dhcp for wired connections, as Yocto adds that policy under /lib/systemd/network/80-wired.network. If you do this, you will need to run the commands "ifconfig eth0 up" and "udhcpc -i eth0" manually.

I just tested that the genphy_suspend function from the ethernet PHY driver in the kernel gets called, when "ifconfig eth0 down" is issued. This way the generic power down over the mdio communication can be done.

Your F&S Support Team

Hello,

please see i.MX8M-Plus Recovery Tool.

We are now providing a recovery tool for the fsimx8mp releases. The binaries in the tool are from release fsimx8mp-Y2023.03, but as long as the NBoot and UBoot fit together, you can exchange the UBoot binary to the release you want to recover to.

The recovery tool is using the UUU tool, so if you know what you do, you can also edit the write-emmc-uboot.auto to write every image. The standard auto script flashes everything up to the UBoot, so the Linux kernel, Device-Tree and RootFS are still missing. But in UBoot, you should better use the install.scr/update.scr script with an USB-Stick.

Your F&S Support Team

For the fsimx8mp releases the new NBoot currently does not support a user interface to recover from a deleted or corrupted UBoot.

For that, we now provide a recovery tool to reflash the NBoot as well as the UBoot. The tool is ready to download as a zip archive on "My F&S" under

<Your-Board-Name> -> Linux -> Recovery Tool

In the same directory there exists a PDF document, which explains the steps necessary to recover the UBoot.

Your F&S Support Team

For our current releases fsimx8mm-B2021.06.1 and fsimx8mm-Y2021.04.2, the USB-C OTG device is not able to detect an USB host device.

This patch enables the detection for revisions of the PCoreBBDSI equal or greater than 1.30. The check for an USB host device is handled in revision 1.30 through polling and in revision 1.40 through an available interrupt.

To apply the patch navigate in the terminal to the Linux source code and issue the following command:

patch -p1 < PATH/TO/PATCH/0001-Enable-USBC-OTG-function-for-fsimx8mm.patch

To avoid wrong behaviour for the USB-C OTG device please ensure that the define CONFIG_PICOCOREBBDSI_BOARD_REVISION in your device-tree contains the correct value for your PCoreBBDSI:

#define CONFIG_PICOCOREBBDSI_BOARD_REVISION 140 // Example for PCoreBBDSI revision 1.40

Your F&S Support Team