Teensyduino 1.56 Beta #4

Status
Not open for further replies.

Paul

Administrator
Staff member
Here is a fourth beta test for Teensyduino 1.56.


Linux 32 bit:
https://www.pjrc.com/teensy/td_156-beta4/TeensyduinoInstall.linux32

Linux 64 bit:
https://www.pjrc.com/teensy/td_156-beta4/TeensyduinoInstall.linux64

Linux ARM:
https://www.pjrc.com/teensy/td_156-beta4/TeensyduinoInstall.linuxarm

Linux ARM64:
https://www.pjrc.com/teensy/td_156-beta4/TeensyduinoInstall.linuxaarch64

MacOS 10.10 to 12.x:
https://www.pjrc.com/teensy/td_156-beta4/Teensyduino_MacOS_Catalina.zip

MacOS 10.7 to 10.14:
https://www.pjrc.com/teensy/td_156-beta4/TeensyduinoInstall.dmg

Windows:
https://www.pjrc.com/teensy/td_156-beta4/TeensyduinoInstall.exe


Changes since Teensyduino 1.56-beta3:

Support for Arduino 1.8.18
SD faster detection of SDIO media change (KurtE)
SdFat fix SDIO on MicroMod (mjs513)
Fix pins 38 & 39 on MicroMod
LittleFS improve erase+write speed for NOR flash chips
LittleFS fix FRAM defines
LittleFS add Write_Speed_Test example
Fix PXP_PS_CTRL register defines
Fix USB receive packet loss with MTP on Teensy 4
Audio fixes for very small buffer size (Eric Fontaine)
FreqCount fix 1st reading on Teensy 4 (mjs513)
Teensy Loader verbose info clearer Standard vs Lockable
 
Arduino's software download page hasn't updated, but the 1.8.18 files are on their server. Like with old versions of Teensyduino, it's pretty easy to copy the URL and edit the version number if you want to download the file.
 
Just installed over TD1.56beta3 no issues. Re-ran a few MTP/LFS quick tests on flash speed-up and File transfer and all is working at least so far :)
 
Looks like they got rid of the donation request and the links just download the file now. Or maybe it's just my browser or ad blocking?
 
Think depends which link you wind up using, just now got the donation page but earlier when I checked went right to download without the donation page.

Anyways - installed 1.1.18 and beta4 without issue. Reran a couple of the MTP/LFS tests and all seems well for now.
 
It took me a couple of attempts to install the zip file...

Norton decided to remove arduino.exe and arduino_debug.exe... tried to restore and system not happy, so deleted, rebooted, and then unziped again...
This time went through... Also needed to update my norton to exclude ...
 
Downloaded so far ...

Paul, you missed this interesting trivia:
Code:
Support the Arduino IDE
Since the release 1.x release in March 2015, the [B]Arduino IDE has been downloaded 57,348,600 times[/B] — impressive! Help its development with a donation.
 
Looks like Arduino's donation request is back. Or whatever happened with my browser & ad blocking isn't happening anymore.
 
IDE 1.8.18 installed(unzipped) and TD 1.56b4 on top of it: okay - not run yet

Ide 1.8.16 (current) beta 4 won't install because teensy_serialmon.exe is active, and TaskMan cannot terminate this task ??? > 'End Task' requests are ignored.
> machine been up 8 days, there is a pending restart for updates so will do that.

Question: What is the state of FS/MTP inclusions and what current libs from github are needed ?

ANSWER HERE :: Teensyduino-File-System-Integration-including-MTP-and-MSC
 
If I may ask, what was the issue with these pins on the MM?

The definitions were swapped, so if you used digitalWrite, digitalRead, analogWrite on pin 38, it would actually control pin 39, and vise versa. For Serial5.setTX and Serial5.setRX, you had to use the other pin number, not the pin actually controlled.

However, the definitions were correct for SDIO, so if you connect a SD card as Sparkfun's documentation shows and use SD.begin(BUILTIN_SDCARD), that has always worked properly. Initially most of the software testing with those pins focused on their main usage for high speed access to a SD card.
 
Using unzipped IDE 1.8.18 and TD 1.56 b4 T_4.1 sketch works with that fresh install.
> only Win 11 secure complaints were unzipped Arduino.exe (wanted to block, not usually seen?) and the typical 'JAVA' approve access on first run.

Also a couple of sketches of T_MM (new lockable Beta board: unlocked): Blink, USB-speed-print-test, MTP-test (more on MTP/FS thread)

RE p#10 - TD install okay after restart - but [unrelated] that involved failed Win update three times and Run of release Win 11 Setup.exe to current update - overwriting original summer beta Win11 series of WIP upgrades.
 
i use a new clean install of IDE1.8.18 and 1.56b4

