Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
eMcem_Fcc_Init failed to clear errors Hello, I run the application on S32K388 and then attach trace32 debugger.  In eMcem_Fcc_Init(), read NCF_S0 status register returns u32ReadBack=0x5 (NCF[0] HSE lockstep error and NCF[2] ECC error).  and eMcem_Fccu_ClearFault() doesn't clear the faults too. How can I clear the faults to make eMcem_Fcc_Init() and eMcem_Init() initialised successfully?  What could be the issue ? Thanks Sara Re: eMcem_Fcc_Init failed to clear errors Hello, NCF_S0 = 0x5 indicates that both FCCU NCF[0] (lockstep/core fault) and NCF[2] (ECC fault) are active. On S32K3 devices, these fault flags are retained after an FCCU functional reset so that software can identify the root cause. The FCCU fault status cannot be cleared while the originating error condition is still present. Therefore, the issue is likely not in eMcem_Fccu_ClearFault(), but that a lockstep fault and an ECC fault are still being reported by the underlying hardware. Please check the corresponding FCCU, RCCU/DCMROD, and ERM status registers to identify the exact source. Since the issue occurs after attaching TRACE32, also verify that FCCU Debug Mode is enabled and compare behavior when the debugger is connected from reset. Best regards, Peter Re: eMcem_Fcc_Init failed to clear errors Hello Peter, Thanks for your response and analysis need to be verified. After looking into the FCCU, RCCU/DCMROD, and ERM status registers, the core 2 got into Lockup state.  On disblaing the CM_7_1/2/3 coreclockEnable of MCU config, the lockup fault doesn't happen and the eMcem_init got configured successfully and the status of NCF_S0 is 0x0. The coreclock can be enabled at the application startup on each core and not in the Mcal by default. This solves the issue. Thanks Sara
View full article
关于将 S32K344 项目从 172 引脚封装迁移到 257 引脚封装的指导请求 尊敬的NXP社区团队: 我目前正在使用 S32 设计工作室 (S32DS) 设计 一款 172 引脚封装的 S32K344 板 。 我想知道为 172 引脚封装开发的同一项目/代码是否可以直接用于 S32K344 257 引脚封装板,或者是否需要进行任何更改。 如果不能直接使用相同的代码,请您就以下方面提供指导: 需要更改 哪些 S32DS 项目配置和设备设置 ? 我们需要修改引脚配置/引脚复用(MUX)设置吗? 时钟、外设、CAN或其他配置设置 是否需要更改 ? 将现有的 172 引脚项目迁移到 257 引脚封装的 推荐步骤是什么 ? 如果您能提供迁移流程或任何与此软件包变更相关的 NXP 文档/参考项目,我将不胜感激。 感谢您的支持。 此致, 阿拉文德·托加拉利 Re: Request for Guidance on Migrating S32K344 Project from 172-Pin to 257-Pin Package 谢谢@VaneB Re: Request for Guidance on Migrating S32K344 Project from 172-Pin to 257-Pin Package 你好@Aravind_Togaralli 从软件角度来看,172 引脚和 257 引脚的 S32K344 封装非常相似,因为它们使用相同的 MCU 架构、存储器和外设模块。主要区别在于,257引脚封装提供了额外的I/O引脚,并为外围信号的布线提供了更多选择。 在 S32 设计工作室配置工具中,可以在引脚工具配置中选择和更改 MCU 封装。 如下例所示,只要两个MCU封装中所有已配置的引脚和外设信号映射都可用,您就可以使用257引脚封装来配置项目。 VaneB_0-1787612000573.png BR,VaneB
View full article
NXP S32M276CHABMKHSR 结构问题 您好,NXP技术员, 我是来自无锡美莱克斯公司的Ted,很高兴与您联系。 我有一个关于S32M276集成电路结构的问题。(请解答。)请参阅附件文件:原理图-S32M276)。 我按照数据手册的建议进行了设计,用磁珠将 9pin-VDD_AE10、12pin、25pin、37pin-VDD_HV_A 连接在一起。据我了解,9pin-VDD_AE10 P5V 输出电压由内部稳压器产生,然后通过 VDD_HV_A 引脚为 MCU 芯片供电。 但我移除了 L300 之后,PCBA 仍然可以正常工作。 所以我的问题是,VDD_AE10引脚和VDD_HV_A引脚内部是否连接在一起?否则,移除L300后系统仍然可以运行,这就说不通了。 Re: NXP S32M276CHABMKHSR Structure question 嗨,泰德, 当移除 L300 时,VDD_HV_A 上测得的电压是多少? MCU 侧电源功能域 VDD_HV_A 很可能是通过 MCU 侧和 AE 侧共享的 GPIO 供电的,因为所有 GPIO 都被钳位到 VDD_HV_A。换句话说,如果某个引脚上的电压大于 VDD_HV_A,则可以通过该引脚为 VDD_HV_A 供电。因此,你应该测量大约 VDD_HV_A = VDD_AE10 - Vf,而不是 VDD_HV_A = VDD_AE10。 谢谢! BR,丹尼尔 Re: NXP S32M276CHABMKHSR Structure question 嗨,丹尼尔, 感谢您的回复。 1、所以这意味着VDD_AE10和VDD_HV_A内部是连接的吗? 我无法理解这句话的意思。 [另外,您应该测量 VDD_AE10 - Vf 到 VDD_HV_A 之间的电压——这可能会损坏设备。] 如果您能再解释一下就太好了。 Re: NXP S32M276CHABMKHSR Structure question 嗨,泰德, AE芯片产生VDD_AE10。 在 AE 侧,VDD_AE10 是 AE 端口的电源,所有端口都钳位到 VDD_AE10。 在 MCU 端,VDD_HV_A 是 MCU 端口的电源,所有端口都被钳位到 VDD_HV_A。 这两个模具是相互连接的。 如果任何 MCU 端口上的输入电压高于钳位电路的 VDD_HV_A + Vf,则 VDD_HV_A 功能域将由注入电流供电。你应该测量 VDD_AE10 - Vf 在 VDD_HV_A 上 - 这可能会损坏设备。 问候, 丹尼尔 Re: NXP S32M276CHABMKHSR Structure question 嗨,丹尼尔, 感谢您的回复。 移除 L300 后,我测量到 VDD_HV_A 为 4.98V,而 VDD_AE10 为 5.02V; 所以,我可以这样说吗?VDD_HV_A 和 VDD_AE10 是内部连接的。 应该将它们连接起来以降低阻抗。 Re: NXP S32M276CHABMKHSR Structure question 你好@Ted_Qiao , 我已经和设计团队确认过了。除了通过两个芯片之间共享的 GPIO 进行的当前注入路径外,它们之间还有一个用于内部监控的连接。但是,这些路径并非设计用于承受工作电流,因此需要外部 PCB 连接。 BR,丹尼尔
View full article
S32K118 VLPS: I/O retention in the low power mode, plus SIRCSTEN and VLPSA queries Hi, We have VLPS entry and pin wake-up working on the S32K118, verified standalone with no debugger attached: four consecutive clean sleep/wake cycles, SMC_PMCTRL[VLPSA] clear on each, and SMC_PMSTAT confirming VLPR immediately before each WFI. So this is not a question about VLPS failing to work - it is about current consumption during a sleep that is working correctly. Setup: MCU: S32K118, 48-pin LQFP Board: S32K118EVB-Q048 (SCH-47530 Rev A1) Tools: S32 Design Studio 3.6.8, GCC 11.4 Issue: GPIO output state is retained through VLPS, and a driven RGB LED consumes current for the entire sleep. The on-board RGB LED is connected to PTD15 (green), PTD16 (red) and PTE8 (blue) through series resistors. What we observed: Our application drives the RGB LED from a periodic task while running. When the device enters VLPS, whatever level the LED pins were last driven to is still being driven for the whole time the device is asleep. The core is stopped, the clocks are gated, nothing in software is running - but the LED stays lit and keeps sourcing current until the device wakes. The effect on consumption is large. A single lit LED channel draws several milliamps through its series resistor, which is far above the VLPS current specified for this device and dominates the total completely. Our first supply-current measurements at J15 showed no meaningful drop between RUN and VLPS, and the retained LED state turned out to be the entire reason. The failure is silent. There is no flag, no error, and no difference in any status register between a sleep with the LED off and a sleep with the LED lit. The only symptom is that the low-power mode appears not to save any power, which is easily mistaken for VLPS not being entered at all. It cost us a significant amount of investigation time before we identified the cause. Questions: (a) Is this retention of GPIO output state through VLPS the intended behaviour of the device? (b) Is there any configuration on S32K118 that changes it, or must the application drive every pin to its intended sleep state before entry? (c) Is there recommended practice for configuring digital I/O prior to low-power entry - in particular pull-up/pull-down settings on pins tied to external switches or transceivers, where a retained pull is a continuous leakage path for the duration of the sleep? (d) Under what I/O configuration are the specified VLPS current figures for this device measured? Without knowing that, the specified figure cannot be compared against a measurement on a real board. (e) Are there any pins whose retained state can affect VLPS entry itself, or the wake-up path? deep sleep would put the I/O into an inactive state and the LED would go off by itself, since the core is stopped and all the clocks are gated. That is not what we see - the LED stays lit for the whole sleep at full brightness. Please confirm whether the LED is expected to remain lit in VLPS, and if so, whether there is any device setting that makes the output pins go inactive on low-power entry rather than holding their last driven level. Thanks Re: S32K118 VLPS: I/O retention in the low power mode, plus SIRCSTEN and VLPSA queries Hello @autouser, a) Yes. All I/Os are retained upon entering VLPS:  b) It is up to the application to set the required pins to the intended state before entering VLPS. c) This is application dependent. But, if you have unused pins, you can refer to HW Design Guidelines chapter 8 (unused pins).  "For unused digital and analog pins, the pin function should be set to DISABLED by setting the correspondingPORTx_PCRn[MUX] field to 0b000. The DISABLED function is default state for all pins not initialized. For pins with ADC functionality software should not trigger ADC channel conversion on the channel which is multiplexed with the unused pin.” If they are configured as inputs, they should not be left floating, pulled to either VSS or VDD externally or internally (application-dependent). You can also refer to the S32K3 Low Power Management documentation; chapter 10 provides some HW considerations which apply to general MCU power consumption: d) Table 4.7 (Power consumption) from S32K1xx Data Sheet shows power consumption defined in the attached S32K1xx_Power_Modes_Configuration.xlsx: Last row of the attachment shows which IOs were enabled at measurement. Also, foot note 1 mentions: "All output pins are floating, and On-chip pulldown is enabled for all unused input pins." e) Other than the configured wake-up pins, which will either wake the device immediately if asserted, I cannot think of ones which may affect VLPS entry/exit. Best regards, Julián
View full article
Subject: Standalone Evaluation Software / GUI for MC33774A AFE (RD33774CNC3EVB) I am working with the RD33774CNC3EVB (MC33774A-based CMU) and the RD-K358BMU evaluation board. I would like to evaluate and validate the MC33774A AFE independently, without integrating the complete BMS system. My goal is to verify features such as: - Cell voltage measurements - Temperature measurements - Diagnostics and fault reporting - Passive cell balancing - Register configuration - Communication between the BMU and AFE I have the following questions: 1. Does NXP provide a standalone evaluation GUI or PC software for the MC33774A? 2. Is there a FreeMASTER project, demonstration GUI, or any other graphical tool that can be used to monitor and configure the MC33774A through the BMU? 3. Is there a reference application or example firmware that enables evaluation of the MC33774A with minimal software development? 4. Are there any applications describing the recommended setup for evaluating the MC33774A using only the BMU and CMU evaluation boards? My objective is to perform functional validation of the AFE before integrating it into a complete BMS system. Thank you for your support. RD33774CNC3EVB , MC33774 , MC33665A  Re: Subject: Standalone Evaluation Software / GUI for MC33774A AFE (RD33774CNC3EVB) Dear Sanket, 1. Does NXP provide a standalone evaluation GUI or PC software for the MC33774A? [A] Yes, there is an EvalGUI 7 for the MC33774A. Specifically to be used with RD33774ADSTEVB. The GUI is intended to be used with SPI interface for communication between MCU and SPI to TPL transceiver and then via TPL to the MC33774A. Please refer to the UM11816.  If you are asking if there is a GUI specifically for the RD33774CNC3EVB with populated MC33665A TPL to CAN transceiver for the communication with MCU via CAN interface, unfortunately, there isn't any.  2. Is there a FreeMASTER project, demonstration GUI, or any other graphical tool that can be used to monitor and configure the MC33774A through the BMU? [A] For the BMU and CMU boards you mentioned we have a whole software bundle. However you need an S32DS IDE. Please refer to this link. Included are Demo projects for the FreeMASTER.  Please refer to the Release Notes document on the right side. 3. Is there a reference application or example firmware that enables evaluation of the MC33774A with minimal software development? [A] See above what software is available for the EVBs you have. However, the two boards are not sufficient. You need your own battery pack, with minimally 4 Cells for each MC33774A, or we have BATT-18EMULATOR. Emulating 18 Cells for each MC33774A populated on the RD33774CNC3EVB.  Please refer to the UM11943.  4. Are there any applications describing the recommended setup for evaluating the MC33774A using only the BMU and CMU evaluation boards? [A] Yes there is. However as mentioned above you need either a battery pack or the battery emulator. Please refer to the UM11943 and to this link. With Best Regards, Jozef Re: Subject: Standalone Evaluation Software / GUI for MC33774A AFE (RD33774CNC3EVB) Can we use RD33774CNT3EVB(which is TPL based) for standalone testing as the mentioned part number is not available with us but RD3374CNT3EVB id available along with the required setup  RD33774CNT3EVB 
View full article
例tflm_cifar10_cm33_core0に tflm_label_image_ext_mem のメモリ設定を使ってもいいですか? 良い1日を。 現在はEIQ例tflm_cifar10_cm33_core0 を使ってNPUモードでモデル化しています。モデルデータはSRAMに保存されます。推論時間は良好です。そして、こちらがメモリ構成です。このeiq例を5クラスのモデル用に修正しました https://docs.nxp.com/bundle/AN14700/page/topics/eiq_enablement.html しかし今はモデルが大きくなり、NPU tfliteモデルを外部メモリ上で特定したいと考えています。モデルデータはFlashに格納されています。そして、こちらは eiq の例tflm_label_image_ext_memの設定です。 https://docs.nxp.com/bundle/AN14700/page/topics/imx_rt700_system_details.html 私の目標は、ソースコードをtflm_cifar10_cm33_core0から保持したい(tflm_label_image_ext_memで新しいソースコードを作成したくはありません)が、NPU tfliteモデルを外部メモリ上で特定したい ということです。 私の解決策は、上記の画像のように、メモリ構成をSRAMから外部メモリに変更することだけです。それで合っていますか?あるいは、他の設定も変更する必要があるのかもしれません。 Re: Can I use memory config from tflm_label_image_ext_mem for the example tflm_cifar10_cm33_core0? こんにちは、 @nnxxpp さん。 ご説明ありがとうございます。 「--use-sequencer」を外部メモリモデルの実行と組み合わせて使用しないでください。 「tflm_label_image_ext_mem」例では、モデルが外部メモリから実行されるため、「--fetch-constants-to-sram」を残し、「--use-sequencer」は削除してください。 モデルを以下のように変換してみてください。 ./Neutronコンバータ \ --入力 QAT.tflite\ --出力 QAT_NPU.tflite\ --target imxrt700 \ --ヘッダーファイル出力をダンプする --dump-header-file-input \ --定数をSRAMに取得   お役に立てれば幸いです。 よろしくお願いいたします。 5月 Re: Can I use memory config from tflm_label_image_ext_mem for the example tflm_cifar10_cm33_core0? @mayliu1 こんにちは。これは新たな問題です(まだ解決されていません)。この問題は、外部メモリ(SRAMではなく)でのNPU tfliteモデルのデプロイに関連しています。 現在はSDKs of MIMRT700のeiqサンプルtflm_label_image_ext_memを使っています。この例はCANうまく実行できます。この例はモデル mobilenetv1 で、サイズ=224、クラス数=1000です。 サンプルのモデルを自分のモデル(同じ分類モデル)に置き換えようとしましたが、クラス数を変えました。 ラベルを変えました。(レーベル名の場合)、 サンプルのモデルを自分のモデルに置き換え、名前は同じまま使っています model_data.h ファイル内のmodel_data_lenも変更しました。 ビルドはできましたが、デバッグを実行するとプログラムは「静的プロセッシング」で停止し、結果が出ませんでした。 上の画像には 「モデルハンドルを保存できません。完了したらneutronModelUnprepare()を呼び出せ」というメッセージがありますが、NXPの従業員の一人はエラーではないと言っていました。https://community.nxp.com/t5/eIQ-Machine-Learning-Software/eIQ-FAQ/ta-p/1099741 NPUモデルが外部メモリ上にあるCASE、拡張子.tflite モデルを使います(モデルがSRAM上で位置する場合はヘッダーファイル.hではありません)。 モデルをフラグで--fetch-constants-to-sramに変換して、外部メモリ上のNPUモデルをこのように位置づけています ./Neutronコンバータ \ --input QAT.tflite \ --output QAT_NPU.tflite \ --target imxrt700 \ --ヘッダーファイル出力をダンプする --dump-header-file-input \ --use-sequencer \ --定数をSRAMに取得   NXPから設定や設定(SOの変更方法や場所)のチュートリアルが見当たらなかったので、上記の手順で試しましたがうまくいきませんでした。 手伝ってもらえますか?ありがとう。 Re: Can I use memory config from tflm_label_image_ext_mem for the example tflm_cifar10_cm33_core0? こんにちは@nnxxpp さん、 私たちの製品にご関心を寄せ、コミュニティをご利用いただき、本当にありがとうございます。 返信が遅くなり申し訳ありません。 前回の投稿で、問題はすでに解決済みだと書かれていたことに気づきました。全てが正常に機能していると聞いて安心しました。 ご理解いただき、改めて感謝申し上げます。 よろしくお願いいたします。 5月 Re: Can I use memory config from tflm_label_image_ext_mem for the example tflm_cifar10_cm33_core0? 応援してくれて本当にありがとうございます。正しく動作しました
View full article
MIMXRT1052CVJ5Bの電源問題 MIMXRT1050HDUGの仕様にあるように、このMCUには2つのバージョンが存在します。電源設計の参考にするために、自分のMCUの具体的なバージョンをどのように特定すればよいでしょうか? i.MXRT 105x Re: MIMXRT1052CVJ5B供电问题 ありがとう! Re: MIMXRT1052CVJ5B供电问题 こんにちは、 @Simon_CHan さん。 NXPのRTシリーズ製品にご関心をお寄せいただき、またNXPコミュニティをご利用いただきありがとうございます。 i.MX RT1050 のチップ正誤表にある ERR011093 を参照してください。正誤表には、この問題は A1 シリコンで修正済みであると記載されています。したがって、最も簡単な方法は、チップのシルクスクリーンでシリコン リビジョンを確認することです。A は A0、B は A1 を示します。バージョンが B の場合は、問題は修正済みです。バージョンが A の場合は、正誤表で規定されているとおり、DCDC_IN/DCDC_IN_Q を 2.8 V ~ 3.0 V の範囲内に制御する必要があります。 上記の情報がお役に立てば幸いです。 よろしくお願いします 5月
View full article
S32K388 GMAC0 lwIP FreeRTOS S32DS36 RTD600 Debug Error Dear 1. The original project was developed based on S32DS3.5 + RTD5.0.0, Build OK & Run OK 2. Development requires basic RTD 6.0.0. Development environment: S32DS 3.6.2 + RTD 6.0.0 + TCPIP_STACK_3.0.0 + FreeRTOS_11.1.0_6.0.0 3. RTD5.0.0 and RTD6.0.0 have significant differences, so projects based on the original RTD5.0.0 cannot be used. Instead, refer to the example code provided in the forum ( Example: S32K388 GMAC0 lwIP FreeRTOS S32DS 3.6.1 RTD600 ). 4. Modify the corresponding PIN according to your hardware platform as follows:          5. Debugging the example code revealed that some initialization steps failed, as follows:    6. If the corresponding code is masked, the program can run, but the PHY address cannot be found. The attached file contains a debug example. I'm not sure if the reference example provided on the forum has been modified, or if I only modified the PIN definition, or if there's some other configuration error. Re: S32K388 GMAC0 lwIP FreeRTOS S32DS36 RTD600 Debug Error Hi, Petrs Hello, you are absolutely right. I am indeed using my own hardware platform. During RTD 5.0.0 debugging, I was able to ping successfully using the example code provided on the official website. When using RTD 6.0.0 in person, I followed the same approach, mainly changing the PIN and discovering the code.The program failed to run. The attached file is based on my own hardware RTD 5.0.0 (S32DS3.5 + RTD 5.0.0 + TCPIP_STACK_2.0.0) and can ping. The example code is OK, but I'm not sure if the clock configuration is incorrect. Could you please provide some assistance? Re: S32K388 GMAC0 lwIP FreeRTOS S32DS36 RTD600 Debug Error Hi, It seems you only changed the MDIO/MDC pins compared to the community example you referred to. Does this mean you are using your own custom-designed board? I tested your project on the S32K388EVB-Q289, and the MCU initialization completed successfully. The PHY address was not detected because the MDIO/MDC signals are connected to different pins on the EVB. After changing the MDIO/MDC pins to PTD16/PTD17, the PHY address was correctly obtained. BR, Petr
View full article
S32J100 中 MCU_performreset 没有执行。 你好, 我尝试使用 Mcu_performReset 函数 RESET 控制器,但 PC 从该函数退出时处于 RESET 状态,而处理此 RESET 机制的函数Power_Ip_Specific_RequestPerformReset () 没有数据,取决于功能性 RESET 还是破坏性 RESET。我尝试配置S32DS,但问题仍然存在。 我使用的是 SW32J100_RTD_R23-11_0.8.0_CD04_HF01,S32DS 3.6.7 版本。 请问我哪里做错了? 谢谢! 阿莫尔 Re: MCU_performreset is not happening in S32J100 嗨@PavelL , 我了解了情况,会联系现场工程师解决这个问题。 感谢您的支持。 此致, 阿莫尔 Re: MCU_performreset is not happening in S32J100 你好@Ajadhav5 , 我写信给您是关于您目前拥有的一款产品——一款尚未正式上市的新产品(NPI)。 请注意,已获准提前使用此类产品的客户已指派了现场工程师。您指定的现场工程师应作为您解决有关本产品任何问题、疑虑或疑问的主要支持渠道。 我们的在线支持团队将在该产品正式版本发布后,提供更广泛的支持服务。在此之前,我们将无法提供所需的帮助。 感谢您对此事的理解,我们期待进一步加强与您的合作关系。如有任何疑问,请随时联系您的现场工程师,或直接联系我的团队和我。 感谢您的理解。 顺祝商祺! 帕维尔
View full article
EMIOS Pwm tooling error Emios 0 ch 255 in MCL I am trying to run trapezoidal motor control using S32K312 mini development board.  After porting the initialisation, I get the following error :  Issue: [Generation error] Please configure the counter bus EMIOS_0_CH_255 in MCL Level: Error Type: Tool problem Tool: Peripherals Origin: Peripherals Resource: Sources Information: [Generation error] Please configure the counter bus EMIOS_0_CH_255 in MCL My setup has : EMIOS mcl  initialises 0 and 1  for  EMIOS0 - Channel 0 -> PWM time base EMIOS1 - Channel 23 -> Time base for Hall pulse counter EMIOS pwm for  EMIOS0 Channel 1 as OPWMB for PWM 20KHz EMIOS Channel 3 as OPWMB for PWM pulse  Both the channels are based out od EMIOS Channel 0 in BCD mode.  Re: EMIOS Pwm tooling error Emios 0 ch 255 in MCL Here is a mex file. Re: EMIOS Pwm tooling error Emios 0 ch 255 in MCL Hi @ArunnK  I have tried applying the configuration you mentioned for Emios_Mcl and Emios_Pwm in the FreeRTOS_Toggle_Example_S32K312 (RTD 7.0.0 with FreeRTOS 7.0.0), and I have not been able to reproduce the errors on my side. Would you mind sharing your .mex file? It would also be really helpful if you could outline the steps you followed, so I can try to replicate the same behavior here. BR, VaneB Re: EMIOS Pwm tooling error Emios 0 ch 255 in MCL Hi @ArunnK  Thank you for sharing your .mex file. I imported it into the FreeRTOS_Toggle_Example_S32K312 (RTD 7.0.0 with FreeRTOS 7.0.0) project I previously used, and the error did not appear. To make sure we are following the same steps, could you please try the following: Delete the current example project and recreate. Update the code as needed to ensure everything is correct. Once the configurations are successfully generated, go to File → Import → S32 Configuration Tools → Import Configuration (*.mex). Select the .mex file you shared and merge it into the current configuration. After that, does the error still appear? And just to be sure, please double-check that all the software versions you are using are compatible.
View full article
UJA1169ATK/F/3 I'm using UJA1169ATK/F/3 connected to a S32K146 CPU on FlexCAN1. The UJA1169ATK/F/3 is used in Partial Networking with WakeUp Frame (no FD!) to wakeup the whole system from a deep sleep mode. Actually every thing works correctly if a valid Frame is sent within the CAN BUS (for valid Frame a mean a frame which is compatible with the filtering masks selected). The problem arise when an unwanted Frame (i.e. a frame, non FD, which is syntactically correct but do not pass the WUP filtering in use) is sent. What happen is that, quit often, if one such frame is sent, than any successive valid Frame does not wakeup the transceiver any more. It seems that, when an unwanted Frame, often, locks the capability of the UJA1169ATK/F/3 to correctly recognize valid Frames and hence to wakeup. At first i suppose the problem could be something on the bus which generate a bus error which in turns switch the UJA1169ATK/F/3 in reset mode without moving RX signal and thus without advise CPU. But this is not the case, since i used a CAN monitor and no bus error are recorded (note that i use a Windows application to generate messages on CAN BUS and another application to monitor the bus; both application use separate USB/CAN converter). Do you have any idea of which could be the problem ? Re: UJA1169ATK/F/3 Hello Michele, The behavior you describe is most likely related to the internal PN error handling of the UJA1169A. The device maintains an internal frame detection error counter. If a sequence of frames is received that do not match the configured PN filters (or are interpreted as invalid in PN evaluation), this counter can overflow and trigger a PN frame detection error (PNFDE). Once this condition occurs, the SBC may temporarily stop correctly recognizing valid wake-up frames, which could explain why subsequent valid frames no longer wake the device. I recommend checking the PNFDE status bit and verifying the PN configuration (ID/mask, DLC, data mask and data rate settings). As a debug step, you can try disabling data field evaluation (PNDM = 0) to determine whether the issue is related to data filtering. Please let me know the observed PNFDE state and PN configuration so I can further support your analysis. BRs, Tomas
View full article
RT1064 I2C communication abnormality at 400kHz The I2C2 interface of the RT1064 device connects to Module A. Communication anomalies occur at 400kHz, but it functions properly at 100kHz 1. Connecting module B of a different model within the same series at 400kHz is no problem 2. In terms of waveform, it is equivalent to an anomaly occurring when the host clock is stretched and then restored after connecting to Module A PS: Implement the I2C driver port of the device to another 1064 device, test module A, no issues at 400k What might be the reason? 1. Figure 1 Module A Abnormal Waveform of Logic Analyzer at 400kHz 2. Figure 2: Waveform of Logic Analyzer for Module A at 100kHz 3. Figure 3: Waveform of Module B at 400kHz i.MXRT 106x Re: RT1064 I2C communication abnormality at 400kHz Hi @foreverwlh2025 , Thanks for the additional clarification — this is a very important observation.   From your observations, the issue appears more likely to be related to insufficient 400 kHz I2C timing margin caused by the two-stage ADUM1251 isolation link, rather than an abnormality of Module A itself. Even if the rise time is within spec, on RT1064, we still recommend checking the LPI2C master-side 400 kHz configuration, especially MCFGR2[FILTSCL/FILTSDA] and MCCR0/MCCR1 , because the master synchronization latency on RT1064 is affected not only by rise time, but also by the digital filter and timing parameter settings. We suggest reading out the actual configuration used in your project and comparing it with Table 47-5, “LPI2C Example Timing Configurations,” in Chapter 47 of the RT1064 Reference Manual . In particular, please check whether the following settings match to the example values for your selected clock condition: I2C module clock source Target baud rate: 400Kbps PRESCALE FILTSCL / FILTSDA SETHOLD CLKLO CLKHI DATAVD Wish it helps you Best Regards May Re: RT1064 I2C communication abnormality at 400kHz Additional information, there was some progress in positioning yesterday: Our hardware expansion is: Motherboard: RT1064--- ADUM1251    3.3 V to 5 V Subboard: ADUM1251- Module A          5v to 3.3v After verification, it was found that after adding ADUM1251 to the two layers of the hardware link, module A had abnormal communication. However, after removing it, communication returned to normal at 400k. What could be the reason for this? PS: Our hardware engineers believe that ADUM1251 only increases communication latency and has no other impact Re: RT1064 I2C communication abnormality at 400kHz Hi,@mayliu1 Our product is about to be released, and we have been investigating this issue for several days. If we could receive your response as soon as possible, we would greatly appreciate it! Re: RT1064 I2C communication abnormality at 400kHz Hi  Supplementary information 1. Our two hardware engineers checked the waveform of the problem through an oscilloscope, and the rise time met the requirements, within 100+ns 2. I ported I2C initialization and read-write function drivers to another type of RT1064 device,  and tested module A without any issues The following figure shows the waveform of another device module A testing logic analyzer doubt: 1. If the clock recovers abnormally after stretching, what other reasons could be causing it 2. Is there a dedicated function to set settings such as MCFGR2 mentioned in the last reply? I didn't see any interface to be set in the I2C initialization process ----If the rise time is met, do we not need to consider these register settings? Re: RT1064 I2C communication abnormality at 400kHz Hi @foreverwlh2025 , Thank you so much for your interest in our products and for using our community. I think that this is most likely not a Module A issue, but a 400 kHz timing-margin issue on that specific RT1064 LPI2C2 bus. On RT1064, LPI2C timing is affected by bus rise time, bus loading, pull-up resistors, and glitch-filter latency.  RT1064RM  reference manual describe  that larger rise time increases synchronization latency.  (refer to chapter 47.3.1.4 Timing Parameters) The master glitch filters MCFGR2[FILTSCL/FILTSDA] must be set so their latency stays below the minimum SCL low/high period, and RT1064 provides example 400 kbps timing settings in MCCR0/MCCR1 .  Please check the Table 47-5. LPI2C Example Timing Configurations So if Module A makes the bus edges slightly slower or changes the effective loading, the bus may fail at 400 kHz but still work at 100 kHz .  Wish it helps you Best Regards May Re: RT1064 I2C communication abnormality at 400kHz Below is the configuration for printing. Which parameter may need to be adjusted? PS:apparently due to automatic interface allocation Re: RT1064 I2C communication abnormality at 400kHz A 10 MHz LPI2C functional clock is not listed in the RT1064 Reference Manual example timing configurations for 400 kbps. Although it is possible to generate a 400 kbps baud rate with this clock, the automatically generated timing parameters should be carefully verified against the I2C specification, particularly with respect to tLOW, tHIGH, setup/hold timing, and data valid timing. To reduce design risk, it is recommended to use a validated clock source, such as 48 MHz, as shown in the Reference Manual. Re: RT1064 I2C communication abnormality at 400kHz I tried modifying 60MHz and 8MHz, but it still didn't work. The red box in the figure below shows the values printed after modification, which are different from the manual Re: RT1064 I2C communication abnormality at 400kHz Hi @foreverwlh2025 , There are several ways to configure the I2C clock. As a suggestion, you can try 8 MHz and 60 MHz, as these two clock settings are relatively easy to achieve. I am using the SDK demo: "evkmimxrt1064_lpi2c_edma_b2b_transfer_master" Way 1: Configure LPI2C clock source to 60 MHz Simply set the clock divider to 0. Way 2: Configure LPI2C clock source to 8 MHz Use the MCUXpresso IDE Clock Tool and configure it as shown below. Select OSC_CLK as the clock source and set the divider to 3, which will generate an 8 MHz clock for the LPI2C (I2C) module. Wish it helps you Best Regards May Re: RT1064 I2C communication abnormality at 400kHz Hi @foreverwlh2025 , You may try setting the registers directly. For example, when using a 60 MHz I2C clock, the following configuration can be applied. Wish it helps you Best Regards May Re: RT1064 I2C communication abnormality at 400kHz The current I2C clock is configured based on the sample configuration in the SDK2_13_0-EVK-MIMXRT1064 \ boards \ evkmimxrt1064 \ river_deamples \ lpi2c directory, #define LPI2C_CLOCK_SELECT (0U) #define LPI2C_CLOCK_DIVIDER (5U) CLOCK_SetMux(kCLOCK_Lpi2cMux, LPI2C_CLOCK_SELECT); CLOCK_SetDiv(kCLOCK_Lpi2cDiv, LPI2C_CLOCK_DIVIDER); ---How can I modify it to obtain the precise 8MHz or 48MHz? (The clock tree doesn't seem to be visible) Re: RT1064 I2C communication abnormality at 400kHz As shown in the diagram, I tried to modify the register settings to correspond to the parameters, but there was no improvement at 60MHz; Even good modules cannot function properly at 8MHz Re: RT1064 I2C communication abnormality at 400kHz The cause has been identified, and the module with the problem will experience clock stretching at 400k. However, the isolator chip we are using does not support SCL bidirectional. After replacing the isolator chip, the test was normal; This order can be closed
View full article
Advice for bulk printing NFC cards Hi NFC Community! I want to bulk-order [10-200 pieces, maybe more later] Type 4A NFC cards [standard credit card size] with custom printing on the cards. Both the cards and the printing must be high quality. I also need fast shipping to Canada. Are there any companies / suppliers that anyone can recommend for this kind of thing? I want a long-term relationship with a good group for this. Thanks very much! Re: Advice for bulk printing NFC cards Hello @isenki, Hope you are doing well. For Tag/Card supply, please consult NTAG 424 DNA product page, Design Resources > Engineering Services section. Here you can find the contact for tag and reader manufacturers, solutions providers and system integrators. To find additional partner offerings that support this product, visit our Partner Marketplace. Regards, Eduardo.
View full article
LPC553x 参考手册:表 315 SCT0 信号错误 (SCTIMER) 你好, 我想报告 LPC553x 参考手册(修订版)中似乎存在的一个重大错误。4) 将表 315“SCT0 信号(输出)”与数据表表 3 进行比较,并询问哪个来源是权威的。 这是 LPC553x 参考手册,修订版 4,表 315“SCT0 信号(输出)”: 下表列出了 34 个外部引脚(如果我数得没错的话)。快速浏览 LPC553x 数据手册,发现它只有 31 个引脚。此外,表 315 列出了 PIO2_2、PIO2_9、PIO2_15、PIO2_30 和 PIO2_31 作为 SCT0 输出引脚。从数据手册来看,LPC553x 只实现了 PIO2_0 和 PIO2_1,所以该设备上不存在 Port-2 引脚。 现在,如果您仔细查阅数据手册中的表 3 并提取所有 SCT0_OUT 引脚,那么您最终会得到一个完全不同的表格: SCT0 信号(输出)连接至 SCT0_OUT0 PIO0_2、PIO0_17、PIO1_4、PIO1_23 SCT0_OUT1 PIO0_3、PIO0_18、PIO1_8、PIO1_24 SCT0_OUT2 PIO0_10、PIO0_15、PIO0_19、PIO1_9、PIO1_25 SCT0_OUT3 PIO0_22、PIO0_31、PIO1_10、PIO1_26 SCT0_OUT4 PIO0_23、PIO1_3、PIO1_17 SCT0_OUT5 PIO0_26、PIO1_18 SCT0_OUT6 PIO0_6、PIO0_27、PIO1_31 SCT0_OUT7 PIO0_21、PIO0_28、PIO1_19 SCT0_OUT8 PIO0_29,PIO1_13 SCT0_OUT9 PIO0_30 我的设计以数据手册表 3 为依据。 请, 确认数据手册(修订版 5.0)表 3 是 SCT0 输出引脚的权威来源, 确认参考手册中的表315有误。 请确认我上面的表格是否正确。 谢谢。 担 Re: LPC553x reference manual: Table 315 SCT0 Signals wrong (SCTIMER) 你好, 请使用参考手册中附带的“引脚功能表”来确定 SCT0_OUT 功能的可用引脚。 顺祝商祺!   Re: LPC553x reference manual: Table 315 SCT0 Signals wrong (SCTIMER) 你好, 目前,请参考引脚功能表。 我将信息传递给团队。 此致敬礼,路易斯 Re: LPC553x reference manual: Table 315 SCT0 Signals wrong (SCTIMER) 你好@luis_maravilla , 感谢您指出“引脚功能表”。我不知道参考手册里竟然隐藏着一个电子表格文件。 我快速浏览了一下“引脚功能表”,证实参考手册中表 315 “SCT0 信号(输出)”的信息不正确。 请将此信息转交给文档团队进行更正。 如果对引脚功能还有其他疑问,权威来源是数据手册还是引脚功能表? 谢谢。 此致, 丹尼尔
View full article
P1013 为确保散热和通信稳定性而对 CPU/CCB/DDR 进行降频 我的开发板上有旧的 P1013NSE2MHB 元器件。 我想降低它们的时钟以降低元器件的热负荷,并使用 P1013NSE2LFB 元器件的 PCIe 和 SPI 标准的通信时钟,这是我最熟悉的。 简而言之,我希望让 P1013NSE2MHB 采用 P1013NXE2LFB 的 PLL 时钟配置,即 P1013NSE2MHB 的 CPU/CCB/DDR 最终时钟频率应为 1067/533/533 MHz。  根据 AN4343 第 6 节,两个元器件都应该能够支持 1067/533/533 的时钟速度。 我唯一担心的是,P1013NSE2MHB的CCB限制据说为480MHz。除了只有 CCB 时钟 400 和 480 MHz 才能使用内置的 PLL 设置来达到最大值 1200MHz 之外,我找不到任何理由。(参见AN4343第6.2.1节表16) 我只想让CPU的核心频率达到1067MHz。  P1013NSE2MHB 和 P1013NXE2LFB 均来自同一产品线,应采用相同的架构;因此,即使 CPU 最大时钟频率提升至 1200MHz,也不应妨碍使用先前已实现的 CCB 架构来实现较低的 CPU 时钟频率。除非重新设计CCB总线以支持新的CPU,尽管没有根本的不同,但这将是资源的巨大浪费。 感谢大家提供的见解。 QorIQ P1 设备 Re: P1013 CPU/CCB/DDR Underclocking for Thermal and Communication Stability 根据以下数据,架构似乎有所不同,CPU/CCB/DDR可能不会有相同的趋势 CPU/CCB/D DR 频率 (MHz) LF=1067/533/667 MH=1200/480/800 但这是旧设备,因此可能需要向恩智浦内部团队查询解释 Re: P1013 CPU/CCB/DDR Underclocking for Thermal and Communication Stability 你好, 是的——文档支持您的观察,即 CPU/核心、平台/CCB 和 DDR 在 T2080/T2081 上不必遵循相同的扩展趋势,因为它们是由不同的 PLL 功能域生成的,并且内存总线明确地由其自身的 PLL 决定。核心时钟和平台时钟由不同的 PLL 生成,T2080/T2081 时钟映射为核心集群 PLL、平台 PLL 和 DDR PLL 公开了单独的状态/控制点( Clocking_PLLCnGSR 、 Clocking_PLLPGSR 、 Clocking_PLLDGSR )。硬件规格还直接指出,内存总线时钟速度由其自身的 PLL 决定。 因此,从建筑学角度解释如下: CPU/核心频率来自核心集群PLL,根据配置的不同,可能以PLL/1、/2或/4运行。 平台/CCB 频率是一个独立的平台时钟域,具有其自身允许的 SYSCLK 比率。 DDR频率是独立于DDR的,内存总线时钟频率是DDR数据速率的一半,并由其自身的PLL控制。 这就是为什么像以下这种看起来非单调的数对: LF = 1067 / 533 / 667 MH = 1200 / 480 / 800 从建筑学的角度来看,这在原则上是合理的:这三个功能域不需要同时上升和下降。然而,我在现有的 T2080/T2081 资料中找不到记录的那两个 T2080 频率三元组。   此致 Re: P1013 CPU/CCB/DDR Underclocking for Thermal and Communication Stability 我问的不是T2080/T2081处理器。 我正在考虑P1013/P1022处理器。
View full article
Why model size is limited at 1 MB? I run model from sample tflm_cifar10 on MIMRT700 (NPU model). When building the program, I could see the model's size and correspond region size.  In many cases, the region size is 1 MB. As my understanding, the model's size is limited at 1 MB. Is that right? I did not understand this point. Here is information of MIMRT700 EVK. I don't know where model is saved on MIMRT700 EVK. And where is the 1 MB for region size? Is it actual limit of model size? Or we can increase model size by some methods. Do you have any comment for this problem? Because I try to deploy a larger model > 1 MB. I do wait for your response. Thank you. Re: Why model size is limited at 1 MB? @mayliu1  Thank you so much. Now I understood that we can increase the size of the model by setting region size. Or If I want to run larger model on external memory, I can follow this document https://docs.nxp.com/bundle/AN14700/page/topics/external_memory.html  Re: Why model size is limited at 1 MB? Hi @nnxxpp , Thank you so much for your interest in our products and for using our community. Q: I don't know where model is saved on MIMRT700 EVK. And where is the 1 MB for region size? Is it actual limit of model size? Or we can increase model size by some methods. Do you have any comment for this problem? Because I try to deploy a larger model > 1 MB. A: The 1 MB shown for modeldata is not a hardware limit of the RT700. It is only the default linker allocation used in the sample project. For larger models, this allocation can be adjusted in the project settings, and external XSPI flash can also be used if more storage is needed. For more detail information, you can refer to this AN14700. https://docs.nxp.com/bundle/AN14700/page/topics/introduction.html So, the RT700 is not inherently limited to a 1 MB model. Larger NPU models are supported either by increasing the modeldata memory allocation or by placing the model in external XSPI flash with the appropriate conversion option.  Wish it helps you Best Regards May Liu Re: Why model size is limited at 1 MB? @mayliu1  I want to reopen this topic. Now i am trying to deploy larger model on RT700. The below image is captured when building the program with the small model. I see that there are 4 memory regions: - QSPI_flash: external memory - SRAM: I ask chatgpt and it is for data when running the program (like .data, .bss, stack, heap). Is that correct? - NCACHE_REGION: it is same ktensorArena (for inputs, intermediate outputs and output) -  modeldata: to save model weights I see in the memory configuration when I import SDK example. It means that SRAM, NCACHE_REGION and modeldata from SRAM (7.5 MB). NCACHE_REGION and modeldata should be located in  0x2000_0000 to 0x2058_0000 (5.5 MB) to get best perforemce (SRAM area that can be accessed by the NPU) But location of SRAM (named SRAM) is 0x20080000 (in the second image) ==> It is also in the range 0x2000_0000 to 0x2058_0000. And by default, it is set about 2.5 MB. It means that NCACHE_REGION + modeldata should be less than (5.5 - 2.5) = 3 MB. My model size is about 3.5 MB. Beside that I can locate my model on external memory (it results in larger inference time), how I can config memory to still locate my model (3.5 MB) on memory area that NPU can access? I am curious about whether we can shrink "SRAM" region (in the images 1, 2) or can I move it to another area of RAM (7.5 - 5.5 = 2 MB - the last region in the image 3)? And how I can estimate the size of "SRAM" region? In the below image, it is 15560 B. Sorry for my long questions. Re: Why model size is limited at 1 MB? @mayliu1  Good morning. Maybe you missed my new above questions.  Re: Why model size is limited at 1 MB? Hi @nnxxpp , Apologies for the delayed response. If you don’t mind, could you please create a new case for your new issue?  Thank you for your understanding and cooperation. Best Regards, May Re: Why model size is limited at 1 MB? @mayliu1  Yes, ok. Let me create new issue. Thank you. Re: Why model size is limited at 1 MB? @mayliu1  I have resolved my problem. We can locate SRAM outof 5.5 MB area for NPU. I locate modeldata and kTensorArena in area 5.5 MB and it worked. The inference time is good. But If you did not miss my questions, so I can finish soon my tasks. Thank you. Re: Why model size is limited at 1 MB? Yes. Have a nice day. Re: Why model size is limited at 1 MB? Glad to hear that your issue has been resolved. Apologies for the delayed response,   thank you for your understanding.
View full article
モーター制御eTPUライブラリのソースパッケージを提供していただけますか? 私は3相モータのPWM生成にMPC5777C eTPU PWMMを使用しています。 モーター制御eTPUライブラリのドキュメントには、ライブラリのリリースパッケージにeTPUソースファイルが含まれていると記載されています。 etpuc_ .c/ etpuc_ .h PWMMには以下が必要です。 etpuc_pwmm.c etpuc_pwmm.h CodeWarrior eTPUプロジェクトまたはビルド環境 AZSPWM/NSPWMにおける位相依存キャリア極性を実装するために、PWMMエッジ配置アルゴリズム、特に中心揃え/反転中心揃えエッジの計算を修正する必要があります。 モーター制御eTPUライブラリのソースパッケージを提供していただけますか?あるいは、AN5335SW / PWMM eTPUのソースコードを入手する方法を教えていただけますか? Re: Could you provide the Motor Control eTPU Library source package? こんにちは、 ソースコードを入手するには、NXP.comでチケットを発行してください。この件は公開コミュニティでは対応されません。 よろしくお願いいたします。 ピーター
View full article
S32K3 出现间歇性引导加载程序 → 应用程序跳转故障(无法在所有主板上重现) 您好,NXP团队: 我继续前面关于 S32K3 设备中 S32K311 中 C40 闪存擦除/程序限制 C40 闪存擦除/从引导加载程序写入的讨论(相同闪存块执行): 在您的支持下,我们通过以下方法解决了闪存擦除/编程问题: 确保在操作过程中不执行目标闪存块的操作 本期 我们现在观察到启动加载程序 → 应用程序跳转过程中的间歇性问题。 在大多数情况下,同样的跳转实现方式都能可靠地工作: 在大约 20 块主板上测试 应用程序重新刷新>100 次 ECU RESET >1000 次 在这些情况下没有发现问题 但是,在 2 个板块中,我们偶尔会看到: 控件无法跳转到应用程序 设备仍停留在引导加载程序中 恢复方法: 使用调试器重新刷新组合 HEX(引导加载程序 + 应用程序)后,问题得到解决 关注: 在生产中(车辆安装的 ECU),通过调试器重新刷新是不现实的 使用的跳转功能 C void JumpToApplication(void) { uint32appStack= *(uint32 *)(APP_STARTADDR); uint32 func = *(uint32volatile*)(APP_STARTADDR + 0xC); func = *(uint32volatile*)(((uint32)func) + 0x4); DisableAllInterrupts(); s32_scb->vtor = app_startaddr; __asm volatile("msr msp,%0"::"r"(appStack)); __asm volatile("msr psp,%0"::"r"(appStack)); func = ((((uint32)func)& 0xFFFFFFFEU) | 1U); (*(void(*)(void))func)(); 而(1); } static void DisableAllInterrupts(void) { for (int i = DMATCD0_IRQn; i<= SoC_IRQn; i++)     { IntCtrl_Ip_DisableIrq((IRQn_Type)i); IntCtrl_Ip_ClearPending((IRQn_Type)i);     } S32_SysTick->CSRr = 0U; } 说明 问题无法持续重现 出现间歇性& ,随机发生。 全图像重新刷新(组合 HEX)恢复正常行为 请求指导 能否请您帮忙 在跳转到应用程序之前,还应增加哪些检查? 是否有任何已知情况(MPU、高速缓存、VTOR、障碍等)会导致这种间歇性行为? 这可能与 缓存状态(I/D 缓存未清理/禁用)? 闪存编程不完整或校准问题? 向量表或重置处理程序不一致? 跳转之前有推荐的产品级序列吗(屏障、缓存处理等)? 如果需要更多细节,请告诉我,并提前感谢您的支持。 致以最崇高的敬意, Yusup Khan S32DS-ARM S32K3 S32K31XEVB-Q100 @danielmartynek C40 在 S32K311 中的引导加载程序中擦除/写入闪存(执行相同的闪存块) Re: Intermittent Bootloader → Application Jump Failure on S32K3 (Not Reproducible on All Boards) 你好,尤苏普、 设备仍然停留在引导加载程序中意味着什么? 能否安装调试器,检查卡在哪里? 是故障异常还是软件循环? 真的有必要重新刷新吗? 关于 MPU 和缓存,良好的做法是清理并禁用缓存。应用程序会根据使用情况重新配置 MPU,因此无论如何都应清理并禁用缓存。 您可以添加内存屏障,也可以参阅 S32K3xx 参考手册第 3.8 节 “内存操作序列化”,并使用先写后读顺序。 此外,检查 DCM_GPR 寄存器是否存在故障。(RM,表 231)。产品系列中由 DCM 控制的功能和可用性。) 确保时钟配置与 RM 中列出的时钟选项之一相匹配,例如表 157.选项 A - 高性能模式(CORE_CLK @ 160 MHz)。 总之,关键是要找出引导程序卡住的循环。如果出现故障异常,则需要收集更多有关故障的信息。 https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K312-HARDFAULT-Handling-Interrupt-DS3-5-RTD300/ta-p/1806259 https://community.nxp.com/t5/S32K-Knowledge-Base/How-To-Debug-A-Fault-Exception-On-ARM-Cortex-M-V7M-MCU-S32K3XX/ta-p/1595570 https://community.nxp.com/t5/S32K-Knowledge-Base/Fault-handling-on-S32K14x/ta-p/1114447 此致, 丹尼尔 Re: Intermittent Bootloader → Application Jump Failure on S32K3 (Not Reproducible on All Boards) 你好,@yusupkhan241、 你在许多主板上成功地对其进行了测试,但只有少数几个显示了这个问题。因此,这显然是偶发性的,我无法从现有信息中确定根本原因。可能的原因有很多,需要在故障主板(连接调试器)上进行适当的调试。 有趣的是,上电复位无济于事。如果这只是一个运行时问题(例如如出现高速缓存状态不良、IRQ 挂起、CPU 寄存器状态或剩余 RAM 内容等情况,则 POR 应将其清除。 在 POR 之后,其他工作板是否正常独立组网 (SA)? 如果是,则表示与非易失性存储器有关。我建议将闪存内容转储到故障主板上,然后逐字节将其与正常运行的主板进行比较。 此致, 丹尼尔   Re: Intermittent Bootloader → Application Jump Failure on S32K3 (Not Reproducible on All Boards) 你好@丹尼尔-马蒂内克 感谢您的回复。 说明一下,我们观察到两种间歇性行为: 1) 启动加载程序,但跳转失败: - 引导加载程序接收到更新命令,并成功对应用程序进行编程。 - 应用程序 CRC 校验通过。 - 但是,在发出跳转后,控制权并没有转移到应用程序。 2) 启动加载程序无反应: - 无 UART 响应,无 LED 指示。 -POR/软件RESET无法恢复。 - 只有通过调试器重新刷新才能恢复系统。 到目前为止,仅靠 POR 并不能解决问题。 对于跳跃序列,我们目前采用以下方法: - 跳转前验证申请: IVT 标记检查 堆栈指针(非 0x0 / 0xFFFFFFFF) RESET 处理器有效期 - 跳跃序列包括 禁用中断(单独清除) 禁用 SysTick 缓存清理 + 失效 VTOR 最新情况 MSP/PSP 最新情况 DSB/ISB 障碍 跳转到重置处理器 /* -------------------------------------------------------------------------- */ /* 闪存布局 */ /* -------------------------------------------------------------------------- */ /** @brief 内部闪存的基地址。*/ #define FLASH_BASE_ADDR (0x00400000U) /** @brief 闪存总容量(1 MB)。*/ #define FLASH_TOTAL_SIZE (0x00100000U) /** @brief 内部闪存的结束地址。*/ #define FLASH_END_ADDR (FLASH_BASE_ADDR + FLASH_TOTAL_SIZE) /** @brief 应用程序映像区域的起始地址。*/ #define APP_STARADDR (0x00422000U) /** @brief 支持的最大应用程序图像大小(以字节为单位) 。*/ #define APPLICATION_IMAGE_SIZE (FLASH_END_ADDR - APP_STARTADDR) /** @brief 每个传输步骤分配的最大有效载荷缓冲区。*/ #define FLASH_CHUNK_SIZE (512U) /** @brief RESET 后 CRC 验证期间使用的区块大小。*/ #define CRC_CHUNK_SIZE (4096U) /** @brief 应用程序图像基础的 IVT 标记预期值。*/ #define IVT_MARKER_MAGIC (0x5aa55a5U) /** @brief 保留是为了与现有应用程序映像版本实现布局兼容。 */ #define IVT_ENTRY_ADDR (APP_STARTADDR + 0x2000U) /* -------------------------------------------------------------------------- */ /* 应用程序跳转配置 */ /* -------------------------------------------------------------------------- */ /** @brief 从应用程序开始到核心入口地址的偏移量。*/ #define FLASH_APP_CORE_ENTRY_OFFSET (0x0CU) /** @brief 从核心入口地址重置处理程序的偏移量。 */ #define FLASH_APP_RESET_HANDLER_OFFSET (0x04U) /** @brief 有效应用程序映像的预期 IVT 标记魔法值。*/ #define FLASH_IVT_MARKER_MAGIC (0x5AA55AA5U) /** @brief 默认擦除的 32 位闪存值。*/ #define FLASH_ERASED_U32_VALUE (0xFFFFFFFFU) /** @brief 默认零 32 位值。*/ #define FLASH_ZERO_U32_VALUE (0x00000000U) /** * @brief 验证从应用程序闪存读取的地址。 * * @details * 该函数检查给定地址值是否有效和可用。 * 它过滤掉常见的无效值,例如: *-0x00000000(未编程/空值) *-0xFFFFFFF(擦除的闪存) * * 此函数用于验证堆栈指针和 RESET 处理程序。 * @Param 地址值从闪存(堆栈指针或重置处理程序)读取的地址。 * * 如果值有效,则返回 TRUE,否则返回 FALSE。 */ static boolean Flash_IsAddressValid(uint32 addressValue) { return ((addressValue != FLASH_ZERO_U32_VALUE)&& (addressValue != FLASH_ERASED_U32_VALUE)) ?true : false; } static AppJumpError_t Flash_PrecheckApplication(void) { uint32 appStack; uint32 coreEntry; uint32 resetHandler; /* IVT 标记验证 */ if ((*(volatile const uint32 *)APP_STARTADDR) != FLASH_IVT_MARKER_MAGIC) { return APP_JUMP_ERR_CORRUPT; } /* 堆栈指针验证 */ appStack = *(volatile const uint32 *)APP_STARTADDR; 如果 (Flash_IsAddressValid(appStack) == FALSE) { return APP_JUMP_ERR_STACKPTR; } /* 重置处理程序验证 */ coreEntry = * (volatile const uint32 *) (APP_STARADDR + FLASH_APP_CORE_ENTRY_OFFSET); resetHandler = * (volatile const uint32 *) (CoreEntry + FLASH_APP_RESET_ENTRY_OFFSET); if (Flash_IsAddressValid(resetHandler) == FALSE) { return APP_JUMP_ERR_RESETHANDLER; } return APP_JUMP_OK; } /** * @brief 将执行从引导程序转移到应用程序。 * @details * 此函数执行将控制权 *从引导加载程序转移到应用程序固件所需的最后步骤: * *-禁用所有中断 *-停止系统勾选 *-清除缓存并使其无效 *-设置主堆栈指针 (MSP) *-更新向量表 *-跳转到应用程序重置处理程序 * * 重要: *-必须在调用此函数之前完成所有验证。 * - 此函数不返回。 */ void JumpToApplication(void) { uint32 appStack; uint32 coreEntry; uint32 resetHandler; /* ------------------------------------------------------------------ */ /* 读取应用程序向量表 */ /* ------------------------------------------------------------------ */ appStack = *(volatile const uint32 *)(APP_STARTADDR); coreEntry = *(volatile const uint32 *)(APP_STARTADDR + FLASH_APP_CORE_ENTRY_OFFSET); resetHandler = *(volatile const uint32 *)(coreEntry + FLASH_APP_RESET_HANDLER_OFFSET); /* ------------------------------------------------------------------ */ /* 禁用中断 */ /* ------------------------------------------------------------------ */ Flash_DisableAllInterrupts(); /* 禁用 SysTick */ S32_SysTick->CSRr = 0x00000000; /* ------------------------------------------------------------------ */ /* 缓存处理 */ /* ------------------------------------------------------------------ */ Cache_Ip_Clean(CACHE_IP_CORE, CACHE_IP_DATA, TRUE); Cache_Ip_Invalidate(CACHE_IP_CORE, CACHE_IP_INSTRUCTION); /* ------------------------------------------------------------------ */ /* 设置向量表地址 */ /* ------------------------------------------------------------------ */ S32_SCB->VTOR = (uint32)APP_STARTADDR; /* ------------------------------------------------------------------ */ /* 设置主堆栈指针 */ /* ------------------------------------------------------------------ */ __asm volatile ("msr msp, %0" :: "r"(appStack)); __ asm volatile ("msr psp,%0"::"r"(appStack)); __asm__ __volatile__ ("dsb 0xF": :"memory"); __asm__ __volatile__ ("isb 0xF": :"memory"); /* 确保 Thumb 模式 */ resetHandler = (resetHandler& FLASH_THUMB_ADDRESS_MASK) | FLASH_THUMB_ADDRESS_BIT; /* ------------------------------------------------------------------ */ /* 跳转到应用程序 */ /* ------------------------------------------------------------------ */ ((void (*)(void))resetHandler)(); /* 不应到达此处 */ while (1) { /* 陷阱 */ } } 我们有几个具体问题: 1) 在这个验证/跳转序列中是否有任何关键的遗漏或错误? 2) 你是否建议进行更多检查(如更严格的 SP/PC 范围验证或校准检查)? 3) 即使使用此序列,缓存/MPU 状态或丢失的障碍是否仍会导致这种间歇性行为? 4) 是否存在任何已知的闪存对齐或 ECC 校正依赖性,可以解释为什么调试器重新刷新总是能解决问题? 5) 此外,我们观察到,使用全局中断禁用: __asm volatile("cpsid i"); 会导致跳转失败,而逐个禁用中断则能可靠地工作: for (irqIndex = DMATCD0_IRQn; irqIndex<= SoC_IRQn; irqIndex++)     { IntCtrl_Ip_DisableIrq((IRQn_Type)irqIndex); IntCtrl_Ip_ClearPending((IRQn_Type)irqIndex);     } 请问在这种情况下,全局中断禁用为何会影响跳转行为? S32DS-ARM S32K3 顺祝商祺! 尤苏普 Re: Intermittent Bootloader → Application Jump Failure on S32K3 (Not Reproducible on All Boards) 你好@danielmartynek 感谢您的支持与见解。 您对 POR 无法恢复系统的观察帮助我们专注于非易失性存储器。 我们已确定根本原因是正在进行的闪存写入操作期间发生重置导致的 NVM(数据闪存)损坏。这会导致部分编程和无法更正的 ECC 错误,从而导致在早期启动时出现 HardFault。 我们通过重现问题并比较工作板和故障主板之间的闪存数据来验证这一点。修复了重置处理并确保 NVM 操作在重置之前完成后,该问题不再可重现。 感谢您提供的指导,帮助我们缩小范围。 此致, 尤苏普·汗
View full article
Cell Balancing not working again on MC33774A Hi everyone, I am working with the MC33774A to balance cell pins. First, I set balancing for cell 1 (3.7 V) with an under-voltage threshold UV0 = 3.6 V. When I read the BAL_CH_UV0_STAT0 register, the value is 0x0C00. This makes sense because cell 11 (3.4 V) and cell 12 (3.3 V) are below the threshold. Then, I changed the under-voltage setting to UV0 = 3.2 V (lower than 3.6 V) and activated cell balancing for cell 11 and cell 12, but it did not work. After referring to the MC33774A datasheet, I realized that in voltage-controlled mode there is a third input, which is the status of BAL_CH_UV0_STAT. So, I want to clear the bits of BAL_CH_UV0_STAT (from 0x0C00 to 0x0000) to allow the balancing process to run again. However, these bits are read-only, with a “read clears bit” behavior. I tried to read the entire BAL_CH_UV0_STAT0 register using the command: Bcc_774a_COM_ReadRegisters(BCC_CHAIN_ADDR, 1, MC33774_BAL_CH_UV0_STAT0_OFFSET, 1, Bms_TD);   But the returned value of BAL_CH_UV0_STAT0 is always 0x0C00. It seems that the bits are not being cleared.  Currently, I am facing an issue where I cannot clear the bits in the BAL_CH_UV0_STAT0 register, and I would appreciate any help. Re: Cell Balancing not working again on MC33774A HI  Please follow below step to set CB function under UV condition,seems you don't have correct steps setting for this CB function test.: 1: wake up and assign CID Re: Cell Balancing not working again on MC33774A Hi guoweisun, thanks for your help. After reviewing the steps you provided, I think that I have set the CB function under UV condition correctly. But my issue is not with the configuration steps, but rather with clearing the values in the 'BAL_CH_UV0_STAT0' register. Anyway, thank you so much for your support. While going through the steps you mentioned, I rechecked the datasheet and was able to find a solution to my issue.
View full article
PIC16F877Aを使用してI2Cのビットバンギングを試みましたが、出力が得られません。 それで、I2C通信にビットバンギングを実装しようとしているのですが、出力が得られません。 現在、Proteusを使用しており、EEPROMを使用しています。開始シーケンスは視覚化されますが、シミュレーションではEEPROMが認識されず、sdaは想定どおり常にハイになっているようです。 Re: Trying to bit bang I2C using PIC16F877A but cannot get the output こんにちは、 製造元への連絡を手伝っていただけますか? よろしくお願いいたします。
View full article