Search results

I’m using multiple APA102 LED strips. FastLED describes how to achieve 4 output lines with 2 SPI channels by multiplexing: For Teensy 3.2 this works for 7, 14 and 11, 13 FastLED.addLeds<APA102, 7, 13>(leds,NUM_LEDS); FastLED.addLeds<APA102, 7, 14>(leds,NUM_LEDS); FastLED.addLeds<APA102, 11...

I would appreciate feedback on both the concept and the specs of this breakout board. I have created a Teensy 4.0 breakout board that allows me to work with both 3.3v and 5v digital and analog I/O. It’s in the DUE board format so I call it the “Teensy 4.0 DUE+.” It accepts both 3.3v and 5V...

Blink fixed the upload until I tried to upload my current sketch. Thanks

In the middle of testing a sketch my Teensy 3.6 started reporting “Port failed to open.” Setup: Teensy 3.6 and Teensyduino 1.31 beta #3. I tried 2 separate Teensy 3.2s, different USB cables and PC ports - same errors. Also tried a MEGA 2560. It uploads with no errors. To test the teensyduino...

Achieving the speed benefits of Dma+Spi Applying the DmaSpi library to my project required a bit of trial and error. Hope what I found is helpful to others: The example sketches for the DmaSpi library do not show how the functions would be used to take advantage of DMA. Each example includes...

I have both of these teensy to UNO breakouts. The http://embeddedcoolness.com/shop/rfx...ping-area-kit/ works with the 3.5/3.6. and all UNO pins are accessible. The https://www.sparkfun.com/products/13288 has a problem. The 3.5/3.6 extends over the ICSP pin cluster and cannot be fully inserted.

__MK20DX128__ &__MK20DX256__ identify the teensy 3.1 & 3.2. What are the corresponding IDs for 3.5 & 3.6? I missed the kickstarter campaign by 2 days, so I am looking forward to the retail release.

Using some of the OneWire Teensy3 code in my project, DIRECT_MODE_OUTPUT is not working. I'm using a Teensy 3.1 and OneWire from the Arduino 1.65 release, but the DIRECT_MODE_OUTPUT macro has not changed in quit a while. To test I extracted the macros into a simple sketch and tested against...

The current release has been working and is stable. Thanks for effort to make this library.

I added the dummy call to instantiate trx when the long &cs version locked up. Your new version fixed that problem to that it is not needed now. working code: long loopcntoutter = 5; long loopcntinner = 10; waitForKeyPress(); ActiveLowChipSelect cs(0, SPISettings())...

I tried a few more things and have one version that works with cs(0, SPISettings()). I left the //s in the working version to make it easier to see what changed. Problem code: DMASPI0.begin(); DMASPI0.start(); Serial.println("Testing src -> dest, with CHIP SELECT object")...

I worked through the ActiveLowChipSelect function. When I call in the .ino: ActiveLowChipSelect cs(value, SPISettings()); With the value = 10 the cs pin works properly. In chipSelect.h at line 55: pin_(pin); both pin_ and pin equal 10. With value = 0 both equal 0, and cs remains low. P.S...

I downloaded teensyduino 1.20 and the latest github DmaSpi library. I have not been able to get cs working. It remains LOW at all times. I paired down your example transfers to this: waitForKeyPress(); DMASPI0.begin(); DMASPI0.start(); Serial.println("Testing src -> dest, single...

Thanks cristoph for working this out! Works now.

I re-downloaded the zip from #21. first digit/enter gives the 234us. Second digit/enter stops at the point listed below. I'm using a Teensy 3.1. pins 11 & 12 are connected for the loopback (non-DMA works). I was not sure this zip was also updated to your github folder. I have not used DMA on...

I have been following your dmaspi development and tested the 10/7 zipped update. For me the sketch hangs at the first while(trx.busy()) regardless of the number of bytes to be transferred. If you are looking for an additional tester, I'll volunteer. Any library that can reduce the FPU load is...

Thanks for the detailed response. This will enable me to write more transportable code.

I added pinMode(pin,INPUT) before requesting info on each pin. Teensy3.1 does not return the port and bit mask even after this is added. The UNO32 reports properly even without this statement.

My understanding is that Teensyduino supports these two macros, and the port/mask format for Arduino compatibility.

digitalPinToBitMask and digitalPinToPort are not working I wrote a quick .ino to test digitalPinToBitMask() and digitalPinToPort() on several boards. While these macros work on the UNO, MEGA2560, and several compatibles, they are not returning the proper PORT or MASK on the Teensy3.0 and 3.1...

Thanks for the quick reply. I posted the library in github.com/Paul47/ShiftMatrixPWM2 The documentation still needs some work.

I have successfully converted the ShiftMatrixPWM library to work with the Teensy 3. This library uses SPI4Teensy3 and IntervalTimer libraries to maximize the speed. It handles a 10x16 RGB matrix and I will test it on a larger matrix soon. My test bed uses 2-75HC595/PNP transistor array on the...

Will a selection of 72Mhz for the Teensy 3.1 be added soon? Or will the 96Mhz setting work? If the point of the 3.1 is the added speed, it would be a shame to limit it to 48Mhz.

I am trying to port ShiftMatrixPWM to work with the Teensy3 and spi4teensy3. Compiling with Teensy3.0/3.1 as the target gives errors for PORT B, C and D as expected. I commented out the offending code, hoping to get a staring to to insert spi4teensy3 functions. I added <mk20dx128.h>...

I am surprised not to see this problem reported already. I receive the following compile on the Shiftpwm example program and the Teensy 3.0 in the Arduino IDE with Teensyduino installed. It compiles properly if the I set the hardware to any earlier Teensy. Do I have an outdated library or is...