Recent Posts

Pages: 1 ... 5 6 [7] 8 9 10
61
Digispark (Original) Support / Failing to compile sketchbook with the DigisparkKeyboard library on Android
« Last post by LordHelmii on December 01, 2019, 05:37:09 am »
Hey,
I'm using the app ArduinoDroid (https://play.google.com/store/apps/details?id=name.antonsmirnov.android.arduinodroid2&hl=de) and a Digispark 16.5 attiny85.
Compiling works fine on Windows and Ubuntu, but since adding libaries is a bit different on Android, I had to add the DigisparkKeyboard library
(https://github.com/digistump/DigistumpArduino/tree/master/digistump-avr/libraries/DigisparkKeyboard)
manually to the ArduinoDroid/libraries folder, which worked fine. But when trying to compile, I get the following error in the file
https://github.com/digistump/DigistumpArduino/blob/master/digistump-avr/libraries/DigisparkKeyboard/usbdrv.c

In function 'usbInit':
/path/to/usbdrv.c:618: undefined reference to 'usbCrc16Append'
/path/to/usbdrv.c:618: undefined reference to 'usbCrc16Append'
collect2: error: Id returned 1 exit status
Return code is not 0


Unfortunatlely, there doesn't seem to be any logs and I can't copy the compilation-output. I will provide any further information if needed.
62
Digispark (Original) Support / Why is the --run required while updating the firmware ?
« Last post by hrtk on November 30, 2019, 07:11:03 am »
Hi.
I was successfully able to remove the 5 seconds delay. (http://digistump.com/board/index.php/topic,320.0.html ) Though, I do have a question. Why do we need to pass the `--run` argument to micronucleus while uploading the firmware ?
Don't we just want to flash the firmware and not run it at that time ?
Why does it all go crazy (http://digistump.com/board/index.php/topic,320.msg8546.html#msg8546) when we don't provide the --run argument ?
Also, while trying to flash another firmware after this, would I need to connect P0 to GND ?
63
Digispark (Original) Support / [Documentation] The "removing 5s. delay while boot" doesn't contain proper link
« Last post by hrtk on November 30, 2019, 06:38:38 am »
It took me a while to figure out that the link provided to download the latest jumper firmware on https://digistump.com/wiki/digispark/tricks isn't quite correct.
You need to change the github tag to an earlier version to get the github firmware.
As of today it is tag v1.1 i.e. this one https://github.com/micronucleus/micronucleus/blob/v1.11/upgrade/releases/micronucleus-1.06-jumper-v2-upgrade.hex
64
Digispark (Original) Support / Re: Cannot install unsigned Digistump drivers on Windows XP
« Last post by granzeier on November 30, 2019, 03:45:28 am »
Wow, that's pretty good detective work.
I haven't used Windows (for development work) much for nearly a decade, just for IT support at work. I'm running nearly exclusively on Linux now. So, thanks for finding this, and for posting it here.
65
Digispark (Original) Support / Re: Cannot install unsigned Digistump drivers on Windows XP
« Last post by janis.xyz on November 29, 2019, 01:27:02 pm »
I managed to solve this problem on Windows XP, by looking at the certificate for the drivers. If you look at the properties of the DPinst.exe you will see that the certificate was valid only between August 2014 to August 2015. So the problem is that they have expired.

Solution:

Change system date to any date between August 2014 and August 2015.
Install drivers.
Change date back to correct one.

It worked for me, although I have yet to get digispark working on Windows 7!

Best of luck!
66
Digispark (Original) Support / Re: Retina MBP Issues
« Last post by Anjin on November 16, 2019, 05:15:45 pm »
It is a well known issue with MacBooks going back some ways.  It is as many have surmised, simply that the port design does not allow for contact with the pins on the digispark usb.  Simple enough to get around, just add a hub or extension cable.
67
Digispark Pro Support / Re: Mac OS X Catalina: 64-bit Support for Arduino IDE
« Last post by Anjin on November 16, 2019, 05:07:01 pm »
The newest 1.8.10 has all the parts that are required inside.  One simply needs to trick the Digistump config to use what is included, instead of its own old, out of date, no longer supported snowflake of the AVR tools.

I found this easy enough by simply linking the current shipping 64bit version, into the Digistump tree.

First, make sure your board includes are all setup properly. Next, shutdown the Arduino IDE completely.  Finally, from a shell prompt, you are gonna move the Digistump snowflake out of the way, and link in the current shipping version:

$ cd ~/Library/Arduino15/packages/arduino/tools/avr-gcc
$ mv 4.8.1-arduino5 orig.4.8.1
$ ln -s /Applications/Arduino.app/Contents/Java/hardware/tools/avr 4.8.1-arduino5

You could just delete the old stuff I suppose.  But that should cover it for you.  Fire up Arduino IDE as normal and get back to work :)
68
Digispark (Original) Support / Re: Bad CPU type in executable
« Last post by Anjin on November 16, 2019, 05:06:14 pm »
The newest 1.8.10 has all the parts that are required inside.  One simply needs to trick the Digistump config to use what is included, instead of its own old, out of date, no longer supported snowflake of the AVR tools.

I found this easy enough by simply linking the current shipping 64bit version, into the Digistump tree.

First, make sure your board includes are all setup properly. Next, shutdown the Arduino IDE completely.  Finally, from a shell prompt, you are gonna move the Digistump snowflake out of the way, and link in the current shipping version:

$ cd ~/Library/Arduino15/packages/arduino/tools/avr-gcc
$ mv 4.8.1-arduino5 orig.4.8.1
$ ln -s /Applications/Arduino.app/Contents/Java/hardware/tools/avr 4.8.1-arduino5

You could just delete the old stuff I suppose.  But that should cover it for you.  Fire up Arduino IDE as normal and get back to work :)
69
Digispark (Original) Support / Re: "Unknown Device"
« Last post by Citrusl on November 14, 2019, 08:03:45 am »
14/11/2019 nothing yet.
Pages: 1 ... 5 6 [7] 8 9 10