Posts by bkeohane

Dear F&S,

I came across a mismatch between the document efusA9_Hardware_eng and efusA9-GPIO-ReferenceCard_eng.

The pin 59 of the J1 connector is stated as "Output" pin by efusA9_Hardware_eng:

while the GPIO reference card says, it is an "IO" configurable pin (same for the efusA9R2 GPIO reference card):

Which statement is true? I'd love to know shortly since I am in the process of building a schematic and I want to use that pin as an input pin.

Cheers.

Good morning,

as Yocto ends its LTS for Kirkstone this April, I was asking myself, if F&S plans to make an official release for supporting Scarthgap with the i.MX6, and eFusA9R2, respectively.

Best,

Bjørn

Hello,

thanks for your response!

There was an issue in my schematic: The +5V only go into the IN line of the MIC2026, but not on the OUTA line (as it is in the case of your SINTF board).

I fixed it by connecting the 5V to the OUTA line. It works now.

Thanks!

Issue solved.

Hello,

I can successfully use my custom install script with the SINTF base board for eFus. However, in my target device, I use a custom PCB, where the Hub Controller of SINTF board (USB2514) is not placed. The USB P/N lines are directly connected to pins 214 and 216 of the goldfinger adapter:

Inside UBoot on SINTF board, the hub and my USB flash (SanDisk Cruzer Blade) are deteced as follows:

On my custom PCB, it is not recognized by UBoot:

I reckon, there is a way to tell UBoot to look for my USB Stick and not for the Hub? Do you have any hint, where to check and patch the UBoot build in Yocto?

Thanks!

Ok, I found, that the mkimage command is done in fs-installscript.bb.

I have created a fs-installscript.bbappend:

I placed my_install.txt with my custom changes to /home/developer/fsimx6-Y2024.04/build/yocto-fus/sources/meta-fus/recipes-config/images/files.

it works now. Issue closed (or maybe there is a more elegant solution?).

Thanks.

Hi there,

I would like to customize the install.scr provided by F&S, in my special case, I want to install a bitmap to UserDef partition and setup the display settings in UBoot.

Doing this manually worked great. However, placing the commands in install.scr will fail the installation.

I did some research and found, the install.scr needs to be compiled to an image script with a certain CRC in its header. I did this using mkimage:

So I have generated a new install.scr from a install.cmd, which includes my changes. I can check, that the script is compiled correctly

But when placing it onto a USB drive alongside with my files to install, it fails:

I have attached the install.cmd file to this post. I can see, that the header in my new install.scr shows a lot of NULs (when opened in VS code or Notepad++). I also made sure, the install.cmd is written in Unix-style (using dos2unix command).

Any suggestions on how to get a custom install.scr running?

Thanks!

Hi,

yes, I use this layer. Thanks for looking it up, It seems to be okay then.

Qt Support also mentioned to me, that their meta-qt6 layer supports Kirkstone.

Case closed.

Best, Bjørn

Hello,

I have installed Qt 6.8 on the Feodra 36 VM with Y04.2024 release and I have built a core-image-base image with my Qt application, using my commercial Qt license and the Qt 6.8 installation.

However, I researched, that it is better to use Yocto 5 "Scarthgap" with Qt 6.8.

Do you see any major concerns in using Yocto 4 "Kirkstone" with Qt 6.8? The image runs and my application is running without errors.

I have checked the shared object file of Qt6Core on my iMX6 after image installation using the command:

One line caught my eye:

I see, the build and compilation were successful, however, the line "Incompatible processor" made me a bit nervous

Full output of the strings command is in the attached txt file.

Cheers.

Quote from fs-support_PG

Hello,

could you try using the PLL2 for your LVDS display?

HDMI also uses PLL5 for pixel clock generation. SO driving two different resolutions from a singe clock might me problematic.

Please try these changes and play around with different resolutions.

Code

