RT1170 EVKB Dual-Core Example: CM7 Hangs at Startup Hi everyone, I have just started working with the RT1170 EVKB board and am trying to run the multicore Hello World example located in: boards/evkbmimxrt1170/multicore_examples/hello_world I am using the MCUXpresso SDK v26.03.00 (latest available version). When I load the multicore example, the CM7 core hangs during startup, while the debugger shows that the CM4 core is running. The CM7 never reaches `main()`. The fault status registers are: To rule out an issue with the multicore example, I also tried running the standalone CM7 Hello World example, but it exhibits the same behavior. However, the standalone CM4 Hello World example runs correctly. The board is an RT1170 EVKB with the default jumper and DIP switch settings, and I have not modified any hardware configuration. Has anyone encountered this issue with SDK 26.03.00 or the RT1170 EVKB? Is there any additional board configuration, boot setting, or debugger configuration required for the CM7 core? I also tested the previous SDK version (v2.13.0), but I observed the same issue with the CM7 core. Any suggestions would be greatly appreciated. Thank you! Re: RT1170 EVKB Dual-Core Example: CM7 Hangs at Startup Hi @FranklinOmo, Could you please share the schematic revision of your board? Additionally, to help simplify the review, could you send us a photo of the board? Best Regards, Pablo Re: RT1170 EVKB Dual-Core Example: CM7 Hangs at Startup Hi @Pablo_Ramos  Here is an image of the board for your reference.. Re: RT1170 EVKB Dual-Core Example: CM7 Hangs at Startup Hi @FranklinOmo, Thanks for the picture of the board. Could you help me perform a mass erase of the board? You can find the steps for performing a mass erase using the SPT in the following document: RT board recovery for debugger connect issues Could you also help me test by updating the firmware? Instructions for updating the firmware can be found in Section 2.11, "On-board Debugger," of the MIMXRT1170-EVKB Board Hardware User Guide. Have you been able to successfully program and run a CM7 application before, or has this behavior been present since the board was first taken out of the box? If the problem persists, could you also try programming the device using the GUI Flash Tool or SPT? Best Regards, Pablo

Question about S32 Safety Software Framework (SAF) and Safety Peripheral Drivers (SPD) 1. Does the Safety Peripheral Drivers *replace* the real time driver or augments it? 2. Are both of these (or one or none) are provided in source form? 3. Is there any per-unit royalty when the source is included in shipping firmware? 4. Is the licensing per dev kit/per user/reference counted in some other way or is it unlimited use within the organization once purchased? 5. Do these come with any kind of safety certification? Best regards Durga Choudhury Re: Question about S32 Safety Software Framework (SAF) and Safety Peripheral Drivers (SPD) Hi Durga Choudhury, 1. Augments/complements RTD. The SPD Product Brief and SAF Product Brief mentions “complements the S32 Real Time Drivers (RTD)” to cover safety-related on-chip peripherals, and other NXP material says SPD SAF requires/targets specific compatible RTD packages rather than replacing them. 2. Yes. The S32K3 SAF DELIVERABLES list  “Source code, User manuals, SAF demo application,” and the S32K3 SPD Deliverables similarly list “Source code, User manuals, SPD demo application.” 3.4. Please communicate with your chosen distributor.  5. They come with functional-safety process compliance and safety collateral, not automatic certification of your ECU/system. SAF is described as ISO 26262 functional-safety compliant, developed as SEooC, and usable for integration up to ASIL D;  SPD material similarly says ISO 26262 functional-safety compliance up to ASIL D. Safety packages contain SAF Safety Manual, Safety Analysis FMEA, Fault Coverage Estimation. When downloading SAF/SPD, you can download something like SW32K3_SPD_1.0.6_SafetyPack.zip. Best Regards, Robin Re: Question about S32 Safety Software Framework (SAF) and Safety Peripheral Drivers (SPD) Hello @Robin_Shen  Thanks for the clarification. On topics 3 &4: We are a United States based company. So we buy the licenses (if we decide to do so) from a distributor? I tried the Digikey site and it brings me back to your site on this topic. Can you please provide a specific contact information (such as a URL/email address etc)? Best regards Durga Choudhury Re: Question about S32 Safety Software Framework (SAF) and Safety Peripheral Drivers (SPD) SPD is free of charge. NXP no longer provides the SAF EVAL version. The FULL SAF version is now available also for development purposes only under NDA. The following is information I received from the internal team: Customers interested in obtaining the SAF license for development should go through their respective distributors. Distributors have direct contacts with NXP representatives, who can issue a quote to the customer. If the customer accepts the terms, the software can be provided.  Re: Question about S32 Safety Software Framework (SAF) and Safety Peripheral Drivers (SPD) Hello @Robin_Shen  Thanks for the update. My understanding, based on what you said, is: 1. We contact someone among the approved dealers (a specific contact would be helpful, e.g. an email) 2. We sign an NDA with them (or is it with NXP)? 3. We get the software free of charge (both the SAF and SPD) Can you please confirm if my understanding is correct? Best, Durga Is my Re: Question about S32 Safety Software Framework (SAF) and Safety Peripheral Drivers (SPD) Establish a confidentiality contract with NXP. Learn more about NDAs (FAQs). Request an NDA Please find the website of your local Distributor. Usually, there is a "Contact Us" button that will provide their phone number and email address. SPD is free of charge. The SAF webpage shows that the evaluation period for the "SW32K3M-SAF-D-L S32K3-S32M27x SAF Development Non-Production License (1 year)" is 1 year. Please contact the Distributor if you need to purchase a Production License. Re: Question about S32 Safety Software Framework (SAF) and Safety Peripheral Drivers (SPD) Thanks for your support.

