任何命令上的 S32K116 STATUS_ERROR 你好， 我是 MCU 编程的新手，在 s32k116 上运行任何命令时遇到了问题。我从 s32ds 上的示例项目 csec_keyconfig_s32k116 开始，然后根据我的需要对其进行了更改。我正在使用带有 s32k116 的定制板，并且我通过 WriteCommandHeader 发送的任何命令都会被 csec_readerrorbits() 返回错误，例如：CSEC_WriteCommandHeader(CSEC_CMD_BOOT_OK, CSEC_FUNC_FORMAT_ADDR,CSEC_CALL_SEQ_FIRST, CSEC_SECRET_KEY); 我首先尝试使用 CSEC_CMD_INIT_RNG，但也出现了错误。有谁知道为什么命令会出现错误？ 回复：任何命令上的S32K116状态错误 运行 csec_flash_part 时，似乎我忘记在切换到其他程序时进行电源循环，导致命令不起作用，但在电源循环之后，我能够让命令起作用。感谢您的帮助！ 回复：任何命令上的S32K116状态错误 您是否从 RAM 运行了 csec_flash_part 示例？运行成功了吗？ 当您运行 CSEc 密钥配置示例时，它究竟在哪里失败？ 回复：任何命令上的S32K116状态错误 根据您的问题： 1) 我可以通过寄存器 SIM_SDID 为 11100000 判断该部件已启用 CSEc 2) 我确实尝试在运行我正在运行的项目之前运行上述项目以启用 CSEc，但该项目仍然无法运行 3）当我运行基础项目而不做任何更改时，我将获得 DefaultISR 感谢您的联系，如果您还有任何需要，请告诉我

Interrupt coalescing Hello, We are using NXP LX2160ARDB to build a communication system, and we want to improve the data processing speed performance. To send interrupts from the NIC to the CPU core more frequently, which part of the kernel should we modify? In other words, we want to shorten the interrupt coalescing interval. Thank you. Re: Interrupt coalescing On lx2160a platform, networking data is processing in DPAA2 module. If your data rate exceeds the throughput of DPAA2 Ethernet ports, it will caused loss of those packets. You could contact your DFAE to ask for the performance data of lx2160a Ethernet ports from NXP marketing team. In addition, you could use DPDK solution to improve the networking throughput. Re: Interrupt coalescing Thank you for your response. Is there any way to make NAPI interrupts more frequent? In our experiment, the NXP device is losing packets being received. Please refer to the figure below. Of course, the data rate in our experiment is very high. However, we would like to make it even faster if possible. Is there a way to prevent the loss of those packets? Thank you. Re: Interrupt coalescing Kernel NAPI interrupts are rare, changing this will not improve the throughput.

任意のコマンドでS32K116 STATUS_ERROR こんにちは 私はMCUのプログラミングに不慣れで、s32k116で動作するコマンドを取得するのに問題があります。私は、s32dsがcsec_keyconfig_s32k116されているサンプルプロジェクトから始めて、それを私のニーズに合わせて変更しました。私はs32k116でカスタムボードを使用していますが、WriteCommandHeaderを介して送信するコマンドは、次のようなcsec_readerrorbits()によってエラーで返されます。 CSEC_WriteCommandHeader(CSEC_CMD_BOOT_OK, CSEC_FUNC_FORMAT_ADDR,CSEC_CALL_SEQ_FIRST, CSEC_SECRET_KEY); 最初にCSEC_CMD_INIT_RNGを使用しようとしましたが、エラーも発生しました。コマンドでエラーが発生している理由を誰かが知っていますか? Re:任意のコマンドでS32K116 STATUS_ERROR csec_flash_partを実行しているとき、他のプログラムに切り替えるときに電源を入れ直すのを忘れてコマンドが機能しなかったようですが、電源を入れ直すとコマンドを機能させることができました。ご協力いただきありがとうございます! Re:任意のコマンドでS32K116 STATUS_ERROR csec_flash_part例をRAMから実行しましたか?それは成功しましたか? CSEc キーの設定例を実行すると、正確にはどこで失敗しますか? Re:任意のコマンドでS32K116 STATUS_ERROR あなたの質問に従って: 1) レジスタ 11100000 を持っているレジスタ SIM_SDID でわかるように、部品は CSEc 対応です 2)CSEcを有効にするために、取り組んでいるプロジェクトの前に前述のプロジェクトを実行しようとしましたが、プロジェクトはまだ機能していません 3)何も変更せずにベースプロジェクトを実行すると、DefaultISRが表示されます ご連絡いただきありがとうございます、他に何か必要なことがあればお知らせください

