Technexion PICO-PI-IMX7

@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 ?

@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.

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

OK, perfect

@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

@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:

  1. 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

  2. What is the best way to do RPmsg communication between a7 and m4 using Yocto on a7?


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

@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

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

@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

this is my local.conf:

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.

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

My local.conf atual is:

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

https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe

@drewmoseley @dellgreen devtool is very cool:

https://sergioprado.org/ferramenta-devtool-do-yocto-project/

@texierp @drewmoseley
https://groups.google.com/g/open-amp/c/muD2nZayhAM?pli=1
I need meta-openamp to do RPmsg project here. But I stay with this issue:

Layer openamp-layer is not compatible with the core layer which only supports these series: dunfell (layer is compatible with gatesgarth)

You’ll need to check with the maintainers of the openamp-layer. It does not seem to be compatible with dunfell.

Drew

@drewmoseley thanks for a while

ls mmc 0:1
371 boot.scr
lib/

1 file(s), 1 dir(s)

=>
This issue has been reappearing constantly