Curiosity Nano programmer not working.... (linux specific?)

[wa2mze]

I selected the Curiosity Nano as the programmer, I selected NO BOOTLOADER, and AVR128DA48 as the chip type. Also 24mhz internal (no option listed for using the 32khz oscillator to calibrate the 24 mhz oscillator). Selected TTYACM0 for serial port (which should NOT be used for programmer. Selected for use with serial port (which isn't being used right now) I created a simple led blink sketch:

void setup() { // put your setup code here, to run once: pinMode(20,OUTPUT); }

void loop() { // put your main code here, to run repeatedly: delay(500); digitalWrite(20,1); delay(500); digitalWrite(20,0); }

Sketch compiles OK. Tried uploading and it fails. See error messages (for AVRDUDE only) below.

Arduino: 1.8.13 (Linux), TD: 1.54, Board: "AVR DA-series (no bootloader), Disabled, AVR128DA48, 24 MHz internal, 1.9V, Disabled/Disabled, EEPROM retained, Hardware Reset (recommended), TCB2, 8ms"

Sketch uses 954 bytes (0%) of program storage space. Maximum is 131072 bytes. Global variables use 4 bytes (0%) of dynamic memory, leaving 16380 bytes for local variables. Maximum is 16384 bytes. /home/ken/.arduino15/packages/arduino/tools/avrdude/6.3.0-arduino18/bin/avrdude -C/home/ken/.arduino15/packages/DxCore/hardware/megaavr/1.3.6/avrdude.conf -v -v -pavr128da48 -ccuriosity_updi -Pusb -Ufuse5:w:0b11001001:m -Ufuse7:w:0x00:m -Ufuse8:w:0x00:m -Uflash:w:/tmp/arduino_build_985540/AVR128DAnano.ino.hex:i

avrdude: Version 6.3-20201216 Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/ Copyright (c) 2007-2014 Joerg Wunsch

     System wide configuration file is "/home/ken/.arduino15/packages/DxCore/hardware/megaavr/1.3.6/avrdude.conf"
     User configuration file is "/home/ken/.avrduderc"
     User configuration file does not exist or is not a regular file, skipping

     Using Port                    : usb
     Using Programmer              : curiosity_updi

avrdude: jtag3_open_updi() avrdude: usbdev_open(): Found nEDBG CMSIS-DAP, serno: MCHP3280031800001715 avrdude: usbdev_open(): WARNING: failed to set configuration 1: Device or resource busy avrdude: Found CMSIS-DAP compliant device, using EDBG protocol avrdude: usbdev_send(): wrote -5 out of 912 bytes, err = Input/output error avrdude: jtag3_edbg_prepare(): failed to send command to serial port

avrdude done. Thank you.

the selected serial port does not exist or your board is not connected

[SpenceKonde]

I don't have a linux system to test with but this behavior on linux, buyt all is well on windows.

[wa2mze]

The curiosity Nano works fine under MPLAB under Linux, so there IS a Linux driver for the thing that works. I did have a problem getting it recognized under MPLAB once that required resetting some of the project parameters though. It's strange that Arduino is complaining about the port not being recognized, though the /dev/ACM0 does 'go away' while the programmer is being used (it's a USB device with multiple endpoints). AVRdude DOES find the programmer endpoint, as reported in the error messages.

[killerkalamari]

I needed to add my user to the dialout group on my Debian system for avrdude to be able access /dev/ttyUSB0 to program the AVR128DB28 using jtag2updi. I don't have a Curiosity Nano so this is a shot in the dark, but does sudo adduser $USER dialout and then rebooting (not just logging out), do the trick?

[wa2mze]

I'm already in the dialout group, and a member of sudo (these are usually set by default in ubuntu and kubuntu but not Debian.) So that's not the answer for me. Also the Curiosity Nano does work under MPLAB native Linux.

[pfoun]

I do not think just being a member of the dialout group will give you permission to use a serial usb device. You need to create a rules file in the etc/udev/rules.d system folder. The file can be named "98-anything.rules" and contain this line: SUBSYSTEMS=="usb", ATTRS{idVendor}=="????", ATTRS{idProduct}=="????", MODE:="0666". You will need elevated priviledges to do this. This line containing the wild cards may be a breach of security, but it should match any usb device and has worked for me for /dev/ttyUSB0 as well as others. I am not an expert in this area and direction from others is welcome.

[killerkalamari]

Linux has a kernel module that can sniff USB traffic: https://www.kernel.org/doc/Documentation/usb/usbmon.txt I tried it out on jtag2updi:

sudo modprobe usbmon

Then I took a look at lsusb: Bus 001 Device 010: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter

To capture, I ran (1u comes from lsusb Bus 001... just add a u to the bus):

sudo cat /sys/kernel/debug/usb/usbmon/1u >bus1.txt

In my case, there were multiple devices on the bus, cluttering the output. I filtered the output to just the device I cared about (010 comes from lsusb Device 010):

grep ":010:" bus1.txt >avrdude.txt

Perhaps comparing captured USB outputs for MPLAB and avrdude will reveal something?

[SpenceKonde]

I thought dialout normally gave you access to serial USB devices. But the programmer on the curiosity nanos is not just a serial port (the serial port isn't the thing that is used to program it; it's a composite device that shows up as several devices) You can get the USB PID and VIDs for them from various programmers from avrdude,conf. Of course, we don't even know if it's a permissions issue or what.

[leo60228]

pymcuprog works, but unlike the serial programmer it verifies the device ID, so the MCU always being avr128da28/avr128db28 doesn't work (never mind, I was being dumb with the device ID thing).

[leo60228]

This seems to be specific to mEDBG, or possibly the Dx series. I can program an Xplained Nano ATtiny416 with avrdude on the same system perfectly fine.

[SpenceKonde]

I think you got the the letters in the alphabet soup mixed up. nEDBG is the curiosity nano, mEDBG is the one with the the atmega32u4.

Atmel's debuggers had names that sound like something from an overdone fantasy novel or perhaps slang terms for drugs (Atmel ICE! AVR Dragon! POWER DEBUGGER! Now they won't even Xplain how to use their products, we have to rely on our Curiosity and an alphabet soup of programmers. :-/

[SpenceKonde]

Xplained Mini: mEDBG, debug chip: ATmega32u4 Xplained Pro: EDBG, debug chip: AT32UC3A4256 Curiosity Nano: nEDBG, debug chip: ATSAMD21E18 Is the version of AVRdude you're using the one that gets installed by board manager...? make sure it is; I'm not sure if the versio nthe IDE installs with has the curiosity/nEDBGpatch, it was added some time after the Dx-series parts were available (and after DxCore was available)

[SpenceKonde]

Since this is a bug in avrdude, fixing it is out of my hands. If this problem still occurs with latest avrdude, raise the issue with the avrdude team