Technexion PICO-PI-IMX7

texierp · June 27, 2021, 9:15pm

Yes @neuberfran, as I wrote, the PR is still open.

You need to use pico-pi-imx7d: bump to dunfell by texierp · Pull Request #232 · mendersoftware/meta-mender-community · GitHub

neuberfran · June 27, 2021, 9:22pm

@texierp Please, What I need to change in tutorial ?

gist.github.com

https://gist.github.com/neuberfran/89caf04e82a2607cd05cb3fd18a7c082#file-local-confdunfellissue

local.confDUNFELLissue

#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling

This file has been truncated. show original

This is my local.conf

texierp · June 28, 2021, 6:55am

You need to use my fork instead of the official repo of meta-mender-community.

See mender dunfell pico - Pastebin.com

Then, you’ll need also this commit u-boot-mender: Ignore case when checking variables in mender_Kconfig_… by texierp · Pull Request #1398 · mendersoftware/meta-mender · GitHub

neuberfran · June 30, 2021, 9:44pm

@texierp What about libgpiod v1.6 (not 1.4) in Yocto Zeus/Dunfell/Hardknott?

github.com/openembedded/meta-openembedded

How to put libgpiod v1.6(hardknott yocto release) in zeus release

opened 01:03AM - 12 Jun 21 UTC

neuberfran

Hi, I have a great knowledge of this tutorial: https://hub.mender.io/t/techne…xion-pico-pi-imx7/136 As can be seen it goes to Zeus (libgpiod version = 1.4) I need libgpiod v1.6 in my project to configure pull-up/pull-down I did the copy procedures, etc... and got the issue ERROR: Layer openembedded-layer is not compatible with the core layer which only supports these series: zeus (layer is compatible with hardknott) How to solve (psl) ![Captura de tela de 2021-06-11 22-02-26](https://user-images.githubusercontent.com/38701397/121760354-b7dbb580-cb00-11eb-90a0-e8998ccef645.png) :

neuberfran · July 13, 2021, 2:19pm

@texierp @drewmoseley @mirzak @jorisoffouga hi, I stay trying put dunfell and I have issue in boot: Error: ethernet@30be0000 address not set.
No ethernet found.

my printenv result:

gist.github.com

https://gist.github.com/neuberfran/e423f0731d6b440466fe9f152e076e2e

printenv

printenv
altbootcmd=run mender_altbootcmd; run bootcmd
arch=arm
baudrate=115200
board=pico-imx7d
board_name=pico-imx7d
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_efi_binary=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr ${fdtcontroladdr};fi;load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootarm.efi; if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf}
boot_net_usb_start=usb start

This file has been truncated. show original

After I set ip and mac address, the error becomes the following

DHCP client bound to address 192.168.1.190 (5 ms)
*** Warning: no boot file name; using ‘C0A801BE.img’
Using ethernet@30be0000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.190
Filename ‘C0A801BE.img’.
Load address: 0x80800000
Loading: T T T T T T T T

When I flash Zeus Yocto image (and not dunfell) I not have any errors and this is my printenv:

gist.github.com

https://gist.github.com/neuberfran/944c7a53f2a408a4dabac0e3ebb8345f

printenv_in_Zeus_here_OK

printenv
altbootcmd=run mender_altbootcmd; run bootcmd
arch=arm
baudrate=115200
board=pico-imx7d
board_name=pico-imx7d
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_efi_binary=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr ${fdtcontroladdr};fi;load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootarm.efi; if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf}
boot_net_usb_start=usb start

This file has been truncated. show original

drewmoseley · July 13, 2021, 7:21pm

It sounds to me like the U-Boot configuration for that board in Dunfell is missing something that is available in Zeus. But it may not be a problem unless you are intentionally trying to boot off of the network. I suspect the real problem is that your eMMC boot is somehow not working right.

Drew

texierp · July 13, 2021, 9:55pm

I suspect that the U-Boot boot script (boot.scr) is missing from your first partition.

On my side, after a “clean” build, I can confirm that integration on dunfell is working
as expected, no issues:

U-Boot SPL 2020.04+fslc+g88c58453be (Oct 13 2020 - 21:59:38 +0000)
Trying to boot from MMC1


U-Boot 2020.04+fslc+g88c58453be (Oct 13 2020 - 21:59:38 +0000)

