Hi!
We have redesigned our board (based on arduino due) and added jtag connector and bought an atmel ice.

To be able to use this I had to upgrade to vs2019.

I have been able to build and debug with it in a simple "empty" arduino due project in vs2019.

BUT when I build our project that builds fine in vs2017 it reports link error in vs2019.

I have attached the output from
vs2017 and from vs2019 both with debug on hardware and without debugging

We have found a bug in the arduino library code for the Uart, so we have added the source code for the UartClass to our project and it builds and runs ok with vs2017


the diff is in the write function

original:

size_t UARTClass::write( const uint8_t uc_data )
{
  // Is the hardware currently busy?
  if (((_pUart->UART_SR & UART_SR_TXRDY) != UART_SR_TXRDY) |
      (_tx_buffer->_iTail != _tx_buffer->_iHead))
  {
    // If busy we buffer


our bug-fix version:

size_t UARTClass::write( const uint8_t uc_data )
{
  // Using static since it is faster, no stack operation
  static bool put_in_buffer;
   
  // Make sure that UART_SR_TXRDY and _tx_buffer is not changed by IrqHandler during evaluation
  __ASM volatile ("cpsid i");
  put_in_buffer = (((_pUart->UART_SR & UART_SR_TXRDY) != UART_SR_TXRDY) | (_tx_buffer->_iTail != _tx_buffer->_iHead));
  __ASM volatile ("cpsie i");
   
  // Is the hardware currently busy?
  if (put_in_buffer)
  {
    // If busy we buffer


Can you please help me found why I can't build this in vs2019

Best regards,
Anders Eriksson

Hi

On the 2017 version you have switched off "vMicro>Compiler>Deep Search for Libraries". This setting can be switched off if the .ino code has an #include for all the libraries that you need.

On the 2019 project you have switched off optimization which the core you are using is not designed to allow. You can see this in the output "-O0".

I suggest that switching the optimization to default is probably the solution because the library search looks okay, although possibly not needed in your project.

Hi again,

I see now when comparing the output that the vs2017 output has;

ide.default.revision_name=1.9.0

whereas vs2019 has
ide.default.revision_name=1.8.13

where can I change this setting to test this?

Thanks,
Anders

Deep search library OFF didn't help either, see attached output file.

Link error in both, see attached output files

But how does this setting differs between running visualmicro in vs2017 and vs2019, remind that it builds fine in vs2017?

And I can't remember me or any of my other colleagues have been changing this flag

I did email you the complete project yesterday to sales@visualmicro.com

Thanks,
Anders

the 3 optimization flags are not existing in the vs2017 project settings, see attached screen-dumps of the project settings inside vs2017 and vs2019

I continued to test different combinations of these 3 new opt disable flags and found that only the disable optimization for project is necessary, but still prog size is 5% bigger, see attached screen-dump

Hi yes -Os is shown in the output for both building in vs2017 and vs2019, but what about the prog size difference, about 30Kbyte more with vs2019?

Certainly I really would like this to be solved.

Note the prog sizes 
for vs2017:
Program MotorController size: 132 444 bytes
but for vs2019:
Program MotorController size: 162 588 bytes