Issues with digispark and littlewire

[catdawg426]

Hello,
I'm trying to use my digispark as a littlewire device and I've followed the tutorial here to do so
http://digistump.com/board/index.php/topic,160.0.html


Littlewire uploads, but when I plug it back in, it is not recognized as a usbtiny device. It also disconnects and reconnects constantly. When I run lsusb in the terminal (Ubuntu) it shows as Grautec, I don't know if this means anything.


Any help is appreciated!


Thanks

[digistump]

Use the littlewire firmware with Digisparks all of the time and I've never seen this issue - do you have a windows or mac to test it on? If so, same results? I've never run a littlewire on linux so I can't rule out something with that.

[catdawg426]

I reuploaded the littlewire software on a mac machine, and it's still not recognized. In the system profiler, it comes up as "Vendor-Specific Device".


Product ID: 0x0753
Vendor ID: 0x16d0
Version: 1.02
Speed: Up to 1.5 mb/sec
Location ID: 0x04100000 / 4
Current Available (mA): 500
Current Required (mA): Unknown (Device has not been configured)




What does this mean? Also, I plugged it in a windows machine and the disconnecting/reconnecting started happening and in device manager it says, "Device has not been configured correctly".


Still GrauTec in Ubuntu.


Thanks,

[Bluebie]

This makes me think the bootloader isn't working correctly. Do any other programs you upload work? Are you using an official digistump-made digispark, or one of the diy versions or clones available? It maybe an error in the fuse settings - something a lot like that happens to sparks when the flash self program enable fuse isn't correctly set. The vendor specific device is the bootloader. To save bytes and make more available to uploaded programs, it doesn't store and output a manufacturer name or device name string to the computer, only numeric identifiers.

[catdawg426]

If I upload a sketch from arduino it works fine, so that works. I'm using an official digistump digispark.
How do I correct the fuse settings?

[Bluebie]

Can you try and upload firmware version 1.0 or 1.1 instead of the new 1.2 and see if that works? My suspicion is the latest version of littlewire may require the extra bytes available in more recent versions of micronucleus than the one which ships with digispark devices by default. If this is the case, don't worry! It's really easy to upgrade it to the newer version


Let me know if the previous versions work any better.

[kehribar]

Can you try and upload firmware version 1.0 or 1.1 instead of the new 1.2 and see if that works? My suspicion is the latest version of littlewire may require the extra bytes available in more recent versions of micronucleus than the one which ships with digispark devices by default. If this is the case, don't worry! It's really easy to upgrade it to the newer version


Let me know if the previous versions work any better.

Jenna Hi,

I was considering this and tested the new release with micronucleus-v1.02. Isn't that the one comes with the Digisparks? It was working OK with that version of micronucleus.

By the way, avr-size output of the latest version is as follows.


AVR Memory Usage
----------------
Device: attiny85


Program:    5794 bytes (70.7% Full)
(.text + .data + .bootloader)


Data:        312 bytes (60.9% Full)
(.data + .bss + .noinit)




I'm doubted that previous version can fix catdawg426's proble but it might worth the try.

Best,
ihsan.

[digistump]

I use LW 1.2 with micronucleus 1.02 (the default) all the time - so I can confirm that combo works

[catdawg426]

Do you think you can send me littlewire v1.1? I can't find it anywhere online, all of the links to github are bad.

[Bluebie]

LittleWire 1.0: http://creativepony.com/seadawg/GmAvFa8aHY.hex
LittleWire 1.1: http://creativepony.com/seadawg/T0lG8vX8wy.hex

[catdawg426]

Awesome, the 1.1 hex works. Thank you!