iMX8QXP I2C RPBUS configuration Hi NXP Team, We are using iMX8QXP as our SoC with our custom design. In the EVK when we disable the i2c_rpbus_5, i2c_rpbus_15 nodes in the imx8x-mek-rpmsg.dtsi file we are facing failure in booting of A35. We are using the default power mode application in the M4 side. Hence please let us know on what basis we need to allocate the i2c_rpbus nodes and whether is it mandatory to allocate i2c_rpbus nodes if we wish to use M4 along with A35?. Regards, Ranjith Kumar. Re: iMX8QXP I2C RPBUS configuration Hi Zhiming, We think the issue is sorted out once we change as per your suggestion in the mek.h file. Thanks for your support. Will check with you if any other issue arises. Regards, Ranjith Kumar. Re: iMX8QXP I2C RPBUS configuration Hi @ranjithkumar_kv  From the error log, it seems relate to vring and vdev address, but i just calculate the vdev and vring address, there are in range of 2GB. Maybe this issue is caused by incorrect DRAM definition in Uboot. The Linux still use 3GB DRAM size to map address , this could be the reason about address NULL issue. You can try to modify  include/configs/imx8qxp_mek.h in Uboot like this. Best Regards Zhiming  Re: iMX8QXP I2C RPBUS configuration Hi Zhiming, We are using 2GiB of DRAM in our design. Can you please let me know if any guide is available for changing the address? Regards, Ranjith Kumar. Re: iMX8QXP I2C RPBUS configuration Hi @ranjithkumar_kv  Here are vdevbuffer and vring definitions in mek dtsi, are you using same DRAM size? If not, you need adjust these address. reserved-memory { #address-cells = <2>; #size-cells = <2>; ranges; vdev0vring0: vdev0vring0@90000000 { reg = <0 0x90000000 0 0x8000>; no-map; }; vdev0vring1: vdev0vring1@90008000 { reg = <0 0x90008000 0 0x8000>; no-map; }; vdev1vring0: vdev1vring0@90010000 { reg = <0 0x90010000 0 0x8000>; no-map; }; vdev1vring1: vdev1vring1@90018000 { reg = <0 0x90018000 0 0x8000>; no-map; }; rsc_table: rsc_table@900ff000 { reg = <0 0x900ff000 0 0x1000>; no-map; }; vdevbuffer: vdevbuffer { compatible = "shared-dma-pool"; reg = <0 0x90400000 0 0x100000>; no-map; }; }; Re: iMX8QXP I2C RPBUS configuration Hi Zhiming, We haven't modified the U-boot source code other than the dts, defconfig and board file changes. We have used "flash_linux_m4" flag for booting with M4 and "flash" flag for booting without M4 in the imx-mkimage compilation. Regards, Ranjith Kumar. Re: iMX8QXP I2C RPBUS configuration Hi @ranjithkumar_kv  Have you load the m4_0.bin in uboot? Re: iMX8QXP I2C RPBUS configuration Hi Zhiming, Please find the dtsi files in the attachment (dtsi.zip). Regards, Ranjith Kumar. Re: iMX8QXP I2C RPBUS configuration Hi @ranjithkumar_kv  Can you share your device tree file? Thanks Re: iMX8QXP I2C RPBUS configuration Hi Zhiming, We have received our target board and when I boot the board with M4 having only one i2c bus (mapped to i2c1 in the mek.dtsi file) in the rpmsg.dtsi file, we're facing kernel panic from imx-rproc driver and when I boot the board without M4 there is no issue in booting. Attaching the logs of the kernel panic below. Please look into it and let me know what is the RCA of this issue. Regards, Ranjith Kumar. Re: iMX8QXP I2C RPBUS configuration Hi Zhiming, Thanks for the support. Regards, Ranjith Kumar Re: iMX8QXP I2C RPBUS configuration Hi @ranjithkumar_kv  Yes, of course Re: iMX8QXP I2C RPBUS configuration Hi Zhiming, Thanks for the detailed clarification. My query is like in our target device we won't be having any of the slaves mentioned in the rpmsg.dtsi file, so in this case can we disable all the i2c_rpbus nodes? Regards, Ranjith Kumar Re: iMX8QXP I2C RPBUS configuration Hi @ranjithkumar_kv  It depends on which i2c_rpbus node, for example, if you need use typec port ,you can't disable or comment i2c_rpbus_1. For pca9557_a and pca9557_b in i2c_rpbus_15 node, they could be used for gpio control in other devices, so please handle these devices with care. But for other sensor devices, you can disable them. Best Regards Zhiming Re: iMX8QXP I2C RPBUS configuration Hi Zhiming, Thanks for the information. By disabling the slaves present in the i2c_rpbus_5 we're able to boot the board. One additional query, is it mandatory to have i2c_rpbus nodes or else can we disable all the i2c_rpbus nodes along with it's associated slaves? Regards, Ranjith Kumar. Re: iMX8QXP I2C RPBUS configuration Hi @ranjithkumar_kv  If you have disabled the i2c_rpbus_5 node, please also disabled it's slave devices or comment the whole i2c_rpbus_5 node in rpmsg.dtsi Re: iMX8QXP I2C RPBUS configuration Hi Zhiming, Please find the kernel boot logs in the attachment (kernel_error_logs.txt). Regards, Ranjith Kumar Re: iMX8QXP I2C RPBUS configuration Hello @ranjithkumar_kv  Can you provide kernel boot log? Best Regards Zhiming

T1024 ehernetインターフェースが起動しない ねえ皆さん！ t1024ベースのボードのイメージをまとめようとしました。建物には、Buildrootツールと新しいカーネル6.1.44を使用しました。しかし、イーサネットインターフェースは立ち上がりませんが ip a インターフェイスのリストを表示する 1: lo: mtu 65536 qdisc noqueue qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:00 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:01 brd ff:ff:ff:ff:ff:ff 4: eth2: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:02 brd ff:ff:ff:ff:ff:ff 5: eth3: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:03 brd ff:ff:ff:ff:ff:ff 6: tunl0@NONE: mtu 1480 qdisc noop qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: mtu 1480 qdisc noop qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 切ない ip link set dev eth0 up エラーを与える fsl_dpaa_mac ffe4e0000.ethernet eth0: init_phy() failed ブートログ中に、私はこれを見ることができます: mdio_bus 0x0000000ffe4fc000: MDIO device at address 2 is missing. mdio_bus 0x0000000ffe4fc000: MDIO device at address 6 is missing. mdio_bus 0x0000000ffe4fd000: MDIO device at address 1 is missing. mdio_bus 0x0000000ffe4fd000: MDIO device at address 2 is missing. platform ffe488000.port: Adding to iommu group 15 platform ffe489000.port: Adding to iommu group 16 platform ffe48a000.port: Adding to iommu group 17 platform ffe48b000.port: Adding to iommu group 18 fsl_dpaa_mac ffe4e0000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e0000.ethernet: FMan MAC address: 00:00:00:00:01:00 fsl_dpaa_mac ffe4e2000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e2000.ethernet: FMan MAC address: 00:00:00:00:01:01 fsl_dpaa_mac ffe4e4000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e4000.ethernet: FMan MAC address: 00:00:00:00:01:02 fsl_dpaa_mac ffe4e6000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e6000.ethernet: FMan MAC address: 00:00:00:00:01:03 fsl_dpaa_mac ffe4e0000.ethernet eth0: Probed interface eth0 fsl_dpaa_mac ffe4e2000.ethernet eth1: Probed interface eth1 fsl_dpaa_mac ffe4e4000.ethernet eth2: Probed interface eth2 fsl_dpaa_mac ffe4e6000.ethernet eth3: Probed interface eth3 MDIOが正しく構成されていないというのは本当ですか?私はカーネルソースからのデバイスツリーを使用していますが、Ubootは以前のイメージ(カーネルバージョン3.12.27)から保持されています。新しいrootfs、dtb、uImageをRAMにロードし、そこから実行しました。 ethtool 次を見せてください: ethtool eth0 Settings for eth0: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: Unknown! Duplex: Half Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: off MDI-X: Unknown Current message level: 0x00002037 (8247) drv probe link ifdown ifup hw Link detected: no T1024でイーサネットを使用するための秘訣はありますか? QorIQ SDK 2.0から新しい画像をコンパイルしようとしましたが、非常に古いツールがあり、多くのエラーで停止しました。 QorIQ T1デバイス 日時:T1024 ehernetインターフェースが起動しない どうもありがとうございます。私は問題を解決しました。

Integrating lpddr4_timing.c for custom board using i.MX 8M plus Hello, I am bringing up a custom board using an i.MX 8M plus, and I am having trouble with u-boot SPL failing to boot with what I believe is a calibrated lpddr4_timing.c file. I followed the instructions to use the MSCALE DDR Tool v3.31 to successfully perform a DDR stress test. I then generated a calibrated lpddr4_timing.c. Following section 4.5.2 of MSCALE_DDR_Tool_User_Guide.pdf, I copied the generated lpddr4_timing.c file into the board/freescale/imx8mp_evk/ directory in the u-boot-imx project of my Yocto build environment.  I then forced a compilation of u-boot-imx using the command bitbake u-boot-linux -f -c compile I then built imx-image-core using the usual command bitbake imx-image-core Finally, I wrote the generated .wic.zst image to an SD card as I have done previously when adding packages and modifying the Linux device tree. However, when I boot, I see the following debug message over UART. U-Boot SPL 2024.04+g674440bc73e+p0 (Oct 24 2024 - 14:35:20 +0000) DDRINFO: start DRAM init DDRINFO: DRAM rate 4000MTS Training FAILED Is there a step I am missing when integrating the lpddr4_timing.c into a build of imx-core-image? i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Integrating lpddr4_timing.c for custom board using i.MX 8M plus I believe my build of u-boot was not correctly building in the lpddr4_timing.c file using just the bitbake u-boot-linux -f -c compile command. What worked for me was deleting lpddr4_timing.o from the build artifacts. I then forced another u-boot compile using bitbake u-boot-linux -f -c compile and verified that lpddr4_timing.o was regenerated. I then built imx-image-core using the usual command bitbake imx-image-core Finally, I wrote the generated .wic.zst image to an SD card as I have done previously when adding packages and modifying the Linux device tree. When I booted the device, it worked. I'll need to review how I include my board specific lpddr4_timing.c into my device layer, and how to force a full rebuild, but not a checkout of from source repositories, using bitbake commands. Re: Integrating lpddr4_timing.c for custom board using i.MX 8M plus Hello, You are following the correct steps to generate and implement the DDR scripts using Yocto, there is no additional steps to implement it. How are you flashing the image? UUU? Best regards.

iMX8QXP I2C RPBUS構成 こんにちは、NXP チームの皆様、 iMX8QXPをSoCとして使用し、カスタムデザインを採用しています。EVK で i2c_rpbus_5 を無効にすると、imx8x-mek-rpmsg.dtsi ファイルの i2c_rpbus_15 ノードで A35 の起動に失敗します。M4側のデフォルトの電源モードアプリケーションを使用しています。 したがって、i2c_rpbusノードを割り当てる必要があるのはどのような基準で、A35と一緒にM4を使用する場合、i2c_rpbusノードを割り当てることが必須かどうかをお知らせください。 よろしく ランジス・クマール。 Re:iMX8QXP I2C RPBUS構成 こんにちはZhiming、 mek.hファイルの提案に従って変更すると、問題は解決されると思います。ご支援いただきありがとうございます。 他に問題が発生していないか確認します。 よろしく ランジス・クマール。 Re:iMX8QXP I2C RPBUS構成 こんにちはZhiming、 設計には 2GiB の DRAM を使用しています。住所変更のガイドがあれば教えてください。 よろしく ランジス・クマール。 Re:iMX8QXP I2C RPBUS構成 こんにちはZhiming、 U-boot のソースコードは、dts、defconfig、board ファイルの変更以外は変更していません。imx-mkimage コンパイルでは、M4 での起動には "flash_linux_m4" フラグを、M4 を使用しない起動には "flash" フラグを使用しました。 よろしく ランジス・クマール。 Re:iMX8QXP I2C RPBUS構成 こんにちはZhiming、 添付ファイル(dtsi.zip)でdtsiファイルを見つけてください。 よろしくお願いします。 ランジス・クマール。 Re:iMX8QXP I2C RPBUS構成 こんにちはZhiming、 ターゲット ボードを受け取り、rpmsg.dtsi ファイルに i2c バスが 1 つ (mek.dtsi ファイルの i2c1 にマップされている) しかない M4 でボードを起動すると、imx-rproc ドライバーからカーネル パニックが発生し、M4 なしでボードを起動すると、起動に問題はありません。カーネルパニックのログを以下に添付します。 それを調べて、この問題のRCAが何であるかを教えてください。 よろしく ランジス・クマール。 Re:iMX8QXP I2C RPBUS構成 こんにちはZhiming、 サポートありがとうございます。 よろしく ランジット・クマール Re:iMX8QXP I2C RPBUS構成 こんにちはZhiming、 詳細な説明をありがとう。 私のクエリは、ターゲットデバイスではrpmsg.dtsiファイルに記載されているスレーブが存在しないようなものです。したがって、この場合、すべてのi2c_rpbusノードを無効にできますか? よろしく ランジット・クマール Re:iMX8QXP I2C RPBUS構成 こんにちはZhiming、 情報をありがとう。i2c_rpbus_5に存在するスレーブを無効にすることで、ボードを起動できます。 もう1つの質問として、i2c_rpbusノードを持つことが必須ですか、それともすべてのi2c_rpbusノードとそれに関連するスレーブを無効にすることができますか? よろしくお願いします。 ランジス・クマール。 Re:iMX8QXP I2C RPBUS構成 こんにちはZhiming、 カーネルブートログは添付ファイル(kernel_error_logs.txt)で見つけてください。 よろしくお願いします。 ランジット・クマール

iMX8QXP I2C RPBUS配置 您好，NXP团队： 我们正在使用 iMX8QXP 作为我们的定制设计的 SoC。在 EVK 中，当我们禁用 imx8x-mek-rpmsg.dtsi 文件中的 i2c_rpbus_5、i2c_rpbus_15 节点时，A35 启动将失败。我们在M4端使用的是默认的电源模式应用程序。 因此，请让我们知道我们需要在什么基础上分配 i2c_rpbus 节点，以及如果我们希望将 M4 与 A35 一起使用，是否必须分配 i2c_rpbus 节点？ 问候， 兰吉斯·库马尔。 回复：iMX8QXP I2C RPBUS 配置 嗨志明， 我们认为，一旦我们按照您的建议在 mek.h 文件中进行更改，问题就会得到解决。感谢您的支持。 如果出现任何其他问题，我们将与您核实。 问候， 兰吉斯·库马尔。 回复：iMX8QXP I2C RPBUS 配置 嗨志明， 我们在设计中使用了 2GiB 的 DRAM。您能否告诉我是否有任何更改地址的指南？ 问候， 兰吉斯·库马尔。 回复：iMX8QXP I2C RPBUS 配置 嗨志明， 除了 dts、defconfig 和 board 文件的更改之外，我们没有修改 U-boot 源代码。在 imx-mkimage 编译中，我们使用“flash_linux_m4”标志来使用 M4 启动，使用“flash”标志来不使用 M4 启动。 问候， 兰吉斯·库马尔。 回复：iMX8QXP I2C RPBUS 配置 嗨志明， 请在附件（dtsi.zip）中查找 dtsi 文件。 此致， 兰吉斯·库马尔。 回复：iMX8QXP I2C RPBUS 配置 嗨志明， 我们已经收到了目标板，当我使用 M4 启动目标板时，由于 rpmsg.dtsi 文件中只有一个 i2c 总线（映射到 mek.dtsi 文件中的 i2c1），我们面临来自 imx-rproc 驱动程序的内核恐慌，而当我使用没有 M4 的主板启动目标板时，启动没有问题。下面附上内核崩溃的日志。 请仔细研究一下并告诉我这个问题的 RCA 是什么。 问候， 兰吉斯·库马尔。 回复：iMX8QXP I2C RPBUS 配置 嗨志明， 谢谢支持。 问候， 兰吉斯·库马尔 回复：iMX8QXP I2C RPBUS 配置 嗨志明， 感谢您的详细澄清。 我的问题是，在我们的目标设备中，我们不会拥有 rpmsg.dtsi 文件中提到的任何从属设备，所以在这种情况下我们可以禁用所有 i2c_rpbus 节点吗？ 问候， 兰吉斯·库马尔 回复：iMX8QXP I2C RPBUS 配置 嗨志明， 谢谢你的信息。通过禁用 i2c_rpbus_5 中的从属设备，我们能够启动主板。 还有一个疑问，是否必须有 i2c_rpbus 节点，否则我们可以禁用所有 i2c_rpbus 节点及其相关的从属节点吗？ 此致， 兰吉斯·库马尔。 回复：iMX8QXP I2C RPBUS 配置 嗨志明， 请在附件（kernel_error_logs.txt）中查找内核启动日志。 此致， 兰吉斯·库马尔

T1024 以太网接口无法启动 大家好！ 我尝试为基于 t1024 的主板编译一个图像。为了进行构建，我使用了 Buildroot 工具和新内核 6.1.44。但以太网接口没有启动 ip a 显示接口列表 1: lo: mtu 65536 qdisc noqueue qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:00 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:01 brd ff:ff:ff:ff:ff:ff 4: eth2: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:02 brd ff:ff:ff:ff:ff:ff 5: eth3: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:03 brd ff:ff:ff:ff:ff:ff 6: tunl0@NONE: mtu 1480 qdisc noop qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: mtu 1480 qdisc noop qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 尝试 ip link set dev eth0 up 给我一个错误 fsl_dpaa_mac ffe4e0000.ethernet eth0: init_phy() failed 在启动日志期间我可以看到以下内容： mdio_bus 0x0000000ffe4fc000: MDIO device at address 2 is missing. mdio_bus 0x0000000ffe4fc000: MDIO device at address 6 is missing. mdio_bus 0x0000000ffe4fd000: MDIO device at address 1 is missing. mdio_bus 0x0000000ffe4fd000: MDIO device at address 2 is missing. platform ffe488000.port: Adding to iommu group 15 platform ffe489000.port: Adding to iommu group 16 platform ffe48a000.port: Adding to iommu group 17 platform ffe48b000.port: Adding to iommu group 18 fsl_dpaa_mac ffe4e0000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e0000.ethernet: FMan MAC address: 00:00:00:00:01:00 fsl_dpaa_mac ffe4e2000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e2000.ethernet: FMan MAC address: 00:00:00:00:01:01 fsl_dpaa_mac ffe4e4000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e4000.ethernet: FMan MAC address: 00:00:00:00:01:02 fsl_dpaa_mac ffe4e6000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e6000.ethernet: FMan MAC address: 00:00:00:00:01:03 fsl_dpaa_mac ffe4e0000.ethernet eth0: Probed interface eth0 fsl_dpaa_mac ffe4e2000.ethernet eth1: Probed interface eth1 fsl_dpaa_mac ffe4e4000.ethernet eth2: Probed interface eth2 fsl_dpaa_mac ffe4e6000.ethernet eth3: Probed interface eth3 是不是MDIO配置不正确？我使用来自内核源的设备树，Uboot 保留了之前的图像（内核版本 3.12.27）。我已将新的 rootfs、dtb 和 uImage 加载到 RAM 中并从那里运行。 ethtool 向我展示以下内容： ethtool eth0 Settings for eth0: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: Unknown! Duplex: Half Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: off MDI-X: Unknown Current message level: 0x00002037 (8247) drv probe link ifdown ifup hw Link detected: no 在 T1024 上使用以太网有什么技巧吗？ 我尝试从 QorIQ SDK 2.0 编译新图像，但是它有一个非常旧的工具并且因很多错误而停止。 QorIQ T1设备 回复：T1024 以太网接口无法启动 多谢。我已经解决了这个问题。

How to use Standby RAM in S32K3x? The S32K3x manual and RTD mention the memory allocation, specifically stating that 32KB of SRAM is designated as Standby RAM. Can someone please tell me how Standby RAM is utilized? What issues can arise if the space of Standby RAM is occupied while using SRAM? Re: How to use Standby RAM in S32K3x? Hi @Senlent  Thank you for your response to my post. I need to first understand the information you provided. If there are any questions, I will create additional subject for follow-up. Re: How to use Standby RAM in S32K3x? Hi@Chris-Sun the usage of Standby RAM can be find in the link below. https://community.nxp.com/t5/S32K-Knowledge-Base/S32K3-Low-Power-Management-AN-and-demos/ta-p/1527724

T1024 ehernet interface doesn't up Hi everyone! I've tried to compile an image for the t1024 based board. For the building I've used a Buildroot tools and fresh kernel 6.1.44. But ethernet interfaces doesn't up although ip a show me a list of interfaces 1: lo: mtu 65536 qdisc noqueue qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:00 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:01 brd ff:ff:ff:ff:ff:ff 4: eth2: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:02 brd ff:ff:ff:ff:ff:ff 5: eth3: mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:01:03 brd ff:ff:ff:ff:ff:ff 6: tunl0@NONE: mtu 1480 qdisc noop qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: mtu 1480 qdisc noop qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 trying ip link set dev eth0 up give me an error   fsl_dpaa_mac ffe4e0000.ethernet eth0: init_phy() failed During a boot log I can watch this: mdio_bus 0x0000000ffe4fc000: MDIO device at address 2 is missing. mdio_bus 0x0000000ffe4fc000: MDIO device at address 6 is missing. mdio_bus 0x0000000ffe4fd000: MDIO device at address 1 is missing. mdio_bus 0x0000000ffe4fd000: MDIO device at address 2 is missing. platform ffe488000.port: Adding to iommu group 15 platform ffe489000.port: Adding to iommu group 16 platform ffe48a000.port: Adding to iommu group 17 platform ffe48b000.port: Adding to iommu group 18 fsl_dpaa_mac ffe4e0000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e0000.ethernet: FMan MAC address: 00:00:00:00:01:00 fsl_dpaa_mac ffe4e2000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e2000.ethernet: FMan MAC address: 00:00:00:00:01:01 fsl_dpaa_mac ffe4e4000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e4000.ethernet: FMan MAC address: 00:00:00:00:01:02 fsl_dpaa_mac ffe4e6000.ethernet: FMan MEMAC fsl_dpaa_mac ffe4e6000.ethernet: FMan MAC address: 00:00:00:00:01:03 fsl_dpaa_mac ffe4e0000.ethernet eth0: Probed interface eth0 fsl_dpaa_mac ffe4e2000.ethernet eth1: Probed interface eth1 fsl_dpaa_mac ffe4e4000.ethernet eth2: Probed interface eth2 fsl_dpaa_mac ffe4e6000.ethernet eth3: Probed interface eth3 Is it true that the MDIO is not configured correctly?  I use a device tree from kernel source, Uboot has been kept from previous image (kernel version 3.12.27). I've loaded a new rootfs, dtb and uImage into ram and ran from there. ethtool show me the next: ethtool eth0 Settings for eth0: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: Unknown! Duplex: Half Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: off MDI-X: Unknown Current message level: 0x00002037 (8247) drv probe link ifdown ifup hw Link detected: no Is there some tricks to use ethernet on T1024? I tried to compile new image from QorIQ SDK 2.0, but it has a very old tools and stopped with a lot of errors. QorIQ T1 Devices Re: T1024 ehernet interface doesn't up Thanks a lot. I've solved the issue. Re: T1024 ehernet interface doesn't up Please modify the dts file arch/powerpc/boot/dts/fsl/t1024rdb.dts according to your custom board. Please modify "reg" values to your real PHY addresses at mdio@fc000  and mdio@fd000. fman@400000 { enet0: ethernet@e0000 { phy-handle = <&xg_aqr105_phy3>; phy-connection-type = "xgmii"; sleep = <&rcpm 0x80000000>; }; enet1: ethernet@e2000 { sleep = <&rcpm 0x40000000>; }; enet2: ethernet@e4000 { phy-handle = <&rgmii_phy2>; phy-connection-type = "rgmii"; sleep = <&rcpm 0x20000000>; }; enet3: ethernet@e6000 { phy-handle = <&rgmii_phy1>; phy-connection-type = "rgmii"; sleep = <&rcpm 0x10000000>; }; mdio0: mdio@fc000 { rgmii_phy1: ethernet-phy@2 { reg = <0x2>; }; rgmii_phy2: ethernet-phy@6 { reg = <0x6>; }; }; xmdio0: mdio@fd000 { xg_aqr105_phy3: ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c45"; reg = <0x1>; }; sg_2500_aqr105_phy4: ethernet-phy@2 { compatible = "ethernet-phy-ieee802.3-c45"; reg = <0x2>; }; }; };

Getting started and creating projects with Python Good morning, I would like to start working with Python for the MCXN947 board, creating my environment on VScode. On Vscode I installed the MCUXpresso extension and imported the sdk from github, but I see that they are all examples in c. How can I get started with Python? Are there examples for python too? Do I have to install MicroPython? Is there a step-by-step guide explaining what I need to do and how to start creating my own projects? Thank you Re: Getting started and creating projects with Python Hi @Transidico  1. The following link is Getting Started with FRDM-MCXN947. Getting Started with FRDM-MCXN947 | NXP Semiconductors 2. i.MX RT Series: The i.MX RT series, especially popular models like the i.MX RT1020, RT1050, and RT1060, supports MicroPython, which allows you to write Python code directly for the microcontroller. These chips have enough memory and performance to run MicroPython smoothly. BR Hang Re: Getting started and creating projects with Python Hi, thank you for your reply, could you please send me a quick guide on how to start a c project easily on the frdm-mcxn947 board? I also ask you which micro family using MCUXpresso is compatible with python. thank you very much. Regards Re: Getting started and creating projects with Python Hi @Transidico  unfortunately, the MCXN947 board is typically programmed in C/C++ with the MCUXpresso SDK, so Python-based development options are limited. You may need to adapt MicroPython’s general instructions to your board, as there’s no official guide tailored to MCXN947. BR Hang

Pythonを使用したプロジェクトの開始と作成 おはようございます 私はMCXN947ボードのPythonで作業を開始し、VScodeで環境を作成したいと思います。Vscodeでは、MCUXpresso拡張機能をインストールし、githubからsdkをインポートしましたが、それらはすべてcの例であることがわかります。 Pythonを使い始めるにはどうすればいいですか?Pythonの例もありますか?MicroPythonをインストールする必要がありますか? 何をする必要があるのか、どのように自分のプロジェクトを作成するのかを説明するステップバイステップのガイドはありますか? よろしくお願い申し上げます。

Recommended JTAG IMX8MPlus EVK Hello, Just received my iMX8MPlus EVK and I was wondering what is the recommended JTAG proble that allows me low level board bring up.  For example DDR4 setup, and loading U-boot and Fit Image sirectly into DDR. Thank you. Re: Recommended JTAG IMX8MPlus EVK Hello, We suggest Segger JTAG for debug and Download the images to you board. https://www.segger.com/supported-devices/nxp/i-mx-8m-plus regards

使用 Python 入门和创建项目 早上好， 我想开始使用 Python 为 MCXN947 板工作，并在 VScode 上创建我的环境。在 Vscode 上我安装了 MCUXpresso 扩展并从 github 导入了 sdk，但我发现它们都是 c 语言中的示例。 我如何开始使用 Python？还有 Python 的例子吗？我必须安装 MicroPython 吗？ 是否有分步指南解释我需要做什么以及如何开始创建自己的项目？ 谢谢

RT1020 ADC issues The design I'm using is using ADC2 channel 3. This ADC pin does not work correctly. To double check if there was a design issue, when this pin is used on the MIMXRT1020-EVK it still does not work. R249 and R251 are removed so that it is not connected to a pull up. The behavior I see is it appears to be pulled up and increases up to and stays at a value of ~2700. A square wave running at 1khz from an oscilloscope is put onto the header at J19 pin 10. This input is used on J18 pin 1 when using channel 10. I used the evkmimxrt1020_adc_12b1msps_sar_interrupt example from the sdk as it most closely represents the settings I'm using in my design.  This is the config I used with the sdk: #define DEMO_ADC_BASE ADC2 #define DEMO_ADC_IRQn ADC2_IRQn #define DEMO_ADC_USER_CHANNEL 3U #define DEMO_ADC_CHANNEL_GROUP 0U #define EXAMPLE_ADC_IRQHandler ADC2_IRQHandler Pin configuration with the pins tool for [90] GPIO_AD_B1_02: Peripheral: ADC2 Signal: IN, 3 Slew Rate: Slow Software Input On: Disabled Open Drain: Disabled Speed: Medium Drive Strength: RO/6 Pull/Keeper select: Keeper Pull/Keeper enable: Disabled Pull Up/Down Config: 100k Ohm Pull Down Hysteresis: Disable Using [90] GPIO_AD_B1_10 with the same configuration above, but for signal IN, 10 works. The only change in software is made to: DEMO_ADC_USER_CHANNEL 10U Both pins are enabled for the test but only one is used at a time. I tried many settings to get some sort of response from the pin, but it never returns a reasonable value. In ADC_Init, I added this above "base->CFG = tmp32;" and tested all of the values for the averaging: // kADC_HardwareAverageCount4 = 0U, /*!< For hardware average with 4 samples. */ // kADC_HardwareAverageCount8 = 1U, /*!< For hardware average with 8 samples. */ // kADC_HardwareAverageCount16 = 2U, /*!< For hardware average with 16 samples. */ // kADC_HardwareAverageCount32 = 3U, /*!< For hardware average with 32 samples. */ // kADC_HardwareAverageDiasable = 4U, /*!< Disable the hardware average function. */ tmp32 |= ADC_CFG_AVGS(kADC_HardwareAverageCount8); base->CFG = tmp32; I did this with and without enabling averaging to try and find one working setting: tmp32 |= ADC_GC_AVGE_MASK; base->GC = tmp32; I'm looking for a way to get this pin working and would appreciate any help! MCUXPresso 11.9.0 SDK 2.15.0 Problem occurs with the MIMXRT1020-EVK board as well as the MIMXRT1021DAG5A chip in the design.   i.MXRT 102x Re: RT1020 ADC issues Got the SD mixed up with the AD signal bank. Thanks! Re: RT1020 ADC issues Hi @joshgentrycargt , Thank you for your updated information. I down load your project, and add print information, ADC2 channel3 work normal. ADC2 channel3 connect AREF. ADC2 channel3 connect GND. Please be aware that ADC2 channel3 PIN is PIN90（GPIO_AD_B1_02）, This pin is not connect to  J19 pin 10(GPIO_SD_B1_02).  I connect one end of resistor R85(Connect PIN90) with a wire harness, and the other end to GND or AREF. Wish it helps you. If you still have question about it, please kindly let me know. Best Regards mayliu Re: RT1020 ADC issues I made your changes to this project and still see the same results. Attached is my workspace. I also attached a version of adc_interrupt.c that fills a buffer instead of using getchar. I'm using a mag wire connected to J19 pin 10 to drive ADC2 channel 3. Re: RT1020 ADC issues Hi  , Thank you for your interest in the NXP MIMXRT product, I would  like to provide service for you. I used the MIMXRT1020-EVK board to verify ADC1 channel 0 and ADC2 channel 3, and the ADC conversion results are normal without any issues. 1：Please open the Pins  Tool, and Set ADC2 channel3, and click Update Code button. 2:  In the Project " evkmimxrt1020_adc_12b1msps_sar_interrupt" Please add code as what I do. The image below shows the results of my validation. Wish it helps you. If you still have question about it, please kindly let me know. Best Regards mayliu

i.MX 8M Plus docker が機能しない "無効なホスト ヘッダー" こんにちは i.MX 8M Plus EVK ボードでは、リンク https://github.com/nxp-imx/meta-imx/tree/mickledore-6.1.55-2.2.0 の mickledore ブランチ "mickledore-6.1.55-2.2.0" から yocto ソースを構築します。 EVKボードでイメージをビルドしてフラッシュした後、Dockerが機能していないことがわかりました。以下のコマンドを次のように実行します。 root@imx8mpevk:~# uname -a リナックス imx8mpevk 6.1.55+g770c5fe2c1d1#1 SMP PREEMPT 11月21日(火) 23:45:58 UTC 2023 aarch64 GNU/Linux root@imx8mpevk:~# root@imx8mpevk:~# systemctl start docker root@imx8mpevk:~# root@imx8mpevk:~# docker pull hello-world デフォルトタグの使用: latest latest: library/hello-world からプルしています ダイジェスト: sha256:a26bff933ddc26d5cdf7faa98b4ae1e3ec20c4985e6f87ac0973052224d24302 ステータス: hello-world:latest のイメージは最新です docker.io/library/hello-world:latest root@imx8mpevk:~# root@imx8mpevk:~# docker run hello-world http: 無効な Host ヘッダー root@imx8mpevk:~# また、dockerについては以下のjournalctlログも参照してください。 root@imx8mpevk:~# journalctl -xefu docker Apr 24 12:23:20 imx8mpevk systemd[1]: Docker Application Container Engine を起動しています... -- 件名: ユニット docker.service の開始ジョブが実行を開始しました -- 定義者: systemd -- サポート: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- ユニット docker.service の開始ジョブが実行を開始しました。 -- -- ジョブ ID は 1630 です。 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.465195235Z"level=info msg="起動中" 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.471783509Z"level=info msg="[コア] [チャンネル #1] チャンネル作成" module=grpc 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.471879134Z"level=info msg="[core] [チャンネル #1] 元のダイヤルターゲット: \"unix:///run/containerd/coc 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.472032885Z"level=info msg="[core] [チャネル #1] 解析されたダイヤルターゲット: {Scheme:unix Authority: Endpoc 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.472097885Z"level=info msg="[コア] [チャネル #1] チャネル権限を \"localhost\"" に設定 module=grpc 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.472945263Z"level=info msg="[core] [チャンネル #1] リゾルバの状態が更新されました: {\n \"Addresses\": [\n {c 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.476382650Z"level=info msg="[core] [チャンネル #1] チャンネルが新しいLBポリシー\"pick_first\"" mocに切り替わります 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.479532287Z"level=info msg="[コア] [チャンネル #1 サブチャンネル #2] サブチャンネルが作成されました" module=grpc 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.479762788Z"level=info msg="[core] [チャンネル #1 サブチャンネル #2] サブチャンネル接続を CONNc に変更 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.479931288Z"level=info msg="[core] [チャンネル #1 サブチャンネル #2] サブチャンネルが新しいアドレスを選択します \"/run/c 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.480056039Z"level=info msg="[コア] [チャンネル #1] チャンネル接続を CONNECTING に変更" module=grc 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.488533820Z"level=info msg="[core] [チャンネル #1 サブチャンネル #2] サブチャンネル接続を READc に変更 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.488714945Z"level=info msg="[コア] [チャンネル #1] チャンネル接続がREADYに変更" module=grpc 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.496465474Z"level=info msg="[コア] [チャンネル #4] チャンネル作成" module=grpc 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.496565849Z"level=info msg="[core] [チャンネル #4] 元のダイヤルターゲットは: \"unix:///run/containerd/coc 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.496669974Z"level=info msg="[core] [Channel #4] 解析されたダイヤルターゲット: {Scheme:unix Authority: Endpoc 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.496746725Z"level=info msg="[コア] [チャネル #4] チャネル権限を \"localhost\"" に設定しました。" module=grpc 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.496911225Z"level=info msg="[core] [チャンネル #4] リゾルバの状態が更新されました: {\n \"Addresses\": [\n {c 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.497074476Z"level=info msg="[core] [チャンネル #4] チャンネルが新しいLBポリシー\"pick_first\"" mocに切り替わります 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.497270102Z"level=info msg="[core] [チャンネル #4 サブチャンネル #5] サブチャンネルが作成されました" module=grpc 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.497479852Z"level=info msg="[core] [チャンネル #4 サブチャンネル #5] サブチャンネル接続を CONNc に変更 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.497737228Z "level=info msg="[core] [チャンネル #4 サブチャンネル #5] サブチャンネルは新しいアドレスを選択します \"/run/c 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.497770104Z"level=info msg="[コア] [チャンネル #4] チャンネル接続を CONNECTING に変更" module=grc 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.498877358Z"level=info msg="[core] [チャネル #4 サブチャネル #5] サブチャネル接続を READc に変更 4月24日12:23:21 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:21.499128733Z"level=info msg="[コア] [チャンネル #4] チャンネル接続が READY に変更" module=grpc 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.597137716Z"level=info msg="コンテナのロード中: 開始します。" 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.881553755Z"level=warning msg="IPSEC ルールに必要なモジュールを読み込めませんでした: プロトコルがサポートされていません" 4月24日12:23:21 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:21.893731300Z"level=info msg="デフォルトのブリッジ (docker0) には IP アドレス 172.17.0.0/16 が割り当てられています。D" 4月24日12:23:22 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:22.029149067Z"level=info msg="コンテナをロードしています: 完了しました。" 4月24日12:23:22 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:22.246174432Z"level=warning msg="警告: cpu cfs quota サポートがありません" 4月24日12:23:22 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:22.246261186Z"level=warning msg="警告: CPU cfs期間のサポートはありません" 4月24日12:23:22 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:22.246296437Z"level=warning msg="警告: blkio throttle.read_bps_deviceはありませんサポート" 4月24日12:23:22 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:22.246344064Z"level=warning msg="警告: blkio throttle.write_bps_deviceはありませんサポート" 4月24日12:23:22 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:22.246379941Z"level=warning msg="警告: blkioのthrottle.read_iops_deviceはありませんサポート" 4月24日12:23:22 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:22.246413692Z"level=warning msg="警告: blkioのthrottle.write_iops_deviceはありませんサポート" 4月24日12:23:22 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:22.246501321Z"level=info msg="Dockerデーモン" commit=219f21bf07502b447095649b5a2764661737f164 graphdrive 4月24日12:23:22 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:22.247150101Z"level=info msg="デーモンが初期化を完了しました" 4月24日12:23:22 imx8mpevk dockerd [1393]:time =" 2024-04-24T12:23:22.323320938Z"level=info msg="[コア] [サーバ #7] サーバが作成されました" module=grpc Apr 24 12:23:22 imx8mpevk systemd[1]: Docker Application Container Engine を開始しました。 -- 件名: ユニット docker.service の開始ジョブが正常に終了しました -- 定義者: systemd -- サポート: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- ユニット docker.service の開始ジョブが正常に終了しました。 -- -- ジョブ ID は 1630 です。 4月24日12:23:22 imx8mpevk dockerd [1393]:time = "2024-04-24T12:23:22.347791050Z"level=info msg="API listen on /run/docker.sock" (/run/docker.sock で API listen ) ^C root@imx8mpevk:~# ご意見をお聞かせください 感謝 Re:i.MX 8M Plusドッカーが機能しない「無効なホストヘッダー」 こんにちは ダウングレード後、パッケージに行きます。Dockerは正常に動作しています。 リンク先: https://github.com/moby/moby/issues/46614#issuecomment-1757751921 感謝

i.MX 8M Plus docker not working " invalid Host header" Hi, For our i.MX 8M Plus EVK board , we build yocto source from mickledore branch "mickledore-6.1.55-2.2.0"  from link https://github.com/nxp-imx/meta-imx/tree/mickledore-6.1.55-2.2.0 . After build and  flashing image in EVK board , we found docker is not working. below commands as follow. root@imx8mpevk:~# uname -a Linux imx8mpevk 6.1.55+g770c5fe2c1d1 #1 SMP PREEMPT Tue Nov 21 23:45:58 UTC 2023 aarch64 GNU/Linux root@imx8mpevk:~# root@imx8mpevk:~# systemctl start docker root@imx8mpevk:~# root@imx8mpevk:~# docker pull hello-world Using default tag: latest latest: Pulling from library/hello-world Digest: sha256:a26bff933ddc26d5cdf7faa98b4ae1e3ec20c4985e6f87ac0973052224d24302 Status: Image is up to date for hello-world:latest docker.io/library/hello-world:latest root@imx8mpevk:~# root@imx8mpevk:~# docker run hello-world http: invalid Host header root@imx8mpevk:~# Also please refer below journalctl log for docker. root@imx8mpevk:~# journalctl -xefu docker Apr 24 12:23:20 imx8mpevk systemd[1]: Starting Docker Application Container Engine... -- Subject: A start job for unit docker.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit docker.service has begun execution. -- -- The job identifier is 1630. Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.465195235Z" level=info msg="Starting up" Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.471783509Z" level=info msg="[core] [Channel #1] Channel created" module=grpc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.471879134Z" level=info msg="[core] [Channel #1] original dial target is: \"unix:///run/containerd/coc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.472032885Z" level=info msg="[core] [Channel #1] parsed dial target is: {Scheme:unix Authority: Endpoc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.472097885Z" level=info msg="[core] [Channel #1] Channel authority set to \"localhost\"" module=grpc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.472945263Z" level=info msg="[core] [Channel #1] Resolver state updated: {\n \"Addresses\": [\n {c Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.476382650Z" level=info msg="[core] [Channel #1] Channel switches to new LB policy \"pick_first\"" moc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.479532287Z" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel created" module=grpc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.479762788Z" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.479931288Z" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel picks a new address \"/run/c Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.480056039Z" level=info msg="[core] [Channel #1] Channel Connectivity change to CONNECTING" module=grc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.488533820Z" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel Connectivity change to READc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.488714945Z" level=info msg="[core] [Channel #1] Channel Connectivity change to READY" module=grpc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.496465474Z" level=info msg="[core] [Channel #4] Channel created" module=grpc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.496565849Z" level=info msg="[core] [Channel #4] original dial target is: \"unix:///run/containerd/coc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.496669974Z" level=info msg="[core] [Channel #4] parsed dial target is: {Scheme:unix Authority: Endpoc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.496746725Z" level=info msg="[core] [Channel #4] Channel authority set to \"localhost\"" module=grpc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.496911225Z" level=info msg="[core] [Channel #4] Resolver state updated: {\n \"Addresses\": [\n {c Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.497074476Z" level=info msg="[core] [Channel #4] Channel switches to new LB policy \"pick_first\"" moc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.497270102Z" level=info msg="[core] [Channel #4 SubChannel #5] Subchannel created" module=grpc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.497479852Z" level=info msg="[core] [Channel #4 SubChannel #5] Subchannel Connectivity change to CONNc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.497737228Z" level=info msg="[core] [Channel #4 SubChannel #5] Subchannel picks a new address \"/run/c Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.497770104Z" level=info msg="[core] [Channel #4] Channel Connectivity change to CONNECTING" module=grc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.498877358Z" level=info msg="[core] [Channel #4 SubChannel #5] Subchannel Connectivity change to READc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.499128733Z" level=info msg="[core] [Channel #4] Channel Connectivity change to READY" module=grpc Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.597137716Z" level=info msg="Loading containers: start." Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.881553755Z" level=warning msg="Could not load necessary modules for IPSEC rules: protocol not suppor" Apr 24 12:23:21 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:21.893731300Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. D" Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.029149067Z" level=info msg="Loading containers: done." Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.246174432Z" level=warning msg="WARNING: No cpu cfs quota support" Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.246261186Z" level=warning msg="WARNING: No cpu cfs period support" Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.246296437Z" level=warning msg="WARNING: No blkio throttle.read_bps_device support" Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.246344064Z" level=warning msg="WARNING: No blkio throttle.write_bps_device support" Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.246379941Z" level=warning msg="WARNING: No blkio throttle.read_iops_device support" Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.246413692Z" level=warning msg="WARNING: No blkio throttle.write_iops_device support" Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.246501321Z" level=info msg="Docker daemon" commit=219f21bf07502b447095649b5a2764661737f164 graphdrive Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.247150101Z" level=info msg="Daemon has completed initialization" Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.323320938Z" level=info msg="[core] [Server #7] Server created" module=grpc Apr 24 12:23:22 imx8mpevk systemd[1]: Started Docker Application Container Engine. -- Subject: A start job for unit docker.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit docker.service has finished successfully. -- -- The job identifier is 1630. Apr 24 12:23:22 imx8mpevk dockerd[1393]: time="2024-04-24T12:23:22.347791050Z" level=info msg="API listen on /run/docker.sock" ^C root@imx8mpevk:~# Please share your inputs Thanks Re: i.MX 8M Plus docker not working " invalid Host header" Hi After downgrading go package. docker working fine . refer link : https://github.com/moby/moby/issues/46614#issuecomment-1757751921 Thanks

sha256sum to secure file system update Hello, Recently I have been thinking about a way to keep the integrity of my file system and how to manage this issue after a file system update in my iMX93 EVK. To clarify, let's assume the following eMMC partition: /dev/mmbclk1boot0 -> bootloader /dev/mmbclk1p1 -> FIT image /dev/mmcblk1p2 -> rootFS_one /dev/mmcblk1p3 -> rootFS_two /dev/mmcblk1p4 -> hash_one /dev/mmcblk1p5 -> hash_two The thing is as follows, now I have the bootaloader and the FIT image (with initramfs) secured. So now I am trying to secure the file system. My idea is to use two partitions to store two file systems (/dev/mmcblk1p2 and /dev/mmcblk1p3), in a normal operation one of them is mounted and when an update must be asserted the new content is stored in the other partition. Once the update has been completed the system resets and the updated file system is mounted (and both partitions exchange roles for the next update). Now, the integrity of both file systems is an issue. The idea is to check the integrity of the file system that is going to be mounted during initramfs. My idea is as follows, when the filesystem of /dev/mmcblk1p2 is running (initramfs has mounted this partition previously) the /dev/mmcblk1p3 is updated. Then a hash is calculated from /dev/mmcblk1p3 using sha256sum utility from coreutils. This hash is then signed with a private key and the result is stored in /dev/mmcblk1p5. After a reset the initramfs will read the hash stored in /dev/mmcblk1p5, decrypt it with a public key (inmutable since FIT image is secured by bootloader) and compared with the calcualted hash of /dev/mmcblk1p3. If everything is okey then the system boots from /dev/mmcblk1p3. This process also ocurrs from the second file system to fist one (I won't explain it again, I think that it is clear). I have two questions regarding my idea. Is sha256sum utility suitable for this application (to secure file system)? (I plan to use sha256 over dm-verity or ima since it is much easier to implement). How can I protect the private key that file systems use to sign the hash? Does iMX93 provide some utility to safely store keys? (This question is a little bit rhetoric since I know about the ELE but don't know how to use it). Regards, Gorka. Re: sha256sum to secure file system update Hello, Your use case seems doable, so I would say that it looks fine For the secure ELE, you may request access to the documentation here: https://www.nxp.com/webapp/Download?colCode=IMX93ELEAPI&appType=moderatedWithoutFAE Best regards/Saludos, Aldo.

GUI Guiderを使用してbinファイルフォントを生成するにはどうすればよいですか? こんにちは あなたが私を助けることができるかどうか尋ねてもよろしいですか:GUI Guiderでは、フォントのみをCファイルとして生成できることがわかりました、binファイルフォントを生成するオプションを追加できますか? 現在、LVGL公式サイトでBINファイルを生成することができますが、GUI Guiderで生成したプロジェクトに移植すると、フォントの高さ表示に一貫性がなくなる場合がありますので、解決策がないか聞いてみてもいいですか。 次のバージョンでは、binファイルのフォントを生成するツールを追加したいと考えています。 感謝！ Re:GUI Guiderを使用してbinファイルフォントを生成する方法は? ご回答ありがとうございます。 この機能が将来のバージョンで実装されると、XIP FLASHに画像バイナリのようなフォントバイナリを保存でき、ソフトウェアコードを更新するたびにバイナリを更新する必要がなくなり、プログラムの更新時間を大幅に節約できます。

Reading i.MX8MM register values with sdphost I am trying to find a way to read register values from a i.MX8MM over USB. The tool sdphost should be able to do it, but I am not able to get it to work and I cannot find sufficient instructions anywhere. For example, I want to try and read OCOTP_HW_OCOTP_BOOT_CFG0 which should be at memory address 3035_0470: ./sdphost -u 0x1fc9,0x0134 read-register 0x30350470 33 22 33 00 Status (HAB mode) = 305411090 (0x12343412) HAB enabled. But the bytes (33 22 33 00) are not correct. In fact, no matter what address I give sdphost, it always returns the same four bytes. I know the device is connected and in Serial Download Mode, because I can for example use uuu. What is the correct command to read register values with sdphost? Bonus question: is there any way to read registers with uuu? We already use uuu to flash the device and write fuses, it would be handy to use the same tool for reading registers as well. But I looked at sdphost because it did not seem to be possible with uuu. i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Reading i.MX8MM register values with sdphost Is there any tool available for reading register values over USB? Re: Reading i.MX8MM register values with sdphost Hello, According to the documentation: Serial Download Protocol is a set of commands supported by NXP i.MX RT devices in the Boot ROM application’s serial download mode. I tried on our EVK and also is giving faulty readings. So, I think this tool is not intended to be used on i.MX families as is on i.MX RT families. Also, in the case of UUU, there is no documented a command to read registers on the board. Best regards.

i.MX 8M Plus docker 无法正常工作“无效主机头” 你好， 对于我们的 i.MX 8M Plus EVK 板，我们从链接https://github.com/nxp-imx/meta-imx/tree/mickledore-6.1.55-2.2.0中的 mickledore 分支“mickledore-6.1.55-2.2.0”构建 yocto 源。 在 EVK 板上构建并刷新图像后，我们发现 docker 不起作用。以下命令如下。 root@imx8mpevk:~# uname -a Linux imx8mpevk 6.1.55+g770c5fe2c1d1#1 SMP PREEMPT 11 月 21 日星期二 23:45:58 UTC 2023 aarch64 GNU/Linux root@imx8mpevk:~# root@imx8mpevk:~# systemctl 启动docker root@imx8mpevk:~# root@imx8mpevk:~#docker pull hello-world 使用默认标签：最新 最新：从 library/hello-world 中提取 摘要：sha256：a26bff933ddc26d5cdf7faa98b4ae1e3ec20c4985e6f87ac0973052224d24302 状态：图像已针对 hello-world:latest 更新 docker.io/library/hello-world:latest root@imx8mpevk:~# root@imx8mpevk:~#docker运行hello-world http：无效的主机头 root@imx8mpevk:~# 另请参阅下面的 docker journalctl 日志。 root@imx8mpevk:~# journalctl -xefu docker 4月24日 12:23:20 imx8mpevk systemd[1]:正在启动 Docker 应用程序容器引擎... -- 主题：docker.service 单元的启动作业已开始执行 -- 定义者：systemd -- 支持： https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- 单元 docker.service 的启动作业已开始执行。 -- -- 作业标识符为 1630。 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.465195235Z”level=info msg="正在启动" 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.471783509Z”level=info msg="[core] [Channel #1] 频道已创建" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.471879134Z”level=info msg="[core] [通道#1] 原始拨号目标是：\"unix:///run/containerd/coc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.472032885Z”level=info msg="[core] [Channel #1] 解析的拨号目标是：{Scheme:unix Authority: Endpoc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.472097885Z”level=info msg="[core] [频道 #1] 频道权限设置为 \"localhost\"" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.472945263Z”level=info msg="[核心] [通道 #1] 解析器状态已更新: {\n \"地址\": [\n {c 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.476382650Z”level=info msg="[core] [频道 #1] 频道切换到新的 LB 策略 \"pick_first\"" moc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.479532287Z”level=info msg="[core] [频道 #1 子频道 #2] 子频道已创建" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.479762788Z”level=info msg="[core] [Channel #1 SubChannel #2] 子通道连接更改为 CONNc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.479931288Z”level=info msg="[core] [通道 #1 子通道 #2] 子通道选择一个新地址 \"/run/c 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.480056039Z”level=info msg="[core] [通道 #1] 通道连接状态更改为 CONNECTING" module=grc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.488533820Z”level=info msg="[core] [Channel #1 SubChannel #2] 子通道连接更改为 READc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.488714945Z”level=info msg="[core] [Channel #1] 通道连接更改为 READY" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.496465474Z”level=info msg="[core] [Channel #4] 频道已创建" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.496565849Z”level=info msg="[core] [通道#4] 原始拨号目标是：\"unix:///run/containerd/coc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.496669974Z”level=info msg="[core] [Channel #4] 解析的拨号目标是: {Scheme:unix Authority: Endpoc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.496746725Z”level=info msg="[core] [频道 #4] 频道权限设置为 \"localhost\"" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.496911225Z”level=info msg="[核心] [通道 #4] 解析器状态已更新: {\n \"地址\": [\n {c 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.497074476Z”level=info msg="[core] [频道 #4] 频道切换到新的 LB 策略 \"pick_first\"" moc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.497270102Z”level=info msg="[core] [频道 #4 子频道 #5] 子频道已创建" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.497479852Z”level=info msg="[core] [Channel #4 SubChannel #5] 子通道连接更改为 CONNc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.497737228Z”level=info msg="[core] [通道 #4 子通道 #5] 子通道选择一个新地址 \"/run/c 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.497770104Z”level=info msg="[core] [通道 #4] 通道连接更改为 CONNECTING" module=grc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.498877358Z”level=info msg="[core] [Channel #4 SubChannel #5] 子通道连接更改为 READc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.499128733Z”level=info msg="[core] [Channel #4] 通道连接更改为 READY" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.597137716Z”level=info msg="正在装载容器：开始。" 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.881553755Z”level=warning msg="无法加载 IPSEC 规则所需的模块：协议不支持" 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.893731300Z”level=info msg="默认网桥（docker0）分配了IP地址172.17.0.0/16。D” 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.029149067Z”level=info msg="装载容器：完成。" 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246174432Z”level=warning msg="警告：不支持 CPU CFS 配额" 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246261186Z”level=warning msg="警告：不支持 CPU CFS 周期" 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246296437Z”level=warning msg="警告：没有 blkio throttle.read_bps_device支持” 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246344064Z”level=warning msg="警告：没有 blkio throttle.write_bps_device支持” 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246379941Z”level=warning msg="警告：没有 blkio throttle.read_iops_device支持” 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246413692Z”level=warning msg="警告：没有 blkio throttle.write_iops_device支持” 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246501321Z”级别=信息消息=“Docker守护进程”提交=219f21bf07502b447095649b5a2764661737f164 graphdrive 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.247150101Z”level=info msg="守护进程已完成初始化" 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.323320938Z”level=info msg="[core] [Server #7] 服务器已创建" module=grpc 4 月 24 日 12:23:22 imx8mpevk systemd[1]:已启动 Docker 应用程序容器引擎。 -- 主题：docker.service 单元的启动作业已成功完成 -- 定义者：systemd -- 支持： https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- 单元 docker.service 的启动作业已成功完成。 -- -- 作业标识符为 1630。 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.347791050Z”level=info msg="API 监听 /run/docker.sock" ^C root@imx8mpevk:~# 请分享您的意见 谢谢 回复：i.MX 8M Plus docker 无法正常工作“无效的主机头” 你好 降级 go 包后。docker 工作正常。 参考链接： https ://github.com/moby/moby/issues/46614#issuecomment-1757751921 谢谢

How to use GUI Guider to generate bin file fonts? Hello, may I ask if you could help me: In GUI Guider,I found that only fonts can be generated as C files,Can you add an option to generate bin file fonts?  At present, BIN files can be generated on the LVGL official website, but when ported to the project generated by GUI Guider, there may be inconsistent font height display issues,May I ask if there is a solution. I hope to add a tool for generating bin file fonts in the next version! Thanks! Re: How to use GUI Guider to generate bin file fonts? Thanks for your answer. If this feature is implemented in future versions, I will be able to store the fonts binary like images binary in XIP FLASH and not have to update the binary every time when updating software code, which will greatly save program update time. Re: How to use GUI Guider to generate bin file fonts? Hi @White1, This is a great suggestion. I will share this idea internally with the GUI Guider team. In the end, it is up to them to see if this feature is worth implementing on future releases of GUI Guider, but I believe it would be a great addition to the tool! Thanks for your suggestions. BR, Edwin.