Forum - Recent Threads

Maaxboard IMX8 Mini with raspberry pi camera v3

fa0888 — Sat, 20 Sep 2025 02:05:30 GMT

Hello,

I would like a confirmation if the AES-MC-SBC-IMX8MINI-G will work with the https://www.raspberrypi.com/products/camera-module-3/ via MIPI-CS-2

Raspberry PI camera v3 is using the Sony IMX708.

https://github.com/raspberrypi/linux/blob/rpi-6.6.y/arch/arm/boot/dts/overlays/imx708-overlay.dts

https://github.com/raspberrypi/linux/blob/rpi-6.6.y/arch/arm/boot/dts/overlays/imx708.dtsi

Can i just set in file uEnv.txt ?

dtoverlay_camera=imx708

Thank you.

Please recommend a Linux SBC with Industrial stability while it is made in ABC?

HKPhysicist — Sun, 03 Nov 2024 15:49:31 GMT

Hello Engineers,

I have even tried the BeaglePlay SBC which is out-sourced to China SeeedStudio`s production line in Vietnam. It's TI WL card dies after 6 months of purchase and after 70 days of stability test while it did nothing. 😡
I personally also like Raspberry Pi4 because it is stable while running under a chip fan. Also, it is made in Wales, UK! Quality is the top in the industry! 😍 However, it is not within the industrial electronic requirement (-40C/-20C to 85C).
So could any expert introduce a Linux SBC (working as a border router with LTE dialup) with at least 2GB RAM, 16GB eMMC, average video without graphical acceleration, a wireless lan, an Ethernet, and the last but not the least, not made in China. The cost of electronic made in China is actually very high!!! 😡
Is Snapdrogon 410 board within the industrial stability standard?

Thanks for your opinions.

🤓

MaaXBoard RT operating Temperature verification

P_Schoenke — Wed, 28 Feb 2024 15:48:09 GMT

Hello,

The product brief for the MaaXBoard RT shows:

P22_800_Maaxboard_RT_Product_Brief_al-v2.pdf (avnet.com)

But the hardware user guide shows:

MaaXBoard+RT+User+Guide+(v1.0).pdf (avnet.com)

Any feedback or input is welcomed and appreciated!

Thanks!

Paul

LattePanda3 Delta NVMe SSD installation with Windows 11

robogary — Sun, 16 Jul 2023 15:46:13 GMT

Background:

Late 2022 , I participated in a Road Test for the LattePanda 3 Delta. It is a wonderful SBC.

The onboard Arduino was used to read multiple thermistors and create a enclosure fan control system.

/products/roadtest/rv/roadtest_reviews/1650/lattepanda3_delta

During the Road Test I had filled up the available LattePanda3 Delta storage with screen captures and videos of the tests, short term using Google drive as shared data storage.

I vowed to upgrade the LattePanda3 Delta storage, and here it is .............

using a shopping cart from a subsequent Project 14 winner award, an SSD was ordered

https://www.newark.com/micron/mtfdkba256tfk-1bc1aabyy/ssd-pcie-nvme-nand-256gb/dp/67AJ1367?ost=67aj1367

MTFDKBA256TFK-1BC1AABYY

SSD, M.2 PCIe SSD, M.2 2280, PCIe, NVMe, 256 GB, NAND, AES 256-bit

I not sure what got me to order the NVMe, everywhere I referenced used a SSD SATA, and that was my original intention,

The NVMe SSD install experience:

Several You Tube videos show SATA SSD installs on LattePanda3 Delta, but I didnt see any with Windows 11 or the SSD in the NVMe slot.

The videos all were informative and shared one critical message: Once installed the SSD had to be activated using disc manager.

I stumbled around the Windows 11 disc manager a couple times before finding the way to activate the SSD.

It is really easy...........once you figure it out.

Here are photos and screen shots I hope saves someone time , or gives them confidence, to add an SSD to the LattePanda3 Delta:

This is the LattePanda3 Delta with power off, i.e. the power supply unplugged.

I have an extra terminal board mounted under the standoffs for wiring to the onboard Arduino.

A. Flip the LattePanda 3 over. Note the upper PCie expansion slot for SSD SATA & the lower for NVMe.

I had previously left the expansion boards screws installed underneath.

I removed the holding screw, The NVMe board fit easily into the connector, and put the screw back in.

The slot connectors are keyed, you cant install it in the incorrect slot.

b. flip the LattePanda3 over on its feet and power up.

c. Once the LattePanda3 is booted back up, go to the Windows search at the bottom of the screen, and type in disc manager

the screen is shown in the photo - Notice bottom window shows a disk 0 and disk 1 , with disk 1 being unallocated.

Disk 1 is the new SSD.

It does not show up if using file manager under MyPC.

D. All you have to do now is allocate the SSD and define it. This was surprisingly easy, defaulted suggestions were used.

Start by selecting disc 1 by selecting it with the mouse and left click, then right click. I selected the "simple" wizard.

The screen shots show the rest of the process.

Now the LattePanda3 Delta has a drive D.

YAY !

Learning C++20 - Progress with Standard Template Language

Jan Cumps — Tue, 22 Feb 2022 17:04:20 GMT

Follow up on:
Try out C++20 Preview: set up a development environment
Sorting in the C++20 release

When I wrote the posts above, a good year ago, I started to learn the latest evolutions in C++.
I didn't want to just poke around, but do a thorough training. I purchased this e-book: C++ Standard library (also available in print). By Rainer Grimm.
I've used the STL extensively in my job - I was C++ developer in the 2nd half of the 90's. That allows me to use this book to focus on the concepts new to C++20.
I'm trying to temper my enthousism a little, because I am a Rainer Grimm and STL fanboy, but: this is a great book.

As the title indicates, it doesn't focus on new language constructs but on the template library. While doing that, Rainer manages to sneak in a lot of the new language changes.
(I think) that the majority of changes are in the STL and in concurrent programming, so there is significant overlap by default.

For my learning journey, I've set up Eclipse and the latest GNU toolchain for Windows (if you check my other posts: also for Ubuntu, Pi, ..., but I digress).
Then I walked through all chapters, and tried all examples:

image: Eclipse ready to debug a C++ STL example. To avoid that I have to create a project for each example, I created a project for the whole book. When I'm finished testing an example, I exclude it from build and start with the next one.

Having the examples in a debugger, and step through what's happening, is my preferred learning method for software.
I like to bite into the code. Drill into the statements, view variables, view changes.
That way, they stick into my memory forever. If I read - even with full focus - I tend to forget after a while. Stepping through seems to fix the processes in my memory.

The STL book is well organised. There's a natural flow in three ways:

from overall usable to more specific and niche
from easy to difficult
from known traditional concepts to revolutionary changes

The two first, I think, are self explaining. The third subject is less intuitive. But that's where new concepts can be learned that aren't C++ specific, but show where software development is evolving.
I'm name-dropping one: lambda functions. But there's a number of concepts that help to make executable logic object-savvy.

Last kudo is to the C++ governance team, for taking care that the evolution doesn't increase the footprint. Most changes extend the way you can code your intents, without generating a bigger or slower execution. And some of them deal with fat that was added in previous language increments.

image: customer action photo

If you're interested in evolving together with the C++ language: Rainer Grimm's blog Modern C++ contains everything of my book, and more.
Well written, updated constantly, challenging the brain...

wilc3000 with sama5d3 xplained

raje232ec — Fri, 25 Jun 2021 09:29:23 GMT

iam trying to connect wilc3000 using spi interface with sama5d3 xplained .iam following the wilc300 device porting guide ,i got .ko file is generated when i try to insmod the .ko file in sama5d3 in dmesg it is showing probed sucess.

[ 152.940940] WILC_SPI spi1.0: failed to get Reset GPIO, try default

[ 152.940991] wifi_pm : 1

[ 152.941032] WILC_SPI spi1.0: failed to get Reset GPIO, try default

[ 152.971002] WILC_SPI spi1.0: WILC SPI probe success

my dts file

spi1: spi@f8008000 {

cs-gpios = <&pioC 25 0>;

pinctrl-0= <&pinctrl_spi1_default>;

status = "okay";

wilc_spi@0 {

compatible = "microchip,wilc3000", "atmel,wilc_spi";

spi-max-frequency = <6000000>;

reg = <0>;

status = "okay";

};

i changed the reset ,irq and chip enable pins in wilc-wlan.h file with gpio pins and connect to the corresponding pins.

please help

Attachments:

sama5d3 xplained with wilc3000

raje232ec — Fri, 25 Jun 2021 09:27:38 GMT

[ 152.940940] WILC_SPI spi1.0: failed to get Reset GPIO, try default

[ 152.940991] wifi_pm : 1

[ 152.941032] WILC_SPI spi1.0: failed to get Reset GPIO, try default

[ 152.971002] WILC_SPI spi1.0: WILC SPI probe success

my dts file

spi1: spi@f8008000 {

cs-gpios = <&pioC 25 0>;

pinctrl-0= <&pinctrl_spi1_default>;

status = "okay";

wilc_spi@0 {

compatible = "microchip,wilc3000", "atmel,wilc_spi";

spi-max-frequency = <6000000>;

reg = <0>;

status = "okay";

};

i changed the reset ,irq and chip enable pins in wilc-wlan.h file with gpio pins and connect to the corresponding pins.

please help

Attachments:

i wanted to use 5 in mipi diaply in max board isuggest the driver files

rndsamtech — Tue, 08 Jun 2021 07:37:23 GMT

i wanted to use 5 inch mipi diaplay in max board suggest the driver files

is there a way to clock the maaxboard at a lower frequency .the board is hot

gonewtinwind — Wed, 19 May 2021 17:50:27 GMT

HI Joshu and all,

is there a way to clock the maaxboard at a lower frequency?

We are running into some heat issues and was wondering what the options are?

Thank you very much

is there a way to change maaxboard Frequency to lower ? how to? the board is hot!

gonewtinwind — Wed, 19 May 2021 14:50:22 GMT

Hi Joshua

is there a way to clock the maaxboard at a lower freq.

We are running into some heat issues and was wondering what the options are?

Thank you very much

how to write a system service to auto startup chromium on wayland with non-root user?

gonewtinwind — Wed, 12 May 2021 13:19:14 GMT

Hi Joshua & all

I use the below system service can auto startup chromium on maaxboard wayland with root user, but it's not safe with root user, so I need to startup with non-root user.

I tried to modify it somewhere, but not work.

any help?

my service ,you can see it's root user with --no-sandbox option :

/etc/systemd/system/chromium.service

----

Description=launch chromium

[Service]

User=root

Environment=DISPLAY=:0

Environment=XDG_RUNTIME_DIR="/run/user/0"

Type=oneshot

ExecStart=/bin/sleep 15

ExecStart=/usr/bin/chromium --no-sandbox --disable-infobars --user-data-dir=/tmp/chromium --gpu-no-context-lost --enable-gpu-rasterization --start-fullscreen --kiosk --no-first-run --incognito http://localhost:3300/rpi.html > /dev/null 2>&1 &

[Install]

WantedBy=multi-user.target

ref:can not auto startup chromium(chromium-ozone-wayland)

Maaxboard sn65dsi83 mipi dsi to lvds Converter Issue

akoc — Thu, 06 May 2021 07:23:17 GMT

Hello all,

I have a 10.25 "1280 * 480 resolution screen. I want to run this screen with maaxboard, but I was not successful.

I connect the screen with sn65dsi83 which is a mipi dsi to lvds converter, I tried the kernel configurations with dcss and lcdif, I could only print the test pattern in the test mode on screen when i use sn65dsi83 with maaxboard via i2c communication. I could not get any image in the normal mode .

I'm trying to stand up with maaxboard-dcss-mipi.dtb;

When I use this dtb file, the system gets up properly, I see that the sn65dsi83 installation has been done properly, but I can't get any image. You can see the output of dmesg in the "maaxboard-dcss-mipi-dmesg.txt" file.

I'm trying to stand up with maaxboard-lcdif-mipi.dts;

When I use this dtb file, the system loading is interrupted and the root file cannot jump to the system.

You can see the output of dmesg in the "maaxboard-lcdif-mipi-dmesg.txt" file.

Device : Maaxboard imx8mq / https://www.avnet.com/wps/portal/us/products/new-product-introductions/npi/avnet-maaxboard/

Yocto version : https://github.com/Avnet/meta-maaxboard/tree/zeus

sn65dsi83 driver : https://github.com/digi-embedded/linux/tree/v5.4/dey-3.0%2Fmaint/drivers/gpu/drm/bridge/sn65dsi83

Screen : 10.25 '' 1280x480

I have a hard time understanding where I am having problems. I would be glad if you could help. Thanks

Files

1) maaxboard-dcss-mipi-dmesg.txt

2) maaxboard-lcdif-mipi-dmesg.txt

3) maaxboard-dcss-mipi.dts

4) maaxboard-lcdif-mipi.dts

5) maaxboard-dsi-common.dtsi

6) TestPatern.jpeg

Message was edited by: ahmet koc

Attachments:

community.element14.com/.../maaxboard_2D00_dcss_2D00_mipi_2D00_dmesg.txt.zip
community.element14.com/.../maaxboard_2D00_lcdif_2D00_mipi_2D00_dmesg.txt.zip

community.element14.com/.../maaxboard_2D00_lcdif_2D00_mipi.txt.zip
community.element14.com/.../maaxboard_2D00_dcss_2D00_mipi.txt.zip
community.element14.com/.../maaxboard_2D00_dsi_2D00_common.txt.zip

yocto zeus branch toolchains compile optee_example code ,ModuleNotFoundError: No module named 'Crypto'

gonewtinwind — Tue, 04 May 2021 18:34:52 GMT

Hi all,

yocto zeus branch toolchains compile optee_example code ,ModuleNotFoundError: No module named 'Crypto'

(maaxbaord sumo branch worked well).

I use yocto toolchains to cross compile optee_example code,

error happened:

from Crypto.Signature import PKCS1_v1_5

ModuleNotFoundError: No module named 'Crypto'

but I find in toolchain folder, the Crypto folder is there:

./sysroots/aarch64-poky-linux/usr/lib/python3.7/site-packages/Crypto

It seems the compiler can not find it ?

I have added :

IMAGE_INSTALL_append +=" python3-pycryptodome " in local.conf

any help?

About 2 year ago,I posted a similar question #3441 but that was in yocto bitbake process in early, could not generate the yocto image.
Today I play another board, I can build the image and the toolchain, the new issue is the toolchain compiler can not find the 'Crypto'

Thank you.

error:

aarch64-poky-linux-gcc -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/opt/fsl-imx-xwayland/5.4-zeus/sysroots/aarch64-poky-linux -o optee_example_aes main.o -lteec -L/opt/fsl-imx-xwayland/5.4-zeus/sysroots/aarch64-poky-linux/usr//lib

make[1]: Leaving directory '/opt/oe/iw/iw-5.4.24/optee_examples/aes/host'

make -C ta CROSS_COMPILE="aarch64-poky-linux-" LDFLAGS=""

make[1]: Entering directory '/opt/oe/iw/iw-5.4.24/optee_examples/aes/ta'

CC aes_ta.o

CC user_ta_header.o

CPP ta.lds

LD 5dbac793-f574-4871-8ad3-04331ec17f24.elf

OBJDUMP 5dbac793-f574-4871-8ad3-04331ec17f24.dmp

OBJCOPY 5dbac793-f574-4871-8ad3-04331ec17f24.stripped.elf

SIGN 5dbac793-f574-4871-8ad3-04331ec17f24.ta

Traceback (most recent call last):

File "/usr/local/optee/sysroots/aarch64-poky-linux/usr/include/optee/export-user_ta_arm64//scripts/sign.py", line 78, in

main()

File "/usr/local/optee/sysroots/aarch64-poky-linux/usr/include/optee/export-user_ta_arm64//scripts/sign.py", line 31, in main

from Crypto.Signature import PKCS1_v1_5

ModuleNotFoundError: No module named 'Crypto'

/usr/local/optee/sysroots/aarch64-poky-linux/usr/include/optee/export-user_ta_arm64/mk/link.mk:60: recipe for target '5dbac793-f574-4871-8ad3-04331ec17f24.ta' failed

make[1]: *** [5dbac793-f574-4871-8ad3-04331ec17f24.ta] Error 1

make[1]: Leaving directory '/opt/oe/iw/iw-5.4.24/optee_examples/aes/ta'

Makefile:9: recipe for target 'all' failed

make: *** [all] Error 2

How to change dtsi(eg:maaxboard-extended-gpio.dtsi) to make M41T93 spi rtc work in maaxboard yocto zeus branch?

gonewtinwind — Tue, 20 Apr 2021 13:21:37 GMT

Hi Josh,

I use maaxboard board (not mini, not nano)

the M41T93 spi rtc works well in kernel 4.14(yocto sumo branch) , I showed here before: Enable the SPI port on MaaxBoard?

but

I need to add M41T93 spi rtc chip in yocto zeus branch(kernel 5.4),but I find the maaxboard-extended-gpio.dtsi is different with maaxboard-nano-extended-gpio.dtsi.

the maaxboard-extended-gpio.dtsi file still keeps the gpio for old settings , I thought the zeus did not support maaxboard now, so I need to modify it similar to maaxboard-nano-extended-gpio.dtsi.

so I change the ecspi part as the below patch file(see attached file,001-spi-real-time-M41T93.patch, I change kernel config,I can find the /dev/rtc0, I removed snvs_rtc),but unfortunately the spi rtc still not work!

How to change the dtsi in kerenel 5.4? I think maaxboard nano work well, I just follow it to modify maaxboard .dtsi file similiarly . the spi rtc should work.

Thank you very much.

my full patch file:

diff -Naur ori/arch/arm64/boot/dts/freescale/imx8mq.dtsi patches/arch/arm64/boot/dts/freescale/imx8mq.dtsi

--- ori/arch/arm64/boot/dts/freescale/imx8mq.dtsi 2021-04-15 12:55:28.039009295 -0400

+++ patches/arch/arm64/boot/dts/freescale/imx8mq.dtsi 2021-04-15 16:33:48.243133485 -0400

@@ -591,15 +591,6 @@

compatible = "fsl,sec-v4.0-mon", "syscon", "simple-mfd";

reg = <0x30370000 0x10000>;

- snvs_rtc: snvs-rtc-lp{

- compatible = "fsl,sec-v4.0-mon-rtc-lp";

- regmap =<&snvs>;

- offset = <0x34>;

- interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>,

- <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>;

- clocks = <&clk IMX8MQ_CLK_SNVS_ROOT>;

- clock-names = "snvs-rtc";

- };

snvs_pwrkey: snvs-powerkey {

compatible = "fsl,sec-v4.0-pwrkey";

@@ -832,7 +823,7 @@

clocks = <&clk IMX8MQ_CLK_ECSPI1_ROOT>,

<&clk IMX8MQ_CLK_ECSPI1_ROOT>;

clock-names = "ipg", "per";

- status = "disabled";

+ status = "enabled";

};

ecspi2: spi@30830000 {

diff -Naur ori/arch/arm64/boot/dts/freescale/maaxboard-extended-gpio.dtsi patches/arch/arm64/boot/dts/freescale/maaxboard-extended-gpio.dtsi

--- ori/arch/arm64/boot/dts/freescale/maaxboard-extended-gpio.dtsi 2021-04-08 14:58:09.820015901 -0400

+++ patches/arch/arm64/boot/dts/freescale/maaxboard-extended-gpio.dtsi 2021-04-19 13:57:18.993139208 -0400

@@ -37,10 +37,15 @@

pinctrl_ecspi1: ecspi1grp {

fsl,pins = <

- MX8MQ_IOMUXC_ECSPI1_SS0_GPIO5_IO9 0x16

- MX8MQ_IOMUXC_ECSPI1_MOSI_ECSPI1_MOSI 0x16

- MX8MQ_IOMUXC_ECSPI1_MISO_ECSPI1_MISO 0x16

- MX8MQ_IOMUXC_ECSPI1_SCLK_ECSPI1_SCLK 0x1816

+ MX8MQ_IOMUXC_ECSPI1_MOSI_ECSPI1_MOSI 0x82

+ MX8MQ_IOMUXC_ECSPI1_MISO_ECSPI1_MISO 0x82

+ MX8MQ_IOMUXC_ECSPI1_SCLK_ECSPI1_SCLK 0x82

+ >;

+ };

+ pinctrl_ecspi1_cs: ecspi1cs {

+ fsl,pins = <

+ MX8MQ_IOMUXC_ECSPI1_SS0_GPIO5_IO9 0x40000

};

@@ -90,10 +95,19 @@

&ecspi1{

fsl,spi-num-chipselects = < 1 >;

- cs-gpios = <&gpio5 13 0 > ;

+ cs-gpios = <&gpio5 9 0 > ;

pinctrl-names = "default";

- pinctrl-0 = <&pinctrl_ecspi1 >;

+ pinctrl-0 = <&pinctrl_ecspi1 &pinctrl_ecspi1_cs>;

status = "okay";

+ #address-cells=<1>;

+ #size-cells=<0>;

+ rtc@0x00{

+ #address-cellss=<1>;

+ #size-cells=<1>;

+ compatible = "rtc-m41t93";

+ spi-max-frequency = <5000000>;

+ reg = <0>;

+ };

};

&i2c2 {

73,1 Bot

Attachments:

community.element14.com/.../001_2D00_spi_2D00_real_2D00_time_2D00_M41T93.txt.zip

bitbake -c menuconfig linux-imx NOT work on ubuntu 18.04 for maaxboard yocto zeus branch

gonewtinwind — Mon, 12 Apr 2021 17:32:20 GMT

hi all

I need to config the kernel but

bitbake -c menuconfig linux-imx NOT work on ubuntu 18.04 for maaxboard yocto zeus branch

I can not find the solution on Internet.

any help?

error:

bitbake -c menuconfig linux-imx

Loading cache: 100% |#####################################################################################################################################################################################################################| Time: 0:00:03

Loaded 4675 entries from dependency cache.

NOTE: Resolving any missing task queue dependencies

Build Configuration:

BB_VERSION = "1.44.0"

BUILD_SYS = "x86_64-linux"

NATIVELSBSTRING = "ubuntu-18.04"

TARGET_SYS = "aarch64-poky-linux"

MACHINE = "maaxboard-ddr4-2g-sdcard"

DISTRO = "fsl-imx-wayland-lite"

DISTRO_VERSION = "5.4-zeus"

TUNE_FEATURES = "aarch64 cortexa53 crc crypto"

TARGET_FPU = ""

Embest is ceasing operation?

gonewtinwind — Tue, 06 Apr 2021 14:11:24 GMT

Hi Josh,

My company wants to order more maaxboard ?

but the people(embest) we connect to before told us the Embest is shutdown

who (where) is the CM factory we can connect to ?

Thank you.

the email from embest:

-------

Hi XXX,

Embest is going to shutdown by this month end.

And both eMMC version and standard version is not in the stock.

After Embest shutdown, some products will be transferred to our CM factory to continue the supply. And business part can deal with our recommended distributor.

Now the distributor has 45pcs of standard MaaXBoard in stock. Would you like to accept that please?

Best regards,

XXXX

----

Hello,

I am sorry to inform you that is ceasing operation from Apr 1, 2021 due to Avnet's strategy.

Should there be any questions or any support needed from me, please contact me personally at:

email: XXXXX@qq.com

Mob/WeChat: +XXXXXX

Skype: XXXXXX

Thanks sincerely for your support in the past.

I will be happy to hear from you!

Wish you all the best!

XXXXX

can I build maaxboard zeus branch now?

gonewtinwind — Mon, 05 Apr 2021 13:58:09 GMT

Hi Josh,

Can I build maaxboard zeus branch now?

it shows The "zeus" branch will support MaaXBoard / MaaXBoard Mini in the end of Dec 2020.

beacuse my old maaxboard source code can not support 18.5" mimo touchscreem,I found some discussions in nxp forum,imx8mqevk board can not support some hdmi screem. so I am going to try a higher version. I am building

https://github.com/Avnet/meta-maaxboard/tree/zeus

mimo 18.5" touchscreen DVI-hdmi convertor no display for maaxboard

gonewtinwind — Thu, 01 Apr 2021 12:56:08 GMT

hi all,

I have posted my question here:

https://community.nxp.com/t5/i-MX-Processors/mimo-18-5-quot-touchscreen-DVI-hdmi-convertor-no-display-for/m-p/1255154#M171890

(I will post again at the end of this posting)

from the debug info , uboot is to set the hdmi as: No panel detected: default to HDMI
Display: HDMI (1280x720)

I guess maybe I change to the HDMI (1280x720) to HDMI (1280x1080). It seems it shall work.

do you know how to change in uboot envirment avaible or in uboot source code (uboot use default ENV,*** Warning - bad CRC, using default environment)?

or other solutions?

I tried the emmc maaxboard version from the manufactory setting(your company's image), it did not work.

but the 15.6" mimo touchscreen is working,the uboot debug info is same as: No panel detected: default to HDMI
Display: HDMI (1280x720) ,so I think if I want to change to HDMI (1280x1080) to try. but I do not know how to change.

Thank you

NXP posting same issue:

https://community.nxp.com/t5/i-MX-Processors/mimo-18-5-quot-touchscreen-DVI-hdmi-convertor-no-display-for/m-p/1255154#M1…

Hi all,

I am playing maaxboard (imx8mqevk) board with mimo 18.5" touchscreen DVI port. I use HDMI-DVI convertor.

but there is no any display: no uboot, no penguen logo output for yocto image, can not find any output in the screen

but my 15.6" mimo touchscreen works well.

I read here: https://community.nxp.com/t5/i-MX-Processors/How-to-config-the-hdmi-with-uboot/td-p/359302

it seems I need to set uboot env to choose different hdmi panel, for example : video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 , it tried to set like the following command in uboot command line : setenv video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 ,but can not.

How to do? any thelp?

Thank you

my uboot output in serail console(both 18.5" and 15.6" mimo touchscreen):

U-Boot 2018.03- (Dec 01 2020 - 20:03:21 +0000)

CPU: Freescale i.MX8MQ rev2.1 1300 MHz (running at 800 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 47C
Reset cause: POR
Model: Freescale i.MX8MQ EVK
DRAM: 2 GiB
MMC: FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

Failed (-5)
No panel detected: default to HDMI
Display: HDMI (1280x720)
In: serial
Out: serial
Err: serial

BuildInfo:
- ATF 1cb68fa
- U-Boot 2018.03-

switch to partitions #0, OK

----

my uboot(boot from sdcard) env , it seem the uboot uses the default env:

u-boot=> printenv
baudrate=115200
boot_fdt=try
bootcmd=run envboot;mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; else if run loadimage; then run mmcboot; else run netboot; fi; fi; else booti ${loadaddr} - ${fdti
bootcmd_mfg=run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "R;
bootdelay=2
bootenvfile=uEnv.txt
bootscript=echo Running bootscript from mmc ...; source
console=ttymxc0,115200 earlycon=ec_imx6q,0x30860000,115200
emmc_dev=0
envboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadbootenv; then echo Loaded env from ${bootenvfile};run importbootenv;fi;if test -n $uenvcmd; then echo Ru;
ethprime=FEC
fastboot_dev=mmc0
fdt_addr=0x43000000
fdt_file=em-sbc-imx8m.dtb
fdt_high=0xffffffffffffffff
fdtcontroladdr=bc92a360
image=Image
importbootenv=echo Importing environment from mmc${mmcdev} ...; env import -t ${loadaddr} ${filesize}
initrd_addr=0x43800000
initrd_high=0xffffffffffffffff
jh_clk=
jh_mmcboot=setenv fdt_file fsl-imx8mq-evk-root.dtb; setenv jh_clk clk_ignore_unused; if run loadimage; then run mmcboot; else run jh_netboot; fi;
jh_netboot=setenv fdt_file fsl-imx8mq-evk-root.dtb; setenv jh_clk clk_ignore_unused; run netboot;
kboot=booti
loadaddr=0x40480000
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenvfile}
loadbootscript=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};
loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}
loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}
mfgtool_args=setenv bootargs console=${console},${baudrate} rdinit=/linuxrc clk_ignore_unused
mmcargs=setenv bootargs console=ttymxc0,115200 earlycon=ec_imx6q,0x30860000,115200,115200 root=/dev/mmcblk0p2 rootwait rw rootwait rw video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24
mmcautodetect=yes
mmcboot=echo Booting from mmc ...; run mmcargs; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then booti ${loadaddr} - ${fdt_addr}; else echo WARN: Cannot load the DT; fi; ;
mmcdev=0
mmcpart=1
mmcroot=/dev/mmcblk0p2 rootwait rw
netargs=setenv bootargs ${jh_clk} console=${console} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; ${get_cmd} ${loadaddr} ${image}; if test ${boot_fdt} = yes || test ${b;
script=boot.scr
sd_dev=1
soc_type=imx8mq

Environment size: 2882/4092 bytes

MaaXBoard Introductory Training

jafoste4 — Mon, 29 Mar 2021 17:40:45 GMT

Hi Everyone,

If you have interest in Jump Starting your next NXP i.MX 8M project, check out this training targeting Avnet's MaaXBoard!

For reference, right now there is a discourt of 50% off the required hardware when attending one of the three available training sessions!

https://web.cvent.com/event/87ff33d5-dbe6-4c1d-abd8-4bb639cb41d0/summary

MaaXBoard

ishita8996 — Wed, 17 Mar 2021 05:47:20 GMT

Can someone please tell me how to enter the AVNET MaaXBoard into serial download mode?

Also, how to burn existing image on SD card to the onboard eMMC of the MaaXBoard?

How to replace the mini fuse found on the mother-board of a measuring instrument

subbusuccess — Fri, 12 Mar 2021 01:40:57 GMT

How to replace the mini fuse found on the mother board of a measuring instrument and what will be the rating of the fuse.

can not auto startup chromium(chromium-ozone-wayland)

gonewtinwind — Mon, 08 Mar 2021 14:12:38 GMT

hi all,

I am playing imx8qm maaxboard board

I have added

chromium.service at /etc/systemd/system/chromium.service

and make a link at /etc/systemd/system/multi-user.target.wants/chromium.service

it can run ExecStart=/bin/touch /aa.txt

after startup , I can find /aa.txt generated, it means the chromium.service running

but chromium not running.

anyway, I can manaully start up chromium after log in

Why can not auto startup chromium ?

any help?

thank you.

my chromium.service file:

[Unit]

Description=launch chromium

[Service]

Type=oneshot

ExecStart=/bin/touch /aa.txt

ExecStart=/bin/sleep 20

ExecStart=/usr/bin/chromium --no-sandbox --gpu-no-context-lost --enable-gpu-rasterization --start-fullscreen --kiosk --no-first-run --incognito http://localhost:3300/rpi.html > /dev/null 2>&1 &

[Install]

WantedBy=multi-user.target

Robot to write or draw anything on apparels

ethan12 — Thu, 04 Mar 2021 19:08:24 GMT

Hello Everyone

"DrawBo" is a very intelligent robot which can write or draw on T-shirts or Jersey Shirts.

Any comments or critiques are welcomed.

Share you views.

MaaxBoard HDMI not working

jxa0 — Tue, 02 Mar 2021 01:56:25 GMT

Hello,

I just received my MaaxBoard and flashed the SD card with multiple different oob images I found on your sites and none have worked long enough for me to modify my display or network settings

Is there a specific image that i should be using?

Issues:

the display initially works; however, as soon as I attempt to open a terminal or set up a network connection the screen blanks
The LG nvidia/G-sync display states that the resolution is 3840x2160, yet recommends 1920x1080

Images I've tried a few, including the two below and

MaaXBoard-LinuxShipmentImage-Debian-V1.1.1r10.img
MaaXBoard-LinuxShipmentImage-Yocto-V1.0.6r07

Thank you,
John

"generate_andoid9.0_image.sh" file not found while building .

narashimhaakannan — Mon, 01 Mar 2021 15:14:59 GMT

Hi guyz,
I am Developing Android source for "MAAXBOARD" , I followed all the instruction as per the "Document". But at the last while grouping all the image file that are required, the "generate_andoid9.0_image.sh" cannot be found on any my directory that is required to build. How do I get it. Looking for solutions.

Environment used: Ubuntu 18.04

Board:AVNET MAAXBOARD

Thank You.