May 4th, 2025 at 4:26am (UTC)
 
 

Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
  		Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
  VS Arduino › › › 22.02.18-0 VS 2017-2019, 2022
‹ Previous Topic | Next Topic ›
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic 22.02.18-0 VS 2017-2019, 2022 (Read 521 times)
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2695
Joined: Feb 13th, 2019
22.02.18-0 VS 2017-2019, 2022
Feb 18th, 2022 at 2:37pm
Print Post  
Installer Note: If the install for Visual Studio fails, right click and "Open With>Visual Studio Version Selector"

*** NOTE VS 2022 - If you installed a PRE-RELEASE version of Visual Micro for VS2022 (before 21.11.08.0) please uninstall and install from the gallery, or the link below
***

Download Visual Micro 22.02.18.1900 for Visual Studio 2017/2019
Download Visual Micro  22.02.18.2200 for Visual Studio 2022

  • Fix: Build: Library Caching fix added to greatly speed up second and consequent builds 
  • Fix: Serial Debug: Memory Monitor added for ESP32/ESP8266 boards (Reported Here)
  • Fix: Serial Debug: Memory Monitor Line not displaying in Dark Theme resolved
  • Fix: Intellisense: ZWave Uno Beta Boards (Reported Here)



Download Visual Micro 21.11.08.1920 for Visual Studio 2017/2019
Download Visual Micro  21.11.08.2220 for Visual Studio 2022

  • Updated Fix: Hardware Debugging approach updated for newer ESP32 Modules e.g. WROVER-E (Reported Here, and here)
    NOTE: This is currently behaving differently to our standard installations in the following ways:-
    - You must set one breakpoint in your code before starting the debugging session.
    - Breakpoints can only be added/changed when you are stopped on a breakpoint.

    Add below Local board.txt entries to try this:
    Code
    Select All
    debug.toolingsystem=gdbscript
# Most stable OpenOCD Version for newer ESP32 Boards
tools.openocd.debug.path={runtime.tools.openocd-esp32-0.10.1-2021.07.21.path}
# Very Latest OpenOCD (seems less stable than the above)
# tools.openocd.debug.path={runtime.tools.openocd-esp32-0.10.1-2021.11.11.path}
  • Fix: Teensy COM Ports cleared down after disconnect (within 10s) (Reported Here)
  • Fix: Project Caching for all configurations, ensuring CPP and INO files are cached correctly
  • Fix: Improved Project Caching when Hardware Debug disabled, ensuring Project CPP files are cached correctly
  • Fix: Improved handling for hook patterns ensuring UTF8 characters are handled fully in Sketch/Core/Library paths
  • Added new board.txt property to disable Deep Search vm.runtime.compiler.auto_discover_includes=false
  • Optimization: Override Hardware Debugging Optimization using board.txt property ide.compiler_flags_debug (default is -Og) (Reported Here)
  • Fix: Teensy4 Board Options not showing on older TeensyDuino installs (pre 1.54)
  • Fix: Improved Debug/Upload for STM32 (Official) Boards (STM32 G0/1 L0/1/4 WL WB Boards) (Reported Here)
  • Fix: Clarified Menu Options for Advanced Library Usage
  • Fix: Encoding and Quoting of Disassembly/Hex/Compiled Binary output paths 
« Last Edit: Mar 1st, 2022 at 2:25pm by Simon@Visual Micro »  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint
‹ Previous Topic | Next Topic ›
 
  « Board Index ‹ Board Top  

VS Arduino » Powered by YaBB 2.6.12!
YaBB Forum Software © 2000-2025. All Rights Reserved.