fuse <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 索引|上一页| 下一页 （在 “我的视频” 中查看）

NXP Semiconductorsは、UAVCAN V1.0をサポートできることを嬉しく思います <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 最近更新されたUAVCAN V1.0プロトコルは、CANバス、イーサネット、およびその他の堅牢なトランスポートを介した航空宇宙およびロボットアプリケーションにおける信頼性の高い車内通信のために設計されたオープンで軽量なプロトコルです。NXPのドローンチームは、リファレンスデザインを提供し、ドローン、ローバー、および同様のロボティクスアプリケーションで使用するための高信頼性シリコンソリューションの採用を促進するために活動しています。   現代の産業用ドローンは、人気のあるDIY愛好家や消費者向けカメラのドローンをはるかに超えて進歩しています。これらの新時代の産業グレードの自律システムは、現在、捜索救助から医療輸送や配送まで、安全性が重要なタスクを提供するために使用されています。このようなシステムでは、非常に堅牢で機能的に安全なCANバスネットワークで接続された多くの追加のセンサーが必要になり始めています。   UAVCAN 1.0は、次世代のインテリジェントビークル(有人および無人航空機、宇宙船、ロボット、自動車)のシステムとコンポーネント間の決定論的なオンボードデータ交換の課題に対処します。ドローン、他の小型ロボットシステムでの使用に加えて、産業用アプリケーションや制御システムにも使用できます。更新されたUAVCAN V1.0は、V0仕様からの教訓に基づいており、正式な標準化プロセスを通じて取得することも意図されています。   NXPは、自動車業界向けの世界最大の半導体サプライヤとして、CANおよびCAN-FDシリコンを使用して車両ネットワークを近代化しました。UAVCANも同様に、最新のソフトウェア定義の小型ロボット車両のネットワークを変革する態勢を整えています。産業用ドローンのネットワークは、センサーの数やセンサーとファイトコントローラー間の距離が長くなるにつれて、ますます複雑化しています。さらに、低遅延の確定的ネットワークは、セーフティクリティカルなシステムの鍵となります。ただし、I2CやSPIインターフェースなどの一般的に使用される短距離バスは、それほど堅牢ではなく、ネットワークの距離と複雑さの増大に対応できません。これに対し、CAN-FDは2MbpsBPSから5MbpsBPSのデータレートを提供し、その堅牢性は車載アプリケーションで十分に証明されています。プライオリティ・ベースのバス・アーキテクチャにより、モータ制御などのリアルタイム・ペリフェラルを管理しながら、多くのデバイスを接続できます。複数のバスまたはトランスポートを接続して、冗長性を確保できます。   新しい V1.0 仕様では、実際の機能使用から下位層プロトコルを抽象化できるように規定されています。これにより、さまざまなユースケースや他の機能ドメインに簡単に適応できます。データ型名の定義を変更することで、UAVCAN V1.0プロトコルは、PX4ドローンやマイクロ宇宙船などの完全にカスタム化されたデバイスでも同様に機能します。V1.0 のメジャー アップデートは、最新の高速 CAN-FD ハードウェア インターフェイスのサポートだけでなく、他のタイプの物理層プロトコルよりも CAN-FD を使用できるようにしたことです。 UAVCAN V1は現在開発中であり、NXPはコミュニティと協力し、この改善された標準を可能にするエンジニアリングリソースを提供することで、その開発をサポートできることを嬉しく思います。これは、どなたでもご利用いただける規格です。その実装、配布、または使用には、いかなる種類のライセンスまたは承認も必要ありません。   この規格の適用性をドローンだけでなく、今では多くの異なるネットワークや車両タイプに反映するために、UAVCANという名前はUncomplicated Application-level Vehicular Communication And Networkingと解釈することができます。 さらに、このプロトコルの概要については、記事「UAVCAN: a highly dependable publish-subscribe protocol for real-time intravehicular networking」を参照してください。

