What is ProBug Debugger Board

Short Intro on ProBug Debugger Board

The ProBug Debugger is a cost-effective and reliable tool designed for debugging and programming NXP Semiconductors S32K Platform microcontrollers. This versatile debugger is compatible with all microcontrollers in the S32K Platform that are based on ARM Cortex M series processors, including ARM Cortex M0/M3/M4/M7, and more. The supported SoC names include S32K1xx and S32K3xx.

ProBug Debugger is idle choice when working on custom embedded product development or learning/training/prototyping purpose on NXP S32K automotive Microcontrollers. Looking to start with NXP S32K platform for development, ProBug debugger would be reliable and cost-effective debugger that can be used across S32K MCU’s.

Previous slide
Next slide
SWD Debugging Protocol
Utilizing the SWD interface, the ProBug Debugger seamlessly connects with target S32K microcontrollers through Debug Connectors present on ProBug Debuggers.
Supported Software/IDE's
ProBug Debugger can be used efficiently with following Embedded Software toolchain's: S32 Design Studio/FreeMaster/MBDT tools/Jlink Software Toolchains
Jlink Debug Configuration
ProBug Debugger is detected as Jlink Debugger on connection with Host Desktop/Laptop.
Supports S32K1xx MCU's
S32K116, S32K118, S32K142, S32K144, S32K148, S32K142W, S32K144W
Virtual UART Com Port
ProBug Debugger is also detected as Virtual UART Com Port as we connect it to the Host PC, for real time UART logging.
Supports S32K3xx MCU's
S32K311, S32K312, S32K314, S32K322, S32K324. S32K342, S32K344, S32K358, S32K388
// Kew Features

Technical Specs &
Features of ProBug Debugger

2 Debug Connectors for connecting to Target S32Kxxx Microcontroller
2 Debug Connectors for connecting to Target S32Kxxx Microcontroller

10-pin SWD connector and 20-pin JTAG connector

Segger Jlink Debug Port
Segger Jlink Debug Port

Jlink Debug Port Detection for Programming and Debugging S32K MCU's

Target MCU Power Configuration
Target MCU Power Configuration

Target Microcontroller can be Powered via 3.3V or 5V. That is configurable via Power Header

Virtual UART Serial Com Port
Virtual UART Serial Com Port

Virtual UART COM Port Detection via same Debug connector for logging Realtime data via UART Peripheral.

Connection to Host Laptop/Desktop
Connection to Host Laptop/Desktop

Connect to Host Laptop/Desktop via USB-to Type C Cable

On-Board Reset Button
On-Board Reset Button

On Board Reset Button for resetting Target MCU via ProBug Debugger

Pricing & Buy

Start With An
Affordable

Chinese Clone Jlink Debuggers

<INR5K/ piece
Not Reliable
  • Big in Size
  • Chinese Clone
  • Non-Isolated
Cost Effective, but not reliable and recomended

ProBug Debugger

INR7.5K / piece
Domestic Shipping
  • Readily available
    • Indigenous Product (India)
      • Custom Bootloader (Not Chinese)
        • Galvonic Isolation
Cost Effective and for Industrial Usecases

ProBug Debugger

INR5.0K/piece
Domestic Shipping
  • Readily available
    • Indigenous Product (India)
      • Custom Bootloader (Not Chinese)
        • Non-Galvonic Isolation
Cost Effective, Industrial product for students and academia

Original Jlink and PEMicro Debuggers

<INR30K/piece
Very Costly
// Packet Contents

With ProBug Debugger

Applications

Usecases of ProBug Debugger

ProBug Debugger with NXP S32K312(ARM Cortex M7 Processor)

ProBug Debugger with NXP S32K144(ARM Cortex M4 Processor) using ElecronicsV2 Board

// User Manual and User Guide

To use ProBug Debugger

User Manual of ProBug Debugger
Getting Started Manual of ProBug Debugger

Automotive Microcontroller programming training session at DTU College

