- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2411644_en-US
2411644_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2411644_en-US
2411644_en-US
Hi NXP Community,
I am looking for some clarification regarding the PWM-X deadtime correction feature.
From the documentation, I understand that PWM-X can modify the PWM pulses based on the current/load condition. However, I am not clear about how the PWM pattern is generated and how the required feedback signal is connected and routed.
In my application, the switches and current-sensing circuitry are external to the MCU:
Is the sensed current signal expected to be connected directly to an MCU pin?
Or should it first go through LPCMP and then be internally routed to PWM-X through TRGMUX or another internal connection?
What is the expected signal path and configuration for this feature?
I have attached an image from the NXP reference design/documentation showing the slightly decaying output waveform obtained across the load.
What I am particularly trying to understand is the PWM pulse pattern used to generate this waveform.
The waveform shown in the reference design is the resulting waveform at the load/power stage. However, the PWM signal generated by the MCU will pass through the gate driver and switching stage, so the PWM signal itself will not have the same shape as the waveform shown.
PWM-X generated pulses → gate driver/power stage → resulting waveform across the load
Specifically, I would like to understand how PWM-X determines the pulse width/duty cycle and timing required to obtain the shown output waveform, including how the deadtime correction is applied.
Is there any reference design, application note, example code, or reference software where this PWM-X feature is implemented? An example showing the PWM configuration, pulse pattern, pin configuration, internal signal routing, and required external circuitry would be very helpful.
FlexPWM Synchronization
I also have a question regarding FlexPWM synchronization.
Can the synchronization signal be generated internally by another peripheral, or does it have to originate from an external MCU pin?
For example, can a signal generated by eMIOS be internally routed to the FlexPWM synchronization input?
Any example or clarification regarding the internal routing/configuration would be very helpful.
Thanks in advance.
Best regards,
Ganesh