Teensyduino 1.59 Beta #5

Paul

Administrator
Staff member
Here is a fifth beta test for Teensyduino 1.59.

This is meant to be a candidate for 1.59 release.

Arduino 2.0.x, all systems platforms:
use Boards Manager to install Teensy version 0.59.5
(to refresh versions, Shift-Ctrl-P and click "Arduino: Update Package Index")

Arduino 1.8.x, Linux 32 bit:

Arduino 1.8.x, Linux 64 bit:

Arduino 1.8.x, Linux ARM:

Arduino 1.8.x, Linux ARM64:

Arduino 1.8.x, MacOS (Catalina to Sonoma)

Arduino 1.8.x, Old MacOS (Mojave)

Arduino 1.8.x, Windows:

PlatformIO, DIY beta support:


Changes since Teensyduino 1.59-beta4:

analogRead() disable pin input keeper on Teensy 4.x
attachInterrupt always turn on pin hystersis on Teensy 4.x
Add DSB before return from interrupts from attachInterrupt
Wire: Scanner example scans all ports
Wire: Use WIRE_INTERFACES_COUNT for instances on Teensy 3.x
Add SEMC bitfield defines
Add MPU config for SEMC needed by SDRAM_t4 library
SdFat: Fix compiler warning with LTO linking on Teensy 4.x
SdFat: Removed a couple extraneous printfs (mjs513)
Fix makeWord() return type
Fix compiler warning with LTO on Teensy 3.x
LittleFS: Fix compiler warning with LTO linker
Close Teensy Loader on Arduino IDE 2.2.2 Boards Manager uninstall
Print memory info on Arduino IDE 2.x.x normal color, not red
Fix for wrong Teensy auto-reboot during upload
 
Win11 install for both IDE 2.2.2 and 1.8.19 - no issues.

Ran sdram_realloc on both with no issues using the dev board.

Hooked up 4 boards - 2 T4.1s, 1 T4.0 and the SDRAM Dev Board - ide 2.2.2 picked up each board and loaded sketch to the correct boards
 
Moved to IDE 2 updated to 1.59b5 (0.59.5) and it is working as it should!
So far only tested on the SDRAM DevBoard that shows 'good install' and needed updates are there for that.
 
This is a timely update!
I was having non-linearity issues with ADC readings with a Teensy 4.0 last week, and having searched this forum, discovered the problem with the input pin "keepers".

Just to clarify, to disable the input keepers, we just use the analogRead() command as normal, with nothing more to do?

ie; I read the value on pin "PSU_DAC" into variable "psu_dac_raw"

psu_dac_raw = analogRead(PSU_DAC);


I always appreciate the efforts of those that develop and help debug these updates.
Thanks guys.

ps
Although still mourning the loss of the 3.2, I have started playing with a 4.0 (that was purchased several years ago and sitting in the parts bin since), and love the FPU, which I am finally putting to good use! Also using the cheap 4-Ch Logic Level Converters found on AliExpress to interface to a Nextion HMI (5V) and a MAX232 (5V). I do miss the 5V tolerant pins.

pps 0.59.5 installed with IDE2.0 on a Win 10PC.
 
My flight controller running on the 4.1 works perfectly fine with the update, that includes everything from CAN to Serial to MICRO-SD to Pin Toggling to External PSRAM. All working very well so far!
 
I will publish 1.59-beta6 in a few days, meant as a final test before 1.59 release. If anyone has any last minute issues I should address, now is the time to bring them up!

1.59-beta6 will use (only for beta6) a new URL for the Arduino IDE 2.2.x package index, so we can test the USB device detection and serial monitor utilities before a final 1.59 release. This is needed because of the unfortunate design Arduino chose where all package versions use the latest discovery and monitor utilities, so when we're testing 1.59-beta5 on Arduino IDE 2.2.1, we're really using those utilities from version 1.58.
 
Done a little playing so far with it... W11

Maybe new Arduino release soon? At least last nights nightly has brought in newer CLI...
 