CPU:   Freescale i.MX7D rev1.2 1000 MHz (running at 792 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 37C
Reset cause: POR
Model: TechNexion PICO-IMX7D Board and PI baseboard
Board: i.MX7D PICOSOM
I2C:   ready
DRAM:  512 MiB
PMIC:  PFUZE3000 DEV_ID=0x30 REV_ID=0x11
MMC:   FSL_SDHC: 2, FSL_SDHC: 1, FSL_SDHC: 0
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@30be0000
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
371 bytes read in 8 ms (44.9 KiB/s)
## Executing script at 80800000
switch to partitions #0, OK
mmc0(part 0) is current device
9470544 bytes read in 229 ms (39.4 MiB/s)
34647 bytes read in 18 ms (1.8 MiB/s)
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Using Device Tree in place at 83000000, end 8300b756

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.4.119-fslc+g43980dc5d7e6 (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP Fri May 14 21:08:38 UTC 2021
[    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
...

root@imx7d-pico:~# mender --version
2.6.0	runtime: go1.14.15

neuberfran · July 14, 2021, 6:07pm

@texierp mender dunfell pico - Pastebin.com

I didn’t do these steps above and I copied exactly the steps that jorisoffouga goes through in this tutorial. Are the steps I left undone already integrated in the main mender repository for imx7d-pico ?

texierp · July 14, 2021, 6:27pm

@neuberfran

I didn’t do these steps above and I copied exactly the steps that jorisoffouga goes through in this tutorial. Are the steps I left undone already integrated in the main mender repository for imx7d-pico ?

The same for me … and it works.

Can you try the folllowing command from U-Boot and post the result ?

=> ls mmc 0:1

Also, please provide a complete boot sequence of U-Boot.

neuberfran · July 14, 2021, 6:29pm

I solved this problem. Just rewriting the *.sdimg from dunfell. I didn’t mess with boot.src.

texierp · July 14, 2021, 6:30pm

OK, perfect

neuberfran · July 14, 2021, 6:38pm

@texierp

I have 1 more difficult and important problem now. I want to put c++/gdb on my image and it gives a space error. As below.
I just change the line: EXTRA_IMAGE_FEATURES ?= “debug-tweaks”
to EXTRA_IMAGE_FEATURES ?= “debug-tweaks tools-sdk tools-debug dev-pkgs” and bitbake doesn’t work anymore.

I am analyzing the causes/solutions and would like your help.

According to the screenshot below (df -h command) there is no lack of space in emmc when I put it in /sources/meta-mender/meta-mender-dmo/conf/layer.conf MENDER_STORAGE_TOTAL_SIZE_MB_DEFAULT ?= “3048”
IMAGE_OVERHEAD_FACTOR = “1.5”

What could I do to solve it?

issue:

ERROR: Task (/home/neuberfran/mender-nxp2/build/…/sources/poky/meta/recipes-core/images/core-image-base.bb:do_image_sdimg) failed with exit code ‘1’

ERROR: core-image-base-1.0-r0 do_image_mender: Size of rootfs is greater than the calculated partition space (1192755200 > 973078528). This image won’t fit on a device with the current storage configuration. Try reducing IMAGE_OVERHEAD_FACTOR if it is higher than 1.0, or raise MENDER_STORAGE_TOTAL_SIZE_MB if the device in fact has more storage.

ERROR: core-image-base-1.0-r0 do_image_mender: Execution of ‘/home/neuberfran/mender-nxp2/build/tmp/work/imx7d_pico-poky-linux-gnueabi/core-image-base/1.0-r0/temp/run.do_image_mender.2689808’ failed with exit code 1:

[ -z release-1 ]

stat -Lc %s /home/neuberfran/mender-nxp2/build/tmp/work/imx7d_pico-poky-linux-gnueabi/core-image-base/1.0-r0/deploy-core-image-base-image-complete/core-image-base-imx7d-pico.ext4

rootfs_size=1192755200

neuberfran · August 13, 2021, 3:04am

@texierp @drewmoseley

hi,
I have been interested in communicating between the a7 and the m4 of my imx7d-pico using RPmsg for a long time.

Today I found that this tutorial: Linux and Zephyr “Talking” to Each Other in the Same SoC - Diego Sueiro, Sepura / Embarcados - YouTube

don’t use mainline linux. I stay using kernel 5.6.xx with libgpiod 1.5

Using libgpiod I want to press a controlled button on a7 and flash an LED (which is waiting for this command) on m4

I was checking the issue link below and I have 2 questions below:

How can I adapt this project by @jorisoffouga
to the nxp forum project (link above) for me to get the following files: mu.c, imx_rpmsg.c, imx_rpmsg_tty.c and/or imx_rpmsg_tty.ko
What is the best way to do RPmsg communication between a7 and m4 using Yocto on a7?

drewmoseley · August 13, 2021, 2:33pm

Sorry, but I’m not too familiar with RPMSG. I know it is the best way to communicate between the M and A cores but it will be very platform specific. At a minimum you will need kernel configs enabled but you may also need to add some user space components. Some of the Zephyr mailing lists would be a better place to ask this.

Drew

neuberfran · August 13, 2021, 4:16pm

@drewmoseley What about my issue (Already posted above for Mr @texterp) very important to me to put c/c++ in my Yocto/dunfell project:

I have 1 more difficult and important problem now. I want to put c++/gdb on my image and it gives a space error. As below.
I just change the line: EXTRA_IMAGE_FEATURES ?= “debug-tweaks”
to EXTRA_IMAGE_FEATURES ?= “debug-tweaks tools-sdk tools-debug dev-pkgs” and bitbake doesn’t work anymore.

I am analyzing the causes/solutions and would like your help.

According to the screenshot below (df -h command) there is no lack of space in emmc when I put it in /sources/meta-mender/meta-mender-dmo/conf/layer.conf MENDER_STORAGE_TOTAL_SIZE_MB_DEFAULT ?= “3048”
IMAGE_OVERHEAD_FACTOR = “1.5”

What could I do to solve it?

issue:

ERROR: Task (/home/neuberfran/mender-nxp2/build/…/sources/poky/meta/recipes-core/images/core-image-base.bb:do_image_sdimg) failed with exit code ‘1’

ERROR: core-image-base-1.0-r0 do_image_mender: Size of rootfs is greater than the calculated partition space (1192755200 > 973078528). This image won’t fit on a device with the current storage configuration. Try reducing IMAGE_OVERHEAD_FACTOR if it is higher than 1.0, or raise MENDER_STORAGE_TOTAL_SIZE_MB if the device in fact has more storage.

ERROR: core-image-base-1.0-r0 do_image_mender: Execution of ‘/home/neuberfran/mender-nxp2/build/tmp/work/imx7d_pico-poky-linux-gnueabi/core-image-base/1.0-r0/temp/run.do_image_mender.2689808’ failed with exit code 1:

[ -z release-1 ]

stat -Lc %s /home/neuberfran/mender-nxp2/build/tmp/work/imx7d_pico-poky-linux-gnueabi/core-image-base/1.0-r0/deploy-core-image-base-image-complete/core-image-base-imx7d-pico.ext4

rootfs_size=1192755200

drewmoseley · August 13, 2021, 4:39pm

You actually want to run the compiler tools on the target? That is going to be extremely slow. Why is cross compiling not a possibility?

As for the space issue you will need to modify the variables Mender uses to calculate the size:
MENDER_STORAGE_TOTAL_SIZE_MB
MENDER_DATA_PART_SIZE_MB
MENDER_BOOT_PART_SIZE_MB

Basically, the rootfs size is calculated as:

size = (MENDER_STORAGE_TOTAL_SIZE_MB - MENDER_DATA_PART_SIZE_MB - MENDER_BOOT_PART_SIZE_MB)/2

You will need to tweak those values until the rootfs size is big enough.

Drew

neuberfran · August 13, 2021, 5:42pm

@drewmoseley your question: You actually want to run the compiler tools on the target?

Answer: I just want to run a script in c/c++ to blink a led on imx7d-pico, as I’ve already done with python3.
How to proceed in this case?

this is my layer.conf in /home/neuberfran/mender-nxp2/sources/meta-mender/meta-mender-demo/conf

gist.github.com

https://gist.github.com/neuberfran/7725958058870dab3d0e5ab61b4324ce

layer.conf

# Layer configuration for meta-mender
# Copyright 2017 Northern.tech AS

# We have a conf and classes directory, add to BBPATH
BBPATH .= ":${LAYERDIR}"

# We have recipes-* directories, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
	${LAYERDIR}/recipes-*/*/*.bbappend"

This file has been truncated. show original

this is my local.conf:

gist.github.com

https://gist.github.com/neuberfran/57339c7d2f171ae385eef4d153eb8937

local.conf

#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling

This file has been truncated. show original

drewmoseley · August 13, 2021, 6:34pm

Well, c/c++ is not a scripting language so you don’t generally want to install the compiler on the target. The normal workflow with yocto is to cross compile it. Ideally you would generate a Yocto recipe for your code and have it built as part of your standard Yocto build. Alternatively, and especially during development, you can use the Yocto SDK to get a cross toolchain to allow you to build the code on your desktop. From there you can just scp it to the target and run it.

neuberfran · August 13, 2021, 8:06pm

@drewmoseley tks but I will need change in my local.conf (Or in other file)?

My local.conf atual is:

gist.github.com

https://gist.github.com/neuberfran/57339c7d2f171ae385eef4d153eb8937

local.conf

#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling

This file has been truncated. show original

drewmoseley · August 13, 2021, 9:00pm

You’ll need to generate your own recipe for your c/c++ application. After that you will need to add it into your image using IMAGE_INSTALL_append in local.conf.

Drew

Topic		Replies	Views
Technexion PICO-IMX7D SOM Yocto Project yocto , rocko , nxp	12	3020	August 2, 2020
NXP WaRP7 Yocto Project yocto , sumo , imx7 , nxp , warp7 , freescale , thud , dunfell	0	1903	November 24, 2018
TechNexion PICO-PI-IMX8M-MINI Yocto Project yocto , nxp , zeus	0	2412	October 19, 2020
Technexion PICO-IMX8M Yocto Project yocto , sumo , nxp , technexion	0	1624	January 7, 2021
NXP® i.MX 8M Mini Evaluation Kit Yocto Project sumo , nxp , imx8mm	17	7498	March 22, 2021

Related topics