my serial monitor size got resized, and i cant save another window size, its always like before. :(
 
i use a new clean install of IDE1.8.18 and 1.56b4

my serial monitor size got resized, and i cant save another window size, its always like before. :(

On Windows? Using that the CTRL+rolling scroll wheel changes textsize.

But as far as initial size and placement that seems to repeat restoring where it wants, not where last used.

There is a Serial entry giving screen coords/size in some fasion - the numbers here don't make sense, maybe they are documented and with IDE closed changing that will put it in the desired place and size.
 
ah yes on Win64 :)

i fixed it by myself:
1. tools > port > serial port
2. then resive/reposition the window and close
3. tools > port > teensy port
4. now it is always saved at this size/position :)
 
ah yes on Win64 :)

i fixed it by myself:
1. tools > port > serial port
2. then resive/reposition the window and close
3. tools > port > teensy port
4. now it is always saved at this size/position :)

Congrats! Good to know. Apparently the Teensy SerMon bypasses the save to preferences.txt that IDE SerMon does.
 
@PaulStoffregen
Was playing with the lockable TMM so decided just to start with writing the fuses and that worked without a problem. Thought the following was good to see the status of encryption:

TMM with Blink Sketch loaded:

Code:
09:09:12.491 (ports 5): usb_add: usb:0/140000/0/2/1  hid#vid_16c0&pid_0478 (Teensy MicroMod) Bootloader
09:09:12.586 (loader): remote cmd from 1432: "status"
09:09:12.589 (loader): secure mode can be locked: this is Lockable Teensy
09:09:12.589 (loader): encryption is possible on this Teensy, but not yet configured
09:09:12.589 (loader): Device came online, code_size = 16515072
09:09:12.589 (loader): Board is: Teensy MicroMod (IMXRT1062), version 1.07
09:09:12.598 (loader): File "C:\Users\Merli\AppData\Local\Temp\arduino_build_347683\Blink.pde.hex", 20480 bytes
09:09:12.601 (loader): File "C:\Users\Merli\AppData\Local\Temp\arduino_build_347683\Blink.pde.ehex", 20480 bytes, and 5152 loader utility
09:09:12.601 (loader): ehex is valid, key hash: 3CD8795F ############################################################
09:09:12.601 (loader): File "Blink.pde.hex". 20480 bytes, 0% used
09:09:12.604 (loader): set background IMG_ONLINE
09:09:12.612 (loader): File "C:\Users\Merli\AppData\Local\Temp\arduino_build_347683\Blink.pde.hex", 20480 bytes
09:09:12.615 (loader): File "C:\Users\Merli\AppData\Local\Temp\arduino_build_347683\Blink.pde.ehex", 20480 bytes, and 5152 loader utility
09:09:12.615 (loader): ehex is valid, key hash: 3CD8795F 9A168642 4FCF82ED AFC620F1 BCFECAB3 B978FA67 0D47FE2D F09253DD
09:09:12.615 (loader): File "Blink.pde.hex". 20480 bytes, 0% used
09:09:12.618 (loader): elf appears to be for Teensy MicroMod (IMXRT1062) (16515072 bytes)
09:09:12.618 (loader): elf binary data matches hex file
09:09:12.618 (loader): elf file is for Teensy MicroMod (IMXRT1062)
09:09:12.618 (loader): using hex file - Teensy not configured for encryption


Running the Fuse Write Sketch:
Code:
Writing public key hash
Okay: public key hash is good :-)

Writing decryption key
Okay: key written, setting config

Testing Bus Encryption Engine
Success: ciphertext decryption test passed :-)

Notice: JTAG is still enabled

Notice: Secure mode is not yet set, unencrypted
        programs are still allowed to run


Now when loading Blink Sketch
Code:
09:16:34.367 (loader): Board is: Teensy MicroMod (IMXRT1062), version 1.07
09:16:34.377 (loader): File "C:\Users\Merli\AppData\Local\Temp\arduino_build_347683\Blink.pde.hex", 20480 bytes
09:16:34.380 (loader): File "C:\Users\Merli\AppData\Local\Temp\arduino_build_347683\Blink.pde.ehex", 20480 bytes, and 5152 loader utility
09:16:34.380 (loader): ehex is valid, key hash: 3CD8795F ########################################################
09:16:34.380 (loader): File "Blink.pde.hex". 20480 bytes, 0% used
09:16:34.380 (loader): File "Blink.pde.hex" opened, but "Blink.pde.ehex" will actually be used 
...
09:16:34.407 (loader): elf appears to be for Teensy MicroMod (IMXRT1062) (16515072 bytes)
09:16:34.407 (loader): elf binary data matches hex file
09:16:34.407 (loader): elf file is for Teensy MicroMod (IMXRT1062)
09:16:34.407 (loader): using encrypted ehex (optional - secure mode not yet locked)

In both cases you see that the hex and ehex is created but before writing fuses the hex file is used after its uses the ehex. In addition the loader shows that prior to setting the fuses that the Teensy is not configured for encyption and similarly afterwards it shows that the Teensy is not configured for encyption. So pretty nice it shows you the status of encryption.
 
Status
Not open for further replies.
Back
Top