使用 imx-secure-enclave 库进行 AES 加密/解密 我正在尝试使用 hsm_do_cipher 或 hsm_cipher_one_go 之类的工具来使用 AES 256 加密少量数据（32 字节）。 当我尝试 hsm_do_cipher 时，我收到一个错误，提示句柄不好。如果我使用 hsm_cipher_one_go，我会收到错误参数错误。 我尝试使用此代码来创建我的测试： https://github.com/nxp-imx/imx-secure-enclave/blob/1130c8bb820881ad037ba3f060e7fa70635fae3c/test/hsm/hsm_test.c#L620 我从 hsm_cipher_one_go 收到此错误： SAB Error: SAB CMD [0x62] Resp [0x429] - MU sanity check failed / Invalid parameters. aesencrypt: aesencrypt.c:164: hsm_do_cipher failed, err=0x4 有没有办法确定我的参数出了什么问题？当我在单独的程序中创建密钥时，没有看到任何错误。文件在 /etc/ele 下创建。 这是我设置 cipher_args 的代码： memset(&cipher_args,0,sizeof cipher_args); cipher_args.key_identifier = KEYID; cipher_args.iv = SM2_IDENTIFIER; cipher_args.iv_size = sizeof(SM2_IDENTIFIER); cipher_args.flags = HSM_CIPHER_ONE_GO_FLAGS_ENCRYPT; cipher_args.cipher_algo = HSM_CIPHER_ONE_GO_ALGO_ECB; cipher_args.input = sp; cipher_args.input_size = slength; cipher_args.output = od; cipher_args.output_size = slength; FRDM 培训 回复：使用 imx-secure-enclave 库进行 AES 加密/解密 我找到了可以使用的代码： https://github.com/nxp-imx/imx-secure-enclave/blob/1130c8bb820881ad037ba3f060e7fa70635fae3c/test/common/test_cipher.c#L295 我发现 8 个字节的输入数据会导致函数 hsm_do_hash() 失败并显示无效参数消息。16 个字节确实有效。 如果 key_identifier 要求明确说明就好了，iv_size 没有限制，input_size 也没有限制。 回复：使用 imx-secure-enclave 库进行 AES 加密/解密 应该是： 如果（se_get_soc_id（）==SOC_IMX95） 以下是跳过我想在 i.MX91 上执行的操作的代码： https://github.com/nxp-imx/imx-secure-enclave/blob/1130c8bb820881ad037ba3f060e7fa70635fae3c/test/common/test_cipher.c#L329 回复：使用 imx-secure-enclave 库进行 AES 加密/解密 我看到我复制的测试在开头有这个： f（se_get_soc_id（）==SOC_IMX95） 执行密码流不透明密钥测试（key_store_hdl，key_mgmt_hdl）； 因此这可能会阻止该测试在 i.MX91 上运行。那么为什么 imx95 上存在过滤器？您可以在 i.MX91 上使用带有 AES 加密的密钥库吗？有例子吗？

FlexCAN asserts due to FreeRTOS nesting violation Hello, I have the following setup: S32DS v3.5.12 RTD (P03, AR v4.7.0, SW v2.0.0) FreeRTOS 10.5.1 v2.0.0 S32K148 MCU I use a project that depends on the following drivers FlexCAN FreeRTOS BaseNXP (selects OsifFreeRtosType) others (may not be relevant to the potential bug) When I debug the application I observe that it ends up in an assert statement through the following sequence of function calls: ISR(CAN0_ORED_0_15_MB_IRQHandler) RTD/src/FlexCAN_Ip_Irq.c at line 214 FlexCAN_IRQHandler( ... ) RTD/src/FlexCAN_Ip.c at line 2926 FlexCAN_IRQHandlerRxMB RTD/src/FlexCAN_Ip.c at line 1342 can_RX_TX_callback custom callback for to handle CAN RX/TX events, located inside the project folder calls FlexCAN_Ip_Receive FlexCAN_Ip_Receive RTD/src/FlexCAN_Ip.c at line 2046 FlexCAN_SetMsgBuffIntCmd RTD/src/FlexCAN_Ip_HwAccess.c at line 1053 SchM_Enter_Can_43_FLEXCAN_CAN_EXCLUSIVE_AREA_18 RTD/src/SchM_Can_43_FLEXCAN.c at line 1125 OsIf_SuspendAllInterrupts RTD/include/OsIf_Internal.h at line 274 SuspendAllInterrupts RTD/include/OsIf_Internal.h at line 247 taskENTER_CRITICAL FreeRTOS/Source/Include/task.h at line 210 portENTER_CRITICAL FreeRTOS/Source/portable/GCC/ARM_CM4F/portmacro.h at line 105 vPortEnterCritical FreeRTOS/Source/portable/GCC/ARM_CM4F/port.c at line 425 configASSERT See also the debug session call sequence Now I found a similar ticket where one NXP tech-support employee labels this issue as a bug, which may be resolved in a future RTD package release. To be sure, can you confirm that this is a bug in the RTD driver present a workaround I have tried to replace the portENTER_CRITICAL call by portENTER_CRITICAL_FROM_ISR (same for the EXIT version) in the local RTD folder in the header file Osif_Internal.h and in the RTD installation folder (S32DS.3.5\S32DS\software\PlatformSDK_S32K1_S32M24\RTD\BaseNXP_TS_T40D2M20I0R0\include\Osif_Internal.h) But then I get another build error (Description Resource Path Location Type too few arguments to function 'vPortSetBASEPRI' portmacro.h /__FreeRTOS_Toggle_Led_Example_S32K148__/FreeRTOS/Source/portable/GCC/ARM_CM4F line 102 C/C++ Problem) point out if this is resolved by the RTD P04 package or when you plan to release package which fixes this isse Best regards, M_SCH S32 SDK for S32K1 Re: FlexCAN asserts due to FreeRTOS nesting violation Hello, one more thing. My current implementation relies on the FlexCAN_Ip_Receive function using interrupts. Which of the following options would you recommend for a temporary fix: 1. Modify the Osif_Internal.h file (so that it matches the implementation of the RTD AR 4.4.0, SW 1.0.0): #define ResumeAllInterrupts() ASM_KEYWORD(" cpsie i") #define SuspendAllInterrupts() ASM_KEYWORD(" cpsid i")​ 2. Use FlexCAN_Ip_ReceiveBlocking - keep in mind that I have multiple message buffers to query. Best regards, M_SCH Re: FlexCAN asserts due to FreeRTOS nesting violation Hello Petr, thanks for the information! Best regards, M_SCH Re: FlexCAN asserts due to FreeRTOS nesting violation Hi, yes, this is RTD issue and will be fixed with next RTD release. It should be version 3.0.0, not sure of the release plan. Not able to comment more. BR, Petr

