Multi Source Translation Content

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Multi Source Translation Content

Discussions

Sort by:
GPIO Introduction: How to Read the Pins of a Microcontroller (MCX A153) and Control an LED (Japanese Blog) table of contents Introduction Understanding the pin configuration of the MCX A153 microcontroller Settings for using GPIO Check the relationship between the pins and the board (FRDM-MCXA153). Demonstration: Perform GPIO settings and experience LED control. Bonus: Understanding the "on/off" of LEDs Bonus – What happens if you connect two LEDs in parallel?   Introduction As a beginner in embedded systems development, I began learning about GPIO after receiving a request to write an article about it. This article is a record of what I learned and the insights I gained through trial and error while trying to light up a single LED. This article explains how to use GPIO (General Purpose Input/Output), one of the most basic peripherals in microcontroller development. GPIO is the foundation of embedded systems for connecting microcontrollers to external circuits, enabling functions such as turning on LEDs, reading the state of switches, and receiving signals from sensors. On the other hand, in actual microcontroller development, "using GPIO" doesn't simply mean writing a program. Microcontrollers have numerous pins, and each pin is assigned functions other than GPIO, such as timers and communication interfaces. Therefore, To use GPIO, you need to understand the pin assignments and functions from the datasheet. PinMUX (pin multiplex) settings for assigning GPIO to pins Input/Output Direction Settings This needs to be done properly. This time, using the FRDM-MCXA153 as an example, we will examine the pin configuration of the MCX A153 and the mechanism of PinMUX, configure GPIO settings using Pins Tool, and finally demonstrate blinking LEDs connected to a breadboard.   Understanding the pin configuration of the MCX A153 microcontroller The FRDM-MCXA153 is equipped with a microcontroller with the model number MCXA153VLH. This microcontroller uses an LQFP 64 package and has a total of 64 pins. Of these, 52 are available as GPIOs. The remaining pins consist of power terminals (VDD/VSS), USB terminals, and analog-only terminals, which cannot be used as GPIOs. However, even though it has "52 GPIOs," this doesn't mean that 52 pins are dedicated to GPIO. Many of the pins available for GPIO use are shared with peripheral functions such as UART, SPI, I²C, and timers. Therefore, to actually use them as GPIOs, you need to use the PinMUX function to configure those pins to function as GPIOs. Let's check the pin configuration of the MCX A153 from the datasheet . A list of functions that can be assigned to each pin is provided starting on page 54. For example, looking at the "Pinmux Assignment" for Pin Name: P1_8, there are six possible functions. GPIO is assigned to "ALT0 - P1_8". Other assignments include "ALT2 - LPUART1_RXD" which means it will be used as the UART receive terminal (RXD), and "ALT3 - LPI2C0_SDA" which means it will be used as the I²C data line (SDA). As you can see, a single pin can be assigned to multiple functions, including not only GPIO but also UART, I²C, and timers.   Settings for using GPIO 1. Select pin function (PinMUX) As confirmed in the previous section, P1_8 has several potential functions, including GPIO, UART, and I²C. However, the same pin cannot be used as both GPIO and UART simultaneously. Therefore, typical microcontrollers are equipped with a mechanism called PinMUX. PinMUX is like a toggle switch for connecting a single physical pin to an internal peripheral. For example, P1_8 had six potential connection destinations. By selecting GPIO using PinMUX, P1_8 becomes available for use as a GPIO pin. 2. Set the electrical characteristics of the pins. Pins can be configured not only for their function but also for their electrical behavior. Typical settings include: • Pull-up • Pull-down Drive Strength Open Drain These are some examples. For instance, pull-up resistors are often enabled for switch inputs, and the drive strength may be adjusted when driving LEDs or high-speed signals. Even when used as GPIO, it is important to make appropriate electrical settings according to the application. This article will omit a detailed explanation of these electrical characteristics. 3. Set the input/output direction of the GPIO. The final step is determining the direction in which the signal flows. GPIO has two main operating modes. • Input – Receives signals from the outside • Output – Sends signals to the outside What exactly is happening inside the microcontroller when it comes to Input and Output? The MCX A153 is a microcontroller that operates at 3.3V. Therefore, the GPIO pins basically handle two states: Low (approximately 0V) and High (approximately 3.3V).The A153 has an operating voltage range of 1.71V to 3.6V, and 3.3V is used for the FRDM board. GPIO output values Pin voltage Low (0) Approximately 0V High (1) Approximately 3.3V For example, if you set a specific GPIO pin to Output and connect an external LED, setting it to High (approximately 3.3V) creates a potential difference between the GPIO and GND, allowing current to flow through the LED. Setting it to Low (approximately 0V) eliminates the potential difference with GND, so no current flows. In other words, the "blinking" of the LED is caused by repeatedly switching the voltage of the GPIO pin between High (1) and Low (0), alternating between blinking and being off. On the other hand, in Input mode, the microcontroller monitors the state of the GPIO pins. For example, if approximately 3.3V is input from an external circuit, it is recognized as High (1), and if approximately 0V is input, it is recognized as Low (0). The pin function selection, electrical characteristic settings, and input/output settings described above can all be configured via a GUI using the Pins Tool (which is included in NXP's free Config Tools).   Check the relationship between the pins and the board (FRDM-MCXA153). So far, we've learned that in order to use GPIO, you need to configure PinMUX settings and input/output direction settings. Next, let's confirm where the MCU pins are connected on the FRDM-MCXA153 board, keeping in mind the demonstration we'll be performing. Check the schematics and confirm where pin "P1_8", which was used as an example in the previous chapter, is routed. Looking at page 8 of the circuit diagram, we can see that P1_8 is connected to D18 of Arduino header J2 on the FRDM-MCXA153. FRDM-MCXA153 Schematics So, where is D18 on the Arduino header J2? Next, let's check the Board User Manual. FRDM-MCXA153 Board User Manual Page 6 contains a diagram of the connectors mounted on the board, which allowed me to identify the location of D18 on the Arduino header J2. For this learning exercise, we will connect an external LED via a breadboard using the D18 pin. However, if you do not have a breadboard or LED, you can use the RGB LED mounted on the FRDM-MCXA153 board. However, there is one point to note. When using the RGB LED on the board, the anode (+) of the LED is connected to VDD_BOARD (3.3V), and the cathode (-) is connected to GPIO. Therefore, unlike the externally connected LED mentioned earlier, setting GPIO to High (1) will also bring the GPIO voltage to approximately 3.3V, and the potential difference across the LED will almost disappear, causing the LED to turn off. On the other hand, setting GPIO to Low (0) creates a potential difference across the LED, causing current to flow and the LED to light up. When you check each pin in the circuit diagram... P3_12 is a red LED P3_13 is a green LED P3_0 is a blue LED It supports these features. By configuring these PinMUX settings and input/output settings, you can also verify the operation using the LEDs on the board. In this way, you can use the circuit diagram and the Board User Manual to check where the physical pins inside the microcontroller are connected on the board.   Demonstration: Perform GPIO settings and experience LED control. In this chapter, we will use the Pins Tool in MCUXpresso Config Tools to configure GPIO and control an externally connected LED on a breadboard. Equipment used in the demonstration: FRDM-MCXA153 Breadboard LED • Resistors and jumper wires This demonstration will assume that you have already installed the MCUXpresso SDK and Config Tools in your VS Code environment. *If you have not yet installed the MCUXpresso SDK and Config Tools, please refer to this blog post. MCUXpresso Config Tools: How to Use the Pins Tool (Japanese Blog) Note: While the blog post describes installing the SDK for FRDM-MCXN947, please install the SDK for FRDM-MCXA153 in this article. I had a red LED and a green LED on hand, but I didn't know the part numbers, so I'll start by trying to light up the red LED. I had a 390Ω resistor. The forward voltage (Vf) of a red LED is generally 1.8~2.2V, so I'll assume it's 2.0V and calculate the current flowing through the LED. The microcontroller's operating voltage is 3.3V. VfUsing 2.0V and a 390Ω resistor, the current value can be calculated using Ohm's law as follows. Note that LEDs have a specified maximum forward current (Ifmax), which is said to be 20mA for many general-purpose LEDs. Be careful with the resistance value, as currents exceeding 20mA may cause damage. Furthermore, GPIO pins also have limitations on the current they can output. According to the datasheet, the MCX A153's electrical characteristics during normal operation are specified based on 4mA (6mA for High Drive pins). Therefore, when directly lighting an LED using a GPIO pin, you need to select a resistor value that takes into account not only the LED's current limit but also the GPIO's current limit. Board and breadboard wiring First, we'll do the wiring. On the FRDM board, we will use "D18" and "14 GND" on the Arduino header J2 that we identified earlier . The following diagram is based on the Board User Manual. FRDM-MCXA153 Board User Manual Please refer to the following video for wiring instructions. (function() { var wrapper = document.getElementById('lia-vid-6405195304112w960h540r888'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (Show My Videos) Importing sample code Next, we will proceed to import the sample code from the FRDM-MCXA153 SDK. Click "Import Example From Repository" in the panel on the left. In the tabs displayed on the right, select the imported FRDM-MCXA153 SDK under "Repository" and select FRDM-MCXA153 under "Board". The template used is "driver_examples/gpio/gpio_led_output". Select your desired Toolchain and click "Import". Once the import is complete, it will be added to the Projects section in the left-hand panel. Check the source code gpio_led_output.c. This time, we want to configure GPIO input/output settings using Pins Tool, so we will remove the GPIO output setting code enclosed in the red box from the source code. Configure GPIO settings using Pins Tool. Next, open Config Tools. Right-click on the Project and select "Open with MCUXpresso Config Tools". After a short wait, Config Tools will launch. Once Config Tools opens, first select Pins from Overview in the right-hand panel. The Pins Tool is now open. Enable pin P1_8. Clicking on P1_8 will open another window as shown in the image below. Find "GPIO1:GPIO,8(P1_8)" in this window and check the box next to it. When you check the box, the following window will appear, but you can close it by clicking No. Once you've completed these steps, P1_8 will be added to the Routing Details at the bottom of the Pins Tool. Next, change the GPIO input/output settings as follows. Connect pin #38 (P3_12) from Output to Not Specified, and pin #2 (P1_8) from Not Specified to Output. An error will occur in the GPIO initial state of #38, so please change it from Logical 0 to n/a. Once you've completed these steps, you can rewrite the sample code. First, click Update Code in the upper left corner of the Config Tools screen. A window will then appear. Here you can review the code changes as needed. Files that have been modified will have "change" written next to them. When you return to VS Code, you will see three checkboxes at the top of the screen. Make sure they are checked and click OK. After a short while, the changes to the source code will be completed. Next, we will change the target of GPIO control in the source code gpio_led_output.c. When you open gpio_led_output.c, The following is stated:   while (1) { delay(); GPIO_PortToggle(BOARD_LED_GPIO, 1u << BOARD_LED_GPIO_PIN); } Modify the contents of GPIO_PinInit() and GPIO_PortToggle() as follows: Here, P1_8 is specified as the control target, and each time the function is called, the state of P1_8 switches between High (1) and Low (0). while (1) { delay(); GPIO_PortToggle(GPIO1, 1u << 8); } Further details: GPIO pins are represented in the format Px_y, where x is the GPIO port number and y represents the bit position within that port. For example, P1_8 means "bit 8 of GPIO port 1". In the code GPIO_PortToggle(GPIO1, 1U << 8); In, GPIO1 1U << 8 represents GPIO port 1, is a bitmask where only the 8th bit is set to 1. 1U << 8 ↓ 0000 0001 0000 0000 (2進数) This allows you to invert (switch between High and Low) only the 8th bit in GPIO port 1. Connect the PC to the FRDM-MCXA153. Debugging (build, write, and run the application). Once the debugging process is complete, the program will have stopped at the breakpoint, so click the "|▶" icon at the top of the screen. The LED will start blinking. (function() { var wrapper = document.getElementById('lia-vid-6404528566112w304h540r105'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (Show My Videos) Bonus – Understanding LED "on/off" By the way, when does this LED light up, based on whether the GPIO outputs High (1) or Low (0)? Earlier I mentioned that it lights up when High (1) is output, but let's verify if that's true. The following is the code we used earlier. The `while(1)` statement implies an infinite loop, repeatedly executing the code within the curly braces {}. Additionally, delay() is a function for waiting for a certain period of time. GPIO_PortToggle() is a GPIO control function, so it inverts High (1) and Low (0). while (1) { delay(); GPIO_PortToggle(GPIO1, 1u<<8); } } However, this code doesn't tell us whether the LED is lit when it's High (1) or Low (0). Therefore, we use a different function, GPIO_PinWrite(), to explicitly control the state of the GPIO. Specifically, the code will be changed to wait for one delay() call while in a High (1) state, and then wait for five delay() calls while in a Low (0) state. This should make the LED stay off for a longer period of time. while (1) { GPIO_PinWrite (GPIO1,8U ,1); delay(); GPIO_PinWrite(GPIO1,8U ,0); delay(); delay(); delay(); delay(); delay(); } Run the debug and click the "|▶" icon at the top of the screen. (function() { var wrapper = document.getElementById('lia-vid-6404528052112w304h540r114'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (Show My Videos) As intended, the LEDs were turned off for a longer period. This allowed us to verify that the LED outputs High (1) when it is lit and Low (0) when it is off. To recap, when the GPIO goes high (1), the voltage at P1_8, which is set as the GPIO pin, becomes approximately 3.3V. A potential difference is created between this voltage and GND, causing current to flow through the resistor and the LED. At this time, a forward voltage (approximately 2.0V) is applied across the LED, and the remaining approximately 1.3V is applied across the resistor. As a result, the LED lights up. On the other hand, when GPIO goes low (0), the voltage at P1_8 becomes approximately 0V. Since there is no potential difference between the GPIO pin and GND, no current flows, and the LED turns off. If you think having a lot of `delay()` functions looks ugly, you can also use loop functions. while (1) { GPIO_PinWrite(GPIO1, 8U, 1); delay(); GPIO_PinWrite(GPIO1, 8U, 0); for (int i = 0; i < 5; i++) { delay(); } } Bonus – What happens if you connect two LEDs in parallel? I tried connecting a green LED I had on hand in parallel with a red LED. Since the forward voltage (Vf) of a green LED is generally 2.0 to 2.2V, I assumed it to be 2.0V, similar to the red LED, and built the following circuit. Since there was no need to change the pin settings, I debugged using the same code as before, and the red LED blinked, but the green LED did not. Why is that? (function() { var wrapper = document.getElementById('lia-vid-6404530194112w304h540r514'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (Show My Videos) LEDs have the characteristic that current starts flowing rapidly when the forward voltage (Vf) is exceeded. Therefore, if a red LED and a green LED are simply connected in parallel, the current will concentrate on the LED with the lower Vf, and the other LED may hardly light up at all. In this case, the Vf of the red LED is lower than that of the green LED, so the current is concentrated on the red LED. When I actually measured the voltage across the LEDs with a tester, the red LED was 1.765V and the green LED was 1.766V. At this voltage, the red LED can light up, but the green LED does not receive enough voltage to generate sufficient current. As a result, the red LED lights up, but the green LED does not light up because almost no current flows through it. As shown above, simply connecting different types of LEDs in parallel can cause significant bias in current flow due to even small differences in forward voltage (Vf). Therefore, when connecting LEDs in parallel, it is common practice to install a current-limiting resistor for each LED. When adding resistors, you need to consider the GPIO current limit. If you simply add one more 390Ω resistor as we've been using and calculate the current, the calculated current applied to the GPIO will exceed 6mA. Therefore, to ensure the total current does not exceed 4mA, we connected two 680Ω resistors and built the following circuit. When I debugged the same code again, both the red and green LEDs lit up. (function() { var wrapper = document.getElementById('lia-vid-6405719291112w304h540r698'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (Show My Videos) When the voltage across the LEDs was measured, the red LED was 1.750V and the green LED was 1.906V. By adding a resistor to each LED, the appropriate current was able to flow through each LED. In this article, we've explained the "problems" and "stumbling blocks" encountered by a beginner in embedded development, from how to interpret various documents and use Config Tools to the operating principles of LEDs. We hope this will be helpful for those attempting to blink an LED for the first time using an NXP microcontroller. =========================​ We are currently unable to respond to comments left in the " Comment " section of this post . We apologize for the inconvenience, but please refer to " Technical Questions to NXP - How to Contact Us ( Japanese Blog ) " when making inquiries . (If you are already an NXP distributor or have a relationship with NXP , you may ask your representative directly.) This article explains how to use GPIO (General Purpose Input/Output), one of the most basic peripherals in microcontroller development, using the blinking of an LED as an example. GPIO is one of the first peripherals that many microcontroller developers learn about. Many people want to use GPIO to light up an LED, but they may not know how to read the datasheet or how to configure the pins. This article explains the basics of GPIO using the FRDM-MCXA153, aimed at beginners in microcontroller development. We will learn to read pin information from the datasheet and circuit diagram, configure settings using Pins Tool, and finally experience controlling an external LED. (Estimated time: 15 minutes) *Assuming the development environment is already installed. MCUXpresso MCUXpresso Configuration Tools MCUXpresso IDE MCUXpresso SDK MCX Japanese Blog
View full article
Example FRMD-A-S32K344 FlexCAN TX_RX FreeRTOS S32DS36 RTD600 * ================================================================================================= * Detailed Description: * * This example demonstrates Classical CAN and CAN FD reception and transmission using * interrupt-driven Message Buffers and FreeRTOS. * * FlexCAN0 is configured in Normal mode. MB0 receives standard-ID frames and MB1 receives * extended-ID frames. The FlexCAN callback copies every received frame into a FreeRTOS queue * and immediately rearms the corresponding RX Message Buffer. * * A dedicated FreeRTOS task waits for frames in the queue and echoes them through CAN TX MB2. * The transmitted frame preserves the received identifier type, identifier, payload length, * payload, CAN FD EDL state, and BRS state. The user LED is toggled after a transmit request * is accepted by the driver. * * Note: * FreeRTOS API functions such as xQueueSendFromISR() are used from the FlexCAN callback. * Therefore, the FlexCAN interrupt priority must comply with the FreeRTOS interrupt-priority * requirements defined by configMAX_SYSCALL_INTERRUPT_PRIORITY. * * ================================================================================================= * Test HW: FRDM-A-S32K344 (SCH-94921 / SPF-94921 Rev. C) * MCU: S32K344 * Compiler: S32DS 3.6.x * RTD release: S32K3_RTD_6_0_0_D2506_ASR_REL_4_7_REV_0000_20250610 * Debugger: On-Board Debugger * Target: Internal_FLASH * Communication: Classical CAN / CAN FD, STD and EXT ID, optional BRS * =================================================================================================
View full article
Example S32K344 LPSPI LCD-PAR-S035 FRDM S32DS 3.6.6 RTD 7.0.1 * Detailed Description: * * This project provides a minimal bring-up and reference example for the LCD-PAR-S035 * display and GT911 capacitive touchscreen on the S32K344. It includes standalone LCD * and touchscreen diagnostic modes, together with an LVGL demonstration mode. * * The display is controlled through the LPSPI interface using the ST7796S * display controller driver. The touchscreen is controlled through the LPI2C * interface and uses GPIO signals for interrupt and reset control. * * The original LCD, DBI and touchscreen drivers were obtained from an NXP * App Code Hub MCUXpresso SDK example and adapted to the S32K3 RTD * environment. The project also integrates LVGL 9.4 as the graphical user * interface library. * * The application mode is selected at compile time using the APP_MODE macro * defined in this file. It allows the user to select a standalone display * test, a standalone touchscreen test or the complete LVGL demonstration. * Only one application mode shall be selected for each build. * * A graphical application can be designed using NXP GUI Guider 2.0.1. * GUI Guider is configured for LVGL 9.4.0. The contents of the GUI Guider * "generated" and "custom" output directories can be copied directly into * the corresponding gui_guider directories in this project. After replacing * the generated output, the project shall be rebuilt to include the updated * screens, widgets, events and custom callbacks. * * Installed packages for S32 Design Studio 3.6.6: * * SW32K3_S32M27x_RTD_R23-11_7.0.1_D2603_DesignStudio_updatesite.zip * * Software Sources: * * NXP App Code Hub demo: * https://github.com/nxp-appcodehub/dm-https-lcd-led-demo * * LVGL release/v9.4: * https://github.com/lvgl/lvgl/tree/release/v9.4 * * NXP GUI Guider 2.0.1: * https://www.nxp.com/webapp/Download?colCode=GUI-GUIDER-INSTALLER-2.0.1-WIN&appType=license * * Hardware: * * FRDM-A-S32K344: * Remove jumper JP11 when using an external debugger. * * LCD-PAR-S035: * Set SW1 to 111. * * Board Connections: * * +------------------+----------------------+-----------------+-------------------+------------------------------+ * | FRDM-A-S32K344 | MCU Signal | LCD-PAR-S035 | LCD-PAR-S035 | Function | * | Connector | | Signal | Connector | | * +------------------+----------------------+-----------------+-------------------+------------------------------+ * | J2-20 | PTC27 / GPIO | TP_INT | J5-12 | Touch interrupt, active low | * | J2-19 | PTC7 / LPI2C1_SCL | TP_SCL | J5-8 | Touchscreen I2C clock | * | J2-17 | PTC6 / LPI2C1_SDA | TP_SDA | J5-6 | Touchscreen I2C data | * | J2-13 | GND | GND | J5-4 | Signal ground | * | J2-11 | PTB14 / LPSPI1_SCK | LCD_WR | J5-5 | LCD SPI clock | * | J2-9 | PTB15 / LPSPI1_SIN | LCD_RD | Not connected | SPI data from LCD | * | J2-7 | PTB16 / LPSPI1_SOUT | LCD_MOSI | J5-9 | SPI data to LCD | * | J2-5 | PTB17 / GPIO | LCD_CS | J5-11 | LCD chip select, active low | * | J2-3 | PTC10 / GPIO | LCD_D_C | J5-7 | Command low, data high | * | J2-1 | PTC11 / GPIO | LCD_RST | J5-10 | LCD reset, active low | * | JA3-3 | VDD_HV_A | VCC | J5-1 or J5-2 | 3.3 V supply | * | JA3-13 or JA3-15 | GND | GND | J5-3 | Power ground | * +------------------+----------------------+-----------------+-------------------+------------------------------+ * * Project Files: * * Format: * File or directory - Description - Source - License * * | lvgl_app.c/.h * | LVGL application layer * | Created for this project * | NXP proprietary license * | * | lv_conf.h * | Project-specific LVGL configuration * | Derived from the LVGL v9.4.0 configuration template * | MIT License * | * | lv_port.c/.h * | LVGL initialization and S32K3 port layer * | Created for this project * | NXP proprietary license * | * | main.c * | Application entry point and compile-time mode selection * | Created for this project * | NXP proprietary license * | * +---gui_guider * | +---custom * | | User callbacks and custom GUI logic * | | GUI Guider 2.0.1 output * | | NXP proprietary license * | | * | \---generated * | Generated screens, widgets and events * | GUI Guider 2.0.1 output * | NXP proprietary license * | * +---lcdc * | fsl_st7796s.c/.h * | ST7796S LCD controller driver * | NXP App Code Hub demo * | BSD-3-Clause License * | * +---lcd_par_s035 * | lcd_par_s035.c/.h * | LCD-PAR-S035 board and display integration * | Created for this project * | NXP proprietary license * | * | lcd_par_s035_config.h * | LCD-PAR-S035 project configuration * | Created for this project * | NXP proprietary license * | * +---lvgl * | \---src * | LVGL 9.4 graphics library * | LVGL release/v9.4 * | MIT License * | * +---platform * | display_compat.h * | MCUXpresso SDK and S32K3 RTD compatibility definitions * | Created for this project * | NXP proprietary license * | * | fsl_dbi.c/.h * | Generic display bus interface implementation * | NXP App Code Hub demo * | BSD-3-Clause License * | * | lcd_dbi_s32k3.c/.h * | S32K3 DBI transport implementation using LPSPI * | Created for this project * | NXP proprietary license * | * | lcd_platform.c/.h * | S32K344 board and platform abstraction * | Created for this project * | NXP proprietary license * | * \---touchpanel * fsl_gt911.c/.h * GT911 touchscreen controller driver * NXP App Code Hub demo * BSD-3-Clause License * * gt911_s32k3.c/.h * S32K3 adaptation using LPI2C and GPIO * Created for this project * NXP proprietary license * * ---------------------------------------------------------------------------- * Test Hardware: FRDM-A-S32K344, schematic revision B * MCU: S32K344 * Display: LCD-PAR-S035 with ST7796S controller * Touchscreen: GT911 capacitive touchscreen controller * Debugger: Lauterbach TRACE32 * Build Target: internal_FLASH
View full article
Request FlexNet entitlement for SW32K14-MCAL421-RTMC-1.0.1 Hello NXP Support Team, I would like to request access to: SW32K14-MCAL421-RTMC-1.0.1 Target MCU: S32K144 AUTOSAR MCAL: 4.2.x I have already followed the solution suggested in the existing NXP Community topic: 1. I searched for "S32K1 MCAL" on nxp.com and entered Flexera through the official product page. 2. I also tried the direct link for SW32K14-MCAL421-RTMC-1.0.1 while logged into my NXP account. However, the "Previous" tab is still greyed out, and the direct link shows: "Either the item was not found, or you are not authorized to download this item." I also attempted to create an NXP Support Case, but the Case Portal shows "Case creation disabled" because my email address cannot be linked to a company. It appears that my NXP account does not currently have access rights / FlexNet entitlement for this package. Could you please help add SW32K14-MCAL421-RTMC-1.0.1 to my NXP account, or advise how I can obtain access to this legacy release? Thank you very much for your support. Best regards Re: Request FlexNet entitlement for SW32K14-MCAL421-RTMC-1.0.1 Hi @pikaqiu  Try it now: https://www.nxp.com/webapp/swlicensing/sso/downloadSoftware.sp?catid=SW32K1-MCAL-D However, this SW is not supported and maintained anymore. We recommend to use latest RTD drivers.  Regards, Lukas Re: Request FlexNet entitlement for SW32K14-MCAL421-RTMC-1.0.1 Hi Lukas, Thank you for your support. It has been about a week since your reply, and the issue has now been resolved. I can access the required software successfully. Thank you again for your help. Best regards
View full article
私を驚かせたストリーミングサービス これまでいくつかのストリーミングサービスを試してきましたが、一貫性のあるものを見つけるのは思ったより難しいことがあります。 最近、 NexusIPTV を しばらくテストして み たところ、全体的な体験に非常に驚きました。ストリーミング品質は良好で、チャネルの読み込みも速く、テストしたデバイス間でサービスも良好に動作しました。 アメリカ、イギリス、カナダ にお住まいの方にとっては 、比較検討するサービスのリストに加えておく価値があるかもしれません。 私の体験談については、こちらに詳しく書きました。 👉 私の全体験
View full article
ADC转换时间问题 您好,NXP技术支持, 我正在使用 S32 设计工作室和 RTD 驱动程序对 S32K312 MCU 进行开发,并且我正在尝试了解单通道正常转换的 SAR ADC 的实际转换时序。 我的配置如下: MCU:S32K312 核心频率:120 MHz ADC功能时钟:120 MHz ADC模式:正常转换 通道数:1 预采样:已禁用 采样时间:33 个 ADC 时钟周期 我计算中使用的转换时间:48 个 ADC 时钟周期 硬件平均值:此测试中已禁用 已启用链结束通知/中断 相关代码如下: int main(void) { Clock_Ip_Init(&Clock_Ip_aClockConfig[0]); IntCtrl_Ip_Init(&IntCtrlConfig_0); IntCtrl_Ip_EnableIrq(ADC0_IRQn); Siul2_Port_Ip_Init( NUM_OF_CONFIGURED_PINS_PortContainer_0_BOARD_InitPeripherals, g_pin_mux_InitConfigArr_PortContainer_0_BOARD_InitPeripherals ); volatile Adc_Sar_Ip_StatusType status = ADC_SAR_IP_STATUS_ERROR; status = Adc_Sar_Ip_Init(0, &AdcHwUnit_0); 状态 = Adc_Sar_Ip_DoCalibration(0); Adc_Sar_Ip_EnableNotifications( 0, ADC_SAR_IP_NOTIF_FLAG_NORMAL_ENDCHAIN ); Siul2_Dio_Ip_TogglePins(PTA_L_HALF, 1U < 1U); Adc_Sar_Ip_StartConversion( 0, ADC_SAR_IP_CONV_CHAIN_NORMAL ); while(1) { __asm__ ("nop"); } } void Adc_EndOfNormalChain_Callback(void) { Siul2_Dio_Ip_TogglePins(PTA_L_HALF, 1U < 1U); } 我使用逻辑分析仪测量两次 GPIO 转换之间的时间。 仅根据 ADC 时序,我计算得出大约为 700ns。 然而,测得的 GPIO 脉冲宽度约为 4us。 我想了解以下内容: 当禁用预采样和硬件平均时,单次法线转换的正确公式是什么? Adc_Sar_Ip_DoCalibration()执行的 ADC 校准是否会影响后续每次 ADC 转换的时序,还是仅在初始化期间计算/存储校准值? 增益校正、偏移校正、内部电容充电、建立时间或任何内部ADC处理是否会给每次转换增加额外的周期? S32K312 SAR ADC 在正常转换模式下,单通道的精确转换时间公式是什么? 测量的时间间隔是否为: Adc_Sar_Ip_StartConversion() 和Adc_EndOfNormalChain_Callback() 是否包括显著的RTD软件开销、中断延迟、ISR处理或回调开销? 是否有推荐的方法可以只测量ADC硬件转换时间,而不包括RTD和中断开销? 如果可以,能否提供此配置下预期的ADC时序(以时钟周期为单位)? 我的主要目标是确定大约 4 µs 的测量结果主要是由 ADC 硬件时序引起的,还是由 RTD/中断/软件开销引起的。 任何关于ADC转换的帮助都将不胜感激! 谢谢。 Re: ADC Conversion time issue 您好, ADC转换时间方程直接在S32K3参考手册第60.3.18节中给出。“转换时间”。对于您的配置(单通道,预采样禁用,硬件平均禁用),可以使用该公式和配置的 ADC 时钟计算转换时间。 补充几点: 1. Adc_Sar_Ip_DoCalibration() 不会影响后续转换的时机。校准在初始化期间执行,然后校准值被ADC硬件使用。 2. 测得的 ~4 µs 不仅仅是 ADC 转换时间。您的测量范围: Adc_Sar_Ip_StartConversion() ADC采样和转换 ADC中断生成 NVIC中断延迟 RTD ISR 处理 回调调度 GPIO 切换操作 因此,测得的脉冲宽度包括ADC硬件时间和软件开销。预计转换时间将明显长于仅使用 RM 公式计算出的转换时间。 3. 为了更准确地测量ADC硬件转换时间,我们可以推荐以下方法: Adc_Sar_Ip_StartConversion() 返回后立即切换第一个 GPIO。这样就从测量的脉冲中消除了大部分启动 API 执行时间。 在 ADC 中断处理程序中,在调用配置的通知回调之前,尽早切换 GPIO。这样就将中断入口与回调分发开销分开了。 为了最大限度地降低 GPIO 软件开销,暂时使用直接写入 SIUL2 GPIO 寄存器,而不是使用 Siul2_Dio_Ip_TogglePins()。 或者,轮询 ADC 链结束状态标志,并在硬件标志设置后立即切换 GPIO。这不包括 NVIC 和回调开销,但轮询循环和 GPIO 写入延迟仍然存在。 因此,根据所提供的信息,~4 µs 的测量结果很可能是由整个软件/中断路径主导,而不是 ADC 转换本身。 BR,彼得
View full article
My Experience Finding a Reliable IPTV Service in 2026 After trying and comparing different IPTV services, I found that Nexusiptv.live has been one of the better options for my needs, especially when looking at streaming stability, video quality, and content availability for viewers in the USA, UK, and Canada. Of course, performance can depend on your internet connection and location, but my overall experience has been positive so far. I wrote a more detailed article about what I looked for when choosing a reliable IPTV service in 2026: 👉 Read my full experience on Medium
View full article
2026年に信頼できるIPTVサービスを見つける私の経験 さまざまなIPTVサービスを試して比較した結果、特にアメリカ、イギリス、カナダの視聴者のストリーミングの安定性、映像品質、コンテンツの利用可能性を考えると、Nexusiptv.live が私のニーズに合った選択肢の一つだと感じました。 もちろん、パフォーマンスはインターネット接続や場所によって変わりますが、全体的にはこれまでのところ良い経験です。 2026年に信頼できるIPTVサービスを選ぶ際に私が重視した点について、より詳細な記事を書きました。 👉 Mediumで私の体験談全文をお読みください。
View full article
我在2026年寻找可靠IPTV服务的经验 在尝试和比较了不同的 IPTV 服务之后,我发现Nexusiptv.live是比较符合我需求的选择之一,尤其是在流媒体稳定性、视频质量以及为美国、英国和加拿大的观众提供内容方面。 当然,性能可能取决于您的网络连接和所在位置,但到目前为止,我的整体体验是积极的。 我写了一篇更详细的文章,介绍了我在2026年选择可靠的IPTV服务时所考虑的因素: 👉 在 Medium 上阅读我的完整经历。
View full article
ADC変換時間の問題 こんにちは、NXPサポートの皆さん、 私はS32 Design StudioとRTDドライバーを使ってS32K312 MCUを扱っており、シングルチャネルの通常変換におけるSAR ADCの実際の変換タイミングを理解しようとしています。 私の設定は以下の通りです。 MCU:S32K312 コアクロック:120MHz ADC機能クロック:120MHz ADCモード:通常変換 チャネル数:1 プリサンプリング:無効 サンプリング時間:33 ADCクロックサイクル 計算に使用した変換時間:48 ADCクロックサイクル ハードウェア平均化:このテストでは無効になっています チェーン終了通知/割り込みが有効 該当するコードは以下のとおりです。 int main(void) { Clock_Ip_Init(&Clock_Ip_aClockConfig[0]); IntCtrl_Ip_Init(&IntCtrlConfig_0); IntCtrl_Ip_EnableIrq(ADC0_IRQn); Siul2_Port_Ip_Init( NUM_OF_CONFIGURED_PINS_PortContainer_0_BOARD_InitPeripherals, g_pin_mux_InitConfigArr_PortContainer_0_BOARD_InitPeripherals ); volatile Adc_Sar_Ip_StatusType status = ADC_SAR_IP_STATUS_ERROR; status = Adc_Sar_Ip_Init(0, &AdcHwUnit_0); ステータス = Adc_Sar_Ip_DoCalibration(0); Adc_Sar_Ip_EnableNotifications( 0, ADC_SAR_IP_NOTIF_FLAG_NORMAL_ENDCHAIN ); Siul2_Dio_Ip_TogglePins(PTA_L_HALF, 1U < 1U); Adc_Sar_Ip_StartConversion( 0, ADC_SAR_IP_CONV_CHAIN_NORMAL ); while(1) { __asm__ ("nop"); } } void Adc_EndOfNormalChain_Callback(void) { Siul2_Dio_Ip_TogglePins(PTA_L_HALF, 1U < 1U); } ロジックアナライザを使用して、2つのGPIO遷移間の時間を測定します。 ADCのタイミングのみに基づいて計算したところ、約700ナノ秒という値が得られました。 しかし、測定されたGPIOパルス幅は約4μsである。 以下の点について理解を深めたいです。 プリサンプリングとハードウェア平均化が無効になっている場合、単一の正規変換を行うための正しい式は何ですか? Adc_Sar_Ip_DoCalibration()によって実行される ADC キャリブレーションは、後続のすべての ADC 変換のタイミングに影響しますか、それとも初期化時にのみキャリブレーション値を計算/保存しますか? ゲイン補正、オフセット補正、内部コンデンサの充電、セトルタイム、または内部ADCプロセッシングは変換ごとに追加のサイクルを加えるのでしょうか? 通常の変換モードでの1チャネルのS32K312 SAR ADCの正確な変換時間公式は何ですか? 測定された時間間隔は: Adc_Sar_Ip_StartConversion() およびAdc_EndOfNormalChain_Callback() RTDソフトウェアのオーバーヘッド、割り込みレイテンシ、ISR処理、またはコールバックオーバーヘッドを含むべきか? RTDや割り込みのオーバーヘッドを除き、ADCハードウェア変換時間のみを測定する推奨される方法はありますか? 可能であれば、この構成で期待されるADCタイミング(クロックサイクル単位)を教えてもらえますか? 私の主な目的は、約4μsの測定値が主にADCのハードウェアタイミングによるものか、RTD/割り込み/ソフトウェアのオーバーヘッドによるものかを明らかにすることです。 このADC変換に関するご協力は大歓迎です! ありがとう。 Re: ADC Conversion time issue こんにちは、 ADC変換時間の方程式はS32K3リファレンスマニュアル60.3.18節に直接記載されています「変換時間」あなたの設定(シングルチャネル、プリサンプリング無効、ハードウェア平均無効)では、その式と設定されたADCクロックを使って変換時間を計算できます。 補足事項: 1. Adc_Sar_Ip_DoCalibration() は、後続の変換のタイミングに影響を与えません。キャリブレーションは初期化時に実行され、そのキャリブレーション値はADCハードウェアによって使用されます。 2. 測定された約4µsは、ADC変換時間だけではありません。測定範囲: Adc_Sar_Ip_StartConversion() ADCサンプリングと変換 ADC割り込み生成 NVIC割り込みレイテンシ RTD ISRプロセッシング コールバックディスパッチ GPIOトグル操作 したがって、測定されたパルス幅にはADCのハードウェア時間とソフトウェアのオーバーヘッドの両方が含まれます。これは、RM式のみから計算される変換時間よりも明らかに長くなると予想される。 3. ADCハードウェア変換時間をより正確に測定するために、以下に推奨します Adc_Sar_Ip_StartConversion() が戻った直後に、最初の GPIO をトグルします。これにより、測定されたパルスから、起動APIの実行時間の大部分が除去されます。 ADC割り込みハンドラでは、設定された通知コールバックを呼び出す前に、できるだけ早い段階でGPIOを切り替えてください。これにより、割り込み処理の開始とコールバックディスパッチのオーバーヘッドが分離されます。 GPIOソフトウェアの負荷を最小限に抑えるために、Siul2_Dio_Ip_TogglePins()の代わりに一時的に直接SIUL2 GPIOレジスタ書き込みを使用してください。 あるいは、ADCのチェーン終了ステータスフラグをポーリングし、ハードウェアフラグがセットされたらすぐにGPIOを切り替える。これによりNVICやコールバックのオーバーヘッドは除外されますが、ポーリングループやGPIO書き込みレイテンシは残ります。 したがって、提供された情報に基づくと、~4μsの測定値はADC変換自体よりもソフトウェア/割り込み経路全体に支配されている可能性が高いです。 BR、ペトル
View full article
ADC Conversion time issue Hello NXP Support, I am working with an S32K312 MCU using S32 Design Studio and RTD drivers, and I am trying to understand the actual conversion timing of the SAR ADC for a single-channel normal conversion. My setup is: MCU: S32K312 Core clock: 120 MHz ADC functional clock: 120 MHz ADC mode: Normal conversion Number of channels: 1 Pre-sampling: Disabled Sampling time: 33 ADC clock cycles Conversion time used in my calculation: 48 ADC clock cycles Hardware averaging: Disabled for this test End-of-chain notification/interrupt enabled The relevant code is: int main(void) { Clock_Ip_Init(&Clock_Ip_aClockConfig[0]); IntCtrl_Ip_Init(&IntCtrlConfig_0); IntCtrl_Ip_EnableIrq(ADC0_IRQn); Siul2_Port_Ip_Init( NUM_OF_CONFIGURED_PINS_PortContainer_0_BOARD_InitPeripherals, g_pin_mux_InitConfigArr_PortContainer_0_BOARD_InitPeripherals ); volatile Adc_Sar_Ip_StatusType status = ADC_SAR_IP_STATUS_ERROR; status = Adc_Sar_Ip_Init(0, &AdcHwUnit_0); status = Adc_Sar_Ip_DoCalibration(0); Adc_Sar_Ip_EnableNotifications( 0, ADC_SAR_IP_NOTIF_FLAG_NORMAL_ENDCHAIN ); Siul2_Dio_Ip_TogglePins(PTA_L_HALF, 1U << 1U); Adc_Sar_Ip_StartConversion( 0, ADC_SAR_IP_CONV_CHAIN_NORMAL ); while (1) { __asm__("nop"); } } void Adc_EndOfNormalChain_Callback(void) { Siul2_Dio_Ip_TogglePins(PTA_L_HALF, 1U << 1U); } I measure the time between the two GPIO transitions using a logic analyzer. Based on the ADC timing alone, I calculated it, which gives approximately 700ns. However, the measured GPIO pulse width is approximately 4us. I would like to understand the following: What is the correct formula for a single normal conversion when pre-sampling and hardware averaging are disabled? Does the ADC calibration performed by Adc_Sar_Ip_DoCalibration() affect the timing of every subsequent ADC conversion, or does it only calculate/store calibration values during initialization? Do gain correction, offset correction, internal capacitor charging, settling time, or any internal ADC processing add additional cycles to every conversion? What is the exact conversion-time formula for the S32K312 SAR ADC for one channel in normal conversion mode? Does the measured time between: Adc_Sar_Ip_StartConversion() and Adc_EndOfNormalChain_Callback() include significant RTD software overhead, interrupt latency, ISR processing, or callback overhead? Is there a recommended method to measure only the ADC hardware conversion time, excluding RTD and interrupt overhead? If possible, could you provide the expected ADC timing in clock cycles for this configuration? My main objective is to determine whether the approximately 4 µs measurement is caused mainly by ADC hardware timing or by RTD/interrupt/software overhead. Any help related to this ADC conversion is appreciated!! Thank you.  Re: ADC Conversion time issue Hi, The ADC conversion-time equation is provided directly in S32K3 Reference Manual, section 60.3.18 "Conversion time". For your configuration (single channel, pre-sampling disabled, hardware averaging disabled), the conversion time can be calculated using that formula and the configured ADC clock. A few additional notes: 1. Adc_Sar_Ip_DoCalibration() does not affect the timing of subsequent conversions. Calibration is executed during initialization and the calibration values are then used by the ADC hardware. 2. The measured ~4 µs is not ADC conversion time only. Your measurement spans: Adc_Sar_Ip_StartConversion() ADC sampling and conversion ADC interrupt generation NVIC interrupt latency RTD ISR processing Callback dispatch GPIO toggle operations Therefore, the measured pulse width includes both ADC hardware time and software overhead. It is expected to be noticeably larger than the conversion time calculated from the RM formula alone. 3. To measure the ADC hardware conversion time more accurately, we can recommend below Toggle the first GPIO immediately after Adc_Sar_Ip_StartConversion() returns. This removes most of the start-API execution time from the measured pulse. In the ADC interrupt handler, toggle GPIO as early as possible, before calling the configured notification callback. This separates interrupt entry from callback-dispatch overhead. For the lowest GPIO software overhead, temporarily use a direct SIUL2 GPIO register write instead of Siul2_Dio_Ip_TogglePins(). Alternatively, poll the ADC end-of-chain status flag and toggle the GPIO immediately when the hardware flag becomes set. This excludes NVIC and callback overhead, although polling-loop and GPIO-write latency remain. So, based on the information provided, the ~4 µs measurement is most likely dominated by the complete software/interrupt path rather than the ADC conversion itself. BR, Petr
View full article
一个让我感到惊喜的流媒体服务 这些年来我尝试过好几种流媒体服务,但要找到一个始终保持稳定的服务比想象中要难得多。 最近我试用了NexusIPTV ,整体体验让我非常满意。流媒体播放质量很好,频道加载速度很快,而且在我测试过的所有设备上都能流畅运行。 对于 美国、英国和加拿大 的人们来说 ,或许值得将这项服务添加到比较列表中。 我在这里详细描述了我的经历: 👉 我的完整经历
View full article
A Streaming Service That Surprised Me I’ve tried several streaming services over the years, and finding one that remains consistent can be harder than expected. Recently, I spent some time testing NexusIPTV and was positively surprised by the overall experience. The streaming quality was good, channels loaded quickly, and the service worked well across the devices I tested. For people in the USA, UK, and Canada, it may be worth adding to the list of services to compare. I wrote more about my experience here: 👉 My full experience
View full article
SW32K14-MCAL421-RTMC-1.0.1 の FlexNet 利用権を申請してください。 こんにちは、NXPサポートチームの皆さん、 以下のアクセスを申請したいのです: SW32K14-MCAL421-RTMC-1.0.1 ターゲットMCU:S32K144 AUTOSAR MCAL: 4.2.x 既存の提案に提案された解決策はすでに採用しています NXPコミュニティのトピック: 1.nxp.com で「S32K1 MCAL」を検索してFlexeraと入力しました 公式製品ページを通じて。 2. また、直接リンクも試してみました。 SW32K14-MCAL421-RTMC-1.0.1 をNXPアカウントにログインした状態で実行します。 しかし、「前へ」タブはまだグレー表示されており、直接 リンク先の表示: 商品が見つからなかったか、またはあなたに権限がありません。 このアイテムをダウンロードするには。」 また、NXPサポートCASEの作成も試みましたが、CASE ポータルには「CASE作成が無効」と表示されています。メールアドレスが原因で NXPについてと連携してはいけません。 どうやら私のNXPアカウントは現在アクセスできないようです このパッケージの権利/FlexNet権利について。 ぜひ追加でお願いできますか? SW32K14-MCAL421-RTMC-1.0.1 私のNXPアカウントに、またはアクセス方法を教えてください レガシーリリース? サポートありがとうございます。 よろしくお願いいたします。 Re: Request FlexNet entitlement for SW32K14-MCAL421-RTMC-1.0.1 こんにちは@pikaqiu 今すぐお試しください: https://www.nxp.com/webapp/swlicensing/sso/downloadSoftware.sp?catid=SW32K1-MCAL-D しかし、このソフトウェアは現在サポートおよびメンテナンスされていません。最新のRTDドライバの使用を推奨します。 よろしくお願いいたします。 ルーカス Re: Request FlexNet entitlement for SW32K14-MCAL421-RTMC-1.0.1 こんにちは、ルーカスさん。 サポートありがとうございます。 ご返信から約1週間が経過し、問題は解決いたしました。必要なソフトウェアには問題なくアクセスできます。 ご協力ありがとうございました。 よろしくお願いします
View full article
申请 SW32K14-MCAL421-RTMC-1.0.1 的 FlexNet 授权 您好,NXP支持团队, 我希望申请访问以下内容: SW32K14-MCAL421-RTMC-1.0.1 目标MCU:S32K144 AUTOSAR MCAL:4.2.x 我已经按照现有方案中建议的解决方案进行了操作。 NXP社区主题: 1.我在 nxp.com 上搜索了“S32K1 MCAL”,然后输入了 Flexera。 通过官方产品页面。 2. 我还尝试了直接链接 登录我的 NXP 帐户后,SW32K14-MCAL421-RTMC-1.0.1。 然而,“上一页”选项卡仍然呈灰色,无法点击。 链接显示: “要么未找到该物品,要么您未获得授权。” 下载此项目。 我还尝试创建了一个 NXP 支持案例,但是案例提交失败。 门户网站显示“案例创建已禁用”,因为我的电子邮件地址 无法与任何公司关联。 我的NXP账户目前似乎没有访问权限。 此软件包的权利/FlexNet授权。 请问您能否帮忙添加 SW32K14-MCAL421-RTMC-1.0.1 请告知我如何才能访问我的NXP账户,或者告诉我如何才能获得访问权限。 旧版本发布? 非常感谢您的支持。 顺祝商祺! Re: Request FlexNet entitlement for SW32K14-MCAL421-RTMC-1.0.1 嗨@pikaqiu 立即尝试: https://www.nxp.com/webapp/swlicensing/sso/downloadSoftware.sp?catid=SW32K1-MCAL-D 但是,该软件已停止支持和维护。我们建议使用最新的RTD驱动程序。 此致, Lukas Re: Request FlexNet entitlement for SW32K14-MCAL421-RTMC-1.0.1 嗨,卢卡斯, 感谢您的支持。 自您回复以来已经过去大约一周了,问题现已解决。我可以成功访问所需的软件。 再次感谢您的帮助。 此致
View full article
From Silicon to Supply Chain: How NXP's MCX Portfolio Is Built for Resilience In today's market, MCU selection is no longer based solely on product features like performance or power consumption. Supply assurance, manufacturing flexibility, and long-term availability have become critical design requirements and often lead the selection conversation. Developers need confidence that the device will be available and supported throughout their products’ lifecycle. Supply resiliency is no longer just an operations topic, it's a key design consideration. NXP’s manufacturing and supply strategy for the MCX portfolio is designed with resiliency in mind. Recent investments in manufacturing capacity, combined with the opening of VSMC's new Singapore facility, reinforce NXP's commitment to helping customers plan with greater confidence and address supply chain risk. The MCX portfolio is supported by a diversified manufacturing strategy intended to improve supply flexibility, geographic diversification, and long-term availability. A New Era of Manufacturing Resilience The opening of VSMC’s new Singapore facility marks an important step in NXP’s long-term manufacturing strategy and highlights the value of its joint ownership in the venture, helping expand manufacturing capacity and enhance supply resilience. For MCX customers, this aligns directly with NXP's long-term strategy of expanding manufacturing options and supporting greater geographic diversification over time. NXP's supply architecture leverages multiple manufacturing partners and strategically distributed operations to create a more robust supply chain designed to support evolving customer demand and strengthen long-term supply flexibility. MCX is backed by a comprehensive resiliency strategy centered on three key pillars: Predictable Lead Times NXP maintains a consistent targeted lead time of approximately 16-weeks for MCX devices, helping customers improve production planning and reduce uncertainty during product launches and volume ramp-ups. Diversified Front-End Manufacturing MCX is supported by a diversified front-end manufacturing strategy, including a long-term second-source roadmap incorporating VSMC in Singapore. This geographic diversification provides additional manufacturing flexibility and strengthens long-term supply resilience. Flexible Back-End Operations Multiple assembly and test locations across geographic regions provide customers with sourcing flexibility and support continued capacity expansion. NXP’s back-end strategy includes assembly and test operations across multiple regions, with China and non-China pathways available for select MCX products and package options. More Than Availability: Long-Term Customer Confidence Supply resiliency is not simply about addressing today's demand. It is about enabling product developers to make long-term platform decisions with confidence. The MCX family combines: Consistent lead time target of 16 weeks Geographic manufacturing diversification Multi-source manufacturing strategies Broad package support Long-term product longevity commitments Together, these capabilities help reduce risk while giving customers confidence that the MCU platform selected today can help customers evaluate MCX for long-term product and platform plans. MCX: Supply Strength You Can Build On While many manufacturers continue to face extended lead times across portions of their MCU portfolios, NXP has invested aggressively in capacity expansion and supply chain diversification. These investments are designed to provide customers with a dependable path to production while supporting future growth and innovation. The opening of VSMC’s Singapore facility represents an important step in building a more geographically diversified semiconductor manufacturing ecosystem. Alongside NXP’s broader investments in manufacturing flexibility and expanded sourcing options, it supports the long-term strategy behind the MCX portfolio. Whether developers are building a new industrial controller, updating an existing platform or planning the next generation of connected products, MCX brings together scalable performance, a broad development ecosystem and a manufacturing strategy designed to support long-term product plans. Build your next design with MCX. Celebrate the VSMC grand opening with 50% off one eligible FRDM-MCX board on nxp.com through October 31, 2026. Use coupon code AMKSFYKZ. Limit one eligible board per customer. Terms and conditions apply. Supply resilience is now a critical factor in MCU selection. Discover how NXP’s MCX portfolio combines predictable lead times, diversified manufacturing, long-term product longevity, and strategic investments like VSMC’s new Singapore facility to help developers build with confidence and reduce supply chain risk. Board Design MCX C15 MCX C16 MCXA MCXC MCXN
View full article
imx6ull->ADC こんにちは、 私はi.MX6ULLベースのカスタムSOMモジュールを使用しています。私たちの要件として、 i.MX プロセッサ用のConfig Toolsを使ってピンを設定しています。Config Toolsで、 Create a Standalone Projectを選択し、次にi.MX 6ULL → (6Y2...05)を選択しました。 私たちの要件は、Config Toolsを使用してピンを設定し、生成された.dtsiファイルを取得し、同じファイルを使用してイメージを構築することです。しかし、これは当初はうまくいかなかった。 UARTに関しては、対応するデバイスノードを追加し、そのステータスを「OK」に設定する必要があると理解しました。同様に、生成された.dtsiファイルにも小さな修正が必要でした。ファイル。 .dtsiファイルを添付しました。Config Toolsによって生成されたファイル。ぜひご覧ください。そのファイルで、imx6ull-boardの行をコメントアウトしたところ、設定が正常に動作するようになりました。 UARTの設定が終わったので、次はADCの設定に移りました。Config ToolsでADCの設定を確認したところ、 ADCが同じGPIOピンを使用していることに気づきました。しかし、1つのGPIOピンをGPIOとして、もう1つのGPIOピンをADCとして設定した場合、生成されるIOMUX構成は同じように見えることがわかりました。なぜそうなっているのでしょうか?これは想定される動作でしょうか? i.MX6ULLカスタムSOMでADCの設定やテストの正しい方法を教えていただけますか? また、当初の要件は、Config Toolsを使用してピンを設定し、生成された設定ファイルを使用して、イメージをビルドしてフラッシュすることでした。このアプローチが弊社のカスタムボードにも適用できるかどうか、あるいは生成された.dtsiファイルに追加の変更が必要かどうかを確認したいと思います。ファイル。 dtsファイルと.dtsiファイルを添付しました。参考のために、設定ツールで生成されたファイルを添付します。 これは実際にはどういう意味ですか? Re: imx6ull->ADC こんにちは@Et_MM これはi.MX6ULL用設定ツールのバグのようです。 どのGPIOをADCとして使用したいのか、また他のGPIO機能にはどのGPIOを使用するのかを明確にしてください。 正しい&adc1ノードと正しいピンマックスを生成するお手伝いができます。 よろしくお願いいたします。 サラス。 Re: imx6ull->ADC GPIO01_IO01、GPIO01_IO02 GPIO自体、GPIO01_IO03,GPIO01_IO04 ADCとして欲しいです。 DTSIファイルを調べたところ、ADC1はADC1だけのようです。adc2は利用できません。もし私の理解が間違っていたら、訂正してください。 また、設定したADCとGPIOピンが動作しているかどうか、どのようにテスト・検証すればよいかも教えてください。どうやってそれを検証すればいいですか? 既に、私たちが使用しているdtsファイルとdtsiファイルを共有しました。もうご覧になっていることを願っています。上記で言及されているADCの設定は間違っているのでしょうか? Re: imx6ull->ADC こんにちは@Et_MM お元気でお過ごしのことと思います。 はい、ADC1が唯一利用可能なものです。 あなたのユースケースでは、以下のデバイスツリーをご利用ください: &adc1 { num-channels = <10>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_adc1>; status = "okay"; }; &iomuxc { pinctrl_adc1: adc1grp { fsl,pins = < MX6UL_PAD_GPIO1_IO03__GPIO1_IO03 0x3000 MX6UL_PAD_GPIO1_IO04__GPIO1_IO04 0x3000 >; }; }; それならGPIO1_IO03とGPIO1_IO04だけをADCチャネルとして使います。 root@imx6ul7d:/sys/bus/iio/devices/iio:device1# cat in_voltage3_raw 75 root@imx6ul7d:/sys/bus/iio/devices/iio:device1# cat in_voltage4_raw 0 root@imx6ul7d:/sys/bus/iio/devices/iio:device1# cat name 2198000.adc よろしくお願いいたします。 サラス。 Re: imx6ull->ADC ご返信ありがとうございます。 GPIO01_IO01、GPIO01_IO02をGPIとして設定したい場合。構成はどうなるのか、それについても教えていただけませんか? Re: imx6ull->ADC こんにちは! 以下の内容を&iomuxの中に簡単に追加できます: pinctrl_hog: hoggrp { fsl,pins = < MX6UL_PAD_GPIO1_IO01__GPIO1_IO01 0x10b0 MX6UL_PAD_GPIO1_IO02__GPIO1_IO02 0x10b0 >; }; 他の周辺機器によって既に占有されていないことを確認してください。 よろしくお願いいたします。 サラス。 Re: imx6ull->ADC こんにちは。ご返信ありがとうございます。試してみます。 あなたが教えてくれた設定で ADC を試しましたが、そのコマンドを実行すると、これが私の出力です: root@imx6ul7d:/sys/bus/iio/devices/iio:device0# cat in_voltage1_raw 78 root@imx6ul7d:/sys/bus/iio/devices/iio:device0# cat in_voltage4_raw 74 でも、このピンがうまくいっているか確認するために、他にテストする方法はありますか?
View full article
关于 HSE FW 2.40.0 和 2.55.0 中 GCM IV 长度支撑的问题 你好, 我有一个关于 S32K358 上 HSE 的 GCM 操作的问题。 在 HSE 服务 API 参考手册的 AEAD 服务描述中,HSE FW 2.40.0 和 2.55.0 都对 GCM 进行了如下规定: GCM: 1 <= ivLength <= 2^32-1。建议大小为 12 字节或更大。 但是,HSE FW 2.40.0 手册包含以下附加说明,而 HSE FW 2.55.0 手册中没有此说明: 在 GCM 操作中,建议使用正好 12 字节的 IV 值。对于任何非 12 字节的 IV 大小,GCM 加密操作生成的认证标签可能不正确。在 GCM 解密操作中,身份验证检查可能会失败。 在此,我想澄清以下几点: 1. 当 IV 长度不是 12 字节时,HSE FW 2.40.0 中 GCM 操作能否正常使用? 2. 当使用 12 字节以外的 IV 长度时,HSE FW 2.40.0 和 2.55.0 在 GCM 操作方面是否存在行为差异? 3. 当使用 12 字节以外的 IV 长度时,HSE FW 2.40.0 和 2.55.0 的 GCM 操作可靠性是否存在差异? 在我们的测试中,即使 IV 长度不是 12 字节,GCM 加密和解密也能成功执行,并且认证结果也正确。 因此,我想确认 HSE FW 2.40.0 是否完全支持使用 12 字节以外的 IV 长度,以及在这种情况下与使用 HSE FW 2.55.0 相比是否存在任何功能差异。 谢谢你的解释。 Re: Question about GCM IV Length Support in HSE FW 2.40.0 and 2.55.0 嗨@wodudwo 从技术上讲,ivLength 可以配置为不同的长度;但是,不建议这样做,因为不能保证其行为可靠。正如您正确指出的那样,文档中说明,对于 GCM 解密操作,当使用 12 字节以外的 IV 长度时,身份验证检查可能会失败。 虽然使用不同长度的静脉输液管进行的测试可能通过了,但这并不能保证手术一定会成功。换句话说,某个测试用例的成功结果不应被解释为表明该配置完全受支持或在所有情况下都能稳定运行。 此外,如果您查看这两个固件版本的发行说明,您会发现限制列表包含相同的建议:使用正好为 12 字节的 IV 值。 虽然从 HSE 固件 2.55.0 版本开始,HSE 服务 API 参考手册中已删除该注释,但限制本身仍然存在。 BR,VaneB Re: Question about GCM IV Length Support in HSE FW 2.40.0 and 2.55.0 嗨@wodudwo 如 HSE 服务 API 参考手册中所述,建议的 IV 长度在1<= ivLength <= 2∧32-1 的范围内,建议为 12 字节或更大。 参考实现可在 hse_crypto.c 文件中找到。( S32K3 通用 HSE 演示示例)和 hse_sessionkeys_example.c(HSE 演示应用程序)。 Re: Question about GCM IV Length Support in HSE FW 2.40.0 and 2.55.0 您好,谢谢您的澄清。 关于使用 12 字节以外的 IV,我还有一个问题。 我理解,当使用非 12 字节的 IV 时,身份验证标签的生成/验证可能不可靠。 在这种情况下,无论认证标签如何,加密/解密操作本身是否可以被认为是可靠的? 例如,如果使用 16 字节的 IV 进行 GCM 加密,即使认证标签可能不可靠,能否保证生成的密文正确且一致? 换句话说,这种限制是专门针对身份验证标签的生成/验证,还是使用 12 字节以外的 IV 也会影响实际加密/解密操作的可靠性/正确性? 谢谢! Re: Question about GCM IV Length Support in HSE FW 2.40.0 and 2.55.0 您好,感谢您的回复。 但是,我想澄清一下我之前的问题中没有提到的一点。 如果 GCM 使用非 12 字节的 IV,例如 16 字节的 IV: 1. 加密操作生成的密文是否能保证正确可靠? 2. 解密操作恢复的明文是否能保证正确可靠? 我理解,对于非 12 字节的 IV,身份验证标签的生成/验证可能不可靠。 我的问题是,这种限制是否也适用于实际的加密/解密结果(密文/明文),还是这种限制仅与认证标签有关。 您能否具体解释一下这一点?
View full article
Request to extend expiring license for S32 Design Studio for ARM v2.2 S32 Design Studio for ARM ActivationId: 2FBC-9F2F-AF20-37D9 Evaluation Days: 27 Feature Version: 2.2 Feature Status: Evaluation (27 days) Re: Request to extend expiring license for S32 Design Studio for ARM v2.2 Hi,  your S32DS license has been extended.  Re: Request to extend expiring license for S32 Design Studio for ARM v2.2 Yes, just checked and the license got extended. Thank you very much for your assistance!
View full article
FreeMaster 无法集成 GUI Guider。 各位 FreeMASTER 网页上指出 GUI Giider 支持在 FreeMASTER 中创建小部件,但目前可用的 FreeMASTER 版本为 2.01,并且视频中也提到了这一点: https://community.nxp.com/t5/MCUXpresso-Training-Hub/FreeMASTER-Gui-Guider-integration/ta-p/1924225 请说明如何将 GUI Guider 集成到 FreeMASTER 中,但是 GUI Guider 2.01 中既没有“FreeMASTER 服务器链接”,也没有任何关于 FreeMASTER 配置的参考资料。此外,FREEMaster 不支持 NODE Red(仅轻量版支持)。所以,在FreeMaster中无法创建美观的小部件。 这样说对吗? 看待 保罗 FreeMASTER 中是否可以使用 GUI Guider?如果可以,该如何操作?你能帮我找到相关的视频/应用说明吗? 谢谢 保罗 Re: Impossible to integrate GUI Guider in FreeMaster 各位 根据 NXP 内部的工单系统显示,Gui Guider 2.01 无法集成到 FreeMaster 中,只有下一个版本才能集成。目前我们必须使用 GUI Guider 2.01 v1.10。 此致 Paolo
View full article