CuVoodoo

the sorcery of copper

User Tools

Site Tools

Trace:
busvoodoo

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
busvoodoo [2017/12/15 11:48] – add flashing kingkevinbusvoodoo [2017/12/22 16:57] – [alternatives] low speed kingkevin
Line 12: Line 12:
  
 Device features: Device features:
-  * compact rigid case: 49.3x27.7 mm+  * compact case: 56.0x27.7x14.7 mm
   * host connection: USB 2.0 (mini-B, full speed: 11 Mb/s)   * host connection: USB 2.0 (mini-B, full speed: 11 Mb/s)
   * 2 light indicators: red for power, red+blue for activity   * 2 light indicators: red for power, red+blue for activity
Line 35: Line 35:
   * RS-485/RS-422 port (not terminated)   * RS-485/RS-422 port (not terminated)
   * CAN port (not terminated)   * CAN port (not terminated)
 +
 +programming connector:
 +  * on the board (in the bottom left corner) there is a 2x4 connector (2 mm pitch)
 +  * DFU pin to force the DFU mode and [[#flashing|flash over USB]] (short to the neighbouring 5V pin while powering up)
 +  * UART port to use the BusVoodo as protocol bridge (it provides the same menu as over USB), or [[#flashing|flash using the embedded bootloader]]
 +  * SWD port for [[#flashing|flashing]] or developing firmware
  
 === not the World's first ever: === === not the World's first ever: ===
Line 67: Line 73:
 ===== protocols ===== ===== protocols =====
  
 +The BusVoodoo implements numerous low-speed protocols.
 +The hardware is only designed for signals speeds up to 20 MHz.
 The signals can be driven using 3.3 V push-pull mode, or 1.6 to 5.5 V open-drain mode with 2 kOhm embedded pull-up resistors (can be increased using external resistor). The signals can be driven using 3.3 V push-pull mode, or 1.6 to 5.5 V open-drain mode with 2 kOhm embedded pull-up resistors (can be increased using external resistor).
  
Line 109: Line 117:
   * PICkit2 to program PIC MCUs, using the high voltage output of the full version   * PICkit2 to program PIC MCUs, using the high voltage output of the full version
   * AVR Dragon to rescue Atmal AVR MCUs using the [[http://www.atmel.com/webdoc/avrdragon/avrdragon.hvsp_description.html|High Voltage Serial Programming (HSVP)]], using the high voltage output of the full version   * AVR Dragon to rescue Atmal AVR MCUs using the [[http://www.atmel.com/webdoc/avrdragon/avrdragon.hvsp_description.html|High Voltage Serial Programming (HSVP)]], using the high voltage output of the full version
 +  * logic analyzer (low speed, with 6 digital and 1 analog channels)
  
 note: the alternative firmware are not implemented yet note: the alternative firmware are not implemented yet
Line 161: Line 170:
   * and probably the most important aspect: it is actively developed and has user support   * and probably the most important aspect: it is actively developed and has user support
  
-The Bus Pirate is not the only alternative though.+The Bus Pirate and BusVoodoo are only designed for low speed protocols.
 There is also the [[https://greatscottgadgets.com/greatfet/|GreatFET]], supporting high speed protocols, but is more of a development board than a ready to use tool. There is also the [[https://greatscottgadgets.com/greatfet/|GreatFET]], supporting high speed protocols, but is more of a development board than a ready to use tool.
-And there is the [[http://datenkrake.org/|Datenkrake]] for even high speed protocols (using an FPGA), but is also more of a development board than a ready to use tool.+And there is the [[http://datenkrake.org/|Datenkrake]] for even higher speed protocols (using an FPGA), but is also more of a development board than a ready to use tool.
  
 But BusVoodoo will never replace dedicated tools (USB to UART dongle, JTAG adapter, flash programmer, ...) or prevent from using a development board to control all nifty protocol details. But BusVoodoo will never replace dedicated tools (USB to UART dongle, JTAG adapter, flash programmer, ...) or prevent from using a development board to control all nifty protocol details.