µC/Probe Benefits

You are here : Micrium : Products : µC/Probe : Benefits

Overview

Communication Protocols

Windows Evaluation

Licensing

Pricing Information

What problem does µC/Probe solve?

Allows you to ‘see’ the dynamic behavior of your system

  • Can’t do this with debuggers
  • printf() statements are not enough
  • Not all embedded system are equiped with a graphical display

‘Visualize’ your system

Avoid designing a user interface
— µC/Probe can be your user interface

FEATURES and BENEFITS

Collects and displays target data at run-time
 Any variable
Any memory location
Any I/O port
Works with ANY processor 8-, 16-, 32-, 64-bit or DSP
Works with ANY compiler Compiler/linker needs to generate a .ELF file
Target doesn’t need an RTOS Works with or without an RTOS
Fast update rate > 200 variables/sec - HEW Target Server
> 200 variables/sec - J-Link Interface
> 500 variables/sec - RS-232C Interface
> 4,000 variables/sec - USB
> 6,000 variables/sec - TCP/IP Interface


Visualization


‘Visualize’ of your system using
  • Gauges and Meters
  • Numeric indicators
  • Graphs and Plots
  • Barcharts
  • Tables
  • Virtual LEDs
  • Etc.

When do you use µC/Probe?


As soon as you have hardware
  •    No need to add special hardware for µC/Probe

    • As soon as you have variables to monitor
  •    No need to instrument your code

    • During debugging
  •    ‘Standard’ debuggers only allow you to monitor variables statically (only when you hit a breakpoint)

    • Once the product is deployed
  •    By service technicians

    •