- 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
- :
- 2384026_en-US
2384026_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2384026_en-US
2384026_en-US
I am currently using the S32K3X8EVB-Q289 evaluation board and have developed a custom hardware design based on the S32K358 MCU.
Could you please clarify:
- Is programming/debugging an external S32K358 target using the EVB's on-board debugger officially supported?
- If supported, what jumper settings or hardware modifications are required on the EVB?
- Which debug connector should be used for this purpose?
- Are there any limitations compared to using an S32 Debug Probe ?
- Is there any documentation or application note describing this configuration?
Thank you for your support.
Regards,
Yash Gupta
Hello @Yash2530 ,
1. Yes, using the S32K3X8EVB-Q289 on-board debugger to program/debug an external S32K358 target is supported. Actually, the EVB’s on-board OpenSDA debugger uses a P&E Micro-developed bootloader/debug application - https://community.nxp.com/t5/S32-Design-Studio/Which-debugging-interface-is-better/m-p/1715877
2. No soldering rework or jumper setting is required on the EVB for this use case.
3. J55 USB host connector.
4. In practice, for standard flashing and source-level debug of an external S32K358 target, the EVB’s on-board debugger should be sufficient. Since I don't know what feature is important to you, please compare features by yourself:
https://www.pemicro.com/products/product_viewDetails.cfm?product_id=15320180&productTab=5045
5. Yes, https://www.nxp.com/webapp/Download?colCode=S32K3X8EVB-Q289HWUM
Best regards,
Pavel