I2C receive error Hello everyone, I have an error with I2C on S32K344 EVB board.  I don't know if the configuration and the code are wrong or missing something. The first frame address + 1 bit write is OK (ACK received). The next frame I sent is the data 0x00, I also got ACK from slave. However, the third frame is reading from slave but the API function return status "LPI2C_IP_BUSY_STATUS". Here are some captures of the problem . Thanks for your help. Re: I2C receive error Hi, you are checking wrong return status of Send function. Non-blocking Send returns LPI2C_IP_SUCCESS_STATUS, if transfer was started properly. In your case it does not go to do-while loop to test transfer status. So try     BR, Petr

EB Tresos 激活失败 我从 https://nxp.flexnetoperations.com/control/frse/download?agree=Accept&element=13469337 获得了 激活码 。 使用此激活码激活时会出现以下错误信息： ERROR: flxActAppActivationSend (50040,41147,10248) 指定的数量超过允许的最大数量 (0)。 与 FlexNet Operations Server 的连接失败。 看来这个激活码已经用完了。请更新它。 Re: EB Tresos activation failed 你好 您使用的密钥许可证数量似乎已用完。 您的恩智浦账户上总是有最新的密钥。如果用完了，通常几天后就会换上新的。 顺祝商祺！ Peter Re: EB Tresos activation failed 你好@罗宾-沈 我在其他主题中看到过类似的问题，也看到了你的回复，但这些主题中的解决方案已不再有效。 您能帮我解决这个问题吗？

Using DMA on the MCUexpressoIDE with K64F Good day to you all, I am currently working on a project that needs high sampling rate for the ADC channels. I intended to use direct memory acces to avoid interrupts at all costs. So far, Ive set a hardware trigger for the ADC and configured only 2 channels for it to read. Its the DMA part that's making me thug my hair, it seems overcomplicated on MCU expresso. Can somebody help me set a loop to do continuos sampling of the "n" AD channels. I've been taking the AN4590 document as base, but the functions are behaving a lot diferent from what is in the source material. The EDMA version I am ussing is 2.4.0. The board is the K64F. I'd aprecciate if some light could be shed onto this. Thanx Re: Using DMA on the MCUexpressoIDE with K64F Hi, good day,  Update: I've abbandoned the operational system for now and got it to work as I wanted. For anyone facing the same issues, following the attached PDF is a pretty good place to start in order to understan the way edma works. Once it's working it should not be dificult to place the code on the RTOS system. Also, thank you Edwin, for the support. Best regards. Re: Using DMA on the MCUexpressoIDE with K64F Hi @Edwin, Yes, the SDK currently in use is v2.11.0. I’ve been following your recommendation and using the provided example to configure the DMA peripheral. I’ve hit a bit of a snag — the code is getting stuck in a while loop — and I haven’t had the time to fully investigate it yet. I plan to debug it tomorrow to understand what’s happening. My initial guess is that it’s related to FreeRTOS concurrency, or more likely, an issue in the code itself. For context, my goal is to place the process sample function inside a periodic task that reads and filters all ADC data from the output buffer that the DMA conveniently fills. It’s important to avoid interruptions, since there will be many channels being read at a relatively high sampling rate. Thanks for the input — I really appreciate your help. Best regards, Gabriel. Re: Using DMA on the MCUexpressoIDE with K64F Hi @GabrielChies, What version of the SDK are you using? The latest one is SDK v2.11.0, and I highly recommend you upgrade to that version if you are using an older one. You should be able to continue development with the Peripherals Tool, although implementing the DMA is not a trivial task to do without a base example. I recommend you check the example code I shared previously and base your Peripherals Tool settings to match the ones from the example code. BR, Edwin. Re: Using DMA on the MCUexpressoIDE with K64F Hello Edwin, thanks for the reply. I've already looked into the example you have mentioned. It does not use the Peripherals tools and also some functions seem to be different (not compatible) with the version of the SDK i am running. Should I abbandon the peripherals tool and do the coding by hand? I rather avoid it since the tool is meant to prevent any mistakes if correctly used. Eaguer to listen to your opinion. Best regards. Re: Using DMA on the MCUexpressoIDE with K64F Hi @GabrielChies, You can find an ADC + eDMA example code on the FRDM-K64F SDK called "adc16_continuous_edma". I highly recommend you use this as reference for your application. BR, Edwin.