Does 1.59-beta5 solve the issue you were seeing with attempting upload to the wrong board? This one is still on my list of issues, so wanted to specifically ask if this is solved on your machine?
Powered down DevBoard and Powered Up: T_4.0 + T_4.1 + T_4.1
Opened Blink.ino in IDE 1.8.19
Selected Board/Port: 4.0 > Upload Good
Selected Board/Port: 4.1 > Upload Good
Selected Board/Port: 4.0 > Upload Good
... another cycle or two and no issue, changed blink rate some in the process
 
There still is a leftover from the old code in intervaltimer.h:


here the corresponding PR:

 
Does 1.59-beta5 solve the issue you were seeing with attempting upload to the wrong board? This one is still on my list of issues, so wanted to specifically ask if this is solved on your machine?
@PaulStoffregen:

Not sure if I am seeing the same "attempting to upload to the wrong board" as @defragster, but here's the simple case where I am observing a similar (mis)behavior:

Conditions:
Arduino IDE 1.8.19 + TD 1.59b5

I created a "Blink" folder with the "Blink.ino" sketch in my Arduino source folder. This is important, as the two instances of the Arduino IDE have to be started from the Windows File Explorer (as opposed to using "Open With" or "Open" from the first IDE to start a second instance, where making configuration changes in one IDE also changes the configuration in the other IDE) to allow the two IDEs to be independent, in order to properly demonstrate the undesired behavior.

1) open the first instance of the Arduino IDE by navigating Windows File Explorer to the folder containing the "Blink.ino" sketch & double-clicking on the "Blink.ino" file

2) in the first instance of the Arduino IDE, select the following:
Code:
     Tools/Board:           "Teensy 4.1"
     Tools/USB Type:        "Serial"
     Tools/CPU Speed:       "600MHz"
     Tools/Optimize:        "Faster"
     Tools/Keyboard Layout: "US English"
     Tools/Port:            "COMx Serial (Teensy 4.1)"

3) connect a Teensy 4.1 via USB cable

4) in the first instance of the Arduino IDE, build/upload the "Blink.ino" sketch & verify that it is successfully uploaded to the Teensy 4.1

NOTE: the verbose build output indicates that the build occurred in the "arduino_build_765406" folder as follows:
Code:
10:14:43.028 (post_compile 14): Begin, pid=17232, version=1.59-beta5, high-res time
10:14:43.029 (loader): remote connection 1368 opened
10:14:43.030 (loader): remote cmd from 1368: "comment: Teensyduino 1.59-beta5 - WINDOWS (teensy_post_compile)"
10:14:43.031 (post_compile 14): Sending command: comment: Teensyduino 1.59-beta5 - WINDOWS (teensy_post_compile)
10:14:43.031 (loader): remote cmd from 1368: "status"
10:14:43.031 (loader): file changed
10:14:43.036 (loader): File "C:\Users\mjcul\AppData\Local\Temp\arduino_build_765406\Blink.ino.hex", 21504 bytes
10:14:43.041 (loader): File "C:\Users\mjcul\AppData\Local\Temp\arduino_build_765406\Blink.ino.ehex", 21504 bytes, and 5536 loader utility
10:14:43.042 (loader): ehex is valid, key hash: C98CD607 4C9B5153 DFC66457 FAA47DC9 1C64826D AE55EE72 206786C5 8C3B1D26
10:14:43.042 (loader): File "Blink.ino.hex". 21504 bytes, 0% used
10:14:43.053 (loader): remote cmd from 1368: "dir:C:\Users\mjcul\AppData\Local\Temp\arduino_build_765406\"
10:14:43.054 (post_compile 14): Status: 1, 0, 1, 3, 0, 0, C:\Users\mjcul\AppData\Local\Temp\arduino_build_765406\, Blink.ino.hex
10:14:43.054 (post_compile 14): Sending command: dir:C:\Users\mjcul\AppData\Local\Temp\arduino_build_765406\
10:14:43.056 (loader): remote cmd from 1368: "file:Blink.ino.hex"
10:14:43.056 (post_compile 14): Sending command: file:Blink.ino.hex
10:14:43.061 (loader): File "C:\Users\mjcul\AppData\Local\Temp\arduino_build_765406\Blink.ino.hex", 21504 bytes
10:14:43.063 (loader): File "C:\Users\mjcul\AppData\Local\Temp\arduino_build_765406\Blink.ino.ehex", 21504 bytes, and 5536 loader utility
10:14:43.064 (loader): ehex is valid, key hash: C98CD607 4C9B5153 DFC66457 FAA47DC9 1C64826D AE55EE72 206786C5 8C3B1D26
10:14:43.065 (loader): File "Blink.ino.hex". 21504 bytes, 0% used
10:14:43.077 (loader): remote cmd from 1368: "status"
10:14:43.078 (post_compile 14): Status: 1, 0, 1, 3, 0, 0, C:\Users\mjcul\AppData\Local\Temp\arduino_build_765406\, Blink.ino.hex
10:14:43.078 (post_compile 14): Disconnect
10:14:43.090 (loader): remote connection 1368 closed

