Where i can find example programs for the MC56F8257? Hello, where can i find guides and examples with MC56F82xx series? Re: Where i can find example programs for the MC56F8257? Thank you, mate! Re: Where i can find example programs for the MC56F8257? Hi, I attach the examples here. BR XiangJun Rong Re: Where i can find example programs for the MC56F8257? Hi, Pls check the attached example code. Maybe the MC56F8257 is a bit old, the example code has been removed from the website. I attach several examples. Hope it can help you BR XiangJun Rong

在哪里可以找到 MC56F8257 的示例程序？ 您好，在哪里可以找到 MC56F82xx 系列的指南和示例？ 回复：在哪里可以找到 MC56F8257 的示例程序？ 谢谢你，伙计！

why RSA RsaPkcs1v15VerSrv take too long time When I use RsaPkcs1v15VerSrv(HSE_HASH_ALGO_SHA2_512) to check 64K code, it take 500ms(response is OK), but I would like to use it to do security-boot, it can't be accept now, does there configuration should i do? My configuration: PLL = 80MHz，HW firmware HSE_FW_S32K344_0_2_55_0 The data sheet says that RSA only need 16ms Hash less 1.6ms Re: why RSA RsaPkcs1v15VerSrv take too long time There's no HW support in the device, so it can't be solved by different firmware. Re: why RSA RsaPkcs1v15VerSrv take too long time You are right, I change the hash to SHA-256, time is OK, so S32K3 hardware can support "HW accelerated version",  or another firmware? We use  standard HSE Firmware. Re: why RSA RsaPkcs1v15VerSrv take too long time Hi @zhurui  Here's the reason: There's only SW support for SHA512, so it can take pretty long time. To speed it up, it would be necessary to use HW accelerated version of the hash. Regards, Lukas

i.mxrt1170: CAN Bus trace impedance controller Hi NXP team, we are designing a CAN FD Port (RT1170 +TJA1057BT/0Z) can you tell us is it necessary to control (CANH/CANL) trace impedance as differential signal? And if yes, how many Ohm (120Ohm?) to control or like Single-Ended Signal (50Ohm) is enough Thanks, Huy i.MXRT 105x i.MXRT 106x Re: i.mxrt1170: CAN Bus trace impedance controller Hi Gavin, Thank for your reply We got it Thanks, Huy Re: i.mxrt1170: CAN Bus trace impedance controller Hi @haryanl , Thanks for your interest in NXP MIMXRT series! Yes, and the target impedance is 120 ohm. The schematic you provided is referenced to the correct section. Best regards, Gavin

MK22FN512VLL12 MCU 参考示例 大家好！！！ 实际上，我需要一些有关 MK22FN512VLL12 控制器的信息，例如我们可以在哪个环境中开发代码。我有 Expresso IDE，但我无法找到这个用于开发的控制器。 谁能给我提供上述控制器的示例代码。 回复：MK22FN512VLL12 MCU 参考示例 你好@Pablo_Ramos ， 感谢您的回复，按照您的建议，我已经下载了可支持的 SDK 包，并配置了几个引脚的项目，还生成了没有任何错误的代码，但我发现了一些问题，例如所选处理器不支持的工具：TEE 设备配置，并且它在项目资源管理器会话中的项目名称旁边显示 。

S32K144 Debugging pins are disabled. How to recover the board? I am using NXP S32K144 IC and while creating its demo project on S32 Design Studio via Autosar MCAL layer during the configuring of Port Driver SWD pins: PTA4: JTAG SWD PTA5: System Reset PTA10: JTAG TDO PTC5: JTAG TDI PTC4: JTAG CLK These are configured as UnusedPort pins and theri debugging fucntionality is removed. Now when i am trying to program them via Jlink, i am getting this error: SWD selected. Executing JTAG -> SWD switching sequence. - Connect Under Reset - SWD selected. Executing JTAG -> SWD switching sequence. - Communication error while accessing MDM-AP. - Connect Under Reset - InitTarget() end - Took 377ms - InitTarget() start - SWD selected. Executing JTAG -> SWD switching sequence. - Connect Under Reset - SWD selected. Executing JTAG -> SWD switching sequence. - Communication error while accessing MDM-AP. - Connect Under Reset - InitTarget() end - Took 374ms - ERROR: Failed to connect. Could not establish a connection to target. - ERROR: Connect failed What should i do now? Is their any way i can recover the chip? or is my chip and board damaged now? Isnt their any other way to get it back? Will flashing the code in it via uart using rappid bootloader, solve the problem? Re: S32K144 Debugging pins are disabled. How to recover the board? This is a completely different topic, it has nothing to do with the SWD/JTAG/Reset_b pins discussed in this thread. BR, Daniel Re: S32K144 Debugging pins are disabled. How to recover the board? So is their any way on how to recover the MCU's which are bricket by CSEc. With PeMicro and Lauterback, they will not get recover via that also? Re: S32K144 Debugging pins are disabled. How to recover the board? No, it cannot recover the MCUs bricked by the CSEc engine. Refer to https://wiki.segger.com/J-Link_Commander or contact SEGGER support, J-link is not an NXP product. Regards, Daniel Re: S32K144 Debugging pins are disabled. How to recover the board? Via this method, the chips which are brick because of CSEc peripheral of S32K144 can those also be recovered? And in the shared link for Jlink, it says to execute halt commands. What Jlink Halt are their which needs to be executed. Can you guide us on that too. Thanks and Regards Kunal Gupta Re: S32K144 Debugging pins are disabled. How to recover the board? Hi @Kunal_Gettobyte, The pins are configured for SWD/JTAG/Reset_b after Power-on reset until they are reconfigured by the application. The debugger will have to halt the execution in this short window. PE Micro have Kinetis_Recovery_Utility.exe With Lauterbach we can use: system.CPU S32K144 wait state.power() system.attach Regarding J-link, this should work: https://wiki.rdu.im/_pages/Notes/HOWTOs/howto-recover-swd-after-disabled-with-jlink.html Regards, Daniel

U-Boot on S32G3 ping works only in one direction I am working on an S32G3 board and able to ping from u-boot to the PC connected.  However, it doesn't work the other way around. Using pfe2 device host 192.168.19.5 is alive => ping 192.168.19.5 Using pfe2 device host 192.168.19.5 is alive => ping 192.168.19.5 Using pfe2 device host 192.168.19.5 is alive => ping 192.168.19.5 Using pfe2 device host 192.168.19.5 is alive => ping 192.168.19.5 Using pfe2 device host 192.168.19.5 is alive => ping 192.168.19.5 Using pfe2 device host 192.168.19.5 is alive => ping 192.168.19.5 Using pfe2 device host 192.168.19.5 is alive From the PC when I try to ping there is no response.  The icmp packet was sent on the correct interface as observed using Wireshark.  BSP-S32  Re: U-Boot on S32G3 ping works only in one direction @chenyin_h  Thanks for your response. Yes I also observed that u-boot responded to the ping requests received while u-boot was trying to ping the pc. It makes sense now.  Re: U-Boot on S32G3 ping works only in one direction Hello, @yeshasyesodharan  Thanks for the questions It is correct for the results, u-boot only starts the network driver when it needs to use it (i.e. to send a ping). After it has finished the network driver is stopped. then Any traffic on the network will be ignored, as a result, no ICMP reply would be sent to the PC.  Best Regards Chenyin

S32G3 上的 U-Boot ping 仅在一个方向上工作 我正在使用 S32G3 开发板，能够从 u-boot ping 到所连接的 PC。 然而，反过来就不行。 使用 pfe2 设备 主机 192.168.19.5 处于活动状态 => ping 192.168.19.5 使用 pfe2 设备 主机 192.168.19.5 处于活动状态 => ping 192.168.19.5 使用 pfe2 设备 主机 192.168.19.5 处于活动状态 => ping 192.168.19.5 使用 pfe2 设备 主机 192.168.19.5 处于活动状态 => ping 192.168.19.5 使用 pfe2 设备 主机 192.168.19.5 处于活动状态 => ping 192.168.19.5 使用 pfe2 设备 主机 192.168.19.5 处于活动状态 => ping 192.168.19.5 使用 pfe2 设备 主机 192.168.19.5 处于活动状态 当我尝试从 PC 执行 ping 操作时，没有得到任何响应。 使用 Wireshark 观察到，icmp 数据包已在正确的接口上发送。 BSP-S32 回复：S32G3 上的 U-Boot ping 仅在一个方向上工作 @chenyin_h 感谢您的回复。是的，我还观察到，当 u-boot 尝试 ping 电脑时，它对收到的 ping 请求做出了响应。现在一切都说得通了。 回复：S32G3 上的 U-Boot ping 仅在一个方向上工作 你好， @yeshasyesodharan 谢谢你的提问 结果是正确的，u-boot 仅在需要使用网络驱动程序时启动它（即发送 ping）。完成后，网络驱动程序将停止。那么网络上的任何流量都将被忽略，因此不会向 PC 发送任何 ICMP 回复。 顺祝商祺！ 陈银

The MIPI DSI panel is encountering problems while transitioning from BSP 5 to BSP 6 on the Verdin 8M Hi,  I am currently involved in the migration process from BSP 5.x to BSP 6.5. I am utilizing the VerdIn8mm on a customized board. However, I am encountering difficulties in loading the display driver with BSP 6, as I am receiving error messages. Any ideas on how to fix this problem with BSP6? It was working fine with BSP5. Thank you i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Linux Yocto Project Re: The MIPI DSI panel is encountering problems while transitioning from BSP 5 to BSP 6 on the Verdi Hello @AldoG ,thank you for your answer. I fixed the problem by creating a patch for the /gpu/drm/bridge/sec-dsim.c file. Here’s what I did. I replaced this lines : mvporch |= MVPORCH_SET_MAINVBP(vmode->vback_porch) | MVPORCH_SET_STABLEVFP(vmode->vfront_porch) | MVPORCH_SET_CMDALLOW(0x0); with this lines mvporch |= MVPORCH_SET_MAINVBP(vmode->vback_porch) | MVPORCH_SET_STABLEVFP(vmode->vfront_porch - 15) | MVPORCH_SET_CMDALLOW(0xf); Then i added MIPI_DSI_MODE_VSYNC_FLUSH to dsi->mode_flags when setting mode, typically inside the panel driver. Re: The MIPI DSI panel is encountering problems while transitioning from BSP 5 to BSP 6 on the Verdi Hello, I believe that you are using Toradex BSP, correct? If so, I would recommend to also contact their support channel for assitance on this regard. For the issue on the logs it reports that it failed to attach the bridge, have you compared for any driver changes between version, especifically on the device tree bindings. Best regards/Saludos, Aldo.

