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.

Confusing state diagram in AN14145 - Flash Memory Swap Features on MCX N Series Looking at AN14145 and Figure 2, I am somewhat confused about the error cases when the attempt to run the first "logical" image does not boot. I.e. the diagram gives this possible execution order: Is there a second image file? Yes Whether second image version is greater than first?  No Start first image Startup successful? No Start second image Startup successful?  Yes Run first image The last state should be "Run second image". The same problem exists on the symmetric case when the second image should be tested first and does not boot. I know, it's kind of cosmetic, but its really confusing.  Would be good to fix this in the document. Thanks in advance! https://www.nxp.com/webapp/Download?colCode=AN14145 Boot ROM|Booting | Flash MCXN Re: Confusing state diagram in AN14145 - Flash Memory Swap Features on MCX N Series Hi Omar, thanks for passing on my feedback to the right team.  I appreciate that! Best wishes  Detlev Re: Confusing state diagram in AN14145 - Flash Memory Swap Features on MCX N Series Thank you for your feedback!  I will inform this suggestion to the corresponding team so it is considered.  Best regards, Omar Re: Confusing state diagram in AN14145 - Flash Memory Swap Features on MCX N Series Ah, I just looked at the latest available version of this document, and it is still the same, e.g. my suggestion was not included into the document 😭 As it takes time to post such suggestions, this limits my willingness to spend such time in the future. To be honest, I think this is sad and not a good way to encourage a community.

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.

如何使用GUI Guider生成bin文件字体？ 你好， 请问您是否可以帮助我：在 GUI Guider 中，我发现只有字体可以生成为 C 文件，您能添加一个选项来生成 bin 文件字体吗？ 目前在LVGL官网可以生成BIN文件，但是移植到GUI Guider生成的项目中可能会出现字体高度显示不一致的问题，请问有没有什么解决办法。 希望下个版本能增加生成bin文件字体的工具！ 谢谢！ 回复：如何使用 GUI Guider 生成 bin 文件字体？ 谢谢你的回答。 如果在未来的版本中实现这个功能，我将能够将字体二进制文件像图像二进制文件一样存储在XIP FLASH中，而不必在每次更新软件代码时更新二进制文件，这将大大节省程序更新时间。

K32L2A SWD 引脚 - 除非连接调试器，否则 MCU 无法正常运行 我有一个使用 K32L2A 的新设计，这是旧 Coldfirev1 MCF51QE32 部件的未分级设计。使用原型 PCB，软件在连接 PEMicro Cyclone 的情况下按预期运行，即使不使用该设备进行调试，只需启动设备，MCU 即可按预期运行我们的软件。 然而，当 Cyclone 与电路板断开连接时，MCU 似乎会短暂启动，然后自行关闭（不会按预期运行我们的软件，不确定它是否只是停止，或者是什么，因为我无法将 Cyclone 连接到调试，因为这会立即修复它！）。我们的设计在 SWDIO/SWCLK 线路上没有外部电阻，因为数据表提到这些电阻是由 K32L2A 内部提供的（MCF51QE 在 PCB 上有 10K 上拉电阻）。 尝试过的事情： - 在这两条线路上添加 10K 上拉电阻 - 问题仍然存在 - 将一根电线从 PCB 上取下，这样我就可以将导线接触到引脚，这样就可以解决问题，也就是说，当我用手指捏住连接到 SWDIO 引脚的导线并启动电路板时，MCU 可以正确启动并且我们的软件可以运行。它会一直运行，直到我移开手指。这与任一 SWD 引脚均可兼容。电容？我不知道！？！ 在这些行上加一个小写字母似乎是一种黑客行为，显然我忽略了一些东西。 复位线上也没有外部电阻（疏忽）但这似乎不是问题，因为当我握住其中一个 SWD 引脚时 MCU 就会运行，而当我离开一个引脚时 MCU 就会失败。 想法、希望还是抱负？欢迎大家 🙂 干杯！ 回复：K32L2A SWD 引脚 - 除非连接调试器，否则 MCU 无法正常运行 “在两条线路上都添加 10K 上拉电阻 - 问题仍然存在” SWD_DIO 具有内部上拉电阻。SWD_CLK 具有内部下拉。 猜测，重置时将两者都拉高可能看起来像是调试器时钟脉冲。手指等会拉下足够长的时间。 内部电阻相当高 Z 并且随温度而变化（20k 至 50k）。 我通常会添加自己的低 Z。 来自 K32L2A 的电气数据表： “虽然不需要上拉或下拉电阻 （SWD_DIO 具有内部上拉电阻，SWD_CLK 具有内部下拉电阻），建议使用外部 10 kΩ 上拉电阻以确保系统稳健性。这 还必须考虑上面提到的 RESET_b 引脚建议。”