S32G2 load dtb I got dts both in ATF and in kernal.When the board boots,Which dtb it will actually use?Or it will load both? Thank u. Re: S32G2 load dtb Hi, Both DTB/DTS will be used. When booting, TF-A/uboot will use the TF-A DTS/DTB, when uboot passes the control to the kernel, the kernel will use its own DTB/DTS. There is no conflict between both. Both DTB/DTS should be configured accordingly, if not when uboot passes control to the kernel, devices might not be available to the kernel itself. Please, let us know. Re: S32G2 load dtb Sorry，I can not understand well and could you describe it more detailed.I can find the same device in DTS both in ATF and kernal. Do they conflict with each other? Re: S32G2 load dtb Hi, Both DTB's will be used at the end, but the one that is available under the root partition of the SD card should be the Kernel one. Please, let us know.

Cannot find the sample file "S32K144_PT2000_EXAMPLE" Hello, I am a newcomer to S32 and the NXP community. I am currently using the FRDMPKPT2000EVM evaluation board (EVB) and trying to use the example file "S32K144_ST2000_XAMPLE". But I couldn't find the corresponding file on the official website. I only found the file 'Basic-FRDMPKPT2000EVM.zip' and cannot open it according to the tutorial. Can someone help me solve it? Thank you in advance Solenoid Controller Re: Cannot find the sample file "S32K144_PT2000_EXAMPLE" Thank you very much，Jozef，this is exactly what I need. Re: Cannot find the sample file "S32K144_PT2000_EXAMPLE" Hi Minglong, I apologize for not working link in the KTFRDMPKPT2000EVM User Guide, I will report this issue. The link should bring you to the FRDMPKPT2000EVM product page. The S32K144_PT2000_EXAMPLE.zip is the file under the Software section. Please also find the file attached.  With Best Regards, Jozef Re: Cannot find the sample file "S32K144_PT2000_EXAMPLE" Hi Jozef, Thanks for replying.I would like to rephrase the issue I encountered. I am currently studying the article "KFRDMPKPT2000EVM Evaluation Board Rev. 1.0-7 December 2016 User Guide" and have completed the installation steps for S32 Design Studio as described in section 6.2.1.1. Then, in section 6.2.1.2,the article states that---To download the example file, do the following: 1. Go to the Tool Summary Page at http://www.nxp.com/FRDMPKPT2000EVM and click on the Jump Start icon. 2. Locate and download the zip file named S32K144_PT2000_EXAMPLE.zip. 3. Unzip this file into a folder on the computer that has the S32 Design Studio installed。 I just couldn't find the example file mentioned in the second point.I have already downloaded the first file in the first image you sent before, but importing this file into S32DS does not match the example image provided in the article. I apologize if I misunderstood something. With Best Regards. Re: Cannot find the sample file "S32K144_PT2000_EXAMPLE" Hello Minglong, please point me to the tutorial you are referring to. The software, including the examples can be found in the FRDMPKPT2000EVM product page and on the KITPT2000FRDM3C product page.  With Best Regards, Jozef

Regarding Boot Configuration Settings on MIMXRT1170 Dear NXP Support Team, I have a couple of questions regarding the boot configuration settings for our project: Can we use BOOT_CFG[0:11] as individual functions when booting from fuses? When using the "Boot from Fuses" settings, do the BOOT_CFG[0:11] pins need to be pulled down or set to any specific state? I have attached images for your reference. Please update me as soon as possible. Your assistance in clarifying these points would be greatly appreciated. I appreciate your support. Best regards, Sagar Re: Regarding Boot Configuration Settings on MIMXRT1170 Fuses cannot be re-written. It is suggested to use the fuse configuration once you are completely sure that the parameters are correct.  Even with the fuse configuration you are able to enter serial download mode if boot_mode pin is available.  The ROM will behave like this: Boot_Mode is configured in Boot From Fuses (b00) - BT_FUSE_SEL = 0, No application in boot device, BootROM enters serial downloader mode - BT_FUSE_SEL = 1, valid application in boot device, BootROM gets all boot device info from fuse Boot_Mode is configured in Internal Boot (b10) - BT_FUSE_SEL = 0, valid application in boot device, BootROM gets boot device info from boot_cfg pins. - BT_FUSE_SEL = 1, valid application in boot device, BootROM gets all boot device info from fuse Best regards, Omar Re: Regarding Boot Configuration Settings on MIMXRT1170 Hello @Omar_Anguiano , Thank you for the quick reply. I have another query: if we use Boot from Fuses, can we change it later if we want to? Is Serial Downloader and Internal Boot compulsory? If we set the fuses, can we change the fuse settings afterward? In the reference design file, it is mentioned that the Boot Mode selection header should be used only during the development phase. We use Boot Selection settings during the development phase, but after finalizing the production phase, we switch to Boot from Fuses. What happens if we want to change the bootloader and firmware again after setting Boot from Fuses? Thanks  Sagar Re: Regarding Boot Configuration Settings on MIMXRT1170 If using boot from fuses then the boot_cfg pins can be used for other purpose as the ROM will read the values from the fuses instead of the GPIOs. The state of the pins can be as a normal pin as the state of the GPIO will not be read on that mode. Best regards, Omar

S32K116 LSPI 请问一下： S32K116这款芯片在使用S32DS配置LSPI组件的情况下目前采用默认的配置方式为同步传输，导致CPU运行效率低，通信等待时间很长。请问如何实现LSPI组件的异步通信，是需要自己模拟异步通信还是可以通过配置实现？ 当前LSPI是通过LSPI_Config组件，采用中断形式配置 感谢！ Re: S32K116 LSPI 我找到这个实例工程了，非常感谢 Re: S32K116 LSPI 请问我该如何获取这个安装包，我在我的S32DS软件中查找可用的拓展更新时并没有发现这个RTD。我找到的类似的安装包是给EB Tresos软件安装的。感谢您的帮助

