It was the hex file itself, not a 4.0/4.1 incompatibility? Interesting.
The soft reboot code is only implemented in the Linux portion of the code. There's just a stub for OSX and Windows.
I can duplicate the problem on Raspbian if I load "blink_slow_Teensy40.hex" into a Teensy4.1 and then try and load it again.
me@raspberrypi:~/Documents/src/teensy_loader_cli $ ./teensy_loader_cli --mcu=TEENSY41...
The broken pipe error was caused by a too short "SET_LINE_REQUEST_TYPE" message. The system was expecting 7 bytes (4 bytes for speed, 1 for stop bit, 1 for data bits, and another for parity) but the loader was only...
Out of curiosity I soldered a crystal and end header to my T3.2, hooked up a 3V coin cell and loaded the stripped down and modified version of the TimeTeensy3 sketch shown below. I removed all the time sync stuff (which...
I made a fork of SdFat-beta last year and added in makeSystem(), makeHidden(), makeReadOnly() and makeArchive() methods, as well as code in the sync() method (which is called when the file is closed) to set any changed...
No, actually you didn't.
I didn't say to change and run the program.
I'm saying: if you set those variables to those values, what output would you expect to see from the program? Write that down and show us.
I'm going to approach this from a slightly different direction.
If you set:
Int long Days = 0;
Int long Hours = 0;
Int long Min = 0;
Int long Sec_add = 3;
What exactly would you expect to see...
Sec is an unsigned long, so it will never be less than zero. When you set all your Days, Hours, Min, Sec_add variables to zero, Sec will start at zero, but when you decrement it, it will be a really big positive number....
If we're talking about the Teensy 4.x, from experience, you can get away with just doing another SerialX.begin(new_baud_rate).
Unless you're also using hardware handshaking (RTS/CTS), in which case you need to...