HID(W):LIBUSB_ERROR_PIPE ----i.mx9352 A1 Hi, We am using i.mx9352 A1 model. we are unable to port the BSP file due to some error is coming as given below ======================================================= Success 0 Failure 1 1:2 1/ 1 [HID(W):LIBUSB_ERROR_PIPE ] SDPS: boot -f imx-boot-imx93evk-sd.bin-flash_singleboot ============================================================================= Could you provide solution for that error Thanks, Vivek Re: HID(W):LIBUSB_ERROR_PIPE ----i.mx9352 A1 Hi @Binh_Hoang  Kindly check the voltage as per Table 29 of NXP hardware design guide and check  the VDD_SOC_0V8 at SOC end. Thanks Re: HID(W):LIBUSB_ERROR_PIPE ----i.mx9352 A1 Hi @vivek5676, I'm facing the same issue. Could you please let me know which change is needed for this case? Please give me more details.  Thank you in advance, Binh Re: HID(W):LIBUSB_ERROR_PIPE ----i.mx9352 A1 My problem get resolved after changes done in hardware.  

i.MX8M Plus: IOMUX CTS/RTS directions are reversed Hello, We are having some issues related to the UART4 in a i.MX8M Plus After some investigation, it seems that the IOMUX CTS/RTS directions are reversed (in DCE and DTE mode). In the figure below: TX/RX in both cases are output/input and matches the diagram in the center-right. However, CTS/RTS in both cases are input/output but that doesn't match the diagram. Contrast this with the second image below based on a i.MX6. CTS/RTS are output/input as expected. Is this analysis correct? Where are we wrong? What can we do to correct this? Thank you. Best regards, Adriano Carvalho Re: i.MX8M Plus: IOMUX CTS/RTS directions are reversed Hello, It is an issue with the tool, is not showing the correct signals direction. Best regards. Re: i.MX8M Plus: IOMUX CTS/RTS directions are reversed Hello, Is this just an issue with the tool where it display "input" when it should display "output" and vice versa? Or are the dts files affected as well? Are the values in "imx8mp-pinfunc.h" correct? Best regards, Adriano Carvalho Re: i.MX8M Plus: IOMUX CTS/RTS directions are reversed Hello, This is an issue in the tool that is already reported, it will be fixed in next release. Best regards.

K32L2A SWD ピン - デバッガが接続されていないと MCU が正常に動作しない 私はK32L2Aを使用して新しいデザインを持っています、古いColdfirev1 MCF51QE32パーツからの未評価のデザイン。プロトタイプのPCBでは、デバッグにデバイスを使用していないときでも、PEMicro Cycloneを接続した状態でソフトウェアが期待どおりに動作し、電源を入れるだけで、MCUが期待どおりにソフトウェアを実行します。 ただし、Cycloneがボードから切断されると、MCUは非常に短時間起動し、その後自動的に動作するように見えます(ソフトウェアが期待どおりに実行されず、単に停止するのか、それともデバッグ用にCycloneをアタッチできないため、すぐに修正されるため、ソフトウェアが停止するのかわかりません)。この設計では、SWDIO/SWCLK ラインに外部抵抗はありませんが、データシートには K32L2A によって内部で供給されていると記載されています (MCF51QE、これらの PCB には 10K のプルアップがありました)。 試したこと: - これらのラインに10Kプルアップを追加する - 問題は残っています - PCBからワイヤーを離してリード線をピンに触れると、SWDIOピンに接続されているリード線を指で挟んでボードの電源を入れると、MCUが正しく起動し、ソフトウェアが実行されます。指を離すまで走り続けます。これは、どちらの SWD ピンでも機能しました。静電容量。わからない！。！ これらの行に小さなキャップを付けることはハックのように思えますが、明らかに私は何かを見落としています。 リセットラインにも外部抵抗はありません(見落とし)が、MCUはSWDピンのいずれかを保持した状態で動作し、1つのピンを離すとすぐに故障するため、これは問題ではないようです。 考え、希望、それとも憂慮?どなたでも大歓迎です 🙂よろしくお願いします。 日時: K32L2A SWD ピン - デバッガーが接続されていないと MCU が正常に動作しない 「これらの両方のラインに10Kプルアップを追加すると、問題は残ります」 SWD_DIOには内部プルアップがあります。SWD_CLKには内部プルダウンがあります。 リセット時に両方をプルアップすると、おそらく推測としてデバッガーのクロックパルスのように見えます。指などは十分に長く引き下げられます。 内部抵抗器はかなり高インピーダンスで、温度(20k〜50k)によって異なります。 私は通常、lower-Zの自分のものを追加します。 K32L2Aの電気データシートから: 「プルアップまたはプルダウン抵抗は必要ありませんが (SWD_DIOには内部プルアップがあり、SWD_CLKには内部プルダウンがあります)、システムの堅牢性のために外部10kΩプル抵抗が推奨されます。ザ 上記のRESET_bピンの推奨事項も考慮する必要があります。」