rw612 ble gatt Server paring how to fixed passkey rw612 -> gatt server   NoInputNoOutput phone ->gatt client ble paring，how to fixed rw612 passkey （for example 123456，Not a random value），phone input 123456 to pair rw612 Re: rw612 ble gatt Server paring how to fixed passkey Hi @Christine_Li, Thank you so much for the quick response! The patch you shared worked perfectly, and I’m now able to set the fixed PassKey successfully. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Siddhesh_Nayak  Thanks for reaching me out. I will share the patch with you through working email. And for your information, I already report this issue to our internal SAE team, I think they are evaluating to include the patch in our future release. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi @Christine_Li, I am upgrading the SDK v25.09.00 from v2.15.00 in our MW. I have noticed the same where in even If I set the CONFIG_BT_FIXED_PASSKEY and I call bt_passkey_set(FIXED_PASSKEY_VALUE). the bt_conn_auth_cb.passkey_display callback gives me a random PassKey instead of the Fixed.  This was working perfectly with the SDK version v2.15.00. Environment Details : Board used: FRDM-RW612 SDK : v25.09.00 application : Custom Application. Can you please help me out solve the issue? Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  Thanks for your trying and let me know your result!   Can you please create a new case to track the new issue and mark my answer as a solution for this case? We always recommend to track one issue with one case, so that we can provide a better reference for future cases.   And for your info, we always deal with the case with different priority level. If you have a company email, please do not hesitate to create case with your company's email. It might increase the priority of your case.   If you don't have, please ignore my hints. And we will still continue to support you with current priority.   Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Christine_Li Thanks for the reply, I have tried it and it works，follow the steps you provided,passkey is fiexd to 123456, but a new problem arises: when finish bonding,I try to get Battery Service,it is not work and rw612 shell seems not work. Please take a look at my log to see if there are any problems, thanks for any help. @bt> bt.init @bt> Bluetooth initialized Settings Loaded 29224: DEBUG bt_pal_smp.c:9449:LE SC enabled @bt> bt.advertise on Advertising started @bt> bt.auth display @bt> bt.fixed-passkey 123456 ----func: cmd_fixed_passkey, line: 4347------- @bt> ----func: cmd_fixed_passkey, line: 4368--passkey 123456----- @bt> BLE Connected: 44:BD:E2:B9:92:FD (random) 58269: DEBUG bt_pal_smp.c:7164:conn 200273BC handle 128 58269: DEBUG bt_pal_smp.c:5436:chan 2002948C cid 0x0006 44:BD:E2:B9:92:FD (random)@bt> LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 328) LE conn param req: int (0x0006, 0x0006) lat 0 to 500 LE PHY updated: TX PHY LE 1M, RX PHY LE 1M LE conn param updated: int 0x0006 lat 0 to 500 LE conn param req: int (0x0018, 0x0018) lat 0 to 500 LE conn param updated: int 0x0018 lat 0 to 500 LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 328) LE PHY updated: TX PHY LE 2M, RX PHY LE 2M LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 2120) LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 328) LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 2120) Confirm pairing for 44:BD:E2:B9:92:FD (random) 75262: DEBUG bt_pal_smp.c:9303:event 2 75262: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 75262: DEBUG bt_pal_smp.c:8515:SMP event = SMP_AUTHENTICATION_REQUEST, status 0 75262: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC 75262: DEBUG bt_pal_smp.c:8812:Recvd SMP_AUTHENTICATION_REQUEST 75262: DEBUG bt_pal_smp.c:8824:Bonding type : Bonding 44:BD:E2:B9:92:FD (random)@bt> bt.auth-pairing-confirm 44:BD:E2:B9:92:FD (random)@bt> Passkey for 44:BD:E2:B9:92:FD (random): 123456 81122: DEBUG bt_pal_smp.c:9303:event 4 81122: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 81122: DEBUG bt_pal_smp.c:8515:SMP event = SMP_PASSKEY_DISPLAY_REQUEST, status 0 81122: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC 81122: DEBUG bt_pal_smp.c:8946:Event : SMP_PASSKEY_DISPLAY_REQUEST 81122: DEBUG bt_pal_smp.c:8947:BD Address : FD 92 B9 E2 BD 44 88372: DEBUG bt_pal_smp.c:9303:event 6 88372: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 88373: DEBUG bt_pal_smp.c:8515:SMP event = SMP_KEY_EXCHANGE_INFO_REQUEST, status 0 88373: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC 88373: DEBUG bt_pal_smp.c:8965:Event : SMP_KEY_EXCHANGE_INFO_REQUEST 88373: DEBUG bt_pal_smp.c:8966:BD Address : FD 92 B9 E2 BD 44 Re: rw612 ble gatt Server paring how to fixed passkey Hi， @flybir  Yes， I send it again just now. Please check your email and let me know whether you received the patch, and whether this patch works on your side. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Christine_Li     Thanks for the reply, I did not receive the patch you shared to me by email.     Did you send to the  [email protected] ? Re: rw612 ble gatt Server paring how to fixed passkey Hi @flybir  Have you already added the patch I shared to you by email? If no, please firstly add the patch, then have a try.  Thanks! From your shared log, I see below: The passkey doesn't fixed to 123456, it is showing: 047307 is your passkey. I guess you didn't add my patch shared to you by email. 88617: DEBUG bt_pal_smp.c:8824:Bonding type : Bonding bt.auth-pairing-confirm 49:7B:58:F5:35:CA (random)@bt> Passkey for 49:7B:58:F5:35:CA (random): 047307 Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Christine_Li     Thanks for the reply, I have tried it and it still didn't work，follow the steps you provided，passkey is still not fiexd to 123456；     The FW image I have used provided by the directory:  /components/conn_fwloader/fw_bin/rw61x_sb_ble_a2.bin     Please take a look at my log to see if there are any problems, thanks for any help. /************************************************ENABLE DEBUG LOG *************************************/ @bt> bt.init @bt> Bluetooth initialized Settings Loaded 6065: DEBUG bt_pal_smp.c:9449:LE SC enabled @bt> bt.advertise on Advertising started @bt> bt.auth display @bt> bt.fixed-passkey 123456 ----func: cmd_fixed_passkey, line: 4347------- @bt> ----func: cmd_fixed_passkey, line: 4368--passkey 123456----- BLE Connected: 49:7B:58:F5:35:CA (random) 81457: DEBUG bt_pal_smp.c:7164:conn 200273BC handle 128 81457: DEBUG bt_pal_smp.c:5436:chan 2002948C cid 0x0006 49:7B:58:F5:35:CA (random)@bt> LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 328) LE conn param req: int (0x0006, 0x0006) lat 0 to 500 LE PHY updated: TX PHY LE 1M, RX PHY LE 1M LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 328) LE conn param updated: int 0x0006 lat 0 to 500 LE conn param req: int (0x0018, 0x0018) lat 0 to 500 LE conn param updated: int 0x0018 lat 0 to 500 Confirm pairing for 49:7B:58:F5:35:CA (random) 88617: DEBUG bt_pal_smp.c:9303:event 2 88617: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 88617: DEBUG bt_pal_smp.c:8515:SMP event = SMP_AUTHENTICATION_REQUEST, status 0 88617: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC 88617: DEBUG bt_pal_smp.c:8812:Recvd SMP_AUTHENTICATION_REQUEST 88617: DEBUG bt_pal_smp.c:8824:Bonding type : Bonding bt.auth-pairing-confirm 49:7B:58:F5:35:CA (random)@bt> Passkey for 49:7B:58:F5:35:CA (random): 047307 94322: DEBUG bt_pal_smp.c:9303:event 4 94322: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 94322: DEBUG bt_pal_smp.c:8515:SMP event = SMP_PASSKEY_DISPLAY_REQUEST, status 0 94322: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC 94322: DEBUG bt_pal_smp.c:8946:Event : SMP_PASSKEY_DISPLAY_REQUEST 94322: DEBUG bt_pal_smp.c:8947:BD Address : CA 35 F5 58 7B 49 Pairing failed with 49:7B:58:F5:35:CA (random) reason: Authentication requirements (4) Security failed: 49:7B:58:F5:35:CA (random) level 1 reason: Authentication failure (1) 106742: DEBUG bt_pal_smp.c:9303:event 1 106742: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 106742: DEBUG bt_pal_smp.c:8515:SMP event = SMP_AUTHENTICATION_COMPLETE, status 1028 106742: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC Bond deleted for 49:7B:58:F5:35:CA (random), id 0 Disconnected: 49:7B:58:F5:35:CA (random) (reason 0x13) 109800: DEBUG bt_pal_smp.c:5452:chan 2002948C cid 0x0006 @bt> Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  I already tested it locally, and it can work on my side. Please see attachment for my test logs. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  Firstly add the patch I shared to you by email, then test with below steps. Please let me know whether it works for you. If it does work, please do not hesitate to mark my answer as a solution for this case. Thanks!   Please have a try with below steps: Test process (RW61x as slave，phone with nrf app as master): 1/ bt.init 2/ bt.advertise on 3/ bt.auth display 4/ bt.fixed-passkey 123456 5/ nrf app connect redfinch 6/ nrf app bond 7/ bt.auth-pairing-confirm 8/ nrf app input passkey 123456 Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Christine_Li   Thanks for the reply, I have tried it and it didn't work, When my phone is paired with the RW612, I don't need to enter any passkey.     Please take a look at my log to see if there are any problems, thanks for any help. SHELL build: Oct 24 2025 Copynight 2020 NXP @bt> bt.init @bt> Bluetooth initialized Settings Loaded @bt> bt.fixed-passkey 123456 @bt> bt.advertise on Advertising started @bt> BLE Connected: 78:7B:E1:EC:D5:AC（random） Re: rw612 ble gatt Server paring how to fixed passkey Hi， @flybir  Yes， you are right.  I checked  and found that this API isn't called by anywhere. You might need to call it by referring this example: edgefast_bluetooth_shell. In this example, it calls this API bt_passkey_set(); And please remember enable this Macro: #define CONFIG_BT_FIXED_PASSKEY 1 is also needed. Please see below for my test logs, hope it can help you. @bt> bt.fixed-passkey 123456 Christine:enter cmd_fixed_passkey! @bt> Christine:fixed_passkey is: (passkey 123456) Setting fixed passkey failed (err 0) Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  Thanks for your quick reply. Let me check it further, then share with you. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Christine_Li   Thanks for the reply, I have tried it and it didn't work. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  Can you please have a try with below Macro in edgefast_bluetooth_config.h #define CONFIG_BT_FIXED_PASSKEY 1 Please let me know whether it works for you. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Are you using FRDM-RW612? YES What's your MCUXpresso IDE version? v25.6 SDK version? FRDM-RW612 25.06.00 which example you are using?  frdmrw612_wireless_uart I want the Bluetooth pairing code of the RW612 to be fixed to 123456, and the phone can be paired with the RW612 with a fixed pairing code. I have tryed bt_passkey_set(123456)  not work. Thanks for any help！ Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  Are you using FRDM-RW612? What's your MCUXpresso IDE version? SDK version? and which example you are using? Please let me know more backgrounds of your question, so that I can check further for you. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Thanks for any help Re: rw612 ble gatt Server paring how to fixed passkey Hi @Christine_Li , I'm facing the same issue mentioned above. Could you please share the patch with me. My email is: [email protected]. Please also CC: [email protected] Re: rw612 ble gatt Server paring how to fixed passkey Hi, @saidalghabra  Sorry for my late reply. For this request, can you please help to create a new case to us? We are not allowed to share the patch  to anyone except have case tracking and company's system reviewing/verifying. And also, please let me know which chipset you are using and your SDK version. Thanks for your corporations! Best regards, Christine.

