Blog

Synchronous debug and trace for two Infineon AURIX devices

Synchronized multi-processor debug and trace

What's in it for you?

  • Generic solution for synchronized debug and trace
  • Debug/Flash and Trace a multi-processor target (can be one hardware or two different target systems)
  • Latency is <10us (measured with a setup of two AURIX target systems)
  • The optional iSYSTEM Hub extends the iC5700 with additional three FNET and one FBridge port. Through the FBridge port run/stop control of two iC5700 can be synchronized.  A 1m long FBridge (Ethernet alike) cable comes along the HUB and connects to the FBridge port on each iC5700.

What will it do for you?

  • Test functional safety implementation, e.g. fail-operational systems (fault-tolerant systems, redundant systems)
  • Verify the communication and timing requirements of such a communication between two controllers hosting two different applications.

What's supported today?

  • Infineon AURIX TC2x/TC3x
  • One needs: 2x iC5700, 2x Hub, 2x Active Probe DAP and/or AURORA
  • iSYSTEM will add support for other iSYSTEM Active Probes step by step. This enables heterogenous sync'd debug and trace, e.g.,  for Renesas R-CAR or similar designs

Read the complete application note "Synchronous Debug and Trace for two Infineon AURIX targets"

older entries

Make software builds easier...with MinGW

If you have been working in the world of Linux, you get used to a whole host of command line tools simply being available for use during development. … » Read more

How much do embedded systems development errors actually cost?

Ever since I started my career in the semiconductor industry, the seemingly tacit knowledge that errors found later in a project cost … » Read more

Building test into your development process.

In our earlier post we looked at how the intrepid team at "Hudson Technologies" tackled a transient software bug in an oven control system. Taken … » Read more

To test or not to test, that is not the question (part 2)

In part 1 of this blog post, we looked that the coverage metrics that are highly recommended in ISO 26262 for software unit testing of ASIL A through … » Read more

To test or not to test, that is not the question (part 1)

It is interesting to find out what approaches different people use to test their application code prior to delivering it to the market place. For … » Read more

How a decent IDE can help highlight embedded software bugs earlier...

Originally this post was going to review another code failure case in Lisa Simone's book "If I only changed the software, why is the phone on fire?". … » Read more

What's all this trace stuff anyhow?

Previously in this blog we have talked about the value of code tracing for embedded systems development and how trace forms the entrance to being … » Read more

What debugging methods are used to make embedded software safer?

We probably never take the time to think about it when we drive in our cars, but between our hands sits a small explosive device in the middle of the … » Read more

The value of the methodical approach.

It is probably fair to say that we have all made a 'quick change' during code development at some point in our career. And, at some point, that quick … » Read more