Enabling SD Interface on P1010 Reference Design Board To enable SD interface in SPI boot on P1010RDB: 1. Perform the following updates in u-boot a) Modify pmuxcr to enable SD bus in case of SPI boot b) Update the corresponding static mux implementation in u-boot 2. Perform the following updates in Linux a) Disable IFC from device tree and kernel defconfig The patch details to enable SD interface are given below. A zip file, AN4336SW.zip, containing the patches for u-boot and Linux accompanies this application note. The file can be downloaded from [1]. U-Boot   Extract the u-boot code from the QorIQ SDK 1.0.1 iso   Apply the patch, u-boot-p1010rdb-enabling-sd-in-spi-boot.patch   Compile the u-boot using "make" command for SPI Flash    make ARCH=powerpc   CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu- P1010RDB_SPIFLASH   Use the boot_format utility to generate the spiimage. For more information, see SDK manual.   Update the SPI Flash with the above built spiimage Linux Extract the Linux source code from QorIQ SDK 1.0.1 iso Apply the patch, linux-p1010rdb-enabling-sd-in-spi-boot.patch Compile Linux using make command #make ARCH=powerpc  CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnuarch/  powerpc/configs/qoriq_sdk_nonsmp_defconfig  #make ARCH=powerpc  CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu- Compile the dts ./sripts/dtc/dtc -f -I dts -O dtb -R 8 -S 0x3000  arc/powerpc/boot/dts/p1010rdb.dts.dts > p1010rdb.dtb.dtb With the updated SPI bootloader, Linux uImage and p1010rdb.dtb, the user must be able to enable SD interface on P1010RDB. NOTE The above-mentioned changes must be done only when the user specifically requires the SD interface using SPI boot. For all other boot methods, these patches must not be used. QorIQ P1 Devices Re: Enabling SD Interface on P1010 Reference Design Board Hello! Is it possible to enable SD Interface with IFC boot? The current BSP seems to disable it by default. Tks, Bruno

MCUXpresso开发环境下多核LPC55xx的应用 [中文翻译版] 见附件   原文链接： https://community.nxp.com/community/mcuxpresso/mcuxpresso-ide/blog/2019/02/26/lpc55xx-multicore-applications-with-mcuxpresso-ide LPC55xx

交叉代码挑战网络研讨会 - 12 月 10 日.pdf <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 2019 年 12 月 10 日，恩智浦主办的网络研讨会幻灯片。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 2019 年 12 月 10 日，恩智浦主办的网络研讨会幻灯片。 i.MXRT 101x 回复：跨界代码挑战网络研讨会 - 12 月 10 日.pdf <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 凭借用于电机控制的 Flex PWM、用于音频的 S/PDIF 以及用于图形 LCD 等的 FlexIO 模块等功能，很容易看出可以从这种通用用途中受益的产品和用例的广度www.krogerfeedback.com

通信驱动程序-应用程序配置 本文旨在向您展示让您的嵌入式应用程序开始与 FreeMASTER 主机应用程序通信所需的最低设置。 它是 FreeMASTER 教程系列的一部分： 通信驱动程序（当前文章） 连接到开发板 目标端地址转换 通信驱动程序和 S32 设计工作室 前提条件： FreeMASTER 通信驱动程序 适用于 ARM 2018.R1 的 S32 Design Studio，配备 S32 SDK S32K1xx RTM 3.0.0 请参阅附件中的示例应用程序源代码。 （在 “我的视频” 中查看） 如果您阅读了《通信驱动程序》文章，您可能已经注意到 FreeMASTER 下载页面上提供的独立包实现了通信协议的 2.0 版本。 为什么这个视频仍然使用旧版本？ 最新版本比较新，并不是所有平台都有更新支持。 S32 Design Studio和基于模型的设计工具箱仍然使用以前版本的驱动程序。 主机应用程序完全向后兼容并支持两个版本的通信协议。