5) open the second instance of the Arduino IDE by navigating Windows File Explorer to the folder containing the "Blink.ino" sketch & double-clicking on the "Blink.ino" file

6) in the second instance of the Arduino IDE, select the following:
Code:
     Tools/Board:           "Teensy 4.0"
     Tools/USB Type:        "Serial"
     Tools/CPU Speed:       "600MHz"
     Tools/Optimize:        "Faster"
     Tools/Keyboard Layout: "US English"
     Tools/Port:            "COMx Serial (Teensy 4.0)"

7) in the second instance of the IDE, build (only) the "Blink.ino" sketch

NOTE: the verbose build output indicates that the build occurred in the "arduino_build_905299" folder, but it is still referencing the "arduino_build_765406" folder in a few places
Code:
10:18:43.836 (post_compile 15): Begin, pid=20176, version=1.59-beta5, high-res time
10:18:43.838 (loader): remote connection 1368 opened
10:18:43.840 (post_compile 15): Sending command: comment: Teensyduino 1.59-beta5 - WINDOWS (teensy_post_compile)
10:18:43.840 (loader): remote cmd from 1368: "comment: Teensyduino 1.59-beta5 - WINDOWS (teensy_post_compile)"
10:18:43.841 (loader): remote cmd from 1368: "status"
10:18:43.843 (loader): remote cmd from 1368: "dir:C:\Users\mjcul\AppData\Local\Temp\arduino_build_905299\"
10:18:43.843 (post_compile 15): Status: 1, 0, 1, 3, 0, 0, C:\Users\mjcul\AppData\Local\Temp\arduino_build_765406\, Blink.ino.hex
10:18:43.843 (post_compile 15): Sending command: dir:C:\Users\mjcul\AppData\Local\Temp\arduino_build_905299\
10:18:43.845 (loader): remote cmd from 1368: "file:Blink.ino.hex"
10:18:43.845 (post_compile 15): Sending command: file:Blink.ino.hex
10:18:43.852 (loader): File "C:\Users\mjcul\AppData\Local\Temp\arduino_build_905299\Blink.ino.hex", 19456 bytes
10:18:43.858 (loader): File "C:\Users\mjcul\AppData\Local\Temp\arduino_build_905299\Blink.ino.ehex", 19456 bytes, and 5536 loader utility
10:18:43.860 (loader): ehex is valid, key hash: C98CD607 4C9B5153 DFC66457 FAA47DC9 1C64826D AE55EE72 206786C5 8C3B1D26
10:18:43.862 (loader): File "Blink.ino.hex". 19456 bytes, 0% used
10:18:43.874 (loader): remote cmd from 1368: "status"
10:18:43.877 (post_compile 15): Status: 1, 0, 1, 3, 0, 0, C:\Users\mjcul\AppData\Local\Temp\arduino_build_905299\, Blink.ino.hex
10:18:43.877 (post_compile 15): Disconnect
10:18:43.892 (loader): remote connection 1368 closed

8) with the Teensy 4.1 still connected via USB cable, press the PROGRAM button on the Teensy 4.1. The T4.1 goes into programming mode, but the download fails with the following report:

1706372771671.png


And the verbose build log shows the following (still referencing the "arduino_build_905299" folder from the second build:

Code:
10:25:51.067 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
10:25:51.068 (ports 5): remove: loc=usb:0/140000/0/2
10:25:51.068 (ports 5): usb_remove: usb:0/140000/0/2
10:25:51.068 (ports 5): nothing new, skipping HID & Ports enum
10:25:51.070 (ports 11): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
10:25:51.071 (ports 11): remove: loc=usb:0/140000/0/2
10:25:51.071 (ports 11): usb_remove: usb:0/140000/0/2
10:25:51.071 (ports 11): nothing new, skipping HID & Ports enum
10:25:51.086 (ports 11): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
10:25:51.087 (ports 11): nothing new, skipping HID & Ports enum
10:25:51.087 (ports 11): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
10:25:51.087 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
10:25:51.087 (ports 11): nothing new, skipping HID & Ports enum
10:25:51.087 (ports 5): nothing new, skipping HID & Ports enum
10:25:51.092 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
10:25:51.092 (ports 5): nothing new, skipping HID & Ports enum
10:25:51.420 (ports 11): WM_DEVICECHANGE DBT_DEVICEARRIVAL
10:25:51.420 (ports 11): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00137c19#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
10:25:51.420 (ports 11): found_usb_device, loc=usb:0/140000/0/2    Port_#0002.Hub_#0002
10:25:51.420 (ports 11): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
10:25:51.420 (ports 11): found_usb_device, devinst=00000015
10:25:51.420 (ports 11): add: loc=usb:0/140000/0/2, class=HID, vid=16C0, pid=0478, ver=0108, serial=00137c19, dev=\\?\usb#vid_16c0&pid_0478#00137c19#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
10:25:51.421 (ports 11): hiddev_from_devinst_list: iface=0
10:25:51.421 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
10:25:51.421 (ports 11): found_usb_device complete
10:25:51.422 (ports 11): hid, found devinst=00000016
10:25:51.422 (ports 11): hid, path=\\?\hid#vid_16c0&pid_0478#6&1be26cd0&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
10:25:51.422 (ports 11): hid,  opened handle
10:25:51.422 (ports 11):  devinst=00000016, location=usb:0/140000/0/2
10:25:51.422 (ports 11):  vid=16C0, pid=0478, ver=0108, usepage=FF9C, use=0025
10:25:51.422 (ports 11):  devpath=\\?\hid#vid_16c0&pid_0478#6&1be26cd0&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
10:25:51.422 (ports 11): usb_add: usb:0/140000/0/2  hid#vid_16c0&pid_0478 (Teensy 4.1) Bootloader
10:25:51.422 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0478#00137c19#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
10:25:51.422 (ports 5): found_usb_device, loc=usb:0/140000/0/2    Port_#0002.Hub_#0002
10:25:51.422 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0478&REV_0108
10:25:51.422 (ports 5): found_usb_device, devinst=00000017
10:25:51.422 (ports 5): add: loc=usb:0/140000/0/2, class=HID, vid=16C0, pid=0478, ver=0108, serial=00137c19, dev=\\?\usb#vid_16c0&pid_0478#00137c19#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
10:25:51.422 (ports 5): hiddev_from_devinst_list: iface=0
10:25:51.422 (ports 5): found_usb_device complete
10:25:51.423 (ports 5): hid, found devinst=00000018
10:25:51.423 (ports 5): hid, path=\\?\hid#vid_16c0&pid_0478#6&1be26cd0&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
10:25:51.423 (ports 5): hid,  opened handle
10:25:51.423 (ports 5):  devinst=00000018, location=usb:0/140000/0/2
10:25:51.423 (ports 5):  vid=16C0, pid=0478, ver=0108, usepage=FF9C, use=0025
10:25:51.423 (ports 5):  devpath=\\?\hid#vid_16c0&pid_0478#6&1be26cd0&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
10:25:51.423 (ports 5): usb_add: usb:0/140000/0/2  hid#vid_16c0&pid_0478 (Teensy 4.1) Bootloader
10:25:51.475 (ports 11): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
10:25:51.476 (ports 11): nothing new, skipping HID & Ports enum
10:25:51.480 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
10:25:51.481 (ports 5): nothing new, skipping HID & Ports enum
10:25:51.493 (loader): secure mode can not be locked: this is Standard Teensy
10:25:51.505 (loader): encryption is possible on this Teensy, but not yet configured
10:25:51.505 (loader): but without secure mode locked, encryption will NOT be secure!
10:25:51.513 (loader): Device came online, code_size = 8126464
10:25:51.523 (loader): Board is: Teensy 4.1 (IMXRT1062), version 1.08
10:25:51.533 (loader): File "C:\Users\mjcul\AppData\Local\Temp\arduino_build_905299\Blink.ino.hex", 19456 bytes
10:25:51.543 (loader): File "C:\Users\mjcul\AppData\Local\Temp\arduino_build_905299\Blink.ino.ehex", 19456 bytes, and 5536 loader utility
10:25:51.543 (loader): ehex is valid, key hash: C98CD607 4C9B5153 DFC66457 FAA47DC9 1C64826D AE55EE72 206786C5 8C3B1D26
10:25:51.553 (loader): File "Blink.ino.hex". 19456 bytes, 0% used
10:25:51.584 (loader): set background IMG_ONLINE
10:25:51.593 (loader): File "C:\Users\mjcul\AppData\Local\Temp\arduino_build_905299\Blink.ino.hex", 19456 bytes
10:25:51.603 (loader): File "C:\Users\mjcul\AppData\Local\Temp\arduino_build_905299\Blink.ino.ehex", 19456 bytes, and 5536 loader utility
10:25:51.603 (loader): ehex is valid, key hash: C98CD607 4C9B5153 DFC66457 FAA47DC9 1C64826D AE55EE72 206786C5 8C3B1D26
10:25:51.617 (loader): File "Blink.ino.hex". 19456 bytes, 0% used
10:25:51.628 (loader): begin elf_guess_size
10:25:51.633 (loader): found elf file
10:25:51.643 (loader): read elf files into memory, 472312 bytes
10:25:51.649 (loader): elf appears to be for Teensy 4.0 (IMXRT1062) (2031616 bytes)
10:25:51.653 (loader): elf binary data matches hex file
10:25:51.665 (loader): elf file is for Teensy 4.0 (IMXRT1062) (id=24)
10:25:51.673 (loader): Incompatible file, showing warning dialog
10:25:51.744 (loader): HID/win32: HidD_GetPreparsedData ok, device still online :-)

