I have Visual Micro (paid, registered) installed on one computer (computer A), and I can compile/run my application no problem.

I then switch to another computer (computer B - free trial) and set up everything the same way, however when I go to run/debug the application on that computer, I run into the following problems:

- the build events that I have defined in the custom boards.txt file do not appear to be getting run unless I tick the "vMicro->Compiler->always export binary"... specifically, the following recipe hook doesn't seem to work on computer B until I ticked that box on computer B: recipe.hooks.savehex.postsavehex)
- visual micro appears to add a breakpoint to main.cpp (not my main.cpp, but the one in the MiniCore core files) --> this doesn't happen on computer A
- my application gets stuck on a line that is waiting for the Timer2 peripheral's prescaler to finish being latched by hardware--> this doesn't happen on computer A

Here are the things that are the same between computer A and B:

- Microchip studio v 7.0.2594
- Arduino 1.8.8 IDE
- MiniCore v2.2.2 (board manager)
- Platform: ATmega328PB with Bootloader

And here are some  things that are different:

Visual Micro Version:

computer A --> Arduino IDE for Microchip Studio (2023.507.703)
computer B -->  Arduino IDE for Microchip Studio (2023.507.714)

I'm guessing that since the core files are the same, that this must have something to do with differences in how the project is compiled between these two versions of visual micro?  Does that make sense?

Here is the line of code that debugging gets stuck on when running my application on computer B:

while((GTCCR & (1<<PSRASY)){};
 

I noticed that when stepping through the early-init code (the main.cpp in MiniCore core files that Visual Micro is putting the breakpoint in), that there appears to be a spot in wiring.c in the init() function which configures TC2, and I'm guessing that this is messing with my app's code and causing the while loop (above) to be an infinite loop.

Is it possible that rolling the version of Visual Micro installed on computer B back to the version installed on computer A would fix these issues?

If so, how do I roll back visual micro from 2023.507.714 to 2023.507.703 ?



What are the "gotchas" that I should know about when I'm trying to work on the same visual micro project on two different computers (using Git to push/pull my development files)?


I've attached some of the relevant config files.