Usblinky: Unterschied zwischen den Versionen
Keine Bearbeitungszusammenfassung |
|||
| (9 dazwischenliegende Versionen von 3 Benutzern werden nicht angezeigt) | |||
| Zeile 3: | Zeile 3: | ||
'''usblinky''' | '''usblinky''' | ||
* is a small usb stick with 4 wires on | * is a small usb stick with 4 wires on one end | ||
* controls up to 150 addressable RGB lights | * controls up to 150 addressable RGB lights for example WS2812B, the current is the limiting factor here. if you run them directly form your USB port 20 individual pixels will work | ||
* can run stand alone from a USB power supply once programmed | * can run stand alone from a USB power supply once programmed | ||
* consists of: | * consists of: | ||
| Zeile 61: | Zeile 61: | ||
But this microcontroller was too small to do fancy effects and so i made a completely new design for this job. | But this microcontroller was too small to do fancy effects and so i made a completely new design for this job. | ||
Later on I finally found a reason to check out [http://www.openscad.org/ OpenSCAD] and boy do I like that. What a great tool! | |||
I made a fully parametric design to use with the usblinky as a psychedelic nightlight. | |||
== Alternate usecases == | == Alternate usecases == | ||
| Zeile 79: | Zeile 80: | ||
They speak USB over vUSB but enumerate the device as a usbtiny programmer. | They speak USB over vUSB but enumerate the device as a usbtiny programmer. | ||
The arduino sees a programmer and | The arduino sees a programmer and programms the ATTINY85 as a target, when it actually overwrites its own FLASH with the user program. | ||
I liked that nifty approach and used the Trinket bootloader when i started this project. | I liked that nifty approach and used the Trinket bootloader when i started this project. | ||
But then i read that adafruit does not | But then i read that adafruit does not want you to use their USB ID in a product that you sell. | ||
I contacted them but got no meaningful reply, only a standardized answer that i should come back once my product launched. | I contacted them but got no meaningful reply, only a standardized answer that i should come back once my product launched. | ||
| Zeile 89: | Zeile 90: | ||
Later on i found out that the bootloader on the trinket is fragile. | Later on i found out that the bootloader on the trinket is fragile. | ||
Under some special circumstances it can happen that the bootloader | Under some special circumstances it can happen that the bootloader wrongful triggers and the FLASH on the MCU is partially overwritten and it can not be programmed any more over USB. | ||
It can still be recovered with a dedicated programmer but this was to fragile for my usecase. | |||
===Digispark / micronucleus=== | ===Digispark / micronucleus=== | ||
| Zeile 98: | Zeile 100: | ||
This bootloader is significantly smaller (2k versus 3.5k) and the code is much more straight forward than the trinket bootloader. | This bootloader is significantly smaller (2k versus 3.5k) and the code is much more straight forward than the trinket bootloader. | ||
The drawback is that you need to modify the | The drawback is that you need to modify the Arduino environment a little more than with the Adafruit Tinket but there are packages available for that. | ||
When I used the usblinky as a BUTTON for the selfiebooth setup I realized that the pinout differs on the trinket. | When I used the usblinky as a BUTTON for the selfiebooth setup I realized that the pinout differs on the trinket. | ||
D+ and D- are | D+ and D- are swapped on the MCU side. | ||
In theory not a big deal, but a lot of libraries that are available for the digispark project (for example the USB keyboard emulation) has this pinout hardcoded and I needed to modify the .cpp files in the Arduino environment to make that work. | In theory not a big deal, but a lot of libraries that are available for the digispark project (for example the USB keyboard emulation) has this pinout hardcoded and I needed to modify the .cpp files in the Arduino environment to make that work. | ||
| Zeile 108: | Zeile 110: | ||
Future versions of USBlinky have the pins swapped as on the original digispark design. | Future versions of USBlinky have the pins swapped as on the original digispark design. | ||
=== Merging the .hex files === | |||
When i programmed the first few usblinky sticks i just uploaded the bootloader and flashed the usblinky program later directly over USB. | |||
That worked great but was timeconsuming, so i looked into merging the bootloader and the userprogram into one .hex file to flash at once. | |||
Turns out that is difficult. | |||
I tried many different approaches but didn't succeed till I did this: | |||
* flash the bootloader | |||
* load the userprogram over USB | |||
* read back the flash from the attiny (avrdude -p attiny85 -P usb -c usbtiny -U flash:r:flash.hex:i) | |||
* write that dump to future usblinky sticks | |||
All the relevant script for reading and writing and a script for semi-automated flashing in a loop can be found [https://github.com/hackerspaceshop/usblinky/tree/master/software/builds/scripts here on github] | |||
== Who == | == Who == | ||
* [[Benutzer:Overflo|Overflo]] -The whole USBLINKY project. | * [[Benutzer:Overflo|Overflo]] -The whole USBLINKY project. | ||
* [[Benutzer:clifford|clifford]], [[Benutzer: | * [[Benutzer:clifford|clifford]], [[Benutzer:MariusKintel|marius]] - OpenSCAD THANK YOU!! | ||
* [[Benutzer:cs|cs]] - vUSB from OBDEV is amazing. Thank you so much. | * [[Benutzer:cs|cs]] - vUSB from OBDEV is amazing. Thank you so much. | ||
==Links== | |||
[http://www.hackerspaceshop.com/blinky/usblinky.html hackerspaceshop, buy one there] | |||
[https://www.tindie.com/products/hackerspaceshop/usblinky/ also available on tindie] | |||
[ | |||
[https://github.com/hackerspaceshop/usblinky github] | [https://github.com/hackerspaceshop/usblinky github] | ||