We have successfully conducted a 10-day training program on Automotive Microcontroller Programing at Delhi Technical University from 6th December to 15th December. The training program was attended by Btech Students of ECE branch and some students of Mtech branch. List of attendance as per dates are: 06/12/2024:25 07/12/2024:25 08/12/2024:23 09/12/2024:22 10/12/2024: Holiday by students 11/12/2024:23 12/12/2024: 22 13/12/2024:19 14/12/2024:15 15/12/2024:10 The 10 day training program session start by introducing students with the Microcontroller Technology. On day 1 of the training session students were made to taught microcontroller technology. General overview of what is semiconductor industry, how does semiconductor industry works and different kind of companies in semiconductor industry. Followed by in depth exploration of microcontroller technology, which is one of the kind of semiconductor chip. Diving into Building block, Functional block, Hardware Development Kit and Software Development Kit of Microcontroller Technology. In the end we conclude the day by discussing about Industrial Microcontroller like that of NXP, Renesas, Infenion giving students exposure to MCU’s apart from Arduino/ESP frameworks. We very much focus on NXP S32K144 MCU which is an automotive MCU and get handson feel with Its Development Board ElecronicsV3 and SDK of S32 Design Studio On Second day we followed by exploring and diving deep into automotive technologies. How Automotive Industry works, Different companies involved in it and overview of Automotive technologies like Functional Domain, E/E Architecture and Autosar Software Tech Stack. On this we very much deep dive into Autosar Software Tech stack and give stduents overview on how to start with it. We start by exploring the MCAL Layer technology of Autosar Software Tech Stack and set up its Software environment using S32 Design Studio IDE and its software package installation. On Day 3-4 we started with Handson experiment after getting initial overview of technologies. On Day 3 & 4 students explored the GPIO/PORT peripheral in Microcontroller technology, students were given in depth overview and understanding on how this peripheral works, why is it used, how to use it and its applications. Students were made to taught about this peripheral from Microcontroller datasheet and made to understand different specs/features of this peripheral from MCU documents. After that students were made to taught how to use this peripheral in Automotive Microcontroller by making them understand on its peripheral stack using Autosar MCAL Driver specs. Students were made to taught how to use Autosar Code configurator tool for GPIO/PORT peripheral. They were taught how to use Software API’s, what parameters to send on those API’s an in which chronology those API’s need to be used. In the end students were given time to learn and have Handson with Embedded Softwrae Debugging of microcontroller. They were made to develop different functional demo codes on GPIO/PORT peripheral and taught how to do embedded software debugging for it. Day 5 was holiday: After continous 4 days of technical learning and information, students asked for day off. Number of students on that day have interviews and assessments so day off on this day was taken. Day 6-7: we started with Handson experiment of ADC peripheral of microcontroller technology. We started by getting overview on what is ADC peripheral, how does it work, why is it needed and different specs/features of ADC peripheral in MCU’s. After that we deep dive into NXP S32K144 concentric ADC peripheral. We explored how ADC peripheral works in S32K144 MCU using its datasheet and exploring its peripheral register’s. After that students were made to taught how to use ADC peripheral in Automotive Microcontroller by making them understand on ADC peripheral Driver using Autosar MCAL Driver specs. Students were made to taught how to use Autosar Code configurator tool for ADC peripheral. Understanding and exploring its different menu sections, sub menu sections. Which sections to configure, how to configure and why to configure. They were taught how to use Software API’s of ADC Driver stack, what parameters to send on those API’s an in which chronology those API’s need to be used. In the end students were given time to learn and have Handson with Embedded Softwrae Debugging of microcontroller for ADC Peripheral. They were made to develop simple functional demo codes of reading POT values using ADC peripheral and taught how to do embedded software debugging for it. Day 8-9:  On these 2 days students were made to taught PWM Peripheral of Microcontroller technology. How PWM signals are generated, how they work , different sepcs/features of PWM Signals. Students were made to introduce the concept of TIMER peripheral in MCU’s which is used to generate PWM signals via it. In these 2 days students were also made to get familarize with Logic Analzer tool which is used to capture PWM Signals. Students were made to understand TIMER peripheral of NXP S32K144 Automotive MCU, how it works and how to use it for generating PWM signals. Followed by theory and hardware overview of PWM signals, students were made to do Handson exploration by generating PWM signals of different frequency/duty cycle using PWM Driver stack of Autosar MCAL Layer. After that students were made to taught how to use TIMER peripheral in Automotive Microcontroller by making them understand on PWM peripheral Driver using Autosar MCAL Driver specs. Students were made to taught how to use Autosar Code configurator tool for PWM Driver. Understanding and exploring its different menu sections, sub menu sections. Which sections to configure, how to configure and why to configure. They were taught how to use Software API’s of PWM Driver stack, what parameters to send on those API’s an in which chronology those API’s need to be used. In the end students were given tasks to generate PWM signals of different frequencies and duty cycle. On the last day, students were instructed to do Integration of What all thinsg they have learned so far. They were given task to Combine all Peripheral of Automotive MCU which was taught as if now in a single project. They did a task of using GPIO, PORT, ADC & PWM Peripherals

