USL：https://community.nxp.com/t5/MCUs-Community-Articles/LPC5500-MCU-Series-There-s-a-lot-under-the-hood...

由 Eli Hughes于 2020-01-21 创建的文档

在一生的大部分时间里，我热衷于编程和嵌入式微控制器。在我的职业生涯中，我积累了许多不同体系结构的经验，包括一些专门用于特定应用程序的体系结构。即使在当前专用设备市场多样化的情况下，我仍然坚持寻找最有趣的通用微控制器市场。我认为这源于我对计算机最初的热爱。这可以追溯到七年级，当我们使用Apple IIe计算机学习“计算机素养”时。在课程中，学生们学习了如何使用BASIC语言编写程序。项目涵盖了从简单图形、打印到游戏的所有内容。与此同时，我了解到，我那些玩Nintendo™的其他7年级同学的热情与计算机素养的活动有关。通过一本流行的游戏杂志，我发现为任天堂供电的芯片是为学校计算机供电的设备，即古老的“ 6502”。那是顿悟的时刻。如果CPU既可以是游戏系统又可以是文字处理器，那么它真的可以*做我想做的任何事情*。不久之后，我便开始挖掘6502的复杂细节来为我的作品提供动力。6502是我的第一个通用CPU。

URL : https://community.nxp.com/community/general-purpose

mcus/k32lseriesmcus/blog/2019/12/05/k32-l3-mcus-energy-efficiency

with-advanced-security-and-physical-protection

最后更新：12-05-2019 更新：Omar Cruz

PyeIQ is written on top of eIQ™ ML Software Development Environment and provides a set of Python classes allowing the user to run Machine Learning applications in a simplified and efficiently way without spending time on cross-compilations, deployments or reading extensive guides.

Now PyeIQ 3.0.x release is announced. This release is based on i.MX Linux BSP 5.4.70_2.3.0 & 5.4.70_2.3.2(8QM, 8M Plus) and can also work on i.MX Linux BSP 5.10.9_1.0.0 & 5.10.35_2.0.0 & 5.10.52_2.1.0. And also, in latest PyeIQ 3.1.0 release, BSP 5.10.72_2.2.0 is also added into supported list.

This article is a simple guide for users. For further questions, please post a comment on eIQ Community or just below this article.

1.     Debugging Packet Loss Issue

1.1 Frame Manager(FMan) Introduction

1.2 Frame Manager Buffer Manager Interface (BMI) Rx Port Statistics Counters

1.3 Linux Sysfs Support for Fman Rx Port Statistics

2.     Queue Manager(Qman) Enqueue Rejections

2.1 Reasons for an Enqueue Rejection

2.2 Frame Queue Descriptor

2.3 Qman Debugfs

2.4 Buffer Manager (BMan) Debugfs

In my previous two articles,  we examined the core components to an RT600 hardware design using the code name “Super-Monkey”.   The objective of the Super-Monkey project to produce minimal configuration design example using RT685 audio crossover MCU that would support my real-time audio processing projects.   There is quite a bit IO available on the RT685, but I chose to constrain my design to the most common functions for real-time audio.   My applications generally use professional, “flagship quality” audio codecs for musical instrument signal processing.   Using this as a guide, the process of coming up with a minimal IO complement was simplified.  It is time to now time reveal the Super-Monkey design!

This article will continue detailing a minimal configuration design that uses an i.MX RT685 crossover MCU.    In the first article of this hardware design series, I introduced the power supply architecture of the RT600 series and illustrated some of the package/PCB layout features of the VFBGA176 package.       I also introduced some of the specs I am working towards for the “Super-Monkey” module and will power some of my future real-time audio processing projects.

As a real-world example, I this article is part one of several articles that will step through a basic RT600 hardware design and bring-up.   I find this to be a very useful exercise as high-end MCU’s can be overwhelming, especially to those coming from a traditional MCU background.   The goal here is to develop a simple “minimal configuration” example and build it for a demonstration.   

The Local Interconnect Network (LIN) was developed as a complementally bus standard to the Controller Area Network (CAN bus) to address the need for a cost-efficient network for lower performance devices within the vehicle.  While the CAN network was already in place within vehicles, its high bandwidth and advanced error detection capabilities were overkill (and thus, cost-prohibitive) for lower performance applications such as seat and window controllers.

In Part 1 of our introduction to the RT600 crossover MCU,  we examined the RT600 CPU/DSP core complex and its unique system memory architecture.   In part 2, we will put a spotlight on some other unique peripheral features that make the RT600 standout as a high-performance audio crossover MCU.

