Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
安全配置工具 - 版本镜像错误 您好,我正在尝试使用 SPT 对代码包,软件包进行签名。 我有一个包含 FCFB + DCD + IVT + app.bin 的二进制文件(一个完整的可启动映像),当我尝试对其进行签名时,签名成功了。 但是,当我选择一个只包含 IVT 和 app.bin 的二进制时,为什么“版本映像”选项被禁用?我已经附上了屏幕截图。 Re: Secure Provisioning Tool - Build image error 我已经附上了图片。请检查 Re: Secure Provisioning Tool - Build image error 你好@Abhay2080 , 请问您使用的是哪个版本的安全配置工具? 此外,我无法看到您在附件中提到的图片。请您再尝试上传一次好吗? 此致, 巴勃罗 Re: Secure Provisioning Tool - Build image error 你好@Abhay2080 , 我使用您分享的二进制文件对 Secure Provisioning Tool v26.09 进行了一些测试,并注意到以下情况: 根据《安全配置工具用户指南 v26.09》第 5.2.2 节“源映像格式”,可以明确指定 S19 文件的入口点。对于其他图像格式,入口点是从中断向量表中检索的(因此中断向量表必须位于应用程序映像的开头)。 对于没有 IVT 和 FCFB 的图像,该工具检测到入口点位于 0x601006C9,该点超出应用程序代码范围。此外,起始地址应在 0x600D2D01 到 0x601006C9 的范围内。 安全配置工具在应用程序映像中定位到偏移量为 0x4 的入口点。 请您测试一下,将入口点更改为有效地址后,是否可以成功构建镜像? 此致, 巴勃罗 Re: Secure Provisioning Tool - Build image error 是的,成功了……谢谢。
View full article
Secure Provisioning Tool - Build image error Hi i am trying to sign a package using SPT. I have one binary that have FCFB + DCD + IVT + app.bin (a complete bootable image) and when i tried to sign it it is succesfull. But when i am selecting a binary that only have IVT and app.bin why Build Image is disabled ?? I have attached the screen shot also. Re: Secure Provisioning Tool - Build image error I have attached the image now. Please check Re: Secure Provisioning Tool - Build image error Hi @Abhay2080, Could you share which version of the Secure Provisioning Tool you are using? Additionally, I'm unable to see the image you mentioned in your attachment. Could you please try uploading it again? Best Regards, Pablo Re: Secure Provisioning Tool - Build image error Hi @Abhay2080, I ran some tests with Secure Provisioning Tool v26.09 using the binary you shared and noticed the following: According to Section 5.2.2, Source Image Formats of the Secure Provisioning Tool User Guide v26.09 the entry point can be specified explicitly for S19 files. For other image formats, the entry point is retrieved from the interrupt vector table (so the interrupt vector table must be at the beginning of the application image). In the case of the image without an IVT and FCFB, the tool detects the entry point at 0x601006C9, which is outside the application code range. Additionally, the start address is expected to be within the range 0x600D2D01 to 0x601006C9. Secure Provisioning Tool locates the entry point at offset 0x4 within the application image. Could you please test whether changing the entry point to a valid address allows you to build the image successfully? Best Regards, Pablo Re: Secure Provisioning Tool - Build image error Yes it worked ..Thankyou
View full article
cst は古い OpenSSL を使用して無効な RSA-PSS 署名を作成する OpenSSL 3.1未満でcstを使用する場合、PSS署名で使用されるソルトが長すぎます。i.MX91のようなプロセッサはソルトの長さがダイジェストと同じであることを期待していますが、OpenSSL 3.1以前はデフォルトでソルトをできるだけ大きくするのが一般的でした。 しかし、新しいバージョンのOpenSSLであっても、デフォルト設定を使用するのは良くありません。なぜなら、署名検証時に短いソルトを受け入れてしまうからです。 解決策は、EVP_PKEY_CTX_set_rsa_pss_saltlen 関数を呼び出し、2 番目のパラメータを RSA_PSS_SALTLEN_DIGEST に設定することです。 なお、OpenSSL 3.0は先月からサポート終了となっています。 Security Re: cst creates invalid RSA-PSS signatures with old OpenSSL こんにちは、 ご連絡いただきありがとうございます。適切なチームに報告いたします。 よろしくお願いいたします。 アルド。
View full article
S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors Hello Community, I am currently working with the S32K344MINI-EVB (FRDM Automotive Evaluation Board) and would like to gain hands-on experience with basic peripheral drivers before starting development on a custom project based on the NXP S32K3 family. Development Environment S32 Design Studio (S32DS) 3.5.8 SW32K3_S32M27x_RTD_R21-11_4.0.0_P19_D2403 EB tresos 29 Current Status I successfully imported and ran the following example projects: SIUL2_DIO_IP_Example_S32K344 Dio_Example_S32K344 For both AUTOSAR and Non-AUTOSAR configurations, the projects built successfully and produced the expected output on the S32K344MINI-EVB. Issue I then imported the following CAN example projects: FlexCAN_IP_Example_S32K344 Can_Example_S32K344 While configuring and building these projects, I encountered the errors shown in the attached screenshot. Request Could anyone please advise: Are any board-specific modifications required for the S32K344MINI-EVB? Are there additional FlexCAN, clock, pin, or EB tresos configurations needed? Is there a guide for running these CAN examples on the MINI-EVB? The attached screenshot shows the errors encountered during configuration/build. Thank you for your support. Regards, Veer Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors Hello @Veereshh, Pinout is fairly similar between S32K344 EVB and FRDM-A-S32K344 (formerly S32K344MINI).  1. No 2. Yes. Both FlexCAN_IP_Example_S32K344 & Can_Example_S32K344 projects only configure FlexCAN in "loopback" mode, meaning there are no pins configured, and FlexCAN_0 is listening to its own messages.  Inside the project's MEX, you must: Change FlexCAN 'Loopback' to 'Normal/User mode' Add Siul2_Port (or Port in MCAL), and configure both PTA6 & PTA7 (CAN_H CAN_L in FRDM-A-S32K344). Add port initialization in your project. FRDM-A-S32K344 also uses TJA1043 CAN transceiver, which must set CAN_EN & CAN_STB to HIGH in order to set the transceiver in normal operation. These are routed to PTC21 & PTC20, as stated in the FRDM's user manual: These must be set to HIGH inside your project as well. You can use the following examples as reference: [RTD600 MCAL & IP] S32K3X4EVB-T172 FlexCAN Example Interrupt/Polling. Keep in mind they are based on RTD 6.0.0, not RTD 4.0.0. After setting this, you can use J15.1 CANH and J15.2 CANL connected to another CAN node (PCAN USB analyzer, another MCU, etc.) to test CAN communication. In the examples I've shared, PCAN-USB analyzer was used. Best regards, Julián Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors Hello  I'm glad the information has been helpful. In order to operate FlexCAN through interrupts, you must install the interrupt handler: Also, the error you are seeing is because when FlexCAN driver uses Polling mode, you must specify the CanMainFunctionRWPeriods for both read and write calls. If Interrupt mode is used, this container must be removed from "CanHardwareObjetc > Can MainFunction RW Period Reference" Best regards, Julián Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors Hi Julian, Thank you for your support. Your guidance helped me successfully resolve the original configuration issues and build the CAN example. I have shared the build steps and screenshots below for the benefit of other users facing the same issue.   I have one additional question. After successfully running the Loopback example, I configured CAN_EN (PTC21) and CAN_STB (PTC20) and then modified the CAN configuration as follows: Disabled Can Loop Back Mode Changed Can Rx Processing Type from Polling to Interrupt After these changes, validation/build errors are generated. Could you please advise if any additional FlexCAN, IntCtrl_Ip, NVIC, or RTD-specific settings are required when switching from Polling to Interrupt mode? Thank you again for your continued support. Steps to Build CAN Example Successfully Import Can_Example_S32K344 project. Open the .mex file. Enable Pins Tool if not already available. Rename Functional Group to PortContainer_0_VS_0. Configure: CAN0_RX → PTA6 CAN0_TX → PTA7 Add PORT module under MCAL.   Configure PortPin settings and assign the required MSCR values.  Update code and resolve validation errors. Generate code and build the project. Program the board and verify CAN Loopback communication. Best regards, Veer Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors Hello @Veereshh, CanIf (and all other interface AUTOSAR modules such as EthIf, WdgIf, LinIf, MemIf, among others) are delivered as "stub" modules, meaning that they are provided simply as a placeholder, and must be overwritten by the customer application, or by a third-party stack (such as Vector). In the posted examples, CanIf.c file was removed from build path, and CanIf APIs were declared inside main.c: /*======================================================================== * GLOBAL FUNCTIONS ==========================================================================*/ void CanIf_ControllerBusOff(uint8 ControllerId) { (void)ControllerId; } void CanIf_ControllerModeIndication(uint8 ControllerId, Can_ControllerStateType ControllerMode ) { (void)ControllerId; (void)ControllerMode; } extern void CanIf_TxConfirmation(PduIdType CanTxPduId) { (void)CanTxPduId; CanIf_bTxFlag = TRUE; } extern void CanIf_RxIndication( const Can_HwType * Mailbox, const PduInfoType * PduInfoPtr ) { (void)Mailbox; (void)PduInfoPtr; CanIf_bRxFlag = TRUE; } Can you try excluding CanIf.c from path and declaring the functions inside main?  Best regards, Julián Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors Hello @Veereshh, Good to know your project now builds successfully. The first disconnection issue seems to be regarding the UnTouchedPortPin container from the "Port" driver. In RTD 4.0.0 and below, the debugger pins must be included inside the UnTouchedPortPin container so that connection is maintained. From the PORT_UM.pdf: In order to be able to use the debug capabilities, the JTAG and Reset pins need to be configured in the Port driver using mechanism B. This means that the following pins/functionalities need to be added to the UnTouchedPortPin list: Reset_b having PortPin Mscr set to 5 and SIUL2 Instance set to SIUL2_0 JTAG_TMS having PortPin Mscr set to 4 and SIUL2 Instance set to SIUL2_0 JTAG_TDO having PortPin Mscr set to 10 and SIUL2 Instance set to SIUL2_0 JTAG_TCK having PortPin Mscr set to 68 and SIUL2 Instance set to SIUL2_0 JTAG_TDI having PortPin Mscr set to 69 and SIUL2 Instance set to SIUL2_0 Adding the following 4 pins is enough: 4 10 68 69 As for the Bus Heavy error message, it could be caused by many reasons. Can you check the following? CAN Bit Rate is the same between S32K3 and PCAN-USB (e.g. 500kbps and 75% sample point). CAN0_EN & CAN0_STB pins are set to HIGH, which enables TJA1043 CAN Transceiver on-board. Connections are correct between CAN0_OUT and PCAN-USB. Best regards, Julián Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors Hi @Julián_AragónM, Thank you for the clarification and continued support. Following your latest guidance, I: Installed the FlexCAN interrupt handlers in the Platform interrupt configuration. Removed the CanMainFunctionRWPeriods reference from CanHardwareObject > Can MainFunction RW Period Reference, as Interrupt mode is being used. Regenerated the code and the configuration completed successfully without validation errors. I also referred to the [RTD600 MCAL & IP] S32K3X4EVB-T172 FlexCAN Example Interrupt/Polling example that you shared and applied the equivalent settings to my RTD 4.0.0 P19 project. However, after the configuration was successfully generated, I encountered the following build/linker errors: Could you please advise whether any additional CanIf callback configuration or application-level implementation is required when enabling Interrupt mode in the AUTOSAR CAN example? Best regards, Veer Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors Hi Julián, Thank you for the explanation regarding the CanIf stub implementation. I followed your recommendation: excluded CanIf.c from the build path and declared the required CanIf callbacks in main.c. After making these changes, the project built successfully with 0 errors and 0 warnings.   I then started debugging step-by-step. The application now breaks during Port initialization, specifically at:   /* Initialize All UnUsed Port Pins */ Port_Ipw_Init_UnusedPins(pConfigPtr);   inside: static inline void Port_Ipw_Init_UnusedPins(...)   The debugger then broke at:   Break at address "0x0" with no debug information available, or outside of program code.   Additionally, PCAN-View reports a Bus Heavy condition. Could this indicate an issue with the Port configuration (unused pins configuration), interrupt configuration, or another missing initialization step? If needed, I can share the complete project for your review. Thank you for your continued support. Best regards, Veer
View full article
RW610:VIT v4.11.0がモデル初期化に成功したにもかかわらずINVALID_DEVICE戻る — ハードウェアID 0x00 こんにちは、チームのみなさん。 私はRW610 MCUを使ってカスタムボードに音声Intelligent Technology(VIT)を統合しています。モデルはロードされ、すべての初期化APIは成功しますが、VIT_Process()はVIT_INVALID_DEVICE(11)を返します。 下記のVITライブラリが私のRW610シリコンをサポートしているか、それとも別のライブラリリリースが必要なのか確認してもらえますか? アイテム構成 MCU カスタム基板上のNXP RW610 オーディオ・コーデック MAX98089 IDE MCUXpresso IDE - 24.12.0 RTOS FreeRTOS デバッグ出力 セミホスト型printf VITパッケージ リリース/24.12.00/CortexM33-RW61X 図書館 libVIT_CM33_RW61X_v04_11_00.a 実行時に報告されたライブラリバージョン 0x00040b00 — v4.11.0 VIT APIバージョン 0x00030400 実行時に報告されるモデルバージョン 0x00040b00 — v4.11.0 設定済みデバイス VIT_RW610 、数値9 動作モード VIT_WAKEWORD_ENABLE 図書館の情報源: https://github.com/nxp-mcuxpresso/VIT/tree/release/24.12.00/CortexM33-RW61X モデル生成: NXPのオンラインモデル生成ツールを使って、以下の設定で代替英語モデルを生成しました。 ポータルで選択されたデバイス:RW612 ポータルバージョン:24.12.00 ポータルにRW610のオプションが見当たらなかったので、RW612を選択しました。 生成されたVIT_Model_en.hはv4.11.0を宣言しています。現在、アプリケーションではウェイクワード認識のみが有効になっています。 VITの初期化シーケンスは次のとおりです。 1. VIT_GetLibInfo() 2. VIT_SetModel() 3. VIT_GetModelInfo() 4. VIT_GetMemoryTable() 5. 整列された静的に割り当てられたメモリ領域を割り当てる。 6. VIT_GetInstanceHandle() 7. VIT_ResetInstance() 8. VIT_SetControlParameters() 9. VIT_GetStatusParameters() 10. マイクのキャプチャを開始し、VIT_Process() を呼び出します。 リストに記載されたすべての初期化呼び出しは成功します。プロセッシングはエラー11を返します。 ランタイムログ: [VIT INFO] ボタンリクエスト: ENTER EXCLUSIVE VIT / START [VIT INFO] 排他モード:アプリケーションタスクの一時停止、スピーカー停止;VITの初期化 [VIT INFO] init: 英語モデル、ウェイクワードのみ;heap=37904 [VIT INFO] GetLibInfo OK [VIT INFO] ライブラリリリース=0x00040b00 API=0x00030400 features=0xe channels=1 requestedDevice=9 [VIT INFO] SetModel OK [VIT INFO] GetModelInfo OK [VIT INFO] VIT: 利用可能なウェイクワード: HEY NURSE [VIT INFO] GetMemoryTable OK [VIT INFO] メモリ領域 0 needs=135934 reserved=144460 bytes [VIT INFO] メモリ領域 1 needs=135894 reserved=157324 bytes [VIT INFO] メモリ領域 2 needs=8854 reserved=17644 bytes [VIT INFO] メモリ領域 3 needs=47079 reserved=49934 bytes [VIT INFO] GetInstanceHandle OK [VIT INFO] ResetInstance OK [VIT INFO] SetControlParameters OK [VIT INFO] GetStatusParameters OK [VIT INFO] インスタンス: library=0x00040b00 model=0x00040b00 selectedDevice=9 features=0x4 [VIT INFO] ResetInstance OK [VIT INFO] VIT: リスニング、PCM48kステレオチャネル 0 -> PCM16kモノラル [VIT ERROR] プロセス失敗: code=11 (INVALID_DEVICE); RED LED = VIT fault [VIT ERROR] RW61x 識別子: addr=0x45001114 raw=0x00007102 masked=0x00007100 libraryExpected=0x00007000 [VIT INFO] VIT: 停止 機器点検の観察 リンクされたライブラリのデバイス検証コードを調べたところ、デバイスID 9の場合、アドレス0x45001114を読み取り、下位8ビットをクリアし、その結果を0x00007000と比較していることがわかりました。 libVIT_CM33_RW61X_v04_11_00.aはアドレス0x45001114で0x00007102を返すRW610デバイスをサポートしていますか? 0x00007000との比較は、このリリースにおける既知の互換性の制限または問題ですか? このRW610には、どのVITライブラリのリリースとそれに対応するAPIヘッダーを使用すればよいですか? ポータルのRW612選択で生成されたモデルはRW610でサポートされていますか?それとも別のRW610モデル生成オプションが必要ですか? サポートされているライブラリ/モデルの組み合わせや、さらに必要な診断についてご助言ください。 ありがとう。
View full article
SPC563M64 JATG 通过 USB Multilink 进行无码传输 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 大家好。我在通过 USB Multilink 连接 SPC563M64 时遇到了一些问题。我的设备处于审查模式,配置为 0xAAAA_AAAA,序列号密码为 0x1122334455667788。我尝试用这个密码解锁设备,但无法连接。   在正常启动模式下,我可以通过 CAN(通过我的软件)读取完整的 Shadow 块的内容,所以我确定串口密码和配置字是正确的。但我无法解除设备的审查。   在串行启动模式下 {[1],[0]},我可以使用密码 0xFEEDFACECAFEBEEF 进入 CAN 启动模式,并且我可以通过禁用闪存访问(正如应该的那样)来访问 JTAG/NEXUS 而无需审查。电源、JTAG连接等都已正确连接。   电源稳定,RESET 电路通过 4K7 电阻上拉。我尝试使用相同的传感器配置连接 MPC5674,并且 JTAG 取消传感器通过,没有任何问题。   猜猜看? 概述 Re: SPC563M64 JATG uncensoring through USB Multilink 嗨@lukaszadrapa , 你知道那种感觉吗?当你遇到一个难题时,却发现有人在 10 年前也遇到过完全相同的问题! 🙂 我目前正在研究博世 MSE6.0 ECU 中的 SPC563M64,以及 C90LC Shadow Flash 和 JTAG/Nexus 审查。 你最终把所有问题都解决了吗?我特别想了解你们是如何管理审查配置的,以及你们是否还有任何代码示例、文档或工具可以分享。 我还在考虑使用 TNM5000 进行 CFLASH 和 CSHADOW 访问。 即使过了这么多年,任何建议我都会非常感激! 谢谢! Re: SPC563M64 JATG uncensoring through USB Multilink <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您好, 我猜你用的是 CodeWarrior 2.10,对吧?我刚刚发现,CW2.10 中包含的 ICDPPCNEXUS 调试器无法解除设备的审查,因为驱动程序中存在一个错误。 作为替代方案,您需要使用 CodeWarrior 10.6,或者您可以从www.pemicro.com下载 PKGPPCNEXUS。 给您带来不便,敬请谅解。 此致, Lukas Re: SPC563M64 JATG uncensoring through USB Multilink <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 是的,我知道C90CL设备上的这个功能,我尝试使用密码0x5566778811223344,但没有成功。 更多信息:我可以通过MCU内部软件重写阴影区域,当我设置配置0x55AA_55AA时,一切正常——在无审查模式下可以完全访问Nexus。 我记得,在旧的 55XX 设备上进行 JTAG 取消审查是不可能的,但这个芯片有迪士尼禁止机制和 JTAG 审查 CTRL 寄存器。 Re: SPC563M64 JATG uncensoring through USB Multilink <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您好, 你试过更换密码吗?在 C90LC 闪存上,需要将密码交换为 0xCAFEBEEFFEEDFACE(而不是 0xFEEDFACECAFEBEEF)。您能试试吗?请告知结果。 此致, Lukas
View full article
SPC563M64 JATGのUSBマルチリンクによる検閲解除 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、みんな。SPC563M64をUSBマルチリンク経由で接続する際に問題が発生しています。私のデバイスは、構成0xAAAA_AAAA、シリアルパスワード0x1122334455667788で検閲モードになっています。このパスワードを使ってデバイスの検閲を解除しようとしましたが、接続できませんでした。   通常の起動モード{[0],[0]}では、ソフトウェアでCANを通じてシャドウブロックの内容を読み取ることができ、どのシリアルパスワードや設定ワードが正しいか確信できます。でもデバイスのアンセンサーはできません。   シリアルブートモード{[1],[0]}ではパスワード0xFEEDFACECAFEBEEFでCANブートモードにアクセスでき、JTAG/NEXUSアクセスも検閲なしでフラッシュアクセスをディアセイブ(あるべき状態)で行えます。つまり、電源やJTAG接続などは正しく行われているということです。   電源は安定しており、リセットは4.7kΩの抵抗器を介してプルアップされている。同じ検閲設定とJTAG検閲解除パスを使用してMPC5674を接続しようとしましたが、問題なく動作しました。   何か予想はありますか? 全般 Re: SPC563M64 JATG uncensoring through USB Multilink こんにちは、 @lukaszadrapa さん。 何か問題で悩んでいる時に、10年前に全く同じ問題を抱えていた人を見つけた時の気持ち、分かりますよね! 🙂 現在、Bosch MSE6.0 ECUに搭載されているSPC563M64を使用して、C90LCシャドウフラッシュとJTAG/Nexusによる検閲について調査しています。 最終的にすべて正常に動作するようになりましたか?特に検閲の設定をどのように管理したのか、そして共有できるコード例やドキュメント、ツールがあれば知りたいです。 また、CFLASHやCSHADOWのアクセスのTNM5000も検討しています。 長年経った今でも、どんなアドバイスでも大変ありがたく思います! ありがとう! Re: SPC563M64 JATG uncensoring through USB Multilink <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、 あなたはCodeWarrior 2.10を使っているんですよね?CW2.10に含まれているICDPPCNEXUSデバッガが、ドライバのバグでデバイスの検閲を解除できないことが最近分かりました。 回避策としてCodeWarrior 10.6を使うか、www.pemicro.com からPKGPPCNEXUSをダウンロードすることも可能です ご迷惑をおかけして申し訳ありません。 よろしくお願いいたします。 ルーカス Re: SPC563M64 JATG uncensoring through USB Multilink <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> はい、C90CLデバイスのこの機能については知っています。パスワードとして0x5566778811223344を試してみましたが、うまくいきませんでした。 追加情報として、内部のMCUソフトでシャドウエリアを書き換えられ、設定設定0x55AA_55AAすべて順調に進み、検閲なしモードでネクサスに完全にアクセスできます。 古い55XXデバイスではJTAGの検閲解除は不可能だったと記憶していますが、このチップにはDISNEXの抑制メカニズムとJTAG Censor CTRLレジスタがあります。 Re: SPC563M64 JATG uncensoring through USB Multilink <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、 パスワードを変更してみましたか?C90LCフラッシュでは、パスワードを0xFEEDFACECAFEBEEFの代わりに0xCAFEBEEFFEEDFACEに変更する必要があります。試してみてくれない?結果を教えてください。 よろしくお願いいたします。 ルーカス
View full article
SPC563M64 JATG uncensoring through USB Multilink Hi all. I have some trouble to connect SPC563M64 through USB Multilink. My device is in censored mode with configuration 0xAAAA_AAAA and serial password 0x1122334455667788. I try to uncensor device with this password, but have no connect.    In normal boot mode {[0],[0]} i can read contents of full Shadow block through CAN (by my software), so I'm sure what serial password and configuration word is correct. But i can't uncensor device.   In serial boot mode {[1],[0]} i can access CAN boot mode with password 0xFEEDFACECAFEBEEF and i have JTAG/NEXUS access without censoring with flash access diasabled (as it should be). So power, JTAG connections etc done right.     Power is stable, reset pulled up through 4K7 resistor. I tryed to connect MPC5674 with same censor configuration and JTAG uncensor pass with no troubles.   Any guess?  General Re: SPC563M64 JATG uncensoring through USB Multilink Hi @lukaszadrapa, You know how it is when you’re struggling with a problem and find someone who had exactly the same issue 10 years ago! 🙂 I’m currently working with the SPC563M64 in a Bosch MSE6.0 ECU, researching C90LC Shadow Flash and JTAG/Nexus censorship. Did you eventually get everything working? I’m particularly interested in how you managed the censorship configuration and whether you still have any code examples, documentation or tools you could share. I’m also considering the TNM5000 for CFLASH and CSHADOW access. Any advice would be greatly appreciated, even after all these years! Thanks! Re: SPC563M64 JATG uncensoring through USB Multilink Hi, I guess that you use CodeWarrior 2.10, right? I just found out that the the ICDPPCNEXUS debugger which is included in CW2.10 is not able to uncensor the device because there's a bug in drivers. As a workaround, it is necessary to use CodeWarrior 10.6 or you can download PKGPPCNEXUS from www.pemicro.com Sorry for inconvenience. Regards, Lukas Re: SPC563M64 JATG uncensoring through USB Multilink Yes, i know about this feature on C90CL devises, i tryed to use password as 0x5566778811223344, but not success.     More info: I can rewrite shadow area by internal MCU software, and when i sets up config 0x55AA_55AA all gone right - full nexus access in uncensored mode.     I remeber, what it impossible to do JTAG uncensor on old 55XX device, but this chip have DISNEX inhibit mechanism and JTAG Censor CTRL register. Re: SPC563M64 JATG uncensoring through USB Multilink Hi, have you tried to swap the password? On C90LC flash, it is necessary to swap the password like this 0xCAFEBEEFFEEDFACE (instead of 0xFEEDFACECAFEBEEF). Could you try that? Please let me know the result. Regards, Lukas
View full article
RT1170 QSPI Flash (MX25L51245G ) Hello, We are using the MX25L51245G external flash and RT1176 and have implemented the configuration shown below. It works flawlessly in XIP mode, but I would like to get a validation from you as well. However, when running a multicore application in "Link application mode", the system hits a hardfault. Specifically, it triggers an assert due to the value read from the FlexCAN MCR register. "I'm also getting various different errors, including HardFaults." I am attaching some screenshots and my lookup table below for your reference. M7 flash init(RAM): M4 flash init(RAM): hardfault for multicore(RAM): Here is the lookup table configuration designed to support the software running seamlessly in both RAM and XIP (Execute-in-Place) modes:   #define FLASH_DUMMY_CYCLES 0x08 const flexspi_nor_config_t qspiflash_config = { .memConfig = { .tag = FLEXSPI_CFG_BLK_TAG, .version = FLEXSPI_CFG_BLK_VERSION, .readSampleClksrc=kFlexSPIReadSampleClk_LoopbackFromDqsPad, .csHoldTime = 3u, .csSetupTime = 3u, .controllerMiscOption = 0x10, .deviceType = kFlexSpiDeviceType_SerialNOR, .sflashPadType = kSerialFlash_4Pads, .serialClkFreq = kFlexSpiSerialClk_133MHz, //okuma hatasi olursa kFlexSpiSerialClk_120MHz .sflashA1Size = 64u * 1024u * 1024u, //64MB //Her acilista QE = 1. ROM once WREN'i (seq 3) kendisi gonderir, sonra 4*12'yi 0x40 ile calistirir. //NXP RT1170 EVK'daki configCmd kalibinin aynisi .configCmdEnable = 1u, .configModeType[0] = kDeviceConfigCmdType_Generic, .configCmdSeqs[0] = {.seqNum = 1u, .seqId = 12u, .reserved = 0u}, //1 tane sequence calistir: 4*12 //asagiyi 0x20 yapinca calismadi dogrudan memory hatasinda patladi main'e gelmeden .configCmdArgs[0] = 0x40u, //WRITE_SDR'nin gonderecegi byte: SR = 0x40 .lookupTable = { [0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x6C, RADDR_SDR, FLEXSPI_1PAD, 0x20),//6Ch QREAD4B: komut ve 4 byte adres tek hattan (1-1-4) [1] = FLEXSPI_LUT_SEQ(DUMMY_SDR, FLEXSPI_4PAD, FLASH_DUMMY_CYCLES, READ_SDR, FLEXSPI_4PAD, 0x04),//8 dummy bekle, data 4 hattan [4 * 1 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x05, READ_SDR, FLEXSPI_1PAD, 0x04),//status regini 0x05'den okuyacam (WIP = bit0) [4 * 3 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x06, STOP, FLEXSPI_1PAD, 0x0),//write en ettim //asagidakini yoruma alinca gercekten silmedi [4 * 5 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x21, RADDR_SDR, FLEXSPI_1PAD, 0x20),//4 byte adress alarak 4 kb sector silecem [4 * 8 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xDC, RADDR_SDR, FLEXSPI_1PAD, 0x20),//64 kb block silecem(app'de kullanmiyoruz) [4 * 9 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x12, RADDR_SDR, FLEXSPI_1PAD, 0x20),//4 byte 1 page yazacam [4 * 9 + 1] = FLEXSPI_LUT_SEQ(WRITE_SDR, FLEXSPI_1PAD, 0x04, STOP, FLEXSPI_1PAD, 0x0),//datayi gonder ve bitir (WEL'i flash program bitince kendisi temizler) [4 * 11 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xC7, STOP, FLEXSPI_1PAD, 0x0),//tum flashi silecem(app'de kullanmiyoruz) [4 * 12 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x01, WRITE_SDR, FLEXSPI_1PAD, 0x01),//WRSR + tam 1 byte (configCmdArgs[0]): sadece SR yazilir, CR'ye dokunmaz //seq 6/7 bos: ROM API suspend/resume kullanmiyor }, }, .pageSize = 256u, .sectorSize = 4u * 1024u, .ipcmdSerialClkFreq = 0x1, .blockSize = 64u * 1024u, .isUniformBlockSize = true, }; Thanks for helping. i.MXRT
View full article
RTD 7.0.0 で生成された設定ファイル名の問題 こんにちは、チームの皆さん、 機能群名SEHS2を付けましたが、この名前は生成されたファイル名に現れ、RTD 7.0.0とDS 3.6.4を使用しています。 以前の6.0.0ではそうではありませんでした。 Re: generated Config file name issue for RTD 7.0.0 こんにちは、ダニエルさん。 依然として同じ問題が発生しています。 BR Re: generated Config file name issue for RTD 7.0.0 こんにちは、 @sbidkar さん、 これはグローバル設定で変更可能です: BR、ダニエル Re: generated Config file name issue for RTD 7.0.0 これで合っているはずです。 Re: generated Config file name issue for RTD 7.0.0 解決しました。ありがとうございました。 BR
View full article
S32K3X4EVB-T172: Lauterbach JTAG fails when on-board debugger USB (J41) is connected – how to use on Hello, I am using the S32K3X4EVB-T172 (Rev B) with a Lauterbach TRACE32 debugger on the JTAG connector. I would like to use the on-board debugger (J41) only as a USB virtual COM port to read LPUART6 logs (PTA15 = LPUART6_RX, PTA16 = LPUART6_TX, as listed in the HW User Manual), while debugging with TRACE32 at the same time. Problem: J41 not connected: TRACE32 connects normally (SYStem.Up OK). J41 connected: the virtual COM port appears in Windows, but TRACE32 reports "debug port fail". It looks like the on-board debugger is driving the JTAG/SWD and/or RESET lines of the S32K3. Questions: Is there a jumper or a set of resistors to isolate the on-board debugger from the MCU JTAG/SWD/RESET lines, while keeping the LPUART6 (PTA15/PTA16) connection to the on-board debugger? If resistors must be removed, which reference designators are they? The HW User Manual (Rev A3, 08/2024) only covers the TRACE isolation resistors (R192, R452, R190, R435, R511), not the on-board debugger. Is there a recommended configuration or firmware setting for the on-board debugger to stay passive (UART only) when an external debugger is used? Setup: Board: S32K3X4EVB-T172 Rev B, S32K314 Debugger: Lauterbach TRACE32 on the JTAG connector Software: S32DS 3.5, RTD 5.0.0 Thank you. Re: S32K3X4EVB-T172: Lauterbach JTAG fails when on-board debugger USB (J41) is connected – how to us Hello @EddiePark, You can see in sheet 7 of 13 that OpenSDA signals are connected through the following resistors R600 - JTAG_TCLK/SWD_CLK R591 - JTAG_TMS/SWD_DIO R588 - JTAG_TDI R246 - JTAG_TDO R239 - RESET_MCU You can depopulate these resistors, which will disable the on-board debugger, and will let you keep using PTA15/16 as UART output through the micro-USB connector. There is no recommended configuration or firmware setting for the on-board debugger to stay passive when an external debugger is used. Best regards, Julián
View full article
RTD 7.0.0 生成的配置文件名称问题 各位团队成员,大家好! 我已将功能组命名为 SEHS2,该名称出现在生成的文件名中,我正在使用 RTD 7.0.0 和 DS 3.6.4。 此前在 6.0.0 版本中并非如此。 Re: generated Config file name issue for RTD 7.0.0 问题已解决,谢谢。 BR Re: generated Config file name issue for RTD 7.0.0 你好,丹尼尔, 问题依旧存在。 BR Re: generated Config file name issue for RTD 7.0.0 应该就是这样了: Re: generated Config file name issue for RTD 7.0.0 你好@sbidkar , 这可以在全局设置中更改: BR,丹尼尔
View full article
NXP Kinetis KM35 Metering Libraries I am working on a metering application with the kinetis KM35 series, and I am having some trouble understanding the Low-power metering library. I have been using the application note AN13259 "Low-Power Real-Time Algorithm for Metering Applications." While trying to integrate this library, I have found that there are actually many versions of this library in addition to multiple versions of the digital-filter and FFT-based versions. The examples in the SDK (imported through MCUExpresso) seem to have versions of these libraries that I cannot even find. My questions is this: What is the best way to determine what version of the library to use? What is the best way to find the most up-to-date information about the LPRT metering library? Am I working form the most recent and up-to-date application notes (AN13259)? Kinetis M Series MCUs Re: NXP Kinetis KM35 Metering Libraries Hi, This got me where I needed to be. I was looking at an old application note about the low-power algorithm itself, AND I was using an older version of the library itself. It seems the library interface was majorly overhauled (and simplified!) since that note was relevant. Using the SDK provided version, and following the in-code documentation was the right way to go. -o7
View full article
NXP Kinetis KM35 メーター ライブラリ 私はKinetis KM35シリーズを使ったメーターアプリケーションを開発しており、低消費電力メーターライブラリの理解に少し苦労しています。私は「Low-Power Real-Time Algorithm for メーター Applications」AN13259アプリケーションノートを使っています。 このライブラリを統合しようとしたところ、デジタルフィルタ版とFFTベース版の複数のバージョンに加えて、このライブラリ自体にも多くのバージョンが存在することがわかりました。SDKの例(MCUExpresso経由でインポート)には、私が見つけられないバージョンのライブラリが含まれているようです。 私の質問は以下の通りです。 使用するライブラリのバージョンを判断する最良の方法は何ですか? LPRTメーターライブラリに関する最新の情報を見つける最良の方法は何でしょうか? 最新かつ最新のアプリケーションノート(AN13259)をもとに作業していますか? Kinetis Mシリーズ・マイクロコントローラ Re: NXP Kinetis KM35 Metering Libraries こんにちは、 これで私は目的の場所にたどり着けた。私は低消費電力アルゴリズム自体についての古いアプリケーションノートを見ていて、しかもライブラリ自体の古いバージョンを使っていました。そのメモが関係していたため、ライブラリのインターフェースは大幅に見直され(そして簡素化された!)ようです。 SDK版を使い、コード内のドキュメントに従うのが正しい方法でした。 -o7
View full article
generated Config file name issue for RTD 7.0.0 Hello Team, I have given functional group name SEHS2, this name is appearing in generated file names and I am using RTD 7.0.0 with DS 3.6.4. Previously for 6.0.0 this was not the case. Re: generated Config file name issue for RTD 7.0.0 Solved.Thanks.  BR Re: generated Config file name issue for RTD 7.0.0 Hello @sbidkar, This can be changed in the global settings: BR, Daniel Re: generated Config file name issue for RTD 7.0.0 Hello Daniel, Still the same issue. BR Re: generated Config file name issue for RTD 7.0.0 This should be it:
View full article
RT1170 QSPIフラッシュ(MX25L51245G) こんにちは、 弊社では、MX25L51245G外部フラッシュメモリとRT1176を使用しており、以下の構成を実装しています。XIPモードでは問題なく動作しますが、念のため貴社からも確認をいただきたいです。 しかし、「リンクアプリケーションモード」でマルチコアアプリケーションを実行すると、システムはハードフォールトに遭遇します。具体的には、FlexCAN MCRレジスタから読み取った値によってアサートが発生します。「ハードフォールトを含む、さまざまなエラーも発生しています。」 参考までに、スクリーンショットとルックアップテーブルを以下に添付します。 M7フラッシュ初期化(RAM): M4フラッシュ初期化(RAM): マルチコア(RAM)のハードフォルト: こちらはRAMモードとXIP(Execute-in-Place)モードの両方でシームレスに動作するソフトウェアをサポートするために設計されたルックアップテーブルの構成です:   #define FLASH_DUMMY_CYCLES 0x08 const flexspi_nor_config_t qspiflash_config = { .memConfig = { .tag = FLEXSPI_CFG_BLK_TAG 、 .version = FLEXSPI_CFG_BLK_VERSION、 .readSampleClksrc= kFlexSPIReadSampleClk_LoopbackFromDqsPad 、 .csHoldTime = 3u、 .csSetupTime = 3u、 .controllerMiscOption = 0x10、 .deviceType = kFlexSpiDeviceType_SerialNOR 、 .sflashPadType = kSerialFlash_4Pads、 .serialClkFreq = kFlexSpiSerialClk_133MHz , //オクマハタシオルルサkFlexSpiSerialClk_120MHz .sflashA1Size = 64u * 1024u * 1024u, //64MB //彼女のアシリスタQE = 1. ROM 1 回 WREN'i ( seq 3) kendisi gonderir 、 sonra 4*12' yi 0x40 ile calistirr 。 //NXP RT1170 EVK'daki configCmd kalibin aynisi .configCmdEnable = 1u、 .configModeType[0] = kDeviceConfigCmdType_Generic、 .configCmdSeqs[0] = {.seqNum = 1u, .seqId = 12u, .reserved = 0u}, //1 taneシーケンスcalistir : 4*12 // asagiyi 0x20ヤピンカカリスマディドグルダンメモリハタシンダパトラディメインエゲルメデン .configCmdArgs[0] = 0x40u, //WRITE_SDR'nin gonderecegi byte: SR = 0x40 .lookupTable = { [0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x6C, RADDR_SDR, FLEXSPI_1PAD, 0x20), //6Ch QREAD4B: komut ve 4 byte adres tek hattan (1-1-4) [1] = FLEXSPI_LUT_SEQ(DUMMY_SDR, FLEXSPI_4PAD, FLASH_DUMMY_CYCLES, READ_SDR, FLEXSPI_4PAD, 0x04), //8 ダミーベール、データ 4ハットン [4 * 1 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x05, READ_SDR, FLEXSPI_1PAD, 0x04), //ステータスregini 0x05'den okuyacam (WIP = bit0) [4 * 3 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x06, STOP, FLEXSPI_1PAD, 0x0), //書き込み完了 //アサギダキニヨルマアリンカゲルツェクテンシルメディ [4 * 5 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x21, RADDR_SDR, FLEXSPI_1PAD, 0x20), //4 バイトアドレスalarak 4 kbセクターsilecem [4 * 8 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xDC, RADDR_SDR, FLEXSPI_1PAD, 0x20)、 //64 kbブロック サイセム(アプリ デkullanmiyoruz ) [4 * 9 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x12, RADDR_SDR, FLEXSPI_1PAD, 0x20), //4バイト1ページyazacam [4 * 9 + 1] = FLEXSPI_LUT_SEQ(WRITE_SDR, FLEXSPI_1PAD, 0x04, STOP, FLEXSPI_1PAD, 0x0), // datayi gonder ve bitir (WEL'i フラッシュ プログラム ビットインスkendisi temizler ) [4 * 11 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xC7, STOP, FLEXSPI_1PAD, 0x0), // tum flashi silecem (app'de kullanmiyoruz ) [4 * 12 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x01, WRITE_SDR, FLEXSPI_1PAD, 0x01), //WRSR + tam 1 バイト (configCmdArgs[0]): sacece SR yazilir , CR'ye dokunmaz // seq 6/7 bos : ROM API サスペンド/レジュームkullanmiyor }、 }、 .pageSize = 256u、 .sectorSize = 4u * 1024u、 .ipcmdSerialClkFreq = 0x1、 .blockSize = 64u * 1024u、 .isUniformBlockSize = true、 }; 手伝ってくれてありがとう。 i.MX RT
View full article
RT1170 QSPI Flash (MX25L51245G) 你好, 我们使用 MX25L51245G 外置闪存和 RT1176,并实现了如下所示的配置。它在 XIP 模式下运行完美,但我也想得到您的验证。 但是,当在“链接应用程序模式”下运行多核应用程序时,系统会发生硬故障。具体来说,它由于从FlexCAN MCR寄存器读取的值而触发信号断言。“我还遇到了各种不同的错误,包括硬故障。” 下面附上一些截图和我的查找表供您参考,引用。 M7 闪存初始化(RAM): M4 闪存初始化(RAM): 多核(RAM)的硬故障: 以下是为支持软件在 RAM 和 XIP(就地执行)模式下无缝运行而设计的查找表配置:   #define FLASH_DUMMY_CYCLES 0x08 const flexspi_nor_config_t qspiflash_config = { .memConfig = { .tag = FLEXSPI_CFG_BLK_TAG , .version = FLEXSPI_CFG_BLK_VERSION, .readSampleClksrc= kFlexSPIReadSampleClk_LoopbackFromDqsPad , .csHoldTime = 3u, .csSetupTime = 3u, .controllerMiscOption = 0x10, .deviceType = kFlexSpiDeviceType_SerialNOR , .sflashPadType = kSerialFlash_4Pads, .serialClkFreq = kFlexSpiSerialClk_133MHz , // kFlexSpiSerialClk_120MHz​​ .sflashA1Size = 64u * 1024u * 1024u, //64MB //她的acilista QE = 1. ROM 一次 WREN'i ( seq 3) kendisi gonderir , sonra 4*12' yi 0x40 ile calistirir . //NXP RT1170 EVK'daki configCmd kalibinin aynisi .configCmdEnable = 1u, .configModeType[0] = kDeviceConfigCmdType_Generic, .configCmdSeqs[0] = {.seqNum = 1u, .seqId = 12u, .reserved = 0u}, //1 个序列calistir : 4*12 // asagiyi 0x20 yapinca calismadi Dogrudan内存hatasinda patladi main'e gelmeden .configCmdArgs[0] = 0x40u, //WRITE_SDR'nin gonderecegi 字节: SR = 0x40 .lookupTable = { [0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x6C, RADDR_SDR, FLEXSPI_1PAD, 0x20), //6Ch QREAD4B: komut ve 4 字节地址tek hattan (1-1-4) [1] = FLEXSPI_LUT_SEQ(DUMMY_SDR, FLEXSPI_4PAD, FLASH_DUMMY_CYCLES, READ_SDR, FLEXSPI_4PAD, 0x04), //8 虚拟bekle , 数据 4 hattan [4 * 1 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x05, READ_SDR, FLEXSPI_1PAD, 0x04), //状态寄存器0x05'den okuyacam (WIP = bit0) [4 * 3 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x06, STOP, FLEXSPI_1PAD, 0x0), //写入en ettim // asagidakini yoruma alinca gercekten silmedi [4 * 5 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x21, RADDR_SDR, FLEXSPI_1PAD, 0x20), //4 字节地址alarak 4 kb扇区silecem [4 * 8 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xDC, RADDR_SDR, FLEXSPI_1PAD, 0x20), //64 kb块silecem (app'de kullanmiyoruz ) [4 * 9 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x12, RADDR_SDR, FLEXSPI_1PAD, 0x20), //4 字节 1 页yazacam [4 * 9 + 1] = FLEXSPI_LUT_SEQ(WRITE_SDR, FLEXSPI_1PAD, 0x04, STOP, FLEXSPI_1PAD, 0x0), // datayi gonder ve bitir (WEL'i flash 程序bitince kendisi temizler ) [4 * 11 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xC7, STOP, FLEXSPI_1PAD, 0x0), //转flashi silecem (app'de kullanmiyoruz ) [4 * 12 + 0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x01, WRITE_SDR, FLEXSPI_1PAD, 0x01), //WRSR + tam 1 字节 (configCmdArgs[0]): sadece SR yazilir , CR'ye dokunmaz // seq 6/7 bos : ROM API 暂停/恢复kullanmiyor }, }, .pageSize = 256u, .sectorSize = 4u * 1024u, .ipcmdSerialClkFreq = 0x1, .blockSize = 64u * 1024u, .isUniformBlockSize = true, }; 谢谢你的帮助。 i.MXRT
View full article
NXP Kinetis KM35 计量库 我正在使用 Kinetis KM35 系列开发一个计量应用程序,但我对低功耗计量库的理解遇到了一些困难。我一直在使用应用笔记 AN13259《用于计量应用的低功耗实时算法》。 在尝试集成这个库的过程中,我发现除了数字滤波器和基于 FFT 的版本之外,这个库实际上还有许多版本。SDK 中的示例(通过 MCUExpresso 导入)似乎包含我根本找不到的这些库的版本。 我的问题是: 确定使用哪个版本的库的最佳方法是什么? 如何才能找到有关 LPRT 计量库的最新信息? 我使用的是最新版的应用笔记(AN13259)吗? Kinetis M系列MCU Re: NXP Kinetis KM35 Metering Libraries 您好, 这让我达到了我的目标。我当时正在查看一份关于低功耗算法本身的旧应用笔记,而且我使用的还是旧版本的库。自那条说明发布以来,图书馆界面似乎已经进行了重大改版(并简化了!)。 使用 SDK 提供的版本,并遵循代码中的文档说明,才是正确的做法。 -o7
View full article
MC33FS6523CAE SBC Thermal Shutdown Occurs at Higher Temperature Than Expected I'm using the NXP MC33FS6523CAE SBC module in our VCU application. We are measuring the SBC die temperature through the AMUX / MUX_OUT output. As per our understanding from the datasheet, the SBC is expected to enter thermal shutdown at approximately 160 deg C. To validate this behavior, we increased the SBC temperature and monitored the AMUX temperature output. However, the SBC did not shut down around 160 deg C. Instead, shutdown occurred only after the measured temperature reached approximately 202 deg C. We also validated the AMUX output by directly measuring the Battery voltage, and the voltage measurement appears accurate. Could you please clarify: Is shutdown around 202 deg C expected behavior for MC33FS6523CAE? What is the exact thermal shutdown threshold and tolerance for this part? Is the AMUX die-temperature output intended to correspond directly to the shutdown temperature threshold? Are there any configuration bits, operating modes, or regulator-specific thermal shutdown behaviors that could explain this difference? Device NXP SBC: MC33FS6523CAE Re: MC33FS6523CAE SBC Thermal Shutdown Occurs at Higher Temperature Than Expected Hi Bharath, Thank you for the follow-up questions. Please find my answers below. 1. There is no direct access to the per-regulator TSD sensor values via SPI or AMUX. The only way to get a meaningful per-regulator thermal indicator is through the thermal warning flags (TWARN), which fire at a typical threshold of ~125 °C, well before TSD (~160 °C min). When TWARN_PRE, TWARN_CORE or TWARN_CCA is set, it indicates that the local temperature near that specific regulator's pass transistor is approaching the shutdown region. This is the most useful in-circuit early warning available. 2. The following approach is possible: - Load only the regulator under test at its target operating current (VCORE at 2.2 A for MC33FS6523, for example) to focus heat dissipation on that regulator's pass transistor. - Ramp ambient temperature slowly while polling the DIAG registers via SPI. - The TWARN flag for that regulator will set first (~125 °C typical), confirming the sensor is active and giving you a reference point. - Continue the ramp; TSD will assert and the regulator output will drop to zero. Record the AMUX die temperature reading at that moment as an approximate reference only. - The TSD is auto-recovering: the regulator restarts automatically once the junction temperature falls below TSD − hysteresis (~10 °C typical), so you can repeat the cycle. 3. Poll the following SPI registers during your thermal ramp: 4. The AMUX temperature is a general die sensor and cannot be used to validate or predict the TSD trip point for any specific regulator. For TSD validation, the only reliable indicators are the TSD flags in the DIAG registers and the observable dropout of the affected regulator's output voltage. BRs, Tomas Re: MC33FS6523CAE SBC Thermal Shutdown Occurs at Higher Temperature Than Expected Hi @TomasVaverka , Thank you for the clarification. Understood that the AMUX/MUX_OUT temperature is from an internal die temperature sensor and is not the same temperature used by the local thermal shutdown circuits of VPRE, VCORE, VCCA, VAUX, and CAN_5V. Could you please advise the recommended method to validate the thermal shutdown threshold for each regulator block? Specifically: 1. Is there any way to read or estimate the local temperature near the regulator thermal shutdown sensors? 2. Is there a recommended test setup or procedure from NXP to validate the 160°C minimum shutdown threshold? 3. During thermal testing, should we monitor any specific diagnostic/status registers to confirm which regulator block triggered thermal shutdown? 4. Can the AMUX/MUX_OUT die temperature be used only as an approximate reference, not as the shutdown validation temperature? In our current test, the AMUX/MUX_OUT temperature reading reached around 202°C before shutdown occurred, and we also validated the MUX_OUT voltage externally. We would like to confirm the correct validation method for this threshold. Best regards, Bharath Re: MC33FS6523CAE SBC Thermal Shutdown Occurs at Higher Temperature Than Expected Hi Bharath, The thermal shutdown threshold of the MC33FS6523CAE regulators is specified as 160°C (minimum) and is implemented locally for each regulator block (VPRE, VCORE, VCCA, VAUX and CAN_5V). Please note that the temperature available through the AMUX/MUX_OUT pin is generated by an internal die temperature sensor and is not necessarily the same temperature used by the individual thermal shutdown circuits. The regulators are protected by dedicated thermal sensors located near their power devices. Therefore, the temperature reported through MUX_OUT differs from the temperature used internally for thermal shutdown decisions. BRs, Tomas
View full article
MC33FS6523CAE 单板计算机过热关机发生在高于预期温度的情况下 我在整车控制器VCU应用中使用的是NXP MC33FS6523CAE SBC模块。我们通过 AMUX/MUX_OUT 输出 测量SBC芯片的温度 。 根据数据手册,该单板计算机预计在约160 摄氏度时进入过热关机状态。为了验证这一特性,我们提高了单板计算机的温度并监测了 AMUX 的温度输出。 然而,SBC 并没有在160 摄氏度左右关机。相反,它仅在测量温度达到约202 摄氏度后才关机。 我们还通过直接测量电池电压验证了 AMUX 输出,电压测量结果似乎准确无误。 请问您能否澄清一下: MC33FS6523CAE 在202 摄氏度左右关机是预期行为吗? 该部件的确切热关断阈值和容差是多少? AMUX芯片温度输出是否旨在直接对应于关断温度阈值? 是否有任何配置位、运行模式或调节器特定的过热关断行为可以解释这种差异? 器件 NXP SBC: MC33FS6523CAE Re: MC33FS6523CAE SBC Thermal Shutdown Occurs at Higher Temperature Than Expected 你好,Bharath, 感谢您提出的后续问题。我的答案如下。 1.无法通过 SPI 或 AMUX 直接访问每个调节器的 TSD 传感器值。获得有意义的每个调节器热指示器的唯一方法是通过热警告标志 (TWARN),该标志在 ~125 °C 的典型阈值处触发,远早于 TSD(~160 °C 最低)。当设置 TWARN_PRE、TWARN_CORE 或 TWARN_CCA 时,表示该特定稳压器传输晶体管附近的局部温度正在接近关断区域。这是目前最有效的电路中早期预警技术。 2. 可以采用以下方法: - 只让被测稳压器在其目标工作电流下运行(例如,MC33FS6523 的 VCORE 为 2.2 A),以便将散热集中在该稳压器的功率晶体管上。 - 通过 SPI 轮询 DIAG 寄存器,同时缓慢升高环境温度。 - 该调节器的 TWARN 标志将首先设置(典型值约为 125 °C),确认传感器处于活动状态,并为您提供一个参考点。 - 继续上升;TSD 将置位,稳压器输出将降至零。仅将此时的 AMUX 芯片温度读数作为近似参考,引用记录。 - The TSD is auto-recovering: the regulator restarts automatically once the junction temperature falls below TSD − hysteresis (~10 °C typical), so you can repeat the cycle. 3. 在温度上升过程中轮询以下SPI寄存器: 4. AMUX 温度是通用芯片传感器,不能用于验证或预测任何特定调节器的 TSD 跳闸点。对于 TSD 验证,唯一可靠的指标是 DIAG 寄存器中的 TSD 标志和受影响的稳压器输出电压的可观察下降。 BRs,托马斯 Re: MC33FS6523CAE SBC Thermal Shutdown Occurs at Higher Temperature Than Expected 嗨@TomasVaverka , 谢谢你的解释。 了解到 AMUX/MUX_OUT 温度来自内部芯片温度传感器,与 VPRE、VCORE、VCCA、VAUX 和 CAN_5V 的本地热关断电路使用的温度不同。 请问验证每个稳压器模块的热关断阈值的推荐方法是什么? 具体来说: 1.是否有办法读取或估算稳压器热关断传感器附近的局部温度? 2. NXP 是否有推荐的测试设置或程序来验证 160°C 的最低关机阈值? 3.在热测试期间,我们是否应该监测任何特定的诊断/状态寄存器,以确认是哪个稳压器模块触发了过热关机? 4. AMUX/MUX_OUT 芯片温度能否仅用作近似参考,而不用作关机验证温度? 在我们目前的测试中,AMUX/MUX_OUT 的温度读数在关机之前达到了约 202°C,我们也从外部验证了 MUX_OUT 电压。我们希望确认此阈值的正确验证方法。 此致, 巴拉特 Re: MC33FS6523CAE SBC Thermal Shutdown Occurs at Higher Temperature Than Expected 你好,Bharath, MC33FS6523CAE 稳压器的热关断阈值规定为 160°C(最低),并且针对每个稳压器模块(VPRE、VCORE、VCCA、VAUX 和 CAN_5V)进行本地化实现。 请注意,通过 AMUX/MUX_OUT 引脚获得的温度是由内部芯片温度传感器生成的,不一定与各个热关断电路使用的温度相同。稳压器由位于其功率器件附近的专用的热传感器进行保护。因此,通过 MUX_OUT 报告的温度与内部用于热关机决策的温度不同。 BRs,托马斯
View full article