Jump to content

Kenny

Active Members
  • Posts

    12
  • Joined

  • Last visited

  • Days Won

    1

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Kenny's Achievements

Newbie

Newbie (1/14)

  1. Test failed in Ubuntu with 2.6.35-32-generic. Still not working for me unless a keyboard LED is activated. Seems like this is still triggering on the same condition as the previous firmware. See this thread for more detail on that. If this is the same firmware that was being tested back in February, why is the source still not available? If binary is released before source, then it is not open source. The section Darren commented out of flash.sh was missing the "then". That error check should make things a bit more clear for folks like webdirector.
  2. It feels pretty dead to me at this point. That is not to say there is no hope for it. As a customer, $80 is a good price for a completed, user-friendly product with the capabilities advertised for the Ducky. But for a budding open source project with poor developer communication? Not worth the money. As an unpaid contributor, my time is the most valuable thing I give. Duplication of effort is a complete waste of my time. I could spend my time working on fixing the Linux compatibility issue. But since Darren posted weeks ago that he was testing a FW with Linux support, I'm not interested in wasting my time on it. Why isn't the previously referenced beta FW in the repository for others to help test, find bugs, and submit patches? This is how open source works. Or is supposed to work. So, what we have here is not really an example of working open source. Until the development and communication process is fixed, the Ducky will not mature into the kind of product that I want to use or support.
  3. For the folks who prefer lsusb formatted info: idVendor 0x03eb Atmel Corp. idProduct 0x2401 bcdDevice 1.00 iManufacturer 1 ATMEL AVR iProduct 2 HID Keyboard iSerial 0 bNumConfigurations 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 1 Keyboard On the topic of VID/PID changes to fix OS support issues: see this post. Micahmic, you raise a very important issue that is on the minds of a lot of *nix users with regard to cross-platform operation. Since that is a significantly different topic than the original posters question, I'm sure many people would appreciate you starting a new thread. (I'd love to see that get fixed too.)
  4. JTAG is certainly an effective way to go about debugging, albeit a little slow depending on the controller. Depending on the complexity of what you are trying to accomplish, you may find it easier to debug code in a simulator. Or on the much lighter end, adding logging features to the firmware might help you get what you want. This could look for a "DEBUG" file in the root of the MicroSD card filesystem. If that exists, then write logging output to another (or the same) file on the card. What does bus enumeration look like on your system? Does broadcast Ack/Nack timing returning to your keyboard give away your password to neighbouring USB devices? Can has class 09h? The Ducky has so much untapped potential. I'm really looking forward to seeing what people come up with.
×
×
  • Create New...