imx8MP swupdateのお問い合わせ(ext4イメージの入手方法) 私の環境は、以下の通りです。 i.MX Linux Yocto Project BSP 6.1.22_2.0.0 リリース NXP i.MX 8MPlus EVK (imx8mpevk) imx8MP で swupdate を使用するには、SWUpdate OTA i.MX8MM EVK_rev3.pdf を参照してください。 「画像組み立て」の内容には、以下の内容があります。 06-imx-image-multimedia --> ../slota/imx-image-multimedia-imx8mmevk.ext4 bitbake の出力に ext4 形式の画像はありません。(wic.zst と tar.zst があります) ext4形式の画像を取得するにはどうすればよいですか?あるいは、wic.zstを使用して「画像の組み立て」に進むことはできますか? ブートROM|ブート|フラッシュ Re:imx8MPスワプアップデートのお問い合わせ(ext4イメージの入手方法) ご指摘のドキュメントによると、ext4を作成できるようです。 最初からドキュメントがあれば難しくはなかったのですが、グーグルで得られる断片的な知識には限界がありました。 ありがとうございます。 Re:imx8MPスワプアップデートのお問い合わせ(ext4イメージの入手方法) ドキュメントを参照できます Re:imx8MPスワプアップデートのお問い合わせ(ext4イメージの入手方法) ご返信ありがとうございます 以下を作りました。 06-IMX-イメージ-マルチメディア -> ../slota/imx-image-multimedia-imx8mp-lpddr4-evk.wic.zst そして、readme.txtの内容に合わせ、以下を実行しました。 切り捨てる -S 3000M 06-IMX-イメージ-マルチメディア e2fsck -f 06-imx-image-multimedia resize2fs 06-imx-image-multimedia その後、以下のようなエラーが発生します。 e2fsck 1.45.5 (2020 年 1 月 7 日) ext2fs_open2:スーパーブロックの魔法の数字が悪い e2fsck:スーパーブロックが無効です。バックアップブロックを試みています... e2fsck: 06-imx-image-multimedia を開こうとしているときに、スーパーブロックに不正なマジックナンバーが表示されます スーパーブロックを読み取れなかったか、有効な ext2/ext3/ext4 を記述していません ファイルシステム。デバイスが有効で、実際に ext2/ext3/ext4 が含まれている場合 ファイルシステム (スワップや UFS などではない)、次にスーパーブロック が破損している場合は、別のスーパーブロックを指定して e2fsck を実行してみてください。 e2fsck -b 8193 又は e2fsck -b 32768 どうすればよいですか? Re:imx8MPスワプアップデートのお問い合わせ(ext4イメージの入手方法) あるいは、wic.zstを使用して「画像の組み立て」に進むことはできますか? はい、お使いいただけます、問題ありません。

MC33772B功耗 大家好，团队： 我在我的项目中使用 MC33772B。我想了解 MC33772B 在不同模式下的功耗，例如正常模式、睡眠模式、空闲模式、诊断模式。我在数据手册中找不到有关它的任何信息？ 你能提供一些帮助吗？ 谢谢！

