LPCScrypt not running on Windows 11 25H2 [LPCScrypt version 2.1.3_83] For booting and flashing an old LPC1857 we use LPCScrypt for updating device firmware. Since Windows 11 25H2 LPCScrypt is broken: calling it on the command line (ie PowerShell) leads to "Error: Error from CreateProcess: The system cannot find the file specified" Sysinternal's Process Monitor leads to the assumption that LPCScrypt is performing a wmi query by using "wmic path Win32_PnPEntity where (service like '%usbser%' and name like '%lpc%') get.exe". But wmic is declared deprecated since 2016 and had been removed from Windows 11 since 25H2 (see Windows Management Instrumentation Command-line (WMIC) removal from Windows - Microsoft Support) Request to NXP dev team: Is this issue known yet? How to get it to work in the future? Re: LPCScrypt not running on Windows 11 25H2 Hi ErichStyger, you are right. By upgrading from Windows 10 wmic is kept in Windows 11. But I had to setup a fresh Windows 11 system and came accross that issue. Re: LPCScrypt not running on Windows 11 25H2 Thank you for the information. My workaround was to add wmic support to Windows 11 as follows open system settings as an administrator, go to optional features (...further features...) and add wmic  or by using "DISM /Online /Add-Capability /CapabilityName:WMIC" [see Install WMIC to a Windows 11 computer - Microsoft Q&A] Regards, Mathias Re: LPCScrypt not running on Windows 11 25H2 Probably because I have upgraded from Win10 to Win11, I still have WMIC on my machine: Re: LPCScrypt not running on Windows 11 25H2 I recently upgraded from Win10 to Win11 25H2. But so far, I have not seen an issue with LPCScrypt (yet). Using the one packaged with LinkServer v25.9.134 (see below) Updating my LPC-Link2 with LPCScrypt worked fine. Not an expert on WMIC, but according to the information it is gone in 25H2, chatGTP suggested to copy wmic.exe and wmic.exe.mui from an older Windows version to 25H2. NXP is aware of the issue, and there might be an updated LPCScrypt in a next LinkServer release. Re: LPCScrypt not running on Windows 11 25H2 Hello @mathiasmonse  Thanks for your question. If WMIC support is removed, yes, you can try to install it. Or  use an earlier Windows version or to run LPCScrypt on Linux or macOS. BR Alice

