Teensyduino 1.60 Beta #3

Hi,

The gdb of this version unfortunately doesn't run on Ubuntu 24.10:

Code:
folkert@snsv ~/.arduino15 $ ./packages/teensy/tools/teensy-compile/11.3.1/arm/bin/arm-none-eabi-gdb
./packages/teensy/tools/teensy-compile/11.3.1/arm/bin/arm-none-eabi-gdb: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory

That libncursesw.so.5 has been replaced by .6, .5 is no longer available for the latest ubuntu.
 
On M2 Macbook Air with Sonoma 14.6.1 and IDE 2.3.3
Tried all the shenanigans in earlier in post for win and mac but still get no security stuff:
noTeensy.png


Read security was not recommend from M2 mac but it should be possible? Oh and added: Should Teensy Loader show 1.60-beta3 vs 0.60?
 
Support for EHEX in PIO is a great addition, great work!
I wish FlasherX could have EHEX support as well, it would bring it all together nicely!
 
Just reporting noticed today that issue at #27 seems to have resolved itself with no input from me except possibly upgrading to Sonoma 14.7.1
I'll be updating to Sequoia 15.1 soon and will report.
 

Attachments

  • security.png
    security.png
    761 KB · Views: 22
  • security2.png
    security2.png
    449.4 KB · Views: 19
I figured out how to rebuild newlib and libstdc++ (and nano versions), and am working on a small write-up. @Paul, do you think you’d like to test this for 1.60 or wait for 1.61? If the latter, I won't prioritize the write-up, and we can take more time. For example, I made a nano version of newlib that has C99 printf things, and a version of libstdc++ that has those "verbose termination" messages disabled with --disable-libstdcxx-verbose.
 
Let's put newlib rebuild off until at least 1.61.

After we wrap up the Black Friday Sale tomorrow, I'm going to go on a sprint to get MTP merged, and then a series of beta releases leading up to 1.60 release with MTP.

Might merge some other stuff besides MTP in the next week or two, but my main goal is to focus on MTP and only merge "small" things so we can get to a 1.60 release sooner. Everything else "large" can be considered for 1.61. But if too many other large things go in soon, we'd probably have to wait many more months before 1.60 can release.
 
Back
Top