Questions about the S32K116 MCU: S32K116 Desired Functionality: UDS-based bootloader and EEPROM enablement. Questions: 1.Where should the UDS-based bootloader be stored? According to AN12218, the bootloader is stored in DFlash. However, the Unified Bootloader User Guide, Rev. 2 describes the bootloader being stored in PFlash.2.If EEPROM needs to be enabled, at least 24KB of the 32KB FlexNVM must be allocated to E-Flash. Can the remaining 8KB store the UDS bootloader? 3.If the bootloader can be stored in PFlash, can the desired functionality be fully supported? 4.If not, which MCU should be used to achieve both functionalities? For example, S32K144? Re: Questions about the S32K116 Yes, your understanding is correct. Re: Questions about the S32K116 We have this application note which talks about A/B swap and using CAN: https://www.nxp.com/docs/en/application-note/AN12323.pdf https://www.nxp.com/docs/en/application-note-software/AN12323SW.zip There are two use-cases - one for S32K144 which has one read partition only on program flash, so the application cannot run during the update. And then for S32K146 which has two read partitions, the application still runs during the update. The first use-case could be used also on S32K116 but it's all about the memory size. If you are able to squeeze everything to 128KB, it's possible. Regards, Lukas Re: Questions about the S32K116 Hi，luka I have a new question. I want to implement AB swap upgrades via UDS (on CAN) on the S32K116. According to the Unified Bootloader User Guide, the bootloader code size is up to 54KB. The application needs to implement UART and CANFD communication and be able to store data in EEPROM during runtime. I added the S32K116's LPUART and CAN_PAL to the S32DS example, and the compiled size is about 22KB. P-Flash stores the bootloader, FirmwareA, and FirmwareB. FlexNVM is used as E-Flash. Is it possible to achieve this on the S32K116? Re: Questions about the S32K116 3. As mentioned above, the only limitation is that you can't access program flash while it is being programmed or erased. ->If the bootloader is stored in P-Flash, during an upgrade (programming or erasing) via the bootloader, the bootloader cannot access the P-Flash area (read/write operations). It must wait until the programming or erasing is completed before it can continue accessing the P-Flash area. Is my understanding correct? Re: Questions about the S32K116 Hi @whale  1. Both options are possible, it depends on your needs. Generaly, it's usually all about read partitions. Devices S32K11x, S32K142 and S32K144 have only one read partition on program flash. So, the code must run from RAM or from data flash when programming the program flash. This is the main limitation. Devices S32K146 and S32K148 has more read partitions (2 and 3), so the bootloader can run from first partition while programming second or third partitionn and there won't be troubles with read-while-write errors. 2. Yes, 8KB data flash can be used for any purpose. I recommend to check section "36.5.9.4 Allowed simultaneous flash operations" in the S32K1 reference manual. 3. As mentioned above, the only limitation is that you can't access program flash while it is being programmed or erased. 4. If it is not acceptable for you, an option is to select S32K146 which has two 512KB read partitions in program flash. Regards, Lukas