i.MX8 + PCA9450CHN の SYS_nRST と 1.8V 電源間のパワーアップ シーケンスのタイミングの説明 こんにちは、NXP チームの皆様、 プロセッサの電源用 PMIC としてPCA9450CHNを搭載した i.MX8 プロセッサを使用しています。プロセッサまたは PMIC のデータシートには、 SYS_nRSTと PMIC の電源VDD_1V8 (BUCK5FB の出力)間の指定された電源投入シーケンスのタイミングが見つかりませんでした。 SYS_nRSTとVDD_1V8電源間の電源投入シーケンスの正しいタイミング要件または仕様について教えていただけますか? SYS_nRSTとVDD_1V8電源間の電源投入シーケンス時間を測定しました。添付の画像を参照してください。計測された時間 ( 50.2 ms ) が正しいかどうか確認していただけますか? サポートありがとうございます。 よろしく ファズレ・ナビー Re: Clarification on Power-Up Sequence Timing Between SYS_nRST and 1.8V Supply for i.MX8 + PCA9450CH こんにちは@fazle_nabiさん、 あなたのデザインはOKです、問題がないことを確認しました。 SYS_nRST と VDD_1V8 電源間の測定時間は 50.2 ミリ秒であり、実装には許容範囲内です。i.MX8MP プロセッサでは、ステップ間の正確なタイミングよりも、電圧適用シーケンス自体が重要です。ドキュメント内のほとんどの最小電圧上昇タイミング値は 0 ミリ秒であり、適切なシーケンスが維持される限り、特定の遅延は厳密には必要ないことを示しています。 PCA9450CHN は、i.MX8 プロセッサで動作するように特別に設計されており、適切な電源シーケンスを自動的に処理します。正しい電圧シーケンスを示すオシロスコープ測定により、参照図とのタイミングの違いにかかわらず、実装が適切に機能することが確認できます。 これがお役に立てれば幸いです 良い一日をお過ごしください よろしくお願いいたします。 リタ Re: Clarification on Power-Up Sequence Timing Between SYS_nRST and 1.8V Supply for i.MX8 + PCA9450CH 添付の PIMIC 回路図デザインを参照してください。 よろしくお願いします！ Re: Clarification on Power-Up Sequence Timing Between SYS_nRST and 1.8V Supply for i.MX8 + PCA9450CH はい、PIMIC 回路図を参照してください。 ありがとう！ よろしくお願いします。 ファズル Re: Clarification on Power-Up Sequence Timing Between SYS_nRST and 1.8V Supply for i.MX8 + PCA9450CH こんにちは@fazle_nabiさん、 デザインはどうですか？当社のリファレンスボードも同様ですか? 良い一日をお過ごしください よろしくお願いいたします。 リタ Re: Clarification on Power-Up Sequence Timing Between SYS_nRST and 1.8V Supply for i.MX8 + PCA9450CH こんにちは@Rita_Wang添付画像を参照してください よろしくお願いします！ Re: Clarification on Power-Up Sequence Timing Between SYS_nRST and 1.8V Supply for i.MX8 + PCA9450CH こんにちは@Rita_Wang素早い返信ありがとうございます。 VDD_1V8 および SYS_nRTS 信号の電源投入時間の受け入れ基準を知りたいと思いました。プロセッサと PMIC のいずれのデータシートでも、許容範囲を見つけることができません。 VDD_1V8 と SYS_nRTS 間の電源投入時間を測定したところ、カーネル バージョン 5.4.70 で約 51 ミリ秒でした。参考までに添付画像をご参照ください。 迅速なサポートありがとうございます。 よろしく ファズレ・ナビー Re: Clarification on Power-Up Sequence Timing Between SYS_nRST and 1.8V Supply for i.MX8 + PCA9450CH こんにちは@fazle_nabi 、 私はボード上で Linux 5.4.70 バージョンを実行しています。ボードの電源投入時のタイミングは約 30 ミリ秒です。以下を参照してください。 良い一日をお過ごしください よろしくお願いいたします。 リタ Re: Clarification on Power-Up Sequence Timing Between SYS_nRST and 1.8V Supply for i.MX8 + PCA9450CH こんにちは@fazle_nabiさん、 先週はずっとトレーニングだったので、あなたのThreadに返信できませんでした。データがないことは確認しましたので、ボードを測定して結果を共有します。 良い一日をお過ごしください よろしくお願いいたします。 リタ

