AT90USB162 - DFU bootloader - device descriptor read error

Go To Last Post
4 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi

 

I was trying to get the DFU bootloader running on AT90USB162 (at90usb162-bl-usb-1_0_5) but have not succeded. (running on internal OSC, 8MHz).

BOOTRZT flag is set and boot size is set to 1800.

 

 

Windows (Win10) does not recognize the device claiming unknown device descriptor. I tried to install the dfu driver found in "dfu-programmer-win-0.7.0" but it would not be accepted. The following is an output from "Device Monitoring Studio", an usb protocol sniffer in evaluation mode. I am not familiar with the USB protocol that much that I am able to get the wanted hints for what might be wrong here.

The output is marked as an USB Packet of size 160 bytes (2size bytes and 158 data (shown below)), direction UP. I guess UP means from PC to Device and that this is a request for info from device, but the device never answer.
Device is marked connected when this message arrives

"\\??\\USB#VID_0000&PID_0002#5&32692177&0&1#{a6782bce-4376-4de2-8096-70aa9e8fed19}"

 

Then I get 2 packages, also with direction set UP,  now device is marked disconnected, but size is only 2 and no datacontainer. Then silenze

 

 

I also tried to enumerate in Linux environment and got the following dmsg result.

new low-speed USB device number 51 using ehci-hcd
device descriptor read/64, error -32

 

(I uploaded the output from "device monitoring studio", but it is in a propritary forma and need the studio sw installed. But just in case......)

 

 

I know this is not much info, but I need to start somewhere to be able to solve why the system fails.
I have been using LUFA earlier on same HW, where I based on the example sw successfully made a one button keyboard for
some animation/stop motion project I had, but I would like to add DFU bootloader capability to this device but run into troubles as shown above.

 

Thanks in advance

 

 

Attachment(s): 

Regards
Vidar (Z)

----------------------------------------------------------

"The fool wonders, the wise man asks"

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have sent you bootloader GUI software and various controller HEX files with name. Direct upload in your  chip. 

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you for your support, but this is not an USB bootloader (which should be using USB standard DFU protocol) and can not be used in my HW. I do not even have any com ports available.

 

Breg

Vidar (Z)

Regards
Vidar (Z)

----------------------------------------------------------

"The fool wonders, the wise man asks"

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

... I made a fresh board just to test the DFU loader on another HW, Same problem as before.
I will contact Atmel directly to get an answer to the FW available for download.

 

After all, my HW mainly consists of a few components like a few capacitors, USB serial resitors and a push button. Not much that can go wrong.

I tried to switch from internal osc to external xtal to minimize risk of timing errors, but that did not change anything.

 

I would very much like other peoples experiences for USB boot loaders, either Atmels or other that is available somewhere and that fits in a 90USB162.

 

 

Regards
Vidar (Z)

----------------------------------------------------------

"The fool wonders, the wise man asks"