Search results

It was some versions ago, but I definitely tried replacing the original teensy_secure by my confirmed working patched teensy_secure and then upload code using Arduino IDE. I found out, the manually generated ehex had the correct csf, while the one uploaded had not. I guess it was on 1.57.2. if I...

It looks very good :) Only thing that gets me wondering is the much faster upload speed than my java tool. Also: Because teensy.exe ignores the ehex if you chose upload from arduino and has the ehex creation code itself, would it be possible to make use of this somehow even using the automatic...

I was using Windows x64, but I guess Linux x64 will be as useful as Windows.

Hi again, the following parts of HAB4_API.pdf from docs folder show the right values and how to use them. The correct Bytes for the unlock command should be: B2 00 08 1E 00 00 00 03 B2 is for unlock 0008 is total command length (including header and length bytes) 1E means SNVS 00 00 00 03...

This and maybe also the LP_SWR flag. The hex values are in the cst API docs. Would be really great. Best wishes, Alice

Hi, I would also greatly appreciate that change and have successfully tried it by patching the binary teensy_secure. It would also be of some benefit, if also the teensy binary would contain the same code for the DCD. I wrote a java version of the teensy_secure which is able to accomplish those...

Hi, I wrote this little example of a tool to prepare and upload code to Teensy 4.1 Lockable. You can check it out aat https://github.com/Al1c3-1337/teensytool Best regards, Alice

Hi, It would be great, if the CSF contained in teensy_secure.exe (and also teensy.exe) would be extended with the UNLOCK command for SNVS SET ZMK (B2 00 08 1E 00 00 00 03). Just validated it works after manually patching the 1.57.2 teensy_secure windows executable. No NDA documents were needed...