SWD Analyzer plugin improvement

[MarianSavchuk]

This pull request incorporates changes from #4 and additionally enables the decoding of SWD data and control sequences captured by waveforms, per ARM ADIv5, ADIv5.2, and ADIv6.

A brief list of improvements:

• List of available SWD control sequence elements that can be detected:
  • Line reset ( at least 50 SWCLKTCK cycles with SWDIOTMS HIGH )
  • JTAG-to-SWD (Legacy)
  • SWD-to-JTAG (Legacy)
  • IDLE cycles
  • DS Pre-Selection Alert (at least 8 SWCLKTCK cycles with SWDIOTMS HIGH)
  • DS Selection Alert
  • DS Pre Activation Code
  • JTAG-Test-Logic-Reset (at least 5 SWCLKTCK cycles with SWDIOTMS HIGH)
  • DS-to-JTAG (activation code)
  • JTAG-to-DS
  • DS-to-SWD (activation code)
  • SWD-to-DS
• Introduced current protocol (SWD/JTAG/DS) state machine
• The number of turnaround cycles is set per DLCR register read/write operation
• Sticky overrun behaviour is set per CTRL/STAT.ORUNDETECT read/write operation
• DP and AP version is detected based on the value that is read from DPIDR
• DP and AP register values are decoded according to their version
• Configurable initial values of:
  • Debug Protocol
  • Last sequence
  • DP Version
  • Number of turnaround cycles
  • Sticky overrun behaviour

[HexF]

I gave this branch a bit of a test whilst debugging my SWD implementation.
A few things I note;

• I needed to tell CMake to use C++17
• I needed to move definitions of SEQUENCE_JTAG_SERIAL, SEQUENCE_SW_DP and SEQUENCE_JTAG_DP into a cpp file, rather than the h file they are currently in.
• TARGETSEL isn't handled properly - it doesn't get ACK'd by the chip by design, whereas the analyzer looks for them:
  
• I had to modify SWDAnalyzer.cpp, GetAnalyzerName so there isn't a conflict with the inbuilt plugin (this is probably expected?)

[MarianSavchuk]

@HexF,
Thank you for reporting the errors you found.
They should be fixed in the latest commit.
However, the analyzer name should be modified in GetAnalyzerName to avoid conflict with the in-box SWDAnalyzer plugin.
Could you test this on your setup?
Best regards

[MarianSavchuk]

The latest changes involve parallel recognition of sequence elements, allowing the last transaction to be decoded in sequences, as shown in the screenshot.