Introducing FreeMASTER 3.0 Dear users,  18 year after releasing the first version the tool (called PCmaster that time) and four years since the FreeMASTER version 2.0 we are here again with something new. FreeMASTER 3.0 comes with updated communication protocol, extended floating and dockable graph views, new JSON-RPC scripting support and with a Chromium engine to render Control Pages. Old concepts of ActiveX scripting and the embedded Internet Explorer remain available for backward compatibility. Along with the reworked desktop application, we also introduce FreeMASTER Lite service. The FreeMASTER Lite strips down the UI and concentrates on the communication core. Same as the desktop tool, the lite version enables users to connect to the target microcontroller board and to share the access with remote clients using JSON-RPC. It also runs its own web server and enables remote mobile devices like phones or tablets to connect, fetch HTML files and other resources and run the Control Page interface in a standalone environment. FreeMASTER serial driver supporting the new version (v4) of the communication protocol is now available in the MCUXpresso SDK as a middleware component. See more details in the SDK Builder at mcuxpresso.nxp.com. Use this newly created community page to discuss FreeMASTER use cases or issues. See you around, your FreeMASTER team.

T_Box Description Features Block Diagram Products Tools Description With the development of new technologies in today’s world, the automotive industry is now capable of implementing new devices that allow drivers to have wider control of their automobiles. These devices could offer remote diagnostic services for vehicle monitoring, car security, GPS to optimize driving paths, and many other services. T-Box provides a remote communication interface for the vehicle as a wireless gateway. It can provide: Traffic data acquisition Travel track record Information and entertainment services such as navigation, news, weather and other information push Vehicle fault monitoring Vehicle remote control (open lock, air conditioning control, window control, transmitter torque limit, engine start and stop) Driving behavior analysis 4G wireless hotspot sharing and other services Features EMC controller support SDRAM CAN controller (from more than 2 CH to more than 3 CH) Small package (from LQFP to BGA) More I/O pins (more UART, SPI, I2C). Low power (GPIO wakeup and RTC wakeup) Cost effective Block Diagram Products Category Name 1: MCU Product URL 1 LPC1778FET208|Arm Cortex-M3|32-bit MCU | NXP  Product Description 1 The LPC1778FET208 is a low-power, cost-effective MCU featuring up to 512 KB Flash, 96 KB SRAM, 4 KB EEPROM and a wide assortment of connectivity peripherals, including up to five UARTs, three SPI/SSP, and three I²C. Product URL 2 LPC540XX Family of Microcontrollers (MCUs) | NXP  Product Description 2 The LPC54S016 offers power-efficiency and unique architecture, advanced HMI and flexible communication peripherals for real-time performance for the next-generation IoT. Category Name 2: Transceiver Product URL 1 TJA1041A | High-Speed CAN transceiver | NXP  Product Description 1 The TJA1041A is primarily intended for automotive high-speed CAN applications (up to 1 Mbit/s). Product URL 2 TJA1043 | High Speed CAN transceiver | NXP  Product Description 2 The TJA1043 transceiver is designed for high-speed CAN applications in the automotive industry, providing differential transmit and receive capability to (a microcontroller with) a CAN protocol controller. Product URL 3 TJA1051 | High-speed CAN Transceiver | NXP  Product Description 3 The TJA1051 transceiver is designed for high-speed CAN applications in the automotive industry, providing differential transmit and receive capability to (a microcontroller with) a CAN protocol controller. Category Name 3: Peripherals Product URL 1 MC33972 | MSDI with Suppressed Wakeup | NXP  Product Description 1 The 33972 Multiple Switch Detection Interface (MSDI) with suppressed wake-up is designed to detect the closing and opening of up to 22 switch contacts. This device also features a 22-to-1 analog multiplexer for reading inputs as analog. Product URL 2 Tiny Real-Time Clock/calendar | NXP  Product Description 2 The PCF85063TP is a CMOS Real-Time Clock (RTC) and calendar optimized for low power consumption. An offset register allows fine-tuning of the clock. Product URL 3 ±2g/±4g/±8g, Low g, 14-Bit Accelerometer | NXP  Product Description 3 The FXLS8471Q accelerometer is highly versatile and ideal for industrial, consumer and automotive high-performance, low-g applications that offer noise density, board mount offset, temperature performance, and sensitivity. Product URL 4 High-speed CAN core system basis chip | NXP  Product Description 4 The UJA1076A supports the networking applications used to control power and sensor peripherals by using a high-speed CAN as the main network interface. Tools Product Link OM13001: EA LPC1788 Evaluation Board EA LPC1788 Evaluation Board | NXP  LPC54S018M-EVK: LPCXpresso54S018M Development Board LPCXpresso54S018M Development Board | NXP  OM11059A: Demoboard for the I²C RTC PCF85063TP and PCF85063ATL Demoboard for the I²C RTC PCF85063TP and PCF85063ATL | NXP  Sensor Toolbox Development Boards for FXLS8471Q 3-Axis Linear Accelerometer FXLS8471Q 3-Axis Accelerometer Development Boards | NXP  Automotive Block Diagrams