Again, not sure if this is the same condition that you are investigating, but it is the one that I often encounter.

This sequence of events describes the steps I use when building for my TeensyMIDIPolySynth, which includes a T4.1 managing all of the MIDI interfaces, as well as an RA8875 TFT touchscreen display, and a T4.0 performing all of the audio functions with the Teensy Audio Adapter connected. The two Teensys communicate over a shared serial interface running at 500Kbaud. I move my one cable between the two Teensys for programming each. However, in this example sequence, the cable remains connected to the T4.1 as described. Would it be beneficial for me to detail a sequence where both are connected via two USB cables & switching between programming the two, without connecting/dicsonnecting any cables ??

Thanks,

Mark J Culross
KD5RXT
 
Last edited:
@kd5rxt-mark - that is different than the process here - but seems to have the same end?

Have run multiple IDE #1 instances in the past - but not recently.
Often however the IDE #1 and #2 may be open at the same time - and that may have been the case initially ... was 6 months ago ...

Possible when 'recent' repro's happened both IDE #1 and #2 were open and not caught as the problem source. @mjs513 got a repro easily enough and possible he had them both open as well?
 
Just tested this with a teensy 4.1 and a Teensy Micromod - was able to upload blink to both boards no issues.

@kd5rxt-mark - did you remember to change both the board and port in the IDE the first time I did it I forgot to change the change the board and had the issue you showed?
 
