NuttyMonk
Member

The minimum time interval is about 3.7 milliseconds, the maximum is about 60 seconds, at least for the moment. I also want the clock pulses coming out of the project to be as jitter-free and stable as possible and...

I was just getting the timers and interrupts working and then i realised i don't know how to decide when the 3 cascaded timer channels have reached the correct count. I am currently using elapsedMiros to do the...

Ah, that makes sense. Computers-count-from-zero strikes again!!! lol NM

Hi all, so i found the eeprom.h file in this location C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy4\avr and changed this #define E2END 0x437 to this

Thanks for the replies. I'll give that a go. There's absolutely no issue with me using up enough space on the flash memory that i can't run at the max emulated EEPROM. That will give me 12 save spaces on the Teensy...

Hi KurtE, Thanks for the reply. The display can be showing several things as it has 3 pages. One page is just settings for the project so can be ignored. The other two screens show details about the clocks...

Those pins worked a treat. The display updates in 3.4 milliseconds now. It was 35 milliseconds when i was using I2C, Massive difference. Being able to pick the SPI pins will also help when creating the PCB. ...

Very interesting. Thanks, will check it out. NM

Thanks defragster. It's good to get confirmation. Much appreciated NM

Am i correct in saying that these are how the pins are labelled on the Teensy 3.2? MOSI = DOUT (Pin 11) SCK = SCK (Pin 13) Can i pick another SCK pin such as pin 14? If so would i have to change my MOSI pin to...

p.s. i've just realised that i might need to hook up more than 3 pins from the Teensy 3.2 and the SSD1306. I still have enough free pins on the Teensy 3.2 in my project but am even more confused which other pins i...