HSE S32K358 ステータス・レジスタが 0 を返す HSE_FW_ABSWAP_2.40をインストールしましたが、そしてこれまでのところ、乱数生成、署名検証などのサービスを使用することができました。しかし、何らかの理由で、ステータスレジスタを読み取ろうとすると、FSRでは0しか表示されませんが、実際にそうであればHSEサービスを使用することさえできないはずなので、正常ではありません。 何が原因なのかわかりません。 ありがとうございました。 よろしくお願いします。 Re: HSE S32K358 Status レジスタが 0 を返す クイックアップデート、実際にはあなたが正しかったそれは私の問題を解決しました。 私はチャンネル0でいくつかのステータスを持っています、ありがとう! Re: HSE S32K358 Status レジスタが 0 を返す 遅くなってすみません、今週は確認できなくて。来週の月曜日にボードを受け取る必要があります。

How to send UModulation siganl by HCI cmd Hi,    If there is any SDK example can support to control KW45 Bluetooth board to send unmodulation signal by HCI cmd? If not, How can we change the code and support it?    Our surrounding:      IDE version: MCUXpresso IDE v11.8.0_1165     SDK version: KW45B41Z83 V2.12.7     FW: HCI_black_box     hope your support, thanks.          Best Regards,     Annie Re: How to send UModulation siganl by HCI cmd Hi Christine,     In another post, I also send a post and your have replied me. I think we can discuss more detail in that post, I will click this post have been solved, Thanks.    Post link: https://community.nxp.com/t5/Wireless-Connectivity/What-difference-between-Connectivty-test-and-HCI-black-box-FW/m-p/1856276#M17227     Best Regards,     Annie Re: How to send UModulation siganl by HCI cmd Hi， @Annie_he  As my understanding, the modulation and demodulation is implemented by physical layer, not by HCI layer. HCI layer is only a middle layer to transfer commands from host to controller and transfer events from controller to host, or transfer data from both side. It means, for HCI layer, there is no relationship with modulation or demodulation.  Can you please let me know why do you need this kind of HCI cmd to send UModulation siganl? Or provide me more details about your using cases? Best regards, Christine. Re: How to send UModulation siganl by HCI cmd Hi, @Annie_he  Thanks for creating case to us and hope you are doing well. I will check it and reply to you once have any updates. Have a nice weekend. Best regards, Christine.

imx8MP swupdate inquiry (how to get ext4 image) My environment is as follows. i.MX Linux Yocto Project BSP 6.1.22_2.0.0 Release NXP i.MX 8MPlus EVK (imx8mpevk) To use swupdate for imx8MP, refer to SWUpdate OTA i.MX8MM EVK_rev3.pdf. In the contents of "Image Assembling", there is the following: 06-imx-image-multimedia --> ../slota/imx-image-multimedia-imx8mmevk.ext4 There is no image in ext4 format in the output of bitbake. (There are wic.zst and tar.zst) How can I get an image in ext4 format? Alternatively, can we proceed with “Image Assembling” using wic.zst? Boot ROM|Booting | Flash Re: imx8MP swupdate inquiry (how to get ext4 image) According to the document you pointed out, I can create ext4. If there had been document from the beginning, it would have been less difficult, but the fragmented knowledge obtained through Googling had its limits. Thank you. Re: imx8MP swupdate inquiry (how to get ext4 image) You can refer to the document Re: imx8MP swupdate inquiry (how to get ext4 image) Thank you for your reply I made the below. 06-imx-image-multimedia -> ../slota/imx-image-multimedia-imx8mp-lpddr4-evk.wic.zst And, according to the contents of readme.txt, I executed the following. truncate -s 3000M 06-imx-image-multimedia e2fsck -f 06-imx-image-multimedia resize2fs 06-imx-image-multimedia Afterwards, an error occurs as shown below. e2fsck 1.45.5 (07-Jan-2020) ext2fs_open2: Bad magic number in super-block e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open 06-imx-image-multimedia The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 or e2fsck -b 32768 What should I do now? Re: imx8MP swupdate inquiry (how to get ext4 image) Alternatively, can we proceed with “Image Assembling” using wic.zst? Yes, you can use it, no problem.

