Atmel studio 7

Compiling 'vmicro_test_1' for 'Arduino M0 Pro (Programming Port)'
Build Folder: bg/Release"
Summary: Header=1 Prototypes=3 Imports=0
Additional Defines:
Architecture Tools: eabi-gcc/7-2017q4/bin/"
Api: 1.1911.23-0
Sketch Book: "file:///C:/Users/chris/OneDrive/Documents/Arduino"
Sketch Include Paths
Core Include Paths
Include Path .8.3/cores/arduino"
Include Path .8.3/variants/arduino_mzero"

Deep search for libraries ...
\7-2017q4\bin\arm-none-eabi-g++" -mcpu=cortex-m0plus -mthumb -c -g -Os -w -std=gnu++11 -ffunction-sections -fdata-sections -fno-threadsafe-statics -nostdlib --param max-inline-insns-single=500 -fno-rtti -fno-exceptions -w -x c++ -E -CC  -g -DVM_DEBUG_GDB   -DF_CPU=48000000L -DARDUINO=108011 -DARDUINO_SAM_ZERO -DARDUINO_ARCH_SAMD -D__SAMD21G18A__ -mthumb -DUSB_VID=0x2a03 -DUSB_PID=0x804f -DUSBCON -DUSB_MANUFACTURER="\"Unknown\"" -DUSB_PRODUCT="\"Arduino M0 Pro\"" IS/Include/" .0/CMSIS/Device/ATMEL/" ores\arduino" ariants\arduino_mzero" se\vmicro_test_1.cpp" -o "nul"

Building variant ...

  Using previously compiled variant

Building core ...

Building project code ...
  Using previously compiled file: e\vmicro_test_1.cpp.o

Linking it all together ...
# Coping cached core 2a27b\core.a to e\core.a

\7-2017q4/bin/arm-none-eabi-g++" ease" -Os -Wl,--gc-sections -save-temps ariants\arduino_mzero/linker_scripts/gcc/flash_with_bootloader.ld" dbg\Release/vmicro_test_1.ino.map" --specs=nano.specs --specs=nosys.specs -mcpu=cortex-m0plus -mthumb -Wl,--cref -Wl,--check-sections -Wl,--gc-sections -Wl,--unresolved-symbols=report-all -Wl,--warn-common -Wl,--warn-section-align -o se/vmicro_test_1.ino.elf" "vmicro_test_1.cpp.o" 12a27b\variant\variant.cpp.o" -Wl,--start-group IS/Lib/GCC/" -larm_cortexM0l_math -lm se/core.a" -Wl,--end-group

core.a(Uart.cpp.o)*: In function HardwareSerial::HardwareSerial()
HardwareSerial.h:67: undefined reference to vtable for HardwareSerial

Error linking for board Arduino M0 Pro (Programming Port)
Build failed for project 'vmicro_test_1'
  

It is on default optimization
It only happens on M0 (programming)  not M0 or uno

Things seem to keep changing.
here is where i am now.
Ihave attached two files
first is compiler output when set as M0 board.
it compiles fine, but wont download.
the second is set as M0 (programming port), shich is howit is connected.  It fails for a Hardware Serial fault.
Thoughts?

my settings are the same. see attached

This is because you have set the programmer to Atmel EDBG. Please unckeck vMicro>Upload>Always User programmer"

You are also in Debug mode, I suggest you set the tool bar to Release instead of Debug.

Another point is that the vMicro > Debugger and Optimization settings are set per configuration. Release is one configuration and Debug is another configuration. In this  last example core optimization is set to "No Project and Libraries". In your previous example optimization was set to "None or No Optimization". Optimization should always be On which is the default unless you are debugging. Most arduino boards do not allow "No Optimization" because of the HardwareSerial library.

yes i am in debug, because that is the reason I am using m0 board and atmel studio

Upload in Atmel Studo

If you do not want to use the default serial upload you can use Atmel device programming...

