Code

#define HWSERIAL3  Serial3 

Code

#define HardwareSerial3 Serial3 

Code

WhisperSom_01s.ino:In function 'void setup()
WhisperSom_01s.ino:189:71: error: no matching function for call to 'VisualMicroDebug::begin(Serial3*, int)
:void setup() {
    debugger: The error shown above might be caused by invalid breakpoint syntax or the board is not yet supported for debugging (pls let us know!)
WhisperSom_01s.ino:candidates are
WhisperSom_01s.ino:In file included from
VM_DBG.h:begin(usb_serial_class*)
:void begin(usb_serial_class *theSerial)
VM_DBG.h:note    candidate expects 1 argument, 2 provided
VM_DBG.h:begin(usb_serial_class*, long unsigned int)
:void begin(usb_serial_class *theSerial, unsigned long baud)
VM_DBG.h:note    no known conversion for argument 1 from 'Serial3*' to 'usb_serial_class*
Error compiling project sources
 

1. The concept of monitor windows seems to be very strongly coupled to the concept of the upload / debug port. 
   
   If I use the toolbar to open a serial monitor window on any port, VisualMicro attempts to start debugging on that port. 
   
   The documentation says that I can open multiple monitor windows, but if I do open a new monitor window during a debug session, the Upload Port is automatically changed to that window and the current debugging session stops in visual studio (but continues to run in the device). 
   
   If I then reconnect the original serial monitor window and type 'c', the debug session functions and the highlight changes on the VisualStudio screen, BUT the step button remains grayed out and F5 does not function. Also, 'c' causes the program to advance through two loops instead of one.
2. If I set Upload port to an existing hardware or software serial port (Com9), VisMicro thinks it is using that port for upload and for debugging, and it opens a monitor window for that port. However, the *actual* upload is still happening on the original USB port (virtual Com14) and subsequent debug communications are also still happening on Com14. 
   
   When this happens, the step button is grayed out and F5 does not work.  However, if there was a preexisting monitor window for Com14 and I connect that window, pressing 'c' in that window does cause the debug session to cycle twice.
   
   I believe the Teensy uploader will *always* use the direct USB port for uploading. 
3. During debugging, disconnecting any serial port monitor (not just the one over which debug commands are passing) stops the debugging session in Visual Studio.