imx8MP swupdate 查询（如何获取 ext4 图像） 我的环境如下。 i.MX Linux Yocto 项目 BSP 6.1.22_2.0.0 版本 NXP i.MX 8MPlus 评估套件 (imx8mpevk) 要对 imx8MP 使用 swupdate，请参阅 SWUpdate OTA i.MX8MM EVK_rev3.pdf。 在“图像组装”的内容中有以下内容： 06-imx-图像多媒体--> ../slota/imx-图像多媒体-imx8mmevk.ext4 bitbake 的输出中没有 ext4 格式的图像。（有wic.zst和tar.zst） 如何获取 ext4 格式的图像？或者，我们可以使用 wic.zst 进行“图像组装”吗？ 启动 ROM | 启动配置 | 闪存 回复：imx8MP swupdate 查询（如何获取 ext4 图像） 根据您指出的文档，我可以创建 ext4。 如果一开始就有文献的话，难度就会小一些，但是通过谷歌搜索获得的碎片化知识有其局限性。 谢谢。 回复：imx8MP swupdate 查询（如何获取 ext4 图像） 您可以参考文档 回复：imx8MP swupdate 查询（如何获取 ext4 图像） 感谢你的回复 我做了以下事情。 06-imx-图像多媒体->../slota/imx-图像多媒体-imx8mp-lpddr4-evk.wic.zst 并且，根据 readme.txt 的内容，我执行了下列操作。 截断-s 3000M 06-imx-图像多媒体 e2fsck-f 06-imx-图像多媒体 resize2fs 06-imx-图像多媒体 之后就会出现如下错误。 e2fsck 1.45.5（2020年1月7日） ext2fs_open2：超级块中的幻数错误 e2fsck：超级块无效，正在尝试备份块... e2fsck：尝试打开 06-imx-image-multimedia 时超级块中的幻数错误 无法读取超级块或超级块未描述有效的 ext2/ext3/ext4 文件系统。如果设备有效并且确实包含 ext2/ext3/ext4 文件系统（而不是交换或 ufs 或其他），然后是超级块 已损坏，您可以尝试使用备用超级块运行 e2fsck： e2fsck -b 8193 或者 e2fsck -b 32768 我现在该怎么办？ 回复：imx8MP swupdate 查询（如何获取 ext4 图像） 或者，我们可以使用 wic.zst 进行“图像组装”吗？ 是的，你可以使用它，没问题。

FTM-PDBの FTM によって生成された PWM は、立ち上がりエッジと立ち下がりエッジの両方でプリ トリガーを生成して PDB をトリガーするように設定できますか? 日時:FTM - PDB 返信ありがとうございます、理解できたと思います。

MC33772B消費電力 こんにちはチーム: プロジェクトでMC33772Bを使用しています。通常モード、スリープモード、アイドルモード、診断モードなど、さまざまなモードでのMC33772Bの消費電力を知りたいです。データシートにそれに関する情報が見つかりませんか? 何か助けてもらえますか? ありがとうございます！

S32 Configuration Tool Dio Channel ID error Hello, I'm new to MBDT and the S32 Configuration Tool. I want to make a simple blinking LED project using MBDT with S32K358. From the datasheet, I notice the following information: Pin number: 86 Pin name: PTC21 Pin type: OUT Purpose: LED_GRN So I thought the Port ID was 5 for PTC [31-16] and the channel ID was 21. However, it looks like I misunderstood something because it said the channel id is out of range: What should I do to properly configure this pin? Thanks. Re: S32 Configuration Tool Dio Channel ID error Hello nxp team, we are trying to enable the PTD17 pin high with dio peripheral port name: PTD_H Dio port Id: 7 Dio channel Id: 1 how to check the channel id i set is correct or not? right now this pin is not getting high Re: S32 Configuration Tool Dio Channel ID error Hi The value of Dio Channel Id must be in range: 0-15 For PTC21 please enter 5 (21-16) Please notice that Model Based Design Tools (MBDT) are supported by our engineers on this community: https://community.nxp.com/community/mbdt It’s an exception, all our products are supported via these tickets but except these MBDT tools. So, create please new thread on the community and responsible engineers will help you. Thanks for understanding. Best Regards, Robin ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" button. Thank you! - We are following threads for 7 weeks after the last post, later replies are ignored Please open a new thread and refer to the closed one, if you have a related question at a later point in time. -------------------------------------------------------------------------------

