Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
示例 MPC5604B ADC-Pot-ADCWatchDog-INTC-printf CW210 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** * 详细说明: * 示例根据板上电位器调暗 LED1。LED2 和 LED3 演示 * ADC 看门狗功能。当信号电平低于低电平时,LED2 亮起 * 阈值,当信号高于高阈值时,LED3 亮起。 * 示例还将转换结果显示到终端窗口。 * ---------------------------------------------------------------------------------------------- * 测试硬件:XPC560B 100LQFP,XPC56XX EVB MOTHEBOARD Rev.C * 微控制器: PPC5604BE MLL 1M27V * 终端:19200-8-无奇偶校验-1 停止位-LINFLEX_0 无流量控制 * 系统频率:64/48 MHz * 调试器:Lauterbach Trace32 * PeMicro USB-ML-PPCNEXUS * 目标:RAM、internal_FLASH * EVB 连接: - 将 PB[8] 初始化为 ANS0:将电位器连接到 PB[8] 引脚,移除 J30 跳线并将 J30.2 与 P2.9 连接 - 接头 J8 (LED_EN) 已完全安装 ******************************************************************************** <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** * 详细说明: * 示例根据板上电位器调暗 LED1。LED2 和 LED3 演示 * ADC 看门狗功能。当信号电平低于低电平时,LED2 亮起 * 阈值,当信号高于高阈值时,LED3 亮起。 * 示例还将转换结果显示到终端窗口。 * ---------------------------------------------------------------------------------------------- * 测试硬件:XPC560B 100LQFP,XPC56XX EVB MOTHEBOARD Rev.C * 微控制器: PPC5604BE MLL 1M27V * 终端:19200-8-无奇偶校验-1 停止位-LINFLEX_0 无流量控制 * 系统频率:64/48 MHz * 调试器:Lauterbach Trace32 * PeMicro USB-ML-PPCNEXUS * 目标:RAM、internal_FLASH * EVB 连接: - 将 PB[8] 初始化为 ANS0:将电位器连接到 PB[8] 引脚,移除 J30 跳线并将 J30.2 与 P2.9 连接 - 接头 J8 (LED_EN) 已完全安装 ******************************************************************************** 概述
View full article
下一代功能安全架构 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 概述 S32x 下一代安全架构,涵盖 ASIL B 至 ASIL D。有哪些新功能以及我们如何更好地为客户提供全套安全附属品,包括 MCU HW、SW 和 SBC HW。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 概述 S32x 下一代安全架构,涵盖 ASIL B 至 ASIL D。有哪些新功能以及我们如何更好地为客户提供全套安全附属品,包括 MCU HW、SW 和 SBC HW。
View full article
澳洲大学挂科怎么办 澳洲大学挂科怎么办联系QQ1252839746,考试挂科作弊、GPA低被开除退学、收到学术警告。澳洲大学2018 S1的Final成绩已经在陆续发放了,拿到成绩的时候,有些人难免会沮丧,复习了的内容没考,考的内容没复习,所以就有科目理所应当的挂科了…… 澳洲大学向来是宽!进!严!出!随着成绩的公布,小伙伴们都在问挂科了到底该怎么办?一起来了解一下不同情况的挂科该如何处理吧! 同一学期挂科科目挂科小于等于50% 什么叫挂科科目小于等于50%呢?各大学的课程设置都是一学期4门课,如果你在一学期中挂了1-2门,但是还没有出现double fail(一科已经连续fail两次以上),那么学校不会对你有任何行动,下学期一定要争取4门全部Pass来弥补! 同一学期挂科科目挂科大于等于50% 大于等于50%的意思就是如果在一学期中挂了2门以上课程,那一般学校就会采取第一次行动了,会对你发出一封警告信! 学校出勤率低于80% 和挂科无关,但非常重要。如果同学们在一学期中,因各种原因出勤率不满80%的,并且针对这过低的出勤率没有合理的理由,学校也会先对你做出警告需要解释,如果理由没有被学校接受,学校也有资格将你上报移民局,移民局可以会跟据情况取消签证。 努力学习却还是挂科 如果是平时十分努力却还是掌控不了挂科的同学门要及早正视自己的问题,对自己挂科的原因进行总结,可能是由于专业不适合,学习能力不够,学校和你的学习理念存在差异……而这类学生最重要的就是正视自己的情况考虑转学校或者是换专业。 警告信解释 当你不幸收到开除警告信后,书面解释的质量非常重要。 首先,解释列举的原因,一定是不可控的因素,由此导致的学习成绩差;接着表明自己坚信可以完成学业,并列举理由;最后认真的规划应该如何去克服困难,努力提高成绩。 如果以身体健康原因作为理由,必须准备辅助材料,如医生开具的证明等,一同上交。校方受理后会决定十分需要召开听证会,听证会后即会给出解释结果。 转校 这里需要提醒小伙伴们如果被公立大学开除,则无法转到其它公立大学继续学习,只能转到各种私立大学或学院,但可以在收到学校警告信后,马上开始准备转学事宜,在开除程序正式开始之前申请转学。 转学 若未读满6个月的课程就申请转学,首先需要获得想转学学校OFFER,然后向在读学校申请Release letter(放行信),在读学校会根据转学政策和程序审核申请,再决定是否发放Release letter; 如果已经在主课学校就读超过六个月,一般学校都会同意学生的转学申请。 在澳洲挂科除了昂贵的学费外,还有可能会面临强制退学和取消学生签证,并且3年都不得进入澳洲,所以要谨慎对待每次考试,澳洲大学挂科改成绩(Q1252839746)挂科GPA成绩修改,解决被退学开除等问题。 General
View full article
DES-N2005 发挥您的创造力,从专家的个人指导中学习最新的 LPPeripherals 如何为您的最终应用提供硬件和软件优势 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议涵盖的主题包括如何利用 LPC 的状态控制器计时器 (SCT) 创造性地解决嵌入式应用中面临的挑战,例如与数字 LED 控制接口、监听传感器时对脉冲进行硬件检测等。专家将演示为什么 LPC 状态控制器计时器 (SCT) 是市场上最简单的计时器,提供实践培训,引导您完成一系列演示,其中 SCT 能够解决相当复杂的挑战。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议涵盖的主题包括如何利用 LPC 的状态控制器计时器 (SCT) 创造性地解决嵌入式应用中面临的挑战,例如与数字 LED 控制接口、监听传感器时对脉冲进行硬件检测等。专家将演示为什么 LPC 状态控制器计时器 (SCT) 是市场上最简单的计时器,提供实践培训,引导您完成一系列演示,其中 SCT 能够解决相当复杂的挑战。 设计 | 软件与服务
View full article
示例 MPC5777C MCAN-FD simpleTX RX-ISR GHS616 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** * 详细说明: * * 配置 MCAN 发送和接收带有或不带有 CAN FD 消息 * 数据阶段的比特率切换。这是由 BRS 宏定义的。 * 仲裁阶段的波特率设置为 500kbps,数据阶段的波特率设置为 1Mpbs * 因为 EVB 上使用了 PHY。 * * 在此配置中,MCAN_0 传输一条消息。MCAN_1接收消息。 * * MCAN_0 每 1 秒发送一次消息。该间隔由 PIT 生成。 * 单个 TX 缓冲区用于发送 n 个字节。每次 * 传播。发送两个标准 ID 和 2 个扩展 ID。 * * MCAN_1 配置为接收消息,ISR 用于读取新消息。 * 定义了2个标准和2个扩展ID过滤表。经典过滤器 * 配置已设置,表示过滤器 ID 和掩码。 * 具有匹配标准 ID 的消息被接收到 RXFIFO_0 中,具有匹配 * 扩展ID然后存储在RXFIFO_1中。 * * EVB连接: * * J37 和 J38 至位置 2-3,将 MCAN1 TX/RX 连接至收发器 * * P15-1 上的 CAN0-CANH 至 P14-1 上的 CAN1-CANH * P15-2 上的 CAN0-CANL 至 P14-2 上的 CAN1-CANL * * * ---------------------------------------------------------------------------------------------- * 测试硬件:MPC5777C-512DS Rev.A + MPC57xx 主板 Rev.C * 微控制器: PPC5777CMM03 2N45H CTZZS1521A *系统频率:PLL1 = core_clk = 264MHz,PLL0 = 192MHz * 调试器:Lauterbach Trace32 * 目标:internal_FLASH * 终端:19200-8-无奇偶校验-1停止位-eSCI_A上无流量控制 * 使用微型模块上的 USB 连接器 (J21) * * EVB 连接:ETPUA30(PortP P23-15)--> USER_LED_1(P7-1) * ETPUA31 (端口 P23-14) --> USER_LED_2 (P7-2) * ******************************************************************************** <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** * 详细说明: * * 配置 MCAN 发送和接收带有或不带有 CAN FD 消息 * 数据阶段的比特率切换。这是由 BRS 宏定义的。 * 仲裁阶段的波特率设置为 500kbps,数据阶段的波特率设置为 1Mpbs * 因为 EVB 上使用了 PHY。 * * 在此配置中,MCAN_0 传输一条消息。MCAN_1接收消息。 * * MCAN_0 每 1 秒发送一次消息。该间隔由 PIT 生成。 * 单个 TX 缓冲区用于发送 n 个字节。每次 * 传播。发送两个标准 ID 和 2 个扩展 ID。 * * MCAN_1 配置为接收消息,ISR 用于读取新消息。 * 定义了2个标准和2个扩展ID过滤表。经典过滤器 * 配置已设置,表示过滤器 ID 和掩码。 * 具有匹配标准 ID 的消息被接收到 RXFIFO_0 中,具有匹配 * 扩展ID然后存储在RXFIFO_1中。 * * EVB连接: * * J37 和 J38 至位置 2-3,将 MCAN1 TX/RX 连接至收发器 * * P15-1 上的 CAN0-CANH 至 P14-1 上的 CAN1-CANH * P15-2 上的 CAN0-CANL 至 P14-2 上的 CAN1-CANL * * * ---------------------------------------------------------------------------------------------- * 测试硬件:MPC5777C-512DS Rev.A + MPC57xx 主板 Rev.C * 微控制器: PPC5777CMM03 2N45H CTZZS1521A *系统频率:PLL1 = core_clk = 264MHz,PLL0 = 192MHz * 调试器:Lauterbach Trace32 * 目标:internal_FLASH * 终端:19200-8-无奇偶校验-1停止位-eSCI_A上无流量控制 * 使用微型模块上的 USB 连接器 (J21) * * EVB 连接:ETPUA30(PortP P23-15)--> USER_LED_1(P7-1) * ETPUA31 (端口 P23-14) --> USER_LED_2 (P7-2) * ******************************************************************************** 概述 回复:示例 MPC5777C MCAN-FD simpleTX RX-ISR GHS616 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好PetrS 你能检查一下我关于此代码的问题吗? 当我检查 main.c 时,我认为#define MCAN1_BASE_ADDR 0xFFEE8000 不正确。 据我所知,MCAN1 的基数是 0xFFE3_8000... 你能检查一下吗? 谢谢!
View full article
MPC5644A审查CW210示例 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 警告1:请谨慎使用审查功能,因为不当使用可能导致设备无法使用!使用前请仔细阅读所有说明!   警告 2:CodeWarrior 2.10 中包含的 ICDPPCNEXUS 调试器版本无法在包括 MPC5644A 在内的某些设备上启用调试。解决方法是使用 Codewarrior 10.6 或使用 PKGPPCNEXUS 调试器 - 可以从P&E Microcomputer Systems下载   警告 3:如果使用 TRACE32 调试器(Lauterbach),则需要更新 TRACE32 软件。TRACE32 版本 02/2015 和 09/2016..02/2018 可能无法访问受审查的设备。劳特巴赫开发工具   该示例由两部分组成,文档描述了如何使用 PeMicro 或 Lauterbach 调试器通过 JTAG 访问受审查的设备:   1)MPC5644A-Censor_device-CW210: ******************************************************************************** * 详细说明: * 示例代码重新编程影子闪存的内容以启用审查。 * eSCI_A 终端窗口中的通知确认操作成功 *(19200-8-无奇偶校验-1停止位-无流量控制)。 * 开机重启后,设备将通过私人密码进行审查 * 0xFEED_FACE_CAFE_BEEF。随后可以通过启用 * 审查设备的调试如附件 pdf 文档中所述。暗影闪光 * 重新编程代码必须从内部 RAM 执行。 * ----------------------------------------------------------------------------------------------   2)MPC5644A-Uncensor_设备-CW210: ******************************************************************************** * 详细说明: * 假设设备受到示例 MPC5644A-Censor_device-CW210 的审查 * 首先需要启用被审查设备的调试,如 * 附加 pdf 文档。编程密码为 0xFEED_FACE_CAFE_BEEF。 *MPC5644A_run_from_ram.cmm脚本通过命令执行 * 系统选项键码 0xFEEDFACECAFEBEEF。 * 然后运行此代码以解除对设备的审查。操作成功确认 * eSCI_A 终端窗口中的通知(19200-8-无奇偶校验-1 停止位-无流量 * 控制)。上电复位后,设备不受审查,后续访问 * 将无需密码。必须执行影子闪存重新编程代码 * 来自内部 RAM。 * ---------------------------------------------------------------------------------------------- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 警告1:请谨慎使用审查功能,因为不当使用可能导致设备无法使用!使用前请仔细阅读所有说明!   警告 2:CodeWarrior 2.10 中包含的 ICDPPCNEXUS 调试器版本无法在包括 MPC5644A 在内的某些设备上启用调试。解决方法是使用 Codewarrior 10.6 或使用 PKGPPCNEXUS 调试器 - 可以从P&E Microcomputer Systems下载   警告 3:如果使用 TRACE32 调试器(Lauterbach),则需要更新 TRACE32 软件。TRACE32 版本 02/2015 和 09/2016..02/2018 可能无法访问受审查的设备。劳特巴赫开发工具   该示例由两部分组成,文档描述了如何使用 PeMicro 或 Lauterbach 调试器通过 JTAG 访问受审查的设备:   1)MPC5644A-Censor_device-CW210: ******************************************************************************** * 详细说明: * 示例代码重新编程影子闪存的内容以启用审查。 * eSCI_A 终端窗口中的通知确认操作成功 *(19200-8-无奇偶校验-1停止位-无流量控制)。 * 开机重启后,设备将通过私人密码进行审查 * 0xFEED_FACE_CAFE_BEEF。随后可以通过启用 * 审查设备的调试如附件 pdf 文档中所述。暗影闪光 * 重新编程代码必须从内部 RAM 执行。 * ----------------------------------------------------------------------------------------------   2)MPC5644A-Uncensor_设备-CW210: ******************************************************************************** * 详细说明: * 假设设备受到示例 MPC5644A-Censor_device-CW210 的审查 * 首先需要启用被审查设备的调试,如 * 附加 pdf 文档。编程密码为 0xFEED_FACE_CAFE_BEEF。 *MPC5644A_run_from_ram.cmm脚本通过命令执行 * 系统选项键码 0xFEEDFACECAFEBEEF。 * 然后运行此代码以解除对设备的审查。操作成功确认 * eSCI_A 终端窗口中的通知(19200-8-无奇偶校验-1 停止位-无流量 * 控制)。上电复位后,设备不受审查,后续访问 * 将无需密码。必须执行影子闪存重新编程代码 * 来自内部 RAM。 * ---------------------------------------------------------------------------------------------- 概述
View full article
恢复 PHY3250 引导加载程序 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如果您不小心擦除了Phytec LPC3250 开发板上的Kick Start或S1L引导加载程序,可以按照此步骤恢复它们。请注意,此恢复方法中提供的引导加载程序可能比 Phytec 开发板附带的版本更新。您也可以从 Phytec 网站下载原始版本的引导加载程序。 恢复板上的引导加载程序不需要特殊硬件(即 JTAG),而是使用 LPC32x0 通用驱动程序库中构建或包含的引导加载程序和工具来执行。但是,您需要一台带有串行端口的 PC 来执行更新过程。 恢复 Kick Start 加载程序和 S1L 分为两步。 首先恢复 Kick Start 加载程序,然后 恢复 S1L 。串行加载程序用于传输应用程序和烧录器映像(用于将应用程序烧录到 NAND FLASH 中)。LPC32x0 会在下载映像后自动将其烧录到 NAND FLASH 中,然后提供状态信息。 步骤 1:下载资源页面的预建启动软件和恢复映像。 步骤 2:在 Windows PC 上提取文件 步骤 3:使用串行电缆连接 Phytec 开发板的下部串行连接器和 PC 步骤4:启动串行加载器软件(LPC3250_Loader.exe)包含在预建的启动软件包中。 步骤 5:将串行加载程序中的“主启动(IRAM)”文件设置为 burner_kickstart_nand_small_block_rvw.bin 文件。将串行加载器中的“辅助可执行文件(SDRAM)”文件设置为 kickstart_nand_small_block_rvw.bin 文件。验证 Comport 控制选择是否与连接到 Phytec 板的 PC 上的 COM 部分匹配。 注意:预构建的二进制文件的名称可能与步骤 5 和 7 中列出的名称略有不同,具体取决于构建二进制文件所使用的工具。如果二进制文件是使用 GNU 而不是 Realview 构建的,则每个名称中的“rvw”字段将包含标识的“gnu”。根据需要更改您拥有的二进制文件的文件名。   步骤 6:按下串行加载器上的“加载箱/启动主”按钮并打开电路板电源。刻录机映像和启动加载程序映像应传输到电路板,然后启动加载程序将被编程到 NAND FLASH 块 0 中,以便由刻录机应用程序从引导 ROM 进行引导。文件传输完成后,按“启用终端模式”按钮查看程序状态。在串行加载工具的状态/终端输出窗口中,您应该看到以下输出。   等待 BootID?..þ5 ..找到了!发送‘A’...完成!期望第二个 BootId?.. 5 .. 找到了!发送‘U’、‘3’……完成!期望‘R’..R..找到了!发送起始地址..完成!发送尺寸..完成!发送代码..完成!--- 正在加载辅助可执行文件 --- 等待‘X’..X..找到!-- 发送命令..p..完成! 发送起始地址..完成!发送尺寸..完成!等待主引导的接受..o..OK! 发送代码..完成!期望最终的 't'.. t.. 发现, ---- 辅助可执行文件已加载。--- --- 启用终端模式 --- 格式化块... 格式化完成 将 kickstart 写入闪存... 验证数据......成功 NAND闪存编程成功 步骤 7:将串行加载程序中的“主启动(IRAM)”文件设置为 burner_s1app_nand_small_block_rvw.bin 文件。将串行加载器中的“辅助可执行文件(SDRAM)”文件设置为 s1l_from_kick_full_rvw.bin 文件。验证 Comport 控制选择是否与连接到 Phytec 板的 PC 上的 COM 部分匹配。   步骤 8:按下串行加载器上的“加载箱/启动主”按钮并重置电路板。刻录机图像和S1L图像应传输到电路板,然后S1L将被编程到 NAND FLASH 块 1(及之后)中,以便从 kickstart 加载程序启动。文件传输完成后,按“启用终端模式”按钮查看程序状态。在串行加载工具的状态/终端输出窗口中,您应该看到以下输出。   等待 BootID?.. 5 .. 找到了!发送‘A’...完成!期望第二个 BootId?.. 5 .. 找到了!发送‘U’、‘3’……完成!期望‘R’..R..找到了!发送起始地址..完成!发送尺寸..完成!发送代码..完成!--- 正在加载辅助可执行文件 --- 等待‘X’..X..找到!-- 发送命令..p..完成! 发送起始地址..完成!发送尺寸..完成!等待主引导的接受..o..OK! 发送代码..完成!期望最终的 't'.. t.. 发现, ---- 辅助可执行文件已加载。--- --- 启用终端模式 --- 格式化块... 格式化完成 将 S1 图像写入闪存... NAND闪存编程成功 步骤 8:关闭串行加载程序并打开终端程序,然后重置电路板 关闭串行加载工具并打开终端程序,例如 Teraterm。重置电路板, S1L应该启动。   5 Phytec 3250 主板 构建日期:2010年5月21日 12:43:21 PHY3250>
View full article
DES-N1951 Kinetis MCU安全技术 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 随着联网边缘设备在消费者中越来越受欢迎,过去的安全方法和假设将会失效,并对消费者安全和隐私造成新的威胁和漏洞。此外,手机、平板电脑和个人电脑的安全成本将对乘员传感器和心率监测贴片等应用构成挑战。最后,将产品连接到网络的供应商中还没有互联行业安全专家团队。加入此会议,了解行业如何提供经济高效、高度安全、经过认证的硬件,以加快新兴边缘节点应用的学习周期、提供安全解决方案、降低成本并限制供应商所需的特定专业知识。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 随着联网边缘设备在消费者中越来越受欢迎,过去的安全方法和假设将会失效,并对消费者安全和隐私造成新的威胁和漏洞。此外,手机、平板电脑和个人电脑的安全成本将对乘员传感器和心率监测贴片等应用构成挑战。最后,将产品连接到网络的供应商中还没有互联行业安全专家团队。加入此会议,了解行业如何提供经济高效、高度安全、经过认证的硬件,以加快新兴边缘节点应用的学习周期、提供安全解决方案、降低成本并限制供应商所需的特定专业知识。 设计 | 软件与服务
View full article
使用我们的在线应用程序创建免费的 i.MX6 处理器设计 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您好,i.MX6 用户, 我们创建了一个创新的应用程序,您可以在一分钟内根据您的定制要求创建 i.MX6 双光硬件设计。 创建新设计非常容易,您只需将处理器、外围设备要求和电路板输入电源输入添加到应用程序中即可。 有了这些输入要求,应用程序将 1. 查找外设、电源、时钟、复位和电源排序组件 2. 查找处理器引脚复用选项 3. 优化电源、时钟 4. 生成设计并绘制可在线查看的原理图。 它是一种强大的算法,专门用于 i.mx6 等高端处理器。 您可以使用我们在www.circuit-tree.com上托管的应用程序生成任意数量的设计。我们很快将扩大我们的库并添加更多外形尺寸以支持不同的硬件设计。 如果您有任何问题/疑虑/反馈,请告知我们。 谢谢! 电路树团队 概述
View full article
TFC_2015_FasTech_克拉约瓦大学技术报告.pdf <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 罗马尼亚克拉约瓦大学 FasTech 团队的飞思卡尔杯技术报告 - 2015 年 EMEA 决赛入围者 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 罗马尼亚克拉约瓦大学 FasTech 团队的飞思卡尔杯技术报告 - 2015 年 EMEA 决赛入围者
View full article
Boundary Devices - Android Lollipop NFC デモ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> これは、 Android Lollipop 5.0.0 コード ベースに統合された NFC 機能を示すビデオです。これは、 NXP PN7120開発キット とともに Nitrogen6x プラットフォーム上で動作します。 このビデオは、BoundaryのURLでプログラムされたNFCタグが自動的に読み取られ、それに応じてブラウザを起動することを示しています。 NFCデータからデータを読み書きするために、Android は完全に文書化されたAPIを提供します。 タグを書き込むための既存のアプリケーションを探している場合は、次のオプションがいくつかあります。 NXP TagWriterアプリ StickyNotes のサンプル コード 詳細については、http://boundarydevices.com/ をご覧ください。 全般
View full article
iWave 的 i.MX6 产品组合 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自 i.MX6 应用处理器推出以来,全球领先的 SOM 供应商之一 iWave Systems 已推出了多种 i.MX6 CPU 模块和 SBC 板,可满足工业、汽车和医疗应用的需求。@! i.MX6 Q7 SOM 符合 Qseven R2.0 规范, 尺寸为 70mmx70mm,支持工业级操作。i.MX6 MXM SOM 支持汽车级 i.MX6 CPU 和汽车专用接口,并配备 314 针 MXM2 连接器引脚排列,尺寸为 85mmx85mm。近期推出的 i.MX6 SODIMM SOM 模块支持商用和工业级工作温度,尺寸仅为 67.6mmx37mm,非常紧凑。Pico ITX 尺寸的 i.MX6 SBC 板 尺寸为 100mmx70mm, 支持所有 i.MX6 接口的板载连接器,并可选择通过扩展连接器扩展 IO。 所有这三种不同外形尺寸的 SOM 和 SBC 均支持不同的 i.MX6 CPU 变体,例如 Quad、Dual、Dual Lite 和 Solo。除此之外,i.MX6 Qseven 模块还支持 i.MX6 Quad Plus 和 i.MX6 Dual plus CPU 配置。 除了主要的 i.MX6 CPU 产品组合外,iWave Systems 还推出了 i.MX6UL SOM,其尺寸为 67.6mmx29mm,非常小巧的 SODIMM 外形适用于功率和成本受限的商业和工业应用。I.MX6 和 i.MX6UL SODIMM SOM 均引脚兼容,以便客户可以利用广泛的 i.MX6 产品的可扩展性和软件兼容性。 为了快速构建这些不同外形尺寸的 SOM 原型,iWave Systems 为每种外形尺寸的 SOM 提供独立的开发套件版本,并支持 Linux、Android 和 WEC7* BSP。这些开发套件可帮助客户缩短高达 60% 的新产品开发周期,从而快速将产品推向市场。iWave Systems 还凭借其丰富的 i.MX6 产品开发专业知识,提供定制 SOM 和 SBC 开发以及交钥匙制造服务。请联系iWave Systems了解更多详情。 概述
View full article
DwF Automotive Solutions - Chongqing - 2015-08-19 Automotive and Connected Car
View full article
HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本ドキュメントは Flash 上で動作するプロジェクトにおいて、選択した関数を RAM から実行する方法を説明します。 ルーチンを配置するカスタムリンカーセクションをリンカーファイル(.ld)に作成します。配置場所にこだわらない場合、本手順は省略可能であり既定セクションを利用できます。 MEMORY {       flash_rchw : org = 0x00FA0000,   len = 0x4     cpu0_reset_vec : org = 0x00FA0000+0x10,   len = 0x4     cpu1_reset_vec : org = 0x00FA0000+0x14,   len = 0x4     cpu2_reset_vec : org = 0x00FA0000+0x04,   len = 0x4                  m_my_flash :     org = 0x01000000, len = 4K       // optional - this is dedicated section for the RAM function rom image     m_text :         org = 0x01001000, len = 5628K    // default section for code       m_my_ram :       org = 0x40000000, len = 4K       // optional - specific section where a RAM routine(s) should be copied into     m_data :         org = 0x40001000,  len = 764K    // default section for data/stack/heap }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ルーチンを特定セクションに保持したい場合は上記手順を実施します。 SECTIONS { ... .MyRamCode : {    MY_RAM_START = .;       // this symbol is optional    KEEP (*(.MyRamCode))    // KEEP - avoid dead stripping if an object is not referenced    MY_RAM_END = .;         // this symbol is optional } > m_my_ram AT>m_my_flash // the section above is linked into m_my_ram and Rom image is stored into m_my_flash‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ こだわらない場合は既定のコード/データ領域を使用できます。 SECTIONS { ... .MyRamCode  : {     MY_RAM_START = .;     // this symbol are optional     KEEP (*(.MyRamCode))  // KEEP - avoid dead stripping if an object is not referenced     MY_RAM_END = .;       // this symbol are optional }  > m_data  AT>m_text    // the section is linked into default data memory area and its rom image is placed into the default code memory ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ RAM 関数のプロトタイプに __attribute__ ステートメントを追加します。Flash から呼び出すためには関数属性 longcall が必須です。 __attribute__ ((section(".MyRamCode")))              // place the function below into .MyRamCode section int test_RAM(int arg1) __attribute__ ((longcall));   // declare the function as "far"‍‍‍‍ 既定の S32DS スタートアップは既定データセクションのみを初期化するため、カスタムセクションを使用する場合はセクションコピーを手動で実装する必要があります。コピーは RAM ルーチンが呼び出される前、例として main() の冒頭またはスタートアップルーチンで実行します。 リンカーシンボル(.MyRamCode RAMおよびROMのアドレスとサイズ)を作成し、コピーダウンが実装されているモジュールにインポートすることができます。 __MY_RAM_ADR = ADDR (.MyRamCode); __MY_RAM_SIZE = SIZEOF (.MyRamCode); __MY_RAM_ROM_ADR = LOADADDR (.MyRamCode);‍‍‍‍‍‍ 参考実装例は次のようになります。 #include extern unsigned long __MY_RAM_ADR; extern unsigned long __MY_RAM_ROM_ADR; extern unsigned long __MY_RAM_SIZE; __attribute__ ((section(".MyRamCode")))              // place the function below into .MyRamCode section int test_RAM(int arg1) __attribute__ ((longcall));   // declare the function as "far" ... void main(void) {    int counter = 0;    memcpy(&__MY_RAM_ADR , &__MY_RAM_ROM_ADR, &__MY_RAM_SIZE);  // copy the function from flash to RAM    counter = test_RAM(counter);                                // call the function ... }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ お役に立てれば幸いです! Stan Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Duke すでに存在しています。累積版の最新版は https://community.nxp.com/docs/DOC-341653 からインストールできます。 Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> それは素晴らしいです! この問題の公式パッチをお待ちしております。 Alexander さん、NXP S32DS サポートチームの皆さま、アップデートありがとうございます。 Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> cmpe200gcc‑181 は S32 Design Studio for Power Architecture 2017.R1 – Update 2 に同梱されているコンパイラで修正されています。 Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 親愛なる公爵様!   ありがとうございます。私の MPC5746C ボードでは現在問題なく動作しています。以前、m_text を 0x00FE0400 に移動した際はブートに失敗しました。 Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> フォルケルトと同様に、 ecrti.o だけを修正すれば十分でした(私の場合)。 コードをトレースできれば、どの部分に問題があるのかがわかります。 前述したように、もしそのコードが 4 バイト境界に整列していない場合は―― おそらく、同じ手順でコードを修正できるはずです。 または、逆アセンブルされたコードに問題点を投稿してください。 幸運を祈ります。 Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 親愛なる公爵様! ありがとうございました。これは助けになりそうです!(MPC5745Rを使用して) よろしくお願いします。Folkert Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 同じ問題に遭遇しましたが、解決されましたか。 Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 私の回避策は `ELe200/src_gcc/libgcc/config/rs6000/eabivle-ci.S` を編集し、`__init` 関数に `se_nop` を挿入して VLE では暗黙でない 4 バイト境界を強制する方法でした(BookE では自動で挿入されます)。 /* Head of __init function used for static constructors. */ #ifdef __VLE__ .section ".init","axv" #else .section ".init","ax" #endif .align 2 FUNC_START(__init) #ifdef __VLE__ e_stwu 1,-16(1) se_mflr 0 se_nop e_stw 0,20(1) #else stwu 1,-16(1) mflr 0 stw 0,20(1) #endif この回避策を適用するにはコンパイラを再ビルドする必要があります。 敬具 エルカー Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 皆さん、こんにちは。 この問題を報告していただき、ありがとうございます! 本件は e200 GCC リンカーの不具合(ID: CMPE200GCC‑181)であり、現在コンパイラチームが調査中です。 これは ARM gcc (S32DS for ARM) で正常に動作します。 進捗状況については、随時お知らせいたします。 ありがとうございます! Stan Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 問題は解決されましたか。ご指摘のとおりかもしれません。これを回避するにはどうすればよいでしょうか。 Re: HOWTO: S32 Design Studio で RAM からルーチンを実行する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32 Studio for PowerPC v1.2 でも同じ問題が発生しました。さらに簡単に再現する方法を以下に示します。 - 新しいプロジェクト >> MPC5674F - ライブラリ NewLib Nano を選択 - main.c に RAM 関数を追加しました。 - .ramfuncs を追加- input セクションを .dataセクションにマッピング(初期化時にコピーされます) main.c: #include "derivative.h" /* include peripheral declarations */ extern void xcptn_xmpl(void); int counter = 0; #define RAMFUNC __attribute__ ((longcall, section(".ramfuncs"))) RAMFUNC void ramcall(void) {    counter+=2; } int main(void) {    xcptn_xmpl ();    for(;;) {       counter++;       ramcall();    } } 56xx_flash.ld .... .data : { *(.data) *(.data.*) *(.ramfuncs) } > m_data AT>m_text ... メインエントリポイントで逆アセンブリが生成されました (main >> __eabi >> __init) 00004438 <__init>: 4438: 18 21 06 f0 e_stwu r1,-16(r1) 443c: 00 80 se_mflr r0 443e: 54 01 00 14 e_stw r0,20(r1) 4442: 00 00 se_illegal 4444: 79 ff fc ad e_bl 40f0 4448: 79 ff fd b9 e_bl 4200 <__do_global_ctors_aux> 444c: 50 01 00 14 e_lwz r0,20(r1) 4450: 00 90 se_mtlr r0 4452: 20 f1 se_addi r1,16 4454: 00 04 se_blr 4456: 50 01 18 21 e_lwz r0,0(r1) ロングコールが init トランポリンでアラインメント不良を引き起こすことが確認されています。この問題は Debug/Release(Flash)ターゲットの双方で再現し、Debug_RAM ではコードが既に RAM 上にあるため発生しません。 お役に立てれば幸いです。
View full article
NFC Demos - Information, Source codes, Schematics Near Field Communication (NFC) is already present in more than 1.5 Billion smartphones. Well-known applications like payment and access control are enabled by NFC, but also emerging and innovative use cases which are just appearing on the horizon now. This article gives you more information, background and how-to guides around our NFC demos, first exhibited at embedded world 2018 in Nürnberg - to help you put NFC Everywhere. Accessories and consumables Identifying and authenticating accessories and consumables can add significant value to a product, and for the first time we show live how this works: The demo showcases tool identification via NFC for 3 different kinds of tools: A drill bit, a standard flat-blade screwdriver and a Phillips screwdriver. Each of the tools has an embedded NTAG213 NFC tag, and the electric drill contains an NFC reader (CLRC663 plus). As soon as a tool is inserted, the main unit reads the tool type and usage (wear). Based on this information, it can reject non-genuine or worn-out tools, and adjust internal settings like max/min speed based on the tool type. The demo is based on the brand new NFC Nutshell kit by our partner GMMC, and the demo shows how easily an existing product can be retrofitted with NFC using this kit. Find a detailed description of accessory and consumable identification and authentication here: https://community.nxp.com/docs/DOC-340283 Parameterization, Diagnosis and Firmware update This demo shows how you can use an NFC phone to parameterize/configure a DIN rail module (or any other piece of electronics) with an NFC phone - even if the module is completely unpowered. The smart phone app lets you set the behavior of the lamps and also the language of the display. After the configuration (a simple tap) you switch on the main power, and the device comes up as configured. And NFC also lets you read out diagnostic data - no matter whether the device is powered on or off. So you can even replace your service UART by NFC. Thirdly, the demo shows how easy it is to even flash your firmware via NFC. Again, this works even when the device is switched off. This application is based on the NTAG I²C plus passive connected tag IC.   Find a detailed description and all source codes here: https://community.nxp.com/docs/DOC-333834. Interested how this looks like in a commercial product? Watch this video showing how easily the Schneider Zelio NFC Timer Relay can be configured via NFC. Access Management In the Access Management corner, we demonstrate the ultimate contactless connectivity for residential or hospitality applications through NXP NFC and BLE solutions and a superior contactless experience and security with MIFARE ® DESFire ® credential on cards, mobile devices and wearables. Our demonstrator is based on the PN7462 family, the all-in-one full NFC controller, the QN9021, a low power BLE system-on-chip, and the PCF8883T, capacitive proximity switch with auto-calibration, for very low power consumption. We also show two commercial products by our partners: 1) The Salto XS4 range of smart doorlocks, a simple to use and very efficient access control system. 2) A modular access control solution by Kronegger, using their tiny NFC reader boards. We also reveal a very small footprint complete reader board based on the new BGA package (VFBGA64; 4.5x4.5 mm²) for the PN7462 family complementing the existing HVQFN64 package.   NFC Tandem - The Best Of Two Worlds If you need NFC functionality both in powered and unpowered state, have a look at the NFC Tandem demo: An NFC reader (PN7150) and a passive connected NFC tag (NTAG I²C plus) sharing one antenna. A user can interact with the device when it is powered off (through the NTAG I²C plus); when the device is powered, it can read cards, tags or other connected tags. Find design files, a user manual and further downloads here: https://community.nxp.com/docs/DOC-340244 Single-Chip Integrated Solution: LPC8N04 MCU with passive NFC interface In this demo, we show our latest integrated NFC solution, the LPC8N04, a cost-effective MCU with integrated (passive) NFC connectivity. This MCU offers multiple features, including several power-down modes and a selectable CPU frequency of up to 8 MHz for ultra-low power consumption. The demo showcases its features in a conceptual clock format: - Easily set current time/date of the clock via an NFC phone - Real-time clock with optional alarm, programmed and controlled using an Android app - GPIO controlled bar graph indicating programmable "safe operating range" - I2C controlled OLED user display - Data (temperature) logging, configured using an Android App To learn more about this device, please visit: www.nxp.com/LPC8N04 Single-Chip Integrated Solution: NTAG SmartSensor NTAG SmartSensor allows consumers and brand owners to confirm that temperature sensitive products – like fish, wine or pharmaceuticals – have been properly handled. The NTAG SmartSensor allows for temperature sensing at the item level, so each individual product can be confirmed as safe to use. And a single tap with your NFC smartphone is all that's needed to read out the temperature history of the NTAG SmartSensor. Learn more about NTAG SmartSensor on our webpage or watch the video. If you are looking for a ready-made logger using the NTAG SmartSensor, here is a list of manufacturers offering NTAG SmartSensor based loggers. Electronic Shelf Labels With NFC-enabled Electronic Shelf Labels (ESL), wrong price indication, non-transparent processes, and unsatisfactory customer interactions are a thing of the past. In this demo we show labels from 2 manufacturers, one commercial electronic shelf label from SES Imagotag and one ePaper label from MpicoSys. Find more information in the article by Fabrice Punch, Senior Marketing Manager at NXP. Why NFC on ePaper label? NFC allows for creating a product with no batteries, so no recharging, and labels can be in constant use  No cables and connectors - labels can be fully sealed and made waterproof NFC is a well-proven and widely-supported standard  Allows for easy integration with both PC and smartphones  Applications for PicoLabel - MpicoSys ePaper labels Logistic labels (warehousing, supply chain management)  ID Badges (show image on employee, visitor and conference badges)  Authentication badges (identity, authentication, cryptographic security) Door signage (shared offices, conference centers) Manufacturing (replacing paper labels) NFC Cube The NFC Cube is the universal demo for NFC applications: It shows communication between a device and a card/tag, between a device and a phone, and between two devices. It uses the PN7462AU single-chip NFC controller with integrated Cortex M0 core. The NFC Cube kit is interoperable with our NTAG I 2 C plus Explorer board, which enables you to demonstrate how 2 devices can communicate via NFC. NFC Portfolio and Package Options Find here an overview of the package options of our NFC reader and connected tag ICs. Our Partners In The NFC Everywhere Demonstrator We would like to extend a special thanks to our partners who contributed to this demonstrator: Lab ID: NFC/RFID cards, tickets, labels and inlays Kronegger: Demo on logical access control, NFC reader modules and customized solutions Salto: Smart door lock demo GMMC: NFC Nutshell Kit for easy demonstration, retrofitting and development of small NFC reader solutions SES Imagotag: Commercial electronic shelf label with customer interaction via NFC MpicoSys: Commercial PicoLabel based on ePaper and content update via NFC Find out more Discover NFC Everywhere: https://www.nxp.com/nfc All about MIFARE: https://www.mifare.net Get your technical NFC questions answered: https://community.nxp.com/community/identification-security/nfc List of Approved Engineering Consultants (AEC) for NFC: https://nxp.surl.ms/NFC_AEC NFC Everywhere Brochure: https://www.nxp.com/docs/en/brochure/NFC-EVERYWHERE-BR.pdf  Industrial
View full article
RT600 MCUXpresso JLINK debug QSPI flash RT600 MCUXpresso JLINK debug QSPI flash 1 Introduction     MIMXRT600-EVK is the NXP official board, which onboard flash is the external octal flash, the octal flash is connected to the RT685 flexSPI portB. In practical usage, the customer board may use other flash types, eg QSPI flash, and connect to the FlexSPI A port. Recently, nxp published one RT600 customer flash application note: https://www.nxp.com/docs/en/application-note/AN13386.pdf This document mainly gives the CMSIS DAP related flash algorithm usage, which modifies the option data to generate the new flash algo for the different flash types. Some customer’s own board may use the RT600 QSPI flash+MCUXPresso+JLINK to debug the application code. Recently, one of the customers find on his own customer board, when they use debugger JLINK associated with the MCUXPresso download code to the RT600 QSPI flash, they meet download issues, but when using the CMSIS DAP as a debugger and the related QSPI cfx file, they can download OK. So this document mainly gives the experience of how to use the RT600, MCUXpresso IDE, and JLINK to download and debug the code which is located in the external QSPI flash. 2 JLINK driver prepare and test   MCUXpresso IDE use the JLINK download, it will call the JLINK driver related script and the flash algorithm, but to RT600, the JLINK driver will use the RT600 EVK flexSPI port B octal flash in default, so, if the customer board changes to other flexSPI port and to QSPI flash, they need to provide the related QSPI flash algorithm and script file, otherwise, even they can find the ARM CM33 core, the download will be still failed. If customers want to use the MCUXpresso IDE and the JLINK, they need to make sure the JLINK driver attached tool can do the external flash operation, eg, erase, read, write successfully at first. Now, give the JLINK driver related tool how to add the RT600 QSPI flash driver and script file. 2.1 JLINK driver install   Download the Segger JLINK driver from the following link: https://www.segger.com/downloads/jlink/JLink_Windows_V754b_x86_64.exe This document will use the jlink v7.54b to test, other version is similar. Install the driver, the default driver install path is: C:\Program Files\SEGGER 2.2 Universal flashloader RT-UFL    RT-UFL v1.0 is a universal flashloader, which uses one .FLM file for all i.MXRT chips, and the different external flash, it is mainly used for the Segger JLINK debugger. RT-UFL v1.0 downoad link: https://github.com/JayHeng/RT-UFL/archive/refs/tags/v1.0.zip    Now, to the RT600 QSPI, give the related flash algo file patch.    Copy the following path file: \RT-UFL-1.0\algo\SEGGER\JLink_Vxxx To the JLINK install path: \SEGGER\JLink Then copy the content in file: RT-UFL-master\test\SEGGER\JLink_Vxxx\Devices\NXP\iMXRT6xx\archive2\evkmimxrt685.JLinkScript To replace the content in: C:\Program Files\SEGGER\JLink\Devices\NXP\iMXRT_UFL\iMXRT6xx_CortexM33.JLinkScript Otherwise, the MCUXpresso IDE debug reset button function will not work. So, need to add the JLINKScript code for ResetTarget, which will reset the external flash. pic1 The RT-UFL provide 3 types download flash algo: MIMXRT600_UFL_L0, MIMXRT600_UFL_L1, MIMXRT600_UFL_L2. Pic 2 _L0 used for the QSPI Flash and Octal Flash(page size 256 Bytes, sector size 4KB), _L1/2 used for the hyper flash(Page size 512 Bytes,Sector size 4KB/64KB). The JLINKDevices.xml content also can get the detail information. Different name will call different .FLM, the .FLM is the flash algorithm file, the source code can be found in RT-UFL v1.0, it will use different option0 option1 to configure the different external memory when the memory chip can support SFDP. 2.3 JLINK commander test Please note, the device need to select as MIMXRT600_UFL_L0 when using the QSPI flash. Pic 3                                         pic 4 Pic 5 We can find, the JLINK command can realize the external QSPI flash read, erase function. 2.4 Jflash Test Operation steps: Target->connect->production programming Pic 6 We can find, the Jflash also can realize the RT600 external QSPI flash erase and program. Please note, not all the JLINK can support JFLASH, this document is using Segger JLINK plus. 3 MCUXpresso configuration and test MCUXpresso: v11.4.0 SDK_2_10_0_EVK-MIMXRT685 MCUXPresso IDE import the SDK project, eg. Helloworld or led_output. 3.1 QSPI FCB configuration    FCB is located from the flash offset address 0X08000400, which is used for the FlexSPI Nor boot configuration, the detailed content of the FCB can be found from the RT600 user manual Table 997. FlexSPI flash configuration block. Different external Flash, the configuration is different, if need to use the QSPI flash, the FCB should use the QSPI related configuration and its own LUT table.    Modify SDK project flash_config folder flash_config.c and flash_config.h, LUT contains fast read, status read, write enable, sector erase, block erase, page program, erase the whole chip. If the external QSPI flash command is different, the LUT command should be modified by following the flash datasheet mentioned related command. const flexspi_nor_config_t flexspi_config = { .memConfig = { .tag = FLASH_CONFIG_BLOCK_TAG, .version = FLASH_CONFIG_BLOCK_VERSION, .readSampleClksrc=kFlexSPIReadSampleClk_LoopbackInternally, .csHoldTime = 3, .csSetupTime = 3, .columnAddressWidth = 0, .deviceModeCfgEnable = 0, .deviceModeType = 0, .waitTimeCfgCommands = 0, .deviceModeSeq = {.seqNum = 0, .seqId = 0,}, .deviceModeArg = 0, .configCmdEnable = 0, .configModeType = {0}, .configCmdSeqs = {0}, .configCmdArgs = {0}, .controllerMiscOption = (0), .deviceType = 1, .sflashPadType = kSerialFlash_4Pads, .serialClkFreq = kFlexSpiSerialClk_133MHz, .lutCustomSeqEnable = 0, .sflashA1Size = BOARD_FLASH_SIZE, .sflashA2Size = 0, .sflashB1Size = 0, .sflashB2Size = 0, .csPadSettingOverride = 0, .sclkPadSettingOverride = 0, .dataPadSettingOverride = 0, .dqsPadSettingOverride = 0, .timeoutInMs = 0, .commandInterval = 0, .busyOffset = 0, .busyBitPolarity = 0, .lookupTable = { #if 0 [0] = 0x08180403, [1] = 0x00002404, [4] = 0x24040405, [12] = 0x00000604, [20] = 0x081804D8, [36] = 0x08180402, [37] = 0x00002080, [44] = 0x00000460, #endif // Fast Read [4*0+0] = FLEXSPI_LUT_SEQ(CMD_SDR , FLEXSPI_1PAD, 0xEB, RADDR_SDR, FLEXSPI_4PAD, 0x18), [4*0+1] = FLEXSPI_LUT_SEQ(MODE4_SDR, FLEXSPI_4PAD, 0x00, DUMMY_SDR , FLEXSPI_4PAD, 0x09), [4*0+2] = FLEXSPI_LUT_SEQ(READ_SDR , FLEXSPI_4PAD, 0x04, STOP_EXE , FLEXSPI_1PAD, 0x00), //read status [4*1+0] = FLEXSPI_LUT_SEQ(CMD_SDR , FLEXSPI_1PAD, 0x05, READ_SDR, FLEXSPI_1PAD, 0x04), //write Enable [4*3+0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x06, STOP_EXE, FLEXSPI_1PAD, 0), // Sector Erase byte LUTs [4*5+0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x20, RADDR_SDR, FLEXSPI_1PAD, 0x18), // Block Erase 64Kbyte LUTs [4*8+0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xD8, RADDR_SDR, FLEXSPI_1PAD, 0x18), //Page Program - single mode [4*9+0] = FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x02, RADDR_SDR, FLEXSPI_1PAD, 0x18), [4*9+1] = FLEXSPI_LUT_SEQ(WRITE_SDR, FLEXSPI_1PAD, 0x04, STOP_EXE, FLEXSPI_1PAD, 0x0), //Erase whole chip [4*11+0]= FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x60, STOP_EXE, FLEXSPI_1PAD, 0), }, }, .pageSize = 0x100, .sectorSize = 0x1000, .ipcmdSerialClkFreq = 1, .isUniformBlockSize = 0, .blockSize = 0x10000, }; This code has been tested on the RT685+ QSPI flash MT25QL128ABA1ESE, the code boot is working. 3.2 Debug configuration Configure the JLINK options in the MCUXpresso IDE as the JLINK driver: JLinkGDBServerCL.exe Windows->preferences Pic 7 Press debug, generate .launch file. Pic 8 Run->Debug configurations           Pic 9 Choose the device as MIMXRT600_UFL_L0, if the SWD wire is long and not stable, also can define the speed as the fixed low frequency. 3.3 Download and debug test Before download, need to check the RT685 ISP mode configuration, as this document is using the 4 wire QSPI and connect to the FlexSPI A port, so the ISP boot mode should be FlexSPI boot from Port A: ISP2 PIO1_17 low, ISP1 PIO1_16 high, ISP0 PIO1_15 high Click debug button, we can see the code enter the debug mode, and enter the main function, the code address is located in the flexSPI remap address. Pic 10 Click run, we can find the RT685 pin P0_26 is toggling, and the UART interface also can printf information. The application code is working. 4 External SPI flash operation checking To the customer designed board, normally we will use the JLINK command to check whether it can find the ARM core or not at first, make sure the RT chip can work, then will check the external flash operation or not. 4.1 SDK IAP flash code test We can use the SDK related code to test the external flash operation or not at first, the SDK code path is: SDK_2_10_0_EVK-MIMXRT685\boards\evkmimxrt685\driver_examples\iap\iap_flash Then, check the external flash, and modify the code’s related option0, option1 to match the external flash. About the option 0 and option1 definition, we can find it from the RT600 user manual Table 1004.Option0 definition and Table 1005.Option1 definition Pic 11 Pic 12 To the external QSPI flash which is connected to the FLexSPI portA, we can modify the option to the following code:     option.option0.U = 0xC0000001;//EXAMPLE_NOR_FLASH;     option.option1.U = 0x00000000;//EXAMPLE_NOR_FLASH_OPTION1; Then burn the IAP_flash project to the RT685 internal RAM, debug to run it. Pic 13 We can find, the external QSPI flash initialization, erase, read and write all works, and the memory also can find the correct data. 4.2 MCUBootUtility test   Chip enter the ISP mode, then use the MCUBootUtility tool to connect the RT685 and QSPI flash, to do the application code program and read test. ISP mode:ISP2:high, ISP1: high ISP0 low Configure FlexSPI NOR Device Configuration as QSPI, we can use the template: ISSI_IS25LPxxxA_IS25WPxxxA. Pic 14 Click connect to ROM button, check whether it can recognize the external flash: Pic 15 After connection, we can use the tool attached RT685 image to download: NXP-MCUBootUtility-3.3.1\apps\NXP_MIMXRT685-EVK_Rev.E\led_blinky_0x08001000_fdcb.srec Pic 16 We can find, the connection, erase, program and read are all work, it also indicates the RT685+external QSPI flash is working. Then can go to debug it with IDE and debugger. i.MXRT 600
View full article
MCUXpresso IDE v11.9.1现已推出 我们很高兴地宣布 MCUXpresso IDE v11.9.1(build 2170)现已推出。 本次为基于先前版本 MCUXpresso IDE v11.9.0 的维护版本,建议所有现有用户下载安装此新版本。   安装程序下载 要下载所有平台的安装程序,请登录我们的下载网站: https://www.nxp.com/mcuxpresso/ide/download   文档 更多信息可在更新后的用户指南及其他文档中查阅,这些文档可通过 IDE 的“帮助”菜单访问内置帮助系统,或以 PDF 格式从安装目录中获取。   未来版本的发布通知 如需接收有关未来版本发布的通知,请关注:MCUXpresso IDE - 发布历史   变更摘要 - 版本 11.9.1 - 2024 年 4 月 升级:更新的 LinkServer 软件 (v1.5.30) 升级:更新的 SEGGER J-Link 软件 (v7.96c)。 已升级:更新的 PEmicro 插件(v5.7.8)。 更新:MCUXpresso 配置工具升级至 v15.1 版本。 改进:[IDE] 更新了关于窗口的许可文本。 改进:[IDE] 启动配置中支持对 J-Link 脚本文件使用 Eclipse 变量。 已修复:[IDE][SDK 处理] 如果 IDE 未安装在默认位置,自动导入插件 SDK 会返回错误。 已修复:[IDE][SDK 处理] 自动导入插件 SDK 时未能导入某些 SDK。 修复:[IDE][配置工具集成] 解决部分性能问题。 修复:[IDE][欢迎页面] 新增功能章节的版本说明文本可能显示异常的问题。 修复:[KW45/K32W1][J-Link] 闪存擦除后调试功能失效的问题。   已知问题 请参阅安装布局中的 KnownIssues.txt 文件以获取详细列表。
View full article
Bring up the LS1046A How to bring up a card when the flash is blank, or the image is corrupted. How to boot cards from various boot mode when changed the RCW as requirements. This documentation will use LS1046ARDB as new board to realize the functions (all target board in the document is LS1046ARDB). Content Bring up LS1046A with CodeWarrior TAP Boot up from the SD card Compile PBL binary from RCW source file Compile the PBL binary into firmware Program the firmware into the target board (LS1046ARDB) Boot up from the QSPI Compile firmware from RCW source file Program the firmware into the target board (LS1046ARDB) Boot up from the eMMC Enable the on board eMMC Compile firmware from RCW source file Program the firmware into the target board (LS1046ARDB) QorIQ LS1 Devices
View full article
Example S32K312 Switch Debouncing DS3.5 RTD300 *******************************************************************************  The purpose of this demo application is to present a usage of the PORT & SIUL IP Driver for the S32K3xx MCU.  The example uses SW5 for switch debouncing.  ------------------------------------------------------------------------------ * Test HW: S32K3X2EVB-Q172 * MCU: S32K312 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE micro * Target: internal_FLASH ********************************************************************************
View full article
i.MX 8/8X/8XLite - LPDDR4 and DDR3L memory compatibility guide The purpose of this document is to provide supportive information for selection of suitable LPDDR4 and DDR3L devices that are supported by i.MX 8/8X/8XLite family of processors to aid project feasibility assessment capabilities of customers that are evaluating the SoCs for usage in their products.  It is strongly recommended to consult with NXP and the respective memory vendor, the final choice of the memory part number to ensure that the device meets all the compatibility, availability, longevity and pricing requirements. Please note that some of the LPDDR4 devices may not support operation at low speeds and in addition, DQ ODT may not be active, which can impact signal integrity at these speeds. If low speed operation is planned in the use case, please consult with the memory vendor the configuration aspects and possible customization of the memory device so correct functionality is ensured. In all cases, it is strongly recommended to follow the DRAM layout guidelines outlined in the respective NXP i.MX 8 Hardware Developer's Guide available on NXP.com The i.MX8/8X/8XL Reference manuals declare that there are 16GB allocated for the DDR. Please note that this is only the address space, which is reserved for the DDR memory in the memory map. This specification does not guarantee that the entire region can be utilized as the maximum achievable densities listed below in the tables are restricted mainly by the addressing capabilities of the DDR controller, width of the data bus and other implementation-specific parameters as well as availability of supported devices on the market. Memory devices with binary densities (e.g., 1 GB, 2 GB, 4 GB) are preferred because they simplify memory management by aligning with system addressing schemes and reducing software complexity. For any questions related to specific DRAM part numbers please contact the respective DRAM vendor. For any questions regarding the i.MX SoC please contact your support representative or enter a support ticket.  LPDDR4 - maximum supported densities Please note that the SoCs only support memory devices that support either the LPDDR4 mode or support both LPDDR4 and LPDDR4X modes. Memory devices that support only the LPDDR4X mode are not supported. SoC Package Max data bus width Maximum density Assumed memory organization Notes i.MX 8QM/8QP 29x29 mm 32-bit (per controller) 32Gb/4GB (per controller) dual rank, dual-channel  device with 16-row addresses (R0-R15) 1, 2, 4 i.MX 8QXP/8DXP 21x21 mm 32-bit 32Gb/4GB dual rank, dual-channel  device with 16-row addresses (R0-R15) 1, 2, 4 i.MX 8QXP/8DXP 17x17 mm 16-bit 16Gb/2GB dual rank, single-channel  device with 16-row addresses (R0-R15) 1, 2, 3, 4, 9 i.MX 8XLite 15x15 mm 16-bit 32Gb/4GB dual rank, single channel  device with 17-row addresses (R0-R16) 1, 2, 3, 9 LPDDR4 - list of validated memories The validation process is an ongoing effort - updates of the table are expected. SoC Density Memory Vendor Validated Memory Part# Notes i.MX 8QM/8QP 24Gb/3GB (per controller) Micron MT53B768M32D4NQ-062 AIT:B   12, 13 32Gb/4GB (per controller)  Samsung K4FBE3D4HB-KHCL  10, 11 32Gb/4GB (per controller) Micron MT53E1G32D2FW-046 AUT:B (Z42M) 10, 11 32Gb/4GB (per controller) Micron MT53D1024M32D4DT-046 AAT:D   12 16Gb/2GB (per controller) Micron MT53D512M32D2DS-046 WT:D  10, 12 16Gb/2GB (per controller) Nanya NT6AN512T32AC-J1J  10, 11 16Gb/2GB (per controller) Nanya NT6AN512T32AC-J1H  10, 11 32Gb/4GB (per controller) Nanya NT6AN1024F32AC-J2J  10, 11 32Gb/4GB (per controller) Nanya NT6AN1024F32AC-J2H  10, 11 i.MX 8QXP/8DXP 24Gb/3GB Micron MT53B768M32D4NQ-062 AIT:B   12, 13 32Gb/4GB Nanya NT6AN1024F32AC-J2J  10, 11 32Gb/4GB Nanya NT6AN1024F32AC-J2H  10, 11 16Gb/2GB Nanya NT6AN512T32AC-J2J  10, 11 16Gb/2GB Nanya NT6AN512T32AC-J2H  10, 11 32Gb/4GB Micron MT53D1024M32D4DT-046 AAT:D   11 i.MX 8XLite 8Gb/1GB Micron MT53D512M16D1DS 046 AAT ES:D & Z9XGG   12 12Gb/1.5GB Micron MT53E768M16D1ZW-046 AAT:C 10, 11, 13 4Gb/0.5GB Samsung K4F4E164HD-THCL  10, 11 8Gb/1GB ISSI IS43LQ16512A-053BLI 10, 11 8Gb/1GB Nanya NT6AN512M16AV-J1I  10, 11 LPDDR4 - list of incompatible devices Given the limitations mentioned in this document, the following memory devices were identified as incompatible with the particular SoCs as detailed in the following table:   Memory vendor Part Number Density Incompatible SoCs Incompatibility reason Samsung K4FHE3S4HA-KU(H/F)CL 24Gb/3Gb i.MX8QM/8QP, i.MX8QXP/8DXP The memory device requires 17th row address bit to function. Samsung K4UHE3S4AA-KU(H/F)CL 24Gb/3Gb i.MX8QM/QP, i.MX8QXP/8DXP, i.MX8DXL, i.MX8SXL The memory device only supports the LPDDR4X mode. Samsung K4UJE3D4AA-KU(H/F)CL 48Gb/6GB i.MX8QM/QP, i.MX8QXP/8DXP, i.MX8DXL, i.MX8SXL The memory device only supports the LPDDR4X mode. Samsung K4FCE3Q4HB-KU(H/F)CL 64Gb/8GB i.MX8QM/QP, i.MX8QXP/8DXP, i.MX8DXL, i.MX8SXL A byte mode memory device. Samsung K4UCE3Q4AB-KU(H/F)CL 64Gb/8GB i.MX8QM/QP, i.MX8QXP/8DXP, i.MX8DXL, i.MX8SXL A byte mode memory device. The device only supports the LPDDR4X mode.    DDR3L - maximum supported densities SoC Package Max data bus width Maximum density Assumed memory organization Notes i.MX 8QXP/8DXP 21x21 mm 32-bit 64Gb/8GB x8, 8Gb device with 16-row addresses and 11 column addresses 5, 6 i.MX 8QXP/8DXP 17x17 mm 16-bit 32Gb/4GB x8, 8Gb device with 16-row addresses and 11 column addresses 5, 7 i.MX 8XLite 15x15 mm 16-bit 16Gb/2GB x8, 8Gb device with 16-row addresses and 11 column addresses 5, 8 DDR3L - list of validated memories The validation process is an ongoing effort -  updates of the table are expected. SoC Density Memory Vendor Validated Mamory Part#  Notes i.MX 8QXP/8DXP 8Gb/1GB Micron 2x MT41K256M16TW-093 IT:P 12 i.MX 8XLite 4Gb/512MB Micron MT41K256M16TW-093 IT:P 12 Note 1: The numbers are based purely on the IP vendor documentation for the DDR Controller and the DDR PHY, on the settings of the implementation parameters chosen for their integration into the SoC, and on the JEDEC standard JESD209-4A. Therefore, they are not backed by validation, unless said otherwise and there is no guarantee that a DRAM with the specific density and/or desired internal organization is offered by the memory vendors. Should the customers choose to use the maximum density and assume it in the intended use case, they do it at their own risk. Note 2: Byte-mode LPDDR4 devices (x16 channel internally split between two dies, x8 each) of any density are not supported therefore, the numbers are applicable only to devices with x16 internal organization (referred to as "standard" in the JEDEC specification). Note 3: The memory vendors often do not offer so many variants of single-channel memory devices. As an alternative, a dual-channel device with only one channel connected may be used. For example: A dual-rank, single-channel device with 16-row address bits has a density of 16Gb. If such a device is not available at the chosen supplier, a dual-rank, dual-channel device with 16-row address bits can be used instead. This device has a density of 32 Gb however since only one channel can be connected to the SoC, only half of the density is available (16 Gb). Usage of more than one discrete memory chip to overcome market constraints is not supported since only point-to-point connections are assumed for LPDDR4. Note 4: Devices with 17-row addresses (R0-R16) are not supported by the SoCs.  Note 5: The numbers are based purely on the DDR Controller and the DDR PHY, on the settings of the implementation parameters chosen for their integration into the SoC, and on the JEDEC standard JESD79-3E/JESD79-3F. Therefore, they are not backed by validation, unless said otherwise and there is no guarantee that a DRAM with the specific density and/or desired internal organization is offered by the memory vendors. Should the customers choose to use the maximum density and assume it in the intended use case, they do it at their own risk. Note 6: The density can be achieved by connecting 8 single rank discrete devices with one 8Gb die each, 4 devices connected to each chip select, or by connecting 4 dual rank discrete devices with two 8Gb dies each. Note that this number of discrete devices significantly exceeds the number of devices used on the validation board (2 discrete devices, not taking into account the device used for ECC) therefore, it is not guaranteed that the i.MX would be able to drive the signals with margin to the required voltage levels due to increased loading on the traces. A significant effort would be required in terms of PCB layout and signal integrity analysis hence practically, it is not recommended to use more than 2 discrete DDR3L devices. This corresponds to the maximum density of 16Gb/2GB in the case of the single rank devices containing one 8Gb die or 32Gb/4GB in the case of the dual-rank devices containing two 8Gb dies (x16 8Gb devices with 16-row addresses and 10 column addresses assumed instead of x8 devices in such case). Note 7: The density can be achieved by connecting 4 single rank discrete devices with one 8Gb die each, 2 devices connected to each chip select, or by connecting 2 dual rank discrete devices with two 8Gb dies each. Note that the first option exceeds the number of devices used on the validation board (2 discrete devices) therefore, it is not guaranteed that the i.MX would be able to drive the signals with margin to the required voltage levels due to increased loading on the traces. A significant effort would be required in terms of PCB layout and signal integrity analysis, hence practically, it is not recommended to use more than 2 discrete DDR3L devices. This corresponds to the maximum density of 16Gb/2GB in the case of the single rank devices containing one 8Gb die or 32Gb/4GB in the case of the dual-rank devices containing two 8Gb dies. Note 8: The density can be achieved by connecting 2 single rank discrete devices with one 8Gb die each to the i.MX. 8XLite supports only one chip select for DDR3L therefore, dual-rank systems are not supported. Note 9: For single-channel (x16) memory devices, the current maximum available density in the market is 16Gb/2GB (2025). Note 10: The memory part number did not undergo full JEDEC verification however, it passed all functional testing items. Note 11: Part is active. Reviewed Aug 2025 Note 12: Part is being End Of Life'd (EoL) by Vendor or obsolete. Note 13: Memory devices with binary densities (e.g., 1 GB, 2 GB, 4 GB) are preferred because they simplify memory management by aligning with system addressing schemes and reducing software complexity. Additional Links i.MX 8M Quad/8M Mini/8M Nano/8M Plus - LPDDR4, DDR4 and DDR3L memory compatibility guide 
View full article