Seeking Help: Error with SAMD Boards Driver on Arduino Zero - 1st Day User

[zmarcoz]

I am a newbie here and today marks my first day using my Arduino Zero. I initially installed the 1.18.13 version of the SAMD boards driver as per the instructions. However, after going through several posts, I realized that this version might have some errors. Wanting to ensure a smooth operation, I decided to try out other versions ranging from 1.18.05 to 1.18.13. I made sure to uninstall the previous version before installing a new one each time.

Unfortunately, regardless of the version, I keep encountering the same error message. Additionally, there is a notification stating that my com3 is not connected. I am at a loss on how to proceed from here and would greatly appreciate any guidance or suggestions on how to resolve these issues.

Sketch uses 34564 bytes (13%) of program storage space. Maximum is 262144 bytes.
Global variables use 3448 bytes (10%) of dynamic memory, leaving 29320 bytes for local variables. Maximum is 32768 bytes.
Open On-Chip Debugger 0.10.0+dev-gf0767a31 (2018-06-11-13:36)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
debug_level: 0
none separate
adapter speed: 400 kHz
cortex_m reset_config sysresetreq
Error: unable to find CMSIS-DAP device
Error: No Valid JTAG Interface Configured.
Failed uploading: uploading error: exit status 0xffffffff

[b707]

@zmarcoz

, I keep encountering the same error message.

What the error message?
Please never use a pictures of code and error messages.
You have to insert the code and error message directly to the forum as text, using the code tags.
Please return and edit your post.

[zmarcoz]

Done.

[westfw]

@zmarcoz

Error: unable to find CMSIS-DAP device

This probably has very little to do with the version of SAMD support you've installed.
Are you plugged into the correct USB port?

An Arduino Zero has two USB ports, one labeled "debug" connected to a CMSIS-DAP device, and one "Native" connected directly to the SAMD chip. And there are two board types "Programming Port" and "Native USB Port." You have to have you wiring matching - if you are plugged into the "debug" physical port, use the "Programming port" board definition, and vis versa.

[zmarcoz]

I tried all combinations.