Search results

  1. F

    Does anyone have T3.2 ref board for IC_MKL02Z32_QFN16?

    I am looking for Teensy 3.2 reference pcb files with footprint for IC_MKL02Z32_QFN16(bootloader) and Micro USB, the PCB files from https://www.pjrc.com/store/ic_mkl02.html have footprint for the discontinued IC_MKL04Z32_TQFP32(bootloader) and Mini USB.
  2. F

    Does anyone have T3.2 ref board for IC_MKL02Z32_QFN16?

    I found a 8 years old eagle T3.2 ref board on github but it has footprint for IC_MKL04Z32_TQFP32 and Mini USB instead of Micro USB.
  3. F

    Can alc883(codec) be wired to teensy?

    Used this code: #include <Audio.h> #include <Wire.h> #include <SPI.h> #include <SD.h> #include <SerialFlash.h> // GUItool: begin automatically generated code AudioSynthWaveformSine sine1; //xy=204.1999969482422,187.1999969482422 AudioInputUSB usb1...
  4. F

    Can alc883(codec) be wired to teensy?

    Is this good? pin 10(sync) > pin23(teensy 3.2) pin 6(bitclk)> pin9(teensy 3.2) pin8(sdata in) > PIN22(teensy 3.2) what about teensy pin 9 "Output, 11.3 MHz" and alc883 pin6 "24Mhz bit clock input"?
  5. F

    Can alc883(codec) be wired to teensy?

    If so, how? What is "Sync"?, is WS; FS - Frame Sync? (datasheet)
  6. F

    SD.h working with audio shield(on t3.2), SD.h not working on t4.1 built in sd reader

    Example file from: C:\arduino-1.8.19\hardware\teensy\avr\libraries\SD\examples\CardInfo\CardInfo.ino (Teensyduino, Version 1.57) With t4.1 I used: const int chipSelect = BUILTIN_SDCARD; With t3.2 I used: const int chipSelect = 10; SPI.setMOSI(7); // Audio shield has...
  7. F

    Teensy3.2; 4.0 wireless audio nRF24L01 - delay increases over time

    Added a switch to "radio.flush_tx();", resets the latency to "0", then the problem repeats.
  8. F

    Teensy3.2; 4.0 wireless audio nRF24L01 - delay increases over time

    At first there is almost no delay, over a few minutes there is a delay of around 1 sec.Accidentally the SCK of the nRF24L01(transmitter) got disconnected, reconnected it back and the delay disappeared(got fixed) and then after a few minutes it it appeared again.Disconnected and reconnected the...
Back
Top