サンプル ファイル "S32K144_PT2000_EXAMPLE" が見つかりません こんにちは、私はS32とNXPコミュニティの新参者です。私は現在FRDMPKPT2000EVM評価ボード（EVB）を使用しており、サンプルファイル " S32K144_ST2000_XAMPLE " を使用しようとしています。しかし、公式サイトで対応するファイルが見つかりませんでした。ファイル「Basic-FRDMPKPT2000EVM.zip」しか見つかりませんでした。チュートリアルに従って開くことができません。 誰かが私がそれを解決するのを手伝ってくれますか?よろしくお願いいたします ソレノイドコントローラー Re:サンプルファイル「S32K144_PT2000_EXAMPLE」が見つかりません どうもありがとうございました、ヨゼフ、これはまさに私が必要としているものです。

找不到示例文件“S32K144_PT2000_EXAMPLE” 您好，我是 S32 和 NXP 社区的新人。我目前正在使用FRDMPKPT2000EVM评估板（EVB）并尝试使用示例文件“S32K144_ST2000_XAMPLE”。但是在官网上没找到相应的文件。我只找到文件“Basic-FRDMPKPT2000EVM.zip”并且无法按照教程打开它。 有人能帮我解决吗？先感谢您 电磁阀控制器 回复：找不到示例文件“S32K144_PT2000_EXAMPLE” 非常感谢，Jozef，这正是我需要的。

LS1043a and LS1046a botting from QSPI MRAM Hello, I am working on a custom board that will use either the LS1043A or the LS1046A, exactly which processor is TBD and I need some clarification on QSPI-boot hardware requirements. The current thinking is to boot from QSPI using a non-volatile serial MRAM module. My questions are: 1) Can I boot from a serial MRAM module connected to QSPI? Or does it have to be flash for QSPI-boot? 2) If I use the QSPI interface to boot but I set the RCW values in the PBI such that the QSPI interface is not used during normal operation, will I be able to use all IFC pins as IFC pins? Or, if I boot from QSPI are those pins permanently muxxed to QSPI during normal operation? 3) If it's possible to boot from QSPI using MRAM, are there any special procedures we need to follow in code to make that work? Thank you  Re: LS1043a and LS1046a botting from QSPI MRAM Hello, Q1) Flash is recommended as boot-source. Q2)Once you set the pins in the RCW you cannot change the mux without updating the RCW and re-boot. Q3)It should be possible, not recommended as boot source and it only have to meet the requirements for the QSPI boot in the RM.

iMxRT1040 Boot FlexSPI and DQS Hi, I have a problem with my configuration to fit all the required peripherals. I plan to use external Quad SPI NOR Flash with no Strobe. (as the EVK). I need to use : CCM.CLKO1 [J4] and CCM.CLKO2 [J1]. I need one FlexSPI (for ext Flash) and one uSDHC for SdCard. The 2 clocks outputs prevent me from using uSDHC1. Then, I have to use uSDHC2 for the SdCard that has the CMD signal on [M4]. The [M4] pin is shared with FLEXSPI.A_DQS. What's the best way to use SdCard and boot on FlexSPI ? Can I boot easily on FLEXSPI2.A ? or should I use FlexSPI1.A with internal loopback Strobe ? Thanks in advance, Re: iMxRT1040 Boot FlexSPI and DQS Hi @jfz_arturia , Thank you for your interest in the NXP MIMXRT product, I would  like to provide service for you. Question: Can I boot easily on FLEXSPI2.A ? Answer: No, You can't.  In IMXRT1040RM reference manual, You can see that NOR Flash can only be  boot on FlexSPI1 Question: or should I use FlexSPI1.A with internal loopback Strobe ? Answer:  You can use this mode, but the max Frequency of operation is limited to 60MHz if you use this mode . https://www.nxp.com/webapp/Download?colCode=IMXRT1040RM https://www.nxp.com/docs/en/data-sheet/IMXRT1040CEC.pdf Wish it helps you. If you still have question about it, please kindly let me know. Wish you a nice day! Best Regards MayLiu

如何在 NXP YOCTO 中 insmod 模块和 mknod 设备节点 我正在使用的 iMX93-11x11-evk 板，最近我检查了 rtc（pcf2131）模块（gpio28 和 gpio29 pinmux 作为 I2C3 SCL 和 SDA），发现没有 device_create 接口来创建设备节点。所以我认为存在某个地方可以执行这些命令： insmod/modprobe 和 mknod ，但我现在还没有找到，并且在互联网上也没有找到相应的文档/网络链接。 我在源目录中执行了 cmd：grep -irn“mknod”和 grep“insmod”，没有返回结果 因此请给我一些线索或参考文档/网络链接来帮助我。 回复：如何在 NXP YOCTO 中 insmod 模块和 mknod 设备节点 让我们探索如何处理 i.MX93-11x11-evk 板上的内核模块（驱动程序）和设备节点。我将提供有关使用 insmod、modprobe 和创建设备节点的指导。 内核模块（驱动程序）： 内核模块扩展了 Linux 内核的功能。它们允许您添加对新硬件、文件系统或系统调用的支持。 insmod 和 modprobe 命令用于插入和管理内核模块。 使用 insmod： insmod 命令将模块插入正在运行的内核。 例子： 须藤 insmod /path/to/module.ko 将 /path/to/module.ko 替换为模块文件 (.ko) 的实际路径。 使用 modprobe： modprobe 比 insmod 更强大。它自动解决模块依赖关系。 例子： sudo modprobe 模块名称 将 module_name 替换为您的模块名称（不带 .ko扩大）。 创建设备节点（mknod）： 设备节点是 /dev 目录中代表设备的特殊文件。 要创建设备节点，请使用 mknod 命令。 例子： sudo mknod /dev/mydevice c 123 0 这将创建一个名为 /dev/mydevice 的字符设备节点，其主设备号为 123，次设备号为 0。 文档和参考文献： 不幸的是，我找不到与 i.MX93-11x11-evk 板相关的具体文档或网络链接。 但是，您可以参考有关内核模块和设备节点的常规 Linux 文档： Linux内核模块编程指南 Linux设备驱动程序 此致， AARP 会员

