Recent Posts

Pages: [1] 2 3 ... 10
1
Other Arduino Talk / how do i change trinket gamepad device name?
« Last post by bidic17 on Today at 04:09:40 pm »
hi there.

sorry if i am in the wrong forum. i'm just looking around for an answer.

i made a contraption of three foot switches with a usb connection using the trinket and the trinket gamepad library. the software i'm using detects my contraption as "trinket gamepad," and i am able to use it without any problems.

I am looking to change the detected name of the device. "trinket gamepad" is not really an accurate name for the thing i've made. i was thinking of changing it to something like "Trinket USB Device."

I have done this with the usbconfig.h file:



but it does not work.

what have i missed?

by the way, how do i insert an image into my post?

thanks in advance.
2
Digispark (Original) Support / Digispark FW Update / 5 seconds
« Last post by sparkymike on April 29, 2017, 12:21:40 pm »
Hello, I've tried to cure the 5 seconds delay when booting up by micronucleus-ing a new fw file to my Digispark (actually a downgrade from v1.6 to v1.11, it said "Device has firmware version 1.6" during upgrade), but I got no luck, it still is lagging the 5 seconds during boot up. The fw file I've used was "micronucleus-1.11-entry-jumper-pb0-upgrade.hex" (7361 bytes). Any other versions are not working and give me an error "Program file is xxxx bytes too big for the bootloader!". Of course I've tried the current version(s) from github as well (v2.x), but all without luck. There, I've tried: t85_aggressive.hex and t85_default.hex.

Now I'm back to square one. What can I do in order to get rid of the delay?
Thanks in advance for your valued answer
Kind regards
Michael
3
Digispark (Original) Support / Re: Digispark keyboard change USB VID / PID
« Last post by Ralf on April 28, 2017, 12:13:58 pm »
Quote
Thanks Ralf

keine Ursache!
4
Digispark (Original) Support / Re: Digispark keyboard change USB VID / PID
« Last post by timherrm on April 28, 2017, 11:36:37 am »
Thanks Ralf, my fault.
It is working now!

Thanks!
Timo
5
Digispark (Original) Support / Re: Digispark keyboard change USB VID / PID
« Last post by Ralf on April 28, 2017, 08:13:12 am »
Hi Timo,

Code: [Select]
$ lsusb
Bus 002 Device 017: ID 16d0:0753 MCS Digistump DigiSpark

That's the USB  VID / PID of the micronucleus bootloader, it should disappear after 5 seconds and change into 16c0:27db (or your new IDs, if you changed it). If it doesn't change, then your keyboard code probably isn't working at all.

Ralf
6
Digispark (Original) Support / Re: DigiKeyboard and Bluetooth.
« Last post by JRios on April 28, 2017, 07:26:49 am »
Hi, long time ago :D

Yes, you are right, "SoftSerial_INT0" library is for standard Digispark (Attiny85), It need to be modified to be use in Digispark Pro (Attiny167), because "General Interrupt Mask Register" (GIMR) and "MCU Control Register" (MCUCR) does not exists in Attiny167 microcontroller, instead, you have to use " External Interrupt Mask Register" (EIMR) and "External Interrupt Control Register A" (EICRA), you can check all of this in the Datasheets...

However, I think that use this library in Digispark Pro does not make too much sense, because Pro has more pins that can be used by normal "SoftwareSerial" library.

Regards.
7
Digispark (Original) Support / Re: Digispark keyboard change USB VID / PID
« Last post by timherrm on April 28, 2017, 05:10:48 am »
Hi,
I have got the "Digistump AVR Boards by Digistump Version 1.6.7" installed in Arduino IDE 1.8.1 on Linux.

The file i modified was in /home/user/.arduino15/packages/digistump/hardware/avr/1.6.7/libraries/DigisparkKeyboard/usbconfig.h

One thing i noticed is, that the default lines were:
Code: [Select]
#define USB_CFG_VENDOR_ID 0xc0, 0x16
#define USB_CFG_DEVICE_ID 0xdb, 0x27

But also these values aren't correct.
Code: [Select]
$ lsusb
Bus 002 Device 017: ID 16d0:0753 MCS Digistump DigiSpark

This are the other files named usbconfig.h.
I cant find my current Vendor ID and Device ID in any of these files.
Code: [Select]
/home/user/.arduino15/packages/digistump/hardware/avr/1.6.7/libraries/DigisparkMouse/usbconfig.h
/home/user/.arduino15/packages/digistump/hardware/avr/1.6.7/libraries/DigisparkCDC/usbconfig.h
/home/user/.arduino15/packages/digistump/hardware/avr/1.6.7/libraries/DigisparkKeyboard/usbconfig.h
/home/user/.arduino15/packages/digistump/hardware/avr/1.6.7/libraries/DigisparkJoystick/usbconfig.h
/home/user/.arduino15/packages/digistump/hardware/avr/1.6.7/libraries/DigisparkUSB/usbconfig.h
/home/user/Downloads/arduino-1.6.12/hardware/arduino/avr/bootloaders/gemma/usbconfig.h
/home/user/Downloads/arduino-1.8.1/hardware/arduino/avr/bootloaders/gemma/usbconfig.h

Thanks for your help
timo
8
Digispark (Original) Support / Re: DigiKeyboard and Bluetooth.
« Last post by WhamBham on April 28, 2017, 03:15:18 am »
Sorry to bring back a dead thread , but am i correct in assuming SoftSerial_INT0.h library will only work with DigiSpark and not the pro as i get an error when i compile with the pro but not with Digispark

GIMSK' was not declared in this scope

GIMSK &= ~(1 << INT0);     // Disable INT0
9
Digispark (Original) Support / Re: Digispark keyboard change USB VID / PID
« Last post by Ralf on April 28, 2017, 02:49:57 am »
No.

Probably you modified a wrong file which was not used at compiling the stuff.

Ralf
10
Digispark (Original) Support / Re: Readout Lock
« Last post by rookie on April 26, 2017, 04:15:16 am »
Micronucleus states its small size as a "selling point" so I don't think they would bloat it with firmware reading function, but I'll check their docs and code to be sure.

The ATiny85 datasheet also says to set up the fuse bits before locking with LB1 and LB2: "Program the Fuse bits before programming the LB1 and LB2."

What Fuse bits do I have to change for maximum security? SELFPRGEN is enabled already I presume for the bootloader to work, and security related bits are DWEN and SPIEN I think. Should I change them?

I purchased USBasp but I'll have to wait a week before it arrives. So I'll try to lock it then, risky but nonetheless :) I'll report back when I do.

Thank you, Peter!
Pages: [1] 2 3 ... 10