S32K348 FMEDA S32K348 有 FMEDA 吗？ Re: S32K348 FMEDA HI 我还没有在安全资源中找到 S32K348 FMEDA。 今天早上，我在INTERNAL SafeAssure论坛上看到 FAE WeoWang 申请 S32K348 SEooC FMEDA。如果您已经联系了他，请等待他的回复。 祝好， Robin ------------------------------------------------------------------------------- 注： - 如果本帖回答了您的问题，请点击"ACCEPT AS SOLUTION" 按钮。谢谢！ - 我们会在最后一次发帖后的 7 周内跟踪主题，之后的回复将被忽略 如果您以后有相关问题，请另开新主题并参考已关闭的主题。 -------------------------------------------------------------------------------

[Whelen][SE05x][Edgelock2go]Extending CA expiration on EdgeLock2GO & transport lock Hello Experts, The customer is Whelen, and they reached out to us via Arrow, with the following questions: 1. The CA certificate generated by EdgeLock2GO has an expiration of 15 years from creation. I believe this is probably adequate for our use case, but I wanted to check whether it is possible to extend this. 2. In the past we used the transport lock on the A71CH to detect whether there was any tampering prior to first time use of the device. On that part, it was a latching mechanism. It appears the A5000 also has a transport lock but it is not a latching mechanism, but instead uses some type of authentication to lock/unlock the part. It wasn’t clear to me from the documentation exactly how this mechanism works or how the key is configured to use this mechanism. I am not sure whether this is something that can be configured through EdgeLock2GO or whether Arrow has the ability to configure this mechanism during programming. Would you please help to advise? Thanks in advance for any comment! Best Regards, Kan Re: [Whelen][SE05x][Edgelock2go]Extending CA expiration on EdgeLock2GO & transport lock 1.I checked and found the same that currently there is no option to change validity of intermediate CA. In plug and trust middleware there are examples: Transport Lock example(se05x_TransportLock) and transport unlock example(se05x_TransportUnlock), these examples are demos for reference for the usage of APIs. AN13030’s 5.24 and 5.25 also talks about this. You can check these codes to see how to practically do this. Apart from this, section 4.6 in AN13266 talks about its theory. Also refer to AN13187: A5000 Authentication Application APDU Specification  Basically, 1. you need to create authentication object like AES key, ec key or  user id in se at 0x7FFF0200 RESERVED_ID_TRANSPORT (Edgelock2GO  cannot provision this)  2. open authenticated session (any applet level session: aes , ec key or user id.) 3.setting lock (SetLockState APDU mentioned in AN13187) Example I discussed above can help with usage of APIs  and flow PFA of the docs mentioned above

