Patrick Dowling

Hm. I guess it's a tough call because the concept of a "reset" doesn't really mesh with something that has no real beginning, and adding ever more things to try...

IIRC there's no hard requirement that only the lower 8 bits should be used; that seemed like a Good Idea At The Time and makes some sense given that the...

Catalina is such a PITA. Unfortunately I don't think there's an easy solution. I'm not sure when it started failing entirely though. My last info was that with newer versions...

The screen stops working because of a timing issue. That has two parts, and the issue exists in all versions. The first is that the apps use too much CPU...

It's also not uncommon to freeze the toolchain version as "known good" and you're on your own with any other. Issues aren't always as immediately visually apparent as display glitches...

Hm, the quickest solution seems to be to use the branch; eventually I suppose that should make its way into master. There's no need to modernize anything, and in the...

Yes, if one were to spend any significant amount of time on the code, something like that would be far more interesting. OTOH I already have a stm32f4 accelerated o_C...

> I thought the Teensy 4 pin layout was different. It is, but IIRC it's compatible enough for o_C (the internal DAC isn't required, and the ADCs might be worse?)....

Interesting. Not sure if there's any benefit for end users though, now that my branch seems to work on newer Teensyduinos (assuming that makes it upstream at some point). And...

Thanks. As mentioned above you should probably be ok with newer Teensyduino versions and the code in [this branch](https://github.com/patrickdowling/O_C/commits/fix/display_glitch). Heh, all I wanted was to see how interleaving the screen/DAC...