Teensy 3.0\3.1 Hardware SPI Support

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Constructor for HW SPI 
U8GLIB_SSD1306_128X64_2X display(SS, 9, 14);
vs for SW which works
U8GLIB_SSD1306_128X64_2X display(SLK, MOSI, SS, 9, 14);

What is the expected output? What do you see instead?
Blank Display, works in software mode but conflicts with SD Card on SPI bus.

What version of the product are you using? On what operating system?
Windows 7 X64 with Arduino IDE 1.0.5 with Teensy addon.

Please provide any additional information below.

Original issue reported on code.google.com by blackspa...@gmail.com on 22 Apr 2014 at 2:32

[GoogleCodeExporter]

Not sure how to support this as it is difficult for me to test. Precondition is 
to use different chip signal lines for both devices.
Is it Teensy 3.x? Currently there is no HW support for Teensy 3.x

Original comment by olikr...@gmail.com on 22 Apr 2014 at 5:08

[GoogleCodeExporter]

I am using different CS pins. I understand that is it hard to test and not 
supported. Maybe you can point me to the function I can try and work on to get 
it to work. I had it working with the Adafruit lib modified for hardware SPI.

I am working with a PCB so currently can't make any changes to hardware till 
the next hardware revision.

Thanks for anything you can help with.

Original comment by blackspa...@gmail.com on 22 Apr 2014 at 5:15

[GoogleCodeExporter]

you need to implement your own "com" procedure. Someone else had done a nice 
description on this:
http://blog.bastelhalde.de/?p=759

Original comment by olikr...@gmail.com on 22 Apr 2014 at 5:36

[GoogleCodeExporter]

Awesome, I will try and get it to work then. Let you know how it goes.

Original comment by blackspa...@gmail.com on 22 Apr 2014 at 7:27

[GoogleCodeExporter]

Does the Arduino version of the library support adding your own stub or is it 
only the ARM version? Do you think the ARM version will still working with the 
Arduino IDE? I am trying to keep using the Arduino IDE so the device is easily 
hackable by others. 

Thanks.

Original comment by blackspa...@gmail.com on 23 Apr 2014 at 4:39

[GoogleCodeExporter]

The arm version does not include the C++ interface. So it might be difficult 
for the Arduino users.
On the other side, there is a generic C++ constructor, which allows you to 
specify the com interface:
U8GLIB(u8g_dev_t *dev, u8g_com_fnptr com_fn)

Then, for the Arduino Users, this should be:
U8GLIB(u8g_dev_ssd1306_128x64_2x_sw_spi, my_com_fn)
where "my_com_fn" has to be supplied by you as described in the mentioned 
tutorial. Another good thing by using the arduino variant is, that you do not 
need to provide the delay procedures (these are already part of the arduino 
variant).

Original comment by olikr...@gmail.com on 23 Apr 2014 at 4:51

[GoogleCodeExporter]

Okay I have this mostly setup.

How do I specify the DC and reset pins, in the com interface?

So something like this?

U8GLIB(u8g_dev_ssd1306_128x64_2x_hw_spi, u8g_com_hw_spi_fn);

or is it sw_spi even if using hardware?

Also where do you define the object name? In my case display.

Original comment by blackspa...@gmail.com on 23 Apr 2014 at 5:28

[GoogleCodeExporter]

> How do I specify the DC and reset pins, in the com interface?
Your com procedure has to deal with these lines, so if you use fixed pins, then 
just use fixed bins in your com callback procedure. No need to specify them on 
the constructor.

> or is it sw_spi even if using hardware?
The device type does not matter. You can use u8g_dev_ssd1306_128x64_2x_hw_spi 
or u8g_dev_ssd1306_128x64_2x_sw_spi. Only your com procedure matters.

> Also where do you define the object name? In my case display.
Should be this:
U8GLIB display(u8g_dev_ssd1306_128x64_2x_hw_spi, u8g_com_hw_spi_fn);

Original comment by olikr...@gmail.com on 23 Apr 2014 at 9:32

[GoogleCodeExporter]

Thanks so much!!! I got it to work!! Now I just need to clean it up and make it 
more flexiable so anyone can use it. 

I will post on github once its ready.

Actually all it does is uses the Arduino SPI library which is installed by 
Teensy software so the same functions work.  Might be easy to get it to work on 
the core library. 

This post helped as well
http://forum.pjrc.com/threads/24357-u8glib-now-has-an-ARM-variant?p=46427

And looked the Adafruit library as well.

So does your library use the Arduino SPI library or direct port\registers?

Thanks.

Original comment by blackspa...@gmail.com on 24 Apr 2014 at 4:09

[GoogleCodeExporter]

Great.

Regarding HW SPI: I decided to to write directly to the uC registers. Now i 
know it had been a wrong devision. In ucglib (another more recent lib from me) 
i am using SPI fronm the IDE to be more portable.

Original comment by olikr...@gmail.com on 24 Apr 2014 at 4:42

[GoogleCodeExporter]

No problem, it was a good exercise, ;). Cool, I will have to check out the 
ucglib library. I have a Color LCD here. If you want I can test for you. Its a 
2.2in LCD with the iL9341 driver. Right now its connected to a Arduino UNO. I 
haven't had a chance to really play with it.

Original comment by blackspa...@gmail.com on 24 Apr 2014 at 5:06

[GoogleCodeExporter]

Yes, iL9341 is supported and standard SPI.h should work. In fact i learned a 
lot from U8glib and did a major cleanup of the internal interfaces for Ucglib.

Original comment by olikr...@gmail.com on 24 Apr 2014 at 8:08

[GoogleCodeExporter]

Ucglib is available here for download:
http://forum.arduino.cc/index.php?topic=222327.0
Or drop me an e-mail for the latest release.

Original comment by olikr...@gmail.com on 24 Apr 2014 at 8:11

[GoogleCodeExporter]

u8glib 2.x should use the Arduino SPI library instead of the AVR sub system.
will put this into "Milestone-Collect"
However i did not check if this request already exists.

Original comment by olikr...@gmail.com on 16 Jun 2014 at 7:20

• Added labels: Milestone-Collect, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Any updates on the status of hardware SPI for the Teensy 3.0/3.1?

Original comment by lucas.be...@gmail.com on 3 Oct 2014 at 10:15