[Whelen][SE05x][Edgeelock2go]延长 EdgeLock2GO& 运输锁的 CA 过期时间 专家们好 客户是 Whelen，他们通过 Arrow 联系了我们，提出了以下问题： 1.由 edgeLock2Go 生成的 CA 证书自创建之日起有效期为 15 年。我相信这可能足以满足我们的用例，但我想检查一下是否有可能对其进行扩展。 2。过去，我们在首次使用设备之前使用 A71CH 上的传输锁来检测是否存在任何篡改行为。就那部分而言，它是一个锁定机制。看来 A5000 也有传输锁，但它不是锁定机制，而是使用某种类型的身份验证来锁定/解锁该部件。从文档中我并不清楚这个机制到底是如何工作的，也不清楚密钥是如何配置为使用这种机制的。我不确定这是否可以通过edgeLock2Go进行配置，或者Arrow是否能够在编程期间配置这种机制。 能否请您帮忙提供建议？ 预先感谢您的意见！ 顺祝商祺！ 坎 Re: [Whelen][SE05x][Edgelock2go]Extending CA expiration on EdgeLock2GO & transport lock 1.I checked and found the same that currently there is no option to change validity of intermediate CA. 在即插即用中间件中有一些示例：传输锁示例（SE05x_TransportLock）和传输解锁示例（se05x_TransportUnlock），这些示例是演示，可供API的使用参考。AN13030 的 5.24 和 5.25 也谈到了这一点。您可以查看这些代码，了解如何实际操作。除此之外，AN13266 第 4.6 节还介绍了其理论。另请参阅 AN13187：A5000 验证应用 APDU 规范 基本上是这样、 1. 你需要在 se 中创建诸如 AES 密钥、ec 密钥或用户 ID 之类的身份验证对象，位于 0x7FFF0200 RESERVED_ID_TRANSPORT（edgeLock2Go 无法配置此功能） 2. 打开已验证会话（任何小程序级会话：AES、ec key 或用户 ID。） 3.设置锁定（AN13187 中提到的 SetLockState APDU） 我在上文讨论的示例有助于了解应用程序接口和流程的使用情况 上述文件的 PFA

