Note if you have a genuine digispark board and not a cheaper Chinese clone it will likely have the /RESET pin disabled in the fuses in which case you’d have to build a high voltage programmer to re-enable the /RESET pin functionality to allow standard voltage ISP to function. There is a strong possibility that XOD may make extensive use of the stack in RAM for function calls and auto variables etc that could lead the XOD program to overflow the limited 512 bytes or RAM on the Attiny85 while it runs but for now I’d take the bugs in the digispark cores to digistumps developers and hope they can complete the AVR core and complete the headers so their boards are programmable using the language defined in the published reference manual… I just manually downloaded the GitHub repository for the digistump avr core and libraries and it is newer than the 1.6.7 last release but still throws the same errors as 1.6.7 I do not know enough about the avr core at the moment to debug the digspark problem… sorry.
Attiny85 port pin pb5 software#
I do not believe the attinyX5 lack of hardware support for floats is an issue since it is performed in software anyway on most AVRs Mellis attiny85 definitions, the downside of that is I would have to program a digispark board using an Arduino UNO as ISP (see programming the Attiny85 using an Arduino youtube videos for tips how) and overwrite the micronucleus boot loader.
Attiny85 port pin pb5 code#
The exact same xod generated code compiles without error or incident if I use the non digispark David A. For me the errors all stem from incorrect handling of the: There appears to be some bugs in the digispark Arduino attiny cores where certain core features do not appear to have been implemented.
0 kommentar(er)
