F&S Support Forum

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

I have created a fs-installscript.bbappend:

(Code, 17 lines)


I placed my_install.txt with my custom changes to…

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…

Hello,

the mipi-dsi unit waits for the DRM-chain to successfully load. There is a MIPI2LVDS converter on the PicoCore module, which gets initialized pretty late in the logs:
(Code, 5 lines)


As you can see, the converter gets initialized correctly and…

Thanks for the reply.
I was hoping this wouldn’t interfere with I2C, but looks like I’ll have to take it into account after all.

Hi F&S support team,

we have ordered a evaluation kit PicoCore™MX8MM Linux (V14I). Currently the display is not running and I´m wondering why.
I missed to check the installed state when I received it, because I build a custom rootfs with Buildroot and…

Hi Saturnion ,

In general, I would recommend removing the PS (Push-Up Enable) and PE (Push/Pull Enable) flags for I2C.
Provided you have external pull-ups on the I2C lines, it should be fine to use only ODE (open-drain enable) for I2C.

The BBDSI has a CAN…

Hello everyone, I’m working with a PicoCore BBDSI rev. 1.4 module based on the i.MX8ULP M33 core and have run into an issue I hope someone can help me with.

For LPI2C1 I’ve been using two pins on J11 — SPI_B_MOSI and SPI_B_MISO (PTA4 and PTA5) —…

Hello,

The U-Boot is placed in a fixed RAW partition, so Nboot does not care about the partition table.
The fsim6ul U-Boot however needs the partition table to load Linux so you will have to make sure that GPT support is available here.

We have not tested…

Does the fsimx6ul NBoot expect a MBR partition table or is it also capable of handling GPT?

Hello,

yes, for fsimx6ul the U-boot is expected the User Partition. This has historical reasons, because early eMMC chips had smaller boot partitions, which may not be sufficient for future Bootloader sizes. It is more complicated to update the partition…