Just tested this with a teensy 4.1 and a Teensy Micromod - was able to upload blink to both boards no issues.

@kd5rxt-mark - did you remember to change both the board and port in the IDE the first time I did it I forgot to change the change the board and had the issue you showed?
@mjs513:

Fair question. Since I only had one T4.1 connected to IDE instance #1, there was only one COM port active, and each IDE showed its respective T4.x selected for the board type.

Mark J Culross
KD5RXT
 
Last edited:
Windows 10, Arduino IDE 2.2.1. Sketch EchoBoth, HWSERIAL replaced with Serial1 and using DualSerial USB mode.

I tried 0.59.5 and still the same issue since 1.58.0: I have intermittent connections (shorter) and disconnections (longer).

Cannot see my dual serial ports on any terminal.

Firmware was already uploaded to T4.1 (after a long "reset" to default firmware so I can retrieve the ability to upload) and running when red message on Output is got by pushing the [Compile and upload] button.

EDIT: I also tried Blink. Once uploaded to T4.1(after a long "reset" to default firmware again) and running, I can see blinking but same issue as above. Set to RAW HID mode this time.

Now if I make blinking delay to 100ms instead of 1000ms, it blinks thrice then the led is OFF for almost the same delay than blinking then again it blinks thrice and so on. Definitely not normal. And still the same issue so far.
 

Attachments

  • EchoBothOnDualSerial-OFF.png
    EchoBothOnDualSerial-OFF.png
    1.1 MB · Views: 12
  • EchoBothOnDualSerial-ON.png
    EchoBothOnDualSerial-ON.png
    1.1 MB · Views: 12
Last edited:
So getting back to 0.59.5, after uninstalling 1.57.2 and firing Teensy uploader, I reinstall 0.59.5 and recompile EchoBoth. Upload the firmware in Dual Serial mode and... have a stable connection to teensy port and still access to COM8 and COM9. G*d! It really wears me out !!!!
 
I see on another thread that replacing Serial1 with SerialUSB1 solved the problem. Is this problem fully resolved?

If there is something I should investigate, can you give me clear instructions to reproduce the problem and the code you're using? Please copy the actual code, not a graphics screenshot, so I'm able to copy your from this forum into Arduino IDE and follow your instructions to reproduce the problem. Please also understand I mostly use Linux, so if I must use Windows to reproduce this problem, please be detailed and specific because I'm not as familiar with Windows. I need clear and detailed instructions to reproduce the problem if it involves Windows.
 
I had been blocked upon 1.58.0 or later for over one year. So I was stuck on 1.57.2. Whenever I tried to install 1.58.0 or later, I get the same issue as above with no access to serial port(s) or to teensy port to upload next build and so no idea how the program ran. I'm really clueless about how I've now managed to install 0.59.5 this time, whereas I failed the previous time. Now the last process I did was :
- remove the one installed (1.57.2).
- kill the Teensy uploader as the process of safe installation may fail due to a locked script.
- then install the wanted one (0.59.5).

The program is basically the same as in here. Teensy 4.1, Faster, 600MHz, Dual Serial.

There was a time I could install 1.58.0 or later on my machines but then I couldn't.

Let us say the situation is solved concerning 0.59.5 and the issue may be due to improper way to uninstall/install steps.
 
Confirm, on Windows we have a known issue with Arduino IDE not being able to delete the files if Teensy Loader is still running. Sadly, the IDE doesn't check whether it really was able to delete the old files, and when a new install is done there is no checking whether old files will mess it up.

Arduino IDE 2.2.2 (still in testing) will add the ability to an uninstall script to run. 1.59 beta already has this script and it's been tested with the latest 2.2.2 nightly builds. Eventually when Arduino releases IDE 2.2.2 and 1.59 is released, this Windows uninstall (or switch versions which uninstalls the current version) will be fixed. It's an insidious and frustrating problem which hopefully will soon be forever solved (as people migrate to new IDE versions).

Plan is to add the uninstall script to all the old versions, so 1.57.2 will become 1.57.3 with exactly the same code but the uninstall script added.
 
Back
Top