MC33772B Power Consumption Hello Team: I am using MC33772B in my project. I want  to know Power Consumption about MC33772B in different mode,like normal mode、Sleep mode、Idle mode 、diagnosis mode.I cannot find the any information about it in data sheet? Can you provide some help? Thanks! Re: MC33772B Power Consumption Hello Shigi, Supply current in various modes is specified in Table 7 (Power management) of the MC33772B full datasheet which is available as a secure file requiring an NDA. If your company has not signed the NDA with NXP yet, you can request it from: https://www.nxp.com/support/support:SUPPORTHOME If there is a valid NDA in place, you can download the MC33773B full datasheet from the following website: https://www.nxp.com/products/power-management/battery-management/battery-cell-controllers/6-channel-li-ion-battery-cell-controller-ic:MC33772B BR, Tomas

HSE S32K358状态寄存器返回0 我安装了 HSE_FW_ABSWAP_2.40，到目前为止，我设法使用了随机数生成、签名验证等服务；但由于某些原因，当我尝试读取状态寄存器时，我在 FSR 中只得到 0，这是不正常的，因为如果事实确实如此，我甚至不能使用 HSE 服务。 我不知道是什么原因造成的。 谢谢！ 此致 回复：HSE S32K358状态寄存器返回0 快速更新，实际上你是对的，它解决了我的问题。 我在频道 0 中确实有一些状态，谢谢！ 回复：HSE S32K358状态寄存器返回0 很抱歉耽搁了，本周我无法检查。我应该在下周一拿到董事会的证件。

EB激活失败 我尝试激活EB，但是发生了如下情况，请帮我看看需要如何修复这个问题，谢谢。 Activating NodeLocked License ACE1-629A-5121-C8FE, Number Of Licenses: 1 Status: 4, Creating request Status: 5, Request created Status: 6, Context created Status: 7, Connected to remote server Status: 8, Request Sent Status: 9, Polling for response Status: 11, Done ERROR: flxActAppActivationSend (50040,41147,10248) That activation request yields no right to a license. Connection to FlexNet Operations Server failed.

