- 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
- :
- frdm-kw36 no connection to chips debug port
frdm-kw36 no connection to chips debug port
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
frdm-kw36 no connection to chips debug port
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have manage to load, build, and debug some example programs from the SDK_2_2_12_FRDM-KW36 file for the frdm-kw36 board. I even have a program flashed onto the MCU that allows my phone to connect to the chips Bluetooth broadcast. However, I unplugged the board and re-plugged it back in for another example project and I can no longer connect to the chips debug port. I get this error specifically:
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
============= SCRIPT: kinetisunlock.scp =============
Kinetis Unlock Script
Error: Wire Ack Fault - target connected?
Assert NRESET
Reset pin state: 00
Power up Debug
Error: Wire not connected
Error: Wire not connected
No Debug Power
============= END SCRIPT ============================
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1
I'm not sure what to do and have looked through other peoples posts with similar problems without success:
https://community.nxp.com/t5/MCUXpresso-General/FRDM-KW36-Wire-ACK-Fault-in-DAP-access/td-p/863513
Anyone have any suggestions? This seems like a common issue.
EduardoZamora
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Hope you are doing well.
As you might know, some of the wireless examples put the device into low power mode, in which the debug-related modules are kept static or powered off depending on the low power level and the board may not be found on discovery.
Could you please confirm if you have tried the following procedure? When trying to flash/debug your application, try to wake up the device by pressing repeatedly SW3/LLWU or Reset button (board) immediately after selecting "Debug" and while target discovery is trying to connect to the device.
If you are using a BLE example project, depending on the base project, inside app_preinclude.h you may find some macros related to low-power such as gAppLowpowerEnabled_d; please disable (set to 0) this macro. After this, please try flashing/debugging the demo under this configuration.
Also, the Resurrect Kinetis device feature, part of the GUI Flash Tool, may be helpful.
Regards,
Eduardo.
