Flashing Kint36 causes solid LEDs and keyboard is locked up

[zemackdaddy]

I discovered this after fetching and merging every thing that is current into my local repo.

Previous to 84ea77e, I was able to compile and flash my Kint36 (Teensy 3.6 for Kinesis Advantage). Everything worked.

I believe this is related to:

• make the full 4096 bytes of EEPROM work on Teensy 3.6 (core: make the full 4096 bytes of EEPROM work on Teensy 3.6 #12947)

If I use the commit above more recent, I can compile and flash but all of my LEDs are solid blue and the keyboard is locked up.

I am able to reset and flash just fine with the commit at or previous to 928d9f9.

I really don't know anything else about this or how it works. I just searched GitHub history for any commits related to this firmware and went backwards until I found the one that began working again.

Please let me know what else you want from me. Again, I can compile and flash just fine. It just breaks the keyboard with solid LEDs. I receive no errors during compilation or flashing.

[zemackdaddy]

I've held in the reset button on my Teensy 3.6 for 17+ seconds and then refreshed. No success. Still flashes but is all solid LEDs. If I flash back to 928d9f9, everything works fine.

[stapelberg]

Maybe we need to revert that commit again after all and just live without flash until someone can properly fix it.

I have no idea why it works for some people but not for others.

[zemackdaddy]

@stapelberg I am happy to help in anyway possible. I don't really understand the inner workings of the code or the boards but I could enable debug on my side or something to help gather information.

[zemackdaddy]

@stapelberg I got around to reverting the commit in question and indeed I am able to flash and have the keyboard work again.

[badgersow]

Just wanted to confirm that I'm experiencing exactly the same problem

[stapelberg]

I have sent #15695 to revert the change for now.

The next step is figuring out which Teensy 3.6s are affected, i.e. why some work and others apparently don’t. Maybe a post in the PJRC forums would be a good idea. If anyone could help with this, that’d be appreciated. I don’t have time for it currently.

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 30 days. If this issue is still valid, re-open the issue and let us know.
// [stale-action-closed]