So, I started trying to build a minimal Yocto build (version 6). Got everything setup following the instructions. I started building (bitbake core-image-minimal) and it went for quite a while, but then I started getting timeouts.

line 581, in connectProcessServer
** sock.connect(os.path.basename(sockname))**
BlockingIOError: [Errno 11] Resource temporarily unavailable

I will admit that I have turned on and off:
#BB_HASHSERVE_UPSTREAM = “ typhoon.yocto.io:8687 ”
#SSTATE_MIRRORS ?= "file://. http://sstate.yoctoproject.org/3.4/PATH;downloadfilename=PATH " *

and this:
#BB_HASHSERVE = “auto”
#BB_SIGNATURE_HANDLER = “OEEquivHash”

And i get slightly different results but the effect is the same. A timeout error.

The IP address it is trying to get to is 198.145.29.33., which doesn’t show a rDNS entry.
I am also getting this warning:
oe-core/build/…/layers/meta-freescale/recipes-multimedia/imx-codec/imx-codec_4.7.2.bb:63: DeprecationWarning: invalid escape sequence .

I get to this point and things start to go awry:
–2023-06-14 10:26:50-- https://artifacts.toradex.com/artifactory/tdxref-torizoncore-sources-frankfurt/6/x86_64-nativesdk-libc-3.9.tar.xz
Resolving artifacts.toradex.com ( artifacts.toradex.com )… 3.125.132.142
Connecting to artifacts.toradex.com ( artifacts.toradex.com )|3.125.132.142|:443… connected.
HTTP request sent, awaiting response… 404 Not Found
2023-06-14 10:26:51 ERROR 404: Not Found.

–2023-06-14 10:26:51-- https://artifacts.toradex.com/artifactory/tdxref-torizoncore-sources-frankfurt/6/uninative/3dd82c3fbdb59e87bf091c3eef555a05fae528eeda3083828f76cd4deaceca8b/x86_64-nativesdk-libc-3.9.tar.xz
Resolving artifacts.toradex.com ( artifacts.toradex.com )… 3.125.132.142
Connecting to artifacts.toradex.com ( artifacts.toradex.com )|3.125.132.142|:443… connected.
HTTP request sent, awaiting response… 404 Not Found
2023-06-14 10:26:52 ERROR 404: Not Found.

–2023-06-14 10:26:52-- http://downloads.yoctoproject.org/releases/uninative/3.9/x86_64-nativesdk-libc-3.9.tar.xz
Resolving downloads.yoctoproject.org ( downloads.yoctoproject.org )… 198.145.29.62
Connecting to downloads.yoctoproject.org ( downloads.yoctoproject.org )|198.145.29.62|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 6014328 (5.7M) [application/octet-stream]
Saving to: ‘/home/steve/oe-core/build/…/downloads/uninative/3dd82c3fbdb59e87bf091c3eef555a05fae528eeda3083828f76cd4deaceca8b/x86_64-nativesdk-libc-3.9.tar.xz’

So, according to the documentation, this is an imx8m-plus downstream version of Yocto.
Any suggestions here would be helpful!

Steve

It’s been more than a year since I built yocto verdin imx8, but I pulled everything local and built from there.

I hope they haven’t changed the entire build process to require remote fetching. I’ve seen a lot of complaints about their Web site and time outs. I pray to God they aren’t using anything from Amazon because AWS has multi-hour outages on a regular basis.

Greetings @Evets ,

First of all are you trying to build from our Reference BSP or from TorizonCore? Which instructions are you following?

I see you’re trying to build core-image-minimal which isn’t one of our images, did you intend that?

As for the timeout issues I can’t say I’ve seen anything major recently just minor network hiccups that go away upon a retry. Are you able to access the timed-out URLs from your network in the first place?

Best Regards,
Jeremias

Hi @jeremias.tx ,
Yes, I am trying to do a Yocto build of minimal size, and then work my way up from there. I want to see what devices show up in this build, and then add my program to see what else I need.
At this point, I found that if I upgraded the tools to the latest, it built very fast and is complete. So now I am trying to deploy, but I can’t get the board to mount as USB drive. It keeps coming up with an error.
I have built core-image-minimal-verdin-imx8mp-20230615231906-Tezi_6.3.0-devel-202306
15231906+build.0.tar tarball and i want to be able to program it.

I have built core-image-minimal-verdin-imx8mp-20230615231906-Tezi_6.3.0-devel-20230615231906+build.0.tar tarball and i want to be able to program it.

If you have an Easy Installer compatible tar archive then you can try to install it with Easy Installer: Loading Toradex Easy Installer | Toradex Developer Center

Though keep in mind core-image-minimal is not a tested configuration of ours so I can’t give any guarantees on how it will work out for you.

Best Regards,
Jeremias

Hi @jeremias.tx ,
I can’t seem to get the easy installer to mount my flash drive. Is there a particular format it needs? It just comes up with an error. I do also have the reference version as well, so if the core version doesn’t work and I try the reference version.