i.MX8MM no audio/I2S after update to Scarthgap After updating to Scarthgap (imx-6.6.36-2.1.0) there is no more audio output on our custom board. The device tree needed a little update, is there anything obvious missing that might cause this issue after the update? I tried with linux-imx and linux-fslc-imx. sound-max9867 { compatible = "simple-audio-card"; simple-audio-card,name = "MAX9867"; simple-audio-card,format = "i2s"; simple-audio-card,widgets = "Speaker", "Jack", "Microphone", "Mic"; simple-audio-card,routing = "Jack", "LOUT", "Jack", "ROUT", "Mic", "DMICL", "Mic", "DMICR"; simple-audio-card,frame-master = <&cpudai>; simple-audio-card,bitclock-master = <&cpudai>;   cpudai: simple-audio-card,cpu { sound-dai = <&sai5>; dai-tdm-slot-num = <2>; dai-tdm-slot-width = <16>; }; simple-audio-card,codec { sound-dai = <&max9867>; clocks = <&clk IMX8MM_CLK_SAI5_ROOT>; }; };   &i2c2 { status = "okay"; max9867: audio_codec@18 { #sound-dai-cells = <0>; compatible = "maxim,max9867"; reg = <0x18>; clocks = <&clk IMX8MM_CLK_SAI5_ROOT>; // this line is needed after the update }; };   &sai5 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_sai5>; assigned-clocks = <&clk IMX8MM_CLK_SAI5>; assigned-clock-parents = <&clk IMX8MM_AUDIO_PLL1_OUT>; assigned-clock-rates = <24576000>; };     i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: i.MX8MM no audio/I2S after update to Scarthgap Hi, I only added the line "clocks = <&clk IMX8MM_CLK_SAI5_ROOT>;" to the codec node. We also have an imx93 in use on the same baseboard, using the same settings/dt-nodes (except that we use sai3 on imx93) and its working fine. After comparing the two dts, I saw that the i.MX93 had an additional "fsl,sai-mclk-direction-output" in the dt, with that added to the imx8 dt, it is working again. Thanks for your input, comparing the device trees did the trick Re: i.MX8MM no audio/I2S after update to Scarthgap Hello, Which changes did you did with clock? simple-audio-card uses the generic driver simple-card.c, but is working as expected in other devices such as i.MX8MMEVK with WM8524 codec. Please check if differences between last release and your past used release could cause the issue. Is there additional changes that you did in your system to port the CODEC? Best regards Re: i.MX8MM no audio/I2S after update to Scarthgap Hi Jorge, I encountered an error because the max9867 driver needed the clocks property. After adding it, the driver is now probed correctly. I also checked the signals on the board: the master clock (provided by the CPU) is active, but the LR-clock, Bitclock, as well as the I2S Data and Clock are not active. Were there any recent changes in the SAI driver? I’ll check as well, but if you have any input on this part, I’d appreciate it. Best regards, Dominik Re: i.MX8MM no audio/I2S after update to Scarthgap Hello, Do you get error log when using the CODEC? Please check if there is no conflicts with your device and driver used compared with previous release. Best regards.

HSE S32K358 Status register returning 0 I installed HSE_FW_ABSWAP_2.40, and so far I managed to use to services such as random number generation, signature verify; but for some reasons, when I try to read the status register I get only 0s in FSR which is not normal since if it was actually the case I should not even be able to use HSE services.  I don't know what is causing this. Thank you, Regards Re: HSE S32K358 Status register returning 0 Quick update, actually you were right it solved my problem. I do have some status in channel 0 thank you! Re: HSE S32K358 Status register returning 0 Ok, I saw MU_1 in your screenshot, so it looked like this is the problem... In this case, there's obviously something wrong. If you can still use HSE services regardless of the FSR, I would try to erase the firmware by HSE_SRV_ID_ERASE_FW  service and then install the firmware again. Because it works as expected on my side, I do not have other ideas right now. Regards, Lukas Re: HSE S32K358 Status register returning 0 Hello,  Thank you for you response,  To be honest it does not solve my problem because what is strange is that I am actually using MU0 and not MU1 and I still don't read properly , so it seems like I have some kind of bug. here SEC_MU0_INSTANCE is 0. Still thank you for the valuables informations you brought. Best Regards Re: HSE S32K358 Status register returning 0 Hi @fp-theophile  Finally I got the board. The thing is that the status flags (bits 16-31) are visible only in MU0, not in MU1. Till now, I expected that the status bits are mirrored to all MU instances used for communication with HSE because there's a note in HSE FW RM: But it's obviously not correct. I will report it. Thanks for pointing this out. According to this table, MU0 and MU1 are always used for HSE: So, if you check FSR in MU0, you should see: For others - I checked this also on S32K344 and S32K312 and it's obviously the same on all S32K3 devices. So, when checking status of HSE at the beginning of your application, use MU0: Regards, Lukas Re: HSE S32K358 Status register returning 0 I'm sorry for delay, I'm not able to check it this week. I should get the board next Monday. Re: HSE S32K358 Status register returning 0 Hi @fp-theophile  yes, I agree, FSR should not be zero if HSE firmware is installed. I do not have working S32K358 board here right now but if you can wait, I should get one on Monday. I always saw expected content in FSR on other S32K3 devices, so let me check if I can see the same. Regards, Lukas

FTM-PDB Can the PWM generated by the FTM be set to generate a pre trigger on both its rising edge and falling edge to trigger the PDB? Re: FTM-PDB Thanks for the reply, I think I understood. Re: FTM-PDB Hi, only rising edge of input trigger asserts PDB pretrigger Input trigger is selected using Trigger mux, from FTM, initialization and external triggers can be selected. External trigger can be generated several times in PWM period, depends on mode used. Thus PDB can be triggered at both PWM edges. BR, Petr

FTM-PDB 是否可以将 FTM 产生的 PWM 设置为在其上升沿和下降沿产生预触发以触发 PDB？ 回复：FTM-PDB 谢谢您的回复，我想我明白了。

ahab_status error from imx93 secure boot Hi, professionals !  I'm doing the secure boot on imx93. I use Yocto with meta-nxp-security-reference-design/meta-secure-boot meta layer, which supports i.MX boot image signing automation to compile the signed uboot and kernel container. First time, i referred to the ahab document and generated the ecc sha384 keys, and got the signed uboot and kernel container. I flash it to first board and run ahab_status, it succeed Second time, i generated the rsa-2048 sha256 keys, and every steps else is the same with the first time. I flash the signed uboot and kernel to second board and run ahab_status, it failed, shows  0x0287f7d6 IPC = MU APD (0x2) CMD = ELE_OEM_CNTN_AUTH_REQ (0x87) IND = ELE_BAD_CONTAINER_FAILURE_IND (0xF7) STA = ELE_SUCCESS_IND (0xD6) I'm really confused why it can't work with the rsa keys, and what does the failure indication mean? I think the imx93 and ahab support both ECC and RSA, and i really follow the same step, just key type are different. I am very eager to get your support and help! Thanks in advance! Security Re: ahab_status error from imx93 secure boot I ended up with the same errors of Jacky-Cheng... Where is this statement located? I could not find it in the IMX93RM and SRM. Are you referring to the table 4 in UG10106? Re: ahab_status error from imx93 secure boot Hi @Harvey021  I have compiled the image including the meta-secure-boot by follwing the document but previously i was using "core-image-selinux-imx93-11x11-lpddr4x-curiosity.rootfs.wic.zst" to flash now can you please tell what are the images i can use to flash and how can i flash please. Thank you in advance Brati Re: ahab_status error from imx93 secure boot Hi @Jacky-Cheng actually i am also using imx93 with yocto and i want secure boot i.MX 93 signed and encrypted AHAB image but as i am totally new to this i was unable to do after many attempts. What i did was added the layer to my source and then i am confused like how the generated how the keys generated what conf i need to add in local.conf and all can you please help me with this to provide steps! Thanks & regards  Brati Re: ahab_status error from imx93 secure boot That is correct, no RSA with ele device. Re: ahab_status error from imx93 secure boot This issue has been resolved. As the IMX93 Reference Manual say, it support rsa-pss and ecc key, but not rsa key, so it is clear that imx93 doesn't support rsa type keys. Re: ahab_status error from imx93 secure boot Hi As AHAB should support RSA key. With checking the whole statement from the section " 10.9.2 Prerequisites for preparing a signed image". my understanding is that the Signer Tool, by default, will use ECC type of keys for i.MX93 device for signing. Sorry, it is not available for me to have a test for now.  Can you side have a test while using RSA keys? as stated here “Note: (Optional) Create and populate csf_hab4.cfg and/or csf_ahab.cfg with the preferred key type at the CST location to use your preferred PKI tree. The default configuration files are located at the CST Signer work directory in Yocto build.” Regards Harvey Re: ahab_status error from imx93 secure boot Hi Harvey, thanks for your reply first! But, it just said by default, not explicitly stated that other key types can't be used. So i wonder can RSA key type works? And if not, what's the reason? Thanks again! Re: ahab_status error from imx93 secure boot Hi,  Probably a cause as like " By default, the NXP CST Signer Tool uses standard keys of type ECC P256-SHA256 for i.MX 8/8x/8ULP/9 Family" as stated from <10.9.2 Prerequisites for preparing a signed image>  Regards Harvey