I've run sketches on the Digispark USB board with Attiny85 using the libusb-win32 driver. Just got the HW-260 Attiny socketed board which appears to be the same as the Digispark. The two schematics look the same too.
However I can's load any scripts to the HW-260 with usb cable after adding the bootloader to the Attiny85 (with an Uno). Communication isn't right because the libusb driver doesn't appear in Device Mgr.
Next I connected the a FTDI breakout board to HW-260 ICSP header (5V, grd, tx, rx and dtr). This time Arduino recognized FTDI on com4 but still no libusb driver.
Hoping someone can explain what I'm not understanding. What's on the Digispark that's not on the HW-260+Attiny.
I follow these steps: 1. Using an AVR Programmer, I read the Fuse Settings of the ATiny85 MCU located on the Digispark Attiny85 Board and recoder them. How?
Solder 8 header pins on the Digispark Board. Take an 8-pin socket and solder 8 jumpers. Connect the female ends of the jumpers on the pins of the Digispark Board. After that place the socket on the AVR Programmer.
2. I read the whole flash content (the Bootloader) of the ATtiny85 MCU of the Digispark Board.
3. I place my fresh ATtint85 chip on the AVR Programmer. 4. I set/write the Fuse Settings of Step-1. 5. I copy/write the Bootloader of Step-2. 6. I take out the MCU from the AVR Programmer and place it into the empty socket of HW-260 Dev Board.
7. I use HW-260 Dev Board and develop my product/project. 8. I take out the MCU from the HW-260 Board and place it on the AVR programmer. 9. I lock the memory Lock Bits as I need. 10. I take out the MCU from the AVR Programmer and place it on the PCB of my product/project. 11. The project is done.
I don't know exactly where this bootloader could be found. I have got it for myself by reading it from the onboard ATtiny85 MCU of the following Digispark ATtiny85 Dev Board.