Improve analyzer debugging experience on Windows with Visual Studio

Debugging new analyzers with Windows can be tricky for a couple reasons --

1) You cannot debug with the latest versions of the Logic software. You have to use an older version (1.1.18 32-bit), which does not work with the newest Logic analyzers.

2) You cannot import logic captures made with newer versions of the Logic software into version 1.1.18, because the serialization format of the logic captures has changed.

The ways I've thought of to get around these problems developing a analyzer for Infineon DAP include:

1) Debug analyzer using simulations made with existing analyzers (SPI and JTAG, for example). However, using this method, I cannot introduce all the test cases I want.

2) Design the simulator portion of the protocol analyzer. However, due to the complexity of this protocol with many test cases and states, this is a difficult task of its own; and I'd much rather test the protocol with captures taken from the output of the DAP miniWiggler.

3) Use a virtual machine with a different operating system and different IDE. However, I'm not terribly interested in using a different IDE I'm not familiar with, since it will take a bit of time to get used to (something I don't have much of right now).

Anybody have any better ideas?

  • jafeucht
  • Jul 11 2018
  • jafeucht commented
    July 11, 2018 20:20

    Hey, thanks for the advice. I think if I had known to try that earlier, I could have saved a lot of time. Next time, I'll definitely try that out!

  • Mark Garrison commented
    July 11, 2018 20:20

    Sorry for the trouble, this is something we have a plan to fix now, but we won't be able to implement it for a while, we're working on the data processing pipeline first.
    To get a real capture into the analyzer, the best workaround would be to export the capture from the latest software to CSV, with the setting "one row per transition". Then you could write the simulation data generator to parse and simulate that saved CSV file.