I wrote before about coming into contact with a Teensy counterfeit, which I only discovered after help on the forums [1]. It took me at least 4 to 8 hours of work before eventually coming to a solution. Now today I'm working with an older Teensy++ 2.0 board that I'm certain is not a counterfeit. This board I've had work just fine in the past, as far back as 3 years ago, but once again the teensy loader does not work. I'm assuming this is all because of the cat+mouse game teensy is trying to play to weed out the counterfeits. I understand that, but it appears to be adding overhead to legitimate users now as well. I'm bothered that I will now have to spend what could be a couple hours to a couple days trying to figure out what the right combination of software I would need to get this working again. Considering I'm trying to use the teensy to duplicate a project I did a couple years ago, I was not anticipating this new overhead and time dealing with teensy was not allocated in the budgting for this project. For me, and I'm sure others, that's new overhead time that wasn't there before and that I will probably try to find ways to resolve, which could include switching to a different prototyping ecosystem.
1. https://forum.pjrc.com/threads/4597...t-1-8-2-amp-Loader-gt-136?p=151603#post151603
1. https://forum.pjrc.com/threads/4597...t-1-8-2-amp-Loader-gt-136?p=151603#post151603