- 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
- :
- 2282438_en-US
2282438_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2282438_en-US
2282438_en-US
I am unable to debug the MCU using the S32 Debug Probe.
The status I observe is as follows:
SoC Reset: Asserted
SoC Type: GenericDevice
SoC IDCODE: 0xFFFF
SoC UID: 0xFFFF
When I attempt to start debugging, the following message appears during the board initialization stage:
ccs: Initialization sequence error in command 0x5
In addition, I have measured the MCU RESET_B pin, and it is continuously held at a low voltage level.
Could you please advise how to troubleshoot or resolve this issue?
Thank you for your assistance.
Could you specify used EVB?
I am using a self-designed custom board, not the S32K148 EVB.
The MCU I am using is S32K148HAT0MLLT.
I am using S32 Design Studio (S32DS) together with the NXP Debug Probe.
I have tried both DEBUG_RAM and DEBUG_FLASH build configurations, but I am unable to connect in either case.
The error messages are shown in my previous post.
Regarding the hardware status:
- The RESET_B pin remains at a low level continuously.
- Even without connecting the Debug Probe, the RESET_B pin is still low.
- During power-up, RESET_B does not go high even momentarily.
- There is no external reset IC or supervisor on the board.
- The SoC ID is read as 0xFFFF.
- VDD, VDDA, and VDDIO voltages are normal.
- The RESET_B pin has a 3.3 V pull-up resistor, and I have confirmed that it is not being pulled low by any external circuitry.
- I have also confirmed there is no miswiring.
- The RESET_B pin is connected to SWD pin 6 (nRESET) on the debug connector.
- Even when the Debug Probe is not connected, SWD pin 6 (nRESET) remains low.
- This board was working before, and the issue occurred suddenly during development, so it is unlikely to be a soldering or assembly issue.
At this moment, I am not sure what is holding the device in reset or preventing debug access.
Please help me analyze and resolve this issue. Thank you.