Touch Board Description Features Block Diagram Products Documentation Demos Tools Description The user interface of a product is a key element that design engineers need to address to provide a compelling user experience. Touchpads, slides and rotaries offer a more intuitive and effective way of user interaction than traditional buttons. And, designing a touch-based user interface is simplified with this NXP touch solution. The touch function is more and more popular in the consumer market, especially in the white-good field. The KE15Z series of MCUs offers the Touch Sensing Interface (TSI) which recognizes finger touch by sensing capacitance changes. Features Advanced EMC robustness, pass IEC61000-4-6 standard test Supports both self-cap sensor and mutual-cap sensor, up to 36 touch keys Low BOM cost per touch key, no need for external devices Adjustable touch sensing resolution and sensitivity, high-performance for waterproof applications Low-power support Block Diagram Products Category Name 1: MCU Product URL 1 Arm Cortex-M0+|Kinetis KE1xZ 32-bit 5V MCUs with Touch Interface | NXP  Product Description 1 The KE1xZ includes a robust TSI module which provides a high level of stability and accuracy to any HMI system. These MCUs support up to 256 KB flash, 32 KB RAM, and a complete set of analog/digital features. Category Name 2: Wireless Product URL 1 Arm® Cortex®-M0+|Kinetis® KW41Z 2.4 GHz Bluetooth Low Energy Thread Zigbee Radio MCUs | NXP  Product Description 1 The KW41Z is an ideal solution for true single-chip designs that require concurrent communication on both a Bluetooth Low Energy network and an 802.15.4-based network such as Thread and Zigbee. Documentation KE15Z TSI Development for Low Power Applications:  https://www.nxp.com/docs/en/application-note/AN5420.pdf  Demos Touch Sense Interface for Kinetis KE15Z MCUs  Tools Product Link FRDM-KW41Z: Freedom Development Kit for Kinetis® KW41Z/31Z/21Z MCUs FRDM-KW41Z |Bluetooth Thread Zigbee enabled Freedom Development Kit | NXP  FRDM-TOUCH: Touch Module for Freedom Board FRDM-TOUCH|Touch Module for Freedom Board | NXP  Block Diagrams Industrial Mobile Smart Home