LPC55S28 PWMタイミングアライメントの問題 2つのPWMのタイミングを揃えて、一方が他方から特定のオフセットを持つようにするコードがあります。プロジェクトの最適化が無効になっています。ちゃんとしたタイミングに必要なオフセットが変わってしまったことに気づくまでは、うまくいっていると思っていました。2つのタイマーを再起動するというタイムクリティカルな機能のかなり前に、関数呼び出し(テスト関数をコメントアウト)を追加することで問題を再現することができました。この例のタイミングの差は ~72ns ですが、他のコード変更によって差が大きくなったり小さくなったりすることがわかりました。デバイスのコマンドラインインターフェイスを使用して、デフォルト値でAlignPWMs関数を再度呼び出すと、同じタイミングが生成されます。他の値で AlignPWMs 関数を呼び出すと、既定値と一致するオフセット変更が生成されます。要約すると、コードを再度変更するまで、AlignPWMs 関数に渡される値は、リセットや電源喪失を通じてデフォルト値と一致するオフセットを生成します。 問題の原因を特定するために何度も試みたため、「__attribute__（((整列（32)))」、「__DSB()", "__ISB()」、および「__DMB）)」を使用しました。これを使用して、コードの位置合わせ、命令とデータの同期、明示的なメモリ操作の順序の制御を試みました。また、逆アセンブルをレビューしたところ、関数呼び出しの変更以外に、同じアセンブリ コードが生成されていることがわかりました。 ARMがコードの変更で何かを変更する原因となっている2つのCTIMER_StartTimer関数呼び出しの処理方法には何か異なるものがあるはずだと思いますが、何が原因なのか、問題を修正するために何をすべきなのか途方に暮れています。どんな提案でもいただければ幸いです。また、2つのPWMを位置合わせする他の方法にもオープンです。 void Test( void ) { } __attribute__((aligned(32))) void AlignPWMs( uint16_t nOffset ) { // Test(); /* Disable the global interrupt to guarantee timing */ uint32_t primaskValue = DisableGlobalIRQ(); CTIMER_StopTimer( CTIMER0 ); CTIMER_Reset( CTIMER0 ); CTIMER_StopTimer( CTIMER3 ); CTIMER_Reset( CTIMER3 ); CTIMER0->TC = nOffset; __DSB(); // Data Synchronization Barrier - completes all explicit memory accesses __ISB(); // Instruction Synchronization Barrier - flushes the pipeline in the processor __DMB(); // Data Memory Barrier - Ensures the apparent order of the explicit memory operations CTIMER_StartTimer( CTIMER0 ); __DMB(); // Data Memory Barrier - Ensures the apparent order of the explicit memory operations CTIMER_StartTimer( CTIMER3 ); __DMB(); // Data Memory Barrier - Ensures the apparent order of the explicit memory operations EnableGlobalIRQ( primaskValue ); } Re:LPC55S28 PWMタイミングアライメントの問題 私は、時間に敏感なコードをできるだけシンプルにすることで、この問題を回避しました。ペリフェラル レジスタ アドレスを事前に逆参照し、ビット単位または等号演算子を使用する代わりに割り当てを行いました。また、2 つのステートメントを使用する代わりに、2 つの式の割り当てをチェーンしました。これにより、アセンブリはわずか5行になり、関数の内部と外部の両方でコードを変更した後も一貫したタイミングが保たれているように見えます。 // Get the address of the TCR location to be change so that // dereferencing does not need to occur in the time critical code volatile uint32_t * px = & ( CTIMER3->TCR ); volatile uint32_t * py = & ( CTIMER0->TCR ); __DSB(); // Data Synchronization Barrier - completes all explicit memory accesses __ISB(); // Instruction Synchronization Barrier - flushes the pipeline in the processor __DMB(); // Data Memory Barrier - Ensures the apparent order of the explicit memory operations * px = * py = CTIMER_TCR_CEN_MASK; __DMB(); // Data Memory Barrier - Ensures the apparent order of the explicit memory operations 2 つの PWM に使用している CTIMER ピンは、将来必要になった場合に提案を実装できる構成で SCTIMER 機能もサポートしていることがわかります。 Re:LPC55S28 PWMタイミングアライメントの問題 問題は、タイマーを再起動する 2 行の外側にコードをプロジェクトに追加すると、PWM のオフセットが変更されることです。私が挙げた例では、テスト関数を追加すると72nsの変化が発生しました。この問題が見つかったのは、この関数以外のプロジェクト内のコードに対する他の変更により、PWM タイミング オフセットも変更されるように見えるためです。2つのタイマーを有効にするクリティカルタイミングセクションにないコードを変更すると、2つのPWMタイマー間のオフセットが変更されるため、混乱しています。私の予想では、2 つのタイマーを有効にする重要なタイミング セクションが変更されない場合、オフセットのタイミングは常に まったく同じ になるはずです。 現在の動作方法では、プロジェクトでコードを変更すると、PWM 間の実際のタイミング オフセットが変更されるため、オフセットとして 150 を渡すと、プロジェクトでコードが変更される前と同じオフセットが 2 つのタイマーの再起動と関係がなくても、オシロスコープで確認される PWM タイミングと同じオフセットが生成されません。

MK22FN512VLL12マイコンの参考例 みなさん！！！ 実際には、どの環境でコードを開発できるかなどMK22FN512VLL12コントローラーに関する情報はほとんど必要ありません。私はExpresso IDEを持っていますが、開発用のこのコントローラーを見つけることができません。 どなたか上記のコントローラーのサンプルコードを提供していただけますか。 Re:MK22FN512VLL12マイコンの参考例 こんにちは @Pablo_Ramos 、 あなたの返信をありがとう、あなたが提案したように、私はサポート可能なSDKパッケージをダウンロードし、いくつかのピンでプロジェクトを構成し、エラーなしでコードを生成しましたが、選択したプロセッサでサポートされていないツールのようないくつかの問題を観察しました:TEEデバイス構成と、プロジェクトエクスプローラセッションのプロジェクト名の横に が表示されています。

Yocto NXP GA release and meta-freescale mismatch Hi, I am working on upgrading Linux for an old HW platform using i.MX6UL. I am trying to freeze a version/tag/commit for the Yocto meta-imx and meta-freescale. But I found version mismatch when I refer to GA release when bitbake firmware-imx. I have put all the detailed steps and logs in README in this repo. scarthgap-6.6.23-2.0.0  scarthgap-6.6.36-2.1.0  Please follow these two branches to re-produce the problem described in the "Known issue" section: scarthgap-6.6.23-2.0.0 known-issue  scarthgap-6.6.36-2.1.0 known-issue  Please help to look at this issue. Thanks in advance! BR/Chencheng i.MX6UL Yocto Project Re: Yocto NXP GA release and meta-freescale mismatch Hi Chavira, I bumped all the meta layers to use imx GA 6.6.52 2.2.0 release. And this particular issue is gone. BR/Chencheng Re: Yocto NXP GA release and meta-freescale mismatch Hi @securemetersczhang! Thank you for contacting NXP Support! Unfortunately we can't do nothing since is not an official repo. Please download the source code from the official NXP repository. Best Regards! Chavira

Failed to Build imx-image-full with git-native compile error I am trying to build imx-image-full on Ubuntu 24.04 LTS server. I am using the latest versions for all the packages and the imx8 Command line: repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.52-2.2.0.xml DISTRO=fsl-imx-xwayland MACHINE=imx8mp-lpddr4-evk source imx-setup release.sh -b build bitbake imx-image-full Error: WARNING: Host distribution "ubuntu-24.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache: 100% |#########################################################################################################################################| Time: 0:00:05 Loaded 5730 entries from dependency cache. Parsing recipes: 100% |#######################################################################################################################################| Time: 0:00:01 Parsing of 3654 .bb files complete (3653 cached, 1 parsed). 5731 targets, 377 skipped, 3 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.8.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "aarch64-poky-linux" MACHINE = "imx8mp-lpddr4-evk" DISTRO = "fsl-imx-xwayland" DISTRO_VERSION = "6.6-scarthgap" TUNE_FEATURES = "aarch64 armv8a crc crypto" TARGET_FPU = "" meta meta-poky = "HEAD:200d12b6a58ad961d60a7774ca0f7a9d29498724" meta-oe meta-multimedia meta-python = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-freescale = "HEAD:0627128b341cfb2bef7a0832ce8cac0ce1127f13" meta-freescale-3rdparty = "HEAD:6c063450d464eb2f380443c7d9af1b94ce9b9d75" meta-freescale-distro = "HEAD:b9d6a5d9931922558046d230c1f5f4ef6ee72345" meta-imx-bsp meta-imx-sdk meta-imx-ml meta-imx-v2x = "HEAD:219f6d04a4c339eb6f2dc626f944bbdf9a716ff5" meta-nxp-demo-experience = "HEAD:e8e646e22b1f926aac83bb7ad522efa9cd8ccc45" meta-nxp-matter-baseline meta-nxp-openthread = "HEAD:f58365ec75a5768ff3e8e8bcd64f237738c93160" meta-arm meta-arm-toolchain = "HEAD:950a4afce46a359def2958bd9ae33fc08ff9bb0d" meta-clang = "HEAD:2b7433611d80f6d0ee1b04156fa91fc73d3c2665" meta-gnome meta-networking meta-filesystems = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-qt6 = "HEAD:586a6cb5aec755803a3be3cec359baafe89d6432" meta-parsec meta-tpm = "HEAD:459d837338ca230254baa2994f870bf6eb9d0139" meta-virtualization = "HEAD:6f3c1d8f90947408a6587be222fec575a1ca5195" Sstate summary: Wanted 5228 Local 0 Mirrors 0 Missed 5228 Current 2596 (0% match, 33% complete)################################################# | ETA: 0:00:01 Initialising tasks: 100% |####################################################################################################################################| Time: 0:00:15 NOTE: Executing Tasks ERROR: git-native-2.44.1-r0 do_compile: oe_runmake failed ERROR: git-native-2.44.1-r0 do_compile: ExecutionError('/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/temp/run.do_compile.60384', 1, None, None) ERROR: Logfile of failure stored in: /mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/temp/log.do_compile.60384 Log data follows: | DEBUG: Executing python function autotools_aclocals | DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common'] | DEBUG: Python function autotools_aclocals finished | DEBUG: Executing shell function do_compile | NOTE: make -j 16 NO_PYTHON=1 CFLAGS=-isystem/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/include -O2 -pipe LDFLAGS=-L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-O1 -Wl,--allow-shlib-undefined -Wl,--dynamic-linker=/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 -pthread PERL_PATH=/usr/bin/env perl COMPUTE_HEADER_DEPENDENCIES=no NO_GETTEXT=1 NO_CROSS_DIRECTORY_HARDLINKS=1 | LINK git | LINK scalar | /mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/hosttools/ld: common-main.o: in function `main': | common-main.c:(.text.startup+0xde): undefined reference to `cmd_main' | collect2: error: ld returned 1 exit status | make: *** [Makefile:2833: scalar] Error 1 | make: *** Waiting for unfinished jobs.... | /mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/hosttools/ld: git.o:(.data.rel+0x7d0): undefined reference to `cmd_pack_objects' | /mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/hosttools/ld: git.o:(.data.rel+0xb60): undefined reference to `cmd_submodule__helper' | /mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/hosttools/ld: git.o:(.data.rel+0xd10): undefined reference to `cmd_worktree' | collect2: error: ld returned 1 exit status | make: *** [Makefile:2418: git] Error 1 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. ERROR: Task (virtual:native:/mnt/disks/yocto_disk/imx-yocto-bsp/sources/poky/meta/recipes-devtools/git/git_2.44.1.bb:do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 2220 tasks of which 2216 didn't need to be rerun and 1 failed. Summary: 1 task failed: virtual:native:/mnt/disks/yocto_disk/imx-yocto-bsp/sources/poky/meta/recipes-devtools/git/git_2.44.1.bb:do_compile Summary: There was 1 WARNING message. Summary: There were 2 ERROR messages, returning a non-zero exit code. Re: Failed to Build imx-image-full with git-native compile error I guess it helped, because I was managed to pass the git-native step afterwards. Re: Failed to Build imx-image-full with git-native compile error Please go to folder build/tmp/work/x86_64-linux/git-native/2.44.1/git-2.44.1/ run the following command. $ make distclean Then add the following line in build/conf/local.conf. PARALLEL_MAKE ?= "-j 4" Then run  $ bitbake imx-image-full Re: Failed to Build imx-image-full with git-native compile error Though, still retrying to build the bitback for imx8 fails on git-native. ubuntu@yocto-build-server:/mnt/disks/yocto_disk/imx-yocto-bsp/build$ bitbake imx-image-full WARNING: Host distribution "ubuntu-24.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache: 100% |#######################################################################################################################################| Time: 0:00:02Loaded 5730 entries from dependency cache. Parsing recipes: 100% |#####################################################################################################################################| Time: 0:00:00Parsing of 3654 .bb files complete (3653 cached, 1 parsed). 5731 targets, 377 skipped, 3 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.8.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "aarch64-poky-linux" MACHINE = "imx8mp-lpddr4-evk" DISTRO = "fsl-imx-xwayland" DISTRO_VERSION = "6.6-scarthgap" TUNE_FEATURES = "aarch64 armv8a crc crypto" TARGET_FPU = "" meta meta-poky = "HEAD:200d12b6a58ad961d60a7774ca0f7a9d29498724" meta-oe meta-multimedia meta-python = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-freescale = "HEAD:0627128b341cfb2bef7a0832ce8cac0ce1127f13" meta-freescale-3rdparty = "HEAD:6c063450d464eb2f380443c7d9af1b94ce9b9d75" meta-freescale-distro = "HEAD:b9d6a5d9931922558046d230c1f5f4ef6ee72345" meta-imx-bsp meta-imx-sdk meta-imx-ml meta-imx-v2x = "HEAD:219f6d04a4c339eb6f2dc626f944bbdf9a716ff5" meta-nxp-demo-experience = "HEAD:e8e646e22b1f926aac83bb7ad522efa9cd8ccc45" meta-nxp-matter-baseline meta-nxp-openthread = "HEAD:f58365ec75a5768ff3e8e8bcd64f237738c93160" meta-arm meta-arm-toolchain = "HEAD:950a4afce46a359def2958bd9ae33fc08ff9bb0d" meta-clang = "HEAD:2b7433611d80f6d0ee1b04156fa91fc73d3c2665" meta-gnome meta-networking meta-filesystems = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-qt6 = "HEAD:586a6cb5aec755803a3be3cec359baafe89d6432" meta-parsec meta-tpm = "HEAD:459d837338ca230254baa2994f870bf6eb9d0139" meta-virtualization = "HEAD:6f3c1d8f90947408a6587be222fec575a1ca5195" Sstate summary: Wanted 5226 Local 0 Mirrors 0 Missed 5226 Current 2598 (0% match, 33% complete)############################################### | ETA: 0:00:01Initialising tasks: 100% |##################################################################################################################################| Time: 0:00:15NOTE: Executing Tasks ERROR: git-native-2.44.1-r0 do_compile: oe_runmake failed ERROR: git-native-2.44.1-r0 do_compile: ExecutionError('/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/temp/run.do_compile.12690', 1, None, None) ERROR: Logfile of failure stored in: /mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/temp/log.do_compile.12690 Log data follows: | DEBUG: Executing python function autotools_aclocals | DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common'] | DEBUG: Python function autotools_aclocals finished | DEBUG: Executing shell function do_compile | NOTE: make -j 16 NO_PYTHON=1 CFLAGS=-isystem/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/include -O2 -pipe LDFLAGS=-L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-O1 -Wl,--allow-shlib-undefined -Wl,--dynamic-linker=/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 -pthread PERL_PATH=/usr/bin/env perl COMPUTE_HEADER_DEPENDENCIES=no NO_GETTEXT=1 NO_CROSS_DIRECTORY_HARDLINKS=1 | * new build flags | CC oss-fuzz/dummy-cmd-main.o | /bin/sh: 1: cc: not found | CC oss-fuzz/fuzz-commit-graph.o | /bin/sh: 1: cc: not found | make: *** [Makefile:2735: oss-fuzz/dummy-cmd-main.o] Error 127 | make: *** Waiting for unfinished jobs.... | make: *** [Makefile:2735: oss-fuzz/fuzz-commit-graph.o] Error 127 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. ERROR: Task (virtual:native:/mnt/disks/yocto_disk/imx-yocto-bsp/sources/poky/meta/recipes-devtools/git/git_2.44.1.bb:do_compile) failed with exit code '1' Re: Failed to Build imx-image-full with git-native compile error managed to build it successfully after adding these. it gave me curl-config and git-gui issues without them. sudo apt install libcurl4-openssl-dev libssl-dev gettext tcl-dev Re: Failed to Build imx-image-full with git-native compile error Please go to folder "imx-yocto-bsp_scarthgap/build/tmp/work/x86_64-linux/git-native/2.44.1/git-2.44.1" and check whether you could run the following commands sucessfully. $ make distclean $ make -j 4 NO_PYTHON=1 CFLAGS='-isystem/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/include -O2 -pipe' LDFLAGS='-L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-O1 -Wl,--allow-shlib-undefined -Wl,--dynamic-linker=/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 -pthread' PERL_PATH='/usr/bin/env perl' COMPUTE_HEADER_DEPENDENCIES=no NO_GETTEXT=1 NO_CROSS_DIRECTORY_HARDLINKS=1 Re: Failed to Build imx-image-full with git-native compile error yes git-native is part of the sources/poky/meta/conf/bitbake.conf file: ASSUME_PROVIDED = "\ bash-native \ bzip2-native \ chrpath-native \ diffstat-native \ file-native \ findutils-native \ gawk-native \ git-native \ grep-native \ hostperl-runtime-native \ hostpython-runtime-native \ libgcc-native \ patch-native \ sed-native \ tar-native \ texinfo-native \ virtual/crypt-native \ virtual/libiconv-native \ virtual/libintl-native \ wget-native \ " This is the output of the bitback git-native command: ubuntu@yocto-build-server:/mnt/disks/yocto_disk/imx-yocto-bsp$ bitbake git-native WARNING: Host distribution "ubuntu-24.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache: 100% |#######################################################################################################################################| Time: 0:00:02Loaded 5730 entries from dependency cache. Parsing recipes: 100% |#####################################################################################################################################| Time: 0:00:00Parsing of 3654 .bb files complete (3653 cached, 1 parsed). 5731 targets, 377 skipped, 3 masked, 0 errors. WARNING: Explicit target "git-native" is in ASSUME_PROVIDED, ignoring NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.8.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "aarch64-poky-linux" MACHINE = "imx8mp-lpddr4-evk" DISTRO = "fsl-imx-xwayland" DISTRO_VERSION = "6.6-scarthgap" TUNE_FEATURES = "aarch64 armv8a crc crypto" TARGET_FPU = "" meta meta-poky = "HEAD:200d12b6a58ad961d60a7774ca0f7a9d29498724" meta-oe meta-multimedia meta-python = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-freescale = "HEAD:0627128b341cfb2bef7a0832ce8cac0ce1127f13" meta-freescale-3rdparty = "HEAD:6c063450d464eb2f380443c7d9af1b94ce9b9d75" meta-freescale-distro = "HEAD:b9d6a5d9931922558046d230c1f5f4ef6ee72345" meta-imx-bsp meta-imx-sdk meta-imx-ml meta-imx-v2x = "HEAD:219f6d04a4c339eb6f2dc626f944bbdf9a716ff5" meta-nxp-demo-experience = "HEAD:e8e646e22b1f926aac83bb7ad522efa9cd8ccc45" meta-nxp-matter-baseline meta-nxp-openthread = "HEAD:f58365ec75a5768ff3e8e8bcd64f237738c93160" meta-arm meta-arm-toolchain = "HEAD:950a4afce46a359def2958bd9ae33fc08ff9bb0d" meta-clang = "HEAD:2b7433611d80f6d0ee1b04156fa91fc73d3c2665" meta-gnome meta-networking meta-filesystems = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-qt6 = "HEAD:586a6cb5aec755803a3be3cec359baafe89d6432" meta-parsec meta-tpm = "HEAD:459d837338ca230254baa2994f870bf6eb9d0139" meta-virtualization = "HEAD:6f3c1d8f90947408a6587be222fec575a1ca5195" Summary: There were 2 WARNING messages. Re: Failed to Build imx-image-full with git-native compile error Did you modify yocto recipes? Please check whether "git-native" is listed in list "ASSUME_PROVIDED" in sources/poky/meta/conf/bitbake.conf. What is the output when you run command "bitbake git-native"? Re: Failed to Build imx-image-full with git-native compile error Thanks, but all those packages are already installed on my system: ubuntu@yocto-build-server:~$ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential utils-ping python3-git python3-jchrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils Reading package lists... Doneon3-j inja2 python3-subunit zstd liblz4-tool file Building dependency tree... Done Reading state information... Done gawk is already the newest version (1:5.2.1-2build3). wget is already the newest version (1.21.4-1ubuntu4.1). git is already the newest version (1:2.43.0-1ubuntu7.2). diffstat is already the newest version (1.66-1build1). unzip is already the newest version (6.0-28ubuntu4.1). texinfo is already the newest version (7.1-3build2). gcc is already the newest version (4:13.2.0-7ubuntu1). build-essential is already the newest version (12.10ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Re: Failed to Build imx-image-full with git-native compile error In OpenEmbedded-Core, :term:`ASSUME_PROVIDED`  mostly specifies native tools that should not be built. An example is ``git-native``, which when specified, allows for the Git binary from the host to be used rather than building ``git-native``. Please install the following package on your host PC. $ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping python3-git python3-jinja2 python3-subunit zstd liblz4-tool file locales libacl1

NXP S32G-VNP-RDB2 上的以太网启用和网络连接问题 我已经打开 NXP S32G RDB2 板并能够与 PuTTY 进行串行通信。但是当我想将以太网电缆连接到它时。尽管我尝试分配静态 IP，但它仍然无法 ping 通。我想启用以太网驱动程序或解决问题，以便我可以测试我的用例。 回复：NXP S32G-VNP-RDB2 上的以太网启用和网络连接问题 你好@chenyin_h ，我很高兴地分享，它终于可以ping通了，并且可以通过连接到路由器并与其他主板创建专用网络进行测试，现在我也正在探索其他端口的以太网通信。对于任何其他问题，我将开另一张票或帖子。 谢谢你！ 回复：NXP S32G-VNP-RDB2 上的以太网启用和网络连接问题 你好@chenyin_h ， BSP 版本为 Auto Linux 35（来自 SD 卡的 U-boot）并使用 GMAC 端口。但是我认为以太网没有启用。我在 ip route 中检查 eth0 时，它显示 NO-CARRIER，但在 ifconfig 中它显示 UP。我还想用这个接口来实现树莓派和 NXP 开发板之间的通信。请指导我该采取什么步骤，因为我已经尝试了所有的尝试。

关于 evkmimxrt1024_lpi2c_interrupt 的问题 各位 尝试了这个但无法工作，按照说明接线，SCL：J18-12 --> J17 -4， SDA ：J18 -10 -->J17-2。以下函数返回 900 而不是 0（成功） reVal = LPI2C_MasterStart（示例_LPI2C_MASTER_BASEADDR，LPI2C_MASTER_SLAVE_ADDR_7BIT，kLPI2C_Read）； 我遗漏了什么吗？有人试过这个吗？ 我正在使用 IDE24.12 和 SDK24.12。 谢谢！ Ping 回复：关于 evkmimxrt1024_lpi2c_interrupt 的问题 你好@ping1 ， 感谢您的耐心。 我已经与 SDK 团队核实了您的案例。 NXP 内部已经有针对该问题的解决方案，后续的 SDK demo 将会更新，请继续关注 SDK 的更新版本。 如果您急需修复此问题并且不能等到 SDK 更新，请告诉我，我会尽力为您提供支持。 希望它能帮到你。 如果您对此仍有疑问，请告知我。 祝您有个美好的一天！ 此致 刘梅 回复：关于 evkmimxrt1024_lpi2c_interrupt 的问题 你好@ping1 ， 非常感谢您对我们的产品感兴趣并使用我们的社区。 我按照你的做法，也发现了这个错误。 程序检查I2C BUS是否处于kStatus_LPI2C_Busy状态。 我将向相关 SDK 团队请求内部票来检查。 请保持耐心。 希望它能帮到你。 如果您对此仍有疑问，请告知我。 祝您有个美好的一天！ 此致 刘梅

定制 M7 辅助引导加载程序 i.MX RT1176 您好，目前 M7 和 M4 核心固件都存储在 QSPI 闪存FlexSPI1 0x30000000 中。M7 首先启动，然后通过将 QPSI 中的映像复制到 0x20200000 的别名来启动核心 M4。一切正常。 现在我想添加自定义引导加载程序，它将根据某些验证启动 M7 核心，并且 M7 之后将启动 m4。还将负责 M7/M4 或两个固件的 OTA。 您有任何标准的辅助引导加载程序代码吗？请分享以供参考。 谢谢！

S32G399A - System timer module frequency Good morning, I have an S32G399-RDB3 board with a setup derived from the GoldVIP package. The M7 binary and the Linux kernel images were changed, but the bootloader configuration is practically the same of the original configuration. I'm using one of the system timer instances to collect measurements, and I wanted to ask whether there is a practical way to read the STM frequency without following the entire chain of clock signals. Thank you. GoldVIP Re: S32G399A - System timer module frequency Perfect, thank you for your help. Re: S32G399A - System timer module frequency hi，Matteo_Zini Thank you for your reply. If you want to know the exact STM timer time, you must know that the XBAR_DIV3_CLK default is 133.33Mhz, the frequency division factor CPS and CMP values. BR Joey Re: S32G399A - System timer module frequency I'm using Linux on the Cortex-A cores, so I'm not sure how to configure it. Anyway, I would just need to understand the frequency to transform the ticks into seconds, not to set it to any specific value. Thank you. Re: S32G399A - System timer module frequency hi,Matteo_Zini Thank you for your reply. There are multiple possible sources of the XBAR_DIV3_CLK clock, so you need to configure the same value of XBAR_DIV3_CLK for the M core and A core, to avoid conflicts. BR Joey Re: S32G399A - System timer module frequency Hi, thank you for the reply. Because for example if you need to do it at runtime, there are multiple possible sources of the XBAR_DIV3_CLK clock and reconstructing the full chain is not trivial. Re: S32G399A - System timer module frequency hi，Matteo_Zini Thank you for contacting us. May I ask why you want to read the STM frequency without following the entire chain of clock signals? In addition, You can refer to the attachment to check the clock of M core STM.

Yocto Harpoon for iMX8MN custom board Hi Forum, I am porting Yocto Harpoon for an iMX8MN custom board. So far, I could generate and load the imx-image-core into the board then stopped at u-boot prompt and ran : setenv jh_root_dtb imx8mn-custom-harpoon.dtb run jh_mmcboot However, the system seemed to run very slowly and I could not reach the Linux console any more: U-Boot SPL 2023.04-lf_v2023.04+g06e9a4d71cf (Nov 21 2023 - 07:28:53 +0000) DDRINFO: start DRAM init DDRINFO: DRAM rate 3200MTS DDRINFO:ddrphy calibration done DDRINFO: ddrmix config done SEC0: RNG instantiated Normal Boot Trying to boot from BOOTROM Boot Stage: Primary boot image offset 0x0, pagesize 0x200, ivt offset 0x0 NOTICE: Do not release JR0 to NS as it can be used by HAB NOTICE: BL31: v2.8(release):lf-6.1.55-2.2.1-rc1-0-g08e9d4eef NOTICE: BL31: Built : 06:43:30, Nov 21 2023 U-Boot 2023.04-lf_v2023.04+g06e9a4d71cf (Nov 21 2023 - 07:28:53 +0000) CPU: i.MX8MNano Quad rev1.0 1500 MHz (running at 1200 MHz) CPU: Commercial temperature grade (0C to 95C) at 43C Reset cause: POR Model: Custom i.MX8MNano based board DRAM: 2 GiB TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x52] TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50] Power supply on USB1 Core: 192 devices, 33 uclasses, devicetree: separate MMC: FSL_SDHC: 1, FSL_SDHC: 2 Loading Environment from MMC... *** Warning - bad CRC, using default environment [*]-Video Link 0mxs_video lcd-controller@32e00000: failed to get any display timings probe video device failed, ret -22 [0] lcd-controller@32e00000, video mxs_video lcd-controller@32e00000: failed to get any display timings probe video device failed, ret -22 In: serial Out: serial Err: serial SEC0: RNG instantiated switch to partitions #0, OK mmc2(part 0) is current device flash target is MMC:2 Net: Could not get PHY for FEC0: addr 0 No ethernet found. Fastboot: Normal Normal Boot Hit any key to stop autoboot: 0 u-boot=> u-boot=> u-boot=> u-boot=> u-boot=> u-boot=> u-boot=> u-boot=> setenv jh_root_dtb imx8mn-custom-harpoon.dtb u-boot=> run jh_mmcboot 32856576 bytes read in 113 ms (277.3 MiB/s) Booting from mmc ... 42747 bytes read in 8 ms (5.1 MiB/s) ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Working FDT set to 43000000 Using Device Tree in place at 0000000043000000, end 000000004300d6fa Working FDT set to 43000000 mxs_video lcd-controller@32e00000: failed to get any display timings probe video device failed, ret -22 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.1.55+g3cc6b768e08a (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 12.3.0, GNU ld (GNU Binutils) 2.40.0.20230703) #1 SMP PREEMPT Sun Dec 15 03:28:12 UTC 2024 [ 0.000000] Machine model: NXP i.MX8MNano ADSAI board [ 0.000000] Memory limited to 1212MB [ 0.000000] efi: UEFI not found. [ 0.000000] Reserved memory: created CMA memory pool at 0x0000000065c00000, size 640 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x00000000b8700000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node vdevbuffer-ca53@b8700000, compatible id shared-dma-pool [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x000000008dbfffff] [ 0.000000] NUMA: NODE_DATA [mem 0x65966700-0x65968fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000040000000-0x000000008dbfffff] [ 0.000000] DMA32 empty [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x0000000055ffffff] [ 0.000000] node 0: [mem 0x0000000058000000-0x000000008dbfffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000008dbfffff] [ 0.000000] On node 0, zone DMA: 8192 pages in unavailable ranges [ 0.000000] On node 0, zone DMA: 9216 pages in unavailable ranges [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] psci: SMC Calling Convention v1.2 [ 0.000000] percpu: Embedded 20 pages/cpu s44520 r8192 d29208 u81920 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: kernel page table isolation forced ON by KASLR [ 0.000000] CPU features: detected: Kernel page table isolation (KPTI) [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] alternatives: applying boot alternatives [ 0.000000] Fallback order for Node 0: 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 305296 [ 0.000000] Policy zone: DMA [ 0.000000] Kernel command line: clk_ignore_unused mem=1212MB console=ttymxc1,115200 root=/dev/mmcblk2p2 rootwait rw [ 0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off [ 0.000000] Memory: 526384K/1241088K available (19776K kernel code, 1622K rwdata, 7228K rodata, 3328K init, 644K bss, 59344K reserved, 655360K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 128 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: GICv3 features: 16 PPIs [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000 [ 0.000000] ITS: No ITS available, not enabling LPIs [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns [ 0.000000] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns [ 0.000391] Console: colour dummy device 80x25 [ 0.000455] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000) [ 0.000466] pid_max: default: 32768 minimum: 301 [ 0.000521] LSM: Security Framework initializing [ 0.000612] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 0.000628] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 0.002045] cblist_init_generic: Setting adjustable number of callback queues. [ 0.002053] cblist_init_generic: Setting shift to 2 and lim to 1. [ 0.002123] cblist_init_generic: Setting adjustable number of callback queues. [ 0.002126] cblist_init_generic: Setting shift to 2 and lim to 1. [ 0.002281] rcu: Hierarchical SRCU implementation. [ 0.002284] rcu: Max phase no-delay instances is 1000. [ 0.003334] EFI services will not be available. [ 0.003547] smp: Bringing up secondary CPUs ... [ 0.004009] Detected VIPT I-cache on CPU1 [ 0.004088] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000 [ 0.004129] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.004652] Detected VIPT I-cache on CPU2 [ 0.004711] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000 [ 0.004733] CPU2: Booted secondary processor 0x0000000002 [0x410fd034] [ 0.005182] Detected VIPT I-cache on CPU3 [ 0.005245] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000 [ 0.005265] CPU3: Booted secondary processor 0x0000000003 [0x410fd034] [ 0.005321] smp: Brought up 1 node, 4 CPUs [ 0.005328] SMP: Total of 4 processors activated. [ 0.005332] CPU features: detected: 32-bit EL0 Support [ 0.005334] CPU features: detected: 32-bit EL1 Support [ 0.005339] CPU features: detected: CRC32 instructions [ 0.005399] CPU: All CPU(s) started at EL2 [ 0.005418] alternatives: applying system-wide alternatives [ 0.006962] devtmpfs: initialized [ 0.013454] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.013478] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.032658] pinctrl core: initialized pinctrl subsystem [ 0.034684] DMI not present or invalid. [ 0.035309] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.036931] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations [ 0.037723] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.038388] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.038476] audit: initializing netlink subsys (disabled) [ 0.038692] audit: type=2000 audit(0.036:1): state=initialized audit_enabled=0 res=1 [ 0.039217] thermal_sys: Registered thermal governor 'step_wise' [ 0.039221] thermal_sys: Registered thermal governor 'power_allocator' [ 0.039263] cpuidle: using governor menu [ 0.039496] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.039580] ASID allocator initialised with 32768 entries [ 0.040448] Serial: AMBA PL011 UART driver [ 0.040515] imx mu driver is registered. [ 0.040536] imx rpmsg driver is registered. [ 0.045540] platform soc@0: Fixed dependency cycle(s) with /soc@0/bus@30000000/efuse@30350000/unique-id@4 [ 0.048460] imx8mn-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver [ 0.048984] platform 30350000.efuse: Fixed dependency cycle(s) with /soc@0/bus@30000000/clock-controller@30380000 [ 0.058752] KASLR enabled [ 0.077851] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages [ 0.077863] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page [ 0.077867] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages [ 0.077873] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page [ 0.077877] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages [ 0.077882] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page [ 0.077886] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages [ 0.077891] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page [ 0.079637] ACPI: Interpreter disabled. [ 0.080318] iommu: Default domain type: Translated [ 0.080323] iommu: DMA domain TLB invalidation policy: strict mode [ 0.080617] SCSI subsystem initialized [ 0.080931] usbcore: registered new interface driver usbfs [ 0.080973] usbcore: registered new interface driver hub [ 0.080997] usbcore: registered new device driver usb [ 0.081879] mc: Linux media interface: v0.10 [ 0.081914] videodev: Linux video capture interface: v2.00 [ 0.081986] pps_core: LinuxPPS API ver. 1 registered [ 0.081990] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 0.082004] PTP clock support registered [ 0.082127] EDAC MC: Ver: 3.0.0 [ 0.083056] FPGA manager framework [ 0.083129] Advanced Linux Sound Architecture Driver Initialized. [ 0.083658] Bluetooth: Core ver 2.22 [ 0.083686] NET: Registered PF_BLUETOOTH protocol family [ 0.083690] Bluetooth: HCI device and connection manager initialized [ 0.083698] Bluetooth: HCI socket layer initialized [ 0.083703] Bluetooth: L2CAP socket layer initialized [ 0.083714] Bluetooth: SCO socket layer initialized [ 0.084052] vgaarb: loaded [ 0.084525] clocksource: Switched to clocksource arch_sys_counter [ 0.084866] VFS: Disk quotas dquot_6.6.0 [ 0.084905] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.085081] pnp: PnP ACPI: disabled [ 0.091717] NET: Registered PF_INET protocol family [ 0.091946] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 0.093569] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear) [ 0.093643] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.093659] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.093769] TCP bind hash table entries: 16384 (order: 7, 524288 bytes, linear) [ 0.094294] TCP: Hash tables configured (established 16384 bind 16384) [ 0.094418] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear) [ 0.094462] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear) [ 0.094624] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.095019] RPC: Registered named UNIX socket transport module. [ 0.095023] RPC: Registered udp transport module. [ 0.095026] RPC: Registered tcp transport module. [ 0.095029] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.095779] PCI: CLS 0 bytes, default 64 [ 0.096449] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available [ 0.097187] kvm [1]: IPA Size Limit: 40 bits [ 0.098966] kvm [1]: GICv3: no GICV resource entry [ 0.098970] kvm [1]: disabling GICv2 emulation [ 0.098982] kvm [1]: GIC system register CPU interface enabled [ 0.099073] kvm [1]: vgic interrupt IRQ9 [ 0.099156] kvm [1]: Hyp mode initialized successfully [ 0.100291] Initialise system trusted keyrings [ 0.100480] workingset: timestamp_bits=42 max_order=19 bucket_order=0 [ 0.106871] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.107505] NFS: Registering the id_resolver key type [ 0.107531] Key type id_resolver registered [ 0.107535] Key type id_legacy registered [ 0.107606] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.107610] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 0.107632] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.107961] 9p: Installing v9fs 9p2000 file system support [ 0.143277] Key type asymmetric registered [ 0.143282] Asymmetric key parser 'x509' registered [ 0.143328] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 0.143334] io scheduler mq-deadline registered [ 0.143338] io scheduler kyber registered [ 0.148887] EINJ: ACPI disabled. [ 0.159641] imx-sdma 302b0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2 [ 0.159657] imx-sdma 302b0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin [ 0.166529] mxs-dma 33000000.dma-controller: initialized [ 0.169882] SoC: i.MX8MN revision 1.0 [ 0.171194] Bus freq driver module loaded [ 0.176202] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.178493] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 19, base_baud = 5000000) is a IMX [ 0.179088] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 20, base_baud = 5000000) is a IMX [ 0.179595] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 21, base_baud = 1500000) is a IMX [ 1.335963] printk: console [ttymxc1] enabled [ 1.341812] imx-drm 32c00000.bus:display-subsystem: no available port [ 1.358681] loop: module loaded [ 1.363061] of_reserved_mem_lookup() returned NULL [ 1.368029] megasas: 07.719.03.00-rc1 [ 1.376155] spi-nor spi3.0: n25q256ax1 (32768 Kbytes) [ 1.385400] tun: Universal TUN/TAP device driver, 1.6 [ 1.391179] thunder_xcv, ver 1.0 [ 1.394455] thunder_bgx, ver 1.0 [ 1.397722] nicpf, ver 1.0 [ 1.402076] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [ 1.409308] hns3: Copyright (c) 2017 Huawei Corporation. [ 1.414680] hclge is initializing [ 1.418016] e1000: Intel(R) PRO/1000 Network Driver [ 1.422900] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 1.428683] e1000e: Intel(R) PRO/1000 Network Driver [ 1.433656] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.439621] igb: Intel(R) Gigabit Ethernet Network Driver [ 1.445062] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.450674] igbvf: Intel(R) Gigabit Virtual Function Network Driver [ 1.456951] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 1.463024] sky2: driver version 1.30 [ 1.467161] usbcore: registered new interface driver r8152 [ 1.472929] VFIO - User Level meta-driver version: 0.3 [ 1.480869] usbcore: registered new interface driver uas [ 1.486244] usbcore: registered new interface driver usb-storage [ 1.492322] usbcore: registered new interface driver usbserial_generic [ 1.498874] usbserial: USB Serial support registered for generic [ 1.504910] usbcore: registered new interface driver ftdi_sio [ 1.510681] usbserial: USB Serial support registered for FTDI USB Serial Device [ 1.518028] usbcore: registered new interface driver usb_serial_simple [ 1.524579] usbserial: USB Serial support registered for carelink [ 1.530695] usbserial: USB Serial support registered for flashloader [ 1.537076] usbserial: USB Serial support registered for funsoft [ 1.543105] usbserial: USB Serial support registered for google [ 1.549048] usbserial: USB Serial support registered for hp4x [ 1.554818] usbserial: USB Serial support registered for kaufmann [ 1.560935] usbserial: USB Serial support registered for libtransistor [ 1.567484] usbserial: USB Serial support registered for moto_modem [ 1.573777] usbserial: USB Serial support registered for motorola_tetra [ 1.580409] usbserial: USB Serial support registered for nokia [ 1.586262] usbserial: USB Serial support registered for novatel_gps [ 1.592638] usbserial: USB Serial support registered for siemens_mpi [ 1.599019] usbserial: USB Serial support registered for suunto [ 1.604958] usbserial: USB Serial support registered for vivopay [ 1.610987] usbserial: USB Serial support registered for zio [ 1.616681] usbcore: registered new interface driver usb_ehset_test [ 1.625467] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0 [ 1.639860] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0 [ 1.646081] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to 2025-02-24T14:00:33 UTC (1740405633) [ 1.656021] i2c_dev: i2c /dev entries driver [ 1.664255] Bluetooth: HCI UART driver ver 2.3 [ 1.668725] Bluetooth: HCI UART protocol H4 registered [ 1.673873] Bluetooth: HCI UART protocol BCSP registered [ 1.679213] Bluetooth: HCI UART protocol LL registered [ 1.684359] Bluetooth: HCI UART protocol ATH3K registered [ 1.689783] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 1.696138] Bluetooth: HCI UART protocol Broadcom registered [ 1.701823] Bluetooth: HCI UART protocol QCA registered [ 1.708175] sdhci: Secure Digital Host Controller Interface driver [ 1.714377] sdhci: Copyright(c) Pierre Ossman [ 1.719285] Synopsys Designware Multimedia Card Interface Driver [ 1.725787] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.733120] ledtrig-cpu: registered to indicate activity on CPUs [ 1.739993] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping .... [ 1.746960] usbcore: registered new interface driver usbhid [ 1.752547] usbhid: USB HID core driver [ 1.760807] cs_system_cfg: CoreSight Configuration manager initialised [ 1.769024] optee: probing for conduit method. [ 1.773502] optee: revision 4.0 (a303fc80) [ 1.773776] optee: dynamic shared memory is enabled [ 1.783099] optee: initialized driver [ 1.787874] galcore: clk_get 2d core clock failed, disable 2d/vg! [ 1.794386] Galcore version 6.4.11.p2.711242 [ 1.858297] [drm] Initialized vivante 1.0.0 20170808 for 38000000.gpu on minor 0 [ 1.868320] NET: Registered PF_LLC protocol family [ 1.873836] NET: Registered PF_INET6 protocol family [ 1.879655] Segment Routing with IPv6 [ 1.883369] In-situ OAM (IOAM) with IPv6 [ 1.887348] NET: Registered PF_PACKET protocol family [ 1.892435] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 1.905478] Bluetooth: RFCOMM TTY layer initialized [ 1.910376] Bluetooth: RFCOMM socket layer initialized [ 1.915541] Bluetooth: RFCOMM ver 1.11 [ 1.919309] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 1.924629] Bluetooth: BNEP filters: protocol multicast [ 1.929867] Bluetooth: BNEP socket layer initialized [ 1.934836] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 1.940767] Bluetooth: HIDP socket layer initialized [ 1.945856] 8021q: 802.1Q VLAN Support v1.8 [ 1.950064] lib80211: common routines for IEEE802.11 drivers [ 1.955829] 9pnet: Installing 9P2000 support [ 1.960231] Key type dns_resolver registered [ 1.964928] registered taskstats version 1 [ 1.969057] Loading compiled-in X.509 certificates [ 1.991350] imx-rpmsg b8600000.rpmsg-ca53: assigned reserved memory node vdevbuffer-ca53@b8700000 [ 2.024534] virtio_rpmsg_bus virtio0: rpmsg host is online [ 2.036978] usb_phy_generic usbphynop1: supply vcc not found, using dummy regulator [ 2.044768] usb_phy_generic usbphynop1: dummy supplies not allowed for exclusive requests [ 2.063682] nxp-pca9450 0-0025: pca9450bc probed. [ 2.068509] i2c i2c-0: IMX I2C adapter registered [ 2.073818] gpio-144 (scl): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 2.083180] i2c 1-0050: Fixed dependency cycle(s) with /soc@0/bus@32c00000/usb@32e40000/port/endpoint [ 2.093404] i2c i2c-1: IMX I2C adapter registered [ 2.100334] pps pps0: new PPS source ptp0 [ 2.107744] fec 30be0000.ethernet: Invalid MAC address: 00:00:00:00:00:00 [ 2.114590] fec 30be0000.ethernet: Using random MAC address: 12:0e:0a:66:46:0e [ 2.123597] fec 30be0000.ethernet eth0: registered PHC device 0 [ 2.134632] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 8 mkt segment 0 supported-hw 0x100 0x1 [ 2.144664] Hot alarm is canceled. GPU3D clock will return to 64/64 [ 2.154960] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO [ 2.157854] OF: graph: no port node found in /soc@0/bus@30800000/i2c@30a30000/tcpc@50/connector [ 2.168758] OF: graph: no port node found in /soc@0/bus@30800000/i2c@30a30000/tcpc@50/connector [ 2.177501] OF: graph: no port node found in /soc@0/bus@30800000/i2c@30a30000/tcpc@50/connector [ 2.185079] mmc0: SDHCI controller on 30b40000.mmc [30b40000.mmc] using ADMA [ 2.191386] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA [ 2.198534] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 2.209811] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 2.216429] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 2.220580] clk: Not disabling unused clocks [ 2.225107] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db [ 2.229349] ALSA device list: [ 2.240140] No soundcards found. [ 2.243811] Waiting for root device /dev/mmcblk2p2... [ 12.262434] platform sound-bt-sco: deferred probe pending [ 12.267875] platform regulator-audio-board: deferred probe pending [ 60.416613] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2 [ 60.427089] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin [ 62.436596] cfg80211: failed to load regulatory.db [ 121.828563] imx-sdma 30bd0000.dma-controller: external firmware not found, using ROM firmware [ 121.828563] imx-sdma 302b0000.dma-controller: external firmware not found, using ROM firmware [ 121.828633] imx-sdma 302c0000.dma-controller: external firmware not found, using ROM firmware Could you help, please ? Best Regards, Khang i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Yocto Harpoon for iMX8MN custom board I just found the reason in another discussion : https://community.nxp.com/t5/i-MX-Processors/iMX8MP-EVK-Unable-to-launch-jailhouse-mode-with-Yocto-Harpoon/m-p/2074315 Re: Yocto Harpoon for iMX8MN custom board Hi @JosephAtNXP, I double-checked the console output of NXP's iMX8MP-EVK flashed/installed with the Yocto Harpoon of the same BSP version and got similar trace for the main debug console : [ 3.445096] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db [ 3.449382] ALSA device list: [ 3.460120] No soundcards found. [ 3.463714] Waiting for root device /dev/mmcblk2p2... [ 13.542494] platform sound-bt-sco: deferred probe pending [ 60.417495] imx-sdma 30bd0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2 [ 60.427957] imx-sdma 30bd0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin [ 64.485494] cfg80211: failed to load regulatory.db [ 64.485494] cfg80211: failed to load regulatory.db [ 121.829456] imx-sdma 30e10000.dma-controller: external firmware not found, using ROM firmware [ 121.829501] imx-sdma 30bd0000.dma-controller: external firmware not found, using ROM firmware I expected that there would be certain log relevant to the launching of the jailhouse mode but there was not. Full log is in attachment. Could you help? K. Re: Yocto Harpoon for iMX8MN custom board Hi, The EVK boards expose serial ports through their USB debug interface. One of these serial ports is used by Linux for its console, and another one is used by the guest RTOS. To run the reference applications, open both serial ports with terminal emulators. Insert the micro-SD card, on which the Yocto image has been flashed, in the EVK and power up the board. Make sure that your boot partition has the DTB and that your environment points to it. u-boot => setenv jh_root_dtb imx8mn-evk-harpoon.dtb u-boot => run jh_mmcboot Regards, Re: Yocto Harpoon for iMX8MN custom board Hello @JosephAtNXP, Could you help to give more instruction about interracting with the Jailhouse on iMX8MN based board, please? Re: Yocto Harpoon for iMX8MN custom board Hi again, Also, currently I only have access to the main console. Am I missing any UART connection for interacting with Jailhouse? Thanks, K. Re: Yocto Harpoon for iMX8MN custom board Hi @JosephAtNXP, Thanks for your support. Our custom board is similar to the iMX8MN EVK in terms of DDR memory (2 GiB) with only difference being the Ethernet PHY. So it would be straightforward for the porting. Of course we did the DDR training and the board works well with Yocto without Harpoon. I think my current problem is that the jailhouse mode could NOT be entered even I added the imx8mn-custom-inmate.dts copied from imx8mn-evk-inmate.dts with slight change in the header : model = "NXP i.MX8MNano CUSTOM board"; compatible = "fsl,imx8mn-custom", "fsl,imx8mm"; interrupt-parent = <&gic>; #address-cells = <2>; #size-cells = <2>; Re: Yocto Harpoon for iMX8MN custom board Hi, Thank you for your interest in NXP Semiconductor products, The mentioned DTS is required to boot, please fix that. But the issue is likely to porting issues, please go through the following posts and review your built image, try both solutions. https://community.nxp.com/t5/i-MX-Processors/Yocto-build-external-firmware-error/m-p/1227957 https://community.nxp.com/t5/i-MX-Processors/imx6-linux-imx-sdma-firmware-load-failed-error/m-p/1193538 Regards Re: Yocto Harpoon for iMX8MN custom board Hi again, Compared to other device-trees of the EVKs and linked to my previous ticket, is the missing of imx8mn-custom-inmate.dts the cause ? The following guide also seems to add the inmate related device-tree as well : https://variwiki.com/index.php?title=Jailhouse_Guide&release=mx8mn-yocto-mickledore-6.1.36_2.1.0-v1.0 Best Regards, Khang

