DMA 4.0.0 驱动程序不允许配置 DMA 请求（对于 LPSPI） 带有DS3.5和RTD 4.0.0.202311，micro S32K344 我尝试配置 LPSPI 来使用 DMA。 DMA_IP 不允许选择 DMAMUX 源。 附件中有 UM 屏幕截图和 DS 的实际情况。 UM 表明 DMA 通道与该示例中的 SPI2_Tx 源相链接。 实际配置没有任何字段来配置 DMA 源。 只需选择任意两个 DMA 硬件通道并告诉 LPSPI 将它们用于 SPI tx/rx 就足够了吗？ S32K1系列的S32SDK

PN7642 documentation Hello!  I`m using PN7642. I would like to read some documents containing IC`s peripheral detailed description and registers description. Also I would like to know if there are documents which describe bootloader communication protocol for FW programming via, for example, SPI interface.  Can someone suggest where to look for such information? May be somewhere more related documents are available for PN7642?  Thank you in advance! Artem Contact Smart Card Reader ICs Re: PN7642 documentation Thank you for reply. Now it is clear. I will try to sign NDA to be able to use this documentation. Re: PN7642 documentation Hello @ArtemPN Hope you are doing well. For more information about PN7642, you can consult the PN76 family instruction manual and UM11566 PN76 family NFC open controller user manual (since this document is under NDA, it is secured in Secure Files, and you will need to request access to it). Regarding the firmware download, perhaps you may find useful the Secure Firmware Download example "DownloadLibEx1", which is available to demonstrate the secure firmware update by using LPC55 and MCUXpresso. You can find more information on this in PN76 family evaluation board quick start guide, Chapter 4 Software. Regards, Eduardo.

RT1170 跨重置持久 RAM？ RT1170 是否有一些（小）内部 RAM 区域可以在重置后保留其内容？ 回复：RT1170 跨重置持久 RAM？ 是的，但是内部 RAM 块是否会因硬件重置而断电？（抱歉，我对 RT1170 不够熟悉 - 内部 RAM 块是否有单独的电源启用？）

RT1170 persistent-across-reset RAM? Does the RT1170 have some (small) area of internal RAM that will retain its contents across a reset? Re: RT1170 persistent-across-reset RAM? Hi @Littell  Please refer https://www.nxp.com/design/training/i-mx-rt1170-mcus-architecture-overview:TIP-IMX-RT1170-MCUS-ARCHITECTURE-OVERVIEW to know more about RT1170. For hardware reset (E.g. POR ) case, the state of each RAM will be undefined(random, not all zero). B.R, Sam Re: RT1170 persistent-across-reset RAM? Yes, but are the internal RAM blocks powered down as the result of a hardware reset?  (My apologies for not being familiar enough with the RT1170 - do the internal RAM blocks even have separate power enables?) Re: RT1170 persistent-across-reset RAM? Hi @Littell  RAM will retain its contents across a reset if NO any power off, that's how ram works. If power off, it will be lost. https://hackernoon.com/differences-between-ram-rom-and-flash-memory-all-you-need-to-know-ghr341i B.R, Sam