PN7642 SPIA master mode Hello!  I am using PN7642. I would like to ask is it possible to use SPI that is connected to host interface pins ATX_A, ATX_B, ATX_C, ATX_D in master mode or it can be configured only to work in slave mode?  Thanks in advance!  Artem Re: PN7642 SPIA master mode Thank you! Re: PN7642 SPIA master mode Hello @artem_pn Hope you are doing well. Host Interface pins may be intended for SPI target functionality. SPI controller should have dedicated pins according to PN7642 Data Sheet, Section 8 pinning information. Regards, Eduardo.

How to insmod modules and mknod device nodes in NXP YOCTO iMX93-11x11-evk board I'm using, recently I checked the rtc(pcf2131) module(gpio28 & gpio29 pinmux as I2C3 SCL & SDA), found no device_create interface to create device node. So I think that there exists someplace to execute the commands: insmod/modprobe & mknod, but I've not found now yet, and no corresponding docs/weblinks found from internet. I excuted cmd: grep -irn "mknod" & grep "insmod" in the sources dir, no results returned So pls support me some clues or referenced docs/weblinks to help me out. Re: How to insmod modules and mknod device nodes in NXP YOCTO Let’s explore how to handle kernel modules (drivers) and device nodes on your i.MX93-11x11-evk board. I’ll provide guidance on using insmod, modprobe, and creating device nodes. Kernel Modules (Drivers): Kernel modules extend the functionality of the Linux kernel. They allow you to add support for new hardware, filesystems, or system calls. The insmod and modprobe commands are used to insert and manage kernel modules. Using insmod: The insmod command inserts a module into the running kernel. Example: sudo insmod /path/to/module.ko Replace /path/to/module.ko with the actual path to your module file (.ko). Using modprobe: modprobe is more powerful than insmod. It automatically resolves module dependencies. Example: sudo modprobe module_name Replace module_name with the name of your module (without the .ko extension). Creating Device Nodes (mknod): Device nodes are special files in the /dev directory that represent devices. To create a device node, use the mknod command. Example: sudo mknod /dev/mydevice c 123 0 This creates a character device node named /dev/mydevice with major number 123 and minor number 0. Documentation and References: Unfortunately, I couldn’t find specific documentation or weblinks related to the i.MX93-11x11-evk board. However, you can refer to general Linux documentation on kernel modules and device nodes: Linux Kernel Module Programming Guide Linux Device Drivers Best Regards, aarp-membership

NXP YOCTOでモジュールとデバイスノードをインモッドする方法 私が使用しているiMX93-11x11-evkボードは、最近、rtc(pcf2131)モジュール(gpio28 & gpio29 pinmux as I2C3 SCL & SDA)を確認しましたが、デバイスノードを作成するためのdevice_createインターフェイスが見つかりませんでした。ですから、コマンドを実行する場所がどこかに存在すると思います: insmod/modprobeとmknodですが、まだ見つかっておらず、インターネットから対応するドキュメント/ウェブリンクも見つかりませんでした。 ソースディレクトリでcmd: grep -irn "mknod" と grep "insmod" を実行しましたが、結果は返されませんでした それで、私を助けるための手がかりや参考になるドキュメント/ウェブリンクを教えてください。 Re: NXP YOCTOでモジュールとデバイスノードをインモッドする方法 i.MX93-11x11-EVKボードでカーネルモジュール（ドライバー）とデバイスノードを処理する方法を見てみましょう。insmod、modprobeの使い方、デバイスノードの作成に関するガイダンスを提供します。 カーネルモジュール（ドライバー）： カーネルモジュールはLinuxカーネルの機能を拡張します。新しいハードウェア、ファイルシステム、またはシステムコールのサポートを追加できます。 insmodとmodprobeコマンドは、カーネルモジュールの挿入と管理に使用されます。 insmodの使用： insmodコマンドは、実行中のカーネルにモジュールを挿入します。 例: sudo insmod /path/to/module.ko /path/to/module.koを、モジュールファイル（.ko）への実際のパスに置き換えてください。 modprobeの使用： modprobeはinsmodよりも強力です。モジュールの依存関係を自動的に解決します。 例: sudo modprobe モジュール名 module_nameをあなたのモジュールの名前に置き換えてください（.koは除きます）拡張子)。 デバイスノードの作成（mknod）： デバイスノードは、/devディレクトリにあるデバイスを表す特別なファイルです。 デバイスノードを作成するには、mknodコマンドを使います。 例: sudo mknod /dev/mydevice c 123 0 これにより、メジャー番号123、マイナー番号0の/dev/mydeviceという名前のキャラクターデバイスノードが作成されます。 ドキュメントと参考資料： 残念ながら、i.MX93-11x11-EVKボードに関連する特定のドキュメントやウェブリンクは見つかりませんでした。 ただし、カーネルモジュールとデバイスノードに関する一般的なLinuxドキュメントを参照できます。 Linuxカーネルモジュールプログラミングガイド、 Linuxデバイスドライバー、 よろしく、 aarpメンバーシップ

CAN FD bus off state S32k146 Hi, We need to implement a CAN FD communication with 1Mb/s as bitrate. Unfortunately it's not working. The data would be written correct in the RAM, but in Canoe there is no message incomming. I've attached the ESR1, the CAN_init and a function to send a message. Hope you can help me. Sandra Re: CAN FD bus off state S32k146 Hi Petr, thx for your reply. We tested the FlexCAN example, but with the same failures. We detect, that our controller has some issues with the soldering pads. Best regards Sandra Re: CAN FD bus off state S32k146 Hi, seems you are detecting bit errors during transmission which leads to entering bus off state and recovering and so on. A cause of bit error detection can be various, most often inactive CAN transceiver, incorrect bit rate setting, etc.  It would be great to measure TX/RX and CAN line with scope-analyzer to see real signal as well. For your code, seems you have wrong setting for CBT register. I can recommend to use below tool which helps you with calculation https://community.nxp.com/t5/MPC5xxx-Knowledge-Base/MPC5xxx-S32Kxx-LPCxxxx-CAN-CAN-FD-bit-timing-calculation/ta-p/1119319 BR, Petr

