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/15 11:08] – [firmwares] kingkevin | busvoodoo [2017/12/22 16:44] – add case height kingkevin | ||
---|---|---|---|
Line 12: | Line 12: | ||
Device features: | Device features: | ||
- | * compact | + | * 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-485/ | ||
* 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 [[# | ||
+ | * UART port to use the BusVoodo as protocol bridge (it provides the same menu as over USB), or [[# | ||
+ | * SWD port for [[# | ||
=== not the World' | === not the World' | ||
Line 98: | Line 104: | ||
===== firmwares ===== | ===== firmwares ===== | ||
- | Since the BusVoodoo uses native USB, it can be [[flashing|re-flashed]] to clone other USB device. | + | By default |
+ | When connected to USB it is detected as a serial device (using the standard [[https:// | ||
+ | Just connect to it using your favorite serial terminal and off you go. | ||
+ | But since the BusVoodoo hardware | ||
This allows to convert the BusVoodoo into a dedicated/ | This allows to convert the BusVoodoo into a dedicated/ | ||
Line 108: | Line 117: | ||
note: the alternative firmware are not implemented yet | note: the alternative firmware are not implemented yet | ||
+ | |||
+ | ===== flashing ===== | ||
+ | |||
+ | The BusVoodoo is pretty much unbrickable. | ||
+ | It provides several flashing methods: | ||
+ | - the main BusVoodoo firmware provides USB Device Firmware Upgrade (DFU) capabilities. [[http:// | ||
+ | - if switching from runtime to DFU mode does not work, connect to the BusVoodoo using the serial terminal and switch to DFU mode using the menu | ||
+ | - if the BusVoodoo does not appears as USB serial device, there is still a serial port on the debugging connector. Connect to it using an USB to serial adapter and switch to DFU mode using the menu | ||
+ | - if the main firmware is broken and the menu is not accessible over the USB or serial port, short the 5V and DFU pins on the programming connector (follow the DFU indication on the board) while powering the device. This will force booting the DFU bootloader instead of the main application | ||
+ | - if the DFU bootloader (or USB) is broken, short the ICP pad to ground using twizzers (follow the ICP indication on the board) while powering the device. This will start the STM32 embedded UART bootloader, allowing you to [[stm32f1xx# | ||
+ | - finally you can use the SWD pins on the programming connector to [[stm32f1xx# | ||
+ | - if none of the above methods work, the device is definitely bricked (or defective). congratulations. | ||
===== history ===== | ===== history ===== | ||
Line 148: | Line 169: | ||
The Bus Pirate is not the only alternative though. | The Bus Pirate is not the only alternative though. | ||
There is also the [[https:// | There is also the [[https:// | ||
- | And there is the [[http:// | + | And there is the [[http:// |
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. |