Hello there,

I am new to Visual Micro and have for a long time wanted to try this Visual studio integrated tool for my builds.

I have a project written in Arduino IDE 2 where i have used a library called NeoHWSerial for better serial control and to raise the serial buffer to 200. 

Another way of increasing the buffer size is just altering the Arduino core library through the SERIAL_TX_BUFFER_SIZE 
SERIAL_RX_BUFFER_SIZE #defines See topic: Changing Arduino Core HardwareSerial.h Defines

But then it is not compatible with the Arduino IDE´s core library anymore.
So in Arduino IDE I used NeoHWSerial in the beginning to adress this issue and as long as there is no callings to the Arduino serial class, there is no conflicts between these libraries.

So the problem is that i am struggling in Visual Micro because of this. When using the Debug option to use breakpoints and all the cool stuf, i get a conflict from the orignal HardwareSerial library from Arduino core. It suggest that VM is calling the serial class for its code to work.
When adding NeoHWSerial as a library to my sketch i get following message:

HardwareSerial0.cpp.o (symbol from plugin)*: In function Serial
(.text+0x0)*: multiple definition of __vector_25
NeoHWSerial0.cpp.o (symbol from plugin)*: (.text+0x0): first defined here

I have tried using Override remote port or transport under debugger in VM but i cannot manage to attach the NeoSerial class instead of the serial class.

So one of the Remote transport options is also FastSerial. So i tried using that option and that library to get a positive result. But it is the same problem. 
Selecting the FastSerial option under Remote transport just gives me the following message:

HardwareSerial0.cpp.o (symbol from plugin)*: In function Serial
(.text+0x0)*: multiple definition of __vector_25
FastSerial.cpp.o (symbol from plugin)*: (.text+0x0): first defined here

So i hope that someone can help me addressing this issue so i can use the debugging functionality along with the NeoHWSerial library.

I have attached a barebone solution of the problem.

Thanks in advance.

Hi Simon,

When utilizing the debug feature, I encounter a conflict with the hardware serial code. However, this conflict does not manifest when the debugger is set to release mode. This situation mirrors the issue observed in the Arduino IDE, where any invocation of the serial class results in a similar conflict. Based on this observation, it is reasonable to infer that your debugger is likely making a call to the serial class as well.

Arduino IDE Core Library and #defines

I would like to clarify my previous statement regarding the Arduino IDE core library. The core library remains unaltered when my code is opened in the Arduino IDE. Consequently, while the #defines function correctly in Visual Micro (VM), they do not have the same effect in the Arduino IDE.

Potential Solutions and Considerations
While modifying the Arduino IDE core library is a potential solution, it is important to note that this approach would impact all future code. Although workarounds exist, I had initially assumed that Visual Micro already incorporated a feature to circumvent this issue.