S32k310 RTDs port on TCM memories Hi There, I would run some deterministic Functions on TCM, and by consecuence some RTDs (ADC, PWM,...). I noticed, in *Memmap.h files,  that mcal_* linker sections  are spread in few linker sections; for example some sections are cacheable other non  canheable and other unknown sections. I read the RTD IM and UM manuals but there is no info about TCM topic Is there some documentation to port RTDs memory section on I/D TCMs ? NB Also, in s321k310 there is 16kb of SRAM and 64k od DTCM, so an efficient  and accurate partiting of data memory  mapping is almost necessary in any case. Best Regards Fabio  Best Regards Fabio Re: S32k310 RTDs port on TCM memories Hi@FabioG Please refer to the attachment.

I2C MPC5478G こんにちは、MPC5748Gを使ってアンプと通信したいです。パワー・アーキテクチャーのi2c_transfer_mpc5748gのサンプルコードを使っています。アンプのアドレスは0x70です。これを実現するにはどのような変更が必要ですか？また、 i2Cドライバーはアドレス-> データを送信しますが、私はそれをアンプ（アドレス）-> アンプレジスタ（サブアドレス）-> データのアドレスにしたいです。

i.MXRT1176 SAI1 Data channels 2,3,4 & fifo combine Hi there.  I'm trying to use as many SAI data pins as possible on the RT1176.  I am aware that for SAI 1 data channels 2, 3, and 4, the Tx and Rx data lines share a pin, and so can only be assigned to Tx or Rx. Lets try and use all 3 of them all for Tx anyway.. So my configuration is  SAI 1 pins: - Tx1 - Rx1 - Tx2 - Tx3 - Tx4 Using the config tool, I do this on the 'playback' tab Then I generate the code and run, but I hit an assert in fsl_sai_edma.c: #if defined(FSL_FEATURE_SAI_HAS_FIFO_COMBINE_MODE) && FSL_FEATURE_SAI_HAS_FIFO_COMBINE_MODE /* Allow multi-channel transfer only if FIFO Combine mode is enabled */ assert( (saiConfig->channelNums <= 1U) || ((saiConfig->channelNums > 1U) && ((saiConfig->fifo.fifoCombine == kSAI_FifoCombineModeEnabledOnWrite) || (saiConfig->fifo.fifoCombine == kSAI_FifoCombineModeEnabledOnReadWrite)))); #endif   This suggests that you MUST use fifo combine if you use more than 1 SAI data channel. The manual states (p.3475): Combining FIFOs for transmit data channels allows one data channel to use the FIFOs of all enabled channel FIFOs, with identical data output on each enabled data channel. Combining FIFOs for receive data channels allows one data channel to use the FIFOs of all enabled channel FIFOs, with received data from channel 0 stored into each enabled data channel. This suggest that if using SAI 1 data pin2, 3, or 4 for Tx, they will all just output the same data as on pin1?! And if using them for Rx... well it doesn't say but it sounds like pins 2,3 and 4 will be ignored? Can you please clarify this or point me to some more detailed documentation?  Are SAI1 data pins 2,3,4 independently usable at all?   Many thanks. Re: i.MXRT1176 SAI1 Data channels 2,3,4 & fifo combine Thanks for the reply, I tested this today and it appears to work as described. It would be really useful to have this functionality detailed in the SAI FIFO combine section of the RT1176 ref manual because it currently reads as though it is not possible to have different data on different SAI 1 pins. Many thanks Re: i.MXRT1176 SAI1 Data channels 2,3,4 & fifo combine Hello @mttjcksn, I highly recommend consulting this application note, where the multi-channel functionality is explained in greater detail. Additionally, the FCOMB register indicates the following: This means that the FIFO will store data for each enabled channel. Also, if you exprience any issue, do not hesitate to let me know. BR Habib

LSDK21.08 LS1043AQDS SETUP Hello, Wang. With your help, my board ls1043aqds has entered uboot. I use LSDK 21.08 for development, and the boot mode is TF-A. But my qspi flash is small, only 16MB, so I can't write itb directly to flash and start kernel and ramdisk from qspi. I think the next priority is to burn the kernel and ramdisk into 16GB emmc, and then load the kernel from emmc. But I don't know if I have to use an external writer to burn emmc at the moment, and I don't know exactly what needs to be modified and compiled in the next work. I really hope to get your help and look forward to your reply as soon as possible. thank you. @yipingwang Re: LSDK21.08 LS1043AQDS SETUP Dear WANG,Thank you very much for your help, I can now enter the official ubuntu file system. Re: LSDK21.08 LS1043AQDS SETUP You need to modify LS1043AQDS device tree according to your custom board. In LSDK 21.08 build environment: $ source setup.env $ flex-builder -c linux -m ls1043aqds Go to Linux Kernel source code components/linux/linux, please modify arch/arm64/boot/dts/freescale/fsl-ls1043a-qds.dts according to your custom board. For example, please delete the following device node, if there is no IFC NOR flash on your custom board. nor@0,0 { compatible = "cfi-flash"; reg = <0x0 0x0 0x8000000>; big-endian; bank-width = <2>; device-width = <1>; }; Then rebuild Linux Kernel $ flex-builder -c linux -m ls1043aqds Regenerate itb image $ flex-builder -i mkitb -r yocto:tiny Get the image flexbuild_lsdk2108_github/build/images/lsdk2108_yocto_tiny_LS_arm64.itb If you need to the bootpartition image, please regenerate it with the following command $ flex-builder -i mkbootpartition -a arm64 Re: LSDK21.08 LS1043AQDS SETUP Wang,Thank you very much for your technical reply, and I am honored to get your help in debugging this series of boards for the first time. I have made some progress following your suggestions, but it seems that the kernel is stuck and cannot continue. I have attached the log, and I hope to get your help on what I should do next so that I can successfully enter ramdisk. @yipingwang  Re: LSDK21.08 LS1043AQDS SETUP The emmc device is not removable, you could copy all your images to the USB device, then boot up the target board with image lsdk2108_yocto_tiny_LS_arm64.itb and deploy Ubuntu rootfs to emmc device in Linux on the target board. For example under u-boot, => ext2load usb 0:1 0xa0000000 lsdk2108_yocto_tiny_LS_arm64.itb => bootm 0xa0000000#ls1043aqds Under Linux on the target board, please run the following commands to deploy Kernel and Ubuntu rootfs to emmc device. $ flex-installer -i pf -d /dev/mmcblk0 $ flex-installer -b boot_LS_arm64_lts_5.10.tgz -r rootfs_lsdk2108_ubuntu_main_arm64.tgz -d /dev/mmcblk0 Note:/dev/mmcblk0 is the emmc device name on the target board.