LPC845 DMA 写入 GPIO 失败 LPC845 DMA 似乎无法写入 0xA0000000 的 GPIO 地址。 尝试进行 GPIO 写入时，出现 DMA0 -> ERRINT=1 错误。 作为故障排除步骤，我将目标地址更改为 RAM，并且没有收到 ERRINT 标志。 我还没有找到确凿的资料来证明这是否真的不可能。 我确实找到了一份资料，虽然并不确凿，但暗示情况可能如此： https://community.nxp.com/t5/LPC-Microcontrollers/Lpc-824-DMA-to-GPIO/mp/650903 请问有人可以确认一下吗？ Re: LPC845 DMA write to GPIO fails 你好@phatpaul 谢谢你的提问。 是的，LPC845 DMA 控制器不能直接写入地址为 0xA0000000 的 GPIO 寄存器空间。GPIO 外设通过 Cortex-M0+ I/O 总线连接，以实现 CPU 快速访问；而 DMA 控制器则通过 AHB/APB 总线基础设施访问存储器和支持的外设。 此外，LPC845 数据手册指出： “DMA 控制器可以访问所有存储器以及 USART、SPI、I2C、DAC 和电容式触摸。” GPIO 不在 DMA 可访问的外设列表中。因此，不支持向 GPIO 寄存器空间进行 DMA 传输，并且会产生传输错误 (ERRINT)，这与您观察到的行为一致。 谢谢！ BR 爱丽丝

SoC：i.MX8QXP（标记为 S1MX8QX5AVLF1BB）砖头 Re: SoC: i.MX8QXP (marked S1MX8QX5AVLF1BB)brick 嗨@Potesz 你的问题是什么？请提供更多关于您问题的详细信息。 BR

LPC1549 blink darn you, blink! I have the LPC1549 on its own board and I am trying to get familiar with MCUExpresso by using the periph_blinky example. It builds and flashes successfully. Since it is not on the development board, I need to reassign the LED pins. It is clear in the systick.c file where the LED pins are set: Board_LED_Set(0, false); Board_LED_Set(1, true); However, I can't find where the pins are defined. Where do I find where pins "0" and "1" are defined? I need to change them to PIO0_22 and PIO0_23. Thanks! Re: LPC1549 blink darn you, blink! Hi @DanielLongo  You can find it in board.c The default pins "0" and "1" are 25 3 If you want to change them to PIO0_22 and PIO0_23. You just need to change to #define MAXLEDS 3 static const uint8_t ledpins[MAXLEDS] = {22, 23, 1}; static const uint8_t ledports[MAXLEDS] = {0, 0, 1}; Hope this will help you. BR Harry

