Thanks for the information. This comment in that interrupt.c file made me question if I should be using pins 6-9 instead of 9-12, or maybe avoiding them instead. I just wasn't quite sure what to make of it as I also ran...
Are all pins equal in response times for a digital transition on a T4.1?
I am setting no more than four interrupts active at a time to watch for either rising or falling edges.
For example:
void...
Returned... now to find a 20x4 LCD that actually works good.
I re-arranged the PCB so I can use Wire0 to make code use simpler, and then ran the clock and data lines through a voltage translator to boost them to 5v.
Board arrived today!
The timing looks much better. Pleased so far.
< 500 ns count is 999999
< 750 ns count is 1
< 1000 ns count is 0
< 1500 ns count is 0
....
Sum of counts is 1000000
Thanks, I'll take a look at that.
This one was sold by RPIGear. I'm trying to find out what chipset it uses (on the underside of the backpack) and is a 20 pin chip. A 2004A display with possibly a PIC16LF1829-I/SS...
What libraries work with a T4.1 with a I2C Wire2 output for the common 20x4 LCD panels?
So far I'm batting zero with the ones I've tried. Some are supposed to let you override the default, but either that isn't...
Thanks, that looks like it will work great. I've integrated the code changes and will give it a test and post the results after the board gets here next week.
I also have a second version of the code now using both...
Awesome - thanks everyone. I had found bits and pieces but not that reference to put it all together.
Moving to a micro-controller environment with a single program running is a bit like going back to my early...
I'm converting C code from a PI 4 to a Teensy 4.1. For the PI I use this to get the full time to nanoseconds:
struct timespec gettime_now;
long long f1_on_time;
clock_gettime(CLOCK_REALTIME, &gettime_now);...
Find latest posts