K32L2A SWD pins - MCU fails to run properly unless debugger is attached I have a new design using the K32L2A, ungraded design from old Coldfirev1 MCF51QE32 part. With the prototype PCB, software runs as expected with a PEMicro Cyclone connected, even when not using the device for debug, just powering things up and the MCU runs our software as expected.  However, when the Cyclone is disconnected from the board, the MCU seems to start very briefly then go off on it's own (does not run our software as expected, unsure if it simply stops, or what, since I cannot attached the Cyclone to debug, as that immediately fixes it!). Our design has no external resistors on the SWDIO/SWCLK lines, as the datasheet mentioned these are provided internally by the K32L2A (MCF51QE had 10K pullups on the PCB for these).  Things tried: - Adding 10K pullup to both these lines - problem remains - Putting a wire off the PCB so I could touch the lead to the pins DOES FIX IT, that is, it I pinch the lead connected to the SWDIO pin between my fingers and power up the board, the MCU starts correctly and our software runs. It continues to run until I remove my fingers. This worked with either SWD pin. Capacitance? I dunno!?!  Putting a small cap on these lines seems like a hack, clearly I am overlooking something. No external Resistor on the Reset line either (an oversight) but this didn't seem to be the problem, as the MCU runs with me holding either one of the SWD pins, and fails as soon as I left go of the one pin. Thoughts, hope or asperations? All are welcome 🙂 Cheers! Re: K32L2A SWD pins - MCU fails to run properly unless debugger is attached Hi, As you know that the K32L2 has flash configuration area, after the chip starts up, the core will copy the data in flash configuration area to the FTFA_FOPT register automatically. The PTA4 is multiplexed with PTA4, pls connect PTA4 to a pull-up resistor. Secondly, pls clear NMI_DIS bit in the FTFA_FOPT register. In the case, NMI_b pin will not fire interrupt. Hope it can help you BR XiangJun Rong Re: K32L2A SWD pins - MCU fails to run properly unless debugger is attached "Adding 10K pullup to both these lines - problem remains" SWD_DIO has internal Pull-Up. SWD_CLK has internal Pull-Down. Pulling both up at reset probably looks like a debugger clock pulse as a guess. Fingers and such would pull down long enough. The internal resisters are rather high-Z and vary with temperature (20k to 50k). I usually add my own of lower-Z. From the electrical data sheet for the K32L2A: "While pull-up or pull-down resistors are not required (SWD_DIO has an internal pull-up and SWD_CLK has an internal pull-down), external 10 kΩ pull resistors are recommended for system robustness. The RESET_b pin recommendations mentioned above must also be considered."

将 S32K144 项目从 ARM 的 S32 设计工作室迁移到 S32 平台的 S32 设计工作室 您好，NXP团队： 我们从 NXP 网站上获得了 MC33771C 和 MC33772C 的 BCC SW 驱动程序包。 我们正在尝试将这些示例项目迁移到 S32 平台的 S32 设计工作室（版本：3.5）。 我们按照以下链接中的迁移程序进行操作： https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/Video-Migrating-S32K1-projects-from-S32DS-for-ARM-and-SDK-3-0-x/ta-p/1296239 。 但是，代码没有正确迁移，我们无法确定原因。 请帮助我解决这个问题。 顺祝商祺！ 哈里什 回复：将 S32K144 项目从 ARM 的 S32 设计工作室迁移到 S32 平台的 S32 设计工作室 你好@Hareesh 恐怕 S32DS v3.5 的迁移功能不如 S32DS v3.4 那样全面。我们建议迁移到 S32DS v3.4。 我会将这个问题告知相应的团队。带来不便敬请谅解。 回复：将 S32K144 项目从 ARM 的 S32 设计工作室迁移到 S32 平台的 S32 设计工作室 你好@Hareesh 正如我在之前的回复中提到的。所采取的步骤与所分享的视频中提供的步骤相同。完成代码迁移步骤后，出现的错误与库包含有关，可以使用我上一篇文章中提供的信息来解决。

