Recent Posts

21

Digispark (Original) Support / Re: Ubuntu 20.04 64 bit library problem

« Last post by frednet on May 11, 2020, 05:07:23 am »

Finally fixed it, I needed to add a udev rule as per this post.https://digistump.com/board/index.php/topic,106.msg1565.html#msg1565

22

Digispark (Original) Support / Ubuntu 20.04 64 bit library problem (SOLVED)

« Last post by frednet on May 11, 2020, 04:58:43 am »

I'm trying to upload some code to a digispark board but it won't work due to a library issue. It appears loads of people have have a similar issue but I've tried the suggestions and they haven't worked. The error I get is  error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
The first thing I tried was replacing the micronucleus file in the 2.0a4 directory as someone mentioned in this
https://digistump.com/board/index.php/topic,1693.0.html
but I get a permission denied error as a result. Then I changed the permissions to the same as the original (including making it executable) and I'm back with the same error.
I then tried installing install libusb-0.1-4:i386
but it made no difference.
Every post I looked at was quite old, finally I found a post suggesting this sudo apt-get install libusb-dev
which then fixed that error but now hit me with a new one!
Now I get the request to Plug in device now... but when I do I get the following micronucleus: library/micronucleus_lib.c:66: micronucleus_connect: Assertion 'res >=4' failed.
Does anyone have any idea how to get it to work correctly? Is the linux driver unmaintained or something?

23

Oak Support / Max current on pins

« Last post by dynek on April 22, 2020, 07:47:59 am »

Hey,

What is max current that can be drawn from each pin / output on the oak, I have seen this in the specs.
Is it 12mA like other ESP8266/32 devices?

Thank you

24

Digispark (Original) Support / Re: "Unknown Device"

« Last post by granzeier on February 26, 2020, 02:48:36 am »

Don't forget to try the hub, that has had the greatest success rate for me.

Also, I do not have any Windows 10 systems, and so I will not be able to test anything regarding the drivers. If you want something tested with Linux Mint (19.2,) and a Tiny85-based Digispark clone, let me know.

25

Digispark (Original) Support / Re: "Unknown Device"

« Last post by Citrusl on February 25, 2020, 01:32:31 pm »

2020 and here.
Its been a long time, and we must start to work on Windows 10. (but i still have 7 for my fun).

Just to let you know that im using Arduino Teensy USB (Another Option to Digispark) and if the books doesnt lie here it says that the problem to Digispark could be the default driver-itself (or
 his version).
Im not an expert BUT...
The legend tells that Microsoft have an autorun driver detection and here is where all the magic starts.
have you seen that when you plug a keyboard or a mouse this devices are detected automatically? YES, thats what im saying.
So... passing the pencil rubber on the connector will not fix the problem. This require a new driver installation.

Then...
First, there must be a way to erase the default driver for Digispark. (We should search for just at least one device when this is recognized and start working).

What about the new driver?
I would really appreciate if Digispark works on this and share a solution, open source, or something new. In the meanwhile i will try to do it by my self to see what i can do.

It will take some time but i will let you know if i have success.

26

Oak Support / Re: Pinmode output

« Last post by dynek on January 31, 2020, 03:01:25 pm »

Erm OK: Oak Pin to ESP8266 GPIO Mapping
https://digistump.com/wiki/oak/tutorials/pinout

Would have been cool to have a mapping using e.g. P8 instead of (GPIO)15.

27

Oak Support / Pinmode output

« Last post by dynek on January 31, 2020, 10:55:46 am »

Hello guys,

I've been playing with the Oak, the Arduino IDE and ArduinoOTA, so far so good!
Wanted to go next and just put pinMode(6, OUTPUT); in the setup (tried other ports) and the Oak keeps resetting...

Am I missing something very obvious here?

Cheers

Code: [Select]

void setup()
{               
  Serial.begin(115200);
  Serial.println("Before");
  pinMode(8, OUTPUT);
  Serial.println("After");
}

void loop()
{}

Before

 ets Jan  8 2013,rst cause:4, boot mode:(3,0)

wdt reset
load 0x4010f000, len 1392, room 16
tail 0
chksum 0xd0
csum 0xd0
v3d128e5c
~ld
   Before

 ets Jan  8 2013,rst cause:4, boot mode:(3,0)

wdt reset
load 0x4010f000, len 1392, room 16
tail 0
chksum 0xd0
csum 0xd0
v3d128e5c
~ld
   Before

28

Oak Support / Re: Digistump / Oak dead ?

« Last post by dynek on January 27, 2020, 01:18:53 pm »

And finally OTA updates work! Fantastic.

I will still need to keep a way to upload the firmware from scratch, cause I would guess OTA updates could be made unavailable if the sketch has a problem.

29

Oak Support / Re: Digistump / Oak dead ?

« Last post by dynek on January 27, 2020, 01:05:46 pm »

OK had to lower flashing/upload speed to 115200. Seems to work OK, cool stuff!

30

Oak Support / Re: Digistump / Oak dead ?

« Last post by dynek on January 27, 2020, 12:58:53 pm »

OK P2 -> GND apparently but then I get:

Code: [Select]

Executable segment sizes:
IROM   : 227612          - code in flash         (default or ICACHE_FLASH_ATTR)
IRAM   : 26768   / 32768 - code in IRAM          (ICACHE_RAM_ATTR, ISRs...)
DATA   : 1252  )         - initialized variables (global, static) in RAM/HEAP
RODATA : 672   ) / 81920 - constants             (global, static) in RAM/HEAP
BSS    : 24880 )         - zeroed variables      (global, static) in RAM/HEAP
Sketch uses 256304 bytes (24%) of program storage space. Maximum is 1044464 bytes.
Global variables use 26804 bytes (32%) of dynamic memory, leaving 55116 bytes for local variables. Maximum is 81920 bytes.
esptool.py v2.8
Serial port /dev/cu.usbmodem14101
Connecting....
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: 5c:cf:[..]
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Traceback (most recent call last):
[..]
esptool.FatalError: Timed out waiting for packet header
esptool.FatalError: Timed out waiting for packet header