The RT685-AUD-EVK allowed me to validate my custom frontend circuitry and get started on other critical DSP software development. I was able to connect the piezoelectric saddle pickups on my engineering guitar into the test bed via the custom daughtercard. From here I can focus on firmware in the MCU and DSP cores in the RT685.
NXP's free UI design tool for the open source LVGL graphics library continues to add great new features and capabilities. GUI Guider 1.3.0 was released on January 24th 2022 and includes exciting new widgets, more host platform support, Keil project output and Micropython.
NXP has now introduced MCU-Link Pro - the second incarnation of the MCU-Link debug probe architecture, adding several powerful capabilities and features to build on the entry level MCU-Link standalone model. This includes power/energy measurement, USB bridging and a J-Link firmware option.
An interactive tutorial on how to create your own MATLAB Simulink temperature sensor application by applying the model-based design approach, how to configure and use the i.MXRT1060 EVK using NXP MCUXpresso, a thermistor module and the IMXRT Toolbox.
In my previous twoarticles, 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.
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.
Please find attached a document detailing various features related to using the IMXRT1170-EVK evaluation board with MCUXpresso IDE v11.4.x and SDK v2.10.0, including details of multicore debugging and how to enable SWO trace on this MCU.
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.
The i.MX RT series bridges the simplicity of MCUs with the complexity of applications processors into a hybrid portfolio offering ease-of-use designed to address the growing consumer demand for enhanced user experiences. Offering high-performance – up to 1Ghz – modernized HMI capabilities, expanded memory options, and advanced security, the i.MX RT series can help you push the boundaries of what is possible in the IoT – even on price-conscious designs. The possibilities are endless: Imagine using the i.MX RT in clothing technology to help manage airflow; and maybe that device interacts with others such as smartwatches to actively cool the body. Similarly, imagine adding IoT capabilities to gaming devices for an enhanced gaming experience.
This project was implemented by Ioana CULIC (firstname.lastname@example.org), PhD candidate at the Politehnica University of Bucharest, and Alexandru VOCHESCU (email@example.com) as part of his bachelor thesis at the Politehnica University of Bucharest. All the contributions are open source and are part of the Tock project, available on github.
This is Mini Drum Pad build in withIMXRT1015. Also it has AFE shield board which is used for capsense buttons.
IMX RT is, using SAI to play the audio file at 16KHZ. I have created 12 samples (.wav file) and the raw data is stored in the music file. Based on the capsense button press triggering the sound effect.
Speaker I used is from Boat, it has internal battery so only thing required is to feed the Aux input from IMXRT EVK.
I felt that, button sense over I2C bit slow due to that having the limitation of playing the music as faster. Anyway its just demonstration of my concept.
The purpose of this Blog is to assist new users of the AppWizard to create and run their first project. The AppWizard is a tool for creating complete and ready-to-use emWin applications. The tool makes it very easy to build an application, manage resources and even define the application’s behavior.
Managing resources of an application is also made incredibly easy since the user simply has to add their resources to the project. All of the rest is done by the AppWizard, this means the user doesn’t have to fiddle around with dozens of resource files anymore.
The next generation of machine interfaces is here. As embedded technology evolves, NXP continues to innovate with technologies like cloud-based/local voice control and face recognition for secure access/authentication. Resources for these technologies are abundant, but how can NXP continue to offer an efficient, easy, and quick path to development for people who do not want to reinvent the wheel? How do we make it easier to innovate?
Enter NXP’s turnkey, production-grade IoT ML/AI edge computing solutions. NXP provides the option of an integrated approach to development, with solutions that include out-of-box hardware, software, schematics, layouts, documentation, certifications, and BOMs to enable developers to add sensor-based capabilities into their design easily and quickly. The advantage is a faster time to market with the ability to leverage popular services like the Alexa Voice Service for AWS IoT Core Integration or compute completely offline when it comes to face recognition, for instance.
A lot of discussion recently has been around the i.MX RT1010 crossover MCU -and why not? It is the latest and greatest achievement for high-end crossover MCUs. But, you probably noticed that the i.MX RT1010 MCU left off some features in order to keep the cost low. So, what if you need a high performance MCU with all the bells and whistles?
Today I conclude my countdown of top reasons to use i.MX RT1010, and I wanted to end the blog series in the same way that it began – by talking about how to get started. It is has been 2 weeks since my first post, so hopefully by now you have found the $10.10 in your couch cushion to order your i.MX RT1010 EVK. Maybe you even already have the EVK on your desk and followed the instructions on the Getting Started webpage which leads you to download the software and tools. But what is MCUXpresso and how much does it cost?
Listen up everyone. We are winding down the countdown and my blog today is about audio. Many consumer products and embedded devices support various digital audio functions, and more and more engineers are looking for the MCU to support these functions, rather than needing to add a DSP or other dedicated solution. The good news is that many MCUs now have the capabilities to support these basic audio tasks. But how do you choose an MCU that will give your product the price, performance, and design flexibility you need?
So you want to add a display to your product? You look at the i.MX RT series table and see that the i.MX RT1010 device does not have an LCD interface, so you immediately write it off. Not so fast! Did you know that you can add a display to your i.MX RT1010 design through the I2C module? What’s great about the i.MX RT1010 is that we didn’t skimp on peripherals to hit that $1 price point. Even the pin muxing takes into account maximum usability for a variety of applications. But say you are working on a thermostat application and need the I2C module to connect to a variety of sensors instead. Based on yesterday’s blog, hopefully you immediately think of the FlexIO module.
Say for example, you are working on your industrial application using the i.MX RT1010 MCU and have everything designed out. You are using two UARTs for sensor interfaces, one UART for camera, and the fourth UART will be used for development and future debug. Then, your product marketer comes by and asks you to add Bluetooth to the product.
What can you do? The i.MX RT1010 only supports 4 UARTs. Do you move to an i.MX RT1050 MCU since it has 8 UARTs? Do you add another external UART to your design?
All engineers – and most anyone – love to make things spin, right? That explains the revenue made on those fidget spinners. The inventor is a genius! OK ok … now back to MCUs … the i.MX RT MCU motor control demos are some of the most highly viewed demos. So what makes the i.MX RT1010 device ideal for motor control applications? Is it the FlexPWM? The ADC? Or just the raw performance of this 500 MHz MCU? The answer – all of the above. The i.MX RT1010 MCU is an ideal solution for a single motor and here’s why
On what could be perceived as a low-cost MCU, it is nice to see that security was not compromised on the i.MX RT1010 device. In fact, the i.MX RT1010 MCU has the same security block that exists on many of the other i.MX RT products.