busvoodoo
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
busvoodoo [2017/12/14 22:34] – [features] kingkevin | busvoodoo [2017/12/15 08:42] – add firmwares kingkevin | ||
---|---|---|---|
Line 2: | Line 2: | ||
This tool allows to quickly communicate with various other electronic devices. | This tool allows to quickly communicate with various other electronic devices. | ||
- | ==== features ==== | + | ===== features |
The BusVoodoo is a multi-protocol debugging adapter. | The BusVoodoo is a multi-protocol debugging adapter. | ||
Line 12: | Line 12: | ||
Device features: | Device features: | ||
- | * small rigid case: 49.3x27.7 mm | + | * compact |
* 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 18: | Line 18: | ||
* 1 display connector (OLED screen provided in full version) | * 1 display connector (OLED screen provided in full version) | ||
* 1 internal debugging and automation connector (2x4 pins with 2 mm pitch) | * 1 internal debugging and automation connector (2x4 pins with 2 mm pitch) | ||
+ | * re-flashable with [[# | ||
I/O connector: | I/O connector: | ||
Line 49: | Line 50: | ||
It comes with no network connectivity. | It comes with no network connectivity. | ||
Its purpose is to debug and hack devices locally, not to provide a gateway to remotely control other devices. | Its purpose is to debug and hack devices locally, not to provide a gateway to remotely control other devices. | ||
+ | |||
+ | === not the ultimate all-in-one device: === | ||
+ | |||
+ | The BusVoodoo is a compact device which supports a lot of [[# | ||
+ | But it is not intended to replace all the other special purpose adapters (USB to UART, JTAG, ...) which probably can better solve specific task because their are: more stable, simpler, more powerful, faster, more stable, cheaper, or more available. | ||
+ | Thus the BusVoodoo is a good choice to start with, but if you want better performances switch to a device designed for each particular task. | ||
=== not community driven: === | === not community driven: === | ||
Line 57: | Line 64: | ||
Nothing prevents you from building it yourself or forking it though. | Nothing prevents you from building it yourself or forking it though. | ||
Both hardware and software are open-source and available here, and you are welcome to submit bug reports or patches. | Both hardware and software are open-source and available here, and you are welcome to submit bug reports or patches. | ||
- | ==== protocols ==== | ||
- | ==== history ==== | + | ===== protocols ===== |
+ | |||
+ | ===== firmwares ===== | ||
+ | |||
+ | ===== history | ||
Whenever I go to conferences I like to take apart devices I find there. | Whenever I go to conferences I like to take apart devices I find there. | ||
Line 72: | Line 82: | ||
Use a terminal emulation program to connect to it (e.g. [[https:// | Use a terminal emulation program to connect to it (e.g. [[https:// | ||
- | ==== alternatives ==== | + | ===== alternatives |
I am not the first one having this problem and creating such a device. | I am not the first one having this problem and creating such a device. | ||
Line 103: | Line 113: | ||
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. | ||
The BusVoodoo is more of a quick all-in-one first approach tool. | The BusVoodoo is more of a quick all-in-one first approach tool. | ||
- | ==== presentation ==== | ||