Atmel studio uses different usb drivers to the arduino ide. This means that most programmers fail therefore you wills ee that we recommend setting the "vMicro>Uploader>Progammer>Use Atmel Studio Device Programming"

Debugging in Amel Studio

Regardless of upload method, if you want to use the Atmel studio hardware debugger instead of Visual Micro serial debugger...

Check "vMicro>Debugger>Atmel Studio Debugging"



In Atmel studio, both options can apply only to atmel hardware which you have. I guess you have also set no optimization for project and libraries which is often preferred however some libraries have been written in a way that means they will not compile or link with librray optimization set. A future enhancement to visual micro will provide more granular control of which libraries remain optimized. To test things I suggest you leave optimization on which is the default.

Please post verbose output for the build so that we can see your settings now.

That message you see will only appear if you use one of the other programmers. You need to stay in release mode until you prove the upload tool you want to use. 

Out of interest what are you clicking in the arduino ide to upload? If you are not clicking the special "Upload using programmer" menu item in arduino then you are using the standard upload which will be serial/COM.

Let's get past the upload issues which is unrelated to debugging then look at debugging.

Okay so that shows that you just need to use the standard serial upload in visual micro. The arduino ide has confused things for you because it always shows a programmer is selected but it is not used.

In Visual Micro please switch off the "use programmer" in the upload settings and confirm that the upload is then using your COM port.

Thanks

found output in micro build output

this is the page that I got the boards file change from   https://forum.arduino.cc/index.php?topic=622372.0

To be honest it is easier to help users in Visual Studio than atmel studio. To use atmel studio we simply hand off to atmel and users are expected to know how its tools work and how to test connection etc. There are also more options in atmel studio therefore unless users explain exactly what they have set we end up guessing.

In Visual Studio it's more within the vMicro menus and we get better errors back from problems launching hardware debug.

That's not right. From mid last year we released hardware debugging in Visual Studio. You can use either the software/serial debug or the hardware/gdb debug.

You can also run both atmel studio and visual studio on the same machine and try it out.

When you switch on use atmel debugging we simply hand over to atmel studio.

I asked you some questions previously but you did not answer them. Here they re again.


Is vMicro>Debugger>Atmel Studio Debugger enabled?
What happens when you click "Debug>Attach to Target"?
What board is shown in the atmel studio project properties? (right click proj name)

I noticed that there was no tool library path in the tools/options/device & tool libraries/toollibrary path.
i set it to C:\Program Files (x86)\Atmel\Studio\7.0\tools and did debug/attach to target.
it no longer gives backend not running (no tools)
here is the output

------ Build started: Project: moTest6, Configuration: Debug ARM ------
Build started.
Project "moTest6.cppproj" (default targets):
Target "PreBuildEvent" skipped, due to false condition; ('$(PreBuildEvent)'!='') was evaluated as (''!='').
Target "CoreBuild" in file "C:\Program Files (x86)\Atmel\Studio\7.0\Vs\Compiler.targets" from project "C:\Users\chris\OneDrive\Documents\Arduino\moTest6\moTest6.cppproj" (target "Build" depends on it):
     Using "RunCompilerTask" task from assembly "C:\Program Files (x86)\Atmel\Studio\7.0\Extensions\Application\AvrGCC.dll".
     Task "RunCompilerTask"
           Shell Utils Path C:\Program Files (x86)\Atmel\Studio\7.0\shellUtils
           C:\Program Files (x86)\Atmel\Studio\7.0\shellUtils\make.exe all --jobs 8 --output-sync 
cannot open linker script file samd21e18a_flash.ld: No such file or directorycollect2.exe(0,0): error: ld returned 1 exit status
           make: *** [moTest6.elf] Error 1
           Building target: moTest6.elf
           Invoking: ARM/GNU Linker : 6.3.1
           "C:\Program Files " -o moTest6.elf     -mthumb -Wl,-Map="moTest6.map" -Wl,--start-group -lm  -Wl,--end-group -L"../cmsis/linkerScripts"  -Wl,--gc-sections -mcpu=cortex-m0plus -Tsamd21e18a_flash.ld   
