Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
在 MPC5777C 上使用 Trace32 时出现 NCF42 错误 你好 我目前正在使用 MPC5777C 上的 FCCU 配置 BIT。 为了调试,我使用了 Trace32,但在使用 Trace32 时遇到了 BIT 问题。 情况: 使用 Trace32 调试时,间歇性出现 NCF42 错误。即使我尝试使用 FCCU.NCF_Sn 清除错误,错误也不会消失。 根据我在论坛上找到的信息,似乎当 Trace32 执行 "中断"(Break)时,内核可能会脱节,从而导致 NCF42 错误。 但问题是,即使在这种情况下使用 FCCU.NCF_Sn 清除了错误,错误仍然存在并继续出现。 此外,即使使用完全相同的代码,这种现象也会断断续续地出现。 问题 有什么办法可以改善或减轻这种行为? 锁步错误检测的灵敏度如何?在正常运行条件下,它也会间歇性出现吗? 在我们的系统中,如果发生锁步错误,就会立即被视为系统故障,并将操作切换到冗余信道。如果由于灵敏度高而经常出现锁步错误,我们可能需要考虑为这种故障提供异常处理机制或容差值。 提前感谢您的支持。 Re: NCF42 Error with Trace32 on MPC5777C 你好 不知道该加什么。 您正在尝试对异步事件进行分类。 从 FCCU 的角度来看: 如果故障信号激活,则设置 NCF42。 如果您清除了故障,但信号仍处于激活状态,则不会看到它被清除,因为它会立即被设置。 在调试模式下应忽略此故障。 致以最诚挚的问候, Peter Re: NCF42 Error with Trace32 on MPC5777C 调试时必须禁用锁定步骤,仅清除 NCF42 错误是不够的。 调试器只能控制主内核,而调试器无法访问锁步内核。这意味着,当主内核遇到片上断点时,锁步内核不会遇到。它将尝试继续运行,从这时起,两个内核将永远无法恢复同步。这会导致未定义的行为。清除 NCF42 后,警报就会消失,但根本问题"锁定步进的损失" ,却依然存在。 即使您设法清除 NCF42 并保持一段时间(例如关闭调试器中所有可访问内核寄存器或内存的窗口),错误仍会再次发生 最迟当您再次尝试运行内核时。 Re: NCF42 Error with Trace32 on MPC5777C 谢谢您的答复。 我完全理解在使用 TRACE32 时可能会出现 RCCU 故障。 我好奇的是,为什么在使用 TRACE32 运行相同代码时,NCF 清除程序有时能成功清除 NCF42 故障,而有时却不能。 我想了解这种不一致行为背后的原因--为什么在某些情况下故障会被清除,而在另一些情况下却不会--以及在使用 TRACE32 时,系统状态不可能总是被准确确定,这是否在意料之中。 感谢您一如既往的支持和真知灼见。 Re: NCF42 Error with Trace32 on MPC5777C 你好 在我看来,这取决于指令的执行情况。也许调试器连接过程中存在一些故障,它可以/不会在核心上执行会触发信号 RCCU 故障的指令。例如,如果您在加载到核心寄存器的指令上放置断点,它将不会触发信号 RCCU,因为没有输出可由 RCCU 读取。如果从内核寄存器读取数据时,RCCU 被禁用,但锁定步进被启用,或者反之亦然,则会出现故障。 我认为这可以解释你看到的行为。除此以外,除了调试器本身的问题,我想不出其他原因(对于这种行为,最好还是询问 Lauterbach,看他们能否解释清楚)。 顺祝商祺! Peter Re: NCF42 Error with Trace32 on MPC5777C 谢谢您的答复。 按照您的建议,我在系统初始化过程中执行了 NCF42 清除例程。 不过,我对 TRACE32 的使用有一个疑问。当我使用 TRACE32 设置断点时,会出现 NCF42。在恢复执行并执行 NCF42 清除例程后,NCF42 有时会被成功清除,有时则不会。 我担心的是这种不一致的行为。使用 TRACE32 是否无法精确确定 NCF42 的出现? 不使用 TRACE32 时不会出现这个问题。能否请您澄清一下这个问题? Re: NCF42 Error with Trace32 on MPC5777C 你好 故障 42,即锁步模式,每次在启用锁步的情况下启动设备时都会发生,因为它告诉您已启用 Lockstep 功能,但内核处于 RESET 状态。之所以处于RESET状态,是因为核心 1 在开机时始终处于RESET状态,直到 Core 0 将其退出RESET状态。最终结果始终是故障 42,必须在开机时忽略并由应用程序清除。 https://community.nxp.com/t5/MPC5xxx/MPC5777C-Problem-with-NCF-42-using-debugger/m-p/840687?commentID=1060048&et=watches.email.outcome#comment-1060048 我已经用切割的 3N45H 对其进行了测试,但在上电复位或外部 RESET 后我看不到 NCF42 已设置。FCCU 状态标志清除。 顺祝商祺! Peter Re: NCF42 Error with Trace32 on MPC5777C 感谢您的及时解释。 我知道使用 TRACE32 时遇到错误是正常现象。 不过,我想知道为什么这种现象没有持续出现。 具体情况如下: 1.使用 TRACE32 时,会出现 NCF42 错误,但执行 NCF 清除程序后,NCF42 会被清除。在继续使用 TRACE32 的同时,如果发生错误,可以持续清除错误。 2.在与第一种情况相同的情况下,即使执行了 NCF 清除程序,NCF42 也不会被清除,仍然存在。 我想给出一个一致的解释,例如:" 使用 TRACE32、" 或 " 时总是会出现 RCCU 错误,在使用 TRACE32 期间代码中触发中断时会出现,但可以使用 NCF 清除程序将其清除。" 但是,由于行为不一致,我在调试时遇到了麻烦。 我该如何更好地解释这种情况?我是否应该说明在使用 TRACE32 时,RCCU 可能会出错,也可能不会出错? Re: NCF42 Error with Trace32 on MPC5777C 你好 TRACE32 将激活 uC 的调试模式。一旦启动调试模式,RCCU 将被禁用。 所以你观察到的行为是正确的。 您可以清除 FCCU NCF42,但一旦进入调试模式,它又会立即被设置。 因此,您可能看起来无法清除它。 在实际应用程序执行过程中,锁步错误非常罕见,一定是出了什么大问题。 顺祝商祺! Peter Re: NCF42 Error with Trace32 on MPC5777C 此外,即使出现 NCF42 错误,一般也会在通过错误清除程序后得到解决。 不过,在一些间歇性的情况下,尽管尝试清除,NCF42 错误仍然会永久存在。
View full article
PTN5110 仅作为水槽 我目前正试图为水槽设计 PTN5110N。查看应用笔记 AN12137,我看到了 DRP 初始化流程图。在关于 UFP 初始化的段落中,"TCPC 初始化、连接处理、断开连接处理可以与 DRP 流程图或源/汇断开流程图" 中指定的相同。如何修改 DRP 流程图,以获得可运行的仅水槽的 UFP 流程图?我最担心的是,DRP 流程图让 TCPM 在建立连接之前设置 Role_Control 寄存器并写入命令.Looking4Connection。这在我的设计中行不通,因为在我的应用中,TCPC 和 TCPM 只有在连接完成后才能获得电源。此外,我不理解去抖 CC_Status 步骤。如何为 tCCDebounce 除抖动?这意味着什么? Re: PTN5110 as a sink only 你好,NathanS1 日安 如何修改 DRP 流程图,以获得可运行的仅水槽的 UFP 流程图? 从 TCPC 初始化开始 跳过源代码角色配置 将角色设为 UFP(汇流排) 连接检测 处理附加事件 启动 USB PD 协商 断开手柄 可选的:超级角色交换处理 在您的设计中,TCPC(PTN5110N)和 TCPM(主控制器)只有在插入电缆后才接收电源。这意味着 连接前不能预先配置 ROLE_CONTROL 或发出 COMMAND.Looking4Connection。 相反,您需要依靠 PTN5110N 自主的 Type-C 连接检测来唤醒系统。 如何为 tCCDebounce 除抖动?这意味着什么? tCCDebounce 是 Type-C 规范定义的消抖时间,用于确保连接稳定后再对其采取行动。用于水槽/UFP。等待至少 100 毫秒稳定的 CC 线路检测后再宣布连接 收到 TCPC 警报后 读取 CC_STATUS。 启动 tCCDebounce = 100 ms 的计时器。 100 毫秒后,再次读取 CC_STATUS。 如果状态仍然有效且保持不变,则继续处理连接。 如果没有,则丢弃并等待新的警报。 希望这些信息对您有所帮助,如果您还需要其他帮助,请告诉我。 祝你愉快,好运连连。
View full article
外部 JTAG 问题 亲爱的先生 我们已经从 AVNET Asia Pvt.Ltd 购买了带有 JTAG 调试器 USB-ML-MULTILINK 的 MIMXRT1170-EVK 评估板。 我们可以通过 USB 内部调试器下载代码,但无法通过 JTAG、USB-ML-MULTILINK、Make:PE Micro 外部调试器下载代码。 我们向海德拉巴和班加罗尔的 AVNET 公司反映了这一问题,但他们至今没有提供任何解决方案。该问题已通知安富利公司 4 周。 要求尽快提供解决方案并派遣代表。为解决了这些问题。 此致, 拉维-坎特-维尔玛 印度海德省哈尔市 SLDRC           Re: External JTAG Issue 你好@Ravi07011983、 为什么 GPIO_DISP_B2_01 上有 24MHz 时钟?您的定制板上有任何硬件设计问题吗? 祝您愉快, Kan ------------------------------------------------------------------------------- 注: - 如果本帖回答了您的问题,请点击"标记正确" 按钮。谢谢! - 我们会在最后一次发帖后的 7 周内跟踪主题,之后的回复将被忽略 如果您以后有相关问题,请另开新主题,并参考已关闭的主题。 ------------------------------------------------------------------------------- Re: External JTAG Issue 先生 我们无法通过外部 jtag 调试器调试代码。启动模式引脚是内部启动,即 10,启动配置引脚 SRC_BT_CFG0 到 SRC_BT_CFG9 处于下拉状态,但是一个引脚 SRC_BT_CFG7=GPIO_DISP_B2_01 出现了问题,因为该引脚时钟为 24 MHz + 直流 (1.8v),而且电流即将到来画得更少了。调试屏幕没有出现。 Re: External JTAG Issue 你好@Ravi07011983, 在你这边的 MIMXRT1170-EVK 配合下,USB-ML-Multilink 运行得很好吗?如果是,请检查您的自定义板和 EVK 之间的区别,如果没有区别,请检查组装情况。 祝您愉快, Kan ------------------------------------------------------------------------------- 注: - 如果本帖回答了您的问题,请点击"标记正确" 按钮。谢谢! - 我们会在最后一次发帖后的 7 周内跟踪主题,之后的回复将被忽略 如果您以后有相关问题,请另开新主题,并参考已关闭的主题。 ------------------------------------------------------------------------------- Re: External JTAG Issue 我们正在使用 +5v 至 +3.3V、+3.3V 至 +1.8V、+3.3V 至 +1.0V 开关稳压器电源。我们根据评估板制作了定制电路板原理图,但仍未连接 jtag。 Re: External JTAG Issue 你好@Ravi07011983, 启动模式和ext jtag调试之间没有关系,通常我们使用内部启动。 您成功使用 RT1170EVKB/EVK 进行 JTAG 调试了吗?你的自定义板和 EVK 板有什么区别吗?特别是在 JTAG 电路上。 请予以澄清。 祝您愉快, Kan ------------------------------------------------------------------------------- 注: - 如果本帖回答了您的问题,请点击"标记正确" 按钮。谢谢! - 我们会在最后一次发帖后的 7 周内跟踪主题,之后的回复将被忽略 如果您以后有相关问题,请另开新主题,并参考已关闭的主题。 ------------------------------------------------------------------------------- Re: External JTAG Issue 我们的项目使用 MIMXRT1176 IC 进行定制板设计。我们无法使用外部调试器 USB-ML-MULTILINK 调试代码。所有 jtag 线路电压都将到来,24 MHz 时钟也可用。什么是启动模式电阻器 GPIO_LPSR_02 (BOOT_MODE0),外部 jtag 的 GPIO_LPSR_03 (BOOT_MODE1) 值。 Re: External JTAG Issue 我们的项目使用 MIMXRT1176 IC 进行定制板设计。我们无法使用外部调试器 USB-ML-MULTILINK 调试代码。所有 jtag 线路电压都将到来,24 MHz 时钟也可用。什么是启动模式电阻器 GPIO_LPSR_02 (BOOT_MODE0),外部 jtag 的 GPIO_LPSR_03 (BOOT_MODE1) 值。 Re: External JTAG Issue 你好@Ravi07011983、 取消选择 SWD 协议将自动选择 JTAG 协议。 祝您愉快, Kan ------------------------------------------------------------------------------- 注: - 如果本帖回答了您的问题,请点击"标记正确" 按钮。谢谢! - 我们会在最后一次发帖后的 7 周内跟踪主题,之后的回复将被忽略 如果您以后有相关问题,请另开新主题,并参考已关闭的主题。 ------------------------------------------------------------------------------- Re: External JTAG Issue 如何选择 JTAG 协议? Re: External JTAG Issue 你好@Ravi07011983、 SW1 与 JTAG 协议无关,您必须在集成开发环境中配置调试配置。详情请参见下文。 祝您愉快, Kan ------------------------------------------------------------------------------- 注: - 如果本帖回答了您的问题,请点击"标记正确" 按钮。谢谢! - 我们会在最后一次发帖后的 7 周内跟踪主题,之后的回复将被忽略 如果您以后有相关问题,请另开新主题,并参考已关闭的主题。 ------------------------------------------------------------------------------- Re: External JTAG Issue 我们正在使用板提供的电源适配器。所有跳线 J5、J6、J7、J8、J21 均已移除,JTAG 电阻器 R187、R208、R195 和 R78 的跳线均已移除,但仍未送到 JTAG。 JTAG 协议的开关位置 SW1-3 和 SW1-4.IDE MCUXPRESSO 如何切换到 SWD 到 JTAG。 Re: External JTAG Issue 你好@Ravi07011983、 你打算在 MIMXRT1170-EVK 上使用 J1 连接 USB-ML-Multilink 吗?如果是,请使用外部电源适配器代替板载 USB 端口电源,并确保 IDE 使用 SWD 协议,否则必须重新设计板。 希望对你有所帮助、 祝您愉快, Kan ------------------------------------------------------------------------------- 注: - 如果本帖回答了您的问题,请点击"标记正确" 按钮。谢谢! - 我们会在最后一次发帖后的 7 周内跟踪主题,之后的回复将被忽略 如果您以后有相关问题,请另开新主题,并参考已关闭的主题。 -------------------------------------------------------------------------------
View full article
STRX - 用于从 GCC 编译器迁移的 GHS 编译器环境 嗨,团队、 客户希望用 GHS 取代 GCC 编译器选项。(S32DS 3.5 底座) 它们有自己的软件(bootlader 和 RTD base),由 gcc 编译器开发。 因此,我已指导他们参考下面的文档安装 GHS 编译器插件,并已安装完毕 https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Install-GHS-Compiler-Plugin/ta-p/1436232?attachment-id=132569 但我有一些问题,因为我没有 GHS 编译器,无法在自己身边检查。能否请您检查一下问题? 1.能否提供将使用 GCC 编译器开发的 SW 移植到 GHS 编译器的指南,如在 S32DS 环境中定义__ghs__ 等? 2.我们是否有说明如何使用 GHS 编译器制作项目的文件。(我参考了前一张机票才知道)。 https://community.nxp.com/t5/S32-Design-Studio/GHS-Compiler-error-in-S32DS/m-p/889761 https://community.nxp.com/t5/S32-Design-Studio/GHS-toolchain-project-in-debug-configuration/m-p/1080580 https://community.nxp.com/t5/S32-Design-Studio/5744P-S32-Design-Studio-include-Green-Hills-Compiler-Problem/m-p/652339#comment-850410 https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Install-Lauterbach-TRACE32-debugger-plug-in-into-S32/ta-p/1112237 此致, 马可 Re: STRX - GHS compiler environment for migration from GCC compiler 我在项目向导中添加了--为引导加载器附加 RTD。 Re: STRX - GHS compiler environment for migration from GCC compiler 嗨,马可、 遗憾的是,无法在现有项目中更改工具链类型(如从 gcc 改为 GHS)。最简单的方法是创建新项目,在项目向导中选择 GHS 工具链,然后从基于 gcc 的项目中复制现有源代码。
View full article
标签无法放大或缩小(《图形用户界面指南》1.9.1,LVGL 8.3.10) 你好: 最近,我在使用过程中遇到了一个问题: 我创建了一个标签,然后触发信号了放大或缩小另一个标签的事件,然后模拟不成功。按下标签时,另一个标签没有反应。 使用了四个接口函数:lv_obj_set_style_transform_pivot_x(item_array_1a[i].item_obj_icon.item_array_1a[i])50, LV_PART_MAIN); lv_obj_set_style_transform_pivot_y(item_array_1a[i].item_obj_icon, 50, LV_PART_MAIN); lv_obj_set_style_transform_width(item_array_1a[i].item_obj_icon, 512, LV_PART_MAIN); lv_obj_set_style_transform_height(item_array_1a[i].item_obj_icon, 128, LV_PART_MAIN); 那么,为什么标签不能放大或缩小?LVGL 界面是否使用不当? Re: Labels cannot be scaled up and down (Gui Guide 1.9.1, LVGL 8.3.10) V8.3.10 版本的界面有一个问题,V9.2.1 版本的界面可以实现的功能: lv_obj_set_style_transform_pivot_x(item_array_1a[i].item_obj_icon、50, LV_PART_MAIN); lv_obj_set_style_transform_pivot_y(item_array_1a[i].item_obj_icon, 50, LV_PART_MAIN); lv_obj_set_style_transform_scale_x(item_array_1a[i].item_obj_icon,384,LV_PART_MAIN); lv_obj_set_style_transform_scale_y(item_array_1a[i].item_obj_icon,384,LV_PART_MAIN); 感谢 wenbin Re: Labels cannot be scaled up and down (Gui Guide 1.9.1, LVGL 8.3.10) 你好:@文彬元 是的,我要做的是,当我点击 label_a 时,让 label_b 缩放。此外,为什么使用 V8.3.10 版本是因为我们使用贵公司的 MIMXRT1170-EVK 开发板,LVGL V9.2.1 版本没有相应的设备模板,但是 V8.3.10 版本存在。我们公司也希望使用最新版本的 LVGL 版本。现在可以在没有 MIMXRT1170-EVK 开发板的情况下使用设备模板吗? 是的,我目前想实现的效果是点击label_a的时候让label_b缩放大小。另外,为什么使用V8.3.10版本是因为我们使用您公司MIMXRT1170-EVK的开发板,LVGLV9.2.1版本中没有对应设备模板,而V8.3.10中存在。我们公司也希望使用最新版的lvgl版本,现在是没有mimxrt1170-evk开发板的设备模板也可以使用吗? Re: Labels cannot be scaled up and down (Gui Guide 1.9.1, LVGL 8.3.10) @zhuangfei 你好、 能否请您介绍一下您的项目设置?例如,这个案例背后的逻辑——你想在点击 label_a 时在 label_b 上触发信号缩放效果吗?如果是,则应启用 LV_OBJ_FLAG_CLICKABLE 标志,以便 label_a 在我的情况下,使用您的代码,至少 label_b 会改变其主尺寸。不过,效果并不完美--字体大小并没有相应缩放。 顺便问一下,能否请您分享一下您的项目选择LVGL v8.3.10的原因?我们通常建议使用最新版本的 LVGL,因为它包含了重要的改进和错误修复,可能会对您的使用情况有所帮助。 您能麻烦给出这个用例的详细信息吗?例如具体的逻辑链条,您是想在点击 label_a 的时候让 label_b 缩放大小吗?这样的话 label_a 需要使能 LV_OBJ_FLAG_CLICKABLE 。 在我这边的重现中,至少 label_b 本身的大小是会改变的,只是文本的大小不会改变。 能顺便问一下您选择V8.3.10版本开发的原因吗? 我们比较推荐使用最新的LVGL版本,因为有很多功能被丰富了,比如Transform有了更多的配置,可以顺利的改变整个label的大小包括字体本身。 期待您的更新! 顺祝商祺! 文斌 Re: Labels cannot be scaled up and down (Gui Guide 1.9.1, LVGL 8.3.10) hi:@文斌 我根据您的截图添加了标记:添加可点击,但仍然没有反应。对于其他按键,我将触发事件设置为在单击时更改标签背景图像的颜色。这可以实现,但缩放和缩放注释界面功能一直无法运行 我按照你的截图增加了flag:add clickable但是点击还是没有反应,其他按键我是设置触发事件是点击标签背景图片变色这个是可以实现的,但这个放大缩小便签接口函数一直不行。 lv_obj_set_style_transform_pivot_x(item_array_1a[i].item_obj_icon, 50, LV_PART_MAIN); lv_obj_set_style_transform_pivot_y(item_array_1a[i].item_obj_icon, 50, LV_PART_MAIN); lv_obj_set_style_transform_width(item_array_1a[i].item_obj_icon, 512, LV_PART_MAIN); lv_obj_set_style_transform_height(item_array_1a[i].item_obj_icon, 128, LV_PART_MAIN); Re: Labels cannot be scaled up and down (Gui Guide 1.9.1, LVGL 8.3.10) @zhuangfei 你好、 你能否检查一下 LV_OBJ_FLAG_CLICKABLE 标志是否已添加到你的触发信号标签小部件中?默认情况下,标签部件不启用此标记,因此除非明确设置,否则不会响应点击事件。 您可以像这样在小工具的旗帜部分添加旗帜: 希望对您有所帮助!如果您需要进一步的帮助,请随时分享更多详细信息或与我们联系。 顺祝商祺! 文斌
View full article
S32N55:通过外部唤醒源从睡眠模式唤醒时触发两次 RESET 你好,团队、 我们的客户 HKMC 目前正在 S32N55 平台上测试 休眠和唤醒功能 ,结果遇到了意外行为。 观察到的现象 当通过外部引脚(例如, S32N55-RDB 上的 FSS_WKUP2 )唤醒系统时, 破坏性RESET 和功能RESET 都会被触发。此外, PREV_MODE 寄存器显示 FULL_POWER_MODE ,而不是预期的 STDBY _ MODE 。 我使用以下设置重现了这种行为: 软件版本: SW32N5_GRAYVIP_1_0_22_0 使用的 API:Scmi_SystemPowerStateSetSynch(0,0x80000003,0,5000);在 CRS 项目 中调用了该 API,以进入睡眠模式。 唤醒方法 :向下拉 FSS_WKUP2。 捕获的数据 寄存器值和信号轨迹如附图所示。 从波形来看,似乎有两个 RESET_OUT_B 事件触发信号。 为了隔离问题,我在 Reset_Handler 的开头添加了一个循环。唤醒后,系统保持在环路中,有效避免了来自 FSS FW 的任何干扰。 问题 您能否帮助分析一下这种行为是预期的还是不正常的? 在什么条件下,唤醒事件会触发破坏性RESET和功能RESET? 为什么系统报告的是 PREV_MODE = FULL_POWER_MODE ,而不是 STDBY_MODE ? 提前感谢您的支持! 谨致问候, Tangsheng FSS_FW GRAY_VIP 优先级:高 资料来源直接客户 Re: S32N55: trigger twice reset when wake-up from sleep mode by external wake-up source 你好,阿琳娜、 睡眠时间约为6.7 秒,如下图所示。由于违反了 PMIC 协议,它不应该被唤醒。而且 POR_B 始终处于高电平。 顺祝商祺! 唐生。 Re: S32N55: trigger twice reset when wake-up from sleep mode by external wake-up source 你好,唐生、 是的,它将监测待机信号,但我的理解是,如果在该时间段内不触发信号唤醒,待机计时器将过期,并将进行RESET。 从你提供的捕获来看,我怀疑你第一次 RESET 是因为违反了 PMIC 协议(由于 RESET_OUT_B,其他信号看起来不错),第二次 RESET 似乎是由软件触发的(或者可能是因为 Wdg 在唤醒后无法在 Pmic 上及时使用)。 能否同时提供 PMIC_STANBY_MODE_B 保持低电平的时间? 致以最崇高的敬意 阿丽娜 Re: S32N55: trigger twice reset when wake-up from sleep mode by external wake-up source 你好,阿琳娜、 待机计时器用于在待机模式下超时时自动将设备过渡到深度故障保护 (DFS) 模式。不应向监测发出唤醒信号。 我测试了睡眠功能,使用该参数后运行良好。 顺祝商祺! 唐生。 Re: S32N55: trigger twice reset when wake-up from sleep mode by external wake-up source 你好 Tangsheng, 我看到待机计时器持续时间窗口设置为大约 1 秒(1024 毫秒),如果你在该时段内没有收到唤醒触发信号,pmic 将退出低功耗,SoC 将收到 POR。您能增加时间窗口或禁用待机计时器吗? 此致 阿丽娜 Re: S32N55: trigger twice reset when wake-up from sleep mode by external wake-up source 你好,阿琳娜、 感谢您的努力! 关于您的问题 1.我测试了两种情况:SoC 在睡眠状态下分别停留了几十秒和几分钟。我没有记录准确的数字。两者都表现出同样的唤醒行为。 2.测试使用了 Tresos 中的 Sleep_Mode 配置。 顺祝商祺! 唐生。 Re: S32N55: trigger twice reset when wake-up from sleep mode by external wake-up source 你好,唐生! 我们确实知道功能RESET问题,这是我们正在调查的已知限制,但我们之前没有遇到过 CSSI 的破坏性限制。 请问 SoC 在挂起状态下能保持多长时间?此外,在 pmic tresos 配置中为 Pmic 待机窗口配置的值是多少? 关于您的问题"如果是这样,是否有其他方法可以在唤醒后保留或检索唤醒源信息?",很遗憾目前没有,我们在启动 FSS 子系统时会清除标记。但我们知道这个问题,并将加以解决。 Re: S32N55: trigger twice reset when wake-up from sleep mode by external wake-up source 你好,拉杜、 感谢您的支持。期待您的回复。 Re: S32N55: trigger twice reset when wake-up from sleep mode by external wake-up source 您好@Tangsheng_Zhou, 我们的团队已受理此案,并将尽快给您答复。 Re: S32N55: trigger twice reset when wake-up from sleep mode by external wake-up source 你好,团队、 我们观察到,WKPU 模块寄存器在从 RESET 中唤醒后会被清除。 这可能是由CSSI触发的破坏性RESET引起的吗? 如果有,是否有其他方法在唤醒后保留或检索唤醒源信息? 谢谢。 唐生。 Re: S32N55: trigger twice reset when wake-up from sleep mode by external wake-up source 你好 Tangsheng, 是的,如果发生功能/破坏性重置,WKPU 寄存器将被清除。 对于修订版C. 板,我们可以看到唤醒后正在进行功能RESET——我们仍在调查该问题。在 Rev. A 主板上,此功能 RESET 不会发生。 为了解决 CSSI 破坏性重置问题,不应启用 SXOSC 的 CMU(从启用 SXOSC 的 CMU 的 Power_platform_runmodeTolowPower 中移除线路)。在我们禁用这个 CMU 之后,破坏性 RESET 不再出现在我们这边。
View full article
BL2 引导加载程序挂起 你好 我使用基于 S32G3 RDB3 板的自定义板配置作为 BSP43 的参考。版本完成了,但是在使用 fip.bin-qspi & flashimage.bin 文件刷机时,引导加载程序在执行 BL2 后挂起。它不会进入 BL31 功能。(见下面的截图)。   我已应用补丁进行调试。根据 UART 控制台的日志,BL31 的入口点地址设置为 0xFF600000。 根据 BSP43 UM,BL31 的基地址为 0xFF800000。 你能否也分享一下 BL31 & BL33 尺寸的详细信息,以便我们知道是否需要已翻译地址。 要求支持调试此问题。 Re: BL2 Bootloader Hang 你好,@y2jsh 不客气。 一般情况下不需要,我会通过支持系统继续支持您的问题。 BR 切宁 Re: BL2 Bootloader Hang 你好, 谢谢。您需要我的电子邮件或其他信息吗? Re: BL2 Bootloader Hang 你好,@y2jsh 感谢您的回复。 我想与大家分享一下我自己测试的应用程序,因为它太大了,无法在社区中分享, ,请允许我通过邮件发送。 BR 切宁 Re: BL2 Bootloader Hang 您好。 1.是的,我已经确定了文件& ,我正在闪存同样的文件。 2.是的,我按照您的要求做了。我收到的日志与我在最初的帖子中提到的相同。 Re: BL2 Bootloader Hang 你好,@y2jsh 很抱歉由于 PTO 而耽搁了。 1。 我能知道你有没有找到从 Yocto 生成的名为 fsl-image-flash-s32g399ardb3.flash-s32g399ardb3.flashimage 的图像吗? (或者名称相似,因为你使用了自定义板,不知道你是如何修改Yocto源代码/配置的),它通常可以通过命令 bitbake fsl-image-flash 生成。 2。只将 fsl-image-flash-s32g399ardb3.flashimage 刷新到你的 QSPI 上,然后将你的板设置为从 QSPI 启动,要检查能否正常启动,如果仍然有问题,请分享日志。 谢谢。 BR 切宁 Re: BL2 Bootloader Hang Helllo, 感谢您的答复。 我尝试了以下方法进行闪存调试: 1.我已经删除了所有内存 或非 & EMMC 这样启动就可以干净了,因为这将有助于调试问题。 2.我闪存了 fip.bin& flashimage.bin。 3. 我闪存了 dtb、fip& flashimage,结果也是同样的问题。 4. 我只闪过 fip,即使 RESET 后它也没有在 uart 主机上显示任何打印内容。 据我了解,我们的 yocto 输出中有 BL2 & U-Boot。 如果未闪存 DTB 文件,BL2 代码将无法执行。这是我的理解。 Re: BL2 Bootloader Hang 你好,@y2jsh 感谢您的回复。 我能理解你只能使用 BSP43 通过 QSPI 启动板。 在 BSP43 的默认情况下,一旦完成 Yocto 构建,就会生成多个图像。 1.如果你愿意直接刷新 fsl-image-flash-s32g399ardb3.flashimage,那么它包括过去从 QSPI 启动的所有镜像,那么你可能不需要刷新生成的其他镜像。(就像提到的 fip.b in-qspi 一样) 2.如果您只想刷新 Bootloader 部分(TFA 和 uboot),则可以按以下步骤刷新以下两个映像:用于 S32G3 的 BSP43UM 第 4.2.5 章 BR 切宁 Re: BL2 Bootloader Hang 你好, 1。我们正在使用恩智浦 git 仓库本身的 TF-A & 启动,查看 bsp43 分支 2。 至于 dtb.bin,我们没有将它们分开,fip.bin-qspi 也有 bl2 数据。你看到的 Linux 日志来自 fip 和 flashimage.bin 文件 Re: BL2 Bootloader Hang 你好,@y2jsh 感谢您的回复。 1.示例引导加载程序通常来自 GoldVIP 代码包或 Integration_Reference_Examples 软件包,我能知道你从哪里派生引导加载程序吗?来自哪个版本的 GoldVIP(或 Integration_Reference_Examples)? 2。通常,在使用 BSP42 或更早版本时,fip.bin 会被刷新到 QSPI,但是由于 BSP43,A53 端的启动映像被拆分为 2 个映像,那么你可能需要将 bl2_w_dtb.bin 闪存到 Q SPI 而不是 fip.bin。 BR 切宁 Re: BL2 Bootloader Hang 你好。 1.我怎样才能知道如何检查我使用的是哪个版本的引导加载器? 2。是的 fip.bin-qspi 使用 QSPI 闪存到或非闪存中 Re: BL2 Bootloader Hang 你好,@y2jsh 谢谢您的帖子。 请问您使用的启动程序版本是什么?我想板是从 QSPI 启动的,我能知道你把 fip.bin 放在哪里吗?在 QSPI 还是 SD 上? BR 切宁 BR 切宁
View full article
Hands-On Workshop: Advanced Debugging with MCUXpresso IDE This hands-on session will dive deep into the advanced debugging capabilities of the MCUXpresso IDE, including trace, profiling, coverage, watch points and more. This hands-on session will dive deep into the advanced debugging capabilities of the MCUXpresso IDE, including trace, profiling, coverage, watch points and more.
View full article
Win 10 IoT 不稳定千兆以太网修复 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 在运行 Windows 10 IoT Core 的 i.MX 主板上使用千兆以太网时,用户在使用构建 W1809_1_1_0_imx-iotcore 时可能会遇到网络不稳定和低延迟。通过增加以太网驱动程序中 Rx/Tx 缓冲区的大小可以解决这个问题。修复将成为 BSP 下一版本的一部分,为了将修复应用到当前版本,已创建了一个补丁。 要应用补丁,请将 zip 存档的内容复制到文件夹结构中的适当位置并重建 BSP。 Windows 10 IoT 核心版
View full article
DES-N1909 NXP USB Type-Cソリューション <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセクションでは、NXP(SIP)がUSB Type-Cコネクタを取り巻く主要製品を紹介します。このセクションでは、Power Delivery Controller、Power Delivery PHY、CCロジックコントローラー、高速スイッチ、および高速リドライバーについて説明します。NXP Type-Cハードウェアアーキテクチャ、差別化、および製品の利点について説明します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセクションでは、NXP(SIP)がUSB Type-Cコネクタを取り巻く主要製品を紹介します。このセクションでは、Power Delivery Controller、Power Delivery PHY、CCロジックコントローラー、高速スイッチ、および高速リドライバーについて説明します。NXP Type-Cハードウェアアーキテクチャ、差別化、および製品の利点について説明します。 デザイン |ソフトウェア&サービス
View full article
Adding I2C reads to your processing bandwidth constrained application Introduction With the growth of the Internet of Things (IoT), more and more applications are incorporating the use of sensors while also requiring power efficiency and increased performance.  A popular interface for these sensors is the I2C protocol. The I2C bus is a great protocol that is a true multi-master protocol and allows for each bus to contain many devices.  As the performance demand of the application grows, so will the speed of the I2C bus as it will be necessary to get more data from the sensors and/or at a faster rate.  Many applications may already have a need to operate an I2C bus at 400 kHz or more.  Higher data rates means the MCU core will need to spend more time servicing the I2C transactions.  The DMA module is one good way to free up the core in order to let it tend to other aspects of the application.  This can add much needed or much desired performance to applications.  Especially applications that may be using small, power efficient, single core MCUs. It may seem like an easy, straight-forward task to add I2C reads from a sensor to an application.  However I2C is a time sensitive protocol and consequently, so is the I2C peripherals on MCUs.  It is important to understand the time requirements and how to overcome them. The recommended approach is to use DMA to transfer the received I2C data to the desired buffer in your application software.  This document is going to outline how to setup your DMA and provide an example of how to do this for a KW40 device using the Kinetis SDK version 1.3.  The KW40 is being targeted because this is a small, power efficient MCU that incorporates a radio for your wireless applications and as such, it is likely that your application could need this DMA approach.  The KSDK version 1.3 is being targeted because this version of the SDK does not currently support DMA transactions for the I2C peripheral. Understanding the Kinetis I2C peripheral module Before getting into the specifics of creating a DMA enabled I2C driver, it is important to understand some basics of the Kinetis I2C peripheral module.  This module handles a lot of the low-level timing.  However the I2C registers must be serviced in a timely manner to operate correctly.  Take the case of a master reading data from a typical I2C sensor as shown in the diagram below. In the diagram above, the red lines indicate points in the transaction where software or DMA needs to interact with the I2C peripheral to ensure the transaction happens correctly.  To begin a transaction the core must change the MST bit which puts a start bit on the bus (marked by symbol ST).  Immediately following this, the core should then also write the target slave's address (Device Address) including the read/write bit (R/W).  Once this transaction is complete, the I2C will issue an interrupt and then the core should write the register address to be read from. Upon completion of that being put on the bus, the I2C will issue another interrupt and the master should then put a repeated start (SR) on the bus as well as the slave's address again.  Now the slave will send data to the master (once the master begins the transaction by issuing a dummy read of the I2C data register).  In the standard configuration, the I2C peripheral will automatically send the NAK or AK depending on the configuration of the TXAK bit in the I2C peripheral.  Because of this automation, it is important that this bit be handled properly and is configured one frame in advance. Furthermore, to ensure that the NAK bit is sent at the appropriate time, the TXAK bit must be set when the second to last byte is received.  The timing of this configuration change is very important to ensuring that the transaction happens properly. This document will describe how to use DMA to receive the data.  The DMA will be configured before the transaction begins and will be used to receive the data from the slave.  The document will also discuss options to handle proper NAK'ing of the data to end the transaction. Writing a DMA I2C master receive function The first step in adding DMA capability to your SDK driver is to create a new receive function with an appropriate name.  For this example, the newly created receive function is named I2C_DRV_MasterReceiveDataDMA.  To create this function, the I2C_DRV_MasterReceive function (which is called for both blocking and non-blocking) was copied and then modified by removing the blocking capability of the function. Then in this function, after the dummy read of the IIC data register that triggers the reception of data, the DMA enable bit of the I2C control register is written. /*FUNCTION********************************************************************** * * Function Name : I2C_DRV_MasterReceiveDataDMA * Description   : Performs a non-blocking receive transaction on the I2C bus *                 utilizing DMA to receive the data. * *END**************************************************************************/ i2c_status_t I2C_DRV_MasterReceiveDataDMA(uint32_t instance,                                                const i2c_device_t * device,                                                const uint8_t * cmdBuff,                                                uint32_t cmdSize,                                                uint8_t * rxBuff,                                                uint32_t rxSize,                                                uint32_t timeout_ms) {     assert(instance < I2C_INSTANCE_COUNT);     assert(rxBuff);     I2C_Type * base = g_i2cBase[instance];     i2c_master_state_t * master = (i2c_master_state_t *)g_i2cStatePtr[instance];             /* Return if current instance is used */     OSA_EnterCritical(kCriticalDisableInt);         if (!master->i2cIdle)     {         OSA_ExitCritical(kCriticalDisableInt);         return kStatus_I2C_Busy;     }         master->rxBuff = rxBuff;     master->rxSize = rxSize;     master->txBuff = NULL;     master->txSize = 0;     master->status = kStatus_I2C_Success;     master->i2cIdle = false;     master->isBlocking = true;     OSA_ExitCritical(kCriticalDisableInt);             while(I2C_HAL_GetStatusFlag(base, kI2CBusBusy));     I2C_DRV_MasterSetBaudRate(instance, device);         /* Set direction to send for sending of address. */     I2C_HAL_SetDirMode(base, kI2CSend);     /* Enable i2c interrupt.*/     I2C_HAL_ClearInt(base);     I2C_HAL_SetIntCmd(base, true);     /* Generate start signal. */     I2C_HAL_SendStart(base);     /* Send out slave address. */     I2C_DRV_SendAddress(instance, device, cmdBuff, cmdSize, kI2CReceive, timeout_ms);     /* Start to receive data. */     if (master->status == kStatus_I2C_Success)     {         /* Change direction to receive. */         I2C_HAL_SetDirMode(base, kI2CReceive);                 /* Send NAK if only one byte to read. */         if (rxSize == 0x1U)         {         I2C_HAL_SendNak(base);         }         else         {         I2C_HAL_SendAck(base);         }                 /* Dummy read to trigger receive of next byte in interrupt. */         I2C_HAL_ReadByte(base);                 /* Now set the DMA bit to let the DMA take over the reception. */         I2C_C1_REG(I2C1) |= I2C_C1_DMAEN_MASK;                 /* Don't wait for the transfer to finish. Exit immediately*/     }     else if (master->status == kStatus_I2C_Timeout)     {         /* Disable interrupt. */         I2C_HAL_SetIntCmd(base, false);                 if (I2C_HAL_GetStatusFlag(base, kI2CBusBusy))         {         /* Generate stop signal. */         I2C_HAL_SendStop(base);         }                 /* Indicate I2C bus is idle. */         master->i2cIdle = true;     }         return master->status; } After writing the DMA driver, a DMA specific transfer complete function must be implemented. This is needed in order for the application software to signal to the driver structures that the transfer has been completed and the bus is now idle. In addition, the DMA enable bit needs to be cleared in order for other driver functions to be able to properly use the IIC peripheral. void I2C_DRV_CompleteTransferDMA(uint32_t instance) {     assert(instance < I2C_INSTANCE_COUNT);     I2C_Type * base = g_i2cBase[instance];     i2c_master_state_t * master = (i2c_master_state_t *)g_i2cStatePtr[instance];         I2C_C1_REG(base) &= ~(I2C_C1_DMAEN_MASK | I2C_C1_TX_MASK);     I2C_C1_REG(base) &= ~I2C_C1_MST_MASK;;        /* Indicate I2C bus is idle. */     master->i2cIdle = true; } DMA Configuration Next, the application layer needs a function to configure the DMA properly, and a DMA callback is needed to properly service the DMA interrupt that will be used as well as post a semaphore. But before diving into the specifics of that, it is important to discuss the overall strategy of using the DMA in this particular application. After every transaction, the data register must be serviced to ensure that all of the necessary data is received.  One DMA channel can easily be assigned to service this activity.  After the reception of the second to last data byte, the TXAK bit must be written with a '1' to ensure that the NAK is put on the bus at the appropriate time. This is a little trickier to do.  There are three options: A second dedicated DMA channel can be linked to write the I2C_C1 register every time the I2C_D register is serviced.  This option will require a second array to hold the appropriate values to be written to the I2C_C1 register.  The following figure illustrates this process. The second DMA channel can be linked to write the I2C_C1 register after the second to last data byte has been received.  This option would require that the primary DMA channel be set to receive two data bytes less than the total number of desired data bytes.  The primary DMA channel would also need to be re-configured to receive the last two bytes (or the application software would need to handle this).  However this could be a desirable programming path for applications that are memory constrained as it reduces the amount of memory necessary for your application. The primary DMA channel can be set to receive two data bytes less than the total number of desired data bytes and the core (application software) can handle the reception of the last two bytes.  This would be a desirable option for those looking for a simpler solution but has the drawback that in a system where the core is already handling many other tasks, there may still be issues with writing the TXAK bit on time. This example will focus on option number 1, as this is the simplest, fully automatic solution.  It could also easily be modified to fit the second option as the programmer would simply need to change the number of bytes to receive by the primary DMA and add some reconfiguration information in the interrupt to service the primary DMA channel. DMA Channel #1 The first DMA channel is configured to perform 8-bit  transfers from the I2C data register (I2C_D) to the buffer to hold the desired data.  This channel should transfer the number of desired bytes minus one.  The final byte will be received by the core.  Other DMA configuration bits that are important to set are the cycle steal bit, disable request bit, peripheral request bit (ERQ), interrupt on completion of transfer (EINT), and destination increment (DINC).  It also important to configure the link channel control to perform a link to channel LCH1 after each cycle-steal transfer and LCH1 should be configured for the channel that will transfer from memory to the I2C control register (I2C_C1).  The first DMA channel is configured as shown below. // Set Source Address (this is the UART0_D register       DMA_SAR0 = (uint32_t)&I2C_D_REG(base);             // Set BCR to know how many bytes to transfer       // Need to set to desired size minus 1 because the last will be manually       // read.        DMA_DSR_BCR0 = DMA_DSR_BCR_BCR(destArraySize - 1);             // Clear Source size and Destination size fields.        DMA_DCR0 &= ~(DMA_DCR_SSIZE_MASK                     | DMA_DCR_DSIZE_MASK                     );       // Set DMA as follows:       //     Source size is byte size       //     Destination size is byte size       //     D_REQ cleared automatically by hardware       //     Destination address will be incremented after each transfer       //     Cycle Steal mode       //     External Requests are enabled       //     Interrupts are enabled       //     Asynchronous DMA requests are enabled.       //     Linking to channel LCH1 after each cycle steal transfer       //     Set LCH1 to DMA CH 1.        DMA_DCR0 |= (DMA_DCR_SSIZE(1)             // 1 = 8-bit transfers                    | DMA_DCR_DSIZE(1)           // 1 = 8-bit transfers                    | DMA_DCR_D_REQ_MASK                    | DMA_DCR_DINC_MASK                    | DMA_DCR_CS_MASK                    | DMA_DCR_ERQ_MASK                    | DMA_DCR_EINT_MASK                    | DMA_DCR_EADREQ_MASK                    | DMA_DCR_LINKCC(2)          // Link to LCH1 after each cycle-steal transfer                    | DMA_DCR_LCH1(1)            // Link to DMA CH1                    );       // Set destination address       DMA_DAR0 = (uint32_t)destArray; DMA Channel #2 The second DMA channel, which is the linked channel, should be configured to perform 8-bit transfers that transfer data from an array in memory (titled ack_nak_array in this example) to the I2C control register (I2C_C1).  This channel should also disables requests upon completion of the entire transfer, and enable the cycle-steal mode.  In this channel, the source should be incremented (as opposed to the destination as in the first channel). This channel is configured as shown below: // Set Source Address (this is the UART0_D register       DMA_SAR1 = (uint32_t)ack_nak_array;             // Set BCR to know how many bytes to transfer       // Need to set to desired size minus 1 because the last will be manually       // read.       DMA_DSR_BCR1 = DMA_DSR_BCR_BCR(destArraySize - 1);             // Clear Source size and Destination size fields.        DMA_DCR1 &= ~(DMA_DCR_SSIZE_MASK                     | DMA_DCR_DSIZE_MASK                     );             // Set DMA as follows:       //     Source size is byte size       //     Destination size is byte size       //     D_REQ cleared automatically by hardware       //     Destination address will be incremented after each transfer       //     Cycle Steal mode       //     External Requests are disabled       //     Asynchronous DMA requests are enabled.       DMA_DCR1 |= (DMA_DCR_SSIZE(1)             // 1 = 8-bit transfers                    | DMA_DCR_DSIZE(1)           // 1 = 8-bit transfers                    | DMA_DCR_D_REQ_MASK                    | DMA_DCR_SINC_MASK                    | DMA_DCR_CS_MASK                    | DMA_DCR_EADREQ_MASK                    );             // Set destination address       DMA_DAR1 = (uint32_t)&I2C_C1_REG(base); Once the DMA channels are initialized, the only action left is to configure the interrupts, enable the channel in the DMA MUX, and create the semaphore if it has not already been created.  This is done as shown below. //Need to enable the DMA IRQ       NVIC_EnableIRQ(DMA0_IRQn);       //////////////////////////////////////////////////////////////////////////       // MUX configuration       // Enables the DMA channel and select the DMA Channel Source        DMAMUX0_CHCFG0 = DMAMUX_CHCFG_SOURCE(BOARD_I2C_DMAMUX_CHN); //DMAMUX_CHCFG_ENBL_MASK|DMAMUX_CHCFG_SOURCE(0x31); //0xb1;       DMAMUX0_CHCFG0 |= DMAMUX_CHCFG_ENBL_MASK;             /* Create semaphore */       if(semDmaReady == NULL){         semDmaReady = OSA_EXT_SemaphoreCreate(0);       } Finally, the DMA initialization function also initializes the ack_nak_array.  This is only necessary when implementing the first DMA strategy.  The second DMA strategy would only need to write a single value at the correct time.  The array initialization for strategy #1 is shown below.  Note that the values written to the array are 0xA1 plus the appropriate value of the TXAK bit.  By writing 0xA1, it is ensured that the I2C module will be enabled in master mode with the DMA enable bit set. // Initialize Ack/Nak array       // Need to initialize the Ack/Nak buffer first       for( j=0; j < destArraySize; j++)       {           if(j >= (destArraySize - 2))           {               ack_nak_array[j] = 0xA1 | I2C_C1_TXAK_MASK;           }           else           {               ack_nak_array[j] = 0xA1 & (~I2C_C1_TXAK_MASK);           }       } DMA Interrupt Handler Now a DMA interrupt handler is required.  A minimum of overhead will be required for this example as the interrupt handler simply needs to service the DONE bit and post the semaphore created in the initialization.  The DMA interrupt handler is as follows: void DMA0_IRQHandler(void) {     // Clear pending errors or the done bit     if (((DMA_DSR_BCR0 & DMA_DSR_BCR_DONE_MASK) == DMA_DSR_BCR_DONE_MASK)         | ((DMA_DSR_BCR0 & DMA_DSR_BCR_BES_MASK) == DMA_DSR_BCR_BES_MASK)         | ((DMA_DSR_BCR0 & DMA_DSR_BCR_BED_MASK) == DMA_DSR_BCR_BED_MASK)         | ((DMA_DSR_BCR0 & DMA_DSR_BCR_CE_MASK) == DMA_DSR_BCR_CE_MASK))     {         // Clear the Done MASK and set semaphore, dmaDone         DMA_DSR_BCR0 |= DMA_DSR_BCR_DONE_MASK;         //dmaDone = 1;         OSA_SemaphorePost(semDmaReady);     } } Using your newly written driver function Once all of these items have been taken care of, it is now time for the application to use the functions. It is expected that the DMA will be initialized before calling the DMA receive function.  After the first call, the DMA can be re-initialized every time or could simply be reset with the start address of the arrays and byte counter (this is the minimum of actions that must be performed).  Then the application should ensure that the transaction happened successfully.   Upon a successful call to the I2C_DRV_MasterReceiveDataDMA function, the application should wait for the semaphore to be posted.  Once the semaphore posts, the application software should wait for the Transfer Complete flag to become set.  This ensures that the application does not try to put a STOP signal on the bus before the NAK has been physically put on the bus.  If the STOP signal is attempted out of sequence, the I2C module could be put in an erroneous state and the STOP signal may not be sent.  Next, the I2C_DRV_CompleteTransferDMA function should be called to send the STOP signal and to signal to the driver structures that the bus is idle.  At this point, the I2C transaction is now fully complete and there is still one data byte that hasn't been transferred to the receive buffer.  It is the application's responsibility to perform one last read of the Data register to receive the last data byte of the transaction. /* Now initialize the DMA */    dma_init(BOARD_I2C_INSTANCE, Buffer, ack_nak_buffer, FXOS8700CQ_READ_LEN); //Init DMAMUX       returnValue = I2C_DRV_MasterReceiveDataDMA(BOARD_I2C_INSTANCE, &slave,                                                   cmdBuff, 1, Buffer, FXOS8700CQ_READ_LEN, 1000); if (returnValue != kStatus_I2C_Success)    {        return (kStatus_I2C_Fail);    } /* Wait for the DMA transaction to complete */    OSA_SemaphoreWait(semDmaReady, OSA_WAIT_FOREVER);       /* Need to wait for the transfer to complete */ for(temp=0; temp<250; temp++)     {         if(I2C_HAL_GetStatusFlag(base, kI2CTransferComplete))         {             break;         }     }       /* Now complete the transfer; this includes sending the I2C STOP signal and       clearing the DMA enable bit */    I2C_DRV_CompleteTransferDMA(BOARD_I2C_INSTANCE);       // Once the Transfer is complete, there is still one byte sitting in the Data    // register.      Buffer[11] = I2C_D_REG(g_i2cBase[BOARD_I2C_INSTANCE]); Conclusion To summarize, as consumers demand more and more power efficient technology with more and more functionality, MCU product developers need to cram more functionality in small power efficient MCUs.  Relying on DMA for basic data transfers is one good way to improve performance of smaller power efficient MCUs with a single core. This can be particularly useful in applications where an MCU needs to pull information from and I2C sensor.  To do this, there are three methods of implementing an I2C master receive function in your SDK 1.3 based application. Use two DMA channels.  The first to transfer from the I2C Data register to the destination array.  A second dedicated DMA channel can be linked to write the I2C_C1 register every time the I2C_D register is serviced. Use two DMA channels.  The first to transfer from the I2C Data register to the destination array. The second DMA channel can be linked to write the I2C_C1 register only after the second to last data byte has been received. Use a single DMA channel can be set to receive two data bytes less than the total number of desired data bytes and the core (application software) can handle the reception of the last two bytes. The recommendation of this document is to implement the first or second option as these are fully automatic options requiring the least intervention by the core. Kinetis E Series MCUs Kinetis EA Series MCUs Kinetis K Series MCUs Kinetis L Series MCUs Kinetis M Series MCUs Kinetis V Series MCUs Kinetis W Series MCUs Re: Adding I2C reads to your processing bandwidth constrained application Hi Mark, I don't think it is anything that you have done wrong necessarily.  I did see this in testing but it didn't hold me up and I could never really find the solution, so I felt I had to get something out there knowing that this might come back up.  I think this error is due to some kind of compatibility issue between the version of IAR that the project was created in and the version you are using.  So I think there are two options: 1) Delete what you unzipped and re-unzip the package to the same location and open with IAR 7.50.3 if you have that version or can get it. 2) Create a new project from scratch and copy the settings from the example I have provided.  When I get a little more time maybe I'll create a version in the latest version of IAR and hopefully that will be better.  You are using IAR v7.70? Regards, Chris Re: Adding I2C reads to your processing bandwidth constrained application If there are directories in the Path that do not exist GCC can take forever to build something. It is also wise to avoid any paths with with spaces when possible.  Don't locate projects in such paths. Re: Adding I2C reads to your processing bandwidth constrained application Hello, Tried running the above zip file per the instructions in the readme.txt file. I unzipped the project into C:\Freescale\KW40Z_Connectivity_Software_1.0.1\ConnSw\examples\bluetooth. Clicked on the workspace C:\Freescale\KW40Z_Connectivity_Software_1.0.1\ConnSw\examples\bluetooth\bluetooth_running_speed_cadence_sensor_with_i2c\bluetooth_running_speed_cadence_sensor_with_i2c\bluetooth_running_speed_cadence_sensor_with_i2c.eww I did a clean and a build and got several errors that the paths were too long. I know the readme.txt files says to ignore the long path errors but it never completed the build after a few hours. So I gave up. Any idea what I might have done wrong? Thanks! Mark Re: Adding I2C reads to your processing bandwidth constrained application Understood.  And this document targets Connectivity applications that would be using the Connectivity Stack.  Re: Adding I2C reads to your processing bandwidth constrained application OSA_EXT_... API functions are OS Abstraction layer extensions brought in by the connectivity framework distributed for Kinetis W parts. These extensions are used mainly by the connectivity stacks and are not present in the vanilla Kinetis SDK v1.3 build. One can use the code examples above if downloading the KW40Z connectivity software package from here: http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/kinetis-cortex-m-mcus/w-series-wireless-m0-plus-m4/kinetis-kw41z-2.4-ghz-dual-mode-ble-and-802.15.4-wireless-radio-microcontroller-mcu-based-on-arm-cortex-m0-plus-core:KW40Z?fpsp=1&tab=Design_Tools_Tab Re: Adding I2C reads to your processing bandwidth constrained application How should the broken Repeated Start in the MKL27 family be dealt with?
View full article
S32K3 FlexCAN TASD 计算 本文档简要介绍了基于 Excel 开发的计算器,该工具用于辅助计算 S32K3 参考手册所述的 TX 仲裁启动延迟。 该工具实现了数据手册中提供的公式,允许用户输入相关参数并自动计算延迟值。它旨在支持工程师评估 CAN 传输时序并优化基于 S32K3 的仲裁性能。 1.请根据您的要求填写时钟、CBT 和 FDCBT 配置参数。 例如,我们根据案例 3 填入参数: 这样我们就能得到非FD帧的TASD值是24.05。 请注意,本摘要并非 NXP 官方版本。这是个人摘要,仅供参考。如有任何错误,请联系我。
View full article
i.MX v15.1 配置工具现已推出 我们很高兴地宣布,i.MX v15.1 的配置工具现已推出。 下载与链接 如需下载适用于所有平台的安装程序,请通过以下链接登录我们的下载网站: https://www.nxp.com/design/designs/config-tools-for-i-mx-applications-processors:CONFIG-TOOLS-IMX 有关安装和快速入门指南,请参考文档。 如需了解有关 DDR 配置和验证的更多信息,请访问此 博客文章。 发布说明 发布的完整详细信息(功能、已知问题……) 版本 15.1 • 在 MacOS aarch64 上,缺失的概述已修复。 • 球座 – 引脚表现在仅包含特定配置的项目(掩码/安全/中断)。
View full article
例MPC5746R DSPI_serialization S32DS。パワー.2.1 ******************************************************************************** *詳細な説明: ※例では、基本的な初期化を行い、PLLを最大許容周波数までセットアップします。 *周辺機器、GPIOピンのセットアップクロック。 * DSPI_M1はマスターとして設定され、DSI機能はeTPUチャネルをシリアル化するように構成されています。 *出力。eTPU から DSI へのルーティングは、SIU 設定によって行われます。 *ユーザーは、スコープまたはロジックアナライザでSPI波形を確認できます。 * ------------------------------------------------------------------------------ *テストHW:MPC5746R-252DC、MPC57xxマザーボード ※MCU:SPC5746RMMT5 CTQG1740 1N83M HKBGCTB * Fsys:PLL 200MHz *デバッガ:Lauterbach Trace32 *対象:internal_FLASH、RAM *端末:19200-8-パリティなし-1ストップビット-フロー制御なし * EVB接続:以下のピンをスコープまたはロジックアナライザに接続します ・PA7:DSPI_M1 SOUT(マザーボードピンPP[7]) ・PA9:DSPI_M1 SCLK(マザーボードピンPP[9]) ※PA13:DSPI_M1 CS0(マザーボードピンPP[13]) ********************************************************************************
View full article
Linux Embedded Challenge Projects - 2014 1. Adaptive Dynamic Headlights with Pedestrian Spotlight Function - by eVision Team members: Balaban Valeriu  - Master, Advanced Microelectronics, Electronics, UPB Voicu Tudor Alexandru - Bachelor, Applied Electronics, Electronics, UPB Stanescu Sebastian - Bachelor, Telecom Networking and Software, UPB Short description:     Because of the high rate of fatalities between night accidents a lot of research are held for developing techniques to increase the driver area of vision during the night and to reduce the accident damage if this could not be avoided. The adaptive headlight function helps to see further in poor light conditions and especially in bends: the cornering light swivels the headlights in the direction of travel, with the degree of turn computed by a CPU, to illuminate as much road area as possible     An interesting solution is spotlight lighting function, which is a LED beam that specifically illuminates potential hazards. If the near infrared camera detects deer at the roadside or pedestrians on the road, they can be briefly illuminated beyond the normal area covered by the main beams, by a spot-light to attention the driver for a possible danger. Presentation: Please consult eVisionPresentation.pdf. Documentation: Please consult eVisionDoc.pdf. Code Sources https://github.com/izzi/app-evision https://github.com/izzi/meta-evision 2. Voice Commanded Interface for DriverVehicle Interaction - by She# Team members: Iulia Neagoe - Computer Sciences and Military Information Systems,Military Technical Academy Mihaela-Anca Sorostinean - Computer Sciences and Military Information Systems,Military Technical Academy Short description:     In the context of continuous technological advances in the automotive and communications domains, a drivers responsibility has switched from just controlling the car to interacting with the multitude of gadgets provided by the manufacturer. The purpose of this project is to design an interface that offers the driver the possibility of controlling some of the nonvital functionalities of the car by vocal commands, so as to enable the driver to focus his attention on the road while also having a comfortable mean of communication with the car.      We developed a system of vocal recognition of some basic features like the radio, windows, clima or a phone which we implemented on the Wandboard. Also we provide the user with a graphical interface of the recognized commands in order to enhance his interaction with the vehicle. Presentation: Please consult ShePresentation.pdf. Documentation: Please consult SheDoc.pdf. Code Sources Please see She#_Project_Source.zip. 3. Driving Control Software - by FreeSoftwares Team members: Petrosanu Adrian-Sabin - Computer Science, UPB Birsan Nicoleta Cosmina - Computer Science, UPB Radoi Ioana Gabriela - Computer Science, UPB Short description: "Driving Control Software" is a soft to control an automatic gearbox. This project consists of simulating the behavior of an automatic gearbox on the Wandboard. An automatic gearbox is a type of motor vehicle transmission that can automatically change gear ratios as the vehicle moves. Presentation: Please consult FreeSoftwaresPresentation.pdf. Documentation: Please consult FreeSoftwaresDoc.pdf. Code Sources Please see Freesoftwares_Project_Source.zip. 4. Autonomous Car Parking - by ATM Team members: Mihai Coca - Computer Sciences and Military Information Systems,Military Technical Academy Georgian Andrei - Computer Sciences and Military Information Systems,Military Technical Academy Hiji Iulian - Computer Sciences and Military Information Systems,Military Technical Academy Short description: A large number of companies are developing autonomous vehicle technology through applying its work in the area to a particular usage case : parking. The purpose of this project is to design a concept vehicle, which can be dropped off at the curb by its owner and left to its own devices to enter into a spot park. The process can even be reversed when the owner is ready to go, with the car leaving the spot park on its own to meet its key-holder again at the curb. Documentation: Please consult ATMDoc.pdf Code Sources Please see ATM_Project_Source.zip. 5. Collision Detection - by Beer2.0 Team members: Nitu Adrian - Computer Science, UPB Short description: The purpose of our project is to provide cars with a sense of the road ahead and enable it to take preventive actions against collisions; In this way we hope to reduce accidents on the road. It will gather signals and informations from different hardware and will alert the driver or take immediate control of the car in order to make critical maneuvers in order to protect the driver from any life threatening event. A Freescale Cup car will be equipped with a Wandboard and two USB cameras so we can track the environment. After initial object tracking we will incorporate Human Interaction by remote control. For this project we believe a simple warning system and/or breaking will suffice as a proof of concept. Presentation: Please consult Beer20Presentation.pdf Documentation: Please consult Beer20Doc.pdf Code Sources https://bitbucket.org/adriannitu92/freechallenge 6. Feedforward adaptive noise cancellation using sub-band normalized filtered-X LMS algorithm - by Brainiacs Team members: Cristian Monea - Telecommunications and Information Technology, Electronics, UPB Madalin Zaharia - Telecommunications and Information Technology, Electronics, UPB Short description This project proposes a feedforward adaptive noise cancellation (ANC) algorithm based on sub-band normalized filtered-X LMS (NFXLMS). The use of an adaptive algorithm offers advantages over simple filtering algorithms like fixed FIR or IIR filters. Also, noise generated in a car environment can be considered stationary because it preserves some of its properties, like spectral distribution, mean, variance, which allows the use of adaptive filters in car noise cancellation applications. The feedforward system should be more efficient than feedback systems. In this case, a coherent reference noise input is sensed before it propagates past the canceling speaker. Thus, the algorithm will simulate the two sensors (microphones): reference sensor, which measures the primary noise to be canceled, and the error sensor. Presentation: Please consult BrainiacsPresentation.pdf Documentation: Please consult BrainiacsDoc.pdf Linux Embedded Challenge 2014
View full article
FreeMASTER 3.0.1 更新 - 发布公告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> NXP FreeMASTER 工具更新版本 3.0.1 刚刚在线发布。 欲了解更多详细信息,请阅读最近发布的FreeMASTER 3.0 公告。另请参阅http://www.nxp.com/freemaster上的下载、文档和其他资源。 新版本主要变化: 增加了使用 PCANBasic API 对 PEAK-System CAN (PCAN) 设备的支持 P&E Micro BDM 插件已更新,以支持最新的 P&E 调试接口电缆。 数据包驱动的 BDM 插件配置对话框在搜索 PDBDM 命令缓冲区时扩展了可用目标设备和有效 RAM 范围的列表。 错误修复和其他小改动: 修复了在 big-endian 系统上使用旧 V1-V3 协议版本读取示波器数据的问题。 修复使用旧协议版本时手动记录器停止的问题。 项目树项目的展开/折叠状态现在存储到项目文件中,并在项目打开时恢复(仅限 PMPX 文件格式)。 读取大数据块(例如读取嵌入式项目文件(使用 fmstr:// 协议)变得更加健壮,并且不容易出现通信错误。 修复了使用旧协议版本时令人困惑的记录器名称“未找到”的问题。 修复了记录器属性对话框中总记录点大小的计算。 修复了导出的 FreeMASTER Lite 配置文件中的错误 JSON 键。 感谢您使用 NXP 产品和 FreeMASTER 工具。 回复:FreeMASTER 3.0.1 更新 - 发布公告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好,Michal, 非常感谢您推动我的愿望清单:smileyhappy:。 不幸的是,我无法使用 PCAN 接口。我已将 PCANBasic.dll 放在所有文件夹中,并尝试使用 regsvr32 对其进行注册。但是我没有在 CAN 下拉列表中看到新行... 希望您能给我指明正确的方向。 (顺便说一句:展开/折叠状态的 pmpx 可以工作 - 但为什么加载 pmpx 文件比 pmp 慢得多?) 此致 Sebastian
View full article
i.MX Android Introduction.pptx Brief introduction on i.MX Android Brief introduction on i.MX Android Android
View full article
适用于 KV4x、KV5x、MC56F84xxx 和 MC56F82xxx 的两个或多个 eFlexPWM 同步 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 文档介绍了如何基于MC56F84789实现两个eFlexPWM模块的同步,并给出了从示波器复制的PWM信号波形,可以看出eFlexPWMA和eFlexPWMB的所有PWM信号都是同步的。 对于 eFlexPWMA,主同步信号用于同步 eFlexPWMA 的其他子模块。对于 eFlexPWMB 模块,eFlexPWMA 生成 PWMA0_TRIG 信号(与 eFlexPWMA 的主同步信号相同),PWMA0_TRIG 信号通过交叉开关连接到 PWMB0_EXT_SYNC、PWMB1_EXT_SYNC、PWMB2_EXT_SYNC。 回复:KV4x、KV5x、MC56F84xxx 和 MC56F82xxx 的两个或多个 eFlexPWM 同步 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我使用直接地址编写了相同的代码,PWM 对所有子模块都运行良好。 像这样,(*(volatile uint16_t *) 0x40033002U) = 0; //PWMA_SM0Initial 0 我可以监控寄存器 PWMA_SMnSTS 来了解 pwm 寄存器的加载是否正确。这样,寄存器重新加载错误标志就不会被启用。 使用结构体时同样不起作用(在 ARM 系列控制器中,所有寄存器映射都是通过结构定义完成的)。 基地址->SM[0].VAL0 = 0; 如果我使用这种配置设置,我可以在寄存器 PWMA_SMnSTS 中看到寄存器重新加载错误标志设置。 请调查一下这个问题。
View full article
学习我们的经验!利用恩智浦支持,快速完成 QorIQ ® LS1012A、LS1043A 和 LS1046A 设计 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 从我们与数千名 Layerscape 客户合作的经验中学习。我们将分享通过设计 NXP LS1012A、LS1043A 和 LS1046A 产品以及协助早期采用者所学到的技巧和窍门。这些产品适用于需要高核心性能和高集成度的成本和功耗敏感型应用。我们还将回顾恩智浦提供的各种工具服务和支持。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 从我们与数千名 Layerscape 客户合作的经验中学习。我们将分享通过设计 NXP LS1012A、LS1043A 和 LS1046A 产品以及协助早期采用者所学到的技巧和窍门。这些产品适用于需要高核心性能和高集成度的成本和功耗敏感型应用。我们还将回顾恩智浦提供的各种工具服务和支持。
View full article
パワートレイン&ビークルダイナミクス:NXPのxEVエネルギーマネジメントソリューション <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> この地域では、各OEMが2020年までに生産台数の12%をZEVとして製造・販売すると予想しており、大都市では従来のICE車が禁止され、自動車メーカーは新しいEVを発表する頻度が増加しています。このセッションでは、EV市場に影響を与える主な力の概要を説明し、主なアーキテクチャアプローチとシステムコンポーネント、およびこれがNXPにどのような成長の可能性をもたらすかについて説明します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> この地域では、各OEMが2020年までに生産台数の12%をZEVとして製造・販売すると予想しており、大都市では従来のICE車が禁止され、自動車メーカーは新しいEVを発表する頻度が増加しています。このセッションでは、EV市場に影響を与える主な力の概要を説明し、主なアーキテクチャアプローチとシステムコンポーネント、およびこれがNXPにどのような成長の可能性をもたらすかについて説明します。
View full article