LPC1549 眨眼吧，该死的，眨眼吧！ 我有一块单独的电路板，上面安装了 LPC1549，我正在尝试通过使用 periph_blinky 示例来熟悉 MCUExpresso。编译和刷写均成功。由于它不在开发板上，我需要重新分配 LED 引脚。在systick.c文件中很清楚。设置LED引脚的文件： Board_LED_Set(0, false); Board_LED_Set(1, true ); 但是，我找不到引脚的定义位置。在哪里可以找到引脚“0”和“1”的定义？我需要将它们更改为 PIO0_22 和 PIO0_23。 谢谢您！ Re: LPC1549 blink darn you, blink! 嗨@DanielLongo 你可以在 board.c 文件中找到它。 默认引脚“0”和“1”为25 3 如果你想将它们更改为 PIO0_22 和 PIO0_23。 你只需要改成 #define MAXLEDS 3 static const uint8_t ledpins[MAXLEDS] = {22, 23, 1}; static const uint8_t ledports[MAXLEDS] = {0, 0, 1}; 希望这对您有所帮助。 BR 哈里

MRFG35010ANT1 こんにちは!このラベルやチップの刻印の真正性を確認していただけますか?この商品は2018年に販売終了となりました。うちの工場でこの材料コードが必要だったので、マーケットのサプライヤーからこのモデルを購入しました。しかし、偽物の購入を恐れているため、皆様のご協力をいただければ幸いです。 Re: MRFG35010ANT1 マーキング内容／手順については、データシートの20ページを参照してください。 データシートは製品ページでダウンロードできます:https://www.nxp.com/products/MRFG35010ANT1 以下の「偽造品防止ポリシー」をご覧ください。 リスクを最小限に抑えるため、お客様はNXP製品をNXPから直接購入するか、当社の正規販売代理店からのみ購入してください。 https://www.nxp.com/support/sample-and-buy/distributor-network%3ADISTRIBUTORS NXPは、保証サポート、故障解析、マーキングやトレースコードの検証など、無許可の購入に対するサポートを提供していません。 NXP偽造製品対策方針 https://www.nxp.com/company/about-nxp/quality:QUALITY_HOME

MC33774 PWR voltage reading HI. 我当前使用MC33774进行4个AFE自身的VAUX,VBAT,VDDC,VDDA的电压读取，我连续发送两条采集指令，中间间隔10ms，等待50ms后发送读取指令进行SECM寄存器的数据读取，但是奇怪的是虽然大多数情况下读取都是正确的，但是会偶尔出现所有的电压值都很小的情况，这是为什么？ Re: MC33774 PWR voltage reading 我当前使用的采样模式是APP模式，导致我在读取这些电压（PER模式）时出现转换异常，我修改采样模式后采集无异常。感谢你的帮助！ Re: MC33774 PWR voltage reading 你好 Embedded_novice 再会！ 我首先怀疑的是，SECM 电源电压结果在测量周期完全完成之前就被读取了，或者第二个采集命令在第一个结果集被锁存之前就重新启动了转换。这就解释了为什么四个电压通道同时变低，而通信本身仍然能够正常工作。 具体发送的是哪条采集指令？ AFE是否配置为周期模式？ 低值是同时出现在所有四个 AFE 上，还是只出现在菊花链中的一个设备上？ 您能否尝试增加采集指令之间的间隔？ 希望这些信息对您有所帮助，如果您还需要其他帮助，请告诉我。 祝你今天过得愉快，一切顺利。

LPC4078 重新调用 ISP 以启用 ISP 你好 适用于LPC4078微控制器 有一些功能代码、示例或应用说明，展示了（当微控制器设置为 CRP2 或 CRP3 时（仅在使用 CRP2 完成所有测试之后））如何重新调用 ISP 并允许重新启用 ISP UART 功能（使用 flash magic）。 顺祝商祺！ LPC40xx Re: LPC4078 reinvokeISP to enable ISP 你好@azzurrodante 很抱歉回复晚了。如果您还有任何疑问，请联系我们。 BR 爱丽丝