C:\Users\chris\OneDrive\Documents\Arduino\moTest6\Debug\Makefile(95,1): error: recipe for target 'moTest6.elf' failed
           The command exited with code 2.
     Done executing task "RunCompilerTask" -- FAILED.
Done building target "CoreBuild" in project "moTest6.cppproj" -- FAILED.
Done building project "moTest6.cppproj" -- FAILED.

Build FAILED.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========

Thanks, you do not want atmel to try to build so please open build>configuration manager and uncheck your project from build. We only want the debug side of atmel studio.

You also should not be using the atmel device programming, just normal edbg or serial. What we want is same as arduino ide for upload but with as7 for debug.

You do not want atmel to build, so please open build>configuration manager and uncheck your project from build. We only want the debug side of atmel studio.

You also should not be using the atmel device programming, just normal edbg or serial. What we want is same as arduino ide for upload but with as7 for debug.

i have vmicro/debugger/atmel studio degugger checked.
using debug/start debugging and break yields backen not running, no tools

ATSAMD21G18A  same on toolbar

here is the properties window and the toolbar

Tim@Visual Micro wrote on Feb 8^th, 2020 at 1:24pm:


i have it running. breakpoints are working, but i dont see how to step/step into. using the buttons in atmel toolbar results in nothing.  also curious why millis() keeps advancing when the program is halted?

i was running the vmicro debugger.  I switched to the atmel debugger and no project optimization and the screen attached is what I get.

Those are atmel errors so you might get more info by changing the output window from "Micro build" to "Build". The output windows with name that starts "Micro" are visual micro output windows. Atmel has its own.

Try these things in any order.

1) Run a repair on atmel studio via control panel add or remove programs.

2) Create an atmel studio application project and select your board. Click start > debugging to see if it can upload and start the debugger for a standard gcc application.

3) Look at the standard atmel studio project property pages for your project to see which debugger/programmer is selected.

4) Look at tools device programming to see if your device is detected and what config the ide has.

5) Post the verbose micro output when you try to lunch and it fails just so we can see that visual micro isn't doing anything.

There is an update for as7 that allows you to set the micro-controller that the atmel project believes it is using. There isn't a direct connection between the arduino definitions and atmel device names so visual micro has to guess. For SAMD boards Visual Micro is bias to the original Arduino Zero. 

Another AS7 user was using an Adafruit M0 that has a slightly different MCU name. There is a new option on the vMicro>General menu that allows you to switch off Visual Micro attempt to automatically set the Atmel Studio Device. Then you can alter the mcu name to be correct.

Your arduino builds shows the mcu/device name should be SAMD21G18A when your ide is set to SAMD21E18A.

https://www.visualmicro.com/forums/YaBB.pl?num=1580914071

As I said you should try the version published earlier today to the link I posted in my previous comment.

If that doesn't help then you are really looking at an AS7 issue and I suggested previously testing with a simple atmel gcc project to prove the tools are working.

These issues are why we recommend VS over atmel studio. Unless you already know atmel it is a learning curve for arduino users. In atmel studio we have better control over the hardware debugger than in AS7.

It might be worth re-checking the guide for AS7 here

https://www.visualmicro.com/page/Arduino-for-Atmel-Studio-7.aspx

Thanks, those are all atmel errors not caused by Visual Micro.

I switched to atmel studio because it seemed like a simpler environment for an arduino type guy.

Would you suggest I try visual studio, which I have previously used instead of atmel?

I have no toolls available.  see attached.

In your last post atmel studio can not see your board.  EDBG should be in the list, it might be related to my previous note about the wrong process/mcu being assigned to the atmel project.

It is also evident that the last upload you made was with serial debug enabled and NOT using the vmicro>debugger>use atmel studio debugging.