Jump to content

c_for_charlie

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by c_for_charlie

  1. I've figured it out: First off, when I used the command "--suppress-bootloader-mem" I had it spelt incorrectly (see above), which is why I was being prompted with the commands and syntax for using the dfu-programmer. Second, you have to show the path to the .hex file. Relatively easy fixes. I suppose I was just in a rush. lol. Thanks again midnightsnake.
  2. I'm using DFU-programmer 0.5.4, found on the github wiki, here: https://github.com/hak5darren/USB-Rubber-Ducky/wiki/Flashing-ducky Thanks midnight. Appreciate it.
  3. Hello everyone, I've gotten through the majority of flashing the ducky using the dfu-programmer, but at the very last command, I don't seem to be getting any outcome. The steps I've taken are as follows: ./configure make make install dfu-programmer at32uc3b1256 dump >dump.bin dfu-programmer at32uc3b1256 reset dfu-programmer at32uc3b1256 erase dfu-programmer at32uc3b1256 flash --surppress-bootloader-mem c_duck_v2.1.hex The output of the last command that I get is what would be displayed if I only entered "dfu-programmer". That is, I get a list of targets, and an explaination of the commands and syntax for using dfu-programmer. I haven't tried using a different .hex file yet, but I'm just about to head to work so it will have to wait until later. This is in Kali, if that's been known to have any issues. And yes, the ducky has been put into DFU mode via the button on insertion. Does anyone else have any suggestions/see something I may have missed? Thanks in advance, C
×
×
  • Create New...