Multi Source Translation Content

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Multi Source Translation Content

讨论

排序依据:
飞思卡尔物联网解决方案 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 了解什么是物联网网关?不同类型的物联网网关有哪些功能要求?为什么安全很重要以及飞思卡尔如何满足这些需求?您还将了解物联网解决方案的连接选项和软件支持。 在 DwF IoT 无线模块解决方案 - 济南 - 2015 年 4 月 23 日 & 广州 - 2015 年 6 月 11 日 上发表 会话 ID:APF-SNT-T1356 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 了解什么是物联网网关?不同类型的物联网网关有哪些功能要求?为什么安全很重要以及飞思卡尔如何满足这些需求?您还将了解物联网解决方案的连接选项和软件支持。 在 DwF IoT 无线模块解决方案 - 济南 - 2015 年 4 月 23 日 & 广州 - 2015 年 6 月 11 日 上发表 会话 ID:APF-SNT-T1356
查看全文
KW45 Knowledge Hub KW45’s three-core architecture integrates a 96 MHz CM33 application core, dedicated CM3 radio core and an isolated EdgeLock Secure Enclave. The Flash-based radio core with dedicated SRAM delivers a highly configurable and upgradeable software-implemented radio, freeing resources on the main core for customer application space. The Bluetooth Low Energy 5.3-compliant radio supports up to 24 simultaneous secure connections. The EdgeLock Secure Enclave’s isolated execution environment provides a set of cryptographic accelerators, key store operations and secure lifecycle management that minimizes main core security responsibilities. The KW45 MCU additionally integrates FlexCAN, helping enable seamless integration into an automobile’s in-vehicle or industrial CAN communication network. The FlexCAN module can support CAN’s flexible data rate (CAN FD) for increased bandwidth and lower latency. neidys_vargas_0-1729795404448.png KW45 Block Diagram neidys_vargas_0-1730123110234.png KW45 Architecture Block Diagram Documents Reference Manual Datasheet Errata Secure Reference manual** Security Certifications  SESIP Level 2 Cert SESIP Level 2 ST PSA Level 2 Certification Regulatory Certifications RED Certification EUROPEAN UNION DECLARATION OF CONFORMITY (EVK) EUROPEAN UNION DECLARATION OF CONFORMITY (LOC) Japan MIC KW45-LOC _TELEC-20250221 Bluetooth Qualifications Qualified Products | Bluetooth® Technology Website Qualification Workspace - KW45/MCX W71 Bluetooth IInterested in Bluetooth technology? Bluetooth® Low Energy Primer – Essential reading for understanding BLE fundamentals. Bluetooth® Specifications – Full list of standards, protocols, and technical documents. Awards and Recognition - Every year, the Bluetooth Special Interest Group (SIG) celebrates the hard work and commitment of working groups, committee members, and contributors who have been recognized by their peers as making a difference in advancing Bluetooth technology, like NXP! 2024: Channel Sounding 2025: Channel sounding amplitude-based attack resilience, LE test mode enhancements and Ranging profile and service.  Bluetooth Feature Overview Bluetooth_5.0_Feature_Overview  Bluetooth_5.1_Feature_Overview  Bluetooth_5.2_Feature_Overview Bluetooth_5.3_Feature_Overview Bluetooth_5.4_Feature_Overview Bluetooth_6_Feature_Overview Bluetooth_6.1_Feature_Overview Bluetooth_6.2_Feature_Overview Bluetooth_6.3_Feature_Overview Evaluation boards KW45 KW45-EVK KW45-EVK Schematic KW45-EVK Design Files KW45-EVK User manual KW45-LOC User manual KW45-EVK Getting Started Application Notes Software, Hardware and Peripherals: AN14122 : How to use RTC on KW45 This application note describes how to configure and use the RTC peripheral in a BLE demo AN14141 : Enabling Watchdog Timer Module on KW45 Bluetooth Low Energy Connectivity Stack This application note describes the process to implement the WDOG timer in a Connectivity Stack demo. AN13855 : KW45/K32W1 Integrating the OTAP Client Service into a Bluetooth LE Peripheral Device This Application note provides the steps and process for integrating the Over the Air Programming Client Service into a BLE peripheral device. AN13584 : Kinetis KW45 and K32W1 Loadpull Report This application note describes measurement methodology and associated results on the load-pull characteristics. AN13860 : Creating Firmware Update Image for KW45/K32W1 using OTAP tool This application note provides the steps to create and upgrade the image on the KW45 board via OTAP. AN14077 : Steps to migrating KW45 (1MB) to KW45 (512kB) This application note describes the initial steps require to migrate from 1MB flash to 512kB flash. AN14746 : EEPROM Emulation for the KW45B41Z and K32W148 This document describes the process for the EEPROM emulation for the KW45B41Z and K32W148. AN14298 32kHz Cystal-Less Mode on KW45: This application note provides information on the 32 kHz Crystal-less mode on the KW45 device. This mode allows you to reduce the cost of the system, without compromising the 32 kHz clock accuracy.  Power Management: AN13230: Kinetis KW45 and K32W1 Bluetooth LE Power Consumption Analysis This application note provides information about the power consumption of KW45 wireless MCUs, the hardware design and optimized for low power operation. AN13831: KW45/K32W1 Power Management Hardware This application note describes the usage of the different modules dedicated to power management in the KW45/K32W1 MCU. AN14664 Coin cell Hardware Recommendations for Kinetis Bluetooth LE Applications: This document describes some hardware and software solutions to minimize the peaks of current at the coin cell level RF: AN13687 : K32W1 Connectivity test for 802.15.4 Application This application note describes how to use the connectivity test tool to perform K32W1 802.15.4 RF performance. AN13728 : KW45 RF System Evaluation Report for Bluetooth LE and IEEE 802.15.4 Applications This application note provides the radio frequency evaluation test results of the KW45 board for BLE (2FSK modulation) and for IEEE 802.15.4 (OQPSK modulation) applications. Also describes the setup and tools that can be used to perform the tests.  AN14098: KW45-LOC RF Test Report This application note provides basic RF test result of the KW45B41Z localization board.  AN13228 : KW45-EVK RF System Evaluation Report for BLE Applications This application note provides the RF evaluation test result of the KW45B41Z-EVK for BLE application using two frequency Shift Keying modulation. AN13229 : KW45-EVK Co-existence with RF System Evaluation Report for BLE application This application note provides the RF evaluation test results of the KW45B41Z-EVK for BLE application (2FSK modulation) AN13512 : Kinetis Wireless Family Products BLE Coexistence with Wi-Fi Application This application note provides the K32W1/4X low energy family products immunity on Wi-Fi signals and methods to improve coexistence with Wi-Fi  AN14294 : Out of Band Implementation with KW45 This document explains the steps required to set up an Out of Band (OOB) pairing connection between two KW45 EVK boards, using UART and CAN communication interfaces to share OOB data. AN2731 Compact Planar Antennas for 2.5GHz Communication: This document is not an exhaustive inquiry into antenna design. It is instead focused on helping the customers understand enough board layout and antenna basics to select a correct antenna type for their application, as well as avoiding typical layout mistakes that cause performance issues that lead to delays AN14645 How to Use Random Static Device Address for Bluetooth Application: This document introduces how to enable Random Static Device Address for a Bluetooth Low Energy application. The default device address type in the SDK is Public Device Address. AN14112 Car Connectivity Consortium (CCC) Digital Key R3 - Bluetooth LE Vehicle Keyless Access System: This document provides a hardware and software platform to implement a simple CCC Digital Key Release 3.0 system. The hardware and software components of this system allow the user to get familiar with the CCC Digital Keys R3 specification and how it can be implemented using NXP products and tools. AN13953 Integrating NFC Reader Library in a KW4X Bluetooth Low Energy Application:  This document gives instructions on how to create a Bluetooth Low Energy (Bluetooth LE) project for the EVK-KW45 development board and MCUXpresso IDE, and how to integrate NFC Reader Library. Security: AN13859 : KW45/K32W1 In-System Programming Utility This application note provides steps to boot KW45/K32W1 MCU in ISP mode and establish various serial connections to communicate with the MCU. AN14003 : Programming the KW45 Flash for Application and Radio Firmware via Serial Wire Debug during mass production This application note describes the steps to write, burn and programming all the necessary settings via SWD in mass production.  AN13883 : Updating KW45 Radio Firmware Via ISP Using SPSDK This application note provides steps to boot KW45/K32W1 MCU in ISP mode and update the radio firmware with secure binary. AN14109 : KW45 and K32W148 Secure  Boot Using the SEC Tool This application note provides steps to do secure boot KW45/K32W1 MCU using signed images and secure binaries on the SEC GUI tool. AN13838 :  KW45 and K32W148 Secure  Boot Using the SPSDK Command line Tool This application note provides steps to do secure boot KW45/K32W1 MCU using signed images and secure binaries on the SPSDK command line tool. AN13931 : Managing Lifecycles on KW45 and K32W148 This application note provides steps to do transition lifecycles KW45/K32W1 MCU using the SEC GUI and SPSDK command line tools.  AN14158: Debug Authentication on KW45/ K32W148 This application note describes how to do debug authentication to securely debug an application in the field.  AN14544 : EdgeLock 2GO Services for MPU and MCU This application note introduces the EL2GO services for NXP devices. This allows trust provisioning of the device in an untrusted environment.  AN14174: KW45/K32W1 Flash Encryption using NPXThis application note provides steps to do enable on-the-fly encryption on KW45/K32W1 MCU. AN14158: debug authentication on KW45/K32W148 This application note describes the steps for debug authentication using the Secure Provisioning SDK tool (SPSDK). Useful Links [MCUXSDK] How to use GitHub SDK for KW4x, MCXW7x, MCXW2x - NXP Community this community post provides step by step how to use GitHub SDK [MCUXSDK] GitHub SDK - Documentation for Bluetooth LE platforms - NXP Community this community post provides the documentation for BLE platforms.  Clock Measuring using the Signal Frequency Analyzer (SFA) module for KW45/KW47/MCXW71/MCXW72 - NXP Community : this community provides the steps on how to use the Signal Frequency Analyzer  The best way to build a PCB first time right with KW45 (Automotive) or K32W1/MCXW71 (IoT/Industrial)... Community : In this community provides the important link to build a PCB using a KW45 or K32W148 and MCXW71 and all concerning the radio performances, low power and radio certification (CE/FCC/ICC) How to use the HCI_bb on Kinetis family products and get access to the DTM mode:  This article is presenting two parts: How to flash the HCI_bb binary into the Kinetis product. Perform RF measurement using the R&S CMW270 BLE HCI Application to set transmitter/receiver test commands: This article provides the steps to show how user could send serial commands to the device. Bluetooth LE HCI Black Box Quick Start Guide : This article describes a simple process for enabling the user controls the radio through serial commands. Kinetis (../45/47/43;MCX W71/72/70) & MCX W23 Power Profile Tools (including Localization):  This page is dedicated to the Kinetis (KW35/KW38/KW45/KW47/KW43) and MCX W7x (MCX W71/W72/W70) Power Profile Tools. It will help you to estimate the power consumption in your application (Automotive or IIoT) and evaluate the battery lifetime of your solution. KW45/K32W1 32MHz & 32kHz Oscillation margins: this article provides the properly configuration for the Oscillation margins for the circuit. KW45/MCXW71 Changing Clocking peripherals from FRO6M to other clock sources:  This article provides a comprehensive guide to selecting and configuring alternative clock sources   Reference Designs Bluetooth Ranging Access Vehicle Enablement System - NXP Community Blue Ravens (Bluetooth Ranging Access Vehicle Enablement System) is a system solution developed by NXP to assist customers in designing their own BLE-based car access solutions using NXP products. Demo (video) KW45 Based CS 1 to Many Demo NXP - Channel Sounding   Training BLE Introduction  RF Switch Comparison Absorptive/Reflective Standards Comparison ETSI / FCC / ARIB requirements BLE Channel Sounding  - Overview BLE Channel Sounding - RF Hardware BLE Channel Sounding - ANSYS Modeling Tools  BLE Channel Sounding - Antenna Prototypes Validation Measurements     Equipment Wireless Equipment: This article provides the links to the Equipment that helps to the project development  Development Tools  SDK builder: The MCUXpresso SDK brings open-source drivers, middleware, and reference example application to speed your software development. SDK GitHub: SDK open-source Drivers, middleware and reference examples in Github NXP MCUXpresso: MCUXpresso IDE offers advanced editing, compiling and debugging features with the addition of MCU-Specific debugging. Supports connections with all general-purpose Arm Cortex-M.  NXP SPSDK: Is a unified, reliable, and easy to use Python SDK library working across the NXP MCU portfolio providing a strong foundation from quick customer prototyping up to production deployment. NXP SEC Tool: The MCUXpresso Secure Provisioning Tool us a GUI-based application provided to simplify generation and provisioning of bootable executables on NCP MCU devices. NXP OTAP Tool: Is an application that helps the user to perform an over the air firmware update of an NXP development board. Config Tool: MCUXpresso Config Tools, an integrated suite of configuration tools, these configuration tools allow developers to quickly build a custom SDK and leverage pins, clocks and peripheral to generate initialization C code or register values for custom board support. SDK Examples for Wireless MCUs: The wireless examples feature many common Bluetooth configurations. **For secure files is necessary to request additional access.  Hands-On Training Product: K32W1 Protocol: 802.15.4 Protocol: BLE -> connectivity Protocol: Bluetooth Protocol: Matter Protocol: Thread Protocol: Zigbee
查看全文
将 EdgeLock® SE05X 集成到 FRDM-IMX91 本文档内容免责声明: NXP 提供的任何支持、信息和技术(“材料”)均按“现状”提供,不附带任何明示或暗示的保证,且 NXP 在适用法律允许的最大范围内,否认与材料相关的所有直接或间接责任和损害。NXP 对任何与应用或产品设计相关的协助不承担任何责任。材料仅可用于与 NXP 产品相关联。NXP 可以不受限制地使用您对材料提供的任何反馈。 摘要 本文档旨在指导开发者将 EdgeLock® SE050安全芯片集成到 NXP FRDM-i.MX91开发板上,以实现硬件级别的安全增强。通过将 i.MX 91 的高性能计算能力与 SE050 的认证安全特性相结合,可为工业物联网和智能家居等应用提供端到端的安全保障,同时显著降低开发复杂度和上市时间。 硬件先决条件 主机平台:FRDM-i.MX91 扩展板: OM-SE050X。 硬件设置 1. 按如下方式配置 OM-SE05xARD 跳线[1]: Kan_Li_0-1753253567624.png 2. 确认 FRDM-i.MX91 上的启动开关设置,以运行预加载的 Linux®镜像[2]。 启动开关应设置为从 “eMMC” 启动。 Kan_Li_0-1753421616722.png 3. 按如下所示将 SE05X 与 FRDM-i.MX91 连接: Kan_Li_0-1753250411967.png 有线连接正常,或者您可以使用 #OM-SE050RPI 将它们连接在一起,如下所示。 Kan_Li_1-1753422316078.png 4. 将 FRDM-i.MX91 连接到 PC 主机。 将一根 C 型 USB 线缆连接到 FRDM-i.MX91 上的端口 P16,并插入个人电脑(作为主机终端)[2]。 将另一根 C 型 USB 线缆连接到端口 1 作为电源[2]。 Kan_Li_3-1753423476867.png 软件设置 1. 启用 I2C 接口 40 针扩展接口上的 I2C4(/dev/i2c-3) 默认未启用,因此我们需要在 u-boot 阶段将 DTB 切换为“imx91-11x11-frdm-8mic.dtb”。 u-boot=>setenv fdtfile imx91-11x11-frdm-8mic.dtb u-boot=>saveenv u-boot=>reset Kan_Li_0-1753324503160.png 然后,可使用以下命令检查主机与 SE 之间的连接情况。 i2cdetect -y -a -q 3 Kan_Li_1-1753324560234.png 构建 EdgeLock SE 即插即用中间件 1. 将即插即用中间件包复制或下载到 i.MX 文件系统中,并解压到某个文件夹。在本文中,该软件包指的是 04.07.00 版本。 unzip SE-PLUG-TRUST-MW_xx.xx.xx -d {folder name} 2. 构建 EdgeLock SE 即插即用中间件 cd /home/root/simw-top/scripts python3 create_cmake_projects.py cd ../simw-top_build/imx_native_se050_t1oi2c cmake -DPTMW_SMCOM=T1oI2C -DPTMW_Host=iMXLinux -DPTMW_HostCrypto=OPENSSL . cmake --build . make install ldconfig /usr/local/lib 3. 如果需要更改一些必需的 cmake 选项,并需要重新构建和安装一些库。我们可以使用以下方法: cd simw-top_build/imx_native_se050_t1oi2c cmake -DSE05X_Auth=UserID . cmake --build . 验证与 SSS 示例的集成 通过上述步骤,我们可能会得到一些说明 se05x 用法的示例。这些示例可用于验证集成情况,你可以在 build 文件夹/bin 中找到它们,如果你运行了“make install”命令,其中一些示例也可以在 /usr/local/bin 中找到,这样你就可以在文件系统中的任何位置执行它们。但由于使用的是 /dev/i2c-3 而非默认的 /dev/i2c-1,所以在运行任何演示程序之前,我们必须相应地设置端口。 export EX_SSS_BOOT_SSS_PORT=/dev/i2c-3 或者,我们可以在演示命令中指定端口: EX_SSS_BOOT_SSS_PORT=/dev/i2c-3 se05x_GetInfo Kan_Li_2-1753324723418.png 基于 Yocto 生成 SD 卡映像 完成SE050和FRDM-i.MX91开发板的硬件集成后,构建一个包含安全服务的完整操作系统镜像,是实现端到端可信系统的关键步骤。以下步骤提供了基于 Yocto Project 的定制 Linux 镜像构建方案。 1. 在有互联网连接的Linux电脑上安装Yocto[3]。 设置主机 sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping python3-git python3-jinja2 python3-subunit zstd liblz4-tool file locales libacl1 设置 repo 工具 $ mkdir ~/bin $ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo $ chmod a+x ~/bin/repo $ export PATH=~/bin:$PATH 设置 Yocto 项目 $ git config --global user.name "Your Name" $ git config --global user.email "Your Email" $ git config --list 下载 i.MX Linux Yocto 发行版 $ mkdir -p ~/projects/imx-yocto-bsp $ cd ~/projects/imx-yocto-bsp $ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.36-2.1.0.xml $ repo sync 2. 将 i.MX FRDM 层集成到 i.MX Yocto 项目中 $: cd ./sources $: git clone https://github.com/nxp-imx-support/meta-imx-frdm.git $: cd meta-imx-frdm $: git checkout imx-frdm-4.0 3. 为 Plug&Trust MW 添加自定义 Yocto 层 这个定制的 Yocto 层是 Plug&Trust 软件发行版的一部分(simw_top/scripts/ yocto/layers/meta-custom.tgz),必须将其复制并解压到上述创建的 sources 目录中。 cp /simw_top/scripts/yocto/layers/meta-custom.tgz ~/projects/imx-yocto-bsp/sources cd ~/projects/imx-yocto-bsp/sources tar xzvf meta-custom.tgz 将 se05x 配方(se05x_mw.bb)和源代码包(例如,SE050-PLUG-TRUST-MW-v04.07.00.zip)放入 Yocto 开发 PC 的现有 .../sources/meta-custom/recipes 目录中。 Yocto 开发 PC 上生成的 imx-yocto-bsp/sources/meta-custom 目录应如下所示: Kan_Li_0-1753344856894.png 相应地更新 build 文件夹中的 conf/bblayers.conf 和 conf/local.conf。 如何获取更新后的 se05x_mw.bb,local.conf 和 bblayers.conf 解压源代码包,并进入“SE-PLUG-TRUST-MW_04.07.00\simw-top\scripts\yocto\bitbake_script_and_conf_files”文件夹。然后,在该文件夹中使用 git 命令应用所附的补丁: $ git apply bitbake_script_and_conf_files.patch 4. 进入 Yocto 源代码的顶层目录,并执行以下命令来设置构建环境。 MACHINE=imx91frdm DISTRO=fsl-imx-xwayland source sources/meta-imx-frdm/tools/imx-frdm-setup.sh -b frdm-imx91 5. 要将 DTB 切换为启用“/dev/i2c-3”的“imx91-11x11-frdm-8mic.dtb”,请更新以下路径(“~projects/imx-yocto-bsp/sources/meta-imx-frdm/meta-imx-bsp/recipes-bsp/u-boot/u-boot-imx/”)中“0003-imx-imx91_frdm-Add-basic-board-support.patch”的补丁文件 Kan_Li_0-1753347276588.png 6. 执行 bitbake 命令以生成 SD 卡镜像。 $: bitbake imx-image-full 镜像文件可在“~/projects/imx-yocto-bsp/build_imx91frdm/tmp/deploy/images/imx91frdm/”中找到 Kan_Li_1-1753347276587.png [1]基于树莓派的 EdgeLock SE05x 快速入门指南 [2]FRDM-IMX91快速入门指南 [3] 使用 Yocto 构建镜像
查看全文
MakerFaire 上的炫酷科技 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 创客嘉年华,我们来了! 本周末我们将在圣马特奥分享一些超酷的项目,九月份我们将去纽约。 经过大量工作,我们的团队已经整合了一些基于 Kinetis mcus、i.MX 6 处理器、Freedom 开发平台构建的超酷项目,以及以UDOO 、 Riotboard.org为特色的热门社区项目,诺维娜、 CuBox-i 、 Wandboard.org 、Wunderbar 、ZumoBots 等。以下是我们计划的一些事情。 谁不喜欢闪烁、耀眼的灯光?PJRC的工作人员制作了一个 LED 显示屏(准确地说是 4320 个),全部由一块Teensy3.1板控制,该板大约有一块口香糖那么大。Paul 制作了一些特殊的 Teensyduino 草图库,利用 Kinetis K20 MCU 的直接内存访问引擎 (DMA) 功能来实现此演示中显示的视频和音频。Paul 不仅管理了困难的 LED 时序,而且还为 SDCard 接口的所有视频提供服务。我们是否提到过它也可以播放音频?! https://community.nxp.com/docs/DOC-100844 一旦您从标志上获得足够的光线,您就可以使用我们破解的 Wii-Fi(是的,它是 WII + WiFi)Nerf Swarmfire 测试您的技能。添加一些伺服器、一些重新布线和一个定制的 WiFi 遥控器,然后……立即享受乐趣!为了实现这一点,我们在 Nerf 本身(底座)上使用两个 FRDM-KL64F,并使用一个作为无线遥控器。基板处理来自遥控器的数据并相应地控制伺服器。 此视频已被删除。 (在 “我的视频” 中查看) 遥控板的行为有点像 Wii,用户必须移动遥控器,然后板载加速度计将其转换为运动,然后通过 WiFi 传递到基本控制器。最重要的是,我们只需要 3D 打印一个塑料控制器就可以将所有东西放进去。 https://community.nxp.com/docs/DOC-100845 这些是基于我的 Kinetis MCU 的演示。现在让我们来谈谈多媒体,也就是 i.MX 应用处理器。 当你到达该地区时,一定要和马里奥打个招呼。马里奥是一个自制的安卓机器人,拥有语音识别和Twitter连接功能。马里奥的心脏是一个运行 Android 4.3 的 UDOO Quad 加上一个 Arduino Motor Shield,它可以控制 2 个伺服器(马里奥的手臂)和 4 个转动 4 个轮子(马里奥的腿)的电机。为了展示他可爱的脸,马里奥有一个 7 英寸 LVDS 显示屏,而他的嘴是一个小扬声器。为了让他说话,我们利用了 Google API 的语音识别和文本转语音功能,赋予他生命。我们还使用了 Twitter API,通过 Twitter 控制马里奥,让他可以阅读推文,还可以通过简单的鸣叫向马里奥发送指令。
查看全文
The new TPPSDK (GD3000 driver) based on RTD for S32K3 Question As we know, the TPPSDK supports S32K144 MCU and various Kinetis MCUs to initialize GD3000 in NXP MC solutions. Because of the release of S32K3 and related SW RTD, it’s necessary to expand the capability of TPPSDK to support S32K3 MC based RTD LLD driver or MCAL driver. Unfortunately, the AA team will not maintain the TPPSDK anymore.  How could we configure the GD3000 chip for S32K3 platform? JoaquinL_0-1662367122679.png Answer I took some time to finish this work. Here I'd like to share you the The Expanded TPPSDK Based on S32K3 RTD that is suitable for S32K3 MC application. You can find the Application Note, the source code of new TPPSDK (GD3000 driver), two examples in the attachment. I hope these materials can help you get start with the expanded TPPSDK on S32K3.
查看全文
[FINISHED] UX design for MCUXpresso Configuration Tools [Title CZ/SK] UX design pre MCUXpresso Configuration Tools Assignment UX (User experience) design is one of the main deciding factors in the choice of a software application. Analyze UX of MCUXpresso Configuration Tools, specifically its user interface. Suggest specific user interface improvements. Create examples of suggested improvements. Compare the examples with the current solution. Test the examples with the help of app users. Assignment CZ/SK UX design aplikácie je jedným z kľúčových faktorov na základe ktorých sa užívateľ rozhoduje o používaní aplikácie. Analyzujte UX aplikácie MCUXpresso Configuration Tools so zameraním na GUI. Navrhnite konkrétne vylepšenia pre prácu s aplikáciou. Vytvorte ukážky navrhnutých vylepšení. Tieto ukážky porovnajte s existujúcim riešením. Vytvorené ukážky otestujte na užívateloch aplikácie. Language CZ/SK/EN   Leaders David Danaj   Contact University team NXP Semiconductors CZ  Apply by email  Finished
查看全文
i.MX51 EVK Changing Env Changing the storage for U-boot environment variables   U-Boot on Freescale BSP has a compiling option that allows you to choose the storage for environment variables.   1 - Extract the u-boot source using LTIB: ./ltib -m prep -p u-boot   2 - The source will be extracted to /rpm/BUILD/u-boot-2009.08   3 - On u-Boot source locate the i.MXEVK config file, /rpm/BUILD/u-boot-2009.08/include/configs/mx51_bbg.h   4 - To change the storage of variables environment to SD card, on this file, comment out CONFIG_FSL_ENV_IN_SF and define CONFIG_FSL_ENV_IN_MMC:   //#define CONFIG_FSL_ENV_IN_SF   #define CONFIG_FSL_ENV_IN_MMC 5 - Adjust CONFIG_ENV_SECT_SIZE and CONFIG_ENV_OFFSET accordingly. Recall that sd card read block size is 512B.   For example:   #define CONFIG_ENV_SECT_SIZE (256 * 512)   #define CONFIG_ENV_SIZE CONFIG_ENV_SECT_SIZE   #if defined(CONFIG_FSL_ENV_IN_MMC)   #define CONFIG_ENV_IS_IN_MMC 1 #define CONFIG_ENV_OFFSET (1023 * 512)   6 - Save the file.   7 - Recompile u-boot: ./ltib -m scbuild -p u-boot   8 - Your new compiled u-boot image will be saved at: /rpm/BUILD/u-boot-2009.08/u-boot.bin i.MX51
查看全文
第九届飞思卡尔杯智能赛车创意团队赛规则(1).pdf <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 附件最终规则适用于2014年飞思卡尔创新大赛规则 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 附件最终规则适用于2014年飞思卡尔创新大赛规则
查看全文
i.MX7ULP Register Programming Aids Important: If you have any questions or would like to report any issues with the DDR tools or supporting documents please create a support ticket in the i.MX community. Please note that any private messages or direct emails are not monitored and will not receive a response. These are detailed programming aids for the registers associated with DRAM initialization (LPDDR3 and LPDDR2). The last work sheet tab in the tool formats the register settings for use with the ARM DS5 debugger. It can also be used with the windows executable for the DDR Stress Test (note the removal of debugger specific commands in this tab). These programming aids were developed for internal NXP validation boards.   This tool serves as an aid to assist with programming the DDR interface of the i.MX 7ULP and is based on the DDR initialization scripts developed for NXP boards and no guarantees are made by this tool.   The following are some general notes regarding this tool: The default configuration for the tool is to enable bank interleaving. Refer to the "How To Use" tab in the tool as a starting point to use this tool. The tool can be configured for one of the two memory types supported by the i.MX 7ULP.  Nevertheless, two separate programming aids are provided based on the DRAM type: LPDDR3 and LPDDR2.  Therefore, you may use the tool pre-configured for your desired memory type as a starting point. Some of the CCM programming at the beginning of the DRAM initialization script (in the "DStream .ds file" tab) were automatically generated and in very few cases may involve writing to reserved bits, however, these writes to reserved bits are simply ignored. Note that in the "DStream .ds file" tab there are DS5 debugger specific commands that should be commented out or removed when using the DRAM initialization for non-debugger specific applications (like when porting to bootloaders). This tool may be updated on an as-needed basis for bug fixes or future improvements.  There is no schedule for aforementioned maintenance. For questions or additional assistance using this tool, please contact your local sales or FAE. i.MX7ULP
查看全文
尔湾:LPC800 MCU 技术概述:恩智浦®面向广泛的 8 位替代市场增长最快的产品组合 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 参加本次会议,了解如何利用 LPC84x MCU 系列的创新功能,该系列是计划于 2017 年发布的三个 LPC800 版本中的第一个。通过产品功能培训和演示,我们将展示这些低功耗、基于 ARM ® Cortex ® -M0+ 的 MCU 如何为当今的入门级 32 位微控制器市场提供 8 位简易性。我们希望您在本次课程结束后能够获得正确的培训和评估板,以便立即开始您自己的嵌入式开发。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 参加本次会议,了解如何利用 LPC84x MCU 系列的创新功能,该系列是计划于 2017 年发布的三个 LPC800 版本中的第一个。通过产品功能培训和演示,我们将展示这些低功耗、基于 ARM ® Cortex ® -M0+ 的 MCU 如何为当今的入门级 32 位微控制器市场提供 8 位简易性。我们希望您在本次课程结束后能够获得正确的培训和评估板,以便立即开始您自己的嵌入式开发。
查看全文
车身电子:实践研讨会:使用 MagniV 进行边缘节点开发 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将讨论 S12 MagniV 混合信号 MCU 如何帮助客户设计更紧凑、更具成本效益的电子控制单元。S12 MagniV 设备基于成熟的 S12 技术构建,可实现整个产品组合的软件和工具兼容性。S12 MagniV 产品组合将数字可编程性和高精度模拟完美结合,并配有一系列可扩展内存选项,从而简化了汽车设计。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将讨论 S12 MagniV 混合信号 MCU 如何帮助客户设计更紧凑、更具成本效益的电子控制单元。S12 MagniV 设备基于成熟的 S12 技术构建,可实现整个产品组合的软件和工具兼容性。S12 MagniV 产品组合将数字可编程性和高精度模拟完美结合,并配有一系列可扩展内存选项,从而简化了汽车设计。
查看全文
尤达里程碑奖金 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 大家好, 在此视频中,我们展示了我们作为奖励实现的 Android 应用程序。 UDOO Quad 上运行的虚拟助手程序也是一个 Web 服务器,它公开了一个非常基本的 REST API。该API用于远程控制助手。Android 应用程序使用 Google 的 STT API 将语音转换为文本,通过互联网将输入发送给 Yoda,Yoda 处理输入并返回答案,该答案使用 Google 的 TTS API 呈现。 之前视频中演示的所有插件都可以在 Android 应用程序中使用,因为手机只是另一个 I/O,所有处理仍然由在 UDOO 板上运行的应用程序完成。 有关实施、安装说明和其他规格的更多详细信息,请查看我们的 Git 存储库。 感谢观看, 尤达团队 (在 “我的视频” 中查看)
查看全文
扩展资源域控制器 xRDC <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32x 设备的扩展资源域控制器概述。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32x 设备的扩展资源域控制器概述。
查看全文
LPC804 Capacitive Touch Demo Testing Resport         In recently, NXP released a new sub-series: LPC80x which contains two kinds: LPC802 and LPC804 now, they have a variety of package types for choose and the LPC804 seems like the advanced version to LPC802. For details, please refer to these two articles: 《小巧‘零’珑的MCU:LPC80X面面观》 《LPC800系列选型指南》        Below are block diagrams of LPC802 and LPC804. We can find the difference easily after comparing them. Fig1 LPC802 system block diagram Fig2 LPC804 system block diagram        According to the above two figures, we can find that LPC804 has the capacitive touch interface, programmable logic unit (PLU), 10-bit DAC output, and an I2C interface. But these peripherals are not supported in the LPC802. In further, LPC804 has two times as much memory as LPC802 does.Especially, the capacitive touch interface provides hardware support for LPC804 to design the complex HMI implemented.        In the coming section, I'd like to illustrate the problem capacitive touch demo and share some experience to overcome it. Capacitive Touch Demo Testing 1. Evaluation board (OM40001) Fig3 LPCXpresso804 Develpment Kit        2. Demo code        CapTouch_5ch demo is from Code Bundle (supports Keil, IAR, and MCUXpresso), after reset, all the 5 LEDs would be On and Off one by one and flash together. Please do not touch the pads during this period. After all the LEDs are silent, touch any pad and the responding LED will be on until your finger moves away. Meanwhile, run the Freemaster project to monitor the sensing value in runtime. Fig4 Capacitive Touch Shield Fig5 FreeMASTER monitor the sensing value          3. Testing summary         In general, the testing result is not very good, for instance, when touching S4 and S3, LED D1~D5 may be lighted arbitrarily, even the S1 and S2 which have the best performance,  the responding LED usually be on when touching them, sometimes other LEDs would response the touching event.         Combining with the observation of FreeMaster, it can get the conclusion that the discrimination of these touchpads is not enough to distinguish each other.          4. Workaroud         According to the feedback from the AE co-worker, the discrimination performance of the touchpad is mainly determined by the PCB design and the power supply source. Obviously, the touchpad is impossible to be modified, so we should consider eliminating the power supply's noise to improve the performance.          I tried these three power source for supply. Using the USB port of the notebook, meanwhile, the notebook is supplied by 220 V, 50 Hz Using the USB port of the notebook Using mobile power       After several rounds of testing, it illustrates that demo code can work well when using mobile power to supply, as the mobile power is clean enough and the noise is the smallest.       Note: Slowing the FCLK can extend the scan period for a channel (more energy is released through YL for each recharge cycle), then increase the discriminability performance.  mobile power supply
查看全文
下一代功能安全架构 <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。
查看全文
澳洲大学挂科怎么办 澳洲大学挂科怎么办联系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
查看全文
FlexIO USB Video Camera Demo This demo shows how the FRDM-K82F board along with an OV7670 Camera module can be utilized to create a USB web camera application. The demo application software is delivered as part of the KSDK software enablement. The FS USB video class demonstration can deliver images to PCs or tablets. Features: USB Video device class demonstration application included in Kinetis SDK Easy connection to PC or tablet  display and process video captured from the device FlexIO camera driver utilized to interface to OV7670 camera module _______________________________________________________________________________________________________ Featured NXP Products: ARM Cortex-M4 Cores|Kinetis K8x MCUs|NXP AN5275: Using FlexiO for Parallel Camera Interface AN5280: Using Kinetis FlexIO to drive a Graphical LCD _______________________________________________________________________________________________________ Mobile
查看全文
示例 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 的安全元素。
查看全文