S32DS for PA v2.1 license is going to expire Hello, My S32DS for PA v2.1 license is going to expire. Please help extend the maintenance. Thanks a lot. 回复： S32DS for PA v2.1 license is going to expire Hello, the validity period of my entry here has not changed. Is it because I did something wrong in my operation? Re: S32DS for PA v2.1 license is going to expire Hi Zipeng, Go to the following link Power Architecture Development Tools | NXP Semiconductors Click Download. Login to your software account. The updated license key should appear here: Let me know if you encounter any issues. Thank you. Regards, Will Re: S32DS for PA v2.1 license is going to expire Hi Zipeng, Thanks for your feeback. I have forwarded your question to the FlexNet team. Once I receive a response, I will update you. Thank you! Regards, Will Re: S32DS for PA v2.1 license is going to expire The team shared this link. Please let me know if it does not work for you. How to extend my CodeWarrior Evaluation Software Regards, Will

I desperately need a demo of the S32K344 Ethernet port using FreeRTOS, without AUTOSAR, RTD 7.0.1, and S32 Platform 3.6.7. In S32 Platform 3.6.7, the FreeRTOS and LWIP settings for S32K344 are all AUTOSAR. I need a network interface demo that doesn't use AUTOSAR. There are too many settings in EB, and I don't know where to start. Thank you very much. Re: 跪求S32K344使用FreeRTOS的网口demo，不使用AUTOSAR，RTD 7.0.1 S32 Platform 3.6.7 Hi, Starting from TCP/IP Stack 2.0.0, the stack supports only the GMAC HLD driver interface. Therefore, there are no newer official lwIP demos that use purely Ethernet LLD (Low-Level Drivers). The available S32DS lwIP examples are based on the GMAC HLD layer and are intended as the recommended starting point for non-AUTOSAR applications. BR, Petr

FreeRTOSを使用し、AUTOSAR、RTD 7.0.1、およびS32 Platform 3.6.7を使用しないS32K344イーサネットポートのデモがどうしても必要です。 S32 Platform 3.6.7では、S32K344のFreeRTOSとLWIPの設定がすべてAUTOSARになっています。AUTOSARを使用しないネットワークインターフェースのデモが必要です。EBには設定項目が多すぎて、どこから手をつければいいのか分かりません。どうもありがとうございます。 Re: 跪求S32K344使用FreeRTOS的网口demo，不使用AUTOSAR，RTD 7.0.1 S32 Platform 3.6.7 こんにちは、 TCP/IPスタック2.0.0以降、スタックはGMAC HLDドライバインターフェースのみをサポートしています。したがって、純粋にイーサネットLLD(低レベルドライバー)のみを使用する新しい公式lwIPデモは存在しません。利用可能なS32DS lwIPの例はGMAC HLDレイヤーに基づいており、AUTOSAR以外のアプリケーションにおける推奨出発点として意図されています。 BR、ペトル

S32k144 EVBボードのエネルギーメーター 私はModbus RTUを使ってNXPのS32K144ボードとRS-485ベースのエネルギーメーターをインターフェースしようとしています。 S32K144をModbusマスターとして使用 Modbusスレーブとしてのエネルギーメーター(RS-485) テスト用USBからRS485へのコンバーター S32 Design Studio(デバッグ用のリアルタイム表現) RS-485信号(A/B、DE/RE)をS32K144とエネルギーメーターの間にどう接続すればよいでしょうか? S32K144でRS-485 Modbus通信用のUART/SCIを設定する方法は？ デバッガーやリアルタイム式を使ってModbusのデータ転送をリアルタイムでどのように検証できますか? エネルギーメーターはUSB-RS485経由でPCのModbusツールで正しく動作しますが、S32K144上で実装やデバッグの指導が必要です。 Re: Energy meter on S32k144 EVB board こんにちは、 @Turtledove S32K144 EVBにはネイティブのRS-485トランシーバが搭載されていないため、MCU UARTとエネルギーメーターの間に外部RS-485 PHY(例:MAX3485、SN65HVDシリーズなど)が必要です。UART TX/RXをS32K144からトランシーバーのDI/ROピンに接続し、トランシーバーA/B差動ペアをメーターのA/Bラインに接続します。DEと\REはGPIOによって駆動可能で(多くの場合、半二重Modbus RTU動作のために連結されています)。 ソフトウェアでは、メーター設定(通常9600/19200ボー、8ビットデータ、パリティなし、メーター仕様によってパリティなし、ストップビット1ビット)をLPUARTインスタンスのいずれかに設定してください。Modbusフレームを送信する前に、DEを主張し、フレームを送信し、送信が完了するまで待機し、DEを解除して受信モードに戻ります。Modbus RTU自体はUARTドライバの上にソフトウェアで実装されています。 デバッグを行うには、まずオシロスコープまたはロジックアナライザを使用してUARTトラフィックを確認してください。また、S32 Design Studioではウォッチ変数やリアルタイム式を使って送信リクエスト、受信応答、CRCの状態、デコードされたレジスタ値を監視することも可能です。リアルタイム式はアプリケーション変数を表示することはできますが、バス上のModbusフレームを直接デコードすることはできません。 よろしくお願いいたします。 ルーカス

