Author Topic: USB connected LCD (Read 28165 times)

digistump · « **on:** January 05, 2013, 11:18:37 pm »

If you haven't yet check out one of the newest examples of how to use the DigiUSB library:

http://digistump.com/wiki/digispark/tutorials/usb2lcd

Hope you enjoy it!

Trakkasure · « **Reply #1 on:** January 08, 2013, 07:14:46 pm »

When attempting to test this code:

/Users/loggedinuser/Applications/DigiSpark.app/Contents/Resources/Java/hardware/tools/avr/bin/../lib/gcc/avr/4.3.2/../../../../avr/lib/avr25/crttn85.o:(.init9+0x2): relocation truncated to fit: R_AVR_13_PCREL against symbol `exit\' defined in .fini9 section in /Users/loggedinuser/Applications/DigiSpark.app/Contents/Resources/Java/hardware/tools/avr/bin/../lib/gcc/avr/4.3.2/avr25/libgcc.a(_exit.o)

Please advise.

digistump · « **Reply #2 on:** January 08, 2013, 07:25:28 pm »

Do you perhaps not have the board and programmer both set to Digispark (Tiny Core)?

That is the only thing I can think of, unless you made any changes to the code.

Trakkasure · « **Reply #3 on:** January 08, 2013, 07:30:32 pm »

I first loaded the LCD example, (displaying the string \"Digispark!\" on the display)
Changed the text and recompiled. (And uploaded)

All succeeded.

Then loaded the USB2LCD to test this code.

When clicking \"verify\" I received that error. So the error was during compile.
Digispark (Tiny Core) is selected as the board.
Digispark is the programmer (although for just compiling this shouldn\'t matter)

Trakkasure · « **Reply #4 on:** January 08, 2013, 07:32:44 pm »

I should add, I\'m using the latest version of Digispark (from Jan 5th)

Using OSX Mountain Lion (had to make the security changes in system preferences to get it to execute)

Trakkasure · « **Reply #5 on:** January 08, 2013, 07:38:28 pm »

Also, I renamed Arduino.app to DigiSpark.app to keep track of different IDEs for the different boards I have.

Trakkasure · « **Reply #6 on:** January 08, 2013, 07:42:13 pm »

After commenting out all references to DigiUSB in the code (yea, pointless for using the example, but a simple debugging step for me) it compiled fine.

digistump · « **Reply #7 on:** January 08, 2013, 07:44:25 pm »

Ok - got it figured out, it is a bug in the Arduino IDE (or the avr compiler/linker more precisely), I\'m packing orders right now but I\'ll get it fixed and upload a new version tonight

(here is all the technical details: http://avr.2057.n7.nabble.com/Advice-on-R-AVR-13-PCREL-errors-linking-for-Tiny85-and-Mega168-td9327.html)

digistump · « **Reply #8 on:** January 08, 2013, 07:44:53 pm »

commenting out helped because the bug is related to when you get over a certain size compiling for attinys

Trakkasure · « **Reply #9 on:** January 08, 2013, 07:53:54 pm »

Excellent. Thanks.

I\'m systematically testing my shields with different code.

So far, I\'m very happy with the DigiSparks!

digistump · « **Reply #10 on:** January 08, 2013, 08:15:29 pm »

Can you try this version: http://s3.amazonaws.com/digispark/builds/arduino-1.03-osx-digispark-2013-01-08.zip

Trakkasure · « **Reply #11 on:** January 08, 2013, 08:39:50 pm »

Downloading to test now.

Trakkasure · « **Reply #12 on:** January 08, 2013, 09:21:53 pm »

Everything compiles and uploads.

I\'m having trouble locating the python application (is it somewhere in the Java directory?) to send data to the DigiSpark through the USB to have it show on the LCD.

Trakkasure · « **Reply #13 on:** January 08, 2013, 09:24:14 pm »

The ruby version requires ruby >= 1.9.3
I only have 1.8.7 (standard on Mountain Lion)

Trakkasure · « **Reply #14 on:** January 08, 2013, 09:25:54 pm »

Ok. Found the python app.. I was looking in the .app not thinking to look in the ZIP directory.