imx-image-full のビルドに失敗しましたが、git-native コンパイルエラーが発生しました Ubuntu 24.04 LTSサーバーでimx-image-fullをビルドしようとしています。 私はすべてのパッケージとimx8に最新バージョンを使用しています コマンドライン： リポジトリ init -u https://github.com/nxp-imx/imx-manifest-b imx-linux-scarthgap -m imx-6.6.52-2.2.0.xml DISTRO=fsl-imx-xwayland MACHINE=imx8mp-lpddr4-evk ソース imx-setup release.sh -b build ビットベイク imx-image-full エラー： 警告:ホストディストリビューション「ubuntu-24.04」このバージョンのビルドシステムでは検証されていません。予期しない障害が発生する可能性があります。テスト済みのディストリビューションを使用することをお勧めします。 キャッシュの読み込み: 100% |#########################################################################################################################################| Time: 0:00:05 Loaded 5730 entries from dependency cache. Parsing recipes: 100% |#######################################################################################################################################|時刻: 0:00:01 3654 .bb の解析ファイルが完了しました (3653 キャッシュ、1 解析)。5731 ターゲット、377 スキップ、3 マスク、0 エラー。 注: 欠落しているタスクキューの依存関係の解決 ビルド構成: BB_VERSION = "2.8.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "ユニバーサル" TARGET_SYS = "aarch64-poky-linux" マシン = "imx8mp-lpddr4-evk" DISTRO = "fsl-imx-xwayland" DISTRO_VERSION = "6.6-スカースギャップ" TUNE_FEATURES = "aarch64 armv8a crc crypto" TARGET_FPU = "" メタ meta-poky = "HEAD:200d12b6a58ad961d60a7774ca0f7a9d29498724" メタOE メタマルチメディア メタpython = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-freescale = "HEAD:0627128b341cfb2bef7a0832ce8cac0ce1127f13" meta-freescale-3rdparty = "HEAD:6c063450d464eb2f380443c7d9af1b94ce9b9d75" meta-freescale-distro = "HEAD:b9d6a5d9931922558046d230c1f5f4ef6ee72345" メタIMX-BSP メタIMX-SDK メタ-IMX-ML meta-imx-v2x = "ヘッド:219f6d04a4c339eb6f2dc626f944bbdf9a716ff5" meta-nxp-demo-experience = "HEAD:e8e646e22b1f926aac83bb7ad522efa9cd8ccc45" メタ-NXP-マター-ベースライン meta-nxp-openthread = "ヘッド:f58365ec75a5768ff3e8e8bcd64f237738c93160" メタアーム meta-arm-toolchain = "ヘッド:950a4afce46a359def2958bd9ae33fc08ff9bb0d" meta-clang = "ヘッド:2b7433611d80f6d0ee1b04156fa91fc73d3c2665" メタノーム メタネットワーキング meta-filesystems = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-qt6 = "ヘッド:586a6cb5aec755803a3be3cec359baafe89d6432" メタパーセク meta-tpm = "ヘッド:459d837338ca230254baa2994f870bf6eb9d0139" メタ仮想化 = "HEAD:6f3c1d8f90947408a6587be222fec575a1ca5195" Sstateの概要:募集5228ローカル0ミラー0見逃し5228現在の2596(0%一致、33%完了)################################################# | ETA: 0:00:01 Initialising tasks: 100% |####################################################################################################################################|時間: 0:00:15 メモ: タスクの実行 エラー:git-native-2.44.1-r0 do_compile:oe_runmakeに失敗しました エラー:git-native-2.44.1-r0 do_compile:ExecutionError('/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/temp/run.do_compile.60384', 1, なし, なし) エラー:障害のログファイルが/ mnt / disks / yocto_disk / imx-yocto-bsp / build / tmp / work / x86_64-linux / git-native / 2.44.1 / temp / log.do_compile.60384に保存されています。 ログデータは次のとおりです。 |デバッグ:Python関数autotools_aclocalsを実行しています |デバッグ: SITE ファイル ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common'] |デバッグ:Python関数autotools_aclocals終了しました |DEBUG: シェル関数 do_compile を実行しています |注: make -j 16 NO_PYTHON=1 CFLAGS=-isystem/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/include -O2 -pipe LDFLAGS=-L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-O1 -Wl,--allow-shlib-undefined -Wl,--dynamic-linker=/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 -pthread PERL_PATH=/usr/bin/env perl COMPUTE_HEADER_DEPENDENCIES=no NO_GETTEXT=1 NO_CROSS_DIRECTORY_HARDLINKS=1 | リンク git |LINK スカラー |/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/hosttools/ld: common-main.o: 関数 'main' 内: |common-main.c:(.text.startup+0xde):'cmd_main' への未定義の参照 |collect2: エラー: ld が 1 つの終了ステータスを返しました |make: *** [Makefile:2833: scalar] エラー 1 |make: *** 未完成の仕事を待っています...。 |/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/hosttools/ld: git.o:(.data.rel+0x7d0):'cmd_pack_objects' への未定義の参照 |/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/hosttools/ld: git.o:(.data.rel+0xb60):'cmd_submodule__helper' への未定義の参照 |/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/hosttools/ld: git.o:(.data.rel+0xd10):'cmd_worktree' への未定義の参照 |collect2: エラー: ld が 1 つの終了ステータスを返しました |make: *** [Makefile:2418: git] エラー 1 |エラー: oe_runmake失敗しました |警告: シェル コマンドからコード 1 を終了します。 エラー:タスク（virtual:native（/mnt/disks/yocto_disk/imx-yocto-bsp/sources/poky/meta/recipes-devtools/git/git_2.44.1.bb％do_compile)終了コード '1' で失敗しました 注: タスクの概要: 2220 個のタスクを試行しましたが、そのうち 2216 個は再実行する必要がなく、1 個が失敗しました。 概要: 1 つのタスクが失敗しました: virtual:native:/mnt/disks/yocto_disk/imx-yocto-bsp/sources/poky/meta/recipes-devtools/git/git_2.44.1.bb:do_compile 概要:警告メッセージが1つありました。 概要: 2 つの ERROR メッセージがあり、0 以外の終了コードが返されました。 Re:git-nativeコンパイルエラーでimx-image-fullのビルドに失敗しました その後、git-nativeのステップに合格することができたので、それが役立ったと思います。 Re:git-nativeコンパイルエラーでimx-image-fullのビルドに失敗しました ただし、imx8のビットバックをビルドしようとすると、git-nativeで失敗します。 ubuntu@yocto-build-server:/mnt/disks/yocto_disk/imx-yocto-bsp/build$ bitbake imx-image-full WARNING: Host distribution "ubuntu-24.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache: 100% |#######################################################################################################################################| Time: 0:00:02Loaded 5730 entries from dependency cache. Parsing recipes: 100% |#####################################################################################################################################| Time: 0:00:00Parsing of 3654 .bb files complete (3653 cached, 1 parsed). 5731 targets, 377 skipped, 3 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.8.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "aarch64-poky-linux" MACHINE = "imx8mp-lpddr4-evk" DISTRO = "fsl-imx-xwayland" DISTRO_VERSION = "6.6-scarthgap" TUNE_FEATURES = "aarch64 armv8a crc crypto" TARGET_FPU = "" meta meta-poky = "HEAD:200d12b6a58ad961d60a7774ca0f7a9d29498724" meta-oe meta-multimedia meta-python = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-freescale = "HEAD:0627128b341cfb2bef7a0832ce8cac0ce1127f13" meta-freescale-3rdparty = "HEAD:6c063450d464eb2f380443c7d9af1b94ce9b9d75" meta-freescale-distro = "HEAD:b9d6a5d9931922558046d230c1f5f4ef6ee72345" meta-imx-bsp meta-imx-sdk meta-imx-ml meta-imx-v2x = "HEAD:219f6d04a4c339eb6f2dc626f944bbdf9a716ff5" meta-nxp-demo-experience = "HEAD:e8e646e22b1f926aac83bb7ad522efa9cd8ccc45" meta-nxp-matter-baseline meta-nxp-openthread = "HEAD:f58365ec75a5768ff3e8e8bcd64f237738c93160" meta-arm meta-arm-toolchain = "HEAD:950a4afce46a359def2958bd9ae33fc08ff9bb0d" meta-clang = "HEAD:2b7433611d80f6d0ee1b04156fa91fc73d3c2665" meta-gnome meta-networking meta-filesystems = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-qt6 = "HEAD:586a6cb5aec755803a3be3cec359baafe89d6432" meta-parsec meta-tpm = "HEAD:459d837338ca230254baa2994f870bf6eb9d0139" meta-virtualization = "HEAD:6f3c1d8f90947408a6587be222fec575a1ca5195" Sstate summary: Wanted 5226 Local 0 Mirrors 0 Missed 5226 Current 2598 (0% match, 33% complete)############################################### | ETA: 0:00:01Initialising tasks: 100% |##################################################################################################################################| Time: 0:00:15NOTE: Executing Tasks ERROR: git-native-2.44.1-r0 do_compile: oe_runmake failed ERROR: git-native-2.44.1-r0 do_compile: ExecutionError('/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/temp/run.do_compile.12690', 1, None, None) ERROR: Logfile of failure stored in: /mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/temp/log.do_compile.12690 Log data follows: | DEBUG: Executing python function autotools_aclocals | DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common'] | DEBUG: Python function autotools_aclocals finished | DEBUG: Executing shell function do_compile | NOTE: make -j 16 NO_PYTHON=1 CFLAGS=-isystem/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/include -O2 -pipe LDFLAGS=-L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-O1 -Wl,--allow-shlib-undefined -Wl,--dynamic-linker=/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 -pthread PERL_PATH=/usr/bin/env perl COMPUTE_HEADER_DEPENDENCIES=no NO_GETTEXT=1 NO_CROSS_DIRECTORY_HARDLINKS=1 | * new build flags | CC oss-fuzz/dummy-cmd-main.o | /bin/sh: 1: cc: not found | CC oss-fuzz/fuzz-commit-graph.o | /bin/sh: 1: cc: not found | make: *** [Makefile:2735: oss-fuzz/dummy-cmd-main.o] Error 127 | make: *** Waiting for unfinished jobs.... | make: *** [Makefile:2735: oss-fuzz/fuzz-commit-graph.o] Error 127 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. ERROR: Task (virtual:native:/mnt/disks/yocto_disk/imx-yocto-bsp/sources/poky/meta/recipes-devtools/git/git_2.44.1.bb:do_compile) failed with exit code '1' Re:git-nativeコンパイルエラーでimx-image-fullのビルドに失敗しました これらを追加した後、なんとか成功裏にビルドすることができました。 それらがないと、curl-configとgit-guiの問題が発生しました。 sudo apt install libcurl4-openssl-dev libssl-dev gettext tcl-dev Re:git-nativeコンパイルエラーでimx-image-fullのビルドに失敗しました 「imx-yocto-bsp_scarthgap/build/tmp/work/x86_64-linux/git-native/2.44.1/git-2.44.1」フォルダに移動し、以下のコマンドが正常に実行できるかどうかを確認してください。 $ make distclean $ make -j 4 NO_PYTHON=1 CFLAGS='-isystem/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/include -O2 -pipe' LDFLAGS='-L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -L/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,--enable-new-dtags -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath-link,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/usr/lib -Wl,-rpath,/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/work/x86_64-linux/git-native/2.44.1/recipe-sysroot-native/lib -Wl,-O1 -Wl,--allow-shlib-undefined -Wl,--dynamic-linker=/mnt/disks/yocto_disk/imx-yocto-bsp/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 -pthread' PERL_PATH='/usr/bin/env perl' COMPUTE_HEADER_DEPENDENCIES=no NO_GETTEXT=1 NO_CROSS_DIRECTORY_HARDLINKS=1 Re:git-nativeコンパイルエラーでimx-image-fullのビルドに失敗しました はい、git-native は sources/poky/meta/conf/bitbake.conf ファイルの一部です。 ASSUME_PROVIDED = "\ bash-native \ bzip2-native \ chrpath-native \ diffstat-native \ file-native \ findutils-native \ gawk-native \ git-native \ grep-native \ hostperl-runtime-native \ hostpython-runtime-native \ libgcc-native \ patch-native \ sed-native \ tar-native \ texinfo-native \ virtual/crypt-native \ virtual/libiconv-native \ virtual/libintl-native \ wget-native \ " これは、bitback git-native コマンドの出力です。 ubuntu@yocto-build-server:/mnt/disks/yocto_disk/imx-yocto-bsp$ bitbake git-native WARNING: Host distribution "ubuntu-24.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache: 100% |#######################################################################################################################################| Time: 0:00:02Loaded 5730 entries from dependency cache. Parsing recipes: 100% |#####################################################################################################################################| Time: 0:00:00Parsing of 3654 .bb files complete (3653 cached, 1 parsed). 5731 targets, 377 skipped, 3 masked, 0 errors. WARNING: Explicit target "git-native" is in ASSUME_PROVIDED, ignoring NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.8.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "aarch64-poky-linux" MACHINE = "imx8mp-lpddr4-evk" DISTRO = "fsl-imx-xwayland" DISTRO_VERSION = "6.6-scarthgap" TUNE_FEATURES = "aarch64 armv8a crc crypto" TARGET_FPU = "" meta meta-poky = "HEAD:200d12b6a58ad961d60a7774ca0f7a9d29498724" meta-oe meta-multimedia meta-python = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-freescale = "HEAD:0627128b341cfb2bef7a0832ce8cac0ce1127f13" meta-freescale-3rdparty = "HEAD:6c063450d464eb2f380443c7d9af1b94ce9b9d75" meta-freescale-distro = "HEAD:b9d6a5d9931922558046d230c1f5f4ef6ee72345" meta-imx-bsp meta-imx-sdk meta-imx-ml meta-imx-v2x = "HEAD:219f6d04a4c339eb6f2dc626f944bbdf9a716ff5" meta-nxp-demo-experience = "HEAD:e8e646e22b1f926aac83bb7ad522efa9cd8ccc45" meta-nxp-matter-baseline meta-nxp-openthread = "HEAD:f58365ec75a5768ff3e8e8bcd64f237738c93160" meta-arm meta-arm-toolchain = "HEAD:950a4afce46a359def2958bd9ae33fc08ff9bb0d" meta-clang = "HEAD:2b7433611d80f6d0ee1b04156fa91fc73d3c2665" meta-gnome meta-networking meta-filesystems = "HEAD:72018ca1b1a471226917e8246e8bbf9a374ccf97" meta-qt6 = "HEAD:586a6cb5aec755803a3be3cec359baafe89d6432" meta-parsec meta-tpm = "HEAD:459d837338ca230254baa2994f870bf6eb9d0139" meta-virtualization = "HEAD:6f3c1d8f90947408a6587be222fec575a1ca5195" Summary: There were 2 WARNING messages. Re:git-nativeコンパイルエラーでimx-image-fullのビルドに失敗しました yoctoのレシピは修正しましたか? sources/poky/meta/conf/bitbake.conf の "ASSUME_PROVIDED" リストに "git-native" が載っているか確認してください。 コマンド "bitbake git-native"を実行すると、出力はどうなりますか? Re:git-nativeコンパイルエラーでimx-image-fullのビルドに失敗しました おかげで、しかし、これらのパッケージはすべてすでに私のシステムにインストールされています。 ubuntu@yocto-build-server:~$ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential utils-ping python3-git python3-jchrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils パッケージリストを読み込んでいます...ドニオン3-j inja2 python3-subunit zstd liblz4-toolファイル 依存関係ツリーを構築しています...完成です ステート情報を読み取っています...完成です gawkはすでに最新バージョン(1:5.2.1-2build3)です。 wgetはすでに最新バージョン(1.21.4-1ubuntu4.1)です。 gitはすでに最新バージョンです(1:2.43.0-1ubuntu7.2)。 diffstat はすでに最新バージョン (1.66-1build1) です。 解凍はすでに最新バージョン(6.0-28Ubuntu4.1)です。 texinfoはすでに最新バージョン(7.1-3build2)です。 gccはすでに最新バージョンです(4:13.2.0-7ubuntu1)。 build-essentialはすでに最新バージョン(12.10Ubuntu1)です。 0 がアップグレードされ、0 が新しくインストールされ、0 が削除され、0 がアップグレードされません。 Re:git-nativeコンパイルエラーでimx-image-fullのビルドに失敗しました OpenEmbedded-Core では、 :term:'ASSUME_PROVIDED' は主にネイティブ ビルドすべきではないツール。例としては ''git-native'' があります。 指定すると、ホストからの Git バイナリを使用できるようになります 「gitネイティブ」を構築するのではなく。 ホストPCに以下のパッケージをインストールしてください。 $ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential python3-pip python3-pexpect xz-utils debianutils python3-git python3-jinja2 python3-subunit zstd liblz4-toolファイル ロケール libacl1