hantro_VC8000E_enc源代码 NXP技术支持您好 感谢一直以来的帮助和支持。 最近在i.MX8MP开发中，发现连续开关视频压缩，会有一定概率异常停止，经过跟踪调查发现，问题出在imx-gst1.0-plugin的VPUENC插件中，再进一步调查发现，问题可能出现在libhantro_vc8000e.so里面，但是因为工程中没有源代码，只有这个.so文件以及.h文件，无法进一步调查，所以想知道是否有libhantro_vc8000e.so的源代码，如果有，是否可以提供参考一下？ feiyu Re: hantro_VC8000E_enc源代码 VC8000e 有许可限制，所有源代码都放入私人仓库（ https://bitbucket.sw.nxp.com/projects/IMXPRIV/repos/imx-vpu-hantro-vc/ ）。 也许你可以参考下面的链接 https://bitbucket.sw.nxp.com/projects/MMCSH/repos/imx-vpu-hantro-daemon/browse/v4l2_vsi_daemon/src/vsi_enc_video_h2.c https://bitbucket.sw.nxp.com/projects/MMCSH/repos/vpu_wrapper/browse/vpu_wrapper_hantro_VCencoder.c Re: hantro_VC8000E_enc源代码 你好，joanxie： 无法访问您提供的网站。还有其他网站吗？或者是否可以直接将代码作为附件添加？ 飞宇 Re: hantro_VC8000E_enc源代码 你好，joanxie： 非常感谢您的帮助！ 飞宇 Re: hantro_VC8000E_enc源代码 你好，joanxie： 很抱歉再次打扰您，我无法访问您提供的连接。错误如下： 此站点上的连接不安全。比特桶。sw.nxp.com 不接受您的登录证书，或者可能尚未提供。 请尝试联系您的组织。 SSL 客户端身份验证证书错误 飞宇

Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi NXP team, From the NXP website, we obtained the BCC SW Driver Package for MC33771C and MC33772C. We are trying to migrate the those example projects into S32 design studio for S32 platform (Version: 3.5). We followed the migration procedure from the following link: https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/Video-Migrating-S32K1-projects-from-S32DS-for-ARM-and-SDK-3-0-x/ta-p/1296239 . However, the code is not migrating correctly, and we are unable to determine why. Please assist me in fixing this problem. Best regards, Hareesh Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @VaneB , Thanks for the assistance; everything is operating smoothly now. Best regards, Hareesh Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @Hareesh  For the S32SDK S32K1XX RTM 4.0.2, you need to install a service pack, this can be downloaded from S32 Design Studio 3.4 S32K1xx Service Pack 1 > S32 Design Studio IDE >  S32 Design Studio for S32 Platform v.3.4.  Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @VaneB , Following your advice, I installed S32DS v3.4. However, as you can see in the attached image below, when I attempted to migrate the project into S32DS, no project names were displayed. I can see several possibilities mentioned there after expanding the migration filter option. However, the files were associated with SDK S32K1xx 4.0.2 (see to the attached image below). However, all I see in my IDE is SDK S32K1xx 4.0.3 (see attached image below). There is no SDK S32K1xx 4.0.2 listed here. How can it be installed if SDK S32k1xx 4.0.2 is the only version that supports it? Could you please help me to address this problem? Best regards, Hareesh Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @Hareesh  I am afraid that looks like the migration feature of S32DS v3.5 is not as fully functional as S32DS v3.4. We recommend to move to S32DS v3.4.  I will inform the corresponding team of this issue. Sorry for the inconvenience.  Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @VaneB , Yes, there are no mistakes during the code's compilation. However, I am not receiving the project pins and drivers configurations (see screenshots attached), which ought to be provided as they appear in the linked video. Regards, Hareesh Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @Hareesh  As I mentioned in my previous response. The steps made were the ones provided in the video shared. Once the steps of code migration were done the errors presented were related to library inclusion, which can be solved with the information provided in my previous post.  Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @VaneB , Thanks for the update. Despite my following your instructions, it is not migrating. A snapshot of the migration window is attached. Also, for your reference I attached the project which need to be migrated into S32 design studio 3.5. Regards, Hareesh Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @Hareesh  I reproduced the steps of the video and the problems I faced were related to libraries inclusion.  These libraries are located in the Generated_Code file. To solve this problem you need to Rename the ".c" and the ".h", you need to delete the ".bak" of each. You also need to "Exclude from build" the Generated_Code file.  And need to include the file path at project properties.  B.R. VaneB