SPDT Limit switch interfacing with S32k144 board I am interfacing an SPDT limit switch ME8112 with the S32K144 board. The code runs, but I am not seeing any value change in the real-time expression window. I am unsure if this is a hardware connection issue or a GPIO configuration problem. Could anyone suggest possible causes or debugging steps? Re: SPDT Limit switch interfacing with S32k144 board Hi@Turtledove In your program, the variables you defined are temporary variables. You could try defining them as global variables and then try again.

S32N55 HSE2 CRS domain authentication does not complete Hello, We are implementing HSE2-based Secure Debug on S32N55 using the SDC-600 debug authentication flow (challenge/response, APP mode, AES-256-CMAC), driven from a T32 CMM host script talking to SDC-600 over the debug port. **Status** - **FSS domain**: Secure Debug authentication completes successfully. Debug target `0x1A` (FSS) returns `AUTHSTATUS = 0xBBB` after the challenge/response exchange, confirming the domain is unlocked. - **CRS domain**: Authentication does not complete. We use debug target `0x1B` for CRS (assumed, pending confirmation from the HSE2 FW Reference Manual — see question 1 below). **Observed behavior for CRS** 1. SDC-600 COMM_START and SoC Info exchange complete normally. 2. AUTH_MODE_REQ to target `0x1B` returns `AUTH_MODE = 0x0` (challenge-based), as expected. 3. APP_CHALLENGE request completes; a 32-byte challenge is received from the FW. 4. We compute the response as AES-256-CMAC over the challenge using the ADKP, and send the 16-byte `appChallengeAuth` response. This transmission completes without a transport-level error. 5. **At this point, the FW never sends `RxRESULT`.** The host script stalls waiting for the response in `rx_response_from_fw` — no `0xF2` (fail) and no ACK pattern, just no reply at all. This is different from a clean failure; it looks like the FW never reaches the point of generating a response for this request. **Our current hypothesis** On the FSS side, we call `Sherpa_Cdd_SetOwnerDebugKeyMap()` once to register the OTP ADKP as the owner authorization/authentication key (`HSE_SRV_ID_DEBUG_KEY_MAPPING`). We suspect this mapping is only being applied in the context of the MU channel that call happens to be dispatched on, and is not visible to the CRS-side HSE2 instance — which would explain why CARD_REQUEST for CRS stalls instead of returning an explicit failure. **Questions** 1. What is the correct debug target / domain ID value for the CRS domain in `AUTH_MODE_REQ` and `CARD_REQUEST`? We are currently assuming `0x1B`; please confirm or correct. 2. Is `Sherpa_Cdd_SetOwnerDebugKeyMap()` (`HSE_SRV_ID_DEBUG_KEY_MAPPING`) required to be issued per-domain/per-MU, or is there a single global mapping shared across FSS and CRS? If per-domain, how is the target MU/owner selected for this service? 3. Does `SetOwnerDebugKeyMap` need to be called on every boot, or is the mapping persistent once set (e.g. tied to OTP/NVM state) so it only needs to be called once? 4. What OID value(s) are expected for the CRS domain in `CARD_REQUEST`? We are currently sending all-`0xFF` (16 bytes), mirroring what works for FSS. 5. What is the expected `CARD_REQUEST` packet structure (`hseDebugCardCmd_t`) for the CRS domain specifically — are there differences from the FSS/APP domain layout in `KRI`, `OID`, `AuthScheme`, or the debug-domain signal map field? 6. How should the Authentication Tag in `CARD_REQUEST` be computed for CRS — is it CMAC over the same `debugCardInfo` fields as for FSS, or does CRS require different fields to be included? Any pointers on the expected sequence/values for the CRS domain would be very helpful — happy to share our CMM script and captured SDC-600 byte log if useful. Thank you. Re: S32N55 HSE2 CRS domain authentication does not complete Hello, @EddiePark  Thanks for your post. We have initiated discussion with internal teams for your previous 9 questions listed, it is still under investigation, I would reply soon while there are any updates. For the new questions listed, I will check it first referencing with the previous questions, and then start to investigate on them one by one. BR Chenyin 

