- 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
- :
- 2386378_en-US
2386378_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2386378_en-US
2386378_en-US
Hi everyone,
I’ve been trying for a while to use GPIO29/D2 as an I/O pin. However, when I initialize the pin as an I/O pin
/* Initialize GPIO29 functionality on pin GPIO_29 (pin D2) */
IO_MUX_SetPinMux(IO_MUX_GPIO29);
the program crashes. As far as I can tell, GPIO29 isn’t being used for DQS on the connected Flash ICs via FlexSPI—neither on the FRAM board nor in the IRIS module—so it should be available for use. I’ve been using the lpc_gpio_led_output example as a basis.
I’ve also tried changing the clock settings, but that only led to even more errors.
Are there specific settings I need to adjust here?
Thank you very much for your help.
Best regards,
Andreas
Hello @gasar, hope you are doing well.
Even though the GPIO[29] is not physically connected/used by the flash device, the FlexSPI controller uses DQS configuration by default for the boot ROM from Flash to achieve proper data read timings in loopback, and also its configuration is used by the ROM code, therefore its functionality should not be modified as stated in Table 45 - ISP pin assignments of UM11865.
Sorry for the inconveniences this may cause.
Hi Roman,
thank you for the fast response and for confirming my suspicion. I was hoping that the IO could still be used somehow by adjusting some settings. Unfortunately, now I have to repair all the pcbs by hand
Then I'll write to u-blox and ask them to please update their incorrect datasheet so that others are spared the hassle!
BR, Andreas