Read More »
Kunal Gupta
Author: Kunal Gupta

What is ProBug Debugger Board

Short Intro on ProBug Debugger Board

The ProBug Debugger is a cost-effective and reliable tool designed for debugging and programming NXP Semiconductors S32K Platform microcontrollers. This versatile debugger is compatible with all microcontrollers in the S32K Platform that are based on ARM Cortex M series processors, including ARM Cortex M0/M3/M4/M7, and more. The supported SoC names include S32K1xx and S32K3xx.

ProBug Debugger is idle choice when working on custom embedded product development or learning/training/prototyping purpose on NXP S32K automotive Microcontrollers. Looking to start with NXP S32K platform for development, ProBug debugger would be reliable and cost-effective debugger that can be used across S32K MCU’s.

Previous slide
Next slide
SWD Debugging Protocol
Utilizing the SWD interface, the ProBug Debugger seamlessly connects with target S32K microcontrollers through Debug Connectors present on ProBug Debuggers.
Supported Software/IDE's
ProBug Debugger can be used efficiently with following Embedded Software toolchain's: S32 Design Studio/FreeMaster/MBDT tools/Jlink Software Toolchains
Jlink Debug Configuration
ProBug Debugger is detected as Jlink Debugger on connection with Host Desktop/Laptop.
Supports S32K1xx MCU's
S32K116, S32K118, S32K142, S32K144, S32K148, S32K142W, S32K144W
Virtual UART Com Port
ProBug Debugger is also detected as Virtual UART Com Port as we connect it to the Host PC, for real time UART logging.
Supports S32K3xx MCU's
S32K311, S32K312, S32K314, S32K322, S32K324. S32K342, S32K344, S32K358, S32K388
// Kew Features

Technical Specs &
Features of ProBug Debugger

2 Debug Connectors for connecting to Target S32Kxxx Microcontroller
2 Debug Connectors for connecting to Target S32Kxxx Microcontroller

10-pin SWD connector and 20-pin JTAG connector

Segger Jlink Debug Port
Segger Jlink Debug Port

Jlink Debug Port Detection for Programming and Debugging S32K MCU's

Target MCU Power Configuration
Target MCU Power Configuration

Target Microcontroller can be Powered via 3.3V or 5V. That is configurable via Power Header

Virtual UART Serial Com Port
Virtual UART Serial Com Port

Virtual UART COM Port Detection via same Debug connector for logging Realtime data via UART Peripheral.

Connection to Host Laptop/Desktop
Connection to Host Laptop/Desktop

Connect to Host Laptop/Desktop via USB-to Type C Cable

On-Board Reset Button
On-Board Reset Button

On Board Reset Button for resetting Target MCU via ProBug Debugger

Pricing & Buy

Start With An
Affordable

Chinese Clone Jlink Debuggers

<INR5K/ piece
Not Reliable
  • Big in Size
  • Chinese Clone
  • Non-Isolated
Cost Effective, but not reliable and recomended

ProBug Debugger

INR7.5K / piece
Domestic Shipping
  • Readily available
    • Indigenous Product (India)
      • Custom Bootloader (Not Chinese)
        • Galvonic Isolation
Cost Effective and for Industrial Usecases

ProBug Debugger

INR5.0K/piece
Domestic Shipping
  • Readily available
    • Indigenous Product (India)
      • Custom Bootloader (Not Chinese)
        • Non-Galvonic Isolation
Cost Effective, Industrial product for students and academia

Original Jlink and PEMicro Debuggers

<INR30K/piece
Very Costly
// Packet Contents

With ProBug Debugger

Applications

Usecases of ProBug Debugger

ProBug Debugger with NXP S32K312(ARM Cortex M7 Processor)

ProBug Debugger with NXP S32K144(ARM Cortex M4 Processor) using ElecronicsV2 Board

// User Manual and User Guide

To use ProBug Debugger

User Manual of ProBug Debugger
Getting Started Manual of ProBug Debugger

Stay Updated With Us

Error: Contact form not found.

      Blog