This article is the first part of a two part series focusing in on one of the newer members of the i.MX RT crossover family: the RT600.     The RT600 crossover MCUs are focused on real-time number crunching applications such as audio, sensor fusion and machine learning.     

CAN FD is an extension to the Classic CAN protocol that was developed to meet the needs of modern vehicles wherever-increasing numbers of embedded electronics are transmitting ever-increasing amounts of control and diagnostic data.  Because the original CAN specification has a maximum bandwidth limitation of 1 Mbps, data-dense activities like ECU flashing and advanced driver assistance systems (ADAS) ADAS applications were being impeded, forcing automotive manufacturers to add multiple CAN networks into newer vehicles.

We are pleased to announce that MCUXpresso Secure Provisioning Tool v3 is now available.

Where to find 3d printed case designs for MCU-Link.

This demo introduces the secondary boot of i.MX8QXP. 

This feature is very useful for such as OTA, rolling back. 

One aspect of the baseline family of parts in the LPC55 series is having options that deliver a good balance of simplicity and flexibility.     The simplicity/flexibility balance is important in many industrial applications.    Combining standard industrial communication peripherals such as RS-485 capable UARTs and CAN-FD  with a solid CPU foundation means that designers can implement a wide range of products in the industrial space.

Some customer cases need hardware partition and the GPIO need to be allocated by bank.

It causes resource tensive. And some time, one GPIO bank assigned to the M4 side 32 bits of one bank are more than enough. And some customer cases need to use 1 or 2 bit to as board identification for the A core side. Because of the hardware partition, A core could not directly access the M4 partition resource.

The example is to change the i.MX8QXP MEK debug uart(lpuart0) to the base board(lpuart2).

The lpuart2 is J37 on base board.

uart2-linux-uart2_L5.4.70_2.3.0.diff, uart2-u-boot-method1_L5.4.70_2.3.0.diff and uart2-u-boot-method2_L5.4.70_2.3.0.diff are the patches. 

The NPU capability lies in the “sweet spot” for performance to enable real time response for common AI/ML problems. Combined with the video and vision co-processing capabilities, the i.MX 8M Plus will be the standard bearer for Edge ML/AI implementations

Switch i.MX8MM debug port is not simple like i.MX6. Just change the bootargs.The changes include atf(Key changes), u-boot, Linux and systemd.

Please find attached a document detailing various features related to using the IMXRT1170-EVK(B) evaluation board with MCUXpresso IDE v11.x.x and SDK v2.x.x, including details of multicore debugging and how to enable SWO trace on this MCU.

New updates to the MCUXpresso suite of software and tools are now available. These updates include support for NXP’s general purpose, crossover and Bluetooth^®-enabled Arm^® Cortex^®-M-based MCUs.

Communication between these subsystems is critical to ensure the reliability and safety demanded in the automotive market.  The Controller Area Network (CAN bus) is a message-based communication network standard that allows ECUs to communicate within a vehicle without the use of dedicated analog signal wires. 

We are pleased to announce that Config Tools for i.MX Application Processors v9 are now available.

MCUXpresso Config Tools v9 release announcement.

We are pleased to announce that MCUXpresso Secure Provisioning Tool v2.1 is now available.

MCUXpresso Secure Provisioning Tool is a graphical user interface (GUI) tool covering the secure boot
process, aimed primarily at microcontroller customers. It provides unified GUI front-end over existing
command-line tools - FlashLoader, elftosb, blhost, cst.

I proclaim that the digital “on-demand” manufacturing revolution is here! It was 1999 when I first experienced quick turn, “online” PCB fabrication. Since then, PCB fabrication services have become plentiful, inexpensive, and accessible to engineers of all levels. Online automation of full turnkey assembly is the next logical step, and I see it the future of PCB assemblies. I often say it is a great time to be alive if you are in the business of embedded systems. It has never been easier to tap into global manufacturing resources to accelerate product development.

I recently ran into a scenario where we needed to quickly adapt one of our products to a new customer application. It was a situation where we needed to be agile in our response. In this scenario, I needed to plumb a particular commercial off-the-shelf (COTS) temperature sensor into our existing cellular gateway (which only had specific digital-only ports for another application). The prototype would end up being put in a “smart” cable assembly that would adapt a new sensor into our existing system to demonstrate the concept. A small “translator” PCB with some “brains” would have to be designed to link up the sensor to our existing hardware/software platform.

I was quite impressed with how quickly I could get LVGL up and running on the Mini-Monkey.     If you are looking at implementing embedded graphics on the LPC55S69 or another NXP part, LVGL should be on your short list for evaluation.