Teensyduino 1.48 Beta #1

Status
Not open for further replies.

Paul

Administrator
Staff member
Here is a first beta test for Teensyduino 1.48.


Linux 32 bit:
https://www.pjrc.com/teensy/td_148-beta1/TeensyduinoInstall.linux32

Linux 64 bit:
https://www.pjrc.com/teensy/td_148-beta1/TeensyduinoInstall.linux64

Linux ARM:
https://www.pjrc.com/teensy/td_148-beta1/TeensyduinoInstall.linuxarm

Linux ARM64:
https://www.pjrc.com/teensy/td_148-beta1/TeensyduinoInstall.linuxaarch64

Mac OS-X:
https://www.pjrc.com/teensy/td_148-beta1/TeensyduinoInstall.dmg

Windows:
https://www.pjrc.com/teensy/td_148-beta1/TeensyduinoInstall.exe


Changes since Teensyduino 1.47:

Support for Arduino 1.8.10
Drop support for old Arduino versions 1.0.6, 1.6.5 and 1.8.1
Improve Serial Monitor efficiency, Arduino 1.8.9 & 1.8.10 only
Update FastLED to 3.3.1, fixes compile error on Teensy LC (Daniel Garcia)
Fix more than 2 IntervalTimer instances on Teensy 4.0
Fix Teensy 4.0 low power mode for 24 MHz (Defragster)
Teensy 4.0 SPI signal drive strength changed on Teensy 4.0 (KurtE)
Fix I2S output on Teensy 3.0


The Serial Monitor improvement still has debug printing to Arduino's console. You'll see messages there as you open and close the serial monitor, or connect and disconnect Teensy. If you get any messages in red, especially any Java exceptions, please report them on this thread.
 
Installs on macOS 10.15 Catalina beta 19A558d. Didn't compile the Blink example for T4.0 in a first attempt, got an error message telling that Arduino could not access the hardware directory which is buried inside the Arduino.app by Teensyduino.

Had to go into System Preferences - Privacy and to grant full disk access to the Arduino.app manually. Now, it works like a charm!
 
@Theremingenieur - Do you have a Teensy 4.0 handy? Any chance you could run the USB print speed test and let me know how 10.15 does?

On 10.14 Mojave it still uses a lot more CPU than Windows or Linux, but at least the Arduino IDE doesn't seem to give out of memory exceptions.
 
I have (naturally) a Teensy 4.0 handy! :)

USB print speed test does between 240,000 and 248,000 lines per second. CPU usage is rather high :
Capture d’écran 2019-09-14 à 10.09.46.jpg
 
I guess lower CPU use was a long shot. Pretty sure Apple hasn't changed much about that part of the OS in quite a long time.

If you leave it running, does the serial monitor ever stop or freeze up, or Java start throwing exceptions about running out of memory?
 
It did run for about 10 minutes until serial output simply stopped without any error message in the Arduino console :
Capture d’écran 2019-09-14 à 10.40.02.jpg
Arduino does not longer eat CPU (2%) but kernel remains on about 70% from which I guess that the Teensy keeps sending.
 
Closing and re-opening the Serial Monitor shows that the brave Teensy 4.0 continues working. But the serial monitor stalls in arbitrary intervals.
 
It did run for about 10 minutes until serial output simply stopped without any error message in the Arduino console :
View attachment 17593
Arduino does not longer eat CPU (2%) but kernel remains on about 70% from which I guess that the Teensy keeps sending.

Thierry - when it stops - add another Teensy or plug in or remove some other USB device - mouse - flash drive. Any chance that makes it restart?

257K is a good speed - a shame it dies and eats so much of the CPU.
 
Ok. Had to find an USB hub first... Restarted everything then, with the T4 connected through a passive USB-Hub and an USB-C adapter to the MacBook. Waited for the serial monitor stalling. Then unpacked and connected a brand new T3.2. This made the serial monitor run again. Observations continue...

But I must say that I personally do not see that serial monitor stalling as an important issue. None of my projects is made to flood the Serial monitor with so much data and I’d guess that most other real world projects do neither. To me, it looks rather like an academic thing...
 
Ok. Had to find an USB hub first... Restarted everything then, with the T4 connected through a passive USB-Hub and an USB-C adapter to the MacBook. Waited for the serial monitor stalling. Then unpacked and connected a brand new T3.2. This made the serial monitor run again. Observations continue...

But I must say that I personally do not see that serial monitor stalling as an important issue. None of my projects is made to flood the Serial monitor with so much data and I’d guess that most other real world projects do neither. To me, it looks rather like an academic thing...

Thanks for that … it was just a TEST - I get stalling on Win 10 when I resize a BUSY window - it was happening intermittently, though I stopped waiting for that when I spend a couple seconds resizing a busy window it stalls. Then any USB device arriving or departing would wake the T_SerMon code and it would start again.

When Paul gets to look at it - it will be interesting for him to know it acts the same on both platforms to help him reproduce - and perhaps resolve - the issue especially since his Win 10 system hardware is less plentiful. Also interesting you noted the MAC core was still eating lots of cycles - on Windows it drops off over 50% of a lesser number when that happens.
 
After reanimating it by plugging the T3.2 (blinking in factory/hid mode) it ran until stalling again. Then, un-plugging and re-plugging the T3.2 makes no more effect, but un-plugging and re-plugging the T4.0 restarts the counting and re-animates the serial monitor window which I had left open.
 
