Ok, setting Remote Transport to FastSerial it compiles also in compile mode.
But there is no difference in the output screens between compiling in Release and Debug modes (changing nothing else).

Anyway, is it possible to watch the PC13 port registers or what else from that port?

The serial debugger can debug on any built in "Serial" such as Serial1, Serial2 or it can use SoftwareSerial.

This document shows how to use SoftwareSerial. In short, you just need to set the Transport=SoftwareSerial, LocalSpeed to 56k or less, then enter one or two pins into RemoteTx and RemoteRx and set the LocalPort to the COM that connects your usb to pins. (Do NOT set the RemotePort that is for special advanced use). Use simple Arduino numbers in RemoteTx and RemoteRx such as RemoteTx=5 and RemoteRx=6

https://www.visualmicro.com/page/User-Guide.aspx?doc=Debugging-With-Different-Po...

NOTE: Depending on your board, SoftwareSerial works better if the pins are interruptable. Set the LocalSpeed to 56k or less. Most boards have serial data corruption with softwareSerial over 56k.

Yes Serial means any type of Serial and that can also include wifi some board. It's difficult to find the right words. 

Really there is hardware debugging (GDB) and then there is "Serial" debugging which is actually software debugging that uses injected debug statements during the build process. We don't currently call the Serial debugging "software" because it is too easily confused with SoftwareSerial which is just one of the "Serial" options.

Too many Software and Serial words

What do you mean by "peripheral port monitor". Maybe you are asking about our wifi debugging for esp8266 and esp32 or something else?

Yes you can do that with the Hardware debugger options in Visual Micro. The hardware debugger gives ability to step and also to inspect and change all values live.

The serial debugger is simpler and easier for newer users and imporves productivity for all but more advanced needs. It is also stronger than hardware debugging for high speed trace and plotting.

Both types of debugger are available in Visual Micro.

See the Debugging tab on this page, scroll down for hardware debug via STlink pins.

https://www.visualmicro.com/page/STMicroelectronics-STM32-Overview.aspx

or take a look at this page for STM32 debugger support.

https://www.visualmicro.com/page/STM32-Debugging.aspx

See the "Docs" link at the top of visualmicro.com for more info

Documentation Index

This image shows hardware debug but OI couldn't find an image that shows the Watch expressions (objects) that can be expanded and explored. Try it out there is lots of featues to explore. The digital outputs aren't as pretty as some tools, such as Atmel Studio, but the values are visible. You can right click the code and "Add Watch" or right click the Watch list and "Add Watch". All data types are supported such as array and object.

Could you also attach the below log file, just so we can see the OpenOCD Logging too?

_vmicro.ino_DebugOpenOCD.log 

To work with our OpenOCD Setup it needs to be the WinUSB (v6.1.7600.16385) as shown on the right of the image.

NOTE - To use it afterwards with the Native JLink Tools (and potentially other software) this needs to be rolled back using their package to re-install the JLink driver you currently have.

Before we move onto Uploading - Does the Debugging now work using JLink and OpenOCD, now the driver has been updated?

The JLink software works differently. If you have more than one JLink plugged in at a time, there are additional parameters which can be passed to specify which JLink to use, if that is the case?

This Topic was moved here from Usb/Serial/WiFi Debugging [move by] Visual Micro.