RT1170 パーシステント アクロス リセット RAM? RT1170 には、リセット後も内容を保持する (小さな) 内部 RAM 領域がありますか? 日時:RT1170パーシステントクロスリセットRAM? はい、しかし、ハードウェアのリセットの結果として内部RAMブロックの電源がオフになっていますか?(RT1170に十分に精通していないことをお詫びします-内部RAMブロックには個別の電源イネーブルがありますか?

How to load Linux Image into Flash NOR QSPI using custom board based on iMX93 Hello everyone, I'm tryng to flash into my custom iMX93 board with UUU the .wic. I'm using this built-in command: uuu.exe -b qspi core-image-minimal-imx93-11x11-lpddr4x-evk.rootfs-20250328061745.wic But it doesn't work.   The only thing that works is the bootloader. Indeed, when I use the following command: uuu.exe -b qspi imx-boot-imx93-11x11-lpddr4x-evk-sd.bin-flash_singleboot the bootloader starts, even if I reset the board with the boot mode configuration "FlexSPI Serial NOR", so I think it is correctly flashed into memory. What am I doing wrong with the .wic download? What am I supposed to do in order to flash the .wic file into QSPI-flash? Do I need to change something into the source files of the bootloader or it should be working as it comes from the nxp site? Thanks in advance, Best regards, Bob Re: How to load Linux Image into Flash NOR QSPI using custom board based on iMX93 Thanks, it helped me a lot. Bob Re: How to load Linux Image into Flash NOR QSPI using custom board based on iMX93 Hello, I'm using Flash-NOR QSPI. Re: How to load Linux Image into Flash NOR QSPI using custom board based on iMX93 Hello @saxejeh , thank you, I will try it following the patch for imx93 and I'll let you know. Best regards, Bob Re: How to load Linux Image into Flash NOR QSPI using custom board based on iMX93 Hello, The following command burns boot image into FlexSPI NAND: uuu -b spi_nand To generate boot image for FlexSPI NAND boot on i.MX 93, run the following command: make SOC=iMX93 flash_singleboot_spinand Note: Two binaries are generated: • flash.bin is the boot image burned into the SPI NAND. • flash_fw.bin is the NAND UUU FW image used by the UUU tool. Regards Re: How to load Linux Image into Flash NOR QSPI using custom board based on iMX93 I followed this document and it works. https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/all-bootloader-device-tree-Linux-kernel-rootfs-in-spi-nor-demo/ta-p/1663994

VSCodeで動作しないコンポーネントを管理しますか? みなさん Visual Studio Code での SDK コンポーネントの管理で問題が発生しています。「コンポーネントの管理」をクリックしても、何も起こりません。 この機能にアクセスするには、プロジェクトを右クリックし、[構成] → [コンポーネントの管理] を選択します。 インストールしたすべてのツールを示すスクリーンショットを添付しました。ご覧のとおり、SDKはリポジトリに適切に追加されています。 セットアップに欠けているものはありますか?他の誰かがこの問題に遭遇し、解決策を見つけましたか? どんな助けでも大歓迎です! Re:VSCodeで動作していないコンポーネントを管理しますか? ご返信ありがとうございます。VSCodeで直接作成されたプロジェクトで機能します-私はあなたの指示に従って新しいSDKの例を作成しました、そしてそれは示されているように機能しました。 しかし、私のメインプロジェクトはもともとMCUXpresso IDEで開発されていましたが、現在はVSCodeに移行しようとしています。この機能を MCUXpresso IDE で最初に作成されたプロジェクトで機能させる方法はありますか?

iMX8MP-EVK Unable to launch jailhouse mode with Yocto Harpoon image Dear Forum, Why struggling with the Yocto Harpoon on an iMX8MN custom board, I followed the instruction in the Harpoon User Guide  to bitbake a reference Yocto Harpoon image (imx-image-core) for the iMX8MP-EVK that I have. However, after stopping at the u-Boot prompt, running the following commands : u-boot=> setenv jh_root_dtb imx8mp-evk-harpoon.dtb u-boot=> run jh_mmcboot I did not see any information about launching of the jailhouse mode within 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 However, from what I saw from your partner's video, they seemed to launch the jailhouse cell manually within the root console. I am not sure if they ran commands in the u-Boot as I did. Could you help please ? Best Regards, Khang i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: iMX8MP-EVK Unable to launch jailhouse mode with Yocto Harpoon image Hi again, I just found out that the Yocto Harpoon image should be flashed to and executed from the micro-SD card rather than the eMMC. Sorry to bother you.

NTM88でP細胞またはg細胞のエラーが発生する条件は何ですか? BLE TPMSにNTM88H135ST1を使用していますが、センサーに診断とエラー通知を実装したいと考えていました。ファームウェアlibユーザーガイドを読んでいる間、私はこの関数をTPMS_WIRE_AND_ADC_CHECKしました、誰かがこの関数がP-Cellとg-Cellのエラーを与える条件が何であるかを説明して、その条件を再現してテストすることができます。そして、エラーが発生したら、どうすればそれを解決できますか。 Re:NTM88でP細胞またはg細胞エラーが発生する条件は何ですか? ありがとうトーマス、 同様に、次の関数がエラーを返した場合、それらから回復する方法はありますか、またはこれらのエラーは、IC、TPMS_READ_TEMPERATURE、TPMS_COMP_TEMPERATURE、TPMS_READ_VOLTAGE、TPMS_COMP_VOLTAGE、TPMS_READ_PRESSURE、TPMS_COMP_PRESSUREの永久的な損傷も示しています

what are the conditions when P-cell or g-cell error occurs in NTM88? I am using NTM88H135ST1 for my BLE TPMS, i wanted to implement diagnostics and error notification in my sensor. while going through Firmware lib user guide i got this function TPMS_WIRE_AND_ADC_CHECK, can someone explain what are the conditions when this function gives P-Cell and g-Cell errors so that i can recreate that condition and test it for the same. and once the error occurs how can we solve it.  Re: what are the conditions when P-cell or g-cell error occurs in NTM88? Thanks Tomas,  similarly, if the following functions returned error then is there any way to recover from them or these errors also indicate the permanent damage of the IC, TPMS_READ_TEMPERATURE, TPMS_COMP_TEMPERATURE, TPMS_READ_VOLTAGE, TPMS_COMP_VOLTAGE, TPMS_READ_PRESSURE, TPMS_COMP_PRESSURE Re: what are the conditions when P-cell or g-cell error occurs in NTM88? Hello Ankit, The function TPMS_WIRE_AND_ADC_CHECK performs different tests depending on the passed argument: - The ADC test consists of taking two reference measurements, one to Vdd and one to GND. The test fails when the converted value does not correspond to Vdd and GND, indicating an issue in the ADC block (in the ASIC). - The Gcell and Pcell tests check the connection between the sensor (Gcell/Pcell) and the ASIC. The sensor and ASIC are connected via bondwires, and the test check the bondwire connection. The test fails when an issue is found in the bondwire connection. In the application, if one of the tests fails, it is recommended to perform a delay and then at least one retry. If the test fails multiple times consistently then the application can conclude of a failure in the ASIC (for the ADC block) or with the bondwires (Gcell/Pcell). When such error occurs, it is not possible to make the NTM88 recover as it means some permanent failure has occurred. Note that such failure is not expected to occur during runtime. The main purpose of this function is to be run after assembly to check that the TPMS module is fully functional and that no damage has occurred during the assembly process. The conditions to raise the errors flags cannot be re-created on purpose, they require to physically have an ASIC or bondwire failure. BRs, Tomas

Manage components not working on VSCode? Hello everyone, I'm experiencing an issue with managing SDK components in Visual Studio Code. When I click on "Manage components," nothing happens at all. I access this feature by right-clicking on the project, then selecting Configure → Manage Components. I've attached a screenshot showing all the tools I have installed. And as you can see, the SDK has been properly added to my repository. Is there something I'm missing in my setup? Has anyone else encountered this issue and found a solution? Any help would be greatly appreciated! Re: Manage components not working on VSCode? Hi @jBahae, I have replicated this issue. Indeed, when trying to manage components from a project that was converted to VS Code using the MCUXpresso IDE Project Converter, it won't work. I believe this is a bug and I already reported it to the VS Code team for their review. In the meantime, I recommend you manage the necessary components using the option in MCUXpresso, before importing the project to VS Code. This seems to be the only current workaround. Sorry for the inconvenience this may cause. BR, Edwin. Re: Manage components not working on VSCode? Thank you for your reply. It works for projects created directly in VSCode - I created a new SDK example following your instructions and it worked as demonstrated. However, my main project was originally developed in MCUXpresso IDE, and I'm now trying to migrate it to VSCode. Is there a way to make this functionality work for projects that were initially created in MCUXpresso IDE? Re: Manage components not working on VSCode? Hi @jBahae, The manage component option will prompt a component search on the top search bar of VS Code: It might be slow, but after a while of loading the available components, these should display as such: Do you see the top search bar loading? If so, please be patient as it will take a while to load all of the components. BR, Edwin.

管理 VSCode 上不起作用的组件？ 大家好， 我在 Visual Studio Code 中管理 SDK 组件时遇到问题。当我点击“管理组件”时，什么也没有发生。 我通过右键单击项目，然后选择配置→管理组件来访问此功能。 我附上了显示我已安装的所有工具的屏幕截图。正如您所见，SDK 已正确添加到我的存储库。 我的设置中是否缺少了什么？还有其他人遇到过这个问题并找到解决方案吗？ 任何帮助都将不胜感激！ 回复：管理 VSCode 上不起作用的组件？ 感谢你的回复。它适用于直接在 VSCode 中创建的项目 - 我按照您的说明创建了一个新的 SDK 示例，并且它按照演示的方式工作。 但是，我的主要项目最初是在 MCUXpresso IDE 中开发的，现在我正尝试将其迁移到 VSCode。有没有办法让此功能适用于最初在 MCUXpresso IDE 中创建的项目？

goldvip1.9.0下BL2: Failed to load image id 3 ( -5 )   我们将烧录了goldvip1.9.0的sd卡插入到自己设计的电路板，系统启动停止在以下日志 ， 但是使用goldvip 1.10.0 系统一切正常，这是为什么？ Re: goldvip1.9.0下BL2: Failed to load image id 3 ( -5 ) 我通过将bsp38.0有关atf mmc相关的源码合并到goldvip1.9.0下解决了这个问题， git checkout tags/bsp38.0-2.5 -- drivers/mmc/mmc.c drivers/nxp/s32/mmc/s32_mmc.c include/drivers/mmc.h include/plat/common/common_def.h Re: goldvip1.9.0下BL2: Failed to load image id 3 ( -5 ) 对比了bsp38.0-2.5的atf源码，发现在drivers/mmc/mmc.c中的第555行有一段注释 /* On USB-SD-MUX setups, depending on some SD-Card types * experimentally it was observed that a first switch to * 20 Mhz frequency was necessary in order to use * CMD6 func check/switch. */ 随后我们将goldvip1.9.0烧入到不同的卡，测试有的卡是可以成功启动系统，有的不行 请问能否提供有关这段注释提到的现象的代码补丁文件来应用goldvip1.9的atf上? Re: goldvip1.9.0下BL2: Failed to load image id 3 ( -5 ) 还有一个现象就是，所有做好的goldvip1.9.0、1.10.0的sd卡，在官方rdb2板是可以正常启动的。 查看源码视乎是在atf源码出的问题，我添加了一些打印内容（附件是我添加的内容），并将atf修改为debug版本，可以看到以下日志 根据WARING: Failed to load image id=3 （-5）,我又增加了一些调试信息， 定位到问题是arm-trusted-firmware/drivers/mmc/mmc.c文件内的 mmc_send_cmd函数   该函数会调用 ret = ops->send_cmd(&cmd); 执行完会检查其返回值     if (ret != 0) {         VERBOSE("Send command %u error: %d\n", idx, ret);     } 我发现 日志输出以下内容 Send command 17 error: -5 所以我深入ret = ops->send_cmd(&cmd);发现最终调用的是arm-trusted-firmware/drivers/nxp/s32/mmc/s32_mmc.c  里的s32_mmc_send_cmd函数 并且在     do {         regdata = mmio_read_32(USDHC_INT_STATUS);         if (regdata & INT_STATUS_CMD_ERROR)             goto cmd_error;     } while (!(regdata & INT_STATUS_CC));   中发现INT_STATUS_CMD_ERROR某个对应位被置1导致跳转cmd_error，进而导致产生-EIO（-5）错误   所以我将regdata内容打印出，对应INT_STATUS_CMD_ERROR发现是CEBE被置1   综上所述，发送CMD17时，CEBE位被置1，导致产生了-EIO错误码（对应上图“BL2: Failed to load image id 3 ( -5 )”中的-5错误码） Re: goldvip1.9.0下BL2: Failed to load image id 3 ( -5 ) 使用的是s32g2，具体型号如下 使用的均是从官方网站上下载的预先编译好的镜像文件，sd卡烧入方式windows使用win32diskimager、rufus和linux dd命令均有尝试过，包括你发的链接的里的方式也尝试过，还是一样的现象 回复：goldvip1.9.0下BL2：无法加载图像 ID 3 ( -5 ) Hi, 您能告诉我们您使用的是哪款S32G产品吗？另外，您如何将图像刷入 SD 卡？ 您是否正在使用 GoldVIP 的预构建二进制文件？或者您正在建造自己的？ 总体来说，这个错误好像和镜像本身的刷写过程有关。以下社区主题提供了更多信息： “BL2：无法加载带有 BSP35 二进制文件的映像 ID 3 (3)” - NXP 社区 请告知我们。

On IMX8MP LVDS display with 6.1 kernel is not working which is working on 5.15 kernel Hi Team, we are able to bring-up the LVDS display on 5.15 kernel on imx8mp custom board, but when we are porting from 5.15 to 6.1 kernel LVDS display is not working. Below are the panel modifcations added: With the same below modfications display is working in 5.15 kernel. So need supoort to bringup the display. drivers/gpu/drm/panel/panel-simple.c | 97 ++++++++++++++++++++++++++++ 1 file changed, 97 insertions(+) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index b73669808347..605dce99d1ab 100644 --- a/drivers/gpu/drm/panel/panel-simple.c +++ b/drivers/gpu/drm/panel/panel-simple.c @@ -2128,6 +2128,94 @@ static const struct panel_desc hitachi_tx23d38vm0caa = { }, }; +static const struct display_timing auo_g156han04_0_timings = { + .pixelclock = { 141000000, 141000000, 141000000 }, + .hactive = { 1920, 1920, 1920 }, + .hfront_porch = { 60, 60, 60 }, + .hback_porch = { 60, 60, 60 }, + .hsync_len = { 64, 64, 64 }, + .vactive = { 1080, 1080, 1080 }, + .vfront_porch = { 12, 12, 12 }, + .vback_porch = { 12, 12, 12 }, + .vsync_len = { 12, 12, 12 }, +}; + +static const struct panel_desc auo_g156han04_0 = { + .timings = &auo_g156han04_0_timings, + .num_timings = 1, + .bpc = 8, + .size = { + .width = 344, + .height = 194, + }, + .delay = { + .prepare = 10, + .enable = 50, + .disable = 50, + .unprepare = 200, + }, + .bus_format = MEDIA_BUS_FMT_RGB888_1X24, +}; + +static const struct display_timing lxd_m773a_timings = { + .pixelclock = { 60000000, 60000000, 60000000 }, + .hactive = { 1024, 1024, 1024 }, + .hfront_porch = { 40, 40, 40 }, + .hback_porch = { 40, 40, 40 }, + .hsync_len = { 20, 20, 20 }, + .vactive = { 600, 600, 600 }, + .vfront_porch = { 20, 20, 20 }, + .vback_porch = { 20, 20, 20 }, + .vsync_len = { 10, 10, 10 }, +}; + +static const struct panel_desc lxd_m773a = { + .timings = &lxd_m773a_timings, + .num_timings = 1, + .bpc = 8, + .size = { + .width = 154, + .height = 85, + }, + .delay = { + .prepare = 10, + .enable = 50, + .disable = 50, + .unprepare = 200, + }, + .bus_format = MEDIA_BUS_FMT_RGB888_1X24, +}; + +static const struct display_timing lxd_m776a_timings = { + .pixelclock = { 60000000, 60000000, 60000000 }, + .hactive = { 1024, 1024, 1024 }, + .hfront_porch = { 40, 40, 40 }, + .hback_porch = { 40, 40, 40 }, + .hsync_len = { 20, 20, 20 }, + .vactive = { 600, 600, 600 }, + .vfront_porch = { 20, 20, 20 }, + .vback_porch = { 20, 20, 20 }, + .vsync_len = { 10, 10, 10 }, +}; + +static const struct panel_desc lxd_m776a = { + .timings = &lxd_m776a_timings, + .num_timings = 1, + .bpc = 8, + .size = { + .width = 222, + .height = 125, + }, + .delay = { + .prepare = 10, + .enable = 50, + .disable = 50, + .unprepare = 200, + }, + .bus_format = MEDIA_BUS_FMT_RGB888_1X24, +}; + + static const struct drm_display_mode innolux_at043tn24_mode = { .clock = 9000, .hdisplay = 480, @@ -4201,6 +4289,15 @@ static const struct of_device_id platform_of_match[] = { .compatible = "hit,tx23d38vm0caa", .data = &hitachi_tx23d38vm0caa }, { + .compatible = "lxd,m773a", + .data = &lxd_m773a, + }, { + .compatible = "lxd,m776a", + .data = &lxd_m776a, + }, { + .compatible = "auo,g156han04_0", + .data = &auo_g156han04_0, + }, { .compatible = "innolux,at043tn24", .data = &innolux_at043tn24, }, { -- 2.34.1 Here is the DTS file used: / { lvds0_panel { status = "okay"; compatible = "lxd,m776a"; backlight = <&lvds_backlight>; enable-gpios = <&gpio1 13 GPIO_ACTIVE_HIGH>; port { panel_lvds_in: endpoint { remote-endpoint = <&lvds_out>; }; }; }; lvds_backlight { enable-gpios = <&gpio1 0 GPIO_ACTIVE_HIGH>; }; // gpio3_IO23 on lec-imx8mp is display mux reg_mipi_lvds_select: regulator-mipi-lvds { compatible = "regulator-fixed"; regulator-name = "mipi_lvds_select_vbus"; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_disp_select>; regulator-min-microvolt = <1800000>; regulator-max-microvolt = <1800000>; gpio = <&gpio3 23 GPIO_ACTIVE_HIGH>; enable-active-low; regulator-always-on; }; }; &ldb { status = "okay"; //fsl,dual-channel; lvds-channel@0 { fsl,data-mapping = "spwg"; fsl,data-width = <24>; status = "okay"; /delete-node/ port@1; port@1 { reg = <1>; lvds_out: endpoint { remote-endpoint = <&panel_lvds_in>; }; }; }; }; &ldb_phy { status = "okay"; }; &i2c3 { touchscreen@41 { compatible = "ilitek,ili251x"; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_touch_en &pinctrl_touch_rst>; reg = <0x41>; interrupt-parent = <&gpio1>; interrupts = <0 IRQ_TYPE_EDGE_FALLING>; reset-gpios = <&gpio1 7 GPIO_ACTIVE_HIGH>; touchscreen-inverted-x; touchscreen-inverted-y; }; }; @[email protected], @[email protected] Re: On IMX8MP LVDS display with 6.1 kernel is not working which is working on 5.15 kernel after adding the below flags in the panel_desc then display is working as expected .bus_format = MEDIA_BUS_FMT_RGB888_1X7X4_SPWG, .bus_flags = DRM_BUS_FLAG_DE_HIGH, .connector_type = DRM_MODE_CONNECTOR_LVDS, Re: On IMX8MP LVDS display with 6.1 kernel is not working which is working on 5.15 kernel do you mind dumping the clock to check? could you get the correct clock for your lvds panel, I checked the ldb driver, I don't find anything change would affect your display Re: On IMX8MP LVDS display with 6.1 kernel is not working which is working on 5.15 kernel We didn't do any bsp changes except the panel detail structures are added in 5.15 kernel. So did the same modifications in the 6.1 kernel as well Re: On IMX8MP LVDS display with 6.1 kernel is not working which is working on 5.15 kernel did you change any source code in the 5.15? did you just use the default lvds driver? as I known, current bsp couldn't support 60Mhz lvds display(single channel) as default, you need change the source code, if you change the 5.15 bsp, did you change corresponding to the 6.1? Re: On IMX8MP LVDS display with 6.1 kernel is not working which is working on 5.15 kernel There are no error messages, but display is not coming as expected Is there any clock related changes we need to add in 6.1 Kernel?? or any other suggestions. Re: On IMX8MP LVDS display with 6.1 kernel is not working which is working on 5.15 kernel hi @joanxie  The Display backlight is initializing but on the display output is coming like below So unable to figure out what modifications went wrong  Re: On IMX8MP LVDS display with 6.1 kernel is not working which is working on 5.15 kernel what do you mean "not working"？do you get anything error messages?

optee test failed when HSE enabled based on SDK BSP41 on RDB3 v1.1 board Hi, Recently, I tested optee feature, and found that when hse enabled, the optee will fail, messages as following: NOTICE: Reset status: Power-On Reset NOTICE: BL2: v2.10.0 (release):bsp41.0-2.10 NOTICE: BL2: Built : 09:32:10, May 27 2024 NOTICE: BL2: Booting BL31 I/TC: I/TC: Non-secure external DT found I/TC: OP-TEE version: bsp41.0-4.0-dev (gcc version 11.4.0 (GCC)) #1 Thu May 23 14:46:51 UTC 2024 aarch64 I/TC: WARNING: This OP-TEE configuration might be insecure! I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html I/TC: Primary CPU initializing E/TC:0 0 crypto_driver_init:1224 Firmware not initialised E/TC:0 0 crypto_driver_init:1336 HSE Crypto Driver init failed with err 0xffff0007 E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x00075b28 failed I/TC: WARNING: Using fixed value for stack canary I/TC: Primary CPU switching to normal world boot I/TC: WARNING: Using fixed value for stack canary ... Auto Linux BSP 41.0 s32g399ardb3 ttyLF0 s32g399ardb3 login: root root@s32g399ardb3:~# root@s32g399ardb3:~# root@s32g399ardb3:~# xtest -l 15 Run test suite Iith WARNING (i sEE re t npiguration)started ovo get monotTnE instanee for REE ##,#u#i#### ################################## # # regression # ###################################################### * regression_1E/LD: e ie_f tes8s sys_open_ta_bin(d96a5b40-c3e5-21e3-8794-1002a5d5c61b) E/TC:? 0 ldelf_init_with_ldelf:152 ldelf failed with res: 0xffff0001 /usr/src/debug/optee-test/4.0.0-r0/git/host/xtest/regression_1000.c:299: res has an unexpected value: 0xffff0001 = E/ED_ERiOR_ACCf:486 sys_o ex_eatbdn(d96a5b40-cSUCCESS3 7r4-1002a5d510s iled with res: 0xffff0001 /usr/src/debug/optee-test/4.0.0-r0/git/host/xtest/regression_1000.c:338: res has an unexpected value: 0xffff0001 = TEEC_ERROR_ACCESS_DENIED, expected 0x0 = TEEC_SUCCESS /usr/src/debug/optee-test/4.0.0-r0/git/host/xtest/regression_1000.c:350: TEEC_InvokeCommand( &session, 1, &op, &ret_orig) has an unexpected value: 0xffff0006 = TEEC_ERROR_BAD_PARAMETERS Segmentation fault root@s32g399ardb3:~# root@s32g399ardb3:~# uname -a Linux s32g399ardb3 6.6.25-rt29-g8c8864ffb5db #1 SMP PREEMPT Mon May 27 16:30:16 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux root@s32g399ardb3:~#   And the hse firmware is v0.2.51.0 for S32G3 v1.1 version, and the following line: DISTRO_FEATURES:append = " hse optee" is added into the conf/local.conf of the bsp41 project. The whole test log is attached. Would you please help to check the issue? Thanks, Zhantao Re: optee test failed when HSE enabled based on SDK BSP41 on RDB3 v1.1 board Hello. I have the same message from secure boot step after formatting the key store with hse-secboot utility. And the BOOT_SEQ bit in the IVT, at offset 0x48, is unchanged (00e4). That means the board is still in insecure mode. How to switch in secure mode ? Thanks. Jerome Re: optee test failed when HSE enabled based on SDK BSP41 on RDB3 v1.1 board OK, got it. Thanks, Zhantao Re: optee test failed when HSE enabled based on SDK BSP41 on RDB3 v1.1 board Hi, @hittzt  Thanks for the feedback. In general, I often reference the log of "I/TC: HSE is successfully initialized", where HSE is initialized. From the functional test in kernel, seems there are no issues for this feature. BR Chenyin Re: optee test failed when HSE enabled based on SDK BSP41 on RDB3 v1.1 board Hi @chenyin_h, Thanks for your helpful reply. Now I know how to enable the optee with hse existed. But in 2nd time bootup, there still have messges like: E/TC:0 0 hse_copy_and_extract:145 HSE Export Key service request failed E/TC:0 0 hse_retrieve_huk:192 Copy and Export Step failed E/TC:0 0 hse_retrieve_huk:203 HW Unique Key request failed with err 0xffff0007 I/TC: Could not retrieve HSE HUK. Using default HUK I/TC: HSE is successfully initialized I/TC: Primary CPU switching to normal world boot Is this the right status? Thanks, Zhantao Re: optee test failed when HSE enabled based on SDK BSP41 on RDB3 v1.1 board Hello, @hittzt  Thanks for the reply. I was using firmware 0.2.51 as told by the BSP41 release notes. Briefly speaking, enable the OP-TEE Crypto Driver upon booting a freshly built FIP Image, the HSE OP-TEE Driver fails during its first initialization. This happens because the Key Catalog is not yet formatted at that point. The only way to format the catalog is to build the hse-secboot example, and run it in the Linux user space. Reset the board once the operation is complete, there should be no errors displayed by the HSE OP-TEE Driver during any subsequent initializations and the driver should function properly. Hope it helps. Best Regards Chenyin Re: optee test failed when HSE enabled based on SDK BSP41 on RDB3 v1.1 board Hi @chenyin_h, Thanks for your reply. And I checked the log you attached, it seems that, you boot the board 2 times and in 1st time, there are following info in BL31 stage: NOTICE: BL2: Booting BL31 I/TC: I/TC: Non-secure external DT found I/TC: OP-TEE version: bsp41.0-4.0-dev (gcc version 11.4.0 (GCC)) #1 Thu May 23 14:46:51 UTC 2024 aarch64 I/TC: WARNING: This OP-TEE configuration might be insecure! I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html I/TC: Primary CPU initializing E/TC:0 0 crypto_driver_init:1224 Firmware not initialised E/TC:0 0 crypto_driver_init:1336 HSE Crypto Driver init failed with err 0xffff0007 E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x00075b28 failed I/TC: WARNING: Using fixed value for stack canary I/TC: Primary CPU switching to normal world boot I/TC: WARNING: Using fixed value for stack canary And in 2nd time, the board boots up normally. So I want to know if there are any difference between the 1st and 2nd boot? And which HSE firmware version you used for test? Thanks, Zhantao Re: optee test failed when HSE enabled based on SDK BSP41 on RDB3 v1.1 board Hello, @hittzt  Thanks for the question. I checked it with the same configuration with my local RDB3(1.1 silicon). Seems no such issues from side, would you please double check your test, my log is attached for your reference. Best Regards Chenyin

MIMXRT1170-EVK: FreeRTOS 汎用 cm7 実行時エラーの例 linkServer を使用して MIMXRT1170-EVK で FreeRTOS Generic の例を実行しようとすると、次のランタイムエラーが発生します プログラムは信号SIGINT、割り込みを受信しました。 vApplicationIdleHook () を ./ソース/freertos_generic.c:386 386 xFreeStackSpace = xPortGetFreeHeapSize(); この点からハングしているように見えます。なぜそれがハングアップしているように見えるかについての何か提案はありますか?感謝 Re: MIMXRT1170-EVK: FreeRTOS 汎用 cm7 実行時エラーの例 解決済み、間違ったシリアルポート

SPI-1 CSピンが約S32K312機能しません こんにちはNXP:私はSPI1インターフェースで通信しようとし、クロック/ MOSIピンは必要なデータを出力できますが、CSピンは常に高いです。手伝ってくれませんか?ピンとSPIドライバーの間の設定が間違っているのはどこにあるのか、ありがとう。環境の説明:MCU:S32K312 / 100pin S32DS製品:3.5.0.202207261815RTD S32KXX:RTD5.0.0.202407261948SW32K3_FreeRTOS_11.1.0_5.0.0_CD1_D2409_例プロジェクト添付ファイルの説明: 20250407-SPI1_CS_issue.png 20250407-FreeRTOS_S32K312_SPI_test.7z BR Nelson Re:SPI-1 CSピンが約動作しませんS32K312 CS ピンにプルアップ レジスター 4.7K があるボードに問題があることがわかりましたので、この問題について話し合うためにハードウェア エンジニアリングに通知します。Robin_Shenありがとうございました。

Are there any simple examples on how to use smw security middleware? I attempted to write a program to just do a hash-2 512.  This results in the smw_hash() function calling exit(1).  We also would like to do AES 256 with this library which will require key generation and storage. Are there any example programs I could look at?  I realize there is a test program, which does work, but it is much more complicated than what I would like to do. Here is a trace of what I see, just calling smw_hash: #0 __GI__exit (status=status@entry=1) at /usr/src/debug/glibc/2.39+git/sysdeps/unix/sysv/linux/_exit.c:27 #1 0x0000fffff7d8e0e0 in __run_exit_handlers (status=status@entry=1, listp=0xfffff7ef0660 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:131 #2 0x0000fffff7d8e1f0 in __GI_exit (status=status@entry=1) at exit.c:138 #3 0x0000fffff7f90e88 in config_db_mutex_lock () at /usr/src/debug/smw/git/core/config/database.c:66 #4 0x0000fffff7f916fc in smw_config_select_subsystem (operation_id=OPERATION_ID_HASH, args=0xfffffffff958, subsystem_id=subsystem_id@entry=0xfffffffff94c) at /usr/src/debug/smw/git/core/config/database.c:560 #5 0x0000fffff7f7beb8 in smw_utils_execute_common (operation_id=operation_id@entry=OPERATION_ID_HASH, args=args@entry=0xfffffffff958, subsystem_id= , op_step=op_step@entry=SMW_OP_STEP_ONESHOT, implicit=implicit@entry=false) at /usr/src/debug/smw/git/core/utils/exec.c:38 #6 0x0000fffff7f7bf04 in smw_utils_execute_operation (operation_id=operation_id@entry=OPERATION_ID_HASH, args=args@entry=0xfffffffff958, subsystem_id= ) at /usr/src/debug/smw/git/core/utils/exec.c:89 #7 0x0000fffff7f88728 in smw_hash (args=args@entry=0xfffffffff9b8) at /usr/src/debug/smw/git/core/crypto/hash.c:115 #8 0x0000aaaaaaaa0a84 in main () at simplehash.c:38 This appears to be the cause of the EXIT: SMW_DBG_ASSERT(ctx); In my code, I did this prior to calling smw_hash, and it is not getting an error: memset(&ctx_args, 0, sizeof(ctx_args)); ctx_args.subsystem_name = SMW_SUBSYSTEM_NAME_ELE; // Allocate context smw_result = smw_allocate_context(&ctx_args); if (smw_result != SMW_STATUS_OK) { printf("Failed to allocate context: %d\n", smw_result); return -1; }  I am using IMX91 with  FRDM board, and am building with imx-6.6.36-2.1.0.xml. FRDM-Training Re: Are there any simple examples on how to use smw security middleware? Hello, There is no library to play with this Middleware, and the current just support smw_hash at 64KB. Sorry in this case you can search some solution on the web or wait until next release to see if developers add more space to smw_hash. Regards Re: Are there any simple examples on how to use smw security middleware? I found out that if I called smw_osal_lib_init() first, I could get the smw_hash() to work. However smw_hash() would not work with files much over 64K Bytes. If I want to hash 100MB, how do I do this? I don't think any of the test examples hash large files?

有没有简单的例子介绍如何使用 smw 安全中间件？ 我尝试编写一个程序来执行 hash-2 512。这导致 smw_hash() 函数调用 exit(1)。我们还想用这个库来实现 AES 256，这将需要密钥生成和存储。 有没有我可以看看的示例程序？我知道有一个测试程序，它确实可以工作，但它比我想要做的要复杂得多。 这是我所看到的痕迹，只是调用 smw_hash： #0 __GI__exit (status=status@entry=1) at /usr/src/debug/glibc/2.39+git/sysdeps/unix/sysv/linux/_exit.c:27 #1 0x0000fffff7d8e0e0 in __run_exit_handlers (status=status@entry=1, listp=0xfffff7ef0660 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:131 #2 0x0000fffff7d8e1f0 in __GI_exit (status=status@entry=1) at exit.c:138 #3 0x0000fffff7f90e88 in config_db_mutex_lock () at /usr/src/debug/smw/git/core/config/database.c:66 #4 0x0000fffff7f916fc in smw_config_select_subsystem (operation_id=OPERATION_ID_HASH, args=0xfffffffff958, subsystem_id=subsystem_id@entry=0xfffffffff94c) at /usr/src/debug/smw/git/core/config/database.c:560 #5 0x0000fffff7f7beb8 in smw_utils_execute_common (operation_id=operation_id@entry=OPERATION_ID_HASH, args=args@entry=0xfffffffff958, subsystem_id= , op_step=op_step@entry=SMW_OP_STEP_ONESHOT, implicit=implicit@entry=false) at /usr/src/debug/smw/git/core/utils/exec.c:38 #6 0x0000fffff7f7bf04 in smw_utils_execute_operation (operation_id=operation_id@entry=OPERATION_ID_HASH, args=args@entry=0xfffffffff958, subsystem_id= ) at /usr/src/debug/smw/git/core/utils/exec.c:89 #7 0x0000fffff7f88728 in smw_hash (args=args@entry=0xfffffffff9b8) at /usr/src/debug/smw/git/core/crypto/hash.c:115 #8 0x0000aaaaaaaa0a84 in main () at simplehash.c:38 这似乎是 EXIT 的原因： SMW_DBG_ASSERT(ctx); 在我的代码中，我在调用 smw_hash 之前执行了此操作，并且没有出现错误： memset(&ctx_args, 0, sizeof(ctx_args)); ctx_args.subsystem_name = SMW_SUBSYSTEM_NAME_ELE; // Allocate context smw_result = smw_allocate_context(&ctx_args); if (smw_result != SMW_STATUS_OK) { printf("Failed to allocate context: %d\n", smw_result); return -1; } 我正在使用带有 FRDM 板的 IMX91，并使用 imx-6.6.36-2.1.0.xml 进行构建。 FRDM 培训 回复：有没有关于如何使用 smw 安全中间件的简单示例？ 我发现如果我先调用 smw_osal_lib_init()，我就可以让 smw_hash() 工作。但是 smw_hash() 不适用于超过 64K 字节的文件。如果我想对 100MB 进行哈希处理，我该怎么做？我认为没有任何测试示例可以对大文件进行哈希处理？

Migrating console from LPUART1 to LPUART8 in imx93 Hi team,                 I need to migrate console from lpuart1(default) to lpuart8 in iMX93-11x11EVK  board and test from pins 32&33 in J1001. The change done in below files: Enabled LPUART8 node in u-boot & linux-imx(kernel). Added node in imx93-11x11-evk-uboot.dtsi file. Added lines related to uart8 in imx93_evk.c(const uart_pads) changed default base address in platform_def.h file. Please guide me any more changes need be done apart from above. Thanks  Robbi. Re: Migrating console from LPUART1 to LPUART8 in imx93 Is this correct approach for SD changes making DAT3 as cd. Re: Migrating console from LPUART1 to LPUART8 in imx93 Thanks @Manuel_Salas ,                                It is working now. And I need solution for the issue as our custom-board is having SD-CARD with slight difference from EVK. we removed GPIO for card detection. So by default DATA3 is used a card detection?. The modifications done only in u-boot-imx: &usdhc2 { pinctrl-names = "default", "state_100mhz", "state_200mhz"; pinctrl-0 = <&pinctrl_usdhc2>, <&pinctrl_usdhc2_gpio>; pinctrl-1 = <&pinctrl_usdhc2_100mhz>, <&pinctrl_usdhc2_gpio>; pinctrl-2 = <&pinctrl_usdhc2_200mhz>, <&pinctrl_usdhc2_gpio>; //cd-gpios = <&gpio3 06 GPIO_ACTIVE_LOW>; vmmc-supply = <&reg_usdhc2_vmmc>; bus-width = <4>; broken-cd; status = "okay"; no-sdio; no-mmc; }; Removed cd-gpios by comment & added broken-cd. But after boot SPL was unable to boot from SD. Please go through the log.txt file.     Thanks  Robbi Re: Migrating console from LPUART1 to LPUART8 in imx93 Hello @Robbi  I hope you are doing very well. Please try the attached patches. Then, you should be able to run ATF and U-boot on the LPUART8. Best regards, Salas.