Error "DFU_DNLOAD" while upgrading with avrdude #26
Comments
|
This seems to be a problem specific to your installation - can you post more details like avrdude version etc.? |
david-oswald
changed the title
|
avrdude version 6.2 / ubuntu 16.04 And is it normal that the cameleon dosn't blink at all? |
|
Yes the device does not indicate that it is in the bootloader (both LEDs are off) |
|
I don't really understand what you mean by the device dose not indicate that it is in the bootloader? |
|
Get the same (or similar) errors on Arch-Linux while trying to flash the firmware. avrdude-version is 6.3 The error does not occur on a fixed percent-status, seems like a random break in the pipe. dmesg output (first line is on plug-in, second line after avrdude is ran): Syslog does not provide further information. Also already checked another USB-Cable, no success so far. Greetings, |
zgv163
changed the title
|
I have the same issue on Linux/Gentoo with avrdude 6.3: Running: $ sudo avrdude -c flip2 -p ATXMega128A4U -B 60 -P usb -U application:w:Chameleon-Mini.hex:i -U eeprom:w:Chameleon-Mini.eep:i The only message caught by syslog is: and avrdude output is: ** OUTPUT STRIPPED ** |
|
Well I have installed avrdude using brew on my Mac and no problem occurred. We can suppose that the problem is coming from a missing driver on the Linux or a software that interrupts the process. |
|
Verified, also works with Brew-installed avrdude for me. Still, the question is, why it does not work on some Linux-Distros :/ |
|
Thanks for testing. We used the only minimally modified standard AVR flip bootloader, which is pretty standard. You can try to use dfu-programmer as an alternative to avrdude, either as a fix or to further identify the root cause of your problem: https://github.com/dfu-programmer/dfu-programmer |
|
Same issue on Ubuntu 16.04, Avrdude 6.2. |
|
I noticed the "xhci_hcd" in the Kernel Log. So maybe it is an issue with USB 3.0? Can you test the Chameleon with a USB 2.0 port or USB 2.0-only computer? |
|
Also, what avrdude are you using (What Linux Distro+Packet Repo resp. build from sources?). According to this (old) bug, it might be a problem in a (very old, or unpatched) avrdude version. |
|
How to use dfu-programmer? I tried: |
|
Yes, the above command line looks correct to me. There could be a deeper problem with DFU and USB on certain OSes. Can you try the commands directly on the command line, i.e., which output do
give? |
|
Hi, just tested the command under ubuntu 16.04 this is the result:
But After trying to upload firmware again with this command: i get this msg: and after that |
|
I'm getting the same error while flashing on Ubuntu 16.04.1 LTS during the reading phase. VERSION? So I think I was able to flash the device. I get the same error when trying the erase command. |
|
As Simon mentioned, USB3 could be a problem apparently - can anyone who has problems try with a USB2 port? |
|
It's the USB3. I had the problem, and used a cheap USB2 hub. Upgrade worked perfectly. |
|
So my guess is confirmed. I Wunder whether the fault is in the OS, libusb, avrdude or the atmel bootloader. |
|
I successfully upgraded using the files on the GettingStarted page, but HELP does not show all of the commands the video or documentation demonstrates |
|
Dumb user error here. I did not have linewrap on. It was truncating the message. |
|
After issuing |
|
On USB 2.0 ports: On USB 3.0 ports: |
|
Using dfu-programer: ends without any stdout without error. ends with and error code 1. Same for USB 2.0 and USB 3.0 ports. |
|
Well, knowing that it dose work on a Mac with Mac OSX but not on Mac with Linux it shouldn't be a problem with USB 2.0 or 3.0 |
|
Confirmed it worked with USB2 |
|
Any other ideas to try? I am unable to flash using avrdude/dfu-programmer on both USB 2.0/3.0. I have Ubuntu 16.04 on ThinkPad T440p. |
|
I'm having this same issue with a ThinkPad P50 that only has USB3 ports, running Ubuntu 16.04.1 and whatever avrdude and avra packages apt-get installed. Edit: Turns out the dock for my P50 has USB 2 ports. I had no problems flashing the firmware with one of the ports on the dock. |
|
Am I the only one who can't flash even on USB 2.0 ports? |
|
Have you tried a difference USB cable? I used Marshall gold plated should have been perfect. It was not. Tried different ones and it loaded fine. It is a simple solution. Zen |
|
If it's a problem of the USB cable then either voltage drop over the cable (very unlikely imho since the current drawn by the Chameleon is quite low) or (much more probable) some issue with the connector. MicroUSB connectors can wear off quite quickly. In any case, the problem in this thread is not really Chameleon-specific, but should affect the combination "Flip bootloader + avrdude" in general. Maybe we should also discuss with the avrdude devs. |
|
Tried three different USB cables, one of them is completely new, on both USB 2.0/3.0. Errors follow: |
|
I am gettting error with: DFU_UPLOAD, DFU_UPLOAD, both or verification error. The cables works for flashing Arduinos etc. |
|
Did more testing, also got: So there is surely a problem with communication. Dfu programmer does not work either. Could it be manufacturing defect? Any other ideas? I would really like to try it already. |
|
I was able to flash it using USB 2.0 hub. |
|
Thinkpad T450s |
|
I did more testing, only with a single USB hub I am able to flash it, tried two other USB hubs with no luck. Actually the only working hub I have is 5 meter active USB cable. I think this issue needs to be fixed. |
|
Thank you for your tenaciousness. If you now switch back to the non-working (with avrdude anyway) USB hub, can you successfully connect to the Chameleon COM Port and issue commands? I.e. does this problem exist in combination with the bootloader firmware only and not with the chameleon firmware? If so, we can probably outrule any hardware issues. |
|
Hi, same problems here. Managed to flash after trying different USB ports. |
|
Yes I can normally issue commands on any ports. I don't thing anybody reported that type of problem, it is clearly bootloader issue. Also it fails randomly even with the usb hub. I think that bug is present on all combinations USB 2.0/3.0 with hub/without hub. On some combinations I have the bug all the time, on some I have it rarely. |
|
Same problem here, my specs are: I tried to flash the firmware with avrdude, the first time I didn't realize that I didn't have the avra package installed. Although I got the same errors about the broken pipe as all other people, I reconnected the chameleon and its was recognized by dmesg as Kapser And Oswald device. I successfully connected with it through minicom and started to type commands, the only response I have gotten was 101:OK. Following that I realized that I didn't have avra installed, so I installed it and retried. The same errors occurred during the firmware flashing. Now I am getting an "device descriptor read/64, error -110" at my dmesg which is most probably a power relating error and I hope that it is a result of invalid flashing. Anyway, I just wanted to state these. I don't have a usb2 port to try as the other stated but I will try flashing through a virtual machine or windows and I will tell here what it will happen. EDIT: I have successfully flashed the firmware using windows at the exact same port (and the exact same cable ) . Now working with it on linux :) |
|
Same issue with Kali rolling. |
|
@gtpy As you noticed, this seems to be a problem with linux and its usb support since it works with the same hardware but with different OS. Thus, we cannot do here anything. |
|
@geo-rg thanks. So I try it with Windows in virtual box. |
|
.I solved this problem for: ubuntu 17.10 + kali rolling -->
If it doesnt work well, I changed bitclock to different values(-B 60, -B 64, -B 60) and it works well. |
|
It's interesting that changing the -B parameter changes behavior at all. It is supposed to set the click speed when using the hardware isp interface. Someone should check what the parameter does when using -c flip2.
As easy as it sounds, I currently would not target the linux USB stack as the culprit.
Best regards
Am 8. November 2017 23:52:48 MEZ schrieb Christian <[email protected]>:
….I solved this problem for: ubuntu 17.10 + kali rolling --> `sudo apt
install libusb-dev`
`avrdude -c flip2 -p ATXMega128A4U -B 60 -P usb -U
application:w:Chameleon-Mini.hex:i -U eeprom:w:Chameleon-Mini.eep:i
`
If it doesnt work well, I changed bitclock to different values(-B 60,
-B 64, -B 60) and it works well.
Maybe it is in some instances too fast or too slow?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#26 (comment)
|
|
Maybe it was a coincidence that it works after different tries. I'll try to go to an detailed analysis if I find some more time - are actual really busy in Job and family |
|
I am also experiencing the same problems with both 3.0 and 2.0 USB A ports on my Lenovo E580 with Debian 12.5 and 6.1.0-21-amd64 kernel. Using a USB 2.0 Hub in the USB 3.0 port has helped solve this issue for me. |
Hi, When i try to execute the upgrade i get the following message:
zgv@ZGV-MacBookPro:~/Desktop/upgrade$ sudo avrdude -c flip2 -p ATXMega128A4U -B 60 -P usb -U application:w:Chameleon-Mini.hex:i -U eeprom:w:Chameleon-Mini.eep:i
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
avrdude: Device signature = 0x1e9746 (probably x128a4u)
avrdude: NOTE: "application" memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "Chameleon-Mini.hex"
avrdude: writing application (131072 bytes):
Writing | # | 2% 0.05savrdude: Error: DFU_DNLOAD failed: error sending control message: Broken pipe
avrdude: Error: Failed to set memory page 0x0000
avrdude: Error: DFU_DNLOAD failed: error sending control message: Broken pipe
avrdude: Error: Failed to set memory unit 0x00 (Flash)
**failed;
avrdude: Error: DFU_DNLOAD failed: error sending control message: Broken pipe
avrdude: Error: Failed to set memory unit 0x00 (Flash)
*__failed;
avrdude: Error: DFU_DNLOAD failed: error sending control message: Broken pipe
avrdude: Error: Failed to set memory unit 0x00 (Flash)
*__failed;
avrdude: Error: DFU_DNLOAD failed: error sending control message: Broken pipe
avrdude: Error: Failed to set memory unit 0x00 (Flash)
*__failed;
avrdude: Error: DFU_DNLOAD failed: error sending control message: Broken pipe
avrdude: Error: Failed to set memory unit 0x00 (Flash)
*__failed;
avrdude: Error: DFU_DNLOAD failed: error sending control message: Broken pipe
avrdude: Error: Failed to set memory unit 0x00 (Flash)
*__failed;
avrdude: Error: DFU_DNLOAD failed: error sending control message: Broken pipe
avrdude: Error: Failed to write 0x0001 bytes at 0x0007
*__failed;
avrdude: Error: DFU_DNLOAD failed: error sending control message: Broken pipe
avrdude: Error: Failed to write 0x0001 bytes at 0x001E
*__failed;
avrdude: Error: DFU_DNLOAD failed: error sending control message: Broken pipe
avrdude: Error: Failed to write 0x0001 bytes at 0x003E
**failed;
^C
zgv@ZGV-MacBookPro:~/Desktop/upgrade$
Dose any one have an idea why?
The text was updated successfully, but these errors were encountered: