Digistump Forums

The Digispark => Digispark Pro Support => Topic started by: traphyk on October 23, 2014, 11:34:28 am

Title: Problem uploading to Digispark Pro (Beta)
Post by: traphyk on October 23, 2014, 11:34:28 am
I just finally got around to downloading the newer Arduino IDE and as such figured I'd also download the Pro addons and get it running. I soldered my beta board because I also wanted to play with it.


However, after getting my setup complete, I decided to upload the blink sketch (unmodified, from the pro webpage) to my pro to test it out. Every time I try to run this, I get an error message.

I'm on OSX 10.6.8 on an older Macbook running a 2009 MBP motherboard. I have Arduino IDE 1.5.8, and I am sure I have the Digispark Pro board selected. The error message I'm getting is attached. sh keeps quitting. The first 3 or so times, it would happen only after I reset my pro (to initiate the upload). Now, it happens each time I CTRL+U or click upload. Ultimately I'm unable to upload anything to the pro.

I'm thinking it may be because I don't see "Digispark Pro" under my programmers but do see (and have selected) micronucleus.


Any help would be appreciated. I can provide more info if needed.
Title: Re: Problem uploading to Digispark Pro (Beta)
Post by: digistump on November 08, 2014, 02:07:54 pm
You have it all set up right - but I'm thinking this is likely due to the IDE setup being compiled on 10.8 and 10.9 - has anyone else seen this issue?
Title: Re: Problem uploading to Digispark Pro (Beta)
Post by: traphyk on November 10, 2014, 11:19:36 am
I think you may be right. I remember issues with the evasi0n7 jailbreak for iOS 7 on the same machine. The issue there was a dylib file dependency that wasn't packaged with it - it was a dylib file from 10.9 which wasn't compatible with my version. I ended up re-packaging the app with a dylib file from a Mac running 10.9 and all was well. I'm not sure that the issue here is a dylib dependency but it may be something similar.

Hopefully someone else who has this issue can dig a little deeper. I'd be willing to provide my machine specs if that would help.