RDDSP56F8SRDS: 3-Phase SR Motor Sensorless Control Reference Design using 56F80X or 56F8300 DSCs Overview Features Block Diagram Board Design Resources Overview The reference design demonstrates sensorless control of the 3-Phase Switched Reluctance (SR) motor using 56F80x or 56F83XX Digital Signal Controllers. It can also be adapted to 56F81XX Digital Signal Controllers. The concept of this application is that of a sensorless speed closed loop SR drive using flux linkage position estimation. An inner current loop with PI controller is included. The change in phase resistance during motor operation due to its temperature dependency creates errors in the position estimation and significantly affects the performance of the drive. Therefore, a novel algorithm for on-the-fly estimation of the phase resistance is included. The Digital Signal Controller runs the main control algorithm. Rotor position is evaluated using the sensorless flux linkage estimation algorithm. The actual flux linkage is calculated at the rate of the PWM frequency and is compared with the reference flux linkage for a given commutation angle. When the actual flux linkage exceeds the reference, the commutation of the phases is done; the actual phase is turned off and the following phase is turned on. Flux linkage error is used for estimation of the phase resistance at low speeds (US Patent No.: 6,366,865). The actual speed of the motor is determined using the commutation instances. Based on the speed error, the speed controller generates the desired phase current. When the phase is commutated, it is turned on with a duty cycle of 100%. Then, during each PWM cycle, the actual phase current is compared with the desired current. As soon as the actual current exceeds the desired current, the current controller is turned on. The current controller controls the output duty cycle until the phase is turned off (following commutation). Finally, the 3-Phase PWM control signals are generated. The procedure is repeated for each commutation cycle of the motor. Features Sensorless control of an SR motor using a flux linkage estimation technique Targeted for 56F80X, 56F83XX, and 56F81XX Digital Signal Controllers Running on a 3-Phase SR HV Motor Control Development Platform The control technique: current control with a speed closed loop Position estimation based on flux linkage estimation Phase resistance measurement during start-up Phase resistance estimation at low speeds Motor starts from any position with rotor alignment Encoder position reference for evaluation of sensorless position estimation Manual interface FreeMASTER software control interface and monitor Fault protection Block Diagram Board Design Resources Legacy Designs

k64f と kw41z のアプリケーションバイナリの回復 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> アプリ動画

通过使M4 Hello world正确运行来理解iMX8QX硬件分区（硬件分区实践） [中文翻译版] 见附件   原文链接： https://community.nxp.com/docs/DOC-345359  i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus

Power Management for Connectivity & Infotainment This session introduces our safety power management portfolio. Learn how to develop applications for automotive infotainment and connectivity. This session introduces our safety power management portfolio. Learn how to develop applications for automotive infotainment and connectivity. Power Management

FreeRTOS Threads in Eclipse Debug View with SEGGER J-Link in S32DS The following article describes how to add FreeRTOS thread aware debugging to the Eclipse Debug view using SEGGER J-Link: Show FreeRTOS Threads in Eclipse Debug View with SEGGER J-Link and NXP S32 Design Studio | MCU on Eclipse  I hope this is useful, Erich Debugging - Flash Programming Eclipse IDE Usage and Settings General

これで、構成セクションにコンポーネントセクションを要求できるようになりました <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 以前は、設定セクションは設定セクションのみを必要とすることができましたが、現在は設定に設定とコンポーネントを要求できるようになりました。 この新機能により、一部のコンポーネントセクションが一部のボード/キットのすべてのアプリケーションで一般的に必要とされる場合、ユーザーはこのボード/キットの共通の設定セクションを使用して、すべてのymlファイルの「__hierachy__」でそれらを維持するのではなく、それらを要求できるため、保守の労力を大幅に節約できます。 Re:現在、構成セクションにはコンポーネントセクションが必要です <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ケイト、何か例を挙げていただけますか?