Steve

Is there a particular format it needs?

Standard FAT32 should be fine and is what most of my USB drives typically are.

I do also have the reference version as well, so if the core version doesn’t work and I try the reference version.

Wait are you having an issue with the drive or the image itself?

Best Regards,
Jeremias

Hi @jeremias.tx ,
It turns out that the name of the tar file was causing the drive error. When I extracted the tarball to a folder with a short name, Easyloader found it and placed it on the list.
So, my next trick is to change the pinout to add a second SPI device. I did it with a Torizon build, but how do I do that with the yocto build? It says in there that you guys don’t keep files for that. I currently have the reference Yocto build on my board, and I can see the spidev1.0 there as expected.

Steve

Thanks,
Steve

So, my next trick is to change the pinout to add a second SPI device. I did it with a Torizon build, but how do I do that with the yocto build?

Well the core concept is more or less the same. You would still do the same/similar device tree changes you did in TorizonCore, but you now need to integrate your changes into your Yocto build, basically modify the default kernel recipe in order to incorporate your changes.

We have an article on how to do basic changes in Yocto including device tree and kernel changes: Custom meta layers, recipes and images in Yocto Project (hello-world examples) | Toradex Developer Center

Best Regards,
Jeremias

Hi @jeremias.tx ,
So, I read something recently on the site that said you can apply a change to the current build.
I am assuming that the change to the device tree is the same between the reference yocto build and Torizon default build since all the devices seem to be there. Can I just deploy that change to the Yocto reference build? I already have a device tree change working that adds the extra SPI to the device tree. It would seem that the device tree is separate from the Linux build, as it is just setting up the mux and output changes. Is this a correct assumption?

Thanks,
Steve

Hi @jeremias.tx ,
Going through website, it sends me here:
Build Device Tree Overlays from Source Code | Toradex Developer Center ’

it says to clone a directory but add in the correct branch name. However, when I go to the repository, there are no branches here. It appears that this is broken here.

Evets:

Can I just deploy that change to the Yocto reference build? I already have a device tree change working that adds the extra SPI to the device tree.

I mean yes, did you see the documentation I referenced in my previous post? There’s a section in there about how one could incorporate kernel and device tree related changes. It outlines a simple example though, so you may still need to reference Yocto documentation for more complex scenarios.

Hi @alex.tx ,
Yes, if I use your cgit link, I can see the branches. However, if I use the straight git link:
Index of /device-tree-overlays.git (toradex.com) ,
and I click on branches, nothing shows there.

Steve

Hi @jeremias.tx ,
yes, I got to the point that you compile the actual dtb (in my case imx8mp-verdin-wifi-dev.dtb) and I get a whole bunch of warnings. See below:

DTC arch/arm64/boot/dts/freescale/imx8mp-verdin-wifi-dev.dtb
arch/arm64/boot/dts/freescale/imx8mp.dtsi:453.30-459.5: Warning (unit_address_vs_reg): /power-domains/power-domain@14: node has a unit name, but no reg or ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1278.12-1282.7: Warning (unit_address_vs_reg): /soc@0/bus@32c00000/mipi_dsi@32e60000/port@0: node has a unit name, but no reg or ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1362.22-1407.6: Warning (unit_address_vs_reg): /soc@0/bus@32c00000/ldb@32ec005c: node has a unit name, but no reg or ranges property
also defined at arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi:818.6-834.3
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1409.26-1428.6: Warning (unit_address_vs_reg): /soc@0/bus@32c00000/phy@32ec0128: node has a unit name, but no reg or ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:2013.12-2017.7: Warning (unit_address_vs_reg): /soc@0/bus@30c00000/hdmi@32fd8000/port@0: node has a unit name, but no reg or ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:2344.25-2350.4: Warning (unit_address_vs_reg): /mix_gpu_ml: node has a reg or ranges property, but no unit name
arch/arm64/boot/dts/freescale/imx8mp.dtsi:328.26-335.5: Warning (simple_bus_reg): /power-domains/hsiomix-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:337.20-343.5: Warning (simple_bus_reg): /power-domains/pcie-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:345.27-351.5: Warning (simple_bus_reg): /power-domains/usbotg1-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:353.27-359.5: Warning (simple_bus_reg): /power-domains/usbotg2-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:362.22-370.5: Warning (simple_bus_reg): /power-domains/mlmix-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:372.28-379.5: Warning (simple_bus_reg): /power-domains/audiomix-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:381.24-388.5: Warning (simple_bus_reg): /power-domains/gpumix-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:390.22-397.5: Warning (simple_bus_reg): /power-domains/gpu2d-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:399.22-407.5: Warning (simple_bus_reg): /power-domains/gpu3d-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:409.24-415.5: Warning (simple_bus_reg): /power-domains/vpumix-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:417.23-424.5: Warning (simple_bus_reg): /power-domains/vpug1-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:426.23-433.5: Warning (simple_bus_reg): /power-domains/vpug2-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:435.23-442.5: Warning (simple_bus_reg): /power-domains/vpuh1-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:444.28-451.5: Warning (simple_bus_reg): /power-domains/mediamix-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:453.30-459.5: Warning (simple_bus_reg): /power-domains/power-domain@14: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:461.29-467.5: Warning (simple_bus_reg): /power-domains/mipiphy1-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:469.29-475.5: Warning (simple_bus_reg): /power-domains/mipiphy2-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:477.26-485.5: Warning (simple_bus_reg): /power-domains/hdmimix-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:487.27-493.5: Warning (simple_bus_reg): /power-domains/hdmiphy-pd: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:751.29-758.6: Warning (simple_bus_reg): /soc@0/bus@30000000/caam_secvio: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1362.22-1407.6: Warning (simple_bus_reg): /soc@0/bus@32c00000/ldb@32ec005c: missing or empty reg/ranges property
also defined at arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi:818.6-834.3
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1409.26-1428.6: Warning (simple_bus_reg): /soc@0/bus@32c00000/phy@32ec0128: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1884.31-1887.6: Warning (simple_bus_reg): /soc@0/bus@30c00000/audiomix_dsp: missing or empty reg/ranges property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1263.32-1283.6: Warning (avoid_unnecessary_addr_size): /soc@0/bus@32c00000/mipi_dsi@32e60000: unnecessary #address-cells / #size-cells without “ranges” or child “reg” property
arch/arm64/boot/dts/freescale/imx8mp.dtsi:2073.23-2106.5: Warning (unique_unit_address): /soc@0/pcie@33800000: duplicate unit-address (also used in node /soc@0/pcie_ep@33800000)
also defined at arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi:837.7-855.3
also defined at arch/arm64/boot/dts/freescale/imx8mp-verdin-dev.dtsi:135.7-138.3
arch/arm64/boot/dts/freescale/imx8mp.dtsi:760.34-765.6: Warning (unique_unit_address): /soc@0/bus@30000000/caam-snvs@30370000: duplicate unit-address (also used in node /soc@0/bus@30000000/snvs@30370000)
arch/arm64/boot/dts/freescale/imx8mp.dtsi:607.25-618.6: Warning (interrupt_provider): /soc@0/bus@30000000/gpio@30200000: Missing #address-cells in interrupt provider
also defined at arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi:385.8-402.3
arch/arm64/boot/dts/freescale/imx8mp.dtsi:620.25-631.6: Warning (interrupt_provider): /soc@0/bus@30000000/gpio@30210000: Missing #address-cells in interrupt provider
also defined at arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi:404.8-424.3
arch/arm64/boot/dts/freescale/imx8mp.dtsi:633.25-644.6: Warning (interrupt_provider): /soc@0/bus@30000000/gpio@30220000: Missing #address-cells in interrupt provider
also defined at arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi:426.8-457.3
arch/arm64/boot/dts/freescale/imx8mp.dtsi:646.25-657.6: Warning (interrupt_provider): /soc@0/bus@30000000/gpio@30230000: Missing #address-cells in interrupt provider
also defined at arch/arm64/boot/dts/freescale/imx8mp-verdin.dtsi:459.8-502.3
arch/arm64/boot/dts/freescale/imx8mp.dtsi:659.25-670.6: Warning (interrupt_provider): /soc@0/bus@30000000/gpio@30240000: Missing #address-cells in interrupt provider
also defined at arch/arm64/boot/dts/freescale/imx8mp-verdin-wifi.dtsi:20.8-51.3
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1908.37-1923.6: Warning (interrupt_provider): /soc@0/bus@30c00000/irqsteer@32fc2000: Missing #address-cells in interrupt provider
arch/arm64/boot/dts/freescale/imx8mp.dtsi:2034.38-2042.5: Warning (interrupt_provider): /soc@0/interrupt-controller@38800000: Missing #address-cells in interrupt provider
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1285.36-1314.6: Warning (graph_child_address): /soc@0/bus@32c00000/lcd-controller@32e80000: graph node has single child node ‘port@0’, #address-cells / #size-cells are not necessary
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1316.36-1351.6: Warning (graph_child_address): /soc@0/bus@32c00000/lcd-controller@32e90000: graph node has single child node ‘port@0’, #address-cells / #size-cells are not necessary
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1391.20-1406.7: Warning (graph_child_address): /soc@0/bus@32c00000/ldb@32ec005c/lvds-channel@1: graph node has single child node ‘port@0’, #address-cells / #size-cells are not necessary
arch/arm64/boot/dts/freescale/imx8mp.dtsi:1937.36-1977.6: Warning (graph_child_address): /soc@0/bus@30c00000/lcd-controller@32fc6000: graph node has single child node ‘port@0’, #address-cells / #size-cells are not necessary

is this normal?