@Paul: Did UNZIP of 1.8.10 on Windows 10. TeensyInstaller ran well - no issues. IDE 1.8.10 must not be on KNOWN list yet as I had to tell Windows to RUN ANYWAY. Had to Approve JAVA as usual - then upload worked to a T4.

Second sketch uploaded was my long line LPS test - resize for a MINUTE and it never stalled. Did again across both monitors and back to the big one and no issue from smallest size with lots of line shifting.

The LPS reported in that sketch is about what it was at 220K+ and CPU is 6% to 8%.

Running 8+ minutes and 3rd and 4th set of resize - No Problem - more than I could ever do before. And nothing of note in the console:
Code:
Sketch uses 13968 bytes (0%) of program storage space. Maximum is 2031616 bytes.
Global variables use 20240 bytes (1%) of dynamic memory, leaving 1028336 bytes for local variables. Maximum is 1048576 bytes.
T:\arduino_1.8.10\hardware\teensy/../tools/teensy_post_compile -file=lps_test.ino -path=T:\TEMP\arduino_build_888535 -tools=T:\arduino_1.8.10\hardware\teensy/../tools -board=TEENSY40 -reboot -port=usb:0/140000/0/8/7 -portlabel=hid#vid_16c0&pid_0478 Bootloader -portprotocol=Teensy 
TeensyPipeMonitor open usb:0/140000/0/8/7
opened, dev=COM37, name=Serial

>> 1500 seconds still running fine with resize. Started 2nd T4 - using TyComm as Sermon. TyComm 85K to 112 lps and using 27% of CPU for 2nd T4.

Will be running the next few hours ...
 
Last edited:
@Paul -

I just setup Arduino 1.8.10 and TD 1.48 B1 on one my Linux computers. I was playing with HelloSerialMonitor. I selected the 'Show Timestamp' checkbox and nothing happened.
Tried Arduino 1.8.9 Serial Monitor which is setup with TD 1.47 and the time stamps were showing.
Has this been disabled in Arduino 1.8.10?
 
@wwatson and @Paul

I am using IDE 1.8.9 with TD1.47-beta1 and timestamp is available with that combination either.
 
just a guess: the missing timestamp is part of recent speed rework work in progress?

t_sermon running here since last post now beyond this 27778 seconds - but running fine and no amount of resizing causes issues having only uploaded 2 sketches a couple of times - still hold lps speed and CPU ~7% and RAM 438MB in use is good!:
>count=2156887153, lines/s=224071 >count=2156887154, lines/s=224071 >count=2156887155, lines/s=224071 >count=2156887156, lines/s=224071 27778
>count=2156887157, lines/s=224071 >count=2156887158, lines/s=224071 >count=2156887159, lines/s=224071 >count=2156887160, lines/s=224071 27778



>count=2311357145, lines/s=233671 >count=2311357146, lines/s=233671 >count=2311357147, lines/s=233671 >count=2311357148, lines/s=233671 28455
>count=2311357149, lines/s=233671 >count=2311357150, lines/s=233671 >count=2311357151, lines/s=233671 >count=2311357152, lines/s=233671 28455
 
iMac 10.14.6, Arduino 1.8.10, TD 1.48 B1, on T4
After loading certain sketches the serial port goes away and won't come back until I compile something like blink and press the button. T4 crashes?

Haven't narrowed it down but a sketch like Part_1_04_Blink_While_Playing in the tutorials crashes the T4.

Perhaps anything with Audio.h or SerialFlash.h?
 
Last edited:
I have just bought a Teensy 4.0 board, but when I try to select the USB type, it only shows Serial. Is there something wrong with my setup? Or is this a bug in 1.48?
(This is on Mac OS 10.14.6, with Arduino 1.8.10)
 
ralphrmartin
That is what's available now with Teensy 4.0.

FYI, 1.48 is Beta software, ie not ready for prime time. If your just starting with this you may want to go back to Arduino 1.8.9 and Teensyduino 1.47. Typically Beta software takes 8 to 9 revisions to become stable.
 
That 'Serial' means serial over USB I think. You still use the serial port. Perhaps you need to press the button on the Teensy to get it to show up in the ports for the 1st time per the instructions.
 
That's not quite what I meant. I want to use USB for other things than serial...

Using a Teensy 3.2, 3.5, 3.6 to prototype you can start working immediately - Teensy 4.0 support will arrive ASAP and should be expected to be compatible when complete.

At this time Teensy 4.0 hardware is 'Serial Only' just out of Beta and into production and given the choice of 'Perfect function' or 'Usable Hardware' - Usable hardware has to come first or the software can't be perfected. Hardware was great in Beta and refined to be production ready - at which point getting them made and out to a general audience took precedence - along with resolving critical support issues. Also dealing with external changes like New builds and changes to Arduino IDE itself.

So at this time 'Serial' for USB connect is the only supported T4 interface - and it runs at 480 Mbps - up from 12 Mbps and that causes IDE faults and issues already that are being addressed to minimize IDE Crashes and code loss or system instability.

Paul has noted as fast as the T4 presents to the PC now - it has significant room to speed up when the USB stack is updated to be faster and when support for the other interfaces will be presented. So building and extending the current system on an unstable base doesn't make sense.
 
It would have been helpful for this to be made clear somewhere in the sales / announcement pages (with a statement of what is ready now and full support for the rest will be coming later etc .) I feel I have been a bit misled. The earlier Teensy models don't have enough CPU power for my project (processing ultrasonics). Fortunately, my project is not time critical...
 
Status
Not open for further replies.
Back
Top