Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
S32K312:NMI 在 Reset_Handler 执行之前触发,仅在功能(软件)复位之后触发,且仅在特定情况下触发。 设备:S32K312 工具链:Green Hills ELXR(编译器) HSE固件:s32k312_hse_fw_0.13.0_2.55.0_pb250129.bin 调试器:Lauterbach TRACE32 软件:基于AUTOSAR RTD的引导加载程序(FBL)+应用程序(APP),双镜像结构 问题概要 在部分生产单元上,CPU 在执行功能性操作后立即挂起。 (软件)RESET。同样的单位在破坏性 (上电复位)后总能正常启动。在我们的参考/已知良好设备上,不会出现卡顿现象。 证据表明,非军事事件 (NMI) 发生在任何应用程序代码执行之前。 1)在挂起点捕获的 CPU 上下文(自动堆叠的异常帧): - R0-R3 = 0x00000000,R12 = 0x00000000 - LR = 0xFFFFFFFF(重置默认值 -> 尚未执行任何 BL) - PC = 0x00416904(我们的 Reset_Handler 的第一个指令地址) - xPSR = 0x01000000 2) SCB->ICSR = 0x00000802 Chibeom_3-1785136456875.pngChibeom_3-1785136456875.pngChibeom_3-1785136456875.pngChibeom_3-1785136456875.pngChibeom_3-1785136456875.pngChibeom_3-1785136456875.png - VECTACTIVE[8:0] = 2 -> NMI 是当前活动的异常 - RETTOBASE = 1 这证实 CPU 当前正在 NMI 处理程序内部执行。 3) 我们向量表中的 NMI 偏移量条目正确指向我们自己的 默认异常处理程序,因此这是一个真正的 NMI 事件,而不是向量事件。 表格损坏。 在相同的挂起状态下检查的寄存器(全部读取为干净/非活动状态) - MC_RGM_DES = 0x00000000(非破坏性RESET) - MC_RGM_FES = 0x20000000(仅限第 29 位)(仅限“软件功能RESET”) 标志位已设置,无其他功能 RESET源已标记) - FCCU:STAT、N2AF_STATUS、A2FF_STATUS、N2FF_STATUS、NCF_S0、IRQ_STAT 全部 = 0x00000000 - CMU_FC 实例 0、3、4:SR = 0x00000000(无频率高/低故障) - PMC LVSC = 0x00000000(无 LVD/HVD 标志,已锁存或带电) - ERM (0x4025C000): 无法读取正常单元或故障单元的 ERM 值 (在我们的配置中可能采用时钟门控),因此 ERM 状态未经验证。 问题 1. 除了 FCCU / CMU_FC / PMC / MC_RGM 之外,还有其他 NMI 来源吗? 这可能会在应用程序的 Reset_Handler 执行之前触发。 第一条指令? 2. 由于 HSE 子系统独立于应用程序核心运行,因此 应用程序核心功能重置是可能的(但这不会导致) 重置 HSE)以创建状态不匹配,从而触发 NMI。 应用核心? 3. 是否有与此症状相符的 S32K312 已知勘误表(仅限 NMI) 功能性/软件重置(而非上电复位)? 任何关于需要检查的其他登记册的指导,或涵盖以下内容的任何文件 非常感谢来自 FCCU / ERM / CMU_FC / PMC 以外的 NMI 信息来源。 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , 请您在系统处于挂起状态时读取寄存器 MU_0.MUB CSSR0 和 MU_1.MUB CSSR0,并确认其中任何一个寄存器的第 0 位(NMIC)是否已设置? 谢谢 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 嗨@danielmartynek , 感谢您指出 MU_0.MUB / MU_1.MUB CSSR0。 MU_0.MUB 和 MU_1.MUB 上的 CSSR0(位 0,NMIC)均读取 0x00000000。 单元处于挂起状态,因此 MU->NMI 请求路径 (CCR0[NMI] / CSSR0[NMIC]) 似乎并非待处理。 然而,在比较已知良好单元和一台设备之间的MU寄存器时, 故障单元(两者均在相同的挂起状态地址范围内捕获), 我们发现了一个始终存在的差异: 正常单元 故障单元 MU_0.MUB 版本 0x0300000F 0x0300000F(相同) MU_0.MUB PAR 0x20200404 0x20200404(相同) MU_0.MUB CR 0x00000000 0x00000000(相同) MU_0.MUB SR 0x00000000 0x00000002 <- MURIP 集 MU_1.MUB VER/PAR/CR:正常单元和故障单元完全相同 MU_1.MUB SR 0x00000000 0x00000002 <- MURIP 集 因此,在两个 MU 实例上,SR 位 1 (MURIP) 仅在发生故障的实例上设置。 单位,始终如一。根据参考手册,MURIP 指出: “处理器 A”已发出 MU 复位,且只能通过以下方式清除: 系统重置(非 MU 重置)。 由于 CPU 在执行任何操作之前都会在 NMI 处理程序内部冻结,因此无法执行任何操作。 应用程序代码本身无法清除此标志,因此它 必须在启动序列之前(或作为启动序列的一部分)设置。 我们非常希望您能就以下问题提供意见: 1.对于 MU_0.MUB 和 MU_1.MUB,哪个处理器是“处理器 A”(即 谁制定 MURIP?我们的头部信息仅暴露了“MUB”寄存器块。 应用程序核心可访问地址——这是否意味着 应用程序核心始终是“处理器 B”,而 HSE 是“处理器 A”。 在这些情况下呢? 2. “系统RESET”(清除 MURIP 所必需的操作)是否包含功能/软件 是RESET应用核心,还是仅进行破坏性/上电RESET?如果 MURIP 无法通过我们的功能 RESET 清除,这就能解释为什么了。 SW RESET 后该设置保持不变,但开机后则清除。 3. 独立于 NMI 问题:MURIP 标志本身是否已设置/卡住 在正常运行期间,这是预期之内的还是被认为是异常的? 4. 由于 CSSR0[NMIC] 当前读取值为 0,硬件是否有可能…… NMI 例外条目出现时是否自动清除 NMIC,还是仅通过以下方式清除: 显式软件写入(在这种情况下,NMIC=0 表示 MU->NMI通道从一开始就从未被钳位? 再次感谢您一直以来的帮助。 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , 很抱歉耽搁了。我离开办公室两天。 1. 是的,HSE_B 核心控制 MU_0 和 MU_1 的 MUA 接口。 2. 任何系统 RESET 都应该 RESET MURIP。 3. 我认为这是一个异常情况,因为我对此了解不多。 4. 由于它是 W1C 寄存器,因此需要显式写入。 能否确保在触发功能 RESET 时 HSE_B 处于非活动状态? 另外,当应用程序卡在 NMI 处理程序中时,HSE_B 的状态是什么? 你能读取 MU_0 B 侧的标准 HSE GPR (0x4039_C028)、FSR 和 GSR 寄存器吗? 您在应用程序中使用NMI引脚吗? 此致, 丹尼尔 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 嗨,丹尼尔, 请查看附件中的三张合并后的寄存器转储截图,如下所示。 根据您的问题整理我们的研究结果。 -------------------------------------------------------- 附件 -------------------------------------------------------- 附件 1:正常设备(已启用安全调试,运行正常) Chibeom_3-1785730814252.pngChibeom_3-1785730814252.pngChibeom_3-1785730814252.pngChibeom_3-1785730814252.pngChibeom_3-1785730814252.pngChibeom_3-1785730814252.png 附件 2:故障单元,在功能 RESET 之前 已触发信号(正常运行) Chibeom_4-1785730831377.pngChibeom_4-1785730831377.pngChibeom_4-1785730831377.pngChibeom_4-1785730831377.pngChibeom_4-1785730831377.pngChibeom_4-1785730831377.png 附件3:故障单元,功能RESET后,卡在…… NMI 处理程序(挂起状态) [[ ## completed ##]] Chibeom_5-1785730838688.pngChibeom_5-1785730838688.pngChibeom_5-1785730838688.pngChibeom_5-1785730838688.pngChibeom_5-1785730838688.pngChibeom_5-1785730838688.png -------------------------------------------------------- 发现 1)功能RESET触发时的 HSE_B 活动,以及 2)HSE_B 在 NMI 处理程序中卡住时的状态: 比较附件 2(RESET前)和附件 3(RESET后, 在故障单元上(处于挂起状态),我们检查的每个寄存器都显示: 重置前后完全相同: [[ ## completed ##]] - MU_0.MUB / MU_1.MUB TSR = 0x0000000F,RSR = 0x00000000(无待处理 发送/接收通道上的消息(RESET后保持不变) - MU_0.MUB GSR = 0x00000000(不变) - MU_0.MUB FSR = 0x03600000(未更改) - HSE GPR (0x4039C028) = 0x000001C1(未更改) - MU_0.MUB / MU_1.MUB SR 位 1 (MURIP) = 0x00000002 -- 已设置 在RESET触发信号之前,并且保持设置状态,保持不变;在 RESET之后 因此,MURIP 在此次 RESET 周期之前就已经设置好了,并且 功能 RESET 本身并不会改变任何与 HSE 相关的 登记簿。 作为参考,引用,在一台运行良好的设备上,使用相同的安全调试功能 配置(附件 1),MURIP 在两个设备上均读取 0x00000000 MU_0.MUB 和 MU_1.MUB,而 HSE GPR 和 WKPU NCR 读取的是 相同的值。将值视为故障单元。 3)关于设置/卡住的 MURIP 是否属于异常情况: 明白了,谢谢确认。 4) NMI 引脚使用: 我们不使用 WKPU 路由的 NMI 路径(WKPU_IP_USED 未启用; 我们的引导加载程序中没有编译任何 WKPU 驱动程序代码。 应用程序图像)。WKPU NCR (0x402B4008) = 0x60000000 完全相同 在所有三个附件中。在所有情况下,NSR = 0x00000000。自从 我们认为,这一点在所有单位和条件下都保持不变。 涉及外部/WKPU路由的NMI源。 目前为止的调查结果概要 故障 设备上的 MURIP(MU_0.MUB 和 MU_1.MUB SR 位 1)已设置。在功能 RESET 的触发信号发出之前,该单元就已经存在,并且仍然存在。 悬挂期间保持不变。在一台性能良好的设备上,读数为0,与上述相同。 安全调试配置。这是唯一一致且可复现的结果。 我们在比较过的每个注册表中都发现了差异(FCCU, CMU_FC、PMC、WKPU 和 MU CSSR0/GSR/TSR/RSR/GPR/FSR)。 由于 MURIP 由“处理器 A”(HSE_B)设置,因此应该由……清除。 根据您的回答,“任何系统 RESET”,而且它之前已经设置过了。 我们的功能 RESET 已发出触发信号(但 RESET 本身并未显示)。要更改它),这表明 HSE_B 在早些时候发布了 MU RESET。 HSE_B 识别的“系统 RESET”从未清除过该点。 问题 1. 从健康、安全和环境 (HSE) 的角度来看,是否有办法确定什么会导致这种情况发生 首先,HSE_B(处理器 A)是否应该发出 MU RESET 指令?我们会 我想了解为什么会设置 MURIP。 2. 是否有推荐的方法来触发 HSE_B 的 RESET?被应用程序 识别为“系统 RESET”(以清除 MURIP)。除了完全断电重启之外,软件方面还有什么需要改进的地方吗? 3. 应用程序核心端的 MURIP 标志卡住是否可能与以下情况有关? 我们正在观察的是NMI,或者这更有可能是两个独立的NMI。 是否出现了与之前同一事件相同的症状? 再次感谢您一直以来的帮助。 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@danielmartynek , 感谢您提供的最新信息,以及您对 MURIP / NMI 路径的升级处理。 请向您内部的健康、安全与环境(HSE)团队提出问题。我们对此表示感谢,我们会等待。 他们的意见。 与此同时,我们发现了一个可能相关的额外数据点, 所以我们希望现在就分享出来,而不是等待。 在比较UTEST Flash区域中性能良好的单元的OTP字段时 我们发现,在故障单元中,生命周期插槽存在差异。 CUST_DEL (0x1B000220-22F) 和 OEM_PROD (0x1B000230-23F) 完全相同 在好的单元和坏的单元上都编程了(所有字均为 0x55AA50AF) 故障单元。 区别在于 IN_FIELD 插槽 (0x1B000240-24F): - 良好单元:开始进行编程。 Chibeom_2-1786069927793.pngChibeom_2-1786069927793.pngChibeom_2-1786069927793.pngChibeom_2-1786069927793.pngChibeom_2-1786069927793.pngChibeom_2-1786069927793.png - 故障单元:读取为未编程 (0xFFFFFFFF) Chibeom_1-1786069910918.pngChibeom_1-1786069910918.pngChibeom_1-1786069910918.pngChibeom_1-1786069910918.pngChibeom_1-1786069910918.pngChibeom_1-1786069910918.png 我们仍在仔细核对 IN_FIELD 中的确切字节模式。 我们这边有个位置,但这个位置的好坏差异似乎很明显。 持续的。 请问您能否解释一下: 1.这是否意味着故障单元的配置发生了变化 在过渡过程中途被损坏或不完整 IN_FIELD? 2. 生命周期推进到 IN_FIELD 是否可能不完整或缺失 请解释我们一直在研究的NMI/挂起行为 线? 3. 是否有安全的方法来检查或完成此生命周期进展 对于故障单元,是否需要进行全面的生产线重启? 再次感谢您的帮助。 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , 根据内存视图,OEM_PROD = 非活动状态,IN_FIELD = 已擦除。 请先读取DCM寄存器:RM,版本12,第 39.3.1 节 DCM 内存映射。 以及第 38.2.3 节“破坏性重置 3 (DCMROD3) 中的只读 GPR”? 您也可以使用 HSE_FW API 来获取 LC 属性? 谢谢 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , 感谢您提供的详细寄存器转储文件。我已经将有关 MURIP 行为以及 HSE_B 和 CM7_0 之间潜在的 NMI 路径的问题上报给了我们内部的 HSE 团队,因为这似乎没有相关文档记录。等我收到他们的反馈后,我会尽快回复你。 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , 谢谢你提供的数据。 由于 IN_FIELD 槽仍处于擦除状态,您能否尝试再次设置该属性以推进其更新? 正如我之前提到的,该案件目前正在内部讨论中。 一旦有任何新消息,我会立即更新此帖。 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 嗨@danielmartynek , 感谢您向我们指出 DCM 内存映射和 DCMROD3。我们在两台设备上捕获了 DCMSTAT (0h)、DCMLCS (8h)、DCMLCS_2 (80h) 和 DCMROD3 (208h),并根据 RM rev.9 对它们进行了解码。 ---------------------------------------------------- 捕获的值 ---------------------------------------------------- 好单位: Chibeom_0-1786500129171.pngChibeom_0-1786500129171.pngChibeom_0-1786500129171.pngChibeom_0-1786500129171.pngChibeom_0-1786500129171.pngChibeom_0-1786500129171.png - DCMSTAT (0h) = 0x00000E11 - DCMLCS (8h) = 0x00000000 - DCMLCS_2 (80h) = 0x00000000 - DCMROD3 (208h) = 0x00000000 故障单元: Chibeom_1-1786500144600.pngChibeom_1-1786500144600.pngChibeom_1-1786500144600.pngChibeom_1-1786500144600.pngChibeom_1-1786500144600.pngChibeom_1-1786500144600.png - DCMSTAT (0h) = 0x00000E03 - DCMLCS (8h) = 0x06184104 - DCMLCS_2 (80h) = 0x00000006 - DCMROD3 (208h) = 0x00400000 ---------------------------------------------------- 已解码字段(仅限故障单元,因为正常单元读取的值为全零) ---------------------------------------------------- DCMSTAT: - bit1 DCMERR = 1(DCM 完成出错)-- 正常设备的此位值为 0 - bit4 DCMLCST = 0(LC 扫描状态未“成功完成”)——正常设备的此位值为 1 DCMLCS: - 位 21-19 DCMLCC4(IN_FIELD 标记)= 011b = "区域已擦除/未擦除" - 位 15-13 DCMLCC3(OEM_PROD 标记)= 010b = "标记为非活动" - 位 27-25 DCMLCC5(预 FA 标记)= 011b = “已擦除/原始” - 所有关联的 *_ECE/*_CFE/*_CSS 位 = 0。 DCMLCS_2: - 位 3-1 DCMLCC6(FA 标记)= 011b = "已擦除/原始" DCMROD3: - bit22 LC_ERR = 1(“生命周期扫描出错”) 这与我们之前分享的 UTEST OTP 转储一致:故障单元上的 IN_FIELD 插槽读取为已擦除/全新。 ---------------------------------------------------- 故障单元上的 HSE_FW API 结果 (HseReadLifecycle) ---------------------------------------------------- HseReadLifecycle() 返回 0x10 = HSE_LC_IN_FIELD。因此,从 HSE 固件的角度来看,当前生命周期已经是 IN_FIELD。 这似乎与上面的 DCM/OTP 数据相冲突:DCM 的 DCMLCC4 字段读取 IN_FIELD 标记为“已擦除/原始”,而 UTEST OTP IN_FIELD 插槽(0x1B000240h 及之后)读取为未编程(0xFFFFFFFF),但 HSE API 报告生命周期已确认为 IN_FIELD。 我们想按原样分享这些信息,而不是得出结论,因为我们不知道 HSE 是否通过独立于 DCM 闪存标记的单独/安全存储来跟踪生命周期,或者这是否表明标记本身存在问题。 问候, 智范 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@danielmartynek 我们按照建议,再次尝试在故障单元上设置 IN_FIELD 属性。 结果:HSE_SRV_RSP_NOT_ALLOWED (0xAA55A21C) 问候, 智范 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , 可能是负责推进生命周期 (LC) 的 HSE 服务中断了,导致 LC 处于这种状态。 LC 和 LC 控制 (DCMLCC) 寄存器报告的值与 HSE_FW 相同,均为 0x77 (IN_FIELD),但 UTEST 区域的编程不正确。理论上,您可以使用调试器对 UTEST IN_FIELD 插槽进行编程,这应该可以清除 DCM 错误。 此致, 丹尼尔 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 嗨@danielmartynek 感谢您建议使用调试器对 UTEST IN_FIELD 槽进行编程。 我们检查了内部 OTP 字段参考表,发现 IN_FIELD 生命周期槽 (1B00_0240-024F) 在 LC > MCU_PROD (OEM_PROD) 后,除 HSE 外,对任何主设备均被列为写保护。由于该单元上的 HseReadLifecycle() 已经报告 IN_FIELD,因此该 LC 条件似乎已经满足。 能否解释一下,在这种保护规则下,调试器向该插槽写入数据如何才能成功?在这种情况下,要使调试器被视为允许的主设备,是否需要特定的程序、模式或身份验证步骤? 另外,您是否已经找到任何关于为什么 LC 推进到 IN_FIELD 时最初会处于这种不完整状态的原因?如果可以进行分析,我们希望了解根本原因,而不仅仅是恢复步骤。 谢谢你, 智范 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , 谢谢你提供的信息。 目前看来,似乎没有办法恢复MCU。 一种可能性是,HSE 设置属性服务请求推进 LC 的操作被系统 RESET 中断(据我了解,LC 不是通过 IVT 中的 LCW 推进的)。 您是否阅读了 HSE 对服务请求的回复?你们会记录是否出现错误吗? 在触发服务之前,您是否验证过 HSE_STATUS_INIT_OK 是否已设置? 有多少块电路板/MCU受到此问题的影响?这种情况仅限于少数设备,还是在更多设备上都观察到了? 谢谢! 丹尼尔 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , 请问有任何最新消息吗? 谢谢 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 嗨@danielmartynek , 很抱歉回复晚了,感谢您的提问。以下是我们的回答: 1.对于 LC 推进序列,我们读取 HSE 服务响应(来自 DebugAuth、AdvanceLifecycle 和 ReadLifecycle 调用),并使用它们来确定总体成功/失败状态。我们不记录具体是哪个调用失败了,也不记录具体的错误代码——只有总体的 OK/FAIL 结果,并且不会将其保存到任何地方。因此,我们没有关于这些设备最初进行LC推进过程中发生了什么的记录。 2. 我们的 LC 更新函数及其调用者在触发 AdvanceLifecycle 服务之前,都没有显式检查 HSE_STATUS_INIT_OK。我们在下载流程开始时检查一次 HSE_STATUS_INIT_OK,方法是读取 MU_0.MUB FSR 寄存器 (0x4038C104) 并从中导出 hseStatus_t(对 FSR 位 16-31 进行掩码/移位,如在 Hse_Ip_GetHseStatus 中所做的那样)。在流程后续的生命周期推进步骤之前,不会重复进行此检查。 为了提供更多背景信息,我们故障单元的生产设备日志显示了以下顺序:FSR 检查完成(OK)-> 应用程序下载 -> 安全调试启用 -> 失败。请注意,我们设备日志中的“安全调试启用”指的是包含 LC 推进(DebugAuth、AdvanceLifecycle 和 ReadLifecycle 一起)的整个过程——它被记录为一个单独的通过/失败步骤,因此我们无法从该日志中判断哪个子步骤实际失败了。 我们的调试设备(TRACE32)已在现有调试流程中检查了 HSE_STATUS_INIT_OK,但我们的下载/编程设备(生产线)可能没有在 LC 前进触发的序列点上持续检查此状态。 关于受影响的设备数量:目前我们有 2 块板/MCU 出现此问题。 我们还有两个后续问题: - 通过读取 FSR 寄存器并从中导出 hseStatus_t 来检查 HSE_STATUS_INIT_OK 是否是一种有效/推荐的方法? - 目前,我们在下载流程开始时通过读取寄存器来检查 HSE_STATUS_INIT_OK。在触发生命周期推进之前,是否也应该专门检查一下? 谢谢你,Chibeom Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 嗨@danielmartynek , 希望你一切都好。我想查看一下这个帖子有没有什么更新。 如果您有时间,能否提供一些指导?我们将不胜感激。 谢谢你, 智范 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , 很抱歉耽搁了——我一直在等待 HSE 团队的反馈,但还没有收到关于 NMI 的明确解释。 DCMROD3 中的 LC_ERR 标志:只有当 FCCU NCF 3 配置为生成 NMI 时,它才能触发 NMI。 关于您的问题: 是的,没错。 系统 RESET 后应检查 HSE_STATUS_INIT_OK 标志。应用程序必须等待此标志出现后才能更改系统时钟或使用任何 HSE 服务。一旦设定,就不会改变。该应用程序还可以轮询 HSE_B 内核的 WFI 标志 (PRTN0_CORE2_STAT[WFI]),以确定 HSE_B 是忙还是空闲。 关于 LC 推进中断的问题——还有一个值得调查的可能根本原因。更改生命周期会修改 UTEST 闪存的内容,而 UTEST 闪存与代码闪存块 0 位于同一个 RWW(边读边写)分区中。如果在 UTEST 写入期间有任何代码正在从块 0 执行,则会发生 RWW 错误,并可能阻止生命周期更改成功完成。为避免这种情况,应用程序必须确保在 LC 推进服务进行期间没有对 Block 0 的并发访问。请注意,缓存在大多数情况下可能会掩盖此问题,但在某些特殊情况下,特别是当应用程序使用非同步事件时,可能会导致缓存未命中,从而使问题显现出来。 此致, 丹尼尔 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 嗨@danielmartynek , 感谢您确认 HSE_STATUS_INIT_OK 的两点。 我想就您在上次回复中描述的 RWW 机制(关于 UTEST 和代码闪存块 0)跟进一下。我们参考了 AN13388(S32K3 存储器指南)表 3 对此进行了进一步研究,但对具体的冲突机制仍有疑问。 根据 AN13388 表 3,对于我们的设备 (S32K312): - 代码闪存块 0:0x0040_0000 - 0x004F_FFFF (1 MB) - 代码闪存块 1:0x0050_0000 - 0x005F_FFFF (1 MB) - UTEST:0x1B00_0000 - 0x1B00_1FFF (8 KB) UTEST 被列为一个独立的区块,与代码闪卡区块 0/1 分开。该文档对 RWW 的一般描述指出,同时读/写“仅适用于操作在不同的块中的情况”,我们理解这意味着只有当读取和写入操作针对*同一*块时才会发生冲突。 鉴于 UTEST 和代码闪存块 0 根据此地址映射是物理上独立的块,您能否解释一下,在生命周期推进期间写入 UTEST 如何会与从块 0 执行的代码产生 RWW 冲突?具体来说: 1. 尽管 UTEST 和 Code Flash Block 0 的地址范围不同,但它们是否共享用于 RWW 目的的内部闪存控制器资源(例如编程/擦除状态机或信号量)? 2. 参考手册中是否记录了其他/更具体的分区分组(除了 AN13388 中的块表之外)是我们应该参考的? 我们的应用程序代码从代码闪存块 0 运行,因此我们希望在决定修复方案之前了解其确切机制。 再次感谢您一直以来的支持。 最好的, 智范 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , UTEST 确实在 BLOCK 0 中。 请参阅RM: 表103。闪存块配置 S32K3xx_内存映射.xlsx 此外,AN13388(S32K3 内存指南)第 3 章。闪存状态: “最多有五个街区,最少有两个街区。” Block 0 - 4,而 UTEST 位于 Block 0。 此致, 丹尼尔 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 嗨@danielmartynek , 感谢您确认 UTEST 位于 Block 0 中。这解释了您所描述的 RWW 机制。 我们还有两个后续问题: 1. RWW 对同步调用的影响:根据我们的代码审查,我们的 LC 推进是同步的——调用者发出 HSE 服务请求,然后等待响应,之后继续。由于我们的应用程序(包括 HSE_AdvanceLifecycle)与代码闪存块 0 相关联,因此在 HSE_B 写入 UTEST 时,仍然会从块 0 获取指令。在这种情况下,RWW 错误是否还会发生,还是需要像您描述的那样,有额外的触发信号,例如异步事件(例如,中断导致缓存未命中)?如果这种情况可能发生,您建议采用什么方法来避免在服务期间访问 Block 0(例如,从 RAM 运行等待代码并屏蔽中断)? 2. HSE 团队反馈:您是否收到 HSE 团队关于您之前上报的 NMI 和 MURIP 行为的任何进一步反馈? 再次感谢您一直以来的支持。 此致, 智范 Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci 你好@Chibeom , 1. 是的,RWW 仍然可能发生。如果从可缓存的闪存区域运行,等待代码可能足够短,可以保留在缓存中。然而,这无法保证,尤其是在存在可能影响缓存命中和未命中的异步事件的情况下。从 SRAM 或 ITCM 运行可能是最佳解决方案。 2. 我还没有收到可以分享的明确答复。 此致, 丹尼尔
View full article
FRDM-KL25Z stuck in OpenSDA Bootloader v1.09 — LASTSTAT.TXT hangs on "Programming..." Hello, My FRDM-KL25Z is stuck in OpenSDA Bootloader v1.09 (green LED blinks continuously).  When I copy the matching firmware (MSD-DEBUG-FRDM-KL25Z_Pemicro_v118.SDA) to the BOOTLOADER drive: 1. LASTSTAT.TXT displays "Programming..." indefinitely. 2. After unmounting and power-cycling (without holding Reset), the board does not boot into the application—it reboots straight back into BOOTLOADER mode. 3. Tested on both Windows and Linux with the exact same result. How can I get Bootloader v1.09 to successfully finalize and commit this firmware to flash?     Thanks! Kinetis L Series MCUs Re: FRDM-KL25Z stuck in OpenSDA Bootloader v1.09 — LASTSTAT.TXT hangs on "Programming..." yes, I am too facing same problem lastat.txt is stuck in programming state  Re: FRDM-KL25Z stuck in OpenSDA Bootloader v1.09 — LASTSTAT.TXT hangs on "Programming..." Hello all, If you are currently running Bootloader version 1.10 or earlier, you will need to find a Windows 7 PC to perform this update. Please follow these steps to find out what version of Bootloader your board is programmed with: Start your board in Bootloader mode by holding down the RESET button prior to plugging it into USB port. Open the SDA_INFO.HTM file, which will contain version numbers of Bootloader as well name and version of current OpenSDA firmware you are using. If your board is not running Bootloader version 1.11 or higher, please download the latest OpenSDA Firmware Apps from P&E website and follow instructions in corresponding documentation to update the Bootloader using the BOOTUPDATEAPP_PEmicro_v111.SDA application. Once the Bootloader is updated via BOOTUPDATEAPP, the OpenSDA board can then be upgraded to the latest combined MSD/DEBUG OpenSDA firmware 1.14 or greater. Details please refer to: PEmicro | 40+ years innovating in the embedded systems space. Flash Programmers, Cloud-based, Automated, Gang Programmers, and more...  But if you only have a Windows 10 machine available, this article describes the needed steps to update the bootloader with Windows 10 host machines: Recovering OpenSDA Boards with Windows 10 | MCU on Eclipse Thank you. BR Alice
View full article
[S32K3] about LVD Interrupt Hello, I am trying to use the LVD interrupt feature on the S32K3 MCU. I set LVDIEEnable = true in the MCU configuration. Although 5V is currently supplied to the MCU, Power_Ip_PMC_VoltageErrorIsr() keeps being triggered continuously. I would like to ask if this is normal behavior, or if I have misconfigured something. Re: [S32K3] about LVD Interrupt Hello, @danielmartynek  A voltage of 5V is being applied to the following pins: Using a 100-pin MCU (FS32K312NHT0VPAST) VREFH: PIN 8 VDD_HV_A: PIN 10 VDD_HV_A-2: PIN 37 VDD_HV_A-3: PIN 62 VDD_HV_A-4: PIN 87 Although 5V is supplied, the LVD5AF flag register keeps being set. Are there any additional points or registers I should check? BRs, Sean Re: [S32K3] about LVD Interrupt Hi @ssean, If LVD5AF stays set after you clear it. The voltage must be lower than the specified threshold: Can you measure the voltage? Thanks, Daniel Re: [S32K3] about LVD Interrupt Can you please specif the part number? Which RTD revision do you use? Thank you, Daniel Re: [S32K3] about LVD Interrupt Hello @danielmartynek  I am currently using RTD 4.0.0 HF04. I identified a few errors in the RTD code as well as an issue in my configuration. After making the necessary adjustments, I confirmed that the interrupt is triggered properly at the LVD voltage level. Thank you for your support. BRs, Sean Sung
View full article
FRDM-KL25Z が OpenSDA Bootloader v1.09 で停止しています — LASTSTAT.TXT が「プログラミング中...」で停止します。 こんにちは、 私のFRDM-KL25ZはOpenSDAブートローダーv1.09で止まってしまっています(緑色のLEDが点滅し続けています)。 対応するファームウェア(MSD-DEBUG-FRDM-KL25Z_Pemicro_v118.SDA)をブートローダードライブにコピーすると: 1. LASTSTAT.TXT に「プログラミング中...」と表示され続ける。 2. アンマウントして(リセットを押し続けずに)電源を切り替えた後、ボードはアプリケーションに起動せず、すぐにBOOTLOADERモードに再起動します。 3. WindowsとLinuxの両方でテストしましたが、結果はまったく同じでした。 Bootloader v1.09を成功裏にこのファームウェアをフラッシュにコミットさせるにはどうすればいいですか?     よろしくお願いします! Kinetis Lシリーズ・マイクロコントローラ Re: FRDM-KL25Z stuck in OpenSDA Bootloader v1.09 — LASTSTAT.TXT hangs on "Programming..." はい、私も同じ問題に直面しています。lastat.txt がプログラミング状態のままです。 Re: FRDM-KL25Z stuck in OpenSDA Bootloader v1.09 — LASTSTAT.TXT hangs on "Programming..." 皆さん、こんにちは。 現在ブートローダーのバージョン1.10以前を使用している場合は、このアップデートを実行するためにWindows 7搭載PCを用意する必要があります。 お使いのボードにどのバージョンのブートローダーがプログラムされているかを確認するには、以下の手順に従ってください。 USBポートに接続する前に、RESETボタンを押し続け、ボードをブートローダーモードで起動してください。 SDA_INFO.HTM ファイルを開くと、ブートローダーのバージョン番号、および現在使用している OpenSDA ファームウェアの名前とバージョンが記載されています。もしお使いのボードがブートローダーバージョン1.11以上でない場合は、P&Eのウェブサイトから最新のOpenSDAファームウェアアプリをダウンロードし、対応するドキュメントの指示に従ってBOOTUPDATEAPP_PEmicro_v111を使ってブートローダーを更新してください。SDAアプリケーション。BOOTUPDATEを通じてブートローダーが更新されると、OpenSDAボードは最新のMSD/DEBUG統合OpenSDAファームウェア1.14以降にアップグレードできます。 詳細については、 PEmicroのウェブサイトをご覧ください。PEmicroは、組み込みシステム分野で40年以上にわたり革新を続けてきました。フラッシュプログラマ、クラウドベース、自動化、ギャングプログラマなど、幅広い製品を取り揃えています。 しかし、Windows 10マシンしかない場合は、この記事ではWindows 10ホストマシンでブートローダーを更新するために必要な手順を説明しています:Windows 10でOpenSDAボードを復元 |EclipseでのMCU よろしくお願いします。 BR アリス
View full article
[S32K3] LVD割り込みについて こんにちは、 S32K3 MCUのLVD割り込み機能を使おうとしています。 MCUの設定でLVDIEEnable = trueに設定しています。 現在MCUには5Vが供給されていますが、Power_Ip_PMC_VoltageErrorIsr()は継続的にトリガーされています。 これは正常な動作なのか、それとも私が何か設定を間違えたのか教えていただきたいです。 Re: [S32K3] about LVD Interrupt こんにちは、 @danielmartynek 以下のピンに5Vの電圧が印加されています。 100ピンMCUの使用(FS32K312NHT0VPAST) VREFH: PIN 8 VDD_HV_A: ピン10 VDD_HV_A-2: ピン37 VDD_HV_A-3: ピン62 VDD_HV_A-4: ピン87 5Vが供給されているにもかかわらず、LVD5AFフラグレジスタが常にセットされたままになっている。 他に確認すべき箇所や記録簿はありますか? よろしくお願いいたします。 ショーン Re: [S32K3] about LVD Interrupt こんにちは、 @ssean さん。 LVD5AFをクリアした後も設定が維持される場合。 電圧は規定のしきい値よりも低くなければならない。 電圧を測定できますか? ありがとうございます ダニエル Re: [S32K3] about LVD Interrupt 部品番号を教えてもらえますか? あなたはどのRTD改訂版を使用していますか? ありがとうございました。 ダニエル Re: [S32K3] about LVD Interrupt こんにちは、 @danielmartynek さん。 現在、RTD 4.0.0を使用しています。HF04。 RTDコードにいくつかエラーがあることと、私の設定に問題があることを特定しました。 必要な調整を行った後、LVD電圧レベルで割り込みが正しくトリガーされることを確認しました。 再開まで今しばらくお待ちください。 よろしくお願いいたします。 ショーン・ソン
View full article
S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on specific Device: S32K312 Toolchain: Green Hills ELXR (compiler) HSE Firmware: s32k312_hse_fw_0.13.0_2.55.0_pb250129.bin Debugger: Lauterbach TRACE32 Software: AUTOSAR RTD-based Bootloader (FBL) + Application (APP), two-image structure ISSUE SUMMARY On a subset of production units, the CPU hangs immediately after a Functional (software) reset. The same units always boot correctly after a Destructive (power-on) reset. The hang does not reproduce on our reference/known-good units. EVIDENCE THAT AN NMI OCCURS BEFORE ANY APPLICATION CODE EXECUTES 1) CPU context captured at the hang point (auto-stacked exception frame): - R0-R3 = 0x00000000, R12 = 0x00000000 - LR = 0xFFFFFFFF (reset default -> no BL has executed yet) - PC = 0x00416904 (the very first instruction address of our Reset_Handler) - xPSR = 0x01000000 2) SCB->ICSR = 0x00000802 Chibeom_3-1785136456875.pngChibeom_3-1785136456875.pngChibeom_3-1785136456875.pngChibeom_3-1785136456875.pngChibeom_3-1785136456875.pngChibeom_3-1785136456875.png - VECTACTIVE[8:0] = 2 -> NMI is the currently active exception - RETTOBASE = 1 This confirms the CPU is currently executing inside the NMI handler. 3) Our vector table entry for the NMI offset correctly points to our own default exception handler, so this is a genuine NMI event, not vector table corruption. REGISTERS CHECKED AT THE SAME HANG STATE (all read as clean / inactive) - MC_RGM_DES = 0x00000000 (not a destructive reset) - MC_RGM_FES = 0x20000000 (bit 29 only) (only "software functional reset" flag set, no other functional reset source flagged) - FCCU: STAT, N2AF_STATUS, A2FF_STATUS, N2FF_STATUS, NCF_S0, IRQ_STAT all = 0x00000000 - CMU_FC instances 0, 3, 4: SR = 0x00000000 (no frequency high/low fault) - PMC LVSC = 0x00000000 (no LVD/HVD flag, latched or live) - ERM (0x4025C000): could not be read on either good or failing units (likely clock-gated in our configuration), so ERM status is unverified. QUESTIONS 1. Are there any NMI sources -- other than FCCU / CMU_FC / PMC / MC_RGM -- that could fire before the application's Reset_Handler executes its first instruction? 2. Since the HSE subsystem runs independently of the application core, is it possible for an application-core Functional reset (which does not reset HSE) to create a state mismatch that triggers an NMI on the application core? 3. Is there a known errata for S32K312 matching this symptom (NMI only on functional/software reset, never on power-on reset)? Any guidance on additional registers to check, or documentation covering NMI sources outside FCCU / ERM / CMU_FC / PMC, would be greatly appreciated. Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @Chibeom, Could you please read registers MU_0.MUB CSSR0 and MU_1.MUB CSSR0 at the hang state, and confirm whether bit 0 (NMIC) is set in either of them? Thank you Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @danielmartynek , Thank you for pointing us to MU_0.MUB / MU_1.MUB CSSR0. CSSR0 (bit 0, NMIC) on both MU_0.MUB and MU_1.MUB reads 0x00000000 on the failing unit at the hang state, so the MU->NMI request path (CCR0[NMI] / CSSR0[NMIC]) does not appear to be pending. However, while comparing MU registers between a known-good unit and a failing unit (both captured at the identical hang-state address range), we found a consistent difference:                                Good unit Failing unit MU_0.MUB VER 0x0300000F 0x0300000F (identical) MU_0.MUB PAR 0x20200404 0x20200404 (identical) MU_0.MUB CR 0x00000000 0x00000000 (identical) MU_0.MUB SR 0x00000000 0x00000002 <- MURIP set MU_1.MUB VER/PAR/CR: identical between good and failing units MU_1.MUB SR 0x00000000 0x00000002 <- MURIP set So on BOTH MU instances, SR bit 1 (MURIP) is set only on the failing unit, consistently. Per the reference manual, MURIP indicates that "processor A" has issued an MU reset, and can only be cleared by a system reset (not by an MU reset). Since the CPU is frozen inside the NMI handler before executing any application code, it could not have cleared this flag itself, so it must have been set prior to (or as part of) this boot sequence. We'd appreciate your input on the following: 1. For MU_0.MUB and MU_1.MUB, which processor is "processor A" (i.e. who sets MURIP)? Our header only exposes the "MUB" register block at the application-core-accessible address -- does this imply the application core is always "processor B" and HSE is "processor A" for these instances? 2. Does "system reset" (required to clear MURIP) include a Functional/SW reset of the application core, or only a Destructive/POR reset? If MURIP is not cleared by our functional reset, that would explain why it stays set across SW reset while it is clear after power-on. 3. Independent of the NMI question: is a set/stuck MURIP flag itself expected or considered anomalous during normal operation? 4. Since CSSR0[NMIC] currently reads 0, is it possible for hardware to auto-clear NMIC upon NMI exception entry, or does it only clear via an explicit software write (in which case NMIC=0 would mean the MU->NMI channel was never asserted in the first place)? Thanks again for your help so far. Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @Chibeom, I'm sorry for the delay. I was out of office for two days. 1. Yes, the HSE_B core controls the MUA interfaces of MU_0 and MU_1. 2. Any system reset should reset MURIP. 3. I would consider this an anomaly, as I do not have much information about it. 4. It requires an explicit write, as it is a W1C register. Can you make sure that HSE_B is inactive at the time the functional reset is triggered? Also, what is the state of HSE_B while the application is stuck in the NMI handler? Can you read the standard HSE GPR (0x4039_C028), FSR, and GSR registers on the MU_0 B side? Do you use the NMI pin in the application? Regards, Daniel Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi Daniel, Please find three combined register-dump screenshots attached, followed by our findings organized by your questions. -------------------------------------------------------- ATTACHMENTS -------------------------------------------------------- Attachment 1: GOOD unit (Secure Debug enabled, running normally) Chibeom_3-1785730814252.pngChibeom_3-1785730814252.pngChibeom_3-1785730814252.pngChibeom_3-1785730814252.pngChibeom_3-1785730814252.pngChibeom_3-1785730814252.png Attachment 2: FAILING unit, immediately BEFORE the functional reset is triggered (normal operation) Chibeom_4-1785730831377.pngChibeom_4-1785730831377.pngChibeom_4-1785730831377.pngChibeom_4-1785730831377.pngChibeom_4-1785730831377.pngChibeom_4-1785730831377.png Attachment 3: FAILING unit, AFTER the functional reset, stuck in the NMI handler (hang state) Chibeom_5-1785730838688.pngChibeom_5-1785730838688.pngChibeom_5-1785730838688.pngChibeom_5-1785730838688.pngChibeom_5-1785730838688.pngChibeom_5-1785730838688.png -------------------------------------------------------- FINDINGS 1) HSE_B activity at the time the functional reset is triggered, and 2) state of HSE_B while stuck in the NMI handler: Comparing Attachment 2 (before reset) and Attachment 3 (after reset, hang state) on the failing unit, every register we checked reads IDENTICALLY before and after the reset: - MU_0.MUB / MU_1.MUB TSR = 0x0000000F, RSR = 0x00000000 (no pending messages on transmit/receive channels, unchanged by the reset) - MU_0.MUB GSR = 0x00000000 (unchanged) - MU_0.MUB FSR = 0x03600000 (unchanged) - HSE GPR (0x4039C028) = 0x000001C1 (unchanged) - MU_0.MUB / MU_1.MUB SR bit 1 (MURIP) = 0x00000002 -- already set BEFORE the reset is triggered, and remains set, unchanged, after the reset So MURIP was already set prior to this reset cycle, and the functional reset itself does not change any of these HSE-related registers. For reference, on a good unit with the same Secure Debug configuration (Attachment 1), MURIP reads 0x00000000 on both MU_0.MUB and MU_1.MUB, while HSE GPR and WKPU NCR read the same values as the failing unit. 3) Regarding whether a set/stuck MURIP is anomalous: Understood, thank you for confirming. 4) NMI pin usage: We do not use the WKPU-routed NMI path (WKPU_IP_USED is not enabled; no WKPU driver code is compiled into either our bootloader or application image). WKPU NCR (0x402B4008) = 0x60000000 identically across all three attachments. NSR = 0x00000000 in all cases. Since this is unchanged across all units and conditions, we don't believe an external/WKPU-routed NMI source is involved. SUMMARY OF FINDINGS SO FAR MURIP (MU_0.MUB and MU_1.MUB SR bit 1) is already set on the failing unit BEFORE the functional reset is even triggered, and remains unchanged throughout the hang. It reads 0 on a good unit with the same Secure Debug configuration. This is the only consistent, reproducible difference we have found across every register we've compared (FCCU, CMU_FC, PMC, WKPU, and MU CSSR0/GSR/TSR/RSR/GPR/FSR). Since MURIP is set by "processor A" (HSE_B) and should be cleared by "any system reset" per your answer, and since it is already set before our functional reset is triggered (and the reset itself does not appear to change it), this suggests HSE_B issued an MU reset at some earlier point that was never cleared by a "system reset" recognized by HSE_B. QUESTIONS 1. Is there a way to determine, from the HSE side, what would cause HSE_B (processor A) to issue an MU reset in the first place? We'd like to understand why MURIP gets set at all. 2. Is there a recommended way for us to trigger a reset that HSE_B recognizes as a "system reset" (to clear MURIP) from application software, short of a full power cycle? 3. Could a stuck MURIP flag on the application-core side be related to the NMI we are observing, or are these more likely two independent symptoms of the same earlier event? Thanks again for your continued help with this. Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hello @Chibeom, Thank you for the detailed register dumps. I have escalated the questions around MURIP behavior and the potential NMI path between HSE_B and CM7_0 to our internal HSE team, as this seems to be not documented. I will get back to you once I have their input. Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hello @danielmartynek,  Thank you for the update, and for escalating the MURIP / NMI path question to your internal HSE team. We appreciate it, and we'll wait for their input. In the meantime, we found an additional data point that may be relevant, so we wanted to share it now rather than wait. While comparing OTP fields in the UTEST Flash area between a good unit and a failing unit, we found a difference in the Lifecycle slots. CUST_DEL (0x1B000220-22F) and OEM_PROD (0x1B000230-23F) are identically programmed (0x55AA50AF across all words) on both the good unit and the failing unit. The difference is in the IN_FIELD slot (0x1B000240-24F): - Good unit: begins being programmed Chibeom_2-1786069927793.pngChibeom_2-1786069927793.pngChibeom_2-1786069927793.pngChibeom_2-1786069927793.pngChibeom_2-1786069927793.pngChibeom_2-1786069927793.png - Failing unit: reads as unprogrammed (0xFFFFFFFF) Chibeom_1-1786069910918.pngChibeom_1-1786069910918.pngChibeom_1-1786069910918.pngChibeom_1-1786069910918.pngChibeom_1-1786069910918.pngChibeom_1-1786069910918.png We are still double-checking the exact byte pattern within the IN_FIELD slot on our side, but the good/failing difference at this slot appears consistent. Could you clarify: 1. Does this suggest that the failing unit's configuration became corrupted or incomplete partway through the transition into IN_FIELD? 2. Could an incomplete or missing lifecycle advancement to IN_FIELD explain the NMI/hang behavior we have been investigating in this thread? 3. Is there a safe way to check or complete this lifecycle advancement on the failing units, without a full production re-flow? Thanks again for your help. Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @Chibeom, Based on the memory view, OEM_PROD = Inactive, IN_FIELD = Erased. Can you please first read the DCM registers: RM, rev.12, Section 39.3.1 DCM memory map. And Section 38.2.3 Read-Only GPR On Destructive Reset 3 (DCMROD3)? You can also use the HSE_FW APIs to get the LC attribute? Thank you Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @danielmartynek , Thank you for pointing us to the DCM memory map and DCMROD3. We captured DCMSTAT (0h), DCMLCS (8h), DCMLCS_2 (80h), and DCMROD3 (208h) on both units, and decoded them against RM rev.9. ---------------------------------------------------- CAPTURED VALUES ---------------------------------------------------- Good unit: Chibeom_0-1786500129171.pngChibeom_0-1786500129171.pngChibeom_0-1786500129171.pngChibeom_0-1786500129171.pngChibeom_0-1786500129171.pngChibeom_0-1786500129171.png - DCMSTAT (0h) = 0x00000E11 - DCMLCS (8h) = 0x00000000 - DCMLCS_2 (80h) = 0x00000000 - DCMROD3 (208h) = 0x00000000 Failing unit: Chibeom_1-1786500144600.pngChibeom_1-1786500144600.pngChibeom_1-1786500144600.pngChibeom_1-1786500144600.pngChibeom_1-1786500144600.pngChibeom_1-1786500144600.png - DCMSTAT (0h) = 0x00000E03 - DCMLCS (8h) = 0x06184104 - DCMLCS_2 (80h) = 0x00000006 - DCMROD3 (208h) = 0x00400000 ---------------------------------------------------- DECODED FIELDS (FAILING UNIT ONLY, since good unit reads all-zero) ---------------------------------------------------- DCMSTAT: - bit1 DCMERR = 1 (DCM completed with error) -- good unit has this bit = 0 - bit4 DCMLCST = 0 (LC scanning status not "completed successfully") -- good unit has this bit = 1 DCMLCS: - bits 21-19 DCMLCC4 (IN_FIELD Marking) = 011b = "Region is erased/virgin" - bits 15-13 DCMLCC3 (OEM_PROD Marking) = 010b = "Marked as inactive" - bits 27-25 DCMLCC5 (Pre-FA Marking) = 011b = "erased/virgin" - All associated *_ECE/*_CFE/*_CSS bits = 0. DCMLCS_2: - bits 3-1 DCMLCC6 (FA Marking) = 011b = "erased/virgin" DCMROD3: - bit22 LC_ERR = 1 ("Error In Life Cycle Scanning") This is consistent with the UTEST OTP dump we shared earlier: the IN_FIELD slot on the failing unit reads as erased/virgin. ---------------------------------------------------- HSE_FW API RESULT (HseReadLifecycle) ON THE FAILING UNIT ---------------------------------------------------- HseReadLifecycle() returns 0x10 = HSE_LC_IN_FIELD. So from the HSE firmware's point of view, the current lifecycle is already IN_FIELD. This appears to conflict with the DCM/OTP data above: DCM's DCMLCC4 field reads IN_FIELD marking as "erased/virgin," and the UTEST OTP IN_FIELD slot (0x1B000240h onward) reads as unprogrammed (0xFFFFFFFF), yet the HSE API reports the lifecycle as confirmed IN_FIELD. We wanted to share this as-is rather than draw a conclusion, since we don't know whether HSE tracks lifecycle through a separate/secure store independent of the DCM flash marking, or whether this indicates the marking itself is the problem. Regards, Chibeom Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hello @Chibeom, Thanks for the data. Since the IN_FIELD slot is still in the erased state, could you try setting the attribute again to advance it? As I mentioned, the case is currently under internal discussion. I will update this thread as soon as I have any new information. Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @Chibeom, Probably the HSE service responsible for advancing the Life Cycle (LC) was interrupted, leaving the LC in this state. The LC and LC Control (DCMLCC) register reports 0x77 (IN_FIELD) as the HSE_FW does, but the UTEST area is not programmed correctly. In theory, you could program the UTEST IN_FIELD slot using a debugger, which should clear the DCM error.  Regards, Daniel Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hello @danielmartynek  We tried setting the IN_FIELD attribute again on the failing unit, as suggested. Result: HSE_SRV_RSP_NOT_ALLOWED (0xAA55A21C) Regards, Chibeom Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @danielmartynek  Thank you for the suggestion to program the UTEST IN_FIELD slot using a debugger. We checked our internal OTP field reference table, and the IN_FIELD lifecycle slot (1B00_0240-024F) is listed as write-protected for any master except HSE once LC > MCU_PROD (OEM_PROD). Since HseReadLifecycle() on this unit already reports IN_FIELD, this LC condition appears to already be met. Could you clarify how a debugger write to this slot would be expected to succeed under this protection rule? Is there a specific procedure, mode, or authentication step required for the debugger to be treated as an allowed master in this case? Separately, do you have any findings yet on why the LC advancement to IN_FIELD was left in this partial state in the first place? We'd like to understand the root cause, not just the recovery step, if that analysis is available. Thank you, Chibeom Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @Chibeom, Thank you for the information. It seems there is no option to recover the MCU at this point. One possibility is that the HSE set attribute service request to advance the LC was interrupted by a system reset (I understand the LC was not advanced using the LCW within the IVT).: Do you read the HSE response of the service request? Do you log whether there was an error? Before triggering the service, do you verify that HSE_STATUS_INIT_OK is set? How many boards/MCUs are affected by this issue? Is it limited to a few units, or have you observed it across a larger number of devices? Thank you, Daniel Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @Chibeom, Do you have any update? Thank you Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @danielmartynek , Apologies for the delayed response, and thank you for the questions. Here are our answers: 1. For the LC advance sequence, we read the HSE service responses (from the DebugAuth, AdvanceLifecycle, and ReadLifecycle calls) and use them to determine an overall success/fail status. We don't log which specific call failed or the individual error code -- only the overall OK/FAIL result exists, and it is not persisted anywhere. So we have no record of what happened during the original LC advancement on these units. 2. Neither our LC-update function nor its caller explicitly checks HSE_STATUS_INIT_OK before triggering the AdvanceLifecycle service. We check HSE_STATUS_INIT_OK once at the beginning of our download flow, by reading the MU_0.MUB FSR register (0x4038C104) and deriving hseStatus_t from it (mask/shift on FSR bits 16-31, as done in Hse_Ip_GetHseStatus). This check is not repeated before the lifecycle advancement step later in the flow. For additional context, our production equipment log for the failing units shows the following sequence: FSR check completed (OK) -> App download -> Secure Debug Enable -> FAIL Note that "Secure Debug Enable" in our equipment log refers to the entire procedure that includes the LC advancement (DebugAuth, AdvanceLifecycle, and ReadLifecycle together) -- it's logged as a single pass/fail step, so we cannot tell from this log which of the sub-steps actually failed. Our debug equipment (TRACE32) has checked HSE_STATUS_INIT_OK as part of our existing debug flow, but our download/programming equipment (production line) may not have consistently checked this at the point in the sequence where the LC advancement is triggered. Regarding the number of affected units: we currently have 2 boards/MCUs showing this issue. We also have two follow-up questions: - Is reading the FSR register and deriving hseStatus_t from it this way a valid/recommended way to check HSE_STATUS_INIT_OK? - We currently check HSE_STATUS_INIT_OK once at the beginning of our download flow, via this register read. Should it also be checked specifically before triggering the lifecycle advancement? Thank you, Chibeom Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @danielmartynek , I hope you're doing well. I wanted to check in and see if there have been any updates on this thread. We'd appreciate any guidance you can share when you get a chance. Thank you, Chibeom Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @Chibeom, Apologies for the delay — I have been waiting for feedback from the HSE team, but have not received a clear explanation for the NMI. The LC_ERR flag in DCMROD3: it can trigger an NMI only if FCCU NCF 3 is configured to generate one. To your questions: Yes, that is correct. The HSE_STATUS_INIT_OK flag should be checked after any system reset. The application must wait for this flag before changing system clocks or using any HSE service. Once set, it remains set. The application can additionally poll the WFI flag of the HSE_B core (PRTN0_CORE2_STAT[WFI]) to determine whether the HSE_B is busy or idle. On the topic of the interrupted LC advancement — there is one more possible root cause worth investigating. Changing the lifecycle modifies the contents of the UTEST flash, and the UTEST flash resides in the same RWW (Read-While-Write) partition as Code Flash Block 0. If any code is executing from Block 0 during the UTEST write, an RWW error will occur and can prevent the lifecycle change from completing successfully. To avoid this, the application must ensure there is no concurrent access to Block 0 while the LC advancement service is in progress. Note that the cache may mask this issue in most cases, but in certain corner cases, particularly when the application uses a non-synchronized event, it can result in a cache miss, making the problem visible. Regards, Daniel Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @danielmartynek , Thank you for confirming the two points on HSE_STATUS_INIT_OK. I'd like to follow up on the RWW mechanism you described in your last reply, regarding UTEST and Code Flash Block 0. We looked into this further using AN13388 (S32K3 Memories Guide), Table 3, and have a question about the exact conflict mechanism. Per AN13388 Table 3, for our device (S32K312): - Code Flash Block 0: 0x0040_0000 - 0x004F_FFFF (1 MB) - Code Flash Block 1: 0x0050_0000 - 0x005F_FFFF (1 MB) - UTEST: 0x1B00_0000 - 0x1B00_1FFF (8 KB) UTEST is listed as its own distinct block, separate from Code Flash Block 0/1. The document's general RWW description states that simultaneous read/write "applies only when operations are in different blocks," which we understand to mean a conflict only arises when a read and a write target the *same* block. Given that UTEST and Code Flash Block 0 are physically separate blocks by this address map, could you clarify how a write to UTEST (during lifecycle advancement) would create an RWW conflict with code executing from Block 0? Specifically: 1. Do UTEST and Code Flash Block 0 share an internal flash controller resource (e.g. a program/erase state machine or semaphore) for RWW purposes, despite having separate address ranges? 2. Is there a different/more specific partition grouping (beyond the block table in AN13388) documented in the Reference Manual that we should be looking at? Our application code runs from Code Flash Block 0, so we'd like to understand the exact mechanism before deciding on a fix. Thank you again for your continued support. Best, Chibeom Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @Chibeom, UTEST in indeed in BLOCK 0. Refer to the RM:  Table 103. Flash block configuration S32K3xx_Memory_map.xlsx Also, AN13388 (S32K3 Memories Guide) Chapter 3. Flash memory states: "There are five blocks as maximum and two blocks as minimum." Block 0 - 4, while UTEST is in Block 0. Regards, Daniel Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hi @danielmartynek , Thank you for confirming that UTEST is in Block 0. That clarifies the RWW mechanism you described. We have two follow-up questions: 1. RWW impact with a synchronous call: Based on our code review, our LC advancement is synchronous — the caller issues the HSE service request and waits for the response before continuing. Since our application, including HSE_AdvanceLifecycle, is linked to Code Flash Block 0, instruction fetches from Block 0 still occur while HSE_B writes to UTEST. In this case, can the RWW error still occur, or does it require an additional trigger such as an asynchronous event (e.g., an interrupt causing a cache miss) as you described? If it can occur, what approach do you recommend to avoid any Block 0 access during the service (e.g., running the wait code from RAM and masking interrupts)? 2. HSE team feedback: Have you received any further feedback from the HSE team regarding the NMI and MURIP behavior that you escalated earlier? Thank you again for your continued support. Best regards, Chibeom Re: S32K312: NMI triggered before Reset_Handler executes, only after Functional (SW) Reset, on speci Hello @Chibeom, 1. Yes, RWW can still occur. If you run it from a cacheable flash region, the waiting code is probably short enough to remain in the cache. However, this cannot be guaranteed, especially in the presence of asynchronous events that may affect cache hits and misses. Running it from SRAM or ITCM is probably the best solution. 2. I haven't received a clear answer that I could share yet. Regards, Daniel
View full article
DDRCLK frequency of P1020 and P2020 Hello  I have a question about DDRCLK frequency of P1020 and P2020. The data sheets say that minimum DDRCLK frequency of P1020 is 66.66MHz and P2020 is 66.7MHz. Is this small gap from spec difference/change or is this just a result of rounding off to one decimal place? Best regards  Re: DDRCLK frequency of P1020 and P2020 This is a rounding difference only. Both devices specify a maximum DDRCLK period of 15 ns (≈66.67 MHz). P2020 rounds it to 66.7 MHz, while P1020 lists 66.66 MHz. Thanks Re: DDRCLK frequency of P1020 and P2020 Thank you June_Lu for your help. BR,
View full article
Kinetis(KW3x/4x、MCX W7xおよびMCX W23)ワイヤレス接続パワープロファイルツール このページはKinetis(KW35/KW38/KW45/KW47)およびMCX Wx(MCX W71/72およびMCX W23)パワープロファイルツールに特化しています。 これにより、あなたのアプリケーション(オートモーティブ、IIoT、トラッカー/タグ、連続血糖モニタリング[CGM])の消費電力を推定し、ソリューションのバッテリー寿命を評価するのに役立ちます。 このページには、単独製品またはフルシステムアプリケーション向けの専用パワープロファイルツールを提供する4つのマーケットセグメントが含まれています:    1. オートモーティブ Kinetis(KW3x/4x)オートモーティブ用パワープロファイルツール - NXPコミュニティ KW35/36製品用のBluetooth LEをスタンドアロンで使用。 Bluetooth LEはKW37/38/39製品用のスタンドアロン対応です。 KW45/KW47製品用のBluetooth LEをスタンドアロンで使用。 スマートフォブアプリケーション(BLE/KW45;UWB Ranger4;SE;モーション・センサ) スマートフォブアプリケーション(BLE/KW47;UWB Ranger5;SE;モーション・センサ) 2.IIoT Kinetis MCX Wxx(MCX W71/72 および MCX W23)IIoT用パワープロファイルツール - NXPコミュニティ Bluetooth LEは単体でMCX W71/MCX W72製品用です。 MCX W23製品のBluetooth LEをスタンドアロンで提供します。 802.15.4 マター ICD SIT & LIT および ZED(単独の MCX W71 & W72 製品用 IIoT)を用いています。 Aliro Doorlockアプリケーション    3. オートモーティブおよび工業技術向けローカリゼーションアプリケーション(CCC CS) Kinetis MCX Wxx(KW47およびMCX W72)Bluetoothローカライゼーション用パワープロファイルツール - NXPコミュニティ 製品:JN518X 製品:K32W0 製品: K32W1 製品:KW 34|35|36 製品:KW 37|38|39 製品:KW41Z |31Z |21Z 製品番号:QN9080|SIP 製品:QN9090|30 製品:UWB NCJ29D5 プロトコル:BLE→コネクティビティ プロトコル:Matter プロトコル:Zigbee Re: Kinetis (KW3x/4x, MCX W7x and MCX W23) One Wireless Connectivity Power Profile Tool こんにちは、 @stephen_t さん。 この新しいツールの使い方を説明するアプリケーションノートが準備中です。 下書き版を添付しました。現時点では、Bluetooth LEの部分のみをカバーしています。 Re: Kinetis (KW3x/4x, MCX W7x and MCX W23) One Wireless Connectivity Power Profile Tool こんにちは、 もしKW45+NCJ29D5/6+SecureEngineを組み合わせたデジタルキーフォブを設計する必要があると仮定します。このツールの使い方はどうすればいいでしょうか。 入手可能なガイダンス文書はすべて役立ちます。 Re: Kinetis (KW3x/4x, MCX W7x and MCX W23) One Wireless Connectivity Power Profile Tool @christophe_menard 草稿をありがとうございました。最終版もUWBとSEを正しく設定するのに役立つので、ぜひ拝見したいです。 よろしくお願いします。 スティーブン
View full article
i.MX 8M Plus:VPU 能否播放降频至 1080p HDMI 显示器的 4K H.264 短片? 大家好,我们正在考虑使用 i.MX 8M Plus 板在 1080p HDMI 显示器上循环播放短 MP4 片段(每个 4-10 秒,H.264,3840x2160,24 fps)。这些片段来自 AI 视频生成器,例如Veo3 AI 上的 Gemini Omni Flash 模型,它可以导出高达 4K 分辨率的视频(声明:我与 Veo3 AI 合作,这是一个独立的服务,与 Google 无关)。 在进行设置之前,我想先确认一下方法。我设想的就是这样的管道: gst-launch-1.0 filesrc location=clip.mp4 ! qtdemux ! h264parse ! vpudec ! imxvideoconvert_g2d ! video/x-raw,width=1920,height=1080 ! waylandsink 问题: 8M Plus VPU 能否实时解码 24 fps 的 4K H.264 视频,还是最好在复制到板卡之前将视频片段转码为 1080p? imxvideoconvert_g2d 是将 4K 降采样到 1080p 的正确元素吗?或者是否存在无需复制即可使用 waylandsink 的方法? 循环播放视频片段列表时,有没有推荐的方法可以避免文件之间出现黑帧? 感谢您提供的任何建议。 Re: i.MX 8M Plus: can the VPU play 4K H.264 short clips downscaled to a 1080p HDMI display? 嗨@ethancaldwell 1. imx8mp vpu 可以解码 4K 视频而没有硬件限制,但只能保证 1080p 的性能,因此我们通过软件将其限制在了 1080p。如果必须使用 4K 分辨率,则需要修改源代码。所以,最好将视频片段转码为 1080p。 2. 请使用 imxvideoconvert_g2d 进行缩放。 3. 目前,`gst-用上市,不用发布` 中还没有官方的、直接的解决方案来实现多个文件之间的无缝切换。建议事先将多个文件合并成一个长视频,然后将该单个文件设置为循环播放。 B.R
View full article
My current license is about to expire, with 6 days remaining. I am applying for an extension. My current license is about to expire, with 6 days remaining. I am applying for an extension.
View full article
i.MX8M Miniはディスクへのサスペンドをサポートしています こんにちは、i.MX8M Miniが「ディスクへのサスペンド」(eMMCや他のストレージメディアへの休止)をサポートしているか知りたいです。 コマンドは "echo disk > /sys/power/state" です。 i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: i.MX8M Mini support suspend to disk 残念ながら、現在のNXP BSPではサポートされていません。 一般的な参考として、ARMのディスク へのサスペンド - eLinux.org を参照してください。 ありがとうございます。
View full article
Kinetis(KW3x/4x、MCX W7x 和 MCX W23)无线连接功率我的工具 本页面专用的介绍 Kinetis (KW35/KW38/KW45/KW47) 和 MCX Wx (MCX W71/72 & MCX W23) 电动我的工具。 它将帮助您估算应用(汽车、工业物联网、追踪器/标签和连续血糖监测 [CGM])中的功耗,并评估解决方案的电池寿命。 本页面包含 4 个市场细分领域,分别针对独立组网 \(SA\)产品或完整系统应用提供专用的功率分析工具: 1. 汽车 Kinetis (KW3x/4x) 汽车行业功率我的分析工具 - NXP 社区 KW35/36 产品独立组网 \(SA\)的蓝牙低功耗功能。 KW37/38/39 产品独立组网 \(SA\)的蓝牙低功耗功能。 KW45/KW47 产品独立组网 \(SA\)的蓝牙低功耗功能。 SmartFob 应用(BLE/KW45;UWB Ranger4;SE;运动传感器) SmartFob 应用(BLE/KW47;UWB Ranger5;SE;运动传感器) 2.工业物联网 (IIoT) ... Kinetis MCX Wxx(MCX W71/72 和 MCX W23)工业物联网电源我的工具 - NXP 社区 MCX W71/MCX W72 产品独立组网 \(SA\)蓝牙低功耗。 MCX W23 产品独立组网 (SA)的蓝牙低功耗 (Bluetooth LE)。 802.15.4 Matter ICD SIT & LIT 和 ZED 用于 MCX W71 & W72 产品在独立组网 \(SA\)(IIoT)中。 Aliro门锁应用 3. 面向汽车和工业物联网的定位应用(CCC CS) Kinetis MCX Wxx (KW47 & MCX W72) 蓝牙定位电源我的工具 - NXP 社区 产品:JN518X 产品:K32W0 产品:K32W1 产品:KW 34|35|36 产品:KW 37|38|39 产品:KW41Z | 31Z | 21Z 产品:QN9080|SIP 产品:QN9090|30 产品:UWB NCJ29D5 协议:BLE -> 连接性 协议:Matter 协议:Zigbee Re: Kinetis (KW3x/4x, MCX W7x and MCX W23) One Wireless Connectivity Power Profile Tool 嗨@stephen_t , 应用笔记即将发布,其中将解释如何使用这款新工具。 附件为草稿版本。目前仅涵盖蓝牙低功耗部分。 Re: Kinetis (KW3x/4x, MCX W7x and MCX W23) One Wireless Connectivity Power Profile Tool @christophe_menard 非常感谢您提供的文档草稿,我也很期待最终版本,因为它将有助于正确配置UWB和SE。 此致 史蒂芬 Re: Kinetis (KW3x/4x, MCX W7x and MCX W23) One Wireless Connectivity Power Profile Tool 你好 , 假设我们需要设计一个结合了 KW45+NCJ29D5/6+SecureEngine 的数字钥匙扣,该如何使用这个工具? 任何可用的指导文件都将有所帮助。
View full article
私の現在の運転免許証は、あと6日で期限切れになります。延長申請をしたいと思います。 私の現在の運転免許証は、あと6日で期限切れになります。延長申請をしたいと思います。
View full article
i.MX8M Mini support suspend to disk Hi, we would like to know whether the i.MX8M Mini supports "suspend-to-disk" (i.e hibernation to eMMC or others storage media)? command is "echo disk > /sys/power/state" i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: i.MX8M Mini support suspend to disk Unfortunately, it is not supported in the current NXP BSP. For general reference, please refer to Suspend To Disk For ARM - eLinux.org . Thanks.
View full article
P1020およびP2020のDDRCLK周波数 こんにちは P1020とP2020のDDRCLK周波数について質問があります。 データシートによると、P1020のDDRCLK最低周波数は66.66MHz、P2020は66.7MHzとされています。 このわずかな差は、仕様の違いや変更によるものですか、それとも単に小数点以下第1位への四捨五入の結果ですか? よろしくお願いします Re: DDRCLK frequency of P1020 and P2020 これは端数処理による差にすぎません。 両デバイスとも、最大DDRCLK周期は15ナノ秒(約66.67MHz)と規定している。P2020では66.7MHzと丸められているのに対し、P1020では66.66MHzと記載されている。 よろしくお願いします。 Re: DDRCLK frequency of P1020 and P2020 June_Luさん、ご協力ありがとうございました。 BR、
View full article
Kinetis (KW3x/4x, MCX W7x and MCX W23) Wireless Connectivity Power Profile Tools This page is dedicated to the Kinetis (KW35/KW38/KW45/KW47) and MCX Wx (MCX W71/72 & MCX W23) Power Profile Tools. It will help you to estimate the power consumption in your application (Automotive, IIoT, Trackers/Tags and Continuous Glucose Monitoring [CGM]) and evaluate the battery life time of your solution. This page contains 4 market segments which provides dedicated power profile tool on standalone product or full system application for:    1. Automotive Kinetis (KW3x/4x) Power Profile Tools for Automotive - NXP Community Bluetooth LE for the KW35/36 products in standalone. Bluetooth LE for the KW37/38/39 products in standalone. Bluetooth LE for the KW45/KW47 products in standalone. SmartFob application (BLE/KW45; UWB Ranger4; SE; motion sensor)  SmartFob application (BLE/KW47; UWB Ranger5; SE; motion sensor)     2. IIoT Kinetis MCX Wxx (MCX W71/72 & MCX W23) Power Profile Tools for IIoT - NXP Community Bluetooth LE for the MCX W71/MCX W72 product in standalone. Bluetooth LE for the MCX W23 product in standalone. 802.15.4 Matter ICD SIT & LIT and ZED for the MCX W71 & W72 product in standalone (IIoT). Aliro Doorlock application    3. Localisation application (CCC CS) for Automotive & IIoT Kinetis MCX Wxx (KW47 & MCX W72) Power Profile Tools for Bluetooth Localization - NXP Community Product: JN518X Product: K32W0 Product: K32W1 Product: KW 34|35|36 Product: KW 37|38|39 Product: KW41Z |31Z | 21Z Product: QN9080|SIP Product: QN9090|30 Product: UWB NCJ29D5 Protocol: BLE -> connectivity Protocol: Matter Protocol: Zigbee Re: Kinetis (KW3x/4x, MCX W7x and MCX W23) One Wireless Connectivity Power Profile Tool Hi @stephen_t , Application Note is on the way to explain how to use this new tool. Find a draft version attached. It covers Bluetooth LE part for the moment. Re: Kinetis (KW3x/4x, MCX W7x and MCX W23) One Wireless Connectivity Power Profile Tool Hello , Suppose if we need to design a digital keyfob which combine KW45+NCJ29D5/6+SecureEngine how to use this tool. Any guidance document avatilable will be helpful. Re: Kinetis (KW3x/4x, MCX W7x and MCX W23) One Wireless Connectivity Power Profile Tool @christophe_menard  Thank you very much  for the draft document , will be interested in the final version also as it will help to correctly configure UWB and SE. Regards Stephen
View full article
KW45のTx出力出力の消費電力は:-15,-10,-5,-2 dBm(カリキュレータ1_4)で こんにちは、 KW45_WK47_MCXW71_MCXW72_BLE_power_profile_calculator_v1.40.xlsxでは、送信出力(dBm)が0dBmから10dBmまでの消費電力が示されています。 KW45に-15、-10、-5、-2 dBmを追加することは可能でしょうか?追加したファイルを完成させるために。 ありがとうございます。 Re: Consumption for KW45 function of Tx Output power for : -15,-10,-5,-2 dBm with calculator 1_4 こんにちは、 あなたの調子が良いといいのですが。この送信値は、 当社のKW45B(無線)およびKW45Z(MCU)データシートに示された典型的な値に対応しています。 また、すべてのプロファイルツールについては、当社のメイン投稿を参照することをお勧めします: Kinetis(KW3x/4x、MCX W7xおよびMCX W23)ワイヤレス接続パワープロファイルツール よろしくお願いいたします。 リカルド
View full article
S32G274 裸机代码 我想在 S32G274 开发板上使用裸机程序,包括用于启动 A53 处理器、LINFlexD 串口和以太网等模块的裸机驱动程序。我希望它能够开箱即用。S32DS 生成的驱动程序仅包含处理器启动功能。 我尝试自己实现 LINFlexD 串口(启用引脚、启用时钟、初始化串口接口),但我不太清楚如何正确处理时钟启用。 我希望您能提供一个可以直接在 S32DS 中编译的现成裸机程序。 Re: S32G274 baremetal code 你好, @Tatu_dd 感谢你的帖子。 1. NXP针对S32G274A的软件赋能策略主要将A53内核定位为Linux 电路板支持包。运行环境,而非裸机开发环境。S32 Design Studio 3.6.8中针对A53内核的示例代码特意限制为启动代码,因为其预期用途是在这些内核上运行完整的Linux发行版。 2. 对于裸机A53开发,目前公开的参考代码不多,只有一个演示版本,但它并非纯粹的A53裸机代码,而是一个异构实现。 因此,您可能需要根据自身需求实现或移植现有的 Linux 驱动程序或 RTD 驱动程序,很抱歉,NXP 没有提供任何直接的正式示例/软件版本。 BR 陈银 Re: S32G274 baremetal code 你好@chenyin_h , 谢谢你的回复,我知道这条信息。 谢谢你! BR Tatu_dd Re: S32G274 baremetal code 你好, @Tatu_dd 不客气。 如果您在使用 S32G 产品过程中需要任何其他支持,欢迎您为此开设新帖,我们很乐意提供帮助。 BR 陈银
View full article
NXP開発ボード ARM Cortex-A53、FRDM-IMX8MPLUS電源オンスイッチが動作しません こんにちは NXP開発ボード(ARM Cortex-A53、FRDM-IMX8MPLUSを購入しました しかし、スイッチをスライドさせてみると電源が動かなくなりました。マザーボードかスイッチの欠陥でしょうか?スイッチを交換しましたが、それでも動作しません。スイッチ NXP Development Board ARM Cortex-A53, FRDM-IMX8MPLUSNXP Development Board ARM Cortex-A53, FRDM-IMX8MPLUSNXP Development Board ARM Cortex-A53, FRDM-IMX8MPLUSNXP Development Board ARM Cortex-A53, FRDM-IMX8MPLUSNXP Development Board ARM Cortex-A53, FRDM-IMX8MPLUSNXP開発ボードのARM Cortex-A53、FRDM-IMX8MPLUS電源オンのエンバレーリング方法を教えていただけますか i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: NXP Development Board ARM Cortex-A53, FRDM-IMX8MPLUS power on switch not working こんにちは 私はSamsung モバイル Adpoterの5対3Aスペックを使っています Re: NXP Development Board ARM Cortex-A53, FRDM-IMX8MPLUS power on switch not working こんにちは、 @nalini さん。 FRDMには12V以上の入力電圧が必要です。5Vの充電器では動作しません。PDサポートの別の充電器を試してみるのもいいでしょう。 よろしくお願いします、 志明 Re: NXP Development Board ARM Cortex-A53, FRDM-IMX8MPLUS power on switch not working こんにちは、 @nalini さん。 お使いの電源ユニットの消費電力は何ワットですか? よろしくお願いします、 志明 Re: NXP Development Board ARM Cortex-A53, FRDM-IMX8MPLUS power on switch not working やあ、ジュミンさん 5Vのモバイル電源アダプターを使うと、基板がオンになっています。しかし、スライド電源スイッチは基板の電源を切っていません。基板はスライド電源スイッチのどの位置(オンまたはオフ)でも電源がオンのままです。スイッチを交換しましたが、それでも動作しません
View full article
Tamper detection function in iMX6ULL I would like to enable the active tamper detection feature on the i.MX6ULL processor in order to detect when the device enclosure is opened. A switch has been added to the hardware and connected to the external tamper pins, as shown in the attached figure. Do you have any examples or documentation on how to support tamper detection on the software side? Is there an example implementation or a sample function that demonstrates how to configure and handle this feature? Re: Tamper detection function in iMX6ULL Hello, The tamper feature on i.MX 6ULL is controlled by a Fuse which is currently provisioned by NXP to disable this feature on all production part numbers for i.MX6ULL. Several customer-facing documents incorrectly state that i.MX 6ULL supports external tamper. Since the fuse is programmed to disable this feature on all i.MX 6ULL part numbers, a customer will not be able to use the tamper feature even though the tamper pins are documented in the current documentation. Documentation will be updated to reflect that tamper is not Supported. Please also note that the derivative product i.MX 6ULZ also does not support Tamper Feature i.MX 6UL -3 i.MX 6ULL/6ULZ Comments Tamper Detection Signal Yes  No Active Tamper only on i.MX 6UL  Volt/Temp/Freq Detect (DRY-ICE) Yes  No DRY-ICE & Active Tamper features not supported on i.MX 6ULL/ULZ Best regards.
View full article