Multi Source Translation Content

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Multi Source Translation Content

ディスカッション

ソート順:
澳洲大学挂科怎么办 澳洲大学挂科怎么办联系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
記事全体を表示
KL25Z和传感器融合 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 全部, 附件是根据 Andrew Hartnett 的帖子而编写的。它包含用于 KL25Z 上的 9 轴传感器融合 V7.00 的裸机 IAR 项目。您需要为 KL25Z 构建 KSDK 以包含 ISSDK 选项。然后将此文件解压缩到您的 SDK_2.0_FRDM-KL25Z/boards 中目录。示例项目位于 SDK_2.0_FRDM-KL25Z/boards/frdmkl25z_virtual_shield/issdk_examples/algorithms/sensorfusion/baremetal_sensor_fusion/iar。 其中还包含一个 freertos_sensor_fusion 项目。暂时忽略这一点。它可以编译和链接,但需要比 KL25Z 提供的更多的 RAM。我正在寻找降低 RAM 要求的方法。 此致, Mike <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 全部, 附件是根据 Andrew Hartnett 的帖子而编写的。它包含用于 KL25Z 上的 9 轴传感器融合 V7.00 的裸机 IAR 项目。您需要为 KL25Z 构建 KSDK 以包含 ISSDK 选项。然后将此文件解压缩到您的 SDK_2.0_FRDM-KL25Z/boards 中目录。示例项目位于 SDK_2.0_FRDM-KL25Z/boards/frdmkl25z_virtual_shield/issdk_examples/algorithms/sensorfusion/baremetal_sensor_fusion/iar。 其中还包含一个 freertos_sensor_fusion 项目。暂时忽略这一点。它可以编译和链接,但需要比 KL25Z 提供的更多的 RAM。我正在寻找降低 RAM 要求的方法。 此致, Mike 传感器融合 回复:KL25Z和传感器融合 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 全部, 我能够启动并运行 FreeRTOS 版本。以下是您需要了解的内容: 根据裸机说明仅针对 1 种算法进行编译 FreeRTOSConfig.h 中的“#define configMINIMAL_STACK_SIZE ((unsigned short)256)” 替换 FreeRTOS heap_4.c使用 heap_3.c(FreeRTOS 有几种内存分配选项) 将 MKL25Z128xxx4_flash.lcf 中的 __size_heap__ 的值从 0x400 更改为 0x1000。 尽情享受! Mike
記事全体を表示
HMB-N2042 Thread 让互联家居成为现实 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 要在家庭中实现物联网(IoT),企业需要采用开放式生态合作体系,满足从基于IPv6的网状网络协议到最终用户体验等各个方面的要求。 本课程将介绍如何将线程融入智能家居,线程的主要优势以及如何使用恩智浦和线程生态合作体系其它资源提供的模块,将线程产品概念从理念变为成品。 观看视频演示 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 要在家庭中实现物联网(IoT),企业需要采用开放式生态合作体系,满足从基于IPv6的网状网络协议到最终用户体验等各个方面的要求。 本课程将介绍如何将线程融入智能家居,线程的主要优势以及如何使用恩智浦和线程生态合作体系其它资源提供的模块,将线程产品概念从理念变为成品。 观看视频演示 智能家居和智能建筑
記事全体を表示
INS-N2025品質 - 製品選択プロセスにおけるますます関連性のある決定基準 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 明日のインターネットは、クラウドに接続された電子ソリューションで私たちを取り囲んでいます。私たちは、彼らが安全、確実、そして最高の品質と信頼性で運営されていることを確信しなければなりません。自動運転車は、究極のコネクテッドデバイスです。このセッションでは、業界の専門家ワークグループによって特定された、自動車と消費者向け部品の間に存在する可能性のある66の重要な違いに焦点を当て、信頼性、品質、および車両の寿命に影響を与えます。市場間の潜在的な違いに関するこの概要は、顧客がコンポーネントを選択する際のガイドとして理想的なツールになる可能性があります。NXPは、自動車、セキュリティ、コネクティビティ、およびハイエンドのコンピュータネットワーキングのリーダーです。製品セグメントとパフォーマンス範囲全体にわたるNXPの機能が、お客様の隠れたリスクの多くにどのように対処し、コネクテッドソリューションへの優れた出発点を提供するかを示します。 ビデオプレゼンテーションを見る <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 明日のインターネットは、クラウドに接続された電子ソリューションで私たちを取り囲んでいます。私たちは、彼らが安全、確実、そして最高の品質と信頼性で運営されていることを確信しなければなりません。自動運転車は、究極のコネクテッドデバイスです。このセッションでは、業界の専門家ワークグループによって特定された、自動車と消費者向け部品の間に存在する可能性のある66の重要な違いに焦点を当て、信頼性、品質、および車両の寿命に影響を与えます。市場間の潜在的な違いに関するこの概要は、顧客がコンポーネントを選択する際のガイドとして理想的なツールになる可能性があります。NXPは、自動車、セキュリティ、コネクティビティ、およびハイエンドのコンピュータネットワーキングのリーダーです。製品セグメントとパフォーマンス範囲全体にわたるNXPの機能が、お客様の隠れたリスクの多くにどのように対処し、コネクテッドソリューションへの優れた出発点を提供するかを示します。 ビデオプレゼンテーションを見る インサイト&イノベーション
記事全体を表示
示例 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... 你能检查一下吗? 谢谢!
記事全体を表示
LAT-HMB-T2459 - 未来电子:设计时考虑安全性 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 当今的设计师面临着越来越大的挑战,需要保护他们的知识产权和产品免遭假冒或未经授权的访问。为了帮助理解 NXP 提供的安全解决方案,未来的系统设计中心设计了一个安全访问演示板,以展示集成安全性的微控制器 LPC43S57 和 A700X 防篡改安全 MCU 解决方案的功能。本课程将概述安全系统的架构并介绍 NXP 的安全元素。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 当今的设计师面临着越来越大的挑战,需要保护他们的知识产权和产品免遭假冒或未经授权的访问。为了帮助理解 NXP 提供的安全解决方案,未来的系统设计中心设计了一个安全访问演示板,以展示集成安全性的微控制器 LPC43S57 和 A700X 防篡改安全 MCU 解决方案的功能。本课程将概述安全系统的架构并介绍 NXP 的安全元素。
記事全体を表示
恢复 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>
記事全体を表示
TQ-Systems: モジュラー・アプローチで設計を高速化および最適化する方法 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> プロセッサを統合設計で使用するのも一つの方法です。組み込みモジュールを使用することも方法であり、設計を高速化し、設計リスクを軽減し、設計コストを削減します。組み込みモジュールを使用する場合、どのような制限や制約がありますか?組み込みモジュールを選択するための市場概要とガイドライン。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> プロセッサを統合設計で使用するのも一つの方法です。組み込みモジュールを使用することも方法であり、設計を高速化し、設計リスクを軽減し、設計コストを削減します。組み込みモジュールを使用する場合、どのような制限や制約がありますか?組み込みモジュールを選択するための市場概要とガイドライン。
記事全体を表示
FRDM-KW40Z Bluetooth LE Controller Usage with the Linux hcitool Bluetooth Low Energy is a standard for Low Power Wireless Networks introduced in the Bluetooth specification 4.0. Its target application domains include medical, sports & fitness, home automation and others. The adoption and development rates of this technology are growing fast helped by the wide availability of hardware support in most modern mobile phones and mobile operating systems. The purpose of this application note is to show how the Freescale FRDM-KW40Z can board with BLE Controller software can be used with the hcitool from the Linux Bluetooth stack over the HCI interface. 1. Introduction The Bluetooth specification has a very well defined interface between the Controller and the Host called the HCI (Host Controller Interface). This interface is defined for and can be used with various transport layers including an asynchronous serial transport layer. A typical scenario of Bluetooth Low Energy hardware use is a development board which has a BLE Controller accessible via serial transport HCI connected to a device on which the BLE Host runs. The device which runs the BLE Host can be any type of embedded device or a PC. PCs running a Linux type OS can use the hcitool from the Linux Bluetooth Stack to interact with a BLE Controller via the HCI interface. The particular use case of  FRDM-KW40Z board with a serial transport HCI interface running over USB CDC and connected to a PC running the Linux Bluetooth stack is shown in the diagram below and will be detailed din the following sections. Figure 1FRDM-KW40Z (BLE Controller) connected to Linux PC (Bluetooth Host Stack) via HCI Serial Transport 2. Loading the HCI Application onto the FRDM-KW40Z First load the hci_app on the FRDM-KW40Z board. The hci_app aplication can be found in the \ConnSw\examples\bluetooth\hci_app folder. 3. Connecting the FRDM-KW40Z to the Computer via a Serial Port After the app is downloaded to the board plug the board into a free USB port of your Linux computer. The following instructions, commands and their output is typical to a Debian based Linux OS. After the board is plugged in run the following command to list the serial ports available. >> dmesg | grep tty [ 0.000000] console [tty0] enabled [ 2374.118201] cdc_acm 1-2:1.1: ttyACM0: USB ACM device In our example the FRDM-KW40Z board serial port is ttyACM0. To test the connection some HCI commands can be sent in hex format from any terminal application to the serial HCI on the FRDM-KW40Z board. In the figure below an HCI_Read_BD_ADDR command and its corresponding Command Complete Event are shown as they were sent and received in hexadecimal format from the moserial serial terminal GUI application. Figure 2: HCI command and response event in hexadecimal format (HCI UART Transport) 4. Connecting the HCI Serial Interface to the Bluetooth Stack To connect the Linux Bluetooth stack to a serial HCI interface the hciattach command must be run as shown below. >> hciattach /dev/ttyACM0 any 115200 noflow nosleep Device setup complete If the the HCI serial interface is successfully attached to the Bluetooth stack then the "Device setup complete" message is shown. The any parameter specifies a generic Bluetooth device. The 115200 parameter is the UART baudrate. The noflow parameter diasables serial flow control. The nosleep parameter disables hardware specific power managment. Run the hciconfig command with no parameters to check the HCI interface id of the newly attached HCI serial device. >> hciconfig hci1:    Type: BR/EDR  Bus: UART     BD Address: 00:04:9F:00:00:15  ACL MTU: 27:4 SCO MTU: 0:0     UP RUNNING     RX bytes:205 acl:0 sco:0 events:14 errors:0     TX bytes:112 acl:0 sco:0 commands:14 errors:0 hci0:    Type: BR/EDR  Bus: USB     BD Address: 90:00:4E:A4:70:97  ACL MTU: 310:10  SCO MTU: 64:8     UP RUNNING     RX bytes:595 acl:0 sco:0 events:37 errors:0     TX bytes:2564 acl:0 sco:0 commands:36 errors:0 In this example the FRDM-KW40Z is assigned the hci1 interface as can be seen from the bus type (Type: BR/EDR  Bus: UART). The hci0 interface is the example shown corresponds to the on-board Bluetooth module from the machine. On some systems the interface might need to be manually started by using the hciconfig interfaceId up command. hciconfig hci1 up 5. Configuring the Bluetooth Device and Listing its Capabilities The hciconfig command offers the possibility of configuring the device and listing the device capabilities. To find all commands supported by the hciconfig tool type the following command. >> hciconfig –h ...display supported commands... Each individual hciconfig command must be addressed to the correct HCI interface as reported above. In our example we use the hci1 interface. Some hciconfig commands require root privileges and must be run with sudo (the "Operation not permitted(1)" error will be returned if a command needs to be run with root privileges). Some useful hci config commands: >> hciconfig hci1 version    -> lists hci device verison information >> hciconfig hci1 revision    -> lists hci device revision information >> hciconfig hci1 features    -> lists the features supported by the device >> hciconfig hci1 commands    -> lists the hci commands supported by the device >> sudo hciconfig hci1 lestates    -> lists the BLE states supported by the device >> sudo hciconfig hci1 lerandaddr 11:22:33:44:55:66    -> set a random address on the device >> sudo hciconfig hci1 leadv 3    -> enable LE advertising of the specified type >> sudo hciconfig hci1 noleadv    -> disable LE advertising Now the newly connected board with a serial HCI is attached to a HCI interface of the Bluetooth stack and is ready to use. 6.    Controlling the Bluetooth Device using the hcitool The hcitool can be used to send HCI commands to the Bluetooth device. A command is available which lists all available hcitool actions. >> hcitool -h ...display supported commands... To target a specific HCI interface use the -i hciX option for an hcitool command. We will use -i hci1 in our examples. The hcitool supports commands for common BLE HCI operations some of which are shown below and also supports sending generic HCI commands using a dedicated option which uses hexadecimal numbers for the OGF (Command Group), OCF (Command Code) and the parameters. The 6 bit OGF and the 10 bit OCF compose the 16 bit HCI Command Opcode. The command parameters are specific to each command. 6.1.  Listing Devices Available to the hcitool An hcitool command can list all available device interfaces. >> hcitool dev Devices: hci1    00:04:9F:00:00:15 hci0    90:00:4E:A4:70:97 The device we are working with is connected to the hci1 interface as seen from the output of the hciconfig command used above. 6.2.  Scanning for Advertising LE Devices The hcitool can be used to perform a LE Device scan. This command requires root privileges. Press Ctrl+C to stop the scan at any time. >> sudo hcitool -i hci1 lescan LE Scan ... 00:04:9F:00:00:13 (FSL_OTAC) ^C A list of addresses and device names will be shown if advertised (< > or < > as define din the specification). 6.3.  Obtaining Remote LE Device Information Using the hcitool To obtain information about a remote LE device a special hcitool command can be used. The hcitool leinfo command creates a connection, extracts information from the remote device and then disconnects. The remote device information is shown at the command prompt. >> sudo hcitool -i hci1 leinfo 00:04:9F:00:00:13 Requesting information ...        Handle: 32 (0x0020)        LMP Version: 4.1 (0x7) LMP Subversion: 0x113        Manufacturer: Freescale Semiconductor, Inc. (511)        Features: 0x1f 0x00 0x00 0x00 0x00 0x00 0x00 0x00 In this example information about a device previously discovered using the hcitool lescan command is shown. 6.4.  Connecting and Disconnecting from a Remote LE Device Connecting to a remote LE device is done using the hcitool lecc command. >> sudo hcitool -i hci1 lecc 00:04:9F:00:00:13 Connection handle 32 As before a previously discovered device address is used. If the connection is successful then the Connection Handle is returned and in our case the Connection Handle is 32. The hcitool con command shows active connections information: address, connection handle, role, etc. >> hcitool con Connections: < LE 00:04:9F:00:00:13 handle 32 state 1 lm MASTER To end a LE connection the hcitool ledc command can be used. It must be provided with the Connection Handle to be terminated, and optionally the reason. The device handle obtained after the connection and shown in the connected devices list is used. >> hcitool –I hci1 ledc 32 >> Listing the connections after all connections are terminated will show an empty connection list. >> hcitool con Connections: >> 6.5.  Sending Arbitrary HCI Commands To send arbitrary HCI commands to a device using the Command CopCode (OGF and OCF) the hcitool cmd command can be used. As an example the HCI_Read_BD_ADDR command is used which has the 0x1009 OpCode (OGF=0x04, OCF=0x009) and no parameters. It is the same command shown in the direct serial port to HCI communication example above. hcitool -i hci0 cmd 0x04 0x0009 < HCI Command: ogf 0x04, ocf 0x0009, plen 0 > HCI Event: 0x0e plen 10   01 09 10 00 15 00 00 9F 04 00 The OpCode OGF (0x04) and OCF (0x009) and no parameters are passed to the hcitool cmd command all in hexadecimal format. The parameters length (plen) is 0 for the command. The response is a Command Complete event (0x03) with the parameters length (plen) 10. The parameters are 01 09 10 00 15 00 00 9F 04 00: 01 is the Num_HCI_Command_Packets parameter 09 10 is the Command OpCode for which this Command Complete Event is returned (in little endian format) 00 is the status – Success in this case 15 00 00 9F 04 00 is the BD_ADDR of the device as listed by the hcitool dev command KW41Z31Z21Z
記事全体を表示
使用我们的在线应用程序创建免费的 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上托管的应用程序生成任意数量的设计。我们很快将扩大我们的库并添加更多外形尺寸以支持不同的硬件设计。 如果您有任何问题/疑虑/反馈,请告知我们。 谢谢! 电路树团队 概述
記事全体を表示
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了解更多详情。 概述
記事全体を表示
AMF-ACC-T1213 - DwF 底特律 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
記事全体を表示
How To: Get started with IPv6 for MQX RTOS TCP/IP Stack Are you ready for IPv6? The worldwide transition to IPv6 networking is in progress.  Many governments and organizations have already mandated IPv6.  Are your connected products going to be ready? If you need a full-featured traditional host stack with Ipv6 support, Freescale MQX software has a solution for you.  You can even run Ipv4 and Ipv6 at the same time to ease the transition. Check out www.freescale.com/mqx/ipv6 for details and documentation. How to get IPv6? Purchase the add-on at the link above (evaluation available – see below).  The MQX TCP/IP stack (RTCS) supports IPv6 with this optional add-on patch.  Purchasing the add-on gets you all the source code and a year of basic support. How to Evaluate MQX IPv6? Freescale offers a 90-day evaluation of a pre-compiled library for a single low-cost Freescale development platform and toolchain.  In the future, evaluation versions are planned for a broader list of development platforms and toolchains. To evaluate MQX IPv6 today, you will need: MQX RTOS v4.1.1 FRDM-K64F, Freescale Freedom Development Platform for Kinetis K64 IAR Embedded Workbench® for ARM® v7.10.3 Note: Although the evaluation only covers a single board and toolchain, MQX RTCS with IPv6 source code can be purchased for ALL Freescale MCUs and tool-chains supported by MQX RTCS. If you need an evaluation library to support a different board or tool-chain, let me know! Step-By-Step Instructions 1. Obtain a FRDM-K64F Freedom development module from Freescale or a Freescale-authorized distributor (Details at www.freescale.com/frdm-k64f). 2. Plug in the USB cable for the debug connection and the Ethernet cable for the network connection between the board and your computer. 3. Download IAR for ARM® v7.10.3 or later (30-day evaluation available at www.iar.com). 4. Install MQX RTOS 4.1.1 (Available at www.freescale.com/mqxrtos). 5. Now get the evaluation package.  Go to www.freescale.com/mqx/ipv6. 6. Click the Download button, or download tab 7. Click IPv6 for MQX RTOS TCP/IP Stack (90-Day Binary Evaluation) 8. Read the software license agreement.  If it works for you, click I Accept. 9. After you accept, the zip file (e.g. Freescale_MQX_4_1_1_IP6_EVAL.zip) will download. After it downloads, extract the files to the root directory of the MQX 4.1.1 installation (a.k.a. directory).  The default for Windows is C:\Freescale\Freescale_MQX_4_1\. Note: The package does not overwrite or corrupt any MQX files.  It just adds new ones. 10. Open the readme file readme_ip6_eval.txt. The steps in this guide are listed there also. 11. Build the BSP, PSP, RTCS, MFS, and SHELL libraries for FRDM-K64F   a. Open IAR Embedded Workbench   b. Go to File…Open…Workspace.  Browse to \build\frdmk64f\iar   c. Open build_libs.eww 12. Got to Project…Batch Build…  (or press F8) Choose Debug Note, if you are trying to achieve the smallest code size, choose Release instead. Click Make Note: Even though this evaluation provides separate pre-compiled RTCS and SHELL libraries enabled with IPv6. Building RTCS and SHELL is needed to copy over RTCS header files into the appropriate \lib\ folder, which is referenced by application projects.     Wait for the libraries to finish building. 13.  Now, open an example project that has already been configured to use the special Ipv6-enabled rtcs and shell libraries that come with the evaluation.            Available example projects: HTTP Server example RTCS Shell example For this tutorial, I will show the HTTP Server example.      Select Project...Add Existing Project... and browse to \rtcs\examples\httpsrv\build\iar\httpsrv_ip6_frdmk64f 14. Double click on the project name httpsrv_frdmk64f Note: If you chose the Release option in the library builds: Right click on the dropdown box above the project explorer and select the Int Flash Release.  Otherwise chose Int Flash Debug, which is the default. 15. Choose Project… Make (or press F7) to build the project 16. Open the terminal program of your choice. Choose the COM port for the virtual serial connection provided by the board.  Choose 115200 baud. 17. Now, back in IAR. Choose Project…Download and Debug. Wait for it to download to the target and bring up the debug session.  Then click Go. You should see this in the terminal: Starting http server No.0 on IP 192.168.1.202 and fe80::200:5eff:fea8:1ca...[OK] Shell (build: Oct 13 2014) Copyright (c) 2013 Freescale Semiconductor; shell> shell> 18. Type help to see a list of other commands like ipconfig and ping. Windows includes IPv6 support already.  No configuration necessary.  Your computer will already have an auto-configured link-local Ipv6 address. 19. Now open a web browser 20. Type in the Ipv6 address of the board surrounded by brackets [fe80::200:5eff:fea8:1ca].  The webpage served by the board should appear. 21. You’re done.  You can now try out the shell example or use the Ipv6 evaluation library to evaluate it in your own application.  See below. Want to evaluate IPv6 in other applications? It’s easy. 1. In linker options of a user application project, replace the rtcs.a library by rtcs_ip6.a, and the shell.a library by shell_ip6.a 2. In C/C++ compiler preprocessor of a user application project, add defined symbol "RTCSCFG_ENABLE_IP6=1". 3. After that, the application is able to communicate over RTCS IPv6 communication. Best of Luck! Post any comments or feedback you have. Mac Re: How To: Get started with IPv6 for MQX RTOS TCP/IP Stack Hello, I need an example that has a button in the HTML page by sending a command to the microconntrolador and getting an answer. I use the MQX4.0 with MK60DN512 Thanks. Samuel Re: How To: Get started with IPv6 for MQX RTOS TCP/IP Stack Good point!  IPv6 is only a a 1-2 kB (flash) bigger than IPv4.  But when you run dual stack (IPv4 + IPv6) it does Not double the code size because they share common features.    The flash memory requirements look roughly like this: IPv4 with ARP, ICMP,UDP, Sockets enabled:  ~27k  IPv6 with ICMPv6, UDP, Sockets: ~28k IPv4+IPv6 with ARP, ICMP/ICMPv6, UDP, Sockets: ~41k If you add TCP, it increases it about ~14-15k. For RAM, Ipv6 takes just ~100 bytes extra for global data.  I don't have solid numbers on the heap, but I believe it is similar. Thanks, Mac Re: How To: Get started with IPv6 for MQX RTOS TCP/IP Stack Hi Mac. It would be nice to see what the flash and RAM usage is for IPV4 vs IPV6 vs dual stack.
記事全体を表示
DwF Automotive Solutions - Chongqing - 2015-08-19 Automotive and Connected Car
記事全体を表示
电源管理仿真和验证工具 - eFast <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 演示所有者David Lopez 该演示概述了我们的电源管理模拟和验证工具。我们的工具将帮助您加速符合 ISO 26262 标准的电源管理验证。 通过此演示,您将了解 NXP 如何开发创新验证工具来涵盖多种用例,并加速符合 ISO26262 的产品验证。开发该工具所使用的主要设备是 MC33908,具有 DC/DC 和最高功能安全级别的系统基本芯片。此外,该工具还涵盖 MCU 和 SBC 附件的验证。该工具包含一个通过收集不同汽车 OEM“非 ISO”脉冲而创建的数据库,执行速度很快。   特性 暂态仿真工具平台 加速符合 ISO 26262 标准的电源管理验证 全球 OEM 用例数据库 特色恩智浦产品 模拟和电源管理|恩智浦 汽车电子 工业控制
記事全体を表示
如何在 S32 Design Studio 中从 RAM 运行例程 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本文件介绍了一种方法,即在项目运行于 Flash 内存时,从 RAM 中执行选定函数。 具体做法是在链接器文件 (.ld) 中创建一个自定义链接器部分,相关例程应放置在这个部分中。如果您不关心函数在 RAM 中的具体位置,那么这一步骤是可选的。在这种情况下,可以改用默认部分。 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 }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ 如果您打算将需要从 RAM 执行的例程保留在特定的自定义部分中,可按以下方式操作: 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 ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ 将__attribute__语句添加到 RAM 函数原型中。函数属性 “longcall” 是从闪存调用此 RAM 函数所必需的。 __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 地址和大小),并将它们导入到实现 copy-down 的模块中。 __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 回复:如何在 S32 Design Studio 中从 RAM 运行例程 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Duke ,相关组件其实已经包含在内了。您可以直接安装最新累积更新版: https://community.nxp.com/docs/DOC-341653。 回复:如何在 S32 Design Studio 中从 RAM 运行例程 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 太棒了! 我们正在等待这个问题的官方补丁。 感谢您的更新,Alexander 和 NXP S32DS 支持团队。 回复:如何在 S32 Design Studio 中从 RAM 运行例程 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> cmpe200gcc-181 已修复了适用于 Power Architecture 的 S32 设计工作室 2017.R1-更新 2 中已发布的编译器中的 cmpe200gcc-181 相关问题 回复:如何在 S32 Design Studio 中从 RAM 运行例程 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 尊敬的公爵!   非常感谢您。这在我的 MPC5746C 开发板上运行正常,我将 m_text 移动到了 0x00FE0400,此前曾出现启动失败的情况。 回复:如何在 S32 Design Studio 中从 RAM 运行例程 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 和 Folkert 的情况一样, 仅ecrti.o在我看来,是需要进行修改的。 如果您能追踪您的代码,您就能找到哪个部分有问题。 如果那不是我提到的 4 字节对齐的代码。 可能您可以使用相同的方法来修复您的代码。 或者,将问题点发布在反汇编代码中。 祝您好运。 回复:如何在 S32 Design Studio 中从 RAM 运行例程 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 尊敬的公爵! 非常感谢您。这似乎有帮助!(使用 MPC5745R) 顺祝商祺,Folkert 回复:如何在 S32 Design Studio 中从 RAM 运行例程 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我遇到了同样的问题,您解决了吗? 回复:如何在 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 指令以强制执行 4 字节填充(在 VLE 架构中此填充并非隐式,而在 Booke 架构中是隐式的)。 /* Head of __init function used for static constructors. */ #ifdef __VLE__ .section".init","axv"#else .section".init","ax"#endif .align2FUNC_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 遗憾的是,应用此变通方法需要重建编译器。 此致, 埃尔克 回复:如何在 S32 Design Studio 中从 RAM 运行例程 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 大家好, 感谢您报告此问题! 我可以确认这是一个 e200 gcc 链接器缺陷(缺陷编号:CMPE200GCC-181),目前正在由编译器团队进行调查。 这在 ARM gcc (S32DS for ARM) 上运行良好。 我会随时向您汇报进展情况。 谢谢! Stan 回复:如何在 S32 Design Studio 中从 RAM 运行例程 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您解决这个问题了吗?或许您的想法是正确的,那么我们该如何避免出现这种情况呢? 回复:如何在 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将输入部分转换为 .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) 似乎 long call 会触发 init trampoline 上的错误对齐;调试/发布(flash)目标都会出现问题(在 Debug_RAM 中代码已在 RAM 中,所以不会触发问题)。 希望对您有所帮助。
記事全体を表示
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 文件以获取详细列表。
記事全体を表示
eIQ FAQ This document will cover some of the most commonly asked questions we've gotten about eIQ and embedded machine learning. Anything requiring more in-depth discussion/explanation will be put in a separate thread. All new questions should go into their own thread as well What is eIQ? The NXP® eIQ™ machine learning (ML) software development environment enables the use of ML algorithms on NXP EdgeVerse™ microcontrollers and microprocessors, including MCX-N microcontrollers, i.MX RT crossover MCUs, and i.MX family application processors. eIQ ML software is made up of several pieces of enablement including inference engines, neural network compilers and optimized libraries. This software leverages open-source and proprietary technologies and is fully integrated into our MCUXpresso SDK and Yocto development environments, allowing you to develop complete system-level applications with ease. eIQ enablement also enables models to use the new eIQ Neutron NPU found on the MCX-N and i.MX RT700 microcontroller devices and upcoming future NPU enabled embedded devices like i.MX95.  What are the key pieces of eIQ enablement?  eIQ Time Series Studio - PC tool to create and deploy classical machine learning and neural network models for time series analysis eIQ Inference Engines - Included as part of MCUXpresso SDK or Yocto Linux, this software is used to do inferencing of pre-trained neural network models on embedded devices eIQ Toolkit - Contains the Neutron Converter tool for enabling neural network models to be accelerated with eIQ Neutron NPUs eIQ Model Zoo - browse models tested on NXP silicon eIQ Model Watermarking Extension - Enhance copyright protections on custom models eIQ Model Creator - Partnership with ModelCat for vision-based model development How much does eIQ cost? eIQ Time Series Studio, eIQ Toolkit, and eIQ Inference engines are complimentary and royalty free. eIQ Model Creator has a subscription fee with ModelCat.  What is the development flow for developing and deploying AI/ML models with eIQ? There are two options depending on if already have a model or not, or if interested in Time Series or not: 1) Deploy a neural network model using the eIQ Inference Engines 2) Use eIQ Time Series Studio (TSS) to train and deploy a time series model using a simple C library eIQ Inference Engines What is the key enablement for using eIQ Inference Engines? 1) The inference engine, like TensorFlow Lite for Microcontrollers, that is included in the MCUXpresso SDK 2) eIQ Neutron Converter Tool - used to convert a quantized TFLite model into a Neutron-enabled TFLite model that can be parsed by the eIQ software. This is only required if using an eIQ Neutron NPU enabled device.  You can use any workflow to create and train your ML model. The model just needs to be exported as TFLite file so it can be converted by the eIQ Neutron Converter Tool and/or use the TFLM inference engine.  What inference engines are available in eIQ? i.MX apps processors and i.MX RT MCUs support different inference engines. The best inference engine can depend on the particular model being used, so eIQ offers several inference engine options to find the best fit for your particular application.  Inference engines for i.MX: TensorFlow Lite (Supported on both CPU and GPU/NPU) ARM NN (Supported on both CPU and GPU/NPU) OpenCV (Supported on only CPU) ONNX Runtime (Currently only supported on CPU) Inference engines for MCX and i.MX RT TensorFlow Lite for Microcontrollers ExecuTorch (Coming Soon) What devices are supported by eIQ inference engines? eIQ inference engines are available for the following i.MX application processors: i.MX 8M Plus i.MX 8M i.MX 8M Nano i.MX 8M Mini i.MX 8ULP i.MX 8X i.MX 93 i.MX 95 eIQ inference engines are available for the following MCX MCUs: MCX-N eIQ inference engines are is available for the following i.MX RT crossover MCUs: i.MX RT1180 i.MX RT1170 i.MX RT1160 i.MX RT1064 i.MX RT1060 i.MX RT1050 i.MX RT700 i.MX RT685 i.MX RT595 anthony_huereca_0-1730269555807.png Can eIQ inference engines run on other NXP MCU devices? There's no special hardware module required to run eIQ inference engines and it is possible to port the inference engines to other NXP devices.  Is eIQ Toolkit required to use eIQ inference engines?  eIQ Toolkit is required if using a device with an eIQ Neutron NPU as it includes the Neutron Converter tool which is used to convert a model to be accelerated by the NPU.  For devices that do not have an NPU, eIQ Toolkit is optional enablement from NXP to provide an option to generate models that can then be used with the eIQ inference engines. However if you already have your model development flow in place, or want to use pre-created models from a model zoo, you can use those models with eIQ inference engines as well.  What is the eIQ Neutron NPU?  The new eIQ Neutron NPU is a Neural Processing Unit developed by NXP which has been integrated into the MCX N, i.MX RT700, and i.MX95 devices, with many more to come. It was designed to accelerate neural network computations and significantly reduce model inference time. The scalability of this module allows NXP to integrate this NPU into a wide range of devices all while having the same eIQ software enablement.  For more details on the NPU for MCX N see this Community post.  How can I start using the eIQ Neutron NPU?  There are hands-on NPU lab guides available for MCX N or i.MX RT700 that walk through the steps for converting and running a model with the eIQ Neutron NPU. There is also an app note AN14700 - i.MX RT700 eIQ Neutron NPU Enablement and Performance which has more details.  What TFLite operators are supported bythe eIQ Neutron NPU on different devices?  The details and constraints for supported operators can be found in the MCUXpresso SDK documentation.  eIQ Time Series Studio What is eIQ Time Series Studio (TSS)?   eIQ TSS is software application that provides an automated machine-learning workflow that streamlines the development and deployment of time series-based machine learning models across microcontroller (MCU) class devices such as the MCX portfolio of MCUs and i.MX RT portfolio of crossover MCUs. Time Series Studio supports a wide range of sensor input signals, including voltage, current, temperature, vibration, pressure, sound, time of flight, among others, as well as combinations of these for multimodal sensor fusion. The automatic machine learning capability enables developers to extract meaningful insights from raw time-sequential data and quickly build AI models tailored to meet accuracy, RAM and storage criteria for microcontrollers. The tool offers a comprehensive development environment, including data curation, visualization and analysis, as well as model autogeneration, optimization, emulation and deployment. eIQ Time Series Studio was previously included in eIQ Toolkit but is now available as a standalone installer for both Windows and Linux. A web based version is also under development.   What devices are supported by the eIQ Time Series Studio?   TSS will generate a C library that can be included in your application and does not require an Deep Learning inference engine, so it can be deployed to a much wider range of NXP devices as it has very minimal flash and RAM requirements.  MCX FRDM-MCXA153 FRDM-MCXC444 FRDM-MCXN947 FRDM-MCXW17 i.MX RT MIMXRT1060-EVK MIMXRT1170-EVK MIMXRT1180-EVK i.MXRT685 i.MXRT595 i.MXRT700 LPC LPC55S69-EVK Kinetis FRDM-K66F FRDM-KV31F FRDM-K32L3A6 DSC MC56F83000-EVK MC56F80000-EVK i.MX i.MX93 i.MX 8M Plus Can eIQ Time Series Studio create models that can take advantage of the eIQ Neutron NPU?  Yes, TSS now supports creating both Classical Machine Learning (CML) models as well as Neural Network models. Neural Network models can be accelerated by the NPU. However in many cases it will make more sense to use the CML models for time series applications as they can be just as accurate for many time series datasets but will be much faster and use far less memory due to their smaller model size. Even when using NPU acceleration Neural Network models can be slower than their far smaller CML model counterparts. However in some situations Neural Networks may give better accuracy for complex multi-modal analysis. TSS make it easy to determine if a NN or CML model is the best fit for a particular dataset.  But as many time series applications perform well with CML models then it opens up running time series AI on a wide variety of devices even if they do not have an integrated NPU.  How can I start using the eIQ Time Series Studio tool?  There is a hands-on lab guide available to walk through how to use the tool as well as documentation and guides in the tool itself.  General eIQ Questions How can I get eIQ? For MCU devices: eIQ inference engine libraries and examples are included as part of MCUXpresso SDK for supported devices. Make sure to select the “eIQ” middleware option. eIQ Neutron Converter Tool that converts your own neural network model to use the Neutron NPU can be found in eIQ Toolkit.  eIQ Time Series Studio is available as a standalone installer For i.MX devices: eIQ is distributed as part of the Yocto Linux BSP. Starting with the 4.19 release line there is a dedicated Yocto image that includes all the Machine Learning features: ‘imx-image-full’. For pre-build binaries refer to i.MX Linux Releases and Pre-releases pages. There is eIQ Toolkit - for model conversion.   What documentation is available for eIQ? For i.MX RT and MCX devices:  eIQ MCUXPresso SDK documentation can be found online here.  For i.MX devices: The eIQ documentation for i.MX is integrated in the Yocto BSP documentation. Refer to i.MX Linux Releases and Pre-releases pages. i.MX Reference Manual: presents an overview of the NXP eIQ Machine Learning technology. i.MX Linux_User's Guide: presents detailed instructions on how to run and develop applications using the ML frameworks available in eIQ (currently ArmNN, TFLite, OpenCV and ONNX). i.MX Yocto Project User's Guide: presents build instructions to include eIQ ML support (check sections referring to ‘imx-image-full’ that includes all eIQ features). It is recommended to also check the i.MX Linux Release Notes which includes eIQ details. For i.MX devices, what type of Machine Learning applications can I create?  Following the BYOM principle described above, you can create a wide variety of applications for running on I.MX. To help kickstart your efforts, refer to PyeIQ – a collection of demos and applications that demonstrate the Machine Learning capabilities available on i.MX. They are very easy to use (install with a single command, retrieve input data automatically) The implementation is very easy to understand (using the python API for TFLite, ArmNN and OpenCV) They demonstrate several types of ML applications (e.g., object detection, classification, facial expression detection) running on the different compute units available on i.MX to execute the inference (Cortex-A, GPU, NPU). Can I use the python API provided by PyeIQ to develop my own application on i.MX devices? For developing a custom application in python, it is recommended to directly use the python API for ArmNN, TFLite, and OpenCV. Refer to the i.MX Linux User’s Guide for more details. You can use the PyeIQ scripts as a starting point and include code snippets in a custom application (please make sure to add the right copyright terms) but shouldn’t rely on PyeIQ to entirely develop a product. The PyeIQ python API is meant to help demo developers with the creation of new examples. What eIQ example applications are available for MCUs? eIQ example applications can be found in the \boards\ \eiq_examples directory:  What are Glow and DeepViewRT inference engines in the MCUXpresso SDK?  These are inference engines that were supported in previous versions of eIQ but are now deprecated as new development has focused on TensorFlow Lite for Microcontrollers. These projects are still available in MCUXpresso SDK 2.15 for legacy users, but it is highly recommended that any new projects use TensorFlow Lite for Microcontrollers.   How can I learn more about using TensorFlow Lite with eIQ? There is a hands-on TensorFlow Lite for Microcontrollers lab available. There is also a i.MX TensorFlow Lite Lab that provide a step-by-step guide on how to get started with eIQ for TensorFlow Lite for i.MX devices.  What application notes are available to learn more about eIQ? i.MX RT700 eIQ Neutron NPU Enablement and Performance  Anomaly Detection App Note  Handwritten Digit Recognition  Datasets and Transfer Learning App Note  Security for Machine Learning Package  i.MX 8M Plus NPU Warmup Time App Note  What is the advantage of using eIQ instead of using the open-sourced software directly from Github? eIQ supported inference engines work out of the box and are already tested and optimized, allowing for performance enhancements compared to the original code. eIQ also includes the software to capture the camera or voice data from external peripherals. eIQ allows you to get up and running within minutes instead of weeks. As a comparison, rolling your own is like grinding your own flour to make a pizza from scratch, instead of just ordering a great pizza from your favorite pizza place.  Does eIQ include ML models? Do I use it to train a model? eIQ has options to both create model and run pre-existing models so you can Bring Your Own Model (BYOM) and run it on NXP embedded devices. eIQ provides the ability to run your own specialized model on NXP’s embedded devices.  MCUXpresso SDK and the i.MX Linux releases come with several examples that use pre-created models that can be used to get a sense of what is possible on our platforms, and it is very easy to substitute in your own model into those examples. eIQ Time Series Studio can be used to create and deploy time series models eIQ Model Creator is an option to create your own vision based models with our partner ModelCat I’m new to AI/ML and don’t know how to create a model, what can I do? A wide variety of resources are available for creating models, from labs and tutorials, to automated model generation tools like eIQ Time Series Studio, eIQ Model Creator, Google Cloud AutoML, Microsoft Azure Machine Learning, or Amazon ML Services, to 3 rd party partners like ModelCat, SensiML and Au-Zone that can help you define, enhance, and create a model for your specific application. I’m interested in anomaly detect or time series models on microcontrollers, where can I get started? The eIQ Time Series Studio (TSS) tool, included as part of the eIQ Toolkit, is perfect for getting started with time series or anomaly detection models. It allows you to import time series datasets, generate models, and deploy them to NXP microcontrollers.  There is also ML-based System State Monitor Application Software Pack which provides an example of gathering time-series data, in this case vibrations picked up by an accelerometer, and includes Python scripts to use the data that was collected to generate a small model that can be deployed on many different microcontrollers (including i.MX RT1170, LPC55S69, K66F) for anomaly detection. The same concepts and technique can be used for any sort of times series data like magnetometers, pressure, temperature, flow speed, and much more. This can simplify the work of coming up with a customer algorithm to detect the different states of whatever system you're interested in, as you can let the power of machine learning figure all that out for you.  There is also an on-device trained anomaly detection model example that can be found on the Application Code Hub. Troubleshooting: Why do I get an error when running Tensorflow Lite Micro that it "Didn't find op for builtin opcode"? The full error will look something like this: Didn't find op for builtin opcode 'PAD' version '1' Failed to get registration from op code ADD Failed starting model allocation. AllocateTensors() failed Failed initializing model The reason is that with MCUXpresso SDK, the TFLM examples have been optimized to only support the operands necessary for the default models. If you are using your own model, it may use extra types of operands. To fix this issue, add that operator to MODEL_GetOpsResolver function found in source\model\model_name_ops_npu.cpp Also make sure to also increase the size of the static array s_microOpResolver to match the number of operators An alternative method is also described in the TFLM Lab Guide on how to use the All Ops Resolver. Add the following header file #include"tensorflow/lite/micro/all_ops_resolver.h" and then comment out the micro_op_resolver and use this instead:  //tflite::MicroOpResolver &micro_op_resolver = //MODEL_GetOpsResolver(s_errorReporter); tflite::AllOpsResolver micro_op_resolver; Why do I get the error “Internal Neutron NPU driver error 281b in model prepare!” or "Incompatible Neutron NPU microcode and driver versions!" when using the Neutron NPU? The version of the eIQ Neutron Converter Tool needs to be compatible with the NPU libraries used by your project. See more details in this post on using custom models with eIQ Neutron NPU.  Sometimes in eIQ Toolkit the Validation page hangs and it stays stuck on "Converting Model". How do I work around this?  On the Validation section of the wizard, you will need to wait for the "Input Data Type" and "Output Data Type" selection boxes to be populated before clicking on the "Validation" button at the bottom. It may take a minute or two for those selection boxes to pop up on the left hand side. Once they do, then click on Validate and it should no longer hang.  How do I use my GPU when training with eIQ Toolkit? eIQ Toolkit 1.10 only supports GPU training on Linux due to the latest TensorFlow versions no longer supporting GPU on Windows.  Why do I get a blank or black LCD screen when I use the eIQ demos that have camera+LCD support on RT1170 or RT1160? There are different versions of the LCD, so you need to make sure you have the software configured correctly for the LCD you have. See this post for more details on what to change. There is a Javascript error in Time Series Studio when I start the training.  There is a bug where if the eIQ Portal window is closed after opening the Time Series Studio then that error comes up. Try relaunching Time Series Studio but keep the original eIQ Portal window open.  The eIQ Time Series Studio in eIQ Toolkit v1.17 is v1.3.4 but it says there's a newer version?  The eIQ Toolkit v1.17 contains an older version of eIQ Time Series Studio. The latest version can always be found on the eIQ Time Series Studio website. General AI/ML: What is Artificial Intelligence, Machine Learning, and Deep Learning? Artificial intelligence is the idea of using machines to do “smart” things like a human. Machine Learning is one way to implement artificial intelligence, and is the idea that if you give a computer a lot of data, it can learn how to do smart things on its own. Deep Learning is a particular way of implementing machine learning by using something called a neural network. It’s one of the more promising subareas of artificial intelligence today. This video series on Neural Network basics provides an excellent introduction into what a neural network is and the basics of how one works.  What are some uses for machine learning on embedded systems? Image classification – identify what a camera is looking at Coffee pods Empty vs full trucks Factory defects on manufacturing line Produce on supermarket scale Facial recognition – identifying faces for personalization without uploading that private information to the cloud Home Personalization Appliances Toys Auto Audio Analysis Wake-word detection Voice commands Alarm Analytics (Breaking glass/crying baby) Anomaly Detection Identify factory issues before they become catastrophic Motor analysis Personalized health analysis What is training and inference? Machine learning consists of two phases: Training and Inference Training is the process of creating and teaching the model. This occurs on a PC or in the cloud and requires a lot of data to do the training. eIQ is not used during the training process. Inference is using a completed and trained model to do predictions on new data. eIQ is focused on enhancing the inferencing of models on embedded devices. What are the benefits for “on the edge” inference? When inference occurs on the embedded device instead of the cloud, it’s called “on the edge”. The biggest advantage of on the edge inferencing is that the data being analyzed never goes anywhere except the local embedded system, providing increased security and privacy. It also saves BOM costs because there’s no need for WiFi or BLE to get data up to the cloud, and there’s no charge for the cloud compute costs to do the inferencing.  It also allows for faster inferencing since there’s no latency waiting for data to be uploaded and then the answer received from the cloud. What processor do I need to do inferencing of models? Inferencing simply means doing millions of multiple and accumulate math calculations – the dominant operation when processing any neural network -, which any MCU or MPU is capable of. There’s no special hardware or module required to do inferencing. However specialized ML hardware accelerators, high core clock speeds, and fast memory can drastically reduce inference time. Determining if a particular model can run on a specific device is based on: How long will it take the inference to run. The same model will take much longer to run on less powerful devices. The maximum acceptable inference time is dependent on your particular application. Is there enough non-volatile memory to store the weights, the model itself, and the inference engine Is there enough RAM to keep track of the intermediate calculations and output As an example, the performance required for image recognition will be very dependent on the model is being used to do image recognition. This will vary depending on how many classes, what size of images to be analyzed, if multiple objects or just one will be identified, and how that particular model is structured. In general image classification can be done on i.MX RT devices and multiple object detection requires i.MX devices, as those models are significantly more complex. eIQ provides several examples of image recognition for i.MX RT and i.MX devices and your own custom models can be easily evaluated using those example projects.  How is accuracy affected when running on slower/simpler MCUs? The same model running on different processors will give the exact same result if given the same input. It will just take longer to run the inference on a slower processor. In order to get an acceptable inference time on a simpler MCU, it may be necessary to simplify the model, which will affect accuracy. How much the accuracy is affected is extremely model dependent and also very dependent on what techniques are used to simplify the model. What are some ways models can be simplified? Quantization – Transforming the model from its original 32-bit floating point weights to 8-bit fixed point weights. Requires ¼ the space for weights and fixed point math is faster than floating point math. Often does not have much impact on accuracy but that is model dependent. Fewer output classifications can allow for a simpler yet still accurate model Decreasing the input data size (e.g. 128x128 image input instead of 256x256) can reduce complexity with the trade-off of accuracy due to the reduced resolution. How much that trade-off is depends on the model and requires experimentation to find. Software could rotate image to specific position using classic image manipulation techniques, which means the neural network for identification can be much smaller while maintaining good accuracy compared to case that neural network has to analyze an image that could be in all possible orientations. What is the difference between image classification, object detection, and instance segmentation? Image classification identifies an entire image and gives a single answer for what it thinks it is seeing. Object detection is detecting one or more objects in an image. Instance segmentation is finding the exact outline of the objects in an image. Larger and more complex models are needed to do object detection or instance segmentation compared to image classification.   anthony_huereca_2-1762925966820.png What is the difference between Facial Detection and Facial Recognition? Facial detection finds any human face. Facial recognition identifies a particular human face. A model that does facial recognition will be more complex than a model that only does facial detection.  anthony_huereca_0-1762925921960.png How come I don’t see 100% accuracy on the data I trained my model on? Models need to generalize the training data in order to avoid overfitting. This means a model will not always give 100% confidence , even on the data a model was trained on. What are some resources to learn more about machine learning concepts?  Video series on Neural Network basics  ARM Embedded Machine Learning for Dummies Google TensorFlow Lab Google Machine Learning Crash Course Google Image Classification Practica YouTube series on the basics of ML and TensorFlow (ML Zero to Hero Series) i.MX 8 i.MX RT Re: eIQ FAQ Hi David,   eIQ Toolkit 1.0.5 is using TensorFlow version is 2.3.2, so to use the GPU when training you will need to install cuDNN v7.6 and CUDA 10.2. If you have newer versions of those tools installed on your PC you may need to uninstall those first before installing the version needed for the 1.0.5 version of eIQ Toolkit. I've also updated the FAQ with this information and it will be in the documentation in the next version of eIQ Toolkit that is released. -Anthony Re: eIQ FAQ Hi @anthony_huereca , I am using eIQ tool on model training for i.MXRT1170 platform. I find eIQ tool is always use PC CPU resource, so when it perform the model training that will occupy around 60 ~ 80% CPU resource. But it not use any GPU resource. Is there any method to configure eIQ tool to use GPU resource on the model training ? In case that will have better performance on the AI training. Is it? davidchenb3693_0-1625734326453.png davidchenb3693_1-1625734379837.png Thanks. David  
記事全体を表示
S32K344's rx interrupt can't work Hi,     I am working on S32K344's UART. We use this chip's UART0/UART1/UART8, and every UART connect to a RS485 chip and pull out A/B pin to external circuit. I connect UART1 RS485's A to UART8' RS485's A, and UART1 RS485's B to UART8' RS485's B. I set UART1 RS485's DE/RE=1, and UART8 RS485's DE/RE=0. I try to send data from UART1 to UART8, and I observe there is waveform in LPUART1_TX and LPUART8_RX in scope. That means, data has been sent from UART1 to UART8. But there is no rx interrupt in UART8, so the uart8's rx procedure can't run. During Debug, I can see the UART8 CTRL's RE=1/RIE=1 , but STAT's RDRF=0. I switch to UART8 sending and UART1's receiving, but the phenomeno is same. Could you help to check where is the problem? I attach the project. Thanks. Communication & Control(I3C | I2C | SPI | FlexCAN | Ethernet | FlexIO) S32K344's rx interrupt can't work Hi Julián, Thank you for your reply. Yes, other interrups, such CAN, PIT is OK. Now I comments out all code in callback(that means tx and rx interrupt won't run the rx function in callback), but the code still can't run out of the check receiver status loop and can't get RDRF flag set(see red rectangle in interrupt.png). I don't use Rx FIFO, so, when data is received, the RDRF ought to become 1. But it dosen't. I send char 'R'(ASCII=0x01010010) and 'Q'(ASCII=0x01010001) from UART1 and measure the the UART1's TXD and UART8's RXD, it seems the waveform is correct. Is there any other possible reason to cause this issue? I also attach my SDK version. Re: S32K344's rx interrupt can't work Hi @Jimmybai, I imagine other interrupts work with no issue? (PIT, CAN, etc). Are you pinning breakpoints inside the callback to confirm if interrupt is firing?  From your code, I can see you are using both Lpuart_Uart_Ip_SyncReceive & Lpuart_Uart_Ip_AsyncReceive. SyncReceive uses polling, while AsyncReceive function enables reception and immediately leaves function. The application has to get the receive status to know when the receive is complete. After receiving is completed (defined number of bytes received), you need to call AsyncReceive again to start new reception. However, inside the callback, instead of calling AsyncReceive again, use the Lpuart_Uart_Ip_SyncReceive function for blocking reception. You never re-arm UART's reception.  There are some examples in our community you can refer to:  [RTD600 IP] S32K312-EVB Lpuart interrupt echo - NXP Community Example S32K344 LPUART RX/TX ISR FreeRTOS S32DS36 RTD600 - NXP Community Best regards, Julián Re: S32K344's rx interrupt can't work I wonder why my attachment is missing. re-attach it. S32K344's LPUART rx interrupt can't work Hi Julián,       I found the root cause. In below code, the Async receive code should be put before the Async send code. Becasue uart transmit is very fast, when send complete, the data have sent to receiver bus. At this time, you start receiver recv procedure, the data signal has disappeared in bus. So, we need enable receiver, when data signal come, the receiver can work. What we only need to do is to check receiver's receive interrupt signal. Thank you for helping analysis my code. Jimmybai_0-1781766992780.png
記事全体を表示
如何使用 S32K 的编译脚本? 各位恩智浦专家:   目前,我使用 IDE("S32 Design Studio for S32 Platform 3.4" )手动编译项目。 我能否通过脚本在项目中执行清理、刷新、构建和切换链接文件等操作? 这样一来,我就能实现部分自动编译,而无需打开 IDE 进行操作。 Re: How to use the compilation script for S32K? 谢谢你,petervlna!  我试试看,非常感谢! Re: How to use the compilation script for S32K? 你好 是的,你可以在不打开 IDE GUI 的情况下自动版本 S32 Design Studio。S32 设计工作室基于 Eclipse,你可以利用 Eclipse 无头编译机制进行命令行编译。 您可以在以下链接中找到教程: https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/S32DS-list-of-HOWTOs/ta-p/1113475 对于命令行界面: https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-S32-Design-Studio-Command-Line-Interface/ta-p/1112410 顺祝商祺! Peter
記事全体を表示