Multi Source Translation Content

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Multi Source Translation Content

Discussions

Sort by:
i.NX RT 1060 PMIC_ON_REQ 行为 你好, 我正在使用 MIMXRT1062CVJ5B 设计一个定制电路板。电源连接方式如图所示。 关于此配置,您能否帮忙澄清以下几点? (1)施加 VDD_SNVS_IN 后,PMIC_ON_REQ 是否立即变为高电平,还是在钳位之前会有延迟? (2)当 POR_B 被拉低时,PMIC_ON_REQ 的状态是什么?价格会保持高位还是转低? (3)当 VDD_SNVS_IN 电源被移除时,PMIC_ON_REQ 是否变为低电平?在这种情况下,输出电压等级能得到保证吗? (4)VDD_SNVS_IN 是否具有欠压锁定(UVLO)功能?如果是这样,它在多大的电压阈值下会激活? (5)在“波形 - A”所示的情况下,只有 VCC_3V3 关闭(0 V),而 VDD_SNVS_IN 保持供电,这种工作条件是否受支持? 在这种情况下,POR_B 从高到低,然后再从低到高转变。按照上述步骤操作后,i.MX RT1062 能否正常启动并正常运行? 感谢您的支持。 i.MX RT106x Re: i.NX RT 1060 PMIC_ON_REQ behavior 您好, PMIC_ON_REQ 与 VDD_SNVS_IN 相关联,并且是推挽输出。文档中没有明确说明在钳位之前会有延迟。你可以在EVK上测试一下。例如,在 EVKC 上,您可以通过 R282 测量 PMIC_ON_REQ,通过 J30 测量 VDD_SNVS_IN。 文档并未保证当 POR_B 被拉低或 VDD_SNVS_IN 电源被移除时,PMIC_ON_REQ 的输出状态为逻辑低或逻辑高。 您可以参考第 21.3.3 节,i.MX RT1060 处理器参考手册中的电源模式转换部分介绍了不同场景下的 PMIC_ON_REQ 行为,以及 PMIC_ON_REQ 在每种情况下的行为。 i.MX RT1060 的 VDD_SNVS_IN 没有明确记录的 UVLO 规范。参考手册中描述的 SNVS 数字低电压检测器包含一个机制,用于检测 SNVS_LP 电源中断,这可能会导致 LP 控制、状态和安全计数器值发生变化。 关于问题 5,这些情况会在开机、关机还是应用程序代码运行时发生? 此致, 巴勃罗 Re: i.NX RT 1060 PMIC_ON_REQ behavior 你好, 感谢你的回复。 问题 5 中描述的场景假设在正常运行期间,VCC_3V3 上发生了暂时的异常情况,导致电压下降。 此致, 友和 Re: i.NX RT 1060 PMIC_ON_REQ behavior HI 在第 4.1.6 节中i.MX RT1060 数据手册的低功耗模式供电电流描述了一种模式,其中 DCDC_IN = 0 V,VDD_HIGH_IN = 0 V,VDD_SNVS_IN = 3.3 V。有关 SNVS 模式的信息,请参阅 AN12085 的第 5.2.4 节 SNVS 模式:如何使用 i.MX RT 低功耗功能。 要使复位信号有效,必须根据数据手册表 28 复位时序参数中规定的值,至少在一个 RTC_XTALI 时钟周期内钳位。 此致, 巴勃罗
View full article
如果我使用的是树莓派 Pico 2W,如何在 Arduino IDE 中查看 Serial.prints 的输出? 我花了很多时间试图弄明白这件事,但最终一无所获。我尝试运行一个简单的代码,让内置 LED 闪烁,同时在 Serial.print 中打印“hello”。LED 指示灯闪烁,但 pico 没有在串口监视器中输出任何内容。我发现 pico 在上传后会断开连接,然后重新连接,但连接的是不同的端口。我猜我的板是从 COM 5/4 重新连接到 COM 11,但是如果我尝试进入“工具”->“端口”->“COM 11”,LED 指示灯停止闪烁,IDE 显示错误信息,我的笔记本电脑发出类似板断开连接又重新连接的声音。我能做些什么吗?我考虑过从 Arduino IDE 切换到 VS Code,但是没有关于如何在 Windows 上进行切换的教程,而 GPT 也没有教会我太多东西。 Kinetis W系列MCU
View full article
LPC55S06 上的 Hashcrypt 存在漏洞 你好, 我在尝试使用 Hashcrypt 硬件加速时遇到了无限循环。 Hashcrypt 驱动程序版本为2.2.17。微控制器卡在hashcrypt_sha_one_block () 函数的第 679 行: while (0U == (base->STATUS & HASHCRYPT_STATUS_WAITING_MASK))     { //卡在这里     } 令人惊讶的是,它在执行 90 次后似乎就卡住了(我们的微控制器能够执行 89 次hashcrypt_sha_one_block而不会卡住)。 主要调用由 embedTLS ssl_tls.c 完成。文件(参见 err.png)。 这是我目前对 mbedtls_sha256_finish() 的实现(在构建 mbedTLS v3.6.7 时,我需要通过定义 SHA256_ALT 来实现它)。 int mbedtls_sha256_finish ( mbedtls_sha256_context * ctx , unsigned char * output ) { status_t状态; 状态= HASHCRYPT_SHA_Finish ( HASHCRYPT , ( hashcrypt_hash_ctx_t * ) ctx -> hash , 输出, 无效的) ; 返回状态; } 我们的代码是裸机代码,没有不同的流程。 非常感谢您的帮助。 此致, 哈罗德
View full article
How to revert Platform SCP03 keys back to default using se05x_TP_PlatformSCP03keys.c? Hello NXP Community, I am working with the SE051 secure element and would like to ask how to properly revert the Platform SCP03 keys back to their default values using the Plug and Trust Middleware. What I have done so far: I modified demos/se05x/se05x_RotatePlatformSCP03Keys/se05x_TP_PlatformSCP03keys.c by commenting out the key reversion section (between doc:start:revert-scp03-keys and doc:end:revert-scp03-keys). I built and executed the application on my setup. The execution was successful, showing the message: "Congratulations !!! Key Rotation Successful!!!!" To verify the key change, I updated /tmp/SE05X/plain_scp.txt with the new key value (0x4041... for ENC, MAC, and DEK) and successfully connected via ssscli connect. Subsequent operations (ssscli generate rsa, ssscli set aes, and ssscli se05x readidlist) were all completed successfully, confirming that keys were written and IDs were retrieved without issues. Now, I would like to restore the Platform SCP03 keys back to the default keys (defined in sss/ex/inc/ex_sss_tp_scp03_keys.h). Could anyone guide me on how to modify se05x_TP_PlatformSCP03keys.c or what the correct process is to perform this key reversion? Environment: Board: MCIMX8M-WEVK with OM-SE051ARD Plug and Trust MW Version: v04.07.01 OP-TEE OS Version: 3.19.0 Linux Kernel: 6.1.151 OEF ID: A8FA Any advice or code pointers would be greatly appreciated. SE050 Re: How to revert Platform SCP03 keys back to default using se05x_TP_PlatformSCP03keys.c? Hi @Uc_S , If you just need to rotate the keys back to the default, the nano-package example is the recommended simpler path — only the three scp03_* arrays (current keys for auth) and the three NEW_scp03_* arrays (default keys as target) need to be updated, and the revert call within ex_se05x_rotate_scp03_keys() needs to be commented out. Please refer to the following for details. Change 1 — Set the current keys (used to open the SCP03 session) Lines 38–43 are the auth keys passed to ex_set_scp03_keys() . Replace the placeholder 0xABCD... values with your current keys ( 0x4041... 😞 uint8_t scp03_enc_key[AES_KEY_LEN_nBYTE] = { 0x40, 0x41, 0x42, 0x43, 0x44, 0x45, 0x46, 0x47, 0x48, 0x49, 0x4A, 0x4B, 0x4C, 0x4D, 0x4E, 0x4F }; uint8_t scp03_mac_key[AES_KEY_LEN_nBYTE] = { 0x40, 0x41, 0x42, 0x43, 0x44, 0x45, 0x46, 0x47, 0x48, 0x49, 0x4A, 0x4B, 0x4C, 0x4D, 0x4E, 0x4F }; uint8_t scp03_dek_key[AES_KEY_LEN_nBYTE] = { 0x40, 0x41, 0x42, 0x43, 0x44, 0x45, 0x46, 0x47, 0x48, 0x49, 0x4A, 0x4B, 0x4C, 0x4D, 0x4E, 0x4F }; c   Change 2 — Set the NEW target keys (the default SE051C A8FA keys) Lines 45–50 are the keys that will be written into the SE051 via PutKey . Replace the 0x4041... placeholder with the SE051C OEF A8FA default values: uint8_t NEW_scp03_enc_key[AES_KEY_LEN_nBYTE] = { 0xbf, 0xc2, 0xdb, 0xe1, 0x82, 0x8e, 0x03, 0x5d, 0x3e, 0x7f, 0xa3, 0x6b, 0x90, 0x2a, 0x05, 0xc6 }; uint8_t NEW_scp03_mac_key[AES_KEY_LEN_nBYTE] = { 0xbe, 0xf8, 0x5b, 0xd7, 0xba, 0x04, 0x97, 0xd6, 0x28, 0x78, 0x1c, 0xe4, 0x7b, 0x18, 0x8c, 0x96 }; uint8_t NEW_scp03_dek_key[AES_KEY_LEN_nBYTE] = { 0xd8, 0x73, 0xf3, 0x16, 0xbe, 0x29, 0x7f, 0x2f, 0xc9, 0xc0, 0xe4, 0x5f, 0x54, 0x71, 0x06, 0x99 }; c   Change 3 — Comment out the revert block In ex_se05x_rotate_scp03_keys() , comment out lines 85–90 so the code does a single rotation only (current → default) and does not try to rotate back again: /* -- Comment out the revert block below -- */ // SMLOG_I("Reverting SCP03 keys(version - %02x) to OLD KEYS \n", KEY_VERSION); // ret = ex_se05x_change_keys(&se05x_session, &scp03_enc_key[0], &scp03_mac_key[0], &scp03_dek_key[0]); // if (ret != 0) { // SMLOG_E("Error in ex_se05x_change_keys \n"); // return 1; // } c     Have a great day, Kan ------------------------------------------------------------------------------- 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. ------------------------------------------------------------------------------- Re: How to revert Platform SCP03 keys back to default using se05x_TP_PlatformSCP03keys.c? @Kan_Li  Thank you for the clarification. In my case, the current keys are known (0x4041... for ENC, MAC, and DEK), and I can successfully establish an SCP03 session using these keys via ssscli. Since I have the current keys available to authenticate, could you please provide details on how to modify se05x_TP_PlatformSCP03keys.c to perform the key rotation back to the default values? Specifically, I would like to know: Which variables or macros should be updated with the current keys (0x4041...) for authentication during session setup. Which variables or structures should hold the target default key values (ex_sss_tp_scp03_keys.h) for the PutKey operation. Any code snippets or specific line references in se05x_TP_PlatformSCP03keys.c (or related boot/auth headers) would be greatly appreciated. Re: How to revert Platform SCP03 keys back to default using se05x_TP_PlatformSCP03keys.c? Hi @Uc_S , Rotating the Platform SCP03 keys back to the default values is only possible when the current keys are known, as a successfully authenticated SCP03 session is required before any key update ( PutKey ) command can be issued to the SE051. If the current keys have been lost or forgotten, it is not possible to authenticate to the SE051 and perform the key rotation. There is no backdoor or override mechanism — this is by design to preserve the security model of the device. Additionally, a factory reset does not help, as Platform SCP03 keys are explicitly unaffected by the factory reset procedure. In this situation, the only option is to replace the SE051 with a new device that still carries the default NXP-provisioned keys.   Have a great day, Kan ------------------------------------------------------------------------------- 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. ------------------------------------------------------------------------------- Re: How to revert Platform SCP03 keys back to default using se05x_TP_PlatformSCP03keys.c? @Kan_Li  Thank you for providing the detailed guidance. Following your instructions, I updated the keys, commented out the revert block, and successfully built and executed the nano-package example. However, during execution, the SCP03 key update operation failed with a SW status code 6A80 during the PUT KEY APDU command. Here is the summary of the execution log: Plug and Trust nano package - version: 1.6.1 ... Establish Secure Channel to SE05x ! Sending GP Initialize Update Command !!! ... CardCryptogram verified successfully...Calculate HostCryptogram Sending GP External Authenticate Command !!! APDU Tx> :84 82 33 00 10 ... APDU Rx< :69 82 Authentication Successful!!! Created scp03 Session Changing SCP03 keys(version - 0b) to NEW KEYS APDU Tx> :84 d8 0b 81 58 ... APDU Rx< :6a 80 Error in DoAPDUTxRx Error in ex_se05x_change_keys SE05x Rotate SCP03 keys Example Failed ! Regarding potential root causes, I suspect that either the OpenSSL version (OpenSSL 3.x is used on both the build PC and the target evaluation board) is affecting key derivation/formatting during PutKey, or the DEK value in particular might have been mismatched/rewritten previously. At this moment, I do not have sufficient bandwidth to investigate or address these possibilities further. I will look into them separately if time permits later. Thank you again for your assistance. Re: How to revert Platform SCP03 keys back to default using se05x_TP_PlatformSCP03keys.c? Hi @Uc_S , Thank you for the detailed execution log — it provides exactly what is needed to pinpoint the issue. Your two suspects are both valid and well-reasoned. Here is a breakdown of what is most likely happening. What the 6A80 Error Tells Us SW 6A80 ( SW_WRONG_DATA ) means the SE051 rejected the data field of the PUT KEY APDU as cryptographically invalid. Since your log shows that authentication completed successfully (CardCryptogram verified + External Authenticate passed), the ENC and MAC keys are confirmed correct. The failure is isolated specifically to the PUT KEY step, which points directly to an issue with the DEK key or the AES encryption used to wrap the new key material. Suspect 1: DEK Key Mismatch — Most Likely Primary Cause Inside the PUT KEY command, each new key is encrypted under the current DEK before being sent to the SE. If the DEK value in the host code does not exactly match the DEK stored on the device, the SE decrypts garbage and returns 6A80. A near-identical case from a prior SE051C1 customer concluded: "If the minimal example works with PlatformSCP, then ENC and MAC keys are correct. As key rotation still fails, this means the DEK key needs to be wrong... the DEK key may have been set wrongly in the past." This is the most probable root cause given your history — a prior incomplete or incorrect rotation may have left the SE051's DEK in a state that no longer matches 0x4041... . Confirmation step: Test the same code on a brand-new, factory-fresh SE051 sample. If it succeeds immediately, this confirms that the current device's DEK state is corrupted/unknown, and the chip should be replaced — there is no recovery path without the correct DEK. Suspect 2: OpenSSL 3.x Compatibility — Real Risk, Secondary Cause The nano-package's SCP03 crypto path uses the legacy low-level OpenSSL API: AES_set_encrypt_key((uint8_t *)key, keylen * 8, &AESKey); AES_ecb_encrypt(srcData, destData, &AESKey, AES_ENCRYPT); The nano-package was designed and tested with OpenSSL 1.1.1 only. In OpenSSL 3.x, these APIs are deprecated and require the legacy provider to be explicitly loaded at runtime. If it is not loaded, these calls can silently produce incorrect output — which would corrupt the DEK-encrypted payload and also trigger 6A80. Recommended fix: Switch the nano-package to use mbedTLS as the host crypto backend ( -DEX_SE05X_USE_MBEDTLS=1 ), which does not rely on deprecated OpenSSL APIs and is fully supported for this use case. Alternatively, rebuild against OpenSSL 1.1.1 to test the OpenSSL version hypothesis in isolation. Recommended Action Sequence Test on a fresh SE051 first — this is the fastest way to confirm whether the current device's DEK is the root cause. Switch to mbedTLS for the host crypto backend to eliminate any OpenSSL 3.x risk going forward. If the fresh device also fails with mbedTLS, please share the build environment details (OS, compiler, mbedTLS version) for further investigation. Please note: if the current device's DEK is confirmed to be in an unknown state, there is no way to recover it — a replacement chip with factory-default keys will be required. Please let us know the result of the fresh sample test and we will be happy to assist further. Have a great day, Kan ------------------------------------------------------------------------------- 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. ------------------------------------------------------------------------------- Re: How to revert Platform SCP03 keys back to default using se05x_TP_PlatformSCP03keys.c? @Kan_Li  Thank you very much for the detailed explanation and analysis regarding the 6A80 error. The breakdown of the DEK key mismatch and the OpenSSL 3.x compatibility risks (along with the suggestion to use mbedTLS) is helpful and clarifies the exact mechanisms at play. I will keep these suggested options -- such as testing on a fresh sample and considering mbedTLS for the crypto backend -- in mind for future troubleshooting when resources and bandwidth allow.
View full article
i.MX8M Plus – Is there any way to access MIPI CSI-2 Embedded Data (DT 0x12) together with RAW image Hello NXP Community, we are currently integrating a MIPI CSI-2 RAW image sensor with an i.MX8M Plus and would like to clarify whether there is any supported or technically possible way to make the sensor's CSI-2 Embedded Data (Data Type 0x12) available to software on the target. Our camera stream has the typical CSI-2 structure: Frame Start Embedded Data DT = 0x12 RAW image data DT = 0x2A / 0x2B / 0x2C Frame End The image data is captured through the MIPI CSI-2 receiver → Gasket → ISI → memory/V4L2 path and this part is working correctly. The problem is that we additionally need the Embedded Data belonging to each frame. The metadata contains frame-related sensor information, and therefore it is important that the metadata can be associated with the corresponding captured image. According to the i.MX 8M Plus Applications Processor Reference Manual, the MIPI CSI-2 receiver provides configurable data-type handling through the CSI-2 receiver registers, in particular the MIPI_CSIx_ISP_CONFIG0 / DATAFORMAT configuration. The relevant MIPI CSI-2 Rx / CSIS register descriptions are in Chapter 13.5, MIPI CSI-2, and in older revisions of the Reference Manual the supported image data types are described around Section 13.5.6.13. We also found NXP Application Note AN13857 – i.MX 8M Series MIPI Capture System, especially Section 7, "Embedded data support". AN13857 states that a stream containing Embedded Data with DT=0x12 and image data with another data type is considered data type interleaving, and that the i.MX 8M series capture system does not support this mode. The suggested workaround is to configure the sensor to transmit the embedded data using the same data type as the image data. Unfortunately, this workaround is not possible with our sensor. The sensor transmits standard CSI-2 Embedded Data using DT 0x12, while the image data uses the corresponding RAW data type. The Embedded Data data type cannot be changed to the RAW image data type. However, we found an older NXP Community discussion specifically concerning the i.MX8MP where NXP TechSupport stated that the CSI hardware should support DT=0x12, while the BSP did not support metadata at that time: https://community.nxp.com/t5/i-MX-Processors/I-MX8MP-capture-MIPI-embedded-data/td-p/1383845 There is also an older discussion about accessing CSI-2 Embedded Data on i.MX8M devices: https://community.nxp.com/t5/i-MX-Processors/Does-iMX8M-CSI-support-metadata-embedded-data/m-p/977554 Therefore, we would like to clarify whether the limitation described in AN13857 applies to the complete hardware path, or mainly to the currently supported ISI/V4L2 capture architecture. Our main question is: Is there any way on the i.MX8M Plus to receive or access the payload of CSI-2 packets with Data Type 0x12 while simultaneously capturing the RAW image stream, even if this requires modifications to the Linux driver? For example, would any of the following approaches be technically possible? Route DT=0x12 and the RAW image data through different CSI/ISI paths or channels. Access the Embedded Data before the ISI, directly from the MIPI CSI-2 receiver. Configure an additional CSI-2 receiver channel/interface for DT=0x12. Use another DMA or memory path for the Embedded Data. Extend the NXP Linux CSI/ISI driver to expose the Embedded Data as a V4L2 metadata node or separate /dev/videoX device. Use any undocumented or currently unsupported hardware functionality of the CSI-2 receiver that would allow the DT=0x12 payload to reach memory. We do not necessarily require an officially supported V4L2 metadata implementation. If the i.MX8M Plus hardware is capable of transferring the DT=0x12 payload to memory, we would also be interested in implementing the necessary kernel/driver changes ourselves. Could NXP please clarify whether the restriction described in AN13857 is: a fundamental hardware limitation of the i.MX8M Plus CSI-2 → Gasket → ISI architecture, meaning that the DT=0x12 payload cannot be transferred to memory while RAW image data is being captured, or a software/driver limitation, for which a custom driver implementation could provide access to the Embedded Data? If it is a hardware limitation, is there any alternative mechanism on the i.MX8M Plus to obtain the Embedded Data payload without changing the camera's CSI-2 output format? Thank you for any clarification or implementation hints. Best regards, Peter Re: i.MX8M Plus – Is there any way to access MIPI CSI-2 Embedded Data (DT 0x12) together with RAW im Hello, The limitation in application note is a hardware architecture limitation of the i.MX8M Plus CSI. The downstream ISI block has no mechanism to separate DT=0x12 payload from the RAW stream. Unfortunately, there is no supported or officially workaround that mentioned in application note. Best regards. Re: i.MX8M Plus – Is there any way to access MIPI CSI-2 Embedded Data (DT 0x12) together with RAW im Does the answer change when using the integrated ISP instead of the ISI? Our RAW Bayer stream can alternatively be routed from the MIPI CSI-2 receiver to the integrated ISP. Is there any mechanism in the ISP capture path to receive or preserve CSI-2 Embedded Data packets (DT=0x12)? In particular, can the ISP or its input interface separate the RAW image data and Embedded Data, or provide the Embedded Data to software through an ISP statistics/metadata buffer? If not, are the DT=0x12 packets simply discarded by the CSI-to-ISP pixel interface?
View full article
在 KW45B41Z-EVK 上实现 AI/ML NXP社区的各位好, 我正在开发一款适用于KW45B41Z-EVK (Cortex-M33) 的边缘 AI 应用,希望就如何在该板上部署机器学习模型获得一些建议。 由于 KW45 SDK 默认不包含 eIQ/TFLM 中间件,我的计划是: 模型训练:使用eIQ Time Series Studio (eIQ TSS)训练一个用于时间序列数据的 n 类分类模型。由于 eIQ TSS 中未列出 KW45 作为目标平台,因此我选择FRDM-MCXN947 (Cortex-M33) 作为导出模型的目标平台。 运行时部署:将FRDM-MCXN947 SDK中的 中间件/eiq/tensorflow-lite 文件夹移植到我的 KW45 SDK 项目中,并将其与 CMSIS-NN 链接。 我的问题: 将 eIQ TFLM 中间件从 MCXN947 SDK 移植到 KW45 SDK 是否是一种有效且受支持的方法? 在 eIQ TSS 中选择 FRDM-MCXN947 是否适合生成在 KW45 上运行的模型? 在 KW45B41Z-EVK 上实现 AI/ML 是否有其他推荐的或原生工作流程? 感谢您的帮助! KW45B41Z-EVK KW45 EIQ-TFLITE-MICRO EIQ-工具包#AIML Re: Implementing AI/ML on KW45B41Z-EVK 你好,希望你一切都好。 如果您使用的是 eIQ Time Series Studio (TSS),我建议您将项目从 FRDM-MCXW71 移植过来。它是 eIQ TSS 官方支持的目标,并且在软件上与 KW45 兼容。这两个设备都采用相同的 Cortex-M33 内核架构和类似的内存配置,因此生成的库应该与您的硬件更加匹配。 当使用硬件配置差异很大的设备(例如 FRDM-MCXN947)作为移植目标时,可能会生成不兼容的模型,例如,由于两个设备之间的可用 RAM 存在差异,或者生成了专门针对 MCXN947 的 NPU 加速模型。 希望这能帮到你! 此致, 索菲亚。
View full article
IMX95:配备 MIPI DSI 和双通道 LVDS 的显示器 您好, 我可以同时将不同的信号源输出到 DSI 和双通道 LVDS 吗? 如果支持此功能,如何配置设置? 我参考了IMX95 手册和设备树,但我还是不明白 pixel_interleaver、LDB 和 MIPI-DSI 之间的关联。 谢谢。 Re: IMX95: Displays with a MIPI DSI and a dual-channel LVDS 对于普通的 i.MX95 电路板支持包/设备树模型:不要计划同时驱动独立的 MIPI-DSI 显示器和双通道 LVDS 显示器。限制点在于显示输出路由:i.MX95 显示控制器有两个独立的显示输出流,双通道 LVDS 占用了两个 LVDS 侧路径,在标准配置中没有为 MIPI-DSI 留下空闲的输入路径。 这里有一个重要的细节:NXP 社区知识库中的一篇文章提到了适用于 LF-6.6.52-2.2.0 的 i.MX95 三屏 Linux 补丁,支持“1 个 MIPI DSI + 2 个 LVDS”接口,以及名为 imx95-19x19-evk-triple-display-lvds-clone.dtb 的 DTB 文件。和 imx95-19x19-evk-triple-display-lvds-interleaver.dtb。这应该被视为一个经过特定补丁的 EVK/BSP 用例,而不是未修改的参考手册/设备树支持任意独立的 DSI + 双通道 LVDS 路由的证据。 该关联大致如下: 区块 在显示路径中的作用 显示引擎/DPU 输出 生成两个显示流,DISP_IN0 和 DISP_IN1。 像素交错器 对这些数据流进行路由或拆分。在旁路模式下,DISP_IN0 输出到 PL_OUT0,DISP_IN1 输出到 PL_OUT1;在交错模式下,一个选定的输入流被交错传输,而另一个输入流被旁路传输。 LVDS / LDB / 像素映射器 i.MX95 LVDS 路径接收一个或两个显示界面流并驱动 LVDS PHY;RM 描述了驱动 LVDS PHY1 和 LVDS PHY2 的像素映射器。某些 Linux/设备树命名可能仍然使用“LDB”,但在 i.MX95 的架构上,这是像素交错器/像素映射器后面的 LVDS 输出路径。 MIPI-DSI DSI 通过像素链路路径获取像素数据;DSI 像素格式化块将像素链路格式转换为 DSI 主机 DPI 格式,DSI 像素链路控制字段选择连接到 DSI 主机控制器的像素链路。 因此,对于标准配置: 单通道 LVDS + MIPI-DSI :可行;一条显示输出路径可以馈送 LVDS,另一条可以馈送 DSI。 仅支持双通道 LVDS :可行;两个 LVDS 通道同时用于 LVDS 显示。 独立 MIPI-DSI + 双通道 LVDS :当前证据所描述的标准路由不支持;NXP 社区分析指出,双通道 LVDS 会占用两个可用的 DPU 输出端口,因此 MIPI-DSI 不能同时路由。 对于配置方面,我不会尝试仅通过手动更改 pixel_interleaver 寄存器值来修复此问题。在 Linux 系统中,路由由 DRM 设备树图建立:DPU / 显示像素链路端点必须连接到 LVDS/LDB 或 MIPI-DSI 端点。如果 DSI 节点没有有效的上游端点,驱动程序会报告错误,例如 imx95-mipi-dsi ... 未找到有效的输入端点。对于受支持的设置,请使用相应的 电路板支持包。 DTB/overlay: 仅限 LVDS:使用适用于预期 LVDS 通道/模式的 LVDS DTB。 仅限 DSI:使用 DSI 面板/桥接 DTB。 单 LVDS + DSI:将一个像素链路输出路由到 LVDS,另一个路由到 DSI。 三屏显示/DSI + 2 LVDS:从 NXP LF-6.6.52-2.2.0 三屏显示补丁集及其提供的 DTB 开始,前提是该补丁集与您的 BSP 和 EVK 基线匹配。 总之:对于普通的 i.MX95 电路板支持包,可以使用双通道 LVDS 或 DSI + 单通道 LVDS;对于 DSI 加两个 LVDS 输出,请使用 NXP 特定的三屏显示补丁流程,而不是尝试仅从 RM 寄存器中导出它。 Re: IMX95: Displays with a MIPI DSI and a dual-channel LVDS 谢谢你的回复。我学到了很多。 此功能并非必需。我这样做的原因是我的目标板有两个接口:2ch-lvds 和 mipi-dsi,但我不想每次需要更换显示器进行测试时都重置 fdt 文件。 Re: IMX95: Displays with a MIPI DSI and a dual-channel LVDS NXP 是否有发布任何关于独立三屏显示支持的官方文档?
View full article
PFE EMAC0 ECU唤醒后无效缓冲区访问 你好, 我已经将 EMAC0 配置为 2500 MBPS,并进行了所需的 SERDES 通道配置。ECU运行期间,以太网通信正常进行。 关闭所有访问以太网通信的应用程序后,我从ECUM触发ECU睡眠请求,将MCU模式设置为SOC待机模式,并选择HSE_CM7作为主核心。 ECU唤醒后恢复正常运行,COM、SOAD、TCPIP和ETHIF层工作正常。但在ETHIF层调用“提供TX缓冲区”API时,返回错误信息,提示TX缓冲区已满,导致无法发送以太网帧。 以下列出了尝试解决此问题的修复方法: 1. 尝试使用“Eth_43_Pfe_Deinit”关闭 PFE 驱动程序,并通过调用“Eth_43_Pfe_Init”启动 PFE 驱动程序,但如果执行 Init API,CPU 将在执行后锁定。 2. 尝试使用 Eth_43_Pfe_SetController 模式将以太网控制器关闭,然后通过将模式设置回“Active”来激活它,结果导致总线故障。 请告知此问题的潜在解决方案。 PS> 使用的配置器:EB tresos 以太坊 PFE RTD 版本:1.3.0 SDK:GOLDVIP Re: PFE EMAC0 Invalid Buffer Access Post ECU wakeup 你好,Avinash_7373 感谢您的回复。 1.当 SOC 进入待机模式时,分区 2 的 PFE 时钟将被禁用,唤醒后应检查是否已重新启用分区 2。您可以尝试在 PFE 初始化之前检查 PRTN2_STAT.PCS 状态。 2. 检查 SERDES 是否正常工作。 BR 乔伊 Re: PFE EMAC0 Invalid Buffer Access Post ECU wakeup 嗨@Joey_z 1.PFE 仅用于 M 型核心。 2. 我使用的是开发板: S32G-VNP-RDB3 问候, 阿维纳什·V Re: PFE EMAC0 Invalid Buffer Access Post ECU wakeup 你好,Avinash_7373 感谢您与我们联系。 1. PFE 是否仅用于 M 核心?你们都用过A核心组件吗? 2.您使用的是客户的开发板还是我们的开发板? BR 乔伊 Re: PFE EMAC0 Invalid Buffer Access Post ECU wakeup 嗨@Joey_z , Partition_2 状态寄存器中的位域在睡眠前保持为1 ,在睡眠状态下更新为0 ,在唤醒后(即 MCU 模式设置为正常后)更新回1 。 SerDes 工作正常。此外,我还尝试了 EMAC2 的 RGMII 模式,其中 ETH Phy 连接器 (RJ45) 和控制器 (NXPS32G399A) 之间不涉及 SERDES,即使在这种情况下,问题仍然存在。 如果 Partition_2 在唤醒后需要任何重启顺序,请告知。 问候, 阿维纳什·V Re: PFE EMAC0 Invalid Buffer Access Post ECU wakeup 你好,Avinash_7373 您的问题很可能是唤醒后 PFE 初始化问题。检查时钟和相关的 PFE 配置,并确保其已初始化到理想状态。 1. 检查 PFE 初始化是否已放入引导加载程序中,并在应用程序唤醒后正确重新初始化。 2. 根据备用流程检查相关配置。请参阅 RM 32.5.5“运行模式到待机模式”。 BR 乔伊 Re: PFE EMAC0 Invalid Buffer Access Post ECU wakeup 嗨@Joey_z , 请查看以下睡眠-觉醒顺序: 1. 我正在使用 API " EcuM_SelectShutdownTarget()"请求 ECU 进入睡眠模式,这反过来会根据 ECUM 的实现将 MCU 模式设置为待机模式。 2. 当ECU进入睡眠模式后,它会轮询唤醒事件,CAN收发器检测到总线活动并使用EcuM_SetWakeupEvent() API设置唤醒事件,然后ECU恢复正常运行。 关于引导加载程序,NXP引导加载程序(blob文件刷写在闪存的0x0地址)和M-core应用程序刷写在0x400000地址。A核心目前在任何地方都没有使用。 问候, 阿维纳什·V Re: PFE EMAC0 Invalid Buffer Access Post ECU wakeup 你好,Avinash_7373 感谢您的回复。 能否介绍一下你们的待机和唤醒顺序? 1. 如何设置核心和分区? 2.你的应用程序中是否使用了引导加载程序和A核心? BR 乔伊 Re: PFE EMAC0 Invalid Buffer Access Post ECU wakeup 你好, Avinash_7373 你的问题有进展吗?如果您需要继续获得支持,请将您的代码上传到以下链接,以便我们更好地分析问题? https://support.nxp.com BR 乔伊
View full article
在 S32 DS 中创建 .MEX 文件 您好, 我使用 S32 Design Studio 3.4 进行项目活动。实际上,我看到了.mex示例项目中存在该文件。那个.mex该文件帮助我了解外围设备、时钟和引脚连接。 现在,根据我的要求,我创建了一个包含 Makefile 的新项目,并且构建成功了。但在这个项目中,我没有使用 .mex 文件。文件。所以我计划创建一个 .mex 文件。请按我的要求提交文件。但我不知道如何创建 .mex 文件。我的项目文件。 所以,请问您能告诉我创建 .mex 文件的步骤吗?我的项目文件?如果您还需要其他信息,请告诉我。 注:我使用的是S32K344开发板。 Re: Create a .MEX File in S32 DS 我的列表是空的!!? 甚至已经安装了`S32SDK_S32K1xx_RTM_4.0.2.exe`: CY9_0-1787711160177.png -- 顺便问一下, S32 Design Studio for S32 Platform 版本:3.6.10 版本 ID:260720 Re: Create a .MEX File in S32 DS 你好,阿杰, .mex域名有两种获取方式。文件已创建: 项目创建期间。当您使用“新建应用程序项目向导”并选择平台 SDK 时,它将创建一个 .mex 文件。文件包含在生成的项目中。 image.png 如果您已有项目并希望添加 .mex 文件,首先,在文件中附加 SDK。 在“项目资源管理器”视图中右键单击项目名称,然后选择“SDK”。 接下来,从列表中选择 SDK,然后单击“附加/分离”,全选,然后单击“确定”、“应用”和“关闭”。 如果提示检查冲突文件,请选中“替换所有文件”和“备份项目文件”复选框,然后单击“确定”。 现在您将拥有一个 .mex 域名。文件 希望对您有所帮助。 Mike
View full article
总线关闭状态下的 FLEXCAN_EnterFreezeMode 问题 您好,NXP团队: 我认为 FLEXCAN_EnterFreezeMode() 中实现的 ERRATA_9595 解决方法存在潜在问题。 我们使用的是集成在 Zephyr hal_nxp 中的 NXP MCUXpresso FlexCAN 驱动程序,基于以下提交: hal_nxp 提交:3c64cd63 当 FlexCAN 控制器处于总线关闭状态时调用 FLEXCAN_EnterFreezeMode() 会出现此问题。 1.问题描述 在 ERRATA_9595 总线关闭路径中,实现按以下顺序执行: 将 MCR.FRZ 设置为 1 将当前 MCR 值保存到 u32TempMCR 中 将 MCR.SOFTRST 设置为 1 等待软复位完成 等到 MCR.FRZACK 变成 1 使用以下方法恢复 MCR: base->MCR = u32TempMCR; 问题是,当保存 u32TempMCR 时,MCR.HALT 仍然为 0。 在正常的非总线关闭路径中,进入冻结模式时会明确设置 HALT。 但是,在“总线关闭”分支中,MCR 值是在设置 HALT 之前保存的。 因此,u32TempMCR 大约包含: FRZ = 1 停止 = 0 软复位后,驱动程序会等待 FRZACK 变为 1。 然而,紧接着它会执行: base->MCR = u32TempMCR; 因为 u32TempMCR.HALT 为 0,所以会再次清除 HALT。 因此,即使 FLEXCAN_EnterFreezeMode() 即将成功返回,FlexCAN 控制器也会退出冻结模式。 2. 由此导致的失败 这会导致 Zephyr mcux_flexcan_add_rx_filter() 路径出现问题。 只有在 FlexCAN 处于冻结模式时才能修改 RXIMR 寄存器。 该序列大致如下: FLEXCAN_EnterFreezeMode(base); base->RXIMR [index] = mask; 如果控制器处于总线关闭状态,则在恢复 MCR 并将 HALT 设置为 0 后,FLEXCAN_EnterFreezeMode() 可以返回。 因此,当 FlexCAN 实际上不再处于冻结模式时,就会发生以下 RXIMR 访问。 在我们的平台上,这会导致总线故障。 3.预期行为 FLEXCAN_EnterFreezeMode() 成功返回后,我预期控制器会保持在冻结模式,并执行以下操作: MCR.FRZ = 1 MCR.HALT = 1 MCR.FRZACK = 1 控制器应保持此状态,直到调用 FLEXCAN_ExitFreezeMode() 为止。 4.实际行为 在 ERRATA_9595 总线关闭路径中,实际顺序为: FRZ 设置为 1 MCR 在 HALT 仍为 0 时被保存。 执行软复位 FRZACK 变为 1 已恢复已保存的 MCR 值 HALT 再次变为 0 控制器退出冻结模式 然后 FLEXCAN_EnterFreezeMode() 返回 5.可能的解决方法 一个可能的最小修复方法是确保在恢复之前,已将保存的 MCR 值设置为 HALT。 例如,而不是: u32TempMCR = base->MCR; 使用: u32TempMCR = base->MCR | CAN_MCR_HALT_MASK; 然后,步骤 8A MCR 恢复将保持 HALT 钳位: base->MCR = u32TempMCR; 在恢复 MCR 后,FLEXCAN_EnterFreezeMode() 返回成功之前,再次验证 FRZACK 可能也很有用。 6.相关NXP社区讨论 NXP 社区也进行了讨论,NXP 支持人员确认,仅凭 FRZACK 并不一定意味着 FlexCAN 控制器仍处于冻结模式。 讨论表明,进入冻结模式时,FRZ 和 HALT 都应该被钳位。 这似乎与此处描述的问题一致:ERRATA_9595 解决方法观察到 FRZACK,但随后恢复了 HALT 为 0 的 MCR 值。 7.问题 NXP FlexCAN驱动程序团队能否确认以下事项? 在 ERRATA_9595 总线关闭路径中,将 HALT 值设为 0 来恢复 MCR 是否是故意的? 当 FLEXCAN_EnterFreezeMode() 成功返回时,HALT 是否应该保持设置状态? 是否存在针对此行为的内部问题或更新的 MCUXpresso SDK 补丁? 在恢复 MCR 之前,在 u32TempMCR 中设置 CAN_MCR_HALT_MASK 是否是正确的解决方案?   如有需要,我们可以提供注册记录和其他复制信息。 i.MX RT106x Re: FLEXCAN_EnterFreezeMode issue in Bus Off state 嗨,May, 感谢您与 SDK FlexCAN 驱动程序团队确认此事。 是的,这与我们的分析相符。确保在恢复 MCR 时 HALT=1 可以使模块在 FLEXCAN_EnterFreezeMode 返回后保持冻结模式。 我们复现的结果还显示,故障不会在 FLEXCAN_ExitFreezeMode 模式下发生。 在本例中,调用顺序为: mcux_flexcan_add_rx_filter FLEXCAN_进入冻结模式 写入 RXIMR 当控制器已处于总线关闭状态时,FLEXCAN_EnterFreezeMode 将 MCR 恢复为 HALT=0。然后该函数返回,Zephyr 立即写入 RXIMR 寄存器。 由于 RXIMR 只能在冻结模式下写入,因此这种访问会导致我们平台上的总线故障。 因此,恢复 HALT=0 似乎不仅会导致 FLEXCAN_ExitFreezeMode 出现问题,还会导致在 FLEXCAN_EnterFreezeMode 返回后立即执行的任何仅针对冻结模式的寄存器访问出现问题。 建议的解决方案: u32TempMCR = base->MCR | CAN_MCR_HALT_MASK; 或者,在恢复 MCR 时确保 HALT=1 可以解决这两种情况。 请您也确认一下: 哪个 MCUXpresso SDK / FlexCAN 驱动程序版本包含此修复程序? 是否已有内部问题 ID 或可用的补丁/提交? 此修复程序是否也会向后移植到现有的 SDK 版本中? 如果可能的话,我们希望将官方修复程序移植到 Zephyr hal_nxp 中。 再次感谢您确认这个问题。 Re: FLEXCAN_EnterFreezeMode issue in Bus Off state 嗨@zixuan-dev , 非常感谢您对我们产品的关注以及对我们社区的使用。 感谢您详尽的分析。 我已向SDK FlexCAN驱动程序团队确认过这一点。 应用 ERR009595 解决方法时,模块在请求冻结模式之前会进入总线关闭状态。根据目前的实现方式,在软复位之前,保存的值为 FRZ=1,HALT=0。 软复位后,MCR 寄存器由硬件复位为默认值 0x5980000F,其中 FRZ=1 且 HALT=1。 但是,在使用先前保存的值恢复 MCR 寄存器后,FRZ=1,HALT 被强制设为 0。 FLEXCAN_ExitFreezeMode 清除 HALT,然后清除 FRZ 以退出冻结模式。当 HALT 已经为 0 时再次清除它,就会发生硬故障。 解决方法是在恢复 MCR 寄存器时设置 HALT=1。这样一来,在退出冻结模式时清除 HALT 就不会出现问题。 感谢您报告此问题。 顺祝商祺! 5月 Re: FLEXCAN_EnterFreezeMode issue in Bus Off state 嗨@zixuan-dev , 感谢您提供的最新信息。 该修复程序最早将在 SDK 26.12.00 PVW-1 中提供,FlexCAN 驱动程序版本为 2.16.1。 顺祝商祺! 5月
View full article
Top Mobile App Maintenance Company in 2026 JPLoft is one mobile app maintenance company worth considering in 2026. It provides mobile app maintenance and support services, including bug fixes, performance monitoring, security updates, feature enhancements, compatibility updates, and ongoing technical support. Re: Top Mobile App Maintenance Company in 2026 That is a solid list of maintenance services to look for. The security updates and compatibility checks are probably the most important ones to keep an eye on. Re: Top Mobile App Maintenance Company in 2026 I've used JPLoft for app maintenance and their bug fixes are reliable. Separately, when setting up my own business, the privacy company formation package kept my home address off public records, which made registration smooth and stress-free. Re: Top Mobile App Maintenance Company in 2026 I’ve used JPLoft for app maintenance too, and their bug fixes and performance updates have been consistently solid for our needs.
View full article
S32DS 3.6.2 I have a question about S32DS 3.6.2.I'm having an IDE configuration issue. I'm using a demo program generated by RTD 6.0.0, and I'm encountering the problem shown in the image below when configuring CT. What could be causing IVT and other tools to be disabled? I'm a bit confused. Re: S32DS 3.6.2 Hello @sunshine88 , IVT/DCD support in Configuration Tools depends on the selected device and on the scope implemented in the installed tool package. The fact that the IVT editor is disabled does not mean that the RTD example project is invalid.   For the selected S32K358 configuration, the graphical IVT/DCD editors are not available in Configuration Tools. These tools are related to BootROM/boot-image configuration and are not required for the standard projects.   Therefore, if Update Code and the project build complete successfully, the project can still be used normally for the supported configuration areas such as Pins, Clocks and Peripherals. Best regards, Pavel
View full article
交换请求:通过 Hse_Ip_ServiceRequest 发送的 HSE_SRV_ID_ACTIVATE_PASSIVE_BLOCK 返回 0xAA55A11E 您好,目前我正在尝试对 S32K314HMS 微控制器进行 A/B 交换。交换请求通过以下方式提出:   /* 重置作业状态变量 */       交换作业状态=交换作业待处理; /* 设置 HSE 请求的服务描述符 */ swapHseSrvDescriptor.srvId = HSE_SRV_ID_ACTIVATE_PASSIVE_BLOCK; /* 设置要发送到 HSE IP 层的请求参数 */       swapHseIpRequest.eReqType = HSE_IP_REQTYPE_ASYNC_POLL ;​​       swapHseIpRequest.u32Timeout = SWAP_TIMEOUT ;​​ swapHseIpRequest.pfCallback = SwapProcessMuChannelResponse; /* 向 HSE IP 层发送服务请求 */ 如果 (HSE_SRV_RSP_OK != Hse_Ip_ServiceRequest(SWAP_MU_INSTANCE, SWAP_MU_ADMIN_CHANNEL, &swapHseIpRequest, &swapHseSrvDescriptor))     {          结果= E_NOT_OK ;      } 然后会执行 swapHseIpRequest.pfCallback ( SwapProcessMuChannelResponse ) ,返回的 HseResponse 将是: static void SwapProcessMuChannelResponse ( uint8 u8MuInstance , uint8 u8MuChannel ,                                              hseSrvResponse_t HseResponse , void * pCallbackParam ) {    如果( HseResponse == HSE_SRV_RSP_OK )     {       vFotaH_Appl_SwapJobStatus = SWAP_JOB_OK ;    }    别的     {       vFotaH_Appl_SwapJobStatus = SWAP_JOB_FAILED ;       VStdLib_ConvertUint32ToUint8ArrayBigEndian (( uint32 ) HseResponse ,调试数据);    } } #define HSE_SRV_RSP_NOT_SUPPORTED (( hseSrvResponse_t ) 0xAA55A11EUL ) /**< @brief 不支持此操作或功能。 */ 这种情况偶尔会发生,有时交换会按预期进行。原因可能是什么?我可以在哪里找到 HSE 返回此返回代码的原因/情况? 此交换是在更新序列结束时触发的,在RESET/上电几分钟后(因此 HSE 已 100% 初始化)。 Re: Swap request: HSE_SRV_ID_ACTIVATE_PASSIVE_BLOCK via Hse_Ip_ServiceRequest returns 0xAA55A11E 嗨@AlexI 这是一个非常简单的服务,没有任何参数。我唯一的解释就是这是数据缓存内存造成的。请确保将描述符放置在不可缓存的内存中。 通常情况下,所有用于与 HSE 通信的数据对象都必须强制存储在不可缓存的内存中,因为 HSE 无法访问缓存。 虽然这可能不是本案的原因,但是:如果使用 DTCM 内存,则必须使用后门地址。普通地址仅对拥有该内存的核心可见。其他总线主控器(其他核心、DMA、HSE 等)只能通过后门地址看到此内存。 此致, Lukas Re: Swap request: HSE_SRV_ID_ACTIVATE_PASSIVE_BLOCK via Hse_Ip_ServiceRequest returns 0xAA55A11E 感谢@lukaszadrapa 的回复。 我修改了实现方式,使swapHseSrvDescriptor 和swapHseIpRequest具有初始值,并在启动时由链接器初始化而不是在运行时初始化,现在可以正常工作了。
View full article
iMX8M Plus - Flexspiチップセレクトピン i.MX8M Plus EVKでは、ECSPIチップ選択信号をGPIOピンで設定できます。 FlexSPIがGPIOベースのチップセレクト信号もサポートしているのか、それとも専用のFlexSPIチップセレクトピンのみが使えるのか確認していただけますか? 当社の要件に基づき、FlexSPIには2つのチップセレクト信号が必要です。FlexSPIデバイスを2台サポートするための推奨構成をご提案ください。 Re: iMX8M Plus - Flexspi chip select pin こんにちは@pengyong QSPIの2チップセレクトで何ができるでしょうか?これも私たちの要件です。もしCSのピン手段が不足している場合、チップセレクトがあるGPIOを使ってもいいのでしょうか?うまくいくなら Re: iMX8M Plus - Flexspi chip select pin こんにちは、 @Govind1807さん GPIOベースのチップセレクト信号を使うこともできます。しかし、FlexSPIフラッシュデバイスは2つしかありません。なぜGPIOをチップセレクト信号として使用するのですか? imx8mpには4つのFLEX SS信号があり、直接使用できます: https://github.com/nxp-imx/linux-imx/blob/5768b67a64961d932b7c50adf15ba3f5bfcc8f70/arch/arm64/boot/dts/freescale/imx8mp-pinfunc.h BR Re: iMX8M Plus - Flexspi chip select pin こんにちは@pengyong_zhang QSPIの2チップセレクトで何ができるでしょうか?これも私たちの要件からです。もしCSのピン手段が不足している場合、チップセレクトがあるGPIOを使ってもいいのでしょうか?それがうまくいくかどうかは? Re: iMX8M Plus - Flexspi chip select pin こんにちは、 @Govind1807さん QSPIの2チップセレクトで何ができるでしょうか? >>>QSPI CSの設定方法については、以下のdtsファイルを参照してください。 https://github.com/nxp-imx/linux-imx/blob/5b372337acc9c764ce9e92f272e69d0b494ab38f/arch/arm64/boot/dts/freescale/imx8mp-evk.dts#L1122 これも私たちの要件です。もしCSのピン手段が不足している場合、チップセレクトがあるGPIOを使ってもいいのでしょうか?それがうまくいくかどうか? >>>はい、ドライバーがGPIOをサポートしていれば、CSピンにGPIOを使うことは可能です。 BR
View full article
To complement solution how to printf float number in MCUXpresso IDE Hi: In previous topics there are some discussions how to print float number in MCUXpresso IDE and SDK. To try them and summarize the final solution: 1.PRINTF the float number to UART console set below macro in project configuration->C/C++ build ->setting PRINTF_FLOAT_ENABLE=1 such code will work. float test1 = 0.15; PRINTF("%f\r\n",test1); 2.Transform float number to string by sprintf() function. there is one error in SDK user manual, " Ensure Redlib: Use floating point version of printf is selected " during project creation does not work. The default C library Redlib doesn't support floating, so it couldn't work with redlib. The correct solution are: (1)Change link library to NewLib, it's full C library and support float  printf. But notice need include in related c file, or else sprintf(float) doesn't work as expected. (2)Change link library to NewLib Nano, it's compact C library , and need click "enable print float" to enable float function, which actually add " -u _printf_float" link symbol. But notice need include in related c file, or else sprintf(float) doesn't work as expected. So the solution surely add flash & RAM consumption in project, but for i.MXRT series it's not problem. Attach is one example for RT1020 EVK. Re: To complement solution how to printf float number in MCUXpresso IDE Thank you! That solved my problem.  Re: To complement solution how to printf float number in MCUXpresso IDE Hi @daweiyou  Thank you so much for your contribution. The information was pretty helpful and it might be helpful for many people. Thank you again. Best Regards. Pablo Avalos.
View full article
Display Touch input not mapped properly with primary display We are attempting to set up two displays and enable touch on the primary display for the i.MX 8 QuadMax MEK CPU Board using an LVDS to HDMI Adapter Card. We are using a USB Type-C connector (J17) for the touch input. Here are the observations we have made: The input is recognized but is not getting mapped when we connect the touch input to the primary display. However, when we connect it to the secondary display, the touch input works perfectly. As a workaround, we interchanged the display ports, i.e., primary to secondary and vice versa. The secondary screen then takes up the resolution of the primary screen, which is not ideal for our project. Following are the responses and logs received.     $ adb shell dumpsys SurfaceFlinger --display-id  Display 4632668096568543232 (HWC display 0): port=0 pnpId=RTK displayName="WaveShare"[15.6]  Display 4624778001127622657 (HWC display 1): port=1 pnpId=KTC displayName="WaveShare"[12.3]   [Touch input to primary display]  $ adb shell getevent -i | grep location    location: "imx-sc-pwrkey/input0"    adb shell getevent -i   add device 1: /dev/input/event0    bus:      0019    vendor    0000    product   0000    version   0000    name:     "sc-powerkey"    location: "imx-sc-pwrkey/input0"    id:       ""    version:  1.0.1    events:      KEY (0001): 0074     input props:        [Touch input to secondary display]  $adb shell getevent -i | grep location    location: "usb-xhci-hcd.1.auto-1/input0"    location: "imx-sc-pwrkey/input0"    adb shell getevent -i   add device 1: /dev/input/event1    bus:      0003    vendor    0712    product   000a    version   0111    name:     "HID 0712:000a"    location: "usb-xhci-hcd.1.auto-1/input0"    id:       ""    version:  1.0.1    events:      KEY (0001): 014a       ABS (0003): 0000  : value 0, min 0, max 1920, fuzz 0, flat 0, resolution 4                  0001  : value 0, min 0, max 720, fuzz 0, flat 0, resolution 2                  002f  : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0                  0035  : value 0, min 0, max 1920, fuzz 0, flat 0, resolution 4                  0036  : value 0, min 0, max 720, fuzz 0, flat 0, resolution 2                  0039  : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0      MSC (0004): 0005     input props:      INPUT_PROP_DIRECT  add device 2: /dev/input/event0    bus:      0019    vendor    0000    product   0000    version   0000    name:     "sc-powerkey"    location: "imx-sc-pwrkey/input0"    id:       ""    version:  1.0.1    events:      KEY (0001): 0074     input props:        Re: Display Touch input not mapped properly with primary display Hi, Could you please let me know which port on the board is connected to the touch input for the displays, and which port is being used for ADB access? Please reply as soon as possible. Thanks. Re: Display Touch input not mapped properly with primary display Hello @Zhiming_Liu , Thanks for the solution,got the touch mapping right. Just for someone with same blocker, 1)The 'input-port-associations.xml' is located under  /vendor/etc. 2)Check the input configuration of the display using the command $getevent -i | grep location. 3)Now change the configurations of the display mentioned under the xml file. Re: Display Touch input not mapped properly with primary display Hi @adithysm65  Have you tried to modify the input-port-associations.xml file in aosp? https://github.com/nxp-imx-android/android-imx_device_fsl/blob/android-13.0.0_2.2.0/imx8q/mek_8q/input-port-associations.xml
View full article
Sampling issue while streaming for Bayer sensor in iMX95 FRDM Hi Team, We are currently bringing up a Bayer sensor in IMX95 FRDM kit. We initially verified the stream with OS08A20 (reference camera from NXP) we were able to stream. Based on the driver we bringup a driver to support our sensor. It probes fine and media nodes gets generated properly. The media linking is proper which we verified with the media architecture of OS08A20.  We have attached the dmesg log below. Currently we configured the sensor in 8 bit mode (ar0234 sensor) . Current data rate is 800 MBPS per lane .  Data will be out in 4 lane for the sensor . We are able to probe and register. cam -l [0:08:06.049058684] [858]  INFO Camera camera_manager.cpp:340 libcamera v0.0.0+6489-lf-6.18.2-1.0.0 [0:08:06.155690529] [859]  INFO MediaPipeline media_pipeline.cpp:240 Found pipeline: [ar0830 3-0042|0] -> [0|csidev-4ad30000.csi|1] -> [0|4ac10000.syscon:formatter@20|1] -> [2|crossbar] [0:08:06.156726940] [859]  WARN CameraSensorProperties camera_sensor_properties.cpp:586 No static properties available for 'ar0830' [0:08:06.156904446] [859]  WARN CameraSensorProperties camera_sensor_properties.cpp:588 Please consider updating the camera sensor properties database [0:08:06.157054248] [859]  INFO Camera camera_manager.cpp:223 Adding camera '/base/soc/bus@42000000/i2c@42540000/ar0234_mipi@42' for pipeline handler imx8-isi Available cameras: 1: External camera 'ar0234' (/base/soc/bus@42000000/i2c@42540000/ar0234_mipi@42) our camera has been successfully detected , as mentioned above  v4l2-ctl -d 0 -v width=1920,height=1200,pixelformat='GRBG'  --stream-mmap  --verbose VIDIOC_QUERYCAP: ok VIDIOC_G_FMT: ok VIDIOC_S_FMT: ok Format Video Capture Multiplanar:   Width/Height      : 1920/1200   Pixel Format      : 'GRBG' (8-bit Bayer GRGR/BGBG)   Field             : None   Number of planes  : 1   Flags             :    Colorspace        : sRGB   Transfer Function : sRGB   YCbCr/HSV Encoding: ITU-R 601   Quantization      : Limited Range   Plane 0           :      Bytes per Line : 1920      Size Image     : 2304000     VIDIOC_REQBUFS returned 0 (Success)     VIDIOC_CREATE_BUFS returned 0 (Success)     VIDIOC_QUERYBUF returned 0 (Success)     VIDIOC_QUERYBUF returned 0 (Success)     VIDIOC_QUERYBUF returned 0 (Success)     VIDIOC_QUERYBUF returned 0 (Success)     VIDIOC_G_FMT returned 0 (Success)     VIDIOC_QBUF returned 0 (Success)     VIDIOC_QBUF returned 0 (Success)     VIDIOC_QBUF returned 0 (Success)     VIDIOC_QBUF returned 0 (Success)     VIDIOC_STREAMON returned 0 (Success)   We are able to get frames from the camera sensor which we probed with the DSO and verified but the platform is unable to sample it properly. No error comes in the dmesg. Have we missed anything else from the sensor configuration perspective? Also, do the data rate or pixel clock values need to be communicated to the platform through the Device Tree? Specifically, should the following D-PHY parameters be configured in the Device Tree?   cfg-clk-range = <28>; hs-clk-range = <0x2b>;   If these parameters are required, could you clarify on what basis the cfg-clk-range and hs-clk-range values are selected? Are these values derived from the MIPI CSI-2 lane data rate, sensor output resolution, frame rate, or pixel clock? Additionally, what data-rate or pixel-clock range corresponds to the values 28 and 0x2b? Is there a reference table or formula that should be used to determine the correct settings for a given sensor configuration? DMESG LOG [ 104.760033] camera-mipi-clk = 800MHz [ 115.837690] ar0234 3-0042: MIPI Clock = 800, MIPI Lanes = 4 [ 115.837737] ar0234 3-0042: supply avdd not found, using dummy regulator [ 115.837911] ar0234 3-0042: supply dovdd not found, using dummy regulator [ 115.837955] ar0234 3-0042: supply dvdd not found, using dummy regulator [ 115.988087] Current Firmware Version - (11eONO25V6XXX011106014eceGCORAL3) [ 115.988115] Current Firmware Version - (11eONO25V6XXX011106014eceGCORAL3) [ 115.989053] priv->mipi_lane_config is 4 [ 120.297214] SENSOR ID=0x0a56 [ 120.297245] mcu_isp_init [ 125.401238] Detected ar0234 sensor [ 125.453854] ar0234_propagate_fmt is called [ 125.463674] ar0234_propagate_fmt is called [ 125.463959] entering the enum mbus code [ 125.463975] code is 12290 [ 125.463982] entering the enum mbus code [ 125.463989] entering the ar0234_enum_frame_sizes functions [ 125.463995] entering the ar0234_enum_frame_sizes functions [ 125.463999] entering the ar0234_enum_frame_sizes functions [ 125.464004] entering the ar0234_enum_frame_sizes functions [ 125.464033] inside the ar0234_get_selection functions [ 125.464041] inside the ar0234_get_selection functions [ 125.464045] inside the ar0234_get_selection functions [ 126.637118] ar0234_propagate_fmt is called [ 126.637658] entering the enum mbus code [ 126.637681] code is 12290 [ 126.637702] entering the enum mbus code [ 126.637719] entering the ar0234_enum_frame_sizes functions [ 126.637736] entering the ar0234_enum_frame_sizes functions [ 126.637751] entering the ar0234_enum_frame_sizes functions [ 126.637765] entering the ar0234_enum_frame_sizes functions [ 126.637856] inside the ar0234_get_selection functions [ 126.637877] inside the ar0234_get_selection functions [ 126.637892] inside the ar0234_get_selection functions [ 204.157151] audit: type=1006 audit(1782310053.402:28): pid=805 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=4 res=1 [ 204.157191] audit: type=1300 audit(1782310053.402:28): arch=c00000b7 syscall=64 success=yes exit=1 a0=a a1=ffffc191b2d0 a2=1 a3=0 items=0 ppid=1 pid=805 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4 comm="sshd-session" exe="/usr/libexec/sshd-session" key=(null) [ 204.157211] audit: type=1327 audit(1782310053.402:28): proctitle=737368642D73657373696F6E3A20726F6F74205B707269765D [ 206.826792] ar0234_propagate_fmt is called [ 206.826975] entering the enum mbus code [ 206.826986] code is 12290 [ 206.826994] entering the enum mbus code [ 206.827000] entering the ar0234_enum_frame_sizes functions [ 206.827006] entering the ar0234_enum_frame_sizes functions [ 206.827010] entering the ar0234_enum_frame_sizes functions [ 206.827014] entering the ar0234_enum_frame_sizes functions [ 206.827057] inside the ar0234_get_selection functions [ 206.827065] inside the ar0234_get_selection functions [ 206.827070] inside the ar0234_get_selection functions [ 224.637904] ar0234_propagate_fmt is called [ 224.676405] ar0234_propagate_fmt is called [ 224.676442] entering ar0234_set_fmt [ 224.676447] inside the set format loop if condition [ 224.676451] ar0234->mcu_cam_frmfmt[mode].size.width is 1920 [ 224.676456] ar0234_set_fmt: setting resolution width=1920 height=1200, mode=0 [ 224.680462] priv->mcu_cam_frmfmt[mode].size.width is 1920 [ 224.680476] mc_data[8] = 0x07 (7) [ 224.680480] mc_data[9] = 0x80 (128) [ 224.680484] mc_data[10] = 0x04 (4) [ 224.680487] mc_data[11] = 0xb0 (176) [ 228.270636] ar0234_propagate_fmt is called [ 228.270815] entering the enum mbus code [ 228.270823] code is 12290 [ 228.270832] entering the enum mbus code [ 228.270838] entering the ar0234_enum_frame_sizes functions [ 228.270843] entering the ar0234_enum_frame_sizes functions [ 228.270848] entering the ar0234_enum_frame_sizes functions [ 228.270912] entering the ar0234_enum_frame_sizes functions [ 228.270958] inside the ar0234_get_selection functions [ 228.270965] inside the ar0234_get_selection functions [ 228.270970] inside the ar0234_get_selection functions [ 237.329660] dwc-mipi-csi2 4ad30000.csi: Remote sub-device on pad 1 should implement .get_frame_desc! Forcing VC = 0 and DT = 2a [ 487.004807] ar0234_propagate_fmt is called [ 487.004984] entering the enum mbus code [ 487.005053] code is 12290 [ 487.005065] entering the enum mbus code [ 487.005073] entering the ar0234_enum_frame_sizes functions [ 487.005079] entering the ar0234_enum_frame_sizes functions [ 487.005083] entering the ar0234_enum_frame_sizes functions [ 487.005087] entering the ar0234_enum_frame_sizes functions [ 487.005138] inside the ar0234_get_selection functions [ 487.005146] inside the ar0234_get_selection functions [ 487.005150] inside the ar0234_get_selection functions [ 695.743591] audit: type=1006 audit(1782310544.949:29): pid=869 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=5 res=1 [ 695.743649] audit: type=1300 audit(1782310544.949:29): arch=c00000b7 syscall=64 success=yes exit=1 a0=a a1=ffffef74ca20 a2=1 a3=0 items=0 ppid=1 pid=869 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=5 comm="sshd-session" exe="/usr/libexec/sshd-session" key=(null) [ 695.743685] audit: type=1327 audit(1782310544.949:29): proctitle=737368642D73657373696F6E3A20726F6F74205B707269765D
View full article
NXP Config Tools 26.06 for i.MX not loading saved configuration Hello, While evaluating the new version of the DDR configuration for the i.MX95, I came across what looks like a bug in the configuration tool. Here is exactly what I did, so the behavior can be reproduced: 1. Installed the Linux version of the tool. 2. Created a new configuration. 3. Selected processor MIMX9596xxxxN. 4. Changed the preset to "LPDDR4X EVK / FRDM 15x15 4000MTs Configuration". 5. Saved the configuration, then closed the tool. 6. Reopened the tool and loaded the saved configuration. At that point the DDR configuration is not displayed at all. At least the 26.03 version was starting with MCU unselected (selecting it manually solves the problem), now there is no way to solve the problem. Thank you very much for your help. Best regards, Emanuele Re: NXP Config Tools 26.06 for i.MX not loading saved configuration Also the windows version of the tool shows the same problem. Attached screenshots. Re: NXP Config Tools 26.06 for i.MX not loading saved configuration Hello, Thank you for report this bug in the tool. I was able to see the issue on my side. I will report it with internal team to solve it as soon as possible. Best regards. Re: NXP Config Tools 26.06 for i.MX not loading saved configuration Is there an update or a workaround? It is impossible to use it Re: NXP Config Tools 26.06 for i.MX not loading saved configuration I've just installed and tested version 26.09. Followed the same steps that Emanuele listed but for MIMX9529xxxxx. The incorrect behavior is the same, impossible to load previously created config files. Tested on Ubuntu 24.04. Best regards,
View full article
RAM retention not working across functional reset (S32K3xx) Hi Team, We are trying to retain a variable across functional reset on S32K3xx, but it is not working. Implementation: Variable placed in custom RAM section: __attribute__((section(".int_sram_results"))) uint32_t retain_var;               The value is being updated before reset (for testing retain_var= 0x11223344) . Reset type: Functional reset (software-triggered) Observed behaviour: But value is always 0 (cleared) RAM retention is not happening Reference checked: Already referred this discussion and tried the suggested approach: https://community.nxp.com/t5/S32K/S32K311-noinit-ram/td-p/2123035 The example provided there did not work in our case Request: Please share a working example or minimal snippet for retaining RAM across functional reset on S32K3xx Thanks, Yusup S32K3 S32DS-ARM S32K31XEVB-Q100  Re: RAM retention not working across functional reset (S32K3xx) Hi @yusupkhan241, The startup code most likely initializes the entire SRAM to zero (for ECC initialization) after every reset—I haven’t seen your specific startup code. You could consider skipping the ECC initialization when the reset is functional. Refer to this answer: https://community.nxp.com/t5/S32K/SRAM-ECC-Initialization-for-S32K344/m-p/1764143 BR, Daniel Re: RAM retention not working across functional reset (S32K3xx) Hi @yusupkhan241, What do you mean by “it does not work”? The files you posted do not seem to reflect the latest changes. Can you step through the startup code and observe the variable in SRAM after a functional reset? This should clearly show where the variable gets overwritten. To attach the debugger after the functional reset, you can add a simple loop at the beginning of the startup code, for example: Loop: mov r0, #1 cmp r0, 0 /* Change r0 to 0 in register view */ bne Loop /* Capture after power-on reset */ Regards, Daniel Any support, information, and technology (“Materials”) provided by NXP are provided AS IS, without any warranty express or implied, and NXP disclaims all direct and indirect liability and damages in connection with the Material to the maximum extent permitted by the applicable law. NXP accepts no liability for any assistance with applications or product design. Materials may only be used in connection with NXP products. Any feedback provided to NXP regarding the Materials may be used by NXP without restriction. Re: RAM retention not working across functional reset (S32K3xx) Hi @danielmartynek I have simplified the setup to isolate the RAM retention behavior. I placed the variable in a dedicated SRAM section and used a minimal main function with LED indication and watchdog-triggered reset. The idea is: Green LED → value retained after reset Red LED → value lost Below is the test code being used: C __attribute__((section(".int_sram_results"), used)) volatile uint32_t retain_var; int main(void) { Clock_Ip_Init(&Clock_Ip_aClockConfig[0]); DIO_Init(); WDT_Init(); if (retain_var == 0xAABBCCDD) { Siul2_Dio_Ip_SetPins(LED_GREEN_PORT, (1UL << LED_GREEN_PIN)); Siul2_Dio_Ip_ClearPins(LED_RED_PORT, (1UL << LED_RED_PIN)); } else { Siul2_Dio_Ip_SetPins(LED_RED_PORT, (1UL << LED_RED_PIN)); Siul2_Dio_Ip_ClearPins(LED_GREEN_PORT, (1UL << LED_GREEN_PIN)); } retain_var = 0xAABBCCDD; while (1) { /* watchdog reset */ } } Show less Observation: When running with debugger, the behavior is as expected. However, after power-on reset, there is no LED indication, which suggests the code may not be executing as expected. I have attached the latest linker and startup files for reference. Please let me know if you see anything missing on the startup or reset handling side. S32DS-ARM S32K31XEVB-Q100  Thanks, Yusup Re: RAM retention not working across functional reset (S32K3xx) Hi @danielmartynek I replaced the startup instructions below with the changes you shared, but it did not work. For your reference, I have uploaded the relevant files. The .s and .ld files were uploaded with a .c extension. Please review them and let me know if you need any additional information. RamInit: /* Initialize SRAM ECC */ ldr r0, =__RAM_INIT cmp r0, 0 /* Skip if __RAM_INIT is not set */ beq SRAM_LOOP_END ldr r0, =MCRGM_DES ldr r1, [r0] ldr r2, =MCRGM_DES_F_POR and r1, r1, r2 cmp r1, 0 beq NO_INIT_STANDBY_REGION ldr r2, =__INT_SRAM_START ldr r3, =__INT_SRAM_END b ZERO_64B_RAM The above instructions updated with  RamInit: /* Check MC_RGM DES register, if it's non-zero, jump to RAMInit_Start. (RAM init is needed if Destructive reset occurred) */ /* To make it work, customer should clear the MC_RGM DES register in application code. */ ldr r4, =MC_RGM_BASE_ADDR /* 0x4028C000 */ ldr r4, [r4, #0x0] cmp r4, #0x0 bne RamInit_Start /* Check MC_RGM FES register, if the F_EXR bit or ST_DONE bit is set, jump to RAMInit_Start. */ /* RAM init is needed if external reset occurred, or BIST Done functional reset occurred. */ /* To make it work, customer should clear the MC_RGM FES F_EXR register bit in application code. */ ldr r4, =MC_RGM_BASE_ADDR ldr r4, [r4, #0x8] ldr r5, =MC_RGM_FES_MASK_RAM_INIT and r4, r4, r5 cmp r4, #0x0 bne RamInit_Start b SRAM_LOOP_END RamInit_Start: /* Initialize SRAM ECC */ ldr r0, =__RAM_INIT cmp r0, 0 /* Skip if __SRAM_INIT is not set */ beq SRAM_LOOP_END ldr r1, =__INT_SRAM_START ldr r2, =__INT_SRAM_END Thanks, Yusup Re: RAM retention not working across functional reset (S32K3xx) Can you share the whole test project so that I can easily test it on my side? Thank you, Daniel Re: RAM retention not working across functional reset (S32K3xx) Hi @danielmartynek Below are the observations from our testing:  Debug mode behaviour: Power-on reset (RED LED): retain_var = 0x5AA55AA5 @ 0x20407B00 After watchdog reset (GREEN LED): retain_var = 0xAABBCCDD @ 0x20407B00 This confirms that RAM retention across functional reset is working when running under debugger. However, when running standalone (without debugger): After power-on reset, there is no LED indication. It appears that the program is not executing or not reaching the application code. Could you please help identify what might be causing this behaviour? Also, we are planning to use the complete .int_sram_results section to retain multiple parameters across functional reset. Please suggest if any additional changes are required for reliable retention. Additionally, could you please suggest if there is any API or recommended method to trigger a functional reset (alternative to watchdog)? For reference, I have included the changes made in the startup and linker files, and the same can be verified in the shared project. startup file (old code) RamInit:     /* Initialize SRAM ECC */     ldr  r0, =__RAM_INIT     cmp  r0, 0     /* Skip if __RAM_INIT is not set */     beq SRAM_LOOP_END     ldr r0, =MCRGM_DES     ldr r1, [r0]     ldr r2, =MCRGM_DES_F_POR     and r1, r1, r2     cmp r1, 0     beq NO_INIT_STANDBY_REGION     ldr r2, =__INT_SRAM_START     ldr r3, =__INT_SRAM_END     b   ZERO_64B_RAM startup file (new code) .equ MC_RGM_BASE_ADDR, 0x4028C000 .equ MC_RGM_FES_MASK_RAM_INIT, 0xFFFFFFFF RamInit:                /* Check MC_RGM DES register, if it's non-zero, jump to RAMInit_Start. (RAM init is needed if Destructive reset occurred) */                /* To make it work, customer should clear the MC_RGM DES register in application code. */                ldr r4, =MC_RGM_BASE_ADDR   /* 0x4028C000 */                ldr r4, [r4, #0x0]                cmp r4, #0x0                bne RamInit_Start                /* Check MC_RGM FES register, if the F_EXR bit or ST_DONE bit is set, jump to RAMInit_Start. */                /* RAM init is needed if external reset occurred, or BIST Done functional reset occurred. */                /* To make it work, customer should clear the MC_RGM FES F_EXR register bit in application code. */                ldr r4, =MC_RGM_BASE_ADDR                ldr r4, [r4, #0x8]                ldr r5, =MC_RGM_FES_MASK_RAM_INIT                and r4, r4, r5                cmp r4, #0x0                bne RamInit_Start                b SRAM_LOOP_END                RamInit_Start:                /* Initialize SRAM ECC */                ldr r0, =__RAM_INIT                cmp r0, 0                /* Skip if __SRAM_INIT is not set */                beq SRAM_LOOP_END                ldr r1, =__INT_SRAM_START                ldr r2, =__INT_SRAM_END     b   ZERO_64B_RAM linker file changes old code:     .int_results (NOLOAD):     {         . = ALIGN(4);         KEEP(*(.int_results))         . += 0x100;     } > int_sram_results new code:                    .int_results (NOLOAD):     {         . = ALIGN(4);         KEEP(*(.int_results))     } > int_sram_results    S32K31XEVB-Q100  Thanks, Yusup Re: RAM retention not working across functional reset (S32K3xx) Hi @yusupkhan241, I have debugged it found that the code below was incorrect. It used R1 and R2 instead of R2 and R3: We need R2 and R3 because of this: Where did you get this startup code? With the debugger connected, the debugger initializes the SRAM ECC. Without the debugger, there was a Hardfault at 0x20400090. Regards, Daniel Re: RAM retention not working across functional reset (S32K3xx) Hi @danielmartynek  After fixing to use R2/R3, the application is running. However, RED LED always blinks and GREEN never turns ON, indicating the value is not retained after reset. I’ve applied the startup changes from your shared link, but retention is still not working as expected. S32K3 S32DS-ARM  https://community.nxp.com/t5/S32K/SRAM-ECC-Initialization-for-S32K344/m-p/1764143 Thanks, Yusup Re: RAM retention not working across functional reset (S32K3xx) @danielmartynek  Any update on this? S32DS-ARM S32K31XEVB-Q100  Thanks, Yusup. Re: RAM retention not working across functional reset (S32K3xx) Hi @yusupkhan241, Sorry for the delay; I wasn't able to get to the testing until now. I have now tested it and used the simple code below to skip the SRAM initialization when only a Functional Event Status (FES) reset occurred and no Destructive Event Status (DES) reset was detected. /* * Initialize SRAM ECC only after a Destructive Reset. * * Functional reset shall preserve SRAM content, so MC_RGM_FES is not used * here to trigger SRAM initialization. * * Note: * To make this check work correctly, the application should clear MC_RGM_DES * after processing the destructive reset reason. */ /* Check MC_RGM DES register. * If DES is non-zero, a destructive reset occurred and SRAM init is needed. */ ldr r4, =MC_RGM_BASE_ADDR /* 0x4028C000 */ ldr r4, [r4, #0x0] /* MC_RGM_DES */ cmp r4, #0x0 bne RamInit_Start /* No destructive reset detected. * Skip SRAM ECC initialization to preserve SRAM content across Functional Reset. */ b SRAM_LOOP_END In main(), clear the DES register: IP_MC_RGM->DES = 0xFFFFFFFF; BR, Daniel
View full article
RT1160 with external SDRAM and SRAM with wait pin I am using the RT1160 with external 16-bit SDRAM and 16-bit SRAM(for fpga communication).  The SRAM interface is configure as SRAM Read/Write Operation in ASYNC Mode with Wait Pin. I wonder If the wait signal will conflic with SDRAM refresh timing to cause some issue. We've test  it to let our code in SDRAM and let wait pin keep low about 10ms or longer in SRAM ASYNC write,  sometimes it will end at about just 1ms and don'tknow why.   can we use in that way or ther have some limitation when using both SDRAM and SRAM device. Thanks for your help. Re: RT1160 with external SDRAM and SRAM with wait pin Hi  What are you referring to when you mention that it will end at about 1 ms? Does the SRAM write return an error, or does it enter a hard fault? How often does this happen? Could you please help me test the following? 1. Run the code from internal memory (not SDRAM) and repeat the long asynchronous SRAM write. 2. While still executing the code from internal memory, run the same test again, but this time with SDRAM enabled but idle. 3. Run the test as you originally mentioned, but with the SRAM wait signal held active. Additionally, could you check the following during these tests (including the ones mentioned above) Could you monitor the SRAM signals during the transfer? Could you share the SEMC INTR register values for each test? Please let me know your results. Best Regards, Pablo
View full article