HOWTO: Working with AMMCLib SDKs Please note: AMMCLib SDK is standalone from S32/MPC SDK, it is intended for users who will not use the S32/MPC SDK. The AMMCLib SDK does not support all toolchains listed in S32DS new project wizard. For the toolchains it does support, It does not support all versions. The available SDKs will vary depending upon the toolchain which is selected. When creating a new S32DS Application Project, you may have noticed the S32K14x_AMMCLib_xxx SDK option in the Select SDK menu. This is the standalone version of the AMMCLib. If you plan to use one of the S32/MPC SDKs, then it most likely contains an integrated version of the AMMCLib. For this integrated case, the AMMCLib is accessed like any other S32/MPC SDK component and you would not need to add the standalone version. To add the AMMCLib SDK to your project, simply add it in the New Project Wizard (as pictured above) or add it later through the project properties menu, SDKs: Select the SDK from the list and then click 'Attach/Detach...' Click in the column for each build configuration for which you wish to have the SDK attached. You can remove SDKs by clicking the '+', causing it to disappear. It should also be noted that there exist example projects which demonstrate usage of the AMMCLib, though these show usage of the S32/MPC SDK integrated version. When working in your project, you can use the SDK Explorer to drag and drop macros and function calls into your code. To add the SDK Explorer view to your perspective, there are at least 2 methods: 1) Menu method a) Window -> Show View -> Other... OR Alt + Shift + Q, Q b) Filter on 'SDK' c) Select 'SDK Explorer' d) Click OK 2) Quick Access method a) Type 'SDK' b) Select 'SDK Explorer' To access the macros and function calls from the SDK Explorer: 1) Go to the Project Explorer and select your project to make it active. 2) Go to SDK Explorer and all of the SDKs you included in the project will be listed. 3) For the SDK you wish to access, expand the folders and files until you can see the function you wish to add. You can set some filters to hide unwanted content. 4) Simply drag and drop the macro/function call into your source file. The #include statement for the associated header file will be automatically added near the top of your source file. Happy math coding with AMMCLib! General New Project Wizard - Project Management and Settings SDKs

在Ubuntu 18.04 LTS上编译L4.14.98-2.0.0 BSP [中文翻译版] 见附件   原文链接： https://community.nxp.com/docs/DOC-344893  i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus

ミニモンキーレブB 基板付:NG <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Mini-Monkeyの設計を更新し、PCB:NGを使用して製作しました。 (マイビデオで視聴)