How qemu load dtb on LS2088ardb I'm buiding images for LS2088ardb by using Yocto command "bitbake fsl-image-networking" Now I load the dtb in the QEMU but can't boot into kernel and step by step SOP as below:  Open 2 terminals in my host PC (Ubuntu 20.04)  Use the command to run QEMU in first terminal: $ qemu-system-aarch64 \   -smp 8 \   -machine type=virt,gic-version=3 \   -m 2048 \   -cpu cortex-a72 \   -kernel Image \   -serial tcp::4446,server,telnet \   -drive if=none,file=fsl-image-networking-ls2088ardb.rootfs-20240711074828.ext4,id=foo,format=raw \   -device virtio-blk-device,drive=foo \   -append 'root=/dev/vda rw console=ttyAMA0,115200 rootwait earlyprintk' \   -monitor stdio Output as below QEMU 4.2.1 monitor - type 'help' for more information (qemu) qemu-system-aarch64: -serial tcp::4446,server,telnet: info: QEMU waiting for connection on: disconnected:telnet:0.0.0.0:4446,server Use the command to connect QEMU in second terminal: telnet 0.0.0.0 4446 I can success to boot into kernel Trying 0.0.0.0... Connected to 0.0.0.0. Escape character is '^]'. [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083] [ 0.000000] Linux version 6.6.23-gb586a521770e (oe-user@oe-host) (aarch64-fsl-linux-gcc (GCC) 13.2.0, GNU ld (GNU Binutils) 2.42.0.20240216) #1 SMP PREEMPT Fri Jun 7 13:15:57 UTC 2024 [ 0.000000] KASLR disabled due to lack of seed [ 0.000000] Machine model: linux,dummy-virt ... ... ls2088ardb login: root root@ls2088ardb:~# Trying to use the command to load device tree in first terminal $ qemu-system-aarch64 \ -smp 8 \ -machine type=virt,gic-version=3 \ -m 2048 \ -cpu cortex-a72 \ -kernel Image \ -serial tcp::4446,server,telnet \ -dtb fsl-ls2088a-rdb.dtb \ -drive if=none,file=fsl-image-networking-ls2088ardb.rootfs-20240711074828.ext4,id=foo,format=raw \ -device virtio-blk-device,drive=foo \ -append 'root=/dev/vda rw console=ttyAMA0,115200 rootwait earlyprintk' \ -monitor stdio Output as below QEMU 4.2.1 monitor - type 'help' for more information (qemu) qemu-system-aarch64: -serial tcp::4446,server,telnet: info: QEMU waiting for connection on: disconnected:telnet:0.0.0.0:4446,server Use the command to connect QEMU in second terminal Trying 0.0.0.0... Connected to 0.0.0.0. Escape character is '^]'. It stay here and can't boot into kernel I try to add debug info and step same as Step4-5 -d int,cpu_reset Output  CPU Reset (CPU 0) R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=00000000 PSR=40000000 -Z-- A usr26 CPU Reset (CPU 1) R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=00000000 PSR=40000000 -Z-- A usr26 CPU Reset (CPU 2) R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=00000000 PSR=40000000 -Z-- A usr26 CPU Reset (CPU 3) R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=00000000 PSR=40000000 -Z-- A usr26 CPU Reset (CPU 4) R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=00000000 PSR=40000000 -Z-- A usr26 CPU Reset (CPU 5) R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=00000000 PSR=40000000 -Z-- A usr26 CPU Reset (CPU 6) R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=00000000 PSR=40000000 -Z-- A usr26 CPU Reset (CPU 7) R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=00000000 PSR=40000000 -Z-- A usr26 CPU Reset (CPU 0) PC=0000000000000000 X00=0000000000000000 X01=0000000000000000 X02=0000000000000000 X03=0000000000000000 X04=0000000000000000 X05=0000000000000000 X06=0000000000000000 X07=0000000000000000 X08=0000000000000000 X09=0000000000000000 X10=0000000000000000 X11=0000000000000000 X12=0000000000000000 X13=0000000000000000 X14=0000000000000000 X15=0000000000000000 X16=0000000000000000 X17=0000000000000000 X18=0000000000000000 X19=0000000000000000 X20=0000000000000000 X21=0000000000000000 X22=0000000000000000 X23=0000000000000000 X24=0000000000000000 X25=0000000000000000 X26=0000000000000000 X27=0000000000000000 X28=0000000000000000 X29=0000000000000000 X30=0000000000000000 SP=0000000000000000 PSTATE=400003c5 -Z-- EL1h CPU Reset (CPU 1) PC=0000000000000000 X00=0000000000000000 X01=0000000000000000 X02=0000000000000000 X03=0000000000000000 X04=0000000000000000 X05=0000000000000000 X06=0000000000000000 X07=0000000000000000 X08=0000000000000000 X09=0000000000000000 X10=0000000000000000 X11=0000000000000000 X12=0000000000000000 X13=0000000000000000 X14=0000000000000000 X15=0000000000000000 X16=0000000000000000 X17=0000000000000000 X18=0000000000000000 X19=0000000000000000 X20=0000000000000000 X21=0000000000000000 X22=0000000000000000 X23=0000000000000000 X24=0000000000000000 X25=0000000000000000 X26=0000000000000000 X27=0000000000000000 X28=0000000000000000 X29=0000000000000000 X30=0000000000000000 SP=0000000000000000 PSTATE=400003c5 -Z-- EL1h CPU Reset (CPU 2) PC=0000000000000000 X00=0000000000000000 X01=0000000000000000 X02=0000000000000000 X03=0000000000000000 X04=0000000000000000 X05=0000000000000000 X06=0000000000000000 X07=0000000000000000 X08=0000000000000000 X09=0000000000000000 X10=0000000000000000 X11=0000000000000000 X12=0000000000000000 X13=0000000000000000 X14=0000000000000000 X15=0000000000000000 X16=0000000000000000 X17=0000000000000000 X18=0000000000000000 X19=0000000000000000 X20=0000000000000000 X21=0000000000000000 X22=0000000000000000 X23=0000000000000000 X24=0000000000000000 X25=0000000000000000 X26=0000000000000000 X27=0000000000000000 X28=0000000000000000 X29=0000000000000000 X30=0000000000000000 SP=0000000000000000 PSTATE=400003c5 -Z-- EL1h CPU Reset (CPU 3) PC=0000000000000000 X00=0000000000000000 X01=0000000000000000 X02=0000000000000000 X03=0000000000000000 X04=0000000000000000 X05=0000000000000000 X06=0000000000000000 X07=0000000000000000 X08=0000000000000000 X09=0000000000000000 X10=0000000000000000 X11=0000000000000000 X12=0000000000000000 X13=0000000000000000 X14=0000000000000000 X15=0000000000000000 X16=0000000000000000 X17=0000000000000000 X18=0000000000000000 X19=0000000000000000 X20=0000000000000000 X21=0000000000000000 X22=0000000000000000 X23=0000000000000000 X24=0000000000000000 X25=0000000000000000 X26=0000000000000000 X27=0000000000000000 X28=0000000000000000 X29=0000000000000000 X30=0000000000000000 SP=0000000000000000 PSTATE=400003c5 -Z-- EL1h CPU Reset (CPU 4) PC=0000000000000000 X00=0000000000000000 X01=0000000000000000 X02=0000000000000000 X03=0000000000000000 X04=0000000000000000 X05=0000000000000000 X06=0000000000000000 X07=0000000000000000 X08=0000000000000000 X09=0000000000000000 X10=0000000000000000 X11=0000000000000000 X12=0000000000000000 X13=0000000000000000 X14=0000000000000000 X15=0000000000000000 X16=0000000000000000 X17=0000000000000000 X18=0000000000000000 X19=0000000000000000 X20=0000000000000000 X21=0000000000000000 X22=0000000000000000 X23=0000000000000000 X24=0000000000000000 X25=0000000000000000 X26=0000000000000000 X27=0000000000000000 X28=0000000000000000 X29=0000000000000000 X30=0000000000000000 SP=0000000000000000 PSTATE=400003c5 -Z-- EL1h CPU Reset (CPU 5) PC=0000000000000000 X00=0000000000000000 X01=0000000000000000 X02=0000000000000000 X03=0000000000000000 X04=0000000000000000 X05=0000000000000000 X06=0000000000000000 X07=0000000000000000 X08=0000000000000000 X09=0000000000000000 X10=0000000000000000 X11=0000000000000000 X12=0000000000000000 X13=0000000000000000 X14=0000000000000000 X15=0000000000000000 X16=0000000000000000 X17=0000000000000000 X18=0000000000000000 X19=0000000000000000 X20=0000000000000000 X21=0000000000000000 X22=0000000000000000 X23=0000000000000000 X24=0000000000000000 X25=0000000000000000 X26=0000000000000000 X27=0000000000000000 X28=0000000000000000 X29=0000000000000000 X30=0000000000000000 SP=0000000000000000 PSTATE=400003c5 -Z-- EL1h CPU Reset (CPU 6) PC=0000000000000000 X00=0000000000000000 X01=0000000000000000 X02=0000000000000000 X03=0000000000000000 X04=0000000000000000 X05=0000000000000000 X06=0000000000000000 X07=0000000000000000 X08=0000000000000000 X09=0000000000000000 X10=0000000000000000 X11=0000000000000000 X12=0000000000000000 X13=0000000000000000 X14=0000000000000000 X15=0000000000000000 X16=0000000000000000 X17=0000000000000000 X18=0000000000000000 X19=0000000000000000 X20=0000000000000000 X21=0000000000000000 X22=0000000000000000 X23=0000000000000000 X24=0000000000000000 X25=0000000000000000 X26=0000000000000000 X27=0000000000000000 X28=0000000000000000 X29=0000000000000000 X30=0000000000000000 SP=0000000000000000 PSTATE=400003c5 -Z-- EL1h CPU Reset (CPU 7) PC=0000000000000000 X00=0000000000000000 X01=0000000000000000 X02=0000000000000000 X03=0000000000000000 X04=0000000000000000 X05=0000000000000000 X06=0000000000000000 X07=0000000000000000 X08=0000000000000000 X09=0000000000000000 X10=0000000000000000 X11=0000000000000000 X12=0000000000000000 X13=0000000000000000 X14=0000000000000000 X15=0000000000000000 X16=0000000000000000 X17=0000000000000000 X18=0000000000000000 X19=0000000000000000 X20=0000000000000000 X21=0000000000000000 X22=0000000000000000 X23=0000000000000000 X24=0000000000000000 X25=0000000000000000 X26=0000000000000000 X27=0000000000000000 X28=0000000000000000 X29=0000000000000000 X30=0000000000000000 SP=0000000000000000 PSTATE=400003c5 -Z-- EL1h Exception return from AArch64 EL1 to AArch64 EL1 PC 0x423790d0 Taking exception 1 [Undefined Instruction] ...from EL1 to EL1 ...with ESR 0x0/0x2000000 ...with ELR 0xffff800080027b20 ...to EL1 PC 0xffff800080011200 PSTATE 0x3c5 Here is my build image folder boot_ls2088ardb_lts_6.6.tgz core-image-minimal-ls2088ardb.rootfs-20240711074828.cpio.gz core-image-minimal-ls2088ardb.rootfs-20240711074828.cpio.gz.u-boot core-image-minimal-ls2088ardb.rootfs-20240711074828.manifest core-image-minimal-ls2088ardb.rootfs-20240711074828.spdx.tar.zst core-image-minimal-ls2088ardb.rootfs-20240711074828.tar.gz core-image-minimal-ls2088ardb.rootfs-20240711074828.testdata.json core-image-minimal-ls2088ardb.rootfs.cpio.gz->core-image-minimal-ls2088ardb.rootfs-20240711074828.cpio.gz core-image-minimal-ls2088ardb.rootfs.cpio.gz.u-boot->core-image-minimal-ls2088ardb.rootfs-20240711074828.cpio.gz.u-boot core-image-minimal-ls2088ardb.rootfs.manifest->core-image-minimal-ls2088ardb.rootfs-20240711074828.manifest core-image-minimal-ls2088ardb.rootfs.spdx.tar.zst->core-image-minimal-ls2088ardb.rootfs-20240711074828.spdx.tar.zst core-image-minimal-ls2088ardb.rootfs.tar.gz->core-image-minimal-ls2088ardb.rootfs-20240711074828.tar.gz core-image-minimal-ls2088ardb.rootfs.testdata.json->core-image-minimal-ls2088ardb.rootfs-20240711074828.testdata.json fitImage->fitImage--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.bin fitImage--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.bin fitImage-core-image-minimal-ls2088ardb.rootfs--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.bin fitImage-core-image-minimal-ls2088ardb.rootfs-ls2088ardb->fitImage-core-image-minimal-ls2088ardb.rootfs--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.bin fitImage-its--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.its fitImage-its-core-image-minimal-ls2088ardb.rootfs--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.its fitImage-its-core-image-minimal-ls2088ardb.rootfs-ls2088ardb->fitImage-its-core-image-minimal-ls2088ardb.rootfs--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.its fitImage-its-ls2088ardb->fitImage-its--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.its fitImage-linux.bin--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.bin fitImage-linux.bin-ls2088ardb->fitImage-linux.bin--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.bin fitImage-ls2088ardb.bin->fitImage--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.bin fsl-image-networking-ls2088ardb.rootfs-20240711074828.cpio.gz fsl-image-networking-ls2088ardb.rootfs-20240711074828.cpio.gz.u-boot fsl-image-networking-ls2088ardb.rootfs-20240711074828.ext4 fsl-image-networking-ls2088ardb.rootfs-20240711074828.manifest fsl-image-networking-ls2088ardb.rootfs-20240711074828.spdx.tar.zst fsl-image-networking-ls2088ardb.rootfs-20240711074828.tar.gz fsl-image-networking-ls2088ardb.rootfs-20240711074828.testdata.json fsl-image-networking-ls2088ardb.rootfs.cpio.gz->fsl-image-networking-ls2088ardb.rootfs-20240711074828.cpio.gz fsl-image-networking-ls2088ardb.rootfs.cpio.gz.u-boot->fsl-image-networking-ls2088ardb.rootfs-20240711074828.cpio.gz.u-boot fsl-image-networking-ls2088ardb.rootfs.ext4->fsl-image-networking-ls2088ardb.rootfs-20240711074828.ext4 fsl-image-networking-ls2088ardb.rootfs.manifest->fsl-image-networking-ls2088ardb.rootfs-20240711074828.manifest fsl-image-networking-ls2088ardb.rootfs.spdx.tar.zst->fsl-image-networking-ls2088ardb.rootfs-20240711074828.spdx.tar.zst fsl-image-networking-ls2088ardb.rootfs.tar.gz->fsl-image-networking-ls2088ardb.rootfs-20240711074828.tar.gz fsl-image-networking-ls2088ardb.rootfs.testdata.json->fsl-image-networking-ls2088ardb.rootfs-20240711074828.testdata.json fsl-ls2088a-qds--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.dtb->fsl-ls2088a-qds.dtb fsl-ls2088a-qds.dtb fsl-ls2088a-qds-ls2088ardb.dtb->fsl-ls2088a-qds.dtb fsl-ls2088a-rdb--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.dtb->fsl-ls2088a-rdb.dtb fsl-ls2088a-rdb.dtb fsl-ls2088a-rdb-ls2088ardb.dtb->fsl-ls2088a-rdb.dtb Image->Image--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.bin Image--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.bin Image-ls2088ardb.bin->Image--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.bin ls2088ardb_boot.scr modules--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.tgz modules-ls2088ardb.tgz->modules--6.6.23+git0+b586a52177-r0-ls2088ardb-20240711074828.tgz u-boot.bin->u-boot-tfa-2024.04++fslgit-r0.bin u-boot.bin-tfa->u-boot-tfa-2024.04++fslgit-r0.bin u-boot.bin-tfa-secure-boot->u-boot-tfa-secure-boot-2024.04++fslgit-r0.bin u-boot-ls2088ardb.bin->u-boot-tfa-2024.04++fslgit-r0.bin u-boot-ls2088ardb.bin-tfa->u-boot-tfa-2024.04++fslgit-r0.bin u-boot-ls2088ardb.bin-tfa-secure-boot->u-boot-tfa-secure-boot-2024.04++fslgit-r0.bin u-boot-qoriq-initial-env-ls2088ardb-tfa->u-boot-qoriq-initial-env-ls2088ardb-tfa-2024.04++fslgit-r0 u-boot-qoriq-initial-env-ls2088ardb-tfa-2024.04++fslgit-r0 u-boot-qoriq-initial-env-ls2088ardb-tfa-secure-boot->u-boot-qoriq-initial-env-ls2088ardb-tfa-secure-boot-2024.04++fslgit-r0 u-boot-qoriq-initial-env-ls2088ardb-tfa-secure-boot-2024.04++fslgit-r0 u-boot-qoriq-initial-env-tfa->u-boot-qoriq-initial-env-ls2088ardb-tfa-2024.04++fslgit-r0 u-boot-qoriq-initial-env-tfa-secure-boot->u-boot-qoriq-initial-env-ls2088ardb-tfa-secure-boot-2024.04++fslgit-r0 u-boot-tfa-2024.04++fslgit-r0.bin u-boot-tfa-secure-boot-2024.04++fslgit-r0.bin Thanks Re: How qemu load dtb on LS2088ardb You cannot emulate the device in a PC. This would need to create a new QEMU image that works with all the modules of the LS2088A and we do not have any image like that. What I understood was to simulate an Arm OS with QEMU in the board and you can for sure do that.