PNEV7642A and LPC541xx device I2C connection Hello, I’m trying to establish an I2C connection between the evaluation board PNEV7642A and a system based on LPC541xx devices. Pin connections: J46.1 → AD_I2CM_SCL J46.2 → AD_I2CM_SDA J46.4 → GND (Connected to the corresponding I2C pins on the LPC541xx board.) The issue I’m facing is that the I2C bus seems to get stuck — either the data is not received correctly or not received at all. Additionally, when the I2C bus from the PN7642 evaluation board is connected, it appears to pull down the communication of other I2C devices on the same bus. Could this be related to a clock issue (e.g., clock stretching, desynchronization, or incorrect clock/frequency settings)? Initially, I used the clock driver and clock_config files provided in the PNEV7642FAMA software package. Would you recommend using MCUXpresso Config Tools (https://mcuxpresso.nxp.com/) to generate the pin mux and clock configuration? If so, is there any special procedure or configuration required for this setup? Thank you for your help. Re: PNEV7642A and LPC541xx device I2C connection Hi, According to PN7642 Data Sheet, Section 9.6.1.7, I2C Controller interface supports both multi controller and multi controller with target. Latest SDK available (should be v02.15.004) can be found in PN7642 Product Page, under Software section. Available examples for I2C communication are pn76_hostif_i2c (driver_examples > hostif > i2c) and i2c_gpdma_b2b_transfer_master/_slave (driver_examples > i2c). Also, I will recommend you referring to the I2C-bus specification and user manual. Regards, Eduardo. Re: PNEV7642A and LPC541xx device I2C connection Hello Eduardo, I am now getting closer to understanding the root cause. What I actually need is multi-controller (multi-master) I2C communication with DMA. I have already started modifying the I2C driver to handle: • Arbitration lost events • Retry logic • Bus ready checks However, before continuing further development, I would like to confirm: Does the PN7642 support multi-controller I2C operation? If yes, are there: • Any existing SDK examples? • Updated drivers? • Application notes or guidance from NXP? If such resources are available, could you please share them? Thank you in advance for your support. Best regards, Radoslaw Tomasik Re: PNEV7642A and LPC541xx device I2C connection Hi, Please, try using the default source code of the demo (from latest SDK version of each device). I tried to replicate your setup by using: - LPCXpresso54114 Evaluation board -> lpcxpresso54114_i2c_dma_b2b_transfer_master, no modifications - OM27642EVK Evaluation board -> pnev7642fama_i2c_gpdma_b2b_transfer_slave, no modifications Then, connected: PNEV7642A LPCXpresso54114 J46-1 J1-1 J46-2 J1-3 J46-4 J1-7 The communication works as expected: - LPCXpresso54114   - PNEV7642A Regards, Eduardo. Re: PNEV7642A and LPC541xx device I2C connection Hello @EduardoZamora, Did you have a chance to look into the issue? I’ve attached two files showing one I2C message that is sent cyclically. I can see the signal on the oscilloscope connected to the evaluation board pins; however, it does not appear in the receive buffer of the I2C slave software. What could be the reason for this behavior? Please advise. Best regards, Radoslaw   Re: PNEV7642A and LPC541xx device I2C connection Hello @EduardoZamora, Thanks, I’m doing fine — hope you’re doing well too! 🙂 I’m using the i2c_gpdma_b2b_transfer_slave example (from PN7642 SDK > driver_examples > i2c) as a reference for my tests. My goal is to receive data and send a modified response back. I modified the address setting to: slaveConfig.address0.address = 0x00; so that the device can receive all data on the bus. On the oscilloscope, I can see traffic on the bus reaching pins J46.1 and J46.2. Are these pins the correct outputs for I2C communication, or should I use different pins if I only want to receive data? Regarding J54, my current jumper configuration is as delivered (all four jumpers in place): J54 pins 1–3 & 2–4: PN76xx I2CM as leader — default J54 pins 3–5 & 4–6: PN76xx I2CM as follower — optional J54 pins 5–7 & 6–8: PN76xx I2CA (ATX) as follower — default I’ve attached an example of the I2C communication for reference. I hope this helps clarify the situation a bit more. Thank you in advance for your support. Best regards, Radoslaw Re: PNEV7642A and LPC541xx device I2C connection Hello @RadoslawTomasik Hope you are doing well. Could you please confirm if you are using i2c_gpdma_b2b_transfer_master (PN7642 SDK > driver_examples > i2c) demo as a reference for your test? By any chance, have you modified the original source code? What are the pins you are using on the LPC541xx? Can you provide a capture of the I2C communication by using an oscilloscope or logic analyzer? i2c_gpdma_b2b_transfer_master uses a baud rate of 100K. After connecting to LPC55s16 with slave configuration, using pins J46-1 / J46-2 / J46-4, this should be the output: - PN7642 -LPC55s16 Regards, Eduardo.

S32DS 3.6.4 can't found RTD Hello! Recently, I installed S32DS 3.6.4 & RTD 6.0.0. However, when I attempt to create a new app project, I am unable to select RTD. How can I fix it? Re: S32DS 3.6.4 can't found RTD Thank you for your interest in our products and for contributing to our community. According to RTD 6.0.0 Release Notes: So when you create a new project, please make sure you select NXP GCC 10.2.0 in the following step: I hope this information is helpful.

The project cannot be exported as IAR EW I followed the instructions in "HOWTO: Export S32DS Project to IAR EW (S32K14x/S32K11x)", but I couldn't find the "Project Info Export Wizard" option in "Export". Re: The project cannot be exported as IAR EW Hi,  this feature was present in older S32DS with processor expert. I'm not familiar with IAR Workbench, but I assume that you can import project into WB IDE as a ProjectInfo.xml 

Quadrature Encoder Velocity Measurement Hi, I am trying to figure out how to use a timer to improve low speed quadrature encoder measurements on i.MX RT1060. I can see in the reference manual (55.4.2 Prescaler for Slow or Fast Speed Measurement) that there should be some support for low speed measurements using a timer. However, I am having a hard time understanding how I can set this up? Are the some examples since this was posted? If not could you provide a brief explanation of what I need to do? Does the ENC have its own timer or should I setup a separate timer?  What are the steps for setting up such a timer? Thanks! Best regards, Tor i.MXRT 106x Re: Quadrature Encoder Velocity Measurement Hi @Kan_Li , Thank you I have made a support case with the same title as this one. Best regards, Tor Re: Quadrature Encoder Velocity Measurement Hello @RegulaTor , Yes, we have such kind of demo but it is just internal used, would you please raise a private case for it? Please kindly refer to https://www.nxp.com/video/tutorial-for-nxp-support-case-portal:NCP-VIDEO for details. 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. -------------------------------------------------------------------------------

RT1176 custom board no access to LPUART1 or JTAG/SWD ... I have a custom board, that is very close to the EVKB board, except no USB or MIPI. I cannot seem to access serial downloader mode to use the Secure Provisioning Tool via UART, nor obtain any access via JTAG/SWD for programming. The chip seems to be working, on that there is an ON/OFF button that when held for 5 seconds, or whatever the length is, powers the chip off, and then pressing the button again powers it on. I've double-triple checked everything, and it nearly matches the EVKB board, however one things I noticed that was not done was to connect VDD_MIPI_* or VDD_USB_* to anything, again, as the board doesn't use MIPI or USB. Could not connecting those power pins be causing the problems I'm having with accessing UART or JTAG/SWD? Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... The image I posted is from that red circled area, and I am using the exact components, values as detailed in the EVKB there. Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... Hi @application_ninja , In MIMXRT1170-EVKB board  , RC delay time is 30000*0.00000022=0.0066s  =6.6ms. Please check your board, if your board use the same RC delay circuit, Please use an oscilloscope to measure the signal circled in red in the image. Best Regards Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... As an FYI, this is what my delay circuit looks like...  Blue being DCDC_IN and yellow being DCDC_PSWITCH. Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... Not sure what you mean by: "VDD_SNVS_DIG is internal LDO output.", so is 0v output correct for this, or not? My custom board is nearly identical to the EVKB except for not using MIPI/USB/AUDIO. I've gone over things many times, just cannot figure out why I cannot get it into serial downloader mode nor use JTAG/SWD to program it. Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... Hi @application_ninja , VDD_SNVS_DIG is  internal LDO output. 1: I suggest you can compare your customed board with MIMXRT1170-EVKB board, check the difference. 2: If you have MIMXRT1170-EVKB board, did you try modify the MIMXRT1170-EVKB board same as your customed board? Best Regards Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... Apparently VDD_SNVS_DIG is low, and controlled by software, so my design is correct? https://www.nxp.com/docs/en/data-sheet/IMXRT1170BCEC.pdf "The power rail VDD_SNVS_DIG is controlled by software." Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... OK, so it's looking like I'm not getting anything on VDD_SNVS_DIG, not sure why, but any thoughts as to what could cause this off hand? Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... That was going to be my next steps, however quite difficult to test / probe, thus my first questions to see if not connecting those VDD_MIPI_* and VDD_USB_* could be the cause, since everything else seems to power up correctly and I get correct voltages everywhere. Thank you. Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... Hi @application_ninja , Could you use an oscilloscope to check if the power-up sequence is normal, especially the RC delay circuit?  Best Regards MayLiu Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... Yes, thank you, I have verified all that, I have a positive voltage on BOOT_CFG_0, and have positive voltage on the RXD LPUART1 pin coming from the chip, so everything appears as though it should be working, but I get nothing from the secure provisioning tool, nor from the sdphost tool. All my power rails look good, proper voltages, my ONOFF button works, reset button, just really stumped as to why I cannot program / read the chip. Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... Hi @application_ninja , Thanks for your updated information. First, I suggest you follow the HDUG recommended design for your customed hardware development board. Second, please check the Boot Mode pins settings of your custom development board. If you want use the Secure Provisioning Tool via UART, you need set as serial downloader mode. Third,  Only LPUART1 support serial downloader mode. Wish it helps you. Best Regards MayLiu Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... Yes, I am aware of that document, but that does not answer my question, and as you have confirmed what the document states, those are "recommendations", they are not listed as "requirements" for proper board operation. So going by the way you have stated and the documentation reads, as "recommended" they do not have to be performed for proper board  / chip operation. Which leads back to my question, could not doing these "recommendations" cause the problems I am seeing? Re: RT1176 custom board no access to LPUART1 or JTAG/SWD ... Hi @application_ninja , Thank you so much for your interest in our products and for using our community. In MIMXRT1170HDUG, it describe that Unused pins recommendation  https://www.nxp.com/webapp/Download?colCode=MIMXRT1170HDUG Please follow the  Recommended connections for unused analog interfaces. Wish it helps you. If you still have question about it, please kindly let me know.  Best Regards MayLiu

Reallocation FlexRAM Hi I'm trying to reallocate the FlexRam to be DTC = 128KB, ITC = 64KB, OC = 64KB on i.mxrt 1024 I did these changes    I also modified the linker file to fit with these changes. Now it works, but my question is about these two lines "LDR R0, =0x20001fff\n" // load initial value of stack pointer into R0 "MSR MSP, R0\n" // Reinitialize stack pointer by new value Why without these lines it doesn’t work even if I modified the linker so _vStackTop must be up to date! i.MXRT 102x Re: Reallocation FlexRAM Please refer to this post for more details on why SP is reset: RT1176 ROM code does not set stack pointer correctly - NXP Community BR, Omar Re: Reallocation FlexRAM Thank you for your response, It worked but when i try to set DTCram = 192KB, OCram = 64KB and ITCram = 0KB, i cant find the define ARM_MPU_REGION_SIZE_192KB ! Thank you.

FS23 SBC AUTOSAR R21-11 版本 0.9.0 按照发行说明中提到的所有步骤，我在 DS3.5 环境中安装了 FS23 SBC AUTOSAR R21-11 版本 0.9.0。 但是，该代码包未显示在 SDK 中。 以下是我的设置详情： 目标板：S32K311 RTD 版本：3.0 FS23 SBC AUTOSAR R21-11 版本：0.9.0 开发工作室版本：DS3.5 我已经验证了安装路径并按照版本说明中的所有说明进行了操作，但是 SDK 仍然没有列出 FS23 SBC 元器件。 您能否提出任何解决方案或更新，使其在 SDK 中可见？ Re: FS23 SBC AUTOSAR R21-11 Version 0.9.0 嗨，@raghunandanreddy、 FS23 的 IP 元器件在 0.9.0 代码包中不可用，建议改用 FS23 1.0.0 + RTD 4.0.0。 在 1.0.0 代码包中，IP 和 MCAL 元器件以及示例例程都可用： 还存在一个错误， 即在更新站点生成过程 中，FS23 代码包会覆盖 FS26，该错误后来在版本 s32k3xx_sbc_fs 23_r21-11_1.0.0_ds_updatesite_d2402_updated_d250115.zip 上得到修复 。 致以最诚挚的问候， Julián

CA X509証明書の署名のRSA検証による真正性の確認 こんにちは@lukaszadrapaさん、 私は CA 自己署名証明書を作成しました。これを使用して、公開キーによって証明書の署名を検証する必要があるアプリケーションを構築する必要があります。 これは私のアプリケーション コードですが、検証失敗のエラー コードが表示されています。 int main(void) { /* ========================================================== * 1. 環境とハードウェアセキュリティモジュールを初期化する * ============================================================ */ 終了するまで待機します();   /*NVMカタログ内のECCキーペアのキーハンドル*/ hseKeyHandle_t g2b_keyPairHandler = GET_KEY_HANDLE(HSE_KEY_CATALOG_ID_NVM, 0, 0); /* RAMカタログ内の公開鍵のキーハンドル*/ hseKeyHandle_t g2b_keyPubHandler = GET_KEY_HANDLE(HSE_KEY_CATALOG_ID_RAM, 0, 0);   /*キーカタログをフォーマットします */ g2b_HSE_Status = フォーマットキーカタログ(g2b_nvmKeyCatalog_rsa, g2b_ramKeyCatalog_rsa);   /*フレームワーク内のキーを処理するためのキーアロケータドライバを初期化します*/ g2b_HSE_Status = HKF_Init(g2b_nvmKeyCatalog_rsa、g2b_ramKeyCatalog_rsa);   /* ========================================================== * 2. CA証明書（PEM形式）をロードする * ============================================================ */ 静的定数char *ca_pem = "-----証明書開始-----\r\n" "MIIDhDCCAmygAwIBAgIINYKWbrYzIuEwDQYJKoZIhvcNAQELBQAwSDELMAkGA1UE\r\n" "BhMCSU4xJzAlBgNVBAoTHkdldHRvYnl0ZSBUZWNobm9sb2dpZXMgUHZ0IEx0ZDEQ\r\n" 「MA4GA1UEAwwHUm9vdF9DQTAeFw0yNTEwMjgxMTQ0MDBaFw0zNTEwMjgxMTQ0MDBa\r\n」 「MEgxCzAJBgNVBAYTAklOMScwJQYDVQQKEx5HZXR0b2J5dGUgVGVjaG5vbG9naWVz\r\n」 「IFB2dCBMdGQxEDAOBgNVBAMMB1Jvb3RfQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IB\r\n」 "DwAwggEKAoIBAQC5+qqEb+wIDQTG7mgAAgXdH9eM1PjuR34e4qDZDTW7aRukWt0I\r\n" "Whwef6NbfXV51N/CI+4+446sND4jW8Y4tK8h7i+QJBaTx3sdDyBO3JNthpp/uUtt\r\n" "+2EUGJP8tKNiP1GhhAjjCMmHwrY3kqyAzXKiCdRFGnWOdQvae6QfgTogDGoXwfEj\r\n" "IGRfOAXZYOLo/+PTm7AZvF+eWSGnXV3mnvP0FimE/NhBdJwL3T8AoxaMW+jNWRTf\r\n" "XV5NAZili62U7Va/BdGSw3Vrbf70O3S7nbnQWmHJTKrZT8CjUft2fVXpsNWJ+lAp\r\n" "cWqRrOtY5Ux5sO2ke5l52vXVrWckwSHESCCjAgMBAAGjcjBwMA8GA1UdEweb/wQF\r\n" "MAMBAf8wHQYDVR0OBBYEFOaB3KdlqOw1UgifcfwjaAQmyoHjMAsGA1UdDwQEAwIB\r\n" "BjARBglghkgBhvhCAQEEBAMCAcwHgYJYIZIAYb4QgENBBEWD3hjYSBjZXJ0aWZp\r\n" "Y2F0ZTANBgkqhkiG9w0BAQsFAAOCAQEAtkNO6oP39gHMzH6Zz53dOs6zqJbrZFab\r\n" 「w1ekLN30hwAbC9v32zp9Elq1zFnZRQAeILOYTpeR2ejD2PgpZATeYhH9w93OgDgx\r\n」 "/CWtDQAcYN/kOvIzAaFGBY3+QoRsOTzggLNNehhO4ZhevBjRS6QWsJDY1RaAp8ss\r\n" "9QWJnuYtkfUAtfqDD3jGC3VsE9h5dBQn4JG0REeC7go6S7D+ofzzgBDbK/gwdFcr\r\n" 「YnS4e9Mse0D1RQjFEaEKibB0hX7L3uEAzVIDCS2lD/0jzwCLxQ1xhFooVzv5Tb4k\r\n」 「nRr+v8ht/baCu3vtZEeGxM8/IeP3ttjavdNnb/IiCS2nVgj/YfzNDw==\r\n」 "-----証明書終了-----\r\n"; pem_cert_to_der(ca_pem, &ca_der, &ca_der_len);   /* ========================================================== * 3. CA証明書を解析して重要なフィールドを抽出する * ============================================================ */   int rc = simple_x509_parse_der(ca_der, ca_der_len, &c); (rc) の場合 { /* これが失敗した場合、証明書は不正な形式であるかサポートされていません。*/ }   /* ========================================================== * 4. 検証のために重要なASN.1スライスを見つける * ============================================================ */   if (simple_x509_locate_core(ca_der, ca_der_len, &tbs, &tbs_len, &sig_oid, &sig_oid_len, &sig, &sig_len) != SX_OK) { printf("コアの検索に失敗しました\n"); -1 を返します。 }   /* ========================================================== * 5. CA自身の公開鍵を抽出する（SPKIビット -> N、E） * ============================================================ */   simple_x509_locate_spki_bits(ca_der, ca_der_len, &spki_bits, &spki_len); rsa_pub_init(&ca_pub);   /* ========================================================== * 6. 署名アルゴリズムOIDをRSA + SHA256スキームにマッピング * ============================================================ */   sig_params_t スキーム = map_sig_oid(sig_oid, sig_oid_len);   g2b_HSE_Status = ハッシュ要求(HSE_ACCESS_MODE_ONE_PASS, 0U, 1U, HSE_HASH_ALGO_SHA2_256, 0U, (uint32_t) tbs_len, tbs, &hash_len, ハッシュ, txOptions、HSE_SGT_OPTION_NONE);   uint16_t modulus_len = ca_pub.N_len * 8; uint16_t exponent_len = ca_pub.E_len; g2b_HSE_Status = LoadRsaPublicKey(&g2b_keyPubHandler, 0U, modulus_len, ca_pub.N、exponent_len、ca_pub.E);   g2b_HSE_Status = RsaPkcs1v15VerSrv(g2b_keyPubHandler、HSE_HASH_ALGO_SHA2_256、 (uint32_t) tbs_len, tbs, FALSE, HSE_SGT_OPTION_NONE, (uint32_t) &sig_len, sig);   rsa_pub_free(&ca_pub);   /* デモ終了: 生き続ける*/ のために （;;） {   }   /* 到達不能 */ /* 0を返す; */ } Re: RSA Verification of Signature of CA X509 Certificate for authenticity こんにちは@R_S002 前回の返信を解決策として受け入れていただいたのを確認しました。問題は解決したということですか？今日は確認したかったSO、まだアクティブな問題であるかどうかを確認してください。 ありがとうございます ルーカス Re: RSA Verification of Signature of CA X509 Certificate for authenticity こんにちは@lukaszadrapa 実際、私は次のステップに進む前に各ステップを検証するだけで、この完全なコードをステップごとに構築しました。したがって、署名検証ステップより上では問題はないと思います/予想します。 また、中間データはポインターなので、このコードを DS に直接ビルドして実行CAN。したがって、ここにコピーして貼り付けるのは面倒です。 ご希望であれば、証明書と公開鍵の PEM ファイルをCANお送りします。 これは緊急の開発です、SO迅速な返信が非常に役立ちます。 Re: RSA Verification of Signature of CA X509 Certificate for authenticity こんにちは@R_S002 明確にするために、プロセスの各ステップを個別に検証してみましたか？たとえば、中間結果を OpenSSL と比較するなどです。そうすれば、どこで相違があるのかを正確に特定できるかもしれません。可能であれば、取得した中間データ（TBS、署名、公開鍵など）を共有していただけますか？ よろしくお願いいたします。 ルーカス

NXP s32k312 SRAM MultibitError @danielmartynek  I’m able to hit the SRAM ISR (ERM0_ISR_Handler) for single-bit errors, but the handler is not being called for multi-bit errors. As far as I understand, a non-correctable error event corresponds to a multi-bit error, correct? I can see that the SRAM non-correctable error event bit is set in SR0, but the ISR is not being triggered. Could you please help me understand how to call the multi-bit error ISR? I enabled interrupt notification for SRAM0 in CR0 register also Re: NXP s32k312 SRAM MultibitError Hi @Anitha7, Uncorrectable faults trigger a CM7 fault exception. In the example I linked, I enabled the Bus_Fault exception, but with a lower priority than the priority of the ERM handler so that the ERM handler is called first. I believe this might be the issue in your project. Also, double-check the VTOR pointer and ensure that the ERM interrupt is enabled in the NVIC. You may notice the interrupt pending in NVIC. Re: NXP s32k312 SRAM MultibitError hi @danielmartynek  Multibit means Double bit as per RM I configured the system for an SRAM0 as per your reference. uncorrectable ECC fault occur(NEC0) by setting the corresponding bit in the SRO register. I enabled interrupt notification for NEC0 and single bit event in corresponding CR0 register. After Non correctable ECC fault occurs, control transfers to the system call function, software not working after that until i perform reset. The ERM_1_Handler is not being triggered, even though I have added it. For single-bit errors, the ERM_0_Handler is triggered correctly. What should I do to ensure that the ERM_1_Handler is invoked when a multi-bit (uncorrectable) ECC error occurs? Also, just to confirm — does a multi-bit error(double bit error) always indicate an uncorrectable ECC fault? After Non correctable ECC event occurs i need to perform reset run in ECU in normal mode Re: NXP s32k312 SRAM MultibitError Hi @Anitha7, What do you mean by a multi-bit error? There is one 8-bit checksum for 64bits (8 bytes) of data, it is not possible to detect every posilble ECC error. There is ECC SECDED (Single error correction, Double error detection). Regards, Daniel Re: NXP s32k312 SRAM MultibitError Hi @danielmartynek  VTOR table points to flash memory only during SRAM0 inject uncorrectable ECC fault. I configured the system for an SRAM0 as per your reference example code. uncorrectable ECC fault occur by setting the corresponding bit in the SRO register. I enabled interrupt notification in corresponding CR0 register. After uncorrectable ECC fault occurs, control transfers to the system call function, software not working after that until i perform reset. The ERM_1_Handler is not being triggered, even though I have added it. For single-bit errors, the ERM_0_Handler is triggered correctly. What should I do to ensure that the ERM_1_Handler is invoked when a multi-bit (uncorrectable) ECC error occurs? Also, just to confirm — does a multi-bit error always indicate an uncorrectable ECC fault? Re: NXP s32k312 SRAM MultibitError Hi @Anitha7, I updated the example by adding uncorrectable error injection into SRAM0. https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K344-EIM-ERM-DTCM-SRAM-Baremetal-v3-0-S32DS36/ta-p/2193534 Can you read the VTOR register in your application? The interrupt vector table must not reside in SRAM0 when injecting an uncorrectable ECC fault into the memory. Otherwise, the ECC fault would corrupt the vector table during a fetch leading to another fault exception. Regards, Daniel

S32K1: LPUART BAUD register OSR bits stuck Hi. My target MCU is a S32K144W on the S32K14W-Q064 evaluation board. I'm configuring the LPUART0 baud rate and I'm noticing that I cannot clear the lower 4 OSR bits in the BAUD register. Those bits default to 1 on reset, but should be writable/clearable afterward. I can set or clear the upper OSR bit, but the lower 4 bits are stuck, always set, and can't be cleared through any operation on that register. Spoiler (Highlight to read) Obviously that limits the function of the UART, and makes choosing an appropriate baud rate difficult. I have combed through the documentation several times but I can't find any mention of a restriction on these bits, or a condition that must be satisfied for them to be cleared or changed. Perhaps I missed it. I found 2 other forum posts where a user mentions the same problem (though on a different part). "So i noticed that only  value of 16 and 32 can be set in OSR field (15 and 31), any other value results in getting 16/32." Unfortunately, I don't see a resolution. https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-K82F-uart-problem/m-p/845950 https://community.nxp.com/t5/Kinetis-Microcontrollers/LPUART0-baudrate/m-p/792047/highlight/true#M48190 Any thoughts on why these bits are stuck or how I can change them? Thanks for your help! Trevor Re: S32K1: LPUART BAUD register OSR bits stuck Hi Trevor, Thank you for your information. I hadn't noticed before that you can't clear the OSR bit separately; I saw that writing to the BAUD register in the RTD is also done all at once. Best Regards, Robin Re: S32K1: LPUART BAUD register OSR bits stuck Hi Robin, I'm not using S32K1 RTD - I'm configuring the UART directly in the LPUART registers. To clarify, I was trying clear the OSR and SBR bits first (using LPUART_BAUD_OSR_MASK and LPUART_BAUD_SBR_MASK), then set the required bits (using LPUART_BAUD_OSR(x) and LPUART_BAUD_SBR(x)) to get the baud rate that I need. The key is that if you clear all of the OSR bits, it will result in an oversampling ratio of 16, which is the same as the default with the lower 4 bits set. The reference manual says this, but doesn't appear to fully explain what happens when you clear the OSR bits. What I didn't understand was that if you clear all of the OSR bits, the hardware doesn't just interpret that as using an oversample ratio of 16, but instead it literally forces the 4 lower bits back to 1, back to the default setting. So you can't use the typical pattern of masking and clearing those bits first, then setting the bits you need. Instead you have to set the BAUD register all it once with the values that you need in all of the bit groups. So by changing this: IP_LPUART0->BAUD &= ~( LPUART_BAUD_OSR_MASK ); IP_LPUART0->BAUD |= ( LPUART_BAUD_OSR(10u) ); ... To this: IP_LPUART0->BAUD = ( LPUART_BAUD_OSR(10u) | ... ); It looks like it is now working as expected. Thanks again for your help. Regards, Trevor Re: S32K1: LPUART BAUD register OSR bits stuck Hi Did you configure BAUD[BOTHEDGE]? If you are using S32K1 RTD, then you may need to configure it by refer to: Best Regards, Robin ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "ACCEPT AS SOLUTION" 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. -------------------------------------------------------------------------------

Design Studio v3.6.4 - S32 SDK RTM v4.0.2 を追加するにはどうすればいいですか? こんにちは、 私は Windows 11 上の S32 Design Studio の新規ユーザーです。 S32 Design Studio v3.6.4 を正常にインストールし、[ヘルプ] → [S32DS 拡張機能と更新] からいくつかの更新を追加しました。ただし、SDK の利用可能なアップデートはありませんでした。そのため、S32SDK_S32K1xx_RTM_4.0.2.exe (S32 SDKs RTM v4.0.2) を手動でダウンロードしてインストールしました。 Design Studioで新しいS32アプリケーションプロジェクトを作成した後、.mexファイルが見つからないため、コード コンフィギュレータのアイコンが表示されません。その結果、コード コンフィギュレータを開いて GPIO やその他のペリフェラルを構成することができません。 私の目標は、RTM v4.0.2 をインストールして、S32K144 のコード コンフィギュレータを使用して、単純な手続き型 C コード (AUTOSAR スタイルではない) を生成できるようにすることです。RTD の更新は必要ありません。 この問題を解決するにはどうすればよいですか? よろしくお願いします。 Re: Design Studio v3.6.4 - How to add S32 SDK RTM v4.0.2 ? こんにちは、VaneBさん。返信ありがとうございます。DS v3.6.4 をアンインストールし、DS v3.4 をインストールしました。ヘルプ - 拡張機能と更新プログラムで、SDKs RTM v4.0.3 をインストールしました。 Re: Design Studio v3.6.4 - How to add S32 SDK RTM v4.0.2 ? こんにちは@TLHK S32SDK_S32K1xx_RTM_4.0.2 は S32 Design Studio v3.6.4 と互換性がありません。この SDK はもともと S32 Design Studio v3.4 のアップデートとして提供されました。 これを使用するには、S32DS v3.4 用の S32K1xx サービス パック 1 をダウンロードし、S32DS の拡張機能と更新を通じて新しい更新サイトとしてインストールします。 適切な機能を確保するには、対応する IDEs バージョンをダウンロードして使用してください。 BR、ヴェインB

S32 Design Studio v3.6.x および LQFP パッケージ用の S32K39x ピンツール こんにちは、 既存の例をインポートすることと、S32K396 用の RTD 6 QLP01 を使用して新しいアプリケーション プロジェクトを生成することの両方を試しました。 ピン ツールのグラフィック表示は BGA パッケージでは見栄えが良いのですが、パッケージを 176LQFP に変更すると、LQFP パッケージの上部にピンがなくなります (すべて左、右、下部にあります)。 これは対処が予定されている問題ですか、それとも私のインストールの問題ですか? ありがとうございます！ Re: S32 Design Studio v3.6.x and S32K39x Pins tool for LQFP package バグレポートが S32 Design Studio チームに送信されました。彼らはこのバグを確認し、FUTUREリリースで修正する予定です。 Re: S32 Design Studio v3.6.x and S32K39x Pins tool for LQFP package ハイ この問題を報告していただきありがとうございます。この問題は S32DS チームに報告済みです。返答が届き次第お知らせします。 現在、ピンのポジショニングが正しく表示されていません。S32K396RM (Rev. 4 11 2024).pdf のS32K36_IOMUX.xlsxファイルのS32K396_176lqfp_EPを参照してください。正しいピンのポジショニング。 よろしくお願いします、 ロビン --------------------------------------------------------------------------------- 注記： - この投稿があなたの質問への回答である場合は、「解決策として承認」ボタンをクリックしてください。ありがとう！ - Threadは最後の投稿から7週間フォローされます。それ以降の返信は無視されます。 後ほど関連する質問がある場合は、新しいThreadを開いて、閉じたThreadを参照してください。 ---------------------------------------------------------------------------------

What does /S400 suffix stand for in automotive grade Diodes? What does /S400 suffix stand for in automotive grade Diodes?

Using Taplinx library on iOS with Desfire EV2/EV3 tags Dear Team, I am developing an application to format and read data from a DESFire EV3 16KB card. I followed the UG10045 guide and successfully added both TapLinx and J2ObjC libraries as instructed. I also disabled the "Debug executable" option in my application map. Passed the license verification step. However, when I send the SelectApplication or GetFreeMemory command, I get the error as below. I would love to get some help or guidance to resolve this issue. Thank you very much, Manh Vu Vimass class ViewController: UIViewController, NFCTagReaderSessionDelegate { let licenseKey = "..." let licenseKeyLocal = "..." @IBAction func nfcAction(_ sender: Any) { print("nfcAction") var tagReaderSession: NFCTagReaderSession! tagReaderSession = NFCTagReaderSession(pollingOption: [.iso14443, .iso15693], delegate: self) tagReaderSession.alertMessage = "begin scan nfc" tagReaderSession.begin() } func tagReaderSessionDidBecomeActive(_ session: NFCTagReaderSession) { print("tagReaderSessionDidBecomeActive") } func tagReaderSession(_ session: NFCTagReaderSession, didInvalidateWithError error: any Error) { print("tagReaderSession " + error.localizedDescription) } func tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) { guard let firstTag = tags.first else { session.invalidate(errorMessage: "ok nfc") return } session.connect(to: firstTag){ (error: Error?) in switch firstTag { case .iso7816(let tag): self.libraryManager.getDESFireEV3Instance().selectApplication(withAppID: 0) { isSS in print("result selectApplication: \(isSS)") } self.libraryManager.getDESFireEV3Instance().getFreeMemoryonCompletion { data, isSS in print("result getFreeMemoryonCompletion: \(isSS) - \(data)") } break case .feliCa(_): print("feliCa card 1") break case .iso15693(_): print("iso15693 card 1") break case .miFare(_): print("miFare card 1") break @Unknown default: print("unknow card 1") break } } } // var tapLinxLibrary: TapLinxLibrary = TapLinxLibrary.shared() var libraryManager : TLLibraryManager! func initializeTapLinx() { tapLinxLibrary.verifyLicense(licenseKey) { isSS, res in if (isSS) { print("onl TapLinx initialized successfully " + res) self.libraryManager = TLLibraryManager.shared() } else { print("onl TapLinx initialized false " + res ) } } tapLinxLibrary.doLocalVerification(withSignature: licenseKeyLocal) { isSS, res in if (isSS) { print("TapLinx initialized successfully " + res) self.libraryManager = TLLibraryManager.shared() } else { print("TapLinx initialized false " + res ) } } } override func viewDidLoad() { super.viewDidLoad() initializeTapLinx() } } error: onl TapLinx initialized successfully Online license verified successfully, time to explore Taplinx Library TapLinx initialized successfully License Verified Successfully, Time to explore Taplinx Library nfcAction tagReaderSessionDidBecomeActive Command sent to card : 5A000000 Exception Caught: -[ComNxpNfclibCustomModules apduExchangeWithByteArray:]: unrecognized selector sent to instance 0x3007da160 Caught an exception ( 0 CoreFoundation 0x00000001a19d1098 47427277-EE15-3C17-AD68-6886B0380B5E + 540824 1 libobjc.A.dylib 0x000000019ecd32e4 objc_exception_throw + 88 2 CoreFoundation 0x00000001a1ad77c8 47427277-EE15-3C17-AD68-6886B0380B5E + 1615816 3 CoreFoundation 0x00000001a196e888 47427277-EE15-3C17-AD68-6886B0380B5E + 137352 4 CoreFoundation 0x00000001a196e1b0 _CF_forwarding_prep_0 + 96 5 VCard.debug.dylib 0x000000010705fe70 kl0 + 2100 6 VCard.debug.dylib 0x0000000106efcbe4 oBo + 820 7 VCard.debug.dylib 0x000000010704bee0 nrou + 416 8 VCard.debug.dylib 0x0000000106ce2bcc -[TL_DESFireEV3 selectApplicationWithAppID:onCompletion:] + 52 9 VCard.debug.dylib 0x00000001068f67ec $s5VCard14ViewControllerC16tagReaderSession_9didDetectySo06NFCTageF0C_Say7CoreNFC0I0OGtFys5Error_pSgcfU_ + 704 10 CoreNFC 0x000000023c6be28c D938B7C1-5EC0-3CFC-94A2-00A56583760B + 270988 11 CoreNFC 0x000000023c68d198 D938B7C1-5EC0-3CFC-94A2-00A56583760B + 70040 12 libdispatch.dylib 0x00000001a9648370 B8C15E69-D076-317D-9296-1279500738FC + 9072 13 libdispatch.dylib 0x00000001a964a0d0 B8C15E69-D076-317D-9296-1279500738FC + 16592 14 libdispatch.dylib 0x00000001a96516d8 B8C15E69-D076-317D-9296-1279500738FC + 46808 15 libdispatch.dylib 0x00000001a9652214 B8C15E69-D076-317D-9296-1279500738FC + 49684 16 libdispatch.dylib 0x00000001a965d258 B8C15E69-D076-317D-9296-1279500738FC + 94808 17 libdispatch.dylib 0x00000001a965caa4 B8C15E69-D076-317D-9296-1279500738FC + 92836 18 libsystem_pthread.dylib 0x0000000228d1bc7c _pthread_wqthread + 288 19 libsystem_pthread.dylib 0x0000000228d18488 start_wqthread + 8 ) result selectApplication: false Command sent to card : 6E Exception Caught: -[ComNxpNfclibCustomModules apduExchangeWithByteArray:]: unrecognized selector sent to instance 0x3007da160 Caught an exception ( 0 CoreFoundation 0x00000001a19d1098 47427277-EE15-3C17-AD68-6886B0380B5E + 540824 1 libobjc.A.dylib 0x000000019ecd32e4 objc_exception_throw + 88 2 CoreFoundation 0x00000001a1ad77c8 47427277-EE15-3C17-AD68-6886B0380B5E + 1615816 3 CoreFoundation 0x00000001a196e888 47427277-EE15-3C17-AD68-6886B0380B5E + 137352 4 CoreFoundation 0x00000001a196e1b0 _CF_forwarding_prep_0 + 96 5 VCard.debug.dylib 0x000000010705fe70 kl0 + 2100 6 VCard.debug.dylib 0x0000000106f18f7c CQPYCiZw + 164 7 VCard.debug.dylib 0x000000010707ffb8 DiaUpCq + 216 8 VCard.debug.dylib 0x0000000106ce53e0 -[TL_DESFireEV3 getFreeMemoryonCompletion:] + 44 9 VCard.debug.dylib 0x00000001068f693c $s5VCard14ViewControllerC16tagReaderSession_9didDetectySo06NFCTageF0C_Say7CoreNFC0I0OGtFys5Error_pSgcfU_ + 1040 10 CoreNFC 0x000000023c6be28c D938B7C1-5EC0-3CFC-94A2-00A56583760B + 270988 11 CoreNFC 0x000000023c68d198 D938B7C1-5EC0-3CFC-94A2-00A56583760B + 70040 12 libdispatch.dylib 0x00000001a9648370 B8C15E69-D076-317D-9296-1279500738FC + 9072 13 libdispatch.dylib 0x00000001a964a0d0 B8C15E69-D076-317D-9296-1279500738FC + 16592 14 libdispatch.dylib 0x00000001a96516d8 B8C15E69-D076-317D-9296-1279500738FC + 46808 15 libdispatch.dylib 0x00000001a9652214 B8C15E69-D076-317D-9296-1279500738FC + 49684 16 libdispatch.dylib 0x00000001a965d258 B8C15E69-D076-317D-9296-1279500738FC + 94808 17 libdispatch.dylib 0x00000001a965caa4 B8C15E69-D076-317D-9296-1279500738FC + 92836 18 libsystem_pthread.dylib 0x0000000228d1bc7c _pthread_wqthread + 288 19 libsystem_pthread.dylib 0x0000000228d18488 start_wqthread + 8 ) result getFreeMemoryonCompletion: false - 0 tagReaderSession Session invalidated by user Code examples Getting Started

s32k311-100hdqfp IOMUX Could you please provide the Excel sheet for S32K311-100hdqfp pinout (IOMUX/pin configuration)  Appreciate your effort,  Re: s32k311-100hdqfp IOMUX Hi@osama_desoqi You should able to find these documents in S32K3 RM's attachments.

S32K328NHT1MJBSR MAPBGA289 プログラミングの問題 拝啓： 当社はサードパーティプログラマーメーカーです。 現在、S32K328NHT1MJBSR のプログラミングをテストしています。 お客様のファイルのプログラミングに成功すると、J-Linkは正常に接続されます。   しかし、消去は失敗します。 ランダムコードをプログラムする場合は、消去とプログラムを繰り返すCAN。 これが私たちのプログラミング回路です。   何か提案はありますか? よろしくお願いします。 Re: S32K328NHT1MJBSR MAPBGA289 Programming problems こんにちは@gary_yang エラー メッセージによると、HSE 領域を消去しようとしていることが、消去/書き込みの失敗の原因であると考えられます。

How about MCXW71's wireless UART to connect to APPs other than IoT Toolbox? I've recently been using the WirelessUART routines for the MCXW71, and using the IoT Toolbox it is possible to connect and interact with data normally. I would like to use, for example, a laptop with Bluetooth, or an app for another phone to get the data. The problem I'm having is that using the Bluetooth Assistant, after scanning for the mac of the development board, it disconnects just after connecting. 回复： MCXW71的wireless UART怎么样连接除IoT Toolbox之外的APP Window11, support BT+BLE, even his other bluetooth is possible. 回复： MCXW71的wireless UART怎么样连接除IoT Toolbox之外的APP Hi, @lugl On Windows you can try scanning and connecting using the Bleak tool + Python script approach. Bleak is a cross-platform BLE library that supports working on Windows. You can search online for the relevant information, at present we do not provide ready-made internal scripts for reference. Best regards. Christine.

sja1110 100base-tx UDP 失敗 こんにちは： 1.flash_image.bin->sja1110-uc.binをダウンロードします そして switchcore_0_Config.hex -> sja1110-switch.bin (hex から bin) switch_config_s32g_vnp_rdb デモ プロジェクトからボードへの転送が成功しました。 2. その後、100base-tx (192.168.0.200) に正常に ping を実行できます。 3. しかし、sja1110 ECT ツールを 100base-tx に接続することはできません。また、100base-T1 にも接続できません。 アドバイスをお願いします、よろしくお願いします！

ライセンス（この注文では利用可能なライセンスはありません） こんにちは、 ノードロックライセンスを購入しましたが、製品を登録しても機能しません。 会社のメールが使えません。