S32K312 FMEDA Hello， We have obtained the FMEDA for the S32K312. We would like to know if, when we need to modify the configuration based on our own application but without the Medini tool, would NXP support us in making the modifications? What form of support would it be (through FAE? or a meeting? etc.)? What information do we need to provide? Thank you！ BRs Re: S32K312 FMEDA Hello, Apologies for the delay in our response. Yes, we can provide customized FMEDAs based on your use case specifics. We would need the following information: 1. Choice Mission Profile 2. Choice of package or exact part number 3. Choice of failure rate catalog (Default is IEC TR 62380) 4. Peripherals (including GPIO pins) to be considered safety related (Please refer the Safety Manual "Addendum" for the list of SR-AD or Safety Related Application Dependent peripherals which may or may not be a part of your application 5. System level measures (and their coverages) to be considered for the protection of peripherals (refer the safety manual for more details and recommendations) Additionally, we would request you to kindly review the list of safety mechanisms and Assumptions of use (AoUs) mentioned in the safety manual, also required by our assumed safety concept. In case of any deviations in your use case ISO calls for a safety impact analysis to be performed by the party changing the list of applicable assumptions. Hoping this helps! Thanks! -Yashwant

How to Debug a Custom Board with i.MX 8 MP via JTAG How can I perform JTAG debugging on the M7 core using a custom board with the AXON-IMX8M-PLUS? I was able to perform JTAG debugging on the M-core of the i.MX 8M Plus EVK by following the tutorial below. MCUXSDKIMX8MPGSUG  Debugging a custom board using the same method causes the i.MX to reset due to the JTAG TRST signal, preventing debugging from starting. The JTAG circuit layout for the custom board is identical to that of the AXON-WIZARD-IMX8M-PLUS. Why does a reset occur on the custom board but not on the evaluation board? yocto: imx-6.6.52-2.2.0.xml  build option: imx-image-full IDE: VSCode, mcuxpresso debugger: jlink base i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus Yocto Project Re: How to Debug a Custom Board with i.MX 8 MP via JTAG Resolved. I'm embarrassed to say, but the JTAG pin configuration was incorrect. Re: How to Debug a Custom Board with i.MX 8 MP via JTAG Hi, For the EVK board, we recommend to refer this AN, so you can also refer this AN. https://docs.nxp.com/bundle/AN14120/page/topics/introduction.html?_gl=1*1bb0dtd*_ga*MTg5ODQ3MTM0My4xNzU2OTU0NTI1*_ga_WM5LE0KMSH*czE3NjIxMzAwNzEkbzEzOCRnMSR0MTc2MjE0NTA1NiRqMzckbDAkaDE2MDUwMTA5MzQ. Best Regards, Zhiming

シナリオツールの紹介 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> フリースケールのQorIQネットワーキング・プロセッサを使用していて、コードの解析が複雑で負荷の高い作業に苦労している場合は、フリースケール・シナリオ・ツール---役立つものがあります。今すぐにでも、物事をよりシンプルにし、より効率的に作業することができます。 この記事では、ツールの簡単なツアーを提供し、セクション 1 でこのツールの簡単な紹介、セクション 2 のインストール - セクション 3 スタート ガイド - セクション 4 の簡単な例 、 そして最後にセクション 5 で、より多くのドキュメントと情報を見つけることができる場所について説明します。 この記事を大いにサポートしてくれたエド・マルティネスに感謝します! 詳細は添付の記事をダウンロードしてください。

freemaster with s32 我使用S32 design studio for s32 platform 3.5安装freemaster，但是显示 could not find jar:file:freemaster_s32k3_v3.0zip,请问是为什么呢？ Re: freemaster with s32 Hi @wwq1, We provide 2 archives with FreeMASTER Driver. One is the plain archive with the source code and the second one is packaged as Eclipse Update Site. Could you make sure that you use the later version. It is highlighted in the picture bellow: Then  you can follow the steps as in the following print screen to install the update site from within S32DS: If that does not work, please let us know at what step does is fails.

クラウドコンピューティングが今日のゲームパフォーマンスを向上させる方法 クラウド コンピューティングは、組み込みシステムやハイブリッド システムでのゲーム パフォーマンスを向上させる新たな可能性をCAN切り開くのでしょうか?NXP コミュニティ フォーラムの多くの開発者は、ゲームをよりスムーズかつ高速に、そして応答性に優れたものにする刺激的なイノベーションをすでに模索しており、クラウド統合により、さらなる成長の可能性が生まれます。 の活用によりクラウドコンピューティング、リアルタイムレンダリング、AIベースのゲームプレイ、マルチプレイヤー同期といった複雑なタスクを、強力なリモートサーバー上で効率的に処理できます。これにより、ローカルデバイスは最小限の遅延と高いフレームレートでスムーズなゲーム体験を提供することに集中できます。クラウドシステムの柔軟性と拡張性により、ユーザーの要求への適応が容易になり、さまざまなハードウェア構成で一貫したパフォーマンスを確保できます。 組み込みハードウェアとクラウドソリューションを組み合わせることで、パワーと効率性の完璧なバランスが実現できると信じています。テクノロジーの進化を見るのは刺激的で、 NXPコミュニティは洞察、ヒント、成功事例を共有するのに最適な場所です。クラウドベースのワークフローを活用してゲームシステムをよりスマートに、より高速に、そしてよりコネクテッドにするための、ポジティブな体験談や独創的なアイデアがあれば、ぜひお聞かせください。

我把 Mac 上的 MCUXpresso IDE 弄坏了。 我在 Mac 上运行 MCUXpresso。 昨天，我做了一件无法弥补的事。 当我尝试通过单击和拖动来选择文本时，只能选中一行。 它从光标到行的左侧开始高亮，并且只会高亮一行。 命令 A 没有任何作用。 我尝试了重启应用程序、重启电脑和重新安装 MCUXpresso。 我试过旧版本的软件和旧版本的工作区，都有同样的问题 我猜不同的版本会使用一个偏好文件，但我找不到。 有人见过这种情况吗？ Re: I've broken MCUXpresso IDE on my Mac. 嗨，@dporada、 您描述的问题可能是一个错误。我会进一步调查，但与此同时，我建议尽可能使用 MCUXpresso 的 VSCode 扩展来解决这个问题。 BR, Edwin. Re: I've broken MCUXpresso IDE on my Mac. 是的，我升级到了 MacOS 26.1。 我的主要苦恼是 https://community.nxp.com/t5/MCUXpresso-General/LPC-Link2-not-found/m-p/2181399/highlight/false#M5717 Re: I've broken MCUXpresso IDE on my Mac. 您也升级到 26.1 版了吗？ Re: I've broken MCUXpresso IDE on my Mac. 除其他外，我也看到了这一点。 Re: I've broken MCUXpresso IDE on my Mac. 埃德温 我运行的是 Mac OS 26.1 和 MCUXpresso v25.6。 我不确定这是否是我从 26.01（我想应该是 26.01）升级到 26.1 时发生的。 我认为如果是操作系统升级，投诉会更多。 我在使用其他文本编辑器时也没有这个问题。 程序有真正的卸载功能吗？ 我就把文件夹扔了。 我在 ~/Library/Application Support/ 文件夹中找不到任何东西，但我删除了其他文件夹中的文件。 我不知道还有其他变化，但我可能不小心选错了菜单或快捷键。 唐 Re: I've broken MCUXpresso IDE on my Mac. 嗨，@dporada、 您能否提供更多信息，说明您在问题出现前做了哪些更改？您使用的是哪个版本的 macOS？您的 MCUXpresso IDE 版本是什么？ 卸载应用程序时，一些残留数据可能会留在电脑上。请尝试卸载 MCUXpresso，然后 使用"Go to Folder" 在 Finder 中 导航到 ~/Library 文件夹，并检查 ~/Library/ Application Support/ 、 ~/Library/Caches/ 和 ~/Library/Preferences/ 等 文件夹 。这样就可以删除 MCUXpresso 的剩余首选项。 BR, Edwin. Re: I've broken MCUXpresso IDE on my Mac. 我刚刚安装了 macOS Tahoe，发现这个 bug 在六个月后仍然存在，我感到非常震惊。 恩智浦怎么可能没有修复一个在如此基本的层面上影响所有 macOS 用户的错误？ 请与我们联系你解决这个问题的时间表。

iMX93 カスタムターゲット用の u-boot をビルディング 新しい imx93 ボードには Yocto Scarthgap を使用しています。EVK 上の NXP SOM と非常によく似た SOM があり、EVK 用の SDIO カードをボードに挿入すると起動します。 Yocto を扱う際の煩わしさを避けるために、u-boot-imx を取り出し、Yocto の SDK を使用してスタンドアロン ビルドにしました。EVK 用の u-boot を正常にビルドし、CAN 起動します。 SO 私は取締役会に次のことを提案します。 board/freescale/imx93_nimbus/ を追加し、board/freescale/imx93_evk/ の内容を入力しました。 変更されたimx93_evk.cimx93_nimbus.c に、内容は変更なし Kconfig を修正し、EVK/evk を NIMBUS/nimbus に置き換え、arch/arm/mach-imx/imx9/Kconfig に追加しました。 Makefileを修正し、EVK/evkをNIMBUS/nimbusに変更しました。 arch/arm/dts/imx93-nimbus.dts を追加しました。内容は imx93-11x11-evk.dts と同じです。 include/configs/imx93_nimbus.h を追加し、EVK/evk を NIMBUS/nimbus に変更しました。 imx93_11x11_evk_defconfig から configs/imx93_nimbus_defconfig を追加しました。デバイスツリー命名と TARGET 命名のみ異なります。 imx93_nimbus_defconfig を作成する 作成する imx-boot-toolsをコピーし、その下にimx93ディレクトリを作成しました u-boot.bin と spl/u-boot-spl.bin を imx-boot-tools/imx93 にコピーします。 imx-boot-tools/imx93 に cd します make -f ../soc.mak flash_singleboot sudo dd if=flash.bin of=/dev/sdb bs=1k seek=32 conv=fsync そして、今では SDIO カードを持っていて、起動できるはずです...しかし何も起こりません。コンソールには何も表示されません。これと同じプロセスに従い、imx93-evk を使用すると、ボード上で動作し、起動します。 flash.bin の場合、EVK は NIMBUS よりも 24,576 バイト大きいため、何かが欠けているように感じます。Bl31.bin、tee.bin、mx93a1-ahab-container.img がすべて存在します。 EVK u-boot-spl.bin と NIMBUS u-boot.bin を使用したイメージを試してみましたが、SPL は起動しましたが、U-BOOT を実行しようとすると停止してしまいました。 ご協力ください！ Re: iMX93 building u-boot for a custom target 早速のお返事ありがとうございます。 私の問題はデバイス ツリー ファイルが見つからないことであることが判明しました。EVK には「imx93-11x11-evk-u-boot.dtsi」という名前のファイルがあります。このファイルについては聞いたことがありませんし、新しいターゲットを作成する際のドキュメントでも見たことがありません。このファイルは、マルチファイル コンテナーを記述するようです。EVK ファイルをコピーし、名前を新しいターゲットに変更してビルドし、起動しました。 FUTURE、同じ問題に遭遇した誰かにとって、この投稿が役に立つことを願っています。 Re: iMX93 building u-boot for a custom target こんにちは@davidpatton お元気でお過ごしのことと思います。 正しいflash.binを生成するための一般的な手順は3.1.1章に記載されています。i.MX 移植ガイドのスタンドアロン環境で U-Boot を構築する方法。 具体的な手順については4.5.13章をご覧ください。i.MX Linux ユーザーガイドの imx-mkimage を使用して imx-boot イメージを構築する方法。 i.MX93の具体的な手順: 必要なパッケージはすべて表 3 にあります。i.MX Linux リリース ノートの BSP およびマルチメディア標準パッケージ。 よろしくお願いいたします。 サラス。 Re: iMX93 building u-boot for a custom target 私も全く同じ問題に遭遇し、あなたの投稿を見つけるまで2日間試行錯誤していました。これはどこかに記録しておく必要がある。

Trying to Write two SDCards at same time using SPI. MK20DX256VLL10 Hello, this is my first post here, please tell me if im doing something wrong. Also english is not my main language, sorry if i say something wrong. I'm trying to write two SDCards at same time using SPI. Why at the same time? Because i need to do as fast as possible. At the time im writing this, im able to copy 48Mb of hex numbers in 07:10 minutes, using 10Mhz in SPI clock. I use the functions generated by Processor Expert: "SM*_ReceiveBlock(SM*_DeviceData, &Buffer, qnt*). After gathering some logs with my logic, i noticed that even if i send: SM2_ReceiveBlock(SM2_DeviceData, &Suporte, 1); SM2_SendBlock(SM2_DeviceData, StartBlock, 1);   SM3_ReceiveBlock(SM3_DeviceData, &Suporte, 1); SM3_SendBlock(SM3_DeviceData, StartBlock, 1); The SPI sends first the SM2 and them SM3. If its the SPI machine who sends the blocks and handle the receiving, i should be able to make these two at same time, no? Kinetis M Series MCUs Re: Trying to Write two SDCards at same time using SPI. MK20DX256VLL10 Hello @Pedro_Henrique, In order to understand better you application, Is SM2_SendBlock blocking? If the answer is yes, then to allow transfers to occur simultaneously, they must be handled through interrupts; otherwise, the core will execute the transfers sequentially, one after the other. Additionally, DMA can be added for higher speed. BR Habib Re: Trying to Write two SDCards at same time using SPI. MK20DX256VLL10 Sorry about the late reply. Yes, both SM2_SendBlock and SM3_SendBlock are blocking. Handling trought interrupts you say any interrupt? Like, calling them from a external interrupt? About DMA, i was looking for this. I think i will try to add DMA, but first i would need executing the transfers simultaneously. Re: Trying to Write two SDCards at same time using SPI. MK20DX256VLL10 Hello @Pedro_Henrique, You need to configure the SPI to use interrupts instead of blocking writes. This approach allows both data transfers to occur simultaneously. You can achieve this using Processor Expert, and this community post might be helpful as a reference. Additionally, you can review this guide, which demonstrates a typical use case for SPI interrupts. Although the example is not specifically for the K20, the implementation steps are essentially the same. BR Habib

EB tresos prompts missing license S32K312 MACL layer configuration using EB tresos software. Prompts missing license. The software was downloaded from the official website and the lincense was sent to the email address. Re: EB tresos 提示missing license Hi. The EB Tresos download page provided by NXP will be updated with the activation code, if this activation code does not activate EB Tresos then it is recommended to email Flexnet Help Remind them to update. Click on S32K3 Standard Software - > Automotive SW - EB tresos Studio / AUTOSAR Configuration Tool to go to the EB Tresos download page. 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 Please open a new thread and refer to the closed one, if you have a related question at a later point in time. -------------------------------------------------------------------------------

configuration support for MIMX8ML8xxxLZ MIMX8ML8xxxLZ has only pin tool support, would it have clocks, peripheral support soon?

推出一款新的主机实用工具：RAPID BLHOST (RBLHOST) 什么是 Rapid Blhost（RBLHOST）？ RBLHOST 是一个命令行实用程序，提供 MCU 引导加载程序库，用于在主机计算机/处理器上通过 UART 和 I2C 向 NXP 微控制器发出命令。它的命令行界面与原始 blhost 工具兼容，用于图像编程。 它旨在为时间关键型应用提供高性能，并能够无缝集成到用 Python、C 或 Rust（本项目使用的核心语言）开发的系统中。有关 RBLHOST 的更多信息如下： Rapid Blhost (RBLHOST) 0.1.0： GitHub： https://github.com/nxp-mcuxpresso/rblhost 文档： https://crates.io/crates/rblhost 公告

S32K39-37-36 – eMIOS/BTCU/SAR-ADC/DMA – [RTD600] Abstract This example presents an use case for analogue data capturing using eMIOS, BCTU, SAR-ADC and DMA modules on S32K39-37-36 series based on the RTD low level API to support diverse application needs. Connections: S32K396-BGA-DC1 -> Pin -> Signal -> Label J62-1 -> PTC30 -> siul2_gpio_xx -> GPIO1_GPT (D0) J58-1 -> PTE14 -> emios_0_ch_19_z -> PWM1 J58-2 -> PTG9 -> siul2_gpio_xx -> GPIO2_eMIOS_Trigger J62-2 -> PTC31 -> siul2_gpio_xx -> GPIO3_BTCU_Trigger J62-4 -> PTD6 -> siul2_gpio_xx -> GPIO4_BTCU_Watermark J62-24 -> PTB14 -> adc1_s21 -> ADC1 *To use the potentiometer of S32X-MB connect: J62-24 (in S32K396-BGA-DC1) to P26-1 (in S32X-MB) Note: Following line should be added in project/generate/src/Bctu_Ip_PBcfg.c every time the code is updated in Config Tools: #define DMA_LOGIC_CH_0 ((uint8)0U) Detailed Description: The Compare Value of GPT eMIOS_0_ch_0 generates a time-out period. Once time-out is reached its Emios Notification toggles GPIO1. This allows us to observe in scope 2 events, which describe the start and the end of the signal sequence. The eMIOS_0_ch_23 channel is configured as global counter bus A. In this setup, it can act as the time base for other eMIOS_0 channels, enabling synchronization between other them—there is just one PWM in this case. This synchronization ensures that channels share the same time base, thereby defining a common period for their operation. The emios_0_ch_19_g channel is configured as OPWMT mode, which offer more flexibility for triggering. An interrupt is requested on every flag event, during which GPIO2 is toggled—happens at half the time high in this case. This flag event, can be configured using Trigger parameter. For more details about eMIOS, please refer to S32M27x/S32K3 – eMIOS Usage, considering differences for porting from S32K3 to S32K39-37-36 in AN14301. The BCTU implements a list for parallel conversions using ADC0 and ADC1. Which is triggered by the eMIOS channel, and the resulting data is stored in FIFO1, as follows: ADC0: VREFH_ChanNum51 -> BANDGAP_ChanNum48 ADC1: VREFL_ChanNum50 -> S21_ChanNum45 For debugging purposed the GPIO3 is toggled every BCTU Trigger Notification. Additionally, the GPIO4 is toggled in BCTU Watermark Notification, which happens every time the number of active entries in FIFO exceeds the watermark level, and therefore the data is available for reading. See full signal sequence in Figure 1: Figure 1. Signals of example project When you suspend debug session, in Expressions tab (Figure 2) you can observe results: g_fifo1Result, which corresponds to the BCTU list measurements, meanwhile g_fifo1Volts corresponds to the conversion in volts. Figure 2. Expressions tab of example project   References S32 Design Studio for S32 Platform Real-Time Drivers (RTD) S32K39, S32K37 and S32K36 Data Sheet [S32K39-S32K37-DS] S32K39, S32K37, and S32K36 Reference Manual [S32K396RM] S32K344 to S32K39/S32K37 Migration Guide [AN14301] S32K39/37/36 Electrification Microcontrollers Evaluation Board [S32K396-BGA-DC1] S32X-MB I/O Extension Evaluation Board for Real-Time Domain Control and Actuation [S32X-MB] S32M27x/S32K3 – eMIOS Usage [S32M Knowledge Base] S32M27x/S32K3 – eMIOS/BTCU/ADC/DMA – [RTD600] [S32M Knowledge Base] S32K39-37-36 – eFlexPWM/TRGMUX/BCTU/SAR-ADC/DMA – [RTD600] [S32M Knowledge Base] Application Software: - S32K396_RTD600_eMIOS_BCTU_SARADC_DMA_Ip_example Example was built and tested using the following IDE and Driver versions: - S32 Design Studio for S32 Platform Version 3.6.3 - S32K3_S32M27x Real-Time Drivers ASR R21-11 Version 6.0.0