- 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
- :
- 2415366_en-US
2415366_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2415366_en-US
2415366_en-US
I have a few questions in regards to the Pins Tool and the Knowledge Base LED entry for the S32K1xx.
The Entry in question can be found here: HOWTO: Create a Blinking LED example project using S32K1xx RTD with AUTOSAR
The Entry says to disable the Pins Tool.
The MCAL Port User Manual however mentions that it is perfectly fine to use the Pins Tool for configurating the controller.
Which information is correct?
Is there a way to add Pins to the Pins Tool and have them automatically added to the respective MCAL entries (Port, Dio)?
Or do I always have to add each pin three times (Pins Tool, Port, Dio)?
What is the recommended workflow for this admittedly most basic of functionalities?
@VaneB Thanks for clarifying the process.
I highly recommend adding a way to synchronize the pins between the Pins Tool and the MCAL Port and Dio tools.
The Pins Tool is very intuitive and easy to use while the MCAL settings section is tedious and unclear.
This article was published quite some time ago, and the relationship between the Pins Tool and the PORT driver has changed across RTD releases.
In the latest versions, when using MCAL drivers, the Pins Tool and PORT driver work closely together. This means the pins should be configured in the Pins Tool and also added to the PORT driver so the pin initialization structures are generated correctly.
So, with MCAL, you will need to configure the pins in both the Pins Tool and the PORT driver (Peripheral Tool). The DIO driver only needs to be configured if those pins will be used as GPIOs.
BR, VaneB