- 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
- 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
-
- NXP Tech Blogs
- Home
- :
- General Purpose Microcontrollers
- :
- Kinetis Microcontrollers
- :
- Can I reconnect to MK64FN1M0XXX12 after accidentally reconfiguring debug pin?
Can I reconnect to MK64FN1M0XXX12 after accidentally reconfiguring debug pin?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Can I reconnect to MK64FN1M0XXX12 after accidentally reconfiguring debug pin?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was able to flash my MK64FN1M0xxx12 MCU using JLink until I flashed some sample code which seems to reconfigure one of the pins used for the debug connection. Is there any way to reset the pins without being able to connect?
The JLink commander error:
Device "MK64FN1M0XXX12" selected.
Connecting to target via JTAG
InitTarget()
Connect Under Reset
Connect Under Reset
Connect failed. Resetting via Reset pin and trying again.
InitTarget()
Connect Under Reset
Connect Under Reset
****** Error: InitTarget(): PCode returned with error code -1
InitTarget()
Connect Under Reset
Connect Under Reset
Connect failed. Resetting via Reset pin and trying again.
InitTarget()
Connect Under Reset
Connect Under Reset
****** Error: InitTarget(): PCode returned with error code -1
Cannot connect to target.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You might try the approach described in https://mcuoneclipse.com/2022/06/16/resurrecting-bricked-nxp-kinetis-devices/
The 'Resurrect' of the J-Link might help, but I hope you have a P&E Multilink which has a dedicated recovery tool which helped me in similar cases.
Erich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. Unfortunately the resurrect feature fails to connect too. I don't have access to a Multilink. Could there be a way to achieve the Multilink power glitch technique with the J-Link?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You might try to press the reset buttons at the right moment while connecting. Chances are probably low, but just give it a try.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The other idea is: the K64 has a EZ port (kind of bootloading through SPI). You might have a look at that one too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For completeness, is the only way my device could not connect under reset if the reset pin had been re-assigned somehow? Looking closer at the code I don't see anything that should have caused the problem (some pin configurations but not touching the debug pins), but it seems like reassigning the pins was the only thing which could have caused this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Basically there could be many things: from power supply issues, cable/connection issues up to problems on the device itself. Basically usually the debug probe finds out that the device is not responding. I had cases where the debug probe cable had an issue, others with USB cable issues, yet others with devices damaged by ESD somehow, up to locked devices because of security/flash configuration settings. Debug pins disabled is just one thing. Having the reset pin disabled is usually not an issue as long the debug interface is still responsive.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