Doubt about GPT in i.MX8MP Reading the IMX8MPRM document, I see that the there are 6 GPTs available. In Chapter 12, the GPT is described and it says that it has two inputs GPT_CAPTURE1 and GPT_CAPTURE2 that can be used to trigger a capture of the timer counter. In Chapter 8, Chip IO and Pinmux, I can only find 2 capture inputs named GPT1_CAPTURE1 and GPT1_CAPTURE2. Does it means that from the 6 GPTs, only the GPT1 has the ability to use the capture feature? Thanks and regards Re: Doubt about GPT in i.MX8MP Yes, right.

对 i.MX8MP 中的 GPT 的疑问 阅读 IMX8MPRM 文档，我发现有 6 个可用的 GPT。 第 12 章描述了 GPT，并说它有两个输入 GPT_CAPTURE1 和 GPT_CAPTURE2，可用于触发定时器计数器的捕获。 在第 8 章“芯片 IO 和 Pinmux”中，我只能找到 2 个名为 GPT1_CAPTURE1 和 GPT1_CAPTURE2 的捕获输入。 这是否意味着在 6 个 GPT 中，只有 GPT1 具有使用捕获功能的能力？ 感谢并致意 回复：对 i.MX8MP 中的 GPT 的疑问 是的，对。

ARM 用 S32 デザイン スタジオから S32 プラットフォーム用 S32 デザイン スタジオへの S32K144 プロジェクト移行 こんにちは、NXPチームの皆様、 NXPのWebサイトから、MC33771CおよびMC33772C用のBCC SWドライバーパッケージを入手しました。 これらのサンプルプロジェクトをS32プラットフォーム用のS32デザインスタジオ(バージョン:3.5)に移行しようとしています。 次のリンクから移行手順に従いました:https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/Video-Migrating-S32K1-projects-from-S32DS-for-ARM-and-SDK-3-0-x/ta-p/1296239。 ただし、コードが正しく移行されておらず、その理由を特定できません。 この問題を解決するのを手伝ってください。 よろしくお願いいたします。 ハリーシュ Re:ARM用のS32デザインスタジオからS32プラットフォーム用のS32デザインスタジオへのS32K144プロジェクトの移行 こんにちは@Hareesh  残念ながら、S32DS v3.5の移行機能はS32DS v3.4ほど完全には機能していないようです。S32DS v3.4への移行を推奨します。 この問題については、対応するチームに通知します。ご不便をおかけして申し訳ございません。 Re:ARM用のS32デザインスタジオからS32プラットフォーム用のS32デザインスタジオへのS32K144プロジェクトの移行 こんにちは@Hareesh  前の回答で述べたように。行われた手順は、共有されたビデオで提供されたものです。コード移行の手順が完了すると、提示されたエラーはライブラリのインクルードに関連していましたが、これは以前の投稿で提供した情報で解決できます。

i.MX8MPのGPTに対する疑問 IMX8MPRMのドキュメントを読むと、利用可能なGPTが6つあることがわかります。 第12章では、GPTについて説明し、タイマーカウンターのキャプチャをトリガーするために使用できる2つの入力GPT_CAPTURE1とGPT_CAPTURE2があると述べています。 第8章「チップIOとPinmux」では、GPT1_CAPTURE1とGPT1_CAPTURE2という名前の2つのキャプチャ入力しか見つかりません。 6つのGPTのうち、GPT1だけがキャプチャ機能を使用できるということですか? ありがとうございます。よろしくお願いします。 Re:i.MX8MPのGPTについての疑問 はいそうです。