MC33774 PWR voltage reading HI. I am currently using the MC33774 to read the voltages of the four AFEs: VAUX, VBAT, VDDC, and VDDA. I send two acquisition commands consecutively with a 10ms interval in between, and then send a read command after a 50ms wait to read the data from the SECM register. However, strangely, although the reads are correct most of the time, there are occasional cases where all the voltage values are very low. Why is this? Re: MC33774 PWR voltage reading My current sampling mode is APP mode, which caused a conversion error when reading these voltages (PER mode). After changing the sampling mode, the data acquisition is normal. Thank you for your help! Re: MC33774 PWR voltage reading Hello Embedded_novice Good day! My first suspicion would be that the SECM supply-voltage results are being read before the measurement cycle has completely finished, or that the second acquisition command is restarting the conversion before the first result set is latched. This would explain why all four voltage channels become low together while communication itself remains functional. Which acquisition command is being sent exactly? Are the AFEs configured in periodic mode? Do the low values occur on all four AFEs simultaneously, or only on one device in the daisy chain? Can you try increasing the interval between acquisition commands? I hope this information has helped you, please let me know if you need help with anything else. Have a great day and best of luck.

MPC8313CVRAFFC 的替换/替代方案请求 您好， 请问能否推荐一款可以替代您产品编号为 MPC8313CVRAFFC 的型号？ 谢谢。 Re: Replacement/Alternative request for MPC8313CVRAFFC 最后一次购买

MPC8313CVRAFFCの交換/代替品リクエスト こんにちは、 PNのおすすめの代替品や代替品を教えてもらえますか?MPC8313CVRAFFC。 ありがとうございます。 Re: Replacement/Alternative request for MPC8313CVRAFFC 前回購入

MC33774 PWR電圧測定値 こんにちは。 現在、MC33774を使用して、VAUX、VBAT、VDDC、VDDAの4つのAFEの電圧を読み取っています。10ms間隔で2つの取得コマンドを連続して送信し、50ms待機してから読み取りコマンドを送信してSECMレジスタからデータを読み取ります。しかし、ほとんどの場合読み取りは正しいのですが、まれにすべての電圧値が非常に低くなることがあります。これはなぜでしょうか？ Re: MC33774 PWR voltage reading 現在使用しているサンプリングモードはAPPモードですが、このモードでは電圧（PERモード）を読み取る際に変換エラーが発生していました。サンプリングモードを変更したところ、データ取得が正常に行われるようになりました。ご協力ありがとうございました！ Re: MC33774 PWR voltage reading こんにちは、Embedded_noviceさん 良い一日！ 私が最初に疑うのは、SECMの電源電圧の結果が測定サイクルが完全に終了する前に読み取られているか、あるいは最初の結果セットがラッチされる前に2番目の取得コマンドによって変換が再開されているかのどちらかです。これが、通信自体は機能し続けるのに4つの電圧チャネルが同時に低くなる理由を説明できます。 具体的にどの取得コマンドが送信されているのですか？ AFEは定期モードに設定されていますか？ 低い値は、4つのAFEすべてで同時に発生しますか、それともデイジーチェーン内の1つのデバイスのみで発生しますか？ 獲得コマンドの間隔を伸ばしてみることはできますか? この情報がお役に立てば幸いです。他に何かご不明な点がありましたら、お気軽にお問い合わせください。 良い一日をお過ごしください。幸運を祈ります。

SPDT限位开关与S32k144板接口 我正在将 SPDT 限位开关 ME8112 与 S32K144 板连接。代码运行正常，但我没有在实时表达式窗口中看到任何值变化。 我不确定这是硬件连接问题还是GPIO配置问题。 请问有人能指出可能的原因或提供一些调试步骤吗？ Re: SPDT Limit switch interfacing with S32k144 board 您好@ Turtledove 在你的程序中，你定义的变量是临时变量。您可以尝试将它们定义为全局变量，然后再试一次。