1. /*
2. * Depending on the needed pixel clock speed, the LVDS clock source must be
3. * selected accordingly. If pixelclock is between 38.7 MHz and 113 MHz,
4. * PLL2_PFD0 is sufficient. Otherwise PLL5 has to be used. If you have two
5. * LVDS displays with different clock requirements, set one to PLL2_PFD0 and the
6. * other to PLL5. If you have activated the displays in U-Boot already and want
7. * to keep these settings in Linux, de-activate all four lines.
8. */
9. #define CONFIG_EFUSA9_LVDS0_CLK IMX6QDL_CLK_PLL2_PFD0_352M
10. //#define CONFIG_EFUSA9_LVDS0_CLK IMX6QDL_CLK_PLL5_VIDEO_DIV
11. #define CONFIG_EFUSA9_LVDS1_CLK IMX6QDL_CLK_PLL2_PFD0_352M
12. //#define CONFIG_EFUSA9_LVDS1_CLK IMX6QDL_CLK_PLL5_VIDEO_DIV

Display More

If this still does not work, I can again offer an online meeting next week. Please contact F&S support via mail for this.

Your F&S Support Team

Display More

Thank you, Sir, this worked great. Issue closed.

Hi,

I have achieved to successfully run two displays (LVDS + HDMI) with correct color encoding using Wayland Weston, and running an instance of Weston in clone-mode:

Here, the content of fb0 is successfully cloned to fb2.

It works, but I now experience severe lag on the LVDS screen and the touch inputs are also delayed.

Additionally, I had to tune down the HDMI resolution to 900x600 to get it to work (a higher resolution causes the false color rendering on the LVDS).

Since using DRM/KMS is not an option, what can be done to get rid of the lag and running a duplication to HDMI smoothly?

The eFusA9R2 has a GPU and 2 IPUs, so I assume, it should be capable of such things.

Thanks!

Hi,

I indeed used the wrong chokes. The chokes Murata DLP11S need to be used, as stated in your HW documentation.
After removing them, the HDMI works.

Here is a good overview about using chokes in high speed differential layouts: consumer-signal

I will rework my layout.

Thanks. Topic closed.

I use I2C_C for the SGTL5000 audio codec, and my layout also used I2C_C for the HDMI EDID (SDA,SLC), may this cause the issue of a nun.functional HMDI output? Is there a pinmux for this?

Yes, you are correct, I use an eFusa9r2. I accidently posted into armstone, sorry.
I will have a look, thanks for your suggestions!

Hello,

I have drawn and layoutet a HDMI connector onto a custom board, and I took the SINTF hardware documentation as template.

On SINTF, HDMI is working, but not on my custom board. I took another look at the documentation and realized, there exists a HDMI_DDCCEC_AUX_P pin (J24 plug). This one is not shown on J6 plug. Do we need it?

I have attached the layout and schematic of my custom PCB. Pin 154 is connected to GND while 156 is the HDMI_DDCCEC_AUX_N signal.

Thanks!

I adjusted my device tree as you porposed, but I am afraid, it did not work.

In my console output shared before, I noticed:

After some investigation, I come to the conclusion, that clone mode is not stable on this hardware with fbdev.

Would you also relate to this?

For LVDS, I use

For HDMI, it is

See attached file for full DTS settings. We use a custom display.

Hello,

Quote

However, I thing it is important to unblank the HDMI display before starting weston with the clone mode.

Is this done correctly?

Yes. Before starting any weston instance, I unblanked fb2. The application on LVDS remains blurry rendered with color shifts.

I have attached the console output, when starting Weston in two instances in clone-mode and starting my GUI app.

Thanks!

Hi,

thanks for your answer. It works.

However, I experience false colors of the application rendered on the LVDS screen, as soon as I unblank fb2/ clone to the second weston instance on HDMI.

The colors on HDMI are correct, whatsoever. Feel free to check the image I attached, to see what happens.

Any suggestions? I feel, the switch to the open source driver that supports DRM is doable but may be an overload, especially since the HDMI feature shall be very simple.

May any Kernel display driver configs (e.g. IPU settings) or device tree configs help (hardware mirroring)?

Thanks!

Hi,

thanks for your answer.

Quote

Another would be to try to use the same framebuffer for both outputs. This however would require the displays to support the same resolution.

Would this be an option?

Our LVDS display is 1280x800, and I set the HDMI resolution to 1280x720 in the device tree. If there are a few pixels missing on the bottom, it is ok. So yes, this would be a quick solution.

Is it also done in the device tree? May it will work, if the HDMI monitor requires hotplugging?

I tried to make the HDMI use the same IPU as LVDS:

But it does not work. I assume, it is because of different display timings.

Hence, I am asking myself, how to achive a simple copy of the LVDS output to the HDMI output.

Thank you!