Porting CAN to K64 bootloader 1. Introduction MCUboot is a common used bootloader for most of Kinetis and i.mx RT devices. It can support download application via UART/USB/CAN/I2C/SPI. It enables quick and easy programming of Kinetis MCUs and i.mx RT MPU through the entire product life cycle, including application development, final product manufacturing, and beyond. K64 is a very popular device in Kinetis family. It has a M4 core, 512k and above flash, 120M main frequency and plenty of interface, such as I2C/SPI/UART/CAN/USB/ENET. But it is a bit awkward that the MCUboot demo of K64 is not include CAN. Does K64’s CAN can’t support bootloader application? No, of course not. Here we are going to port CAN function to K64 bootloader. There are two kind of CAN peripheral in Kinetis family, FlexCAN and MSCAN. FlexCAN is more complex than MSCAN. K64 has a FlexCAN. To speed up our work, we can port FlexCAN driver and related code from TWR-KV46 bootloader. Hardware: two TWR-SER board two sets of TWR-ELEV TWR-K65F150M TWR-K64F120M   Software: MCUXpresso 11.0 MCUBoot 2.0.0 package SDK_2.6.0_TWR-K64F120M 2. Software porting Step 1, copy below files to twrk64f120m_tower_bootloader project. \drivers\fsl_flexcan.c \drivers\fsl_flexcan.h        \source\bootloader\src\flexcan_peripheral_interface.c   Step 2, modify the project to enable the FlexCAN.       In bootloader_config.h, change BL_CONFIG_CAN definition to 1.        In peripherals_MK64F12.c, add #if BL_CONFIG_CAN     // CAN0     {.typeMask = kPeripheralType_CAN,      .instance = 0,      .pinmuxConfig = can_pinmux_config,      .controlInterface = &g_flexcanControlInterface,      .byteInterface = &g_flexcanByteInterface,      .packetInterface = &g_framingPacketInterface }, #endif    // BL_CONFIG_CAN       Pin mux setting. In peripherals_pinmux.h, add #define BL_ENABLE_PINMUX_CAN0 (BL_CONFIG_CAN) //! CAN pinmux configurations #define CAN0_RX_PORT_BASE PORTB #define CAN0_RX_GPIO_PIN_NUM 18             // PIN 13 in the PTA group #define CAN0_RX_FUNC_ALT_MODE kPORT_MuxAlt2 // ALT mode for CAN0 RX functionality for pin 13 #define CAN0_TX_PORT_BASE PORTB #define CAN0_TX_GPIO_PIN_NUM 19             // PIN 12 in the PTA group #define CAN0_TX_FUNC_ALT_MODE kPORT_MuxAlt2 // ALT mode for CAN0 TX functionality for pin 12       Set clock. FlexCAN clock source can be OSCERCLK or bus clock. Here we use bus clock run at 48Mhz. In flexcan_peripheral.c, add these code. const flexcan_timing_config_t bit_rate_table48m[] = {     { 23, 3, 4, 4, 4 }, /* 125 kHz */     { 11, 3, 4, 4, 4 }, /* 250 kHz */     { 5, 3, 4, 4, 4 },  /* 500 kHz */     { 3, 3, 4, 4, 4 },  /* 750 kHz */     { 2, 3, 4, 4, 4 }   /* 1   MHz */ }; change line 621 FLEXCAN_SetTimingConfig((CAN_Type *)baseAddr, &bit_rate_table48m[s_flexcanInfo.baudrate]); Step 3, compile the project.   3. Function test Software preparation To connect bootloader via CAN bus, NXP has TWR-K65 as bridge. But its source code is not in K64 SDK. It is in MCUBoot2.0.0 package. User can download the package from https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools/mcuboot-mcu-bootloader-for-nxp-microcontrollers:MCUBOOT The bridge project is called buspal which can be found in NXP_Kinetis_Bootloader_2_0_0\apps\bus_pal\MK65F18. BusPal is an embedded software tool that is available as a companion to blhost. The tool acts as a bus translator with an established connection with blhost over UART and with the target device over I2C, SPI, or CAN, and assists blhost in carrying out commands and responses from the USB target device. The BusPal is available for selected platforms. The source code for BusPal is provided with the Kinetis bootloader release, it support FRDM-KL25, TWR-KV46F150M and TWR-K65F180M and can be customized to run on other platforms. More detail of buspal is in Kinetis blhost User's Guide appendix C.   Hardware connection TWR-SER has TJA1050 as transceiver. We can connect J7 on both boards. When construct the Tower system, user should take care the power. The power tree is very flexible. Improper setting may cause TJA1050 can’t work.   The Buspal project on TWR-K65F180M use UART1 to connect with computer. The port is on TWR-SER. To make the connection simple, we can share the openSDA UART port. The openSDA UART use UART2, we can jump UART1 signal to J33 and J34 on K65 tower board.     Testing: Open a command window, type >blhost -p com4,57600 –buspal can,0,321,123 – get-property 10 This command can check if the whole system work properly. Then, you can download the code to K64 now. Please type >blhost -p com4,57600 –buspal can,0,321,123 – flash-image xxxxxx.s19 erase Kinetis K Series MCUs

信息娱乐，连接性和安全性：简介在i.MX 8应用处理器上进行异构处理 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> i.MX 8 架构具有两种处理器类型：用于应用程序的强大的 Arm ® Cortex ® -A 和用于实时处理的 Cortex-M4。在本课程中，您将了解这些核心如何交互以及我们的 SoC 上嵌入了哪些功能以简化此架构的开发。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> i.MX 8 架构具有两种处理器类型：用于应用程序的强大的 Arm ® Cortex ® -A 和用于实时处理的 Cortex-M4。在本课程中，您将了解这些核心如何交互以及我们的 SoC 上嵌入了哪些功能以简化此架构的开发。 身份验证与安全 接口和连接