Forum Rule: Always post complete source code & details to reproduce any issue!
Page 1 of 3 1 2 3 LastLast
Results 1 to 25 of 63

Thread: Teensy 4.1 Lockup

  1. #1
    Senior Member brtaylor's Avatar
    Join Date
    Mar 2016
    Location
    Portland, OR
    Posts
    708

    Teensy 4.1 Lockup

    EDIT: Sorry, wrong category, I thought this was in bug reports...please move.

    I'm encountering a weird issue with a Teensy 4.1 locking up.

    The following is the code that I am using:

    Code:
    void setup() {
      Serial.begin(115200);
      while (!Serial) {}
    }
    
    void loop() {
      Serial.print( tempmonGetTemp() );
      Serial.print("C");
      Serial.print("\t");
      Serial.println(millis());
      
      delay(10);
    }
    Here is a screenshot of my Arduino Serial Monitor after the Teensy had locked up:
    Click image for larger version. 

Name:	Capture.jpg 
Views:	36 
Size:	51.4 KB 
ID:	25855

    Teensyduino version 1.54, Arduino version 1.8.15. CPU Speed 528 MHz.

    I had been running more complicated code and experiencing lockups, which led to this much more simplified example. I also have some sensors attached to the board - I'm going to try repeating this a few times with a new Teensy 4.1 that I have, without any sensors connected, to rule out hardware issues. Will report back later this evening or early tomorrow on those results.
    Last edited by brtaylor; 09-15-2021 at 10:10 PM.

  2. #2
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    @brtaylor - moved thread to 'bug reports'.
    Can you confirm if you see this with TD 1.55?

    Will be installed that soon here on IDE 1.8.16 and try on a t_4.1 and post results.

  3. #3
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Quote Originally Posted by brtaylor View Post
    EDIT: Sorry, wrong category, I thought this was in bug reports...please move.

    I'm encountering a weird issue with a Teensy 4.1 locking up.

    The following is the code that I am using:

    ...

    Teensyduino version 1.54, Arduino version 1.8.15. CPU Speed 528 MHz.

    I had been running more complicated code and experiencing lockups, which led to this much more simplified example. I also have some sensors attached to the board - I'm going to try repeating this a few times with a new Teensy 4.1 that I have, without any sensors connected, to rule out hardware issues. Will report back later this evening or early tomorrow on those results.
    Running that code at 528 MHz on a bare T_4.1 - Pinned with a heat sink - has 8 MB PSRAM and 16 MB Flash on QSPI, SD empty

    Running Windows 11 and IDE 1.8.16 and just installed TD 1.55 :: Using IDE SerMon

    Not seeing any signs of trouble here?

    Code:
    37.43C	790
    37.43C	800
    37.43C	810
    ...
    40.70C	220785
    40.70C	220795
    ...
    41.36C	291080
    40.70C	291090
    ...

  4. #4
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    From post on TD 1.55 release thread - it was working then stopped ...

    Code:
    41.36C	593242
    40.70C	593252
    41.36C	593262
    41.36C	593272
    Closed IDE SerMon and turned on TyCommander Serial to that T_4.1 and it was running:
    Code:
    40.70C	1247819
    40.70C	1247829
    40.05C	1247839
    40.05C	1247849
    ...
    40.05C	1316653
    40.05C	1316663
    40.05C	1316673
    ...
    Turning off TyComm Serial and re-openeing T_SerMon in IDE ... it picked up running ...

  5. #5
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    25,026
    I'm running it here, using the just-released Teensyduino 1.55 on MacOS 11.6. So far hasn't crashed, but only been running about 5 minutes.

  6. #6
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Quote Originally Posted by PaulStoffregen View Post
    I'm running it here, using the just-released Teensyduino 1.55 on MacOS 11.6. So far hasn't crashed, but only been running about 5 minutes.
    Cross post? Did STALL here on Windows ... not locked up just needed to close and restart SerMon? I did cycle TyComm in - but T_SerMon still running

    Code:
    40.05C	1339088
    40.05C	1339098
    40.05C	1339108
    ...
    39.39C	1741572
    39.39C	1741582
    39.39C	1741592
    ...
    After the above is STALLED again:
    Code:
    ...
    38.74C	1961318
    38.74C	1961328
    38.74C	1961338
    38.74C	1961348
    38.74C	1961358
    Close SerMon and then then Re-Open --- picks up runing:
    Code:
    38.74C	1968199
    39.39C	1968209
    38.74C	1968219
    38.74C	1968229
    40.70C	2908345
    ...
    Last edited by defragster; 09-16-2021 at 12:00 AM. Reason: stalled again

  7. #7
    Senior Member brtaylor's Avatar
    Join Date
    Mar 2016
    Location
    Portland, OR
    Posts
    708
    Ditto, stalling on Windows with the bare Teensy 4.1, but no hard crashes.

    With the other Teensy 4.1 (which has sensors and is in an enclosure running about 10C hotter / around 62C typical), I'm incrementally unplugging stuff to see if I can isolate the issue. Right now it seems like a hardware bug unique to my setup. Will report back if I can find anything useful / conclusive.

  8. #8
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Quote Originally Posted by brtaylor View Post
    Ditto, stalling on Windows with the bare Teensy 4.1, but no hard crashes.

    With the other Teensy 4.1 (which has sensors and is in an enclosure running about 10C hotter / around 62C typical), I'm incrementally unplugging stuff to see if I can isolate the issue. Right now it seems like a hardware bug unique to my setup. Will report back if I can find anything useful / conclusive.
    So the other T_4.1 with misc stuff connected doesn't just Stall - but it is 'hanging/locking' in some fashion?

    Have you added the if ( Serial && CrashReport ) Serial.print( CrashReport ); code to see if it exposes anything?
    Last edited by defragster; 09-16-2021 at 04:12 AM.

  9. #9
    Senior Member brtaylor's Avatar
    Join Date
    Mar 2016
    Location
    Portland, OR
    Posts
    708
    Quote Originally Posted by defragster View Post
    So the other T_4.1 with misc stugg connected doesn't just Stall - but it is 'hanging/locking' in some fashion?

    Have you added the if ( Serial && CrashReport ) Serial.print( CrashReport ); code to see if it exposes anything?
    Yes, it's a hard freeze and the Teensy is unresponsive. COM port is greyed out and a power cycle is required. Good idea about the crash report, thanks! So far just adding back in chunks of code and hardware to see if I can isolate the cause.

  10. #10
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    If it were a controlled Crash - it would restart after 8 second pause, but there are some that don't handle that well ... and this may not be hitting any of them.

    Have you worked with TyComm? In this case the SerMon here is losing it now some time later TyCommander is still getting the bare T_4.1 temp ... continues after SerMon stalled again:
    Code:
    ...
    39.39C	1339068
    40.05C	1339078
    40.70C	10070500
    40.70C	10070510
    41.36C	10070520
    41.36C	10070530
    ...
    42.01C	18190687
    42.01C	18190697
    42.01C	18190707
    ...
    42.01C	21258419
    42.01C	21258429
    ...
    42.66C	24138645
    42.66C	24138655
    ...                                    // TyCommander still running uninterrupted
    42.66C	30104580
    42.01C	30104590
    42.66C	30104600
    ...
    Last edited by defragster; 09-16-2021 at 07:33 AM. Reason: TyComm running on ...

  11. #11
    Senior Member+ mjs513's Avatar
    Join Date
    Jul 2014
    Location
    New York
    Posts
    7,546
    As @defragster mentioned that depending on the crash crashreport will give you a means to find where the error is but if you are loosing the Serial Port and the T4.1 doesn't restart then it won't help much.

    I just ran the same thing on the Locked T4 and it froze the serial monitor as well.
    Code:
    49.21C	664169
    49.21C	664179
    48.55C	664189
    48.55C	664199
    49.21C	664209
    49.21C	664219
    49.21C	664229
    49.21C	664239
    49.21C	664249
    Opening and closing the Serial monitor, the data continued - as @defragster mentioned TyCommander Serial Monitor works nicely to avoid the issue but not sure whats causing the issue.

    @Paul a similar issue was noted in other releases as well where dumping alot of data to the serial monitor would cause it to freeze and opening and closing the serial monitor cleared the problem. Not sure this was ever resolved. Unfortunately I can not find where I posted that issue - alot of beta releases

    EDIT: Found it: https://forum.pjrc.com/threads/66357...l=1#post271493 and @defragster confirmed it in following posts

  12. #12
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Follow up to prior extended run - TyCommander as SerMon running without Pause or need to restart over night continued from the following - so seems there is something in the SerMon here:
    Code:
    ...
    40.70C	59868787
    40.70C	59868797
    40.70C	59868807
    Good find on the prior post @mjs513 : I'll find my prior test against .availableForWrite() and see if it triggers to keep tSerMon running - not sure if it was this: forum.pjrc.com/threads/66357-Teensyduino-1-54-Beta-7

    ...

    Quote Originally Posted by defragster View Post
    If it were a controlled Crash - it would restart after 8 second pause, but there are some that don't handle that well ... and this may not be hitting any of them.

    Have you worked with TyComm? In this case the SerMon here is losing it now some time later TyCommander is still getting the bare T_4.1 temp ... continues after SerMon stalled again:
    Code:
    ...
    39.39C	1339068
    40.05C	1339078
    40.70C	10070500
    40.70C	10070510
    41.36C	10070520
    41.36C	10070530
    ...
    42.01C	18190687
    42.01C	18190697
    42.01C	18190707
    ...
    42.01C	21258419
    42.01C	21258429
    ...
    42.66C	24138645
    42.66C	24138655
    ...                                    // TyCommander still running uninterrupted
    42.66C	30104580
    42.01C	30104590
    42.66C	30104600
    ...

  13. #13
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Stopped prior code to TyComm for new code:
    Code:
    ...
    40.70C	62101921
    40.70C	62101931
    41.36C	62101941
    For TD_155 beta Code4Code it was generating the 4,000 Func()'s to dual USB too fast - so delayMicroseconds() were embedded to allow SerMon to capture the 3MB of generated code without loss.

    New Sketch running to tSerMon - will show if it can see "if ( Serial.availableForWrite() > 40 ) {" getting too small. When I first posted to this it seemed the delay(10) would be enough to keep USB Serial running and not related to this??? It is only sending 100 short messages "40.70C 62101931" per second?

    Well it Stalled tSerMon again:
    Code:
    40.70C	668151
    40.70C	668161
    40.70C	668171
    No signs this code triggered - it needs a BLINK in the loop to show if 'halted' or not ...:
    Code:
    // https://forum.pjrc.com/threads/68199-Teensy-4-1-Lockup?p=288611&viewfull=1#post288611
    void setup() {
      Serial.begin(115200);
      Serial.println("\n" __FILE__ " " __DATE__ " " __TIME__);
      while (!Serial) {}
    }
    
    uint32_t writeSkip = 0;
    uint32_t skipLog = 0;
    void loop() {
      if ( Serial.availableForWrite() > 40 ) {
        if ( writeSkip > 0) {
          Serial.print("\t\tskW:");
          Serial.println(writeSkip);
          writeSkip = 0;
          skipLog++;
        }
        Serial.print( tempmonGetTemp() );
        Serial.print("C");
        Serial.print("\t");
        Serial.println(millis());
        if ( skipLog ) {
        Serial.print("\t");
          Serial.print(skipLog);
        }
      }
      else
        writeSkip++;
    
      delay(10);
    }

  14. #14
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Added digitalToggle - tSerMon stalled but the LED was still on DIM ... i.e. Toggling.
    Closed tSerMon and re-opened it and it started with this:

    Code:
    40.05C	675500
    40.05C	675510
    40.05C	675520
    		skW:77026
    39.39C	1445790
    	140.05C	1445800
    	140.05C	1445810
    	140.05C	1445820
    	140.05C	1445830
    	140.05C	1445840
    	140.05C	1445850
    	140.05C	1445860
    It had previously stopped with this before closing - Note the numbers don't show logical sequence? Normally on restart tSermon starts 'EMPTY'??:
    Code:
    39.39C	668238
    39.39C	668248
    40.05C	668258
    It probably did that output before - except I closed tSerMon and immediately uploaded the new code ... edited now in p#13

  15. #15
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    And again {code in p#13}: ended with:
    Code:
    ...
    	140.70C	1997799
    	140.05C	1997809
    Close and open tSerMon:
    Code:
    40.70C	2003971
    	140.70C	2003981
    	140.05C	2003991
    	1		skW:26572
    40.05C	2269721
    	240.05C	2269731
    	240.05C	2269741
    ...
    OPPS: output above has value of "skipLog" appened to start of the line before the TEMP after the TAB. Was trying to minimize output so as to not alter the failure case.
    > It shows '1'TEMP and '2'TEMP in the output above.
    So it is counting each restart of tSerMon - When it can start printing again.

    The value of "writeSkip" is incrementing in the ELSE to :: if ( Serial.availableForWrite() > 40 )

    SO? : it seems the USB buffers may not be emptying as expected to Host tSermon?

  16. #16
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Continuing - Behavior repeats:
    Code:
    	241.36C	2821720
    	241.36C	2821730
    	2         // This char was ON THE SerMon but not copied 
    Close tSerMon and Restart - with increment to '3'TEMP - but first lines are those from PRIOR:
    Code:
    41.36C	2827892
    	241.36C	2827902
    	241.36C	2827912
    	2		skW:345938
    40.70C	6287302
    	340.70C	6287312
    	340.70C	6287322
    	340.70C	6287332
    ...
    Altered BOLD part of the code and now the LED is showing the delay(10) PULSE.
    But the other two added lines are not helping Just added an extra set - RED. Restarted after upload and accidentally hit ENTER/Send in SerMon right away - which would be ignored until .available() is <40. It quickly triggered:
    Code:
    40.70C	45882
    40.70C	45892
    		skW:1
    40.70C	45972
    1	40.70C	45982
    1	40.70C	45992
    1	40.70C	46002
    I have hit 'Send' again and still running. without triggering the '1' (now left of TAB) to go to '2'.

    WELL : it just Stalled again? The .read() did not help adjusting the USB buffers available by freeing one when the char was read.
    Doing tSerMon close and restart begins:
    Code:
    41.36C	604422
    1	40.70C	604432
    1	41.36C	604442
    1			skW:3160
    41.36C	667852
    2	41.36C	667862
    2	41.36C	667872
    ...
    After that tSerMon restart it ran for some time and stopped as:
    Code:
    2	41.36C	1214249
    2	41.36C	1214259
    2			skW:1
    41.36C	1214289
    3	41.36C	1214299
    3	41.36C	1214309
    ...
    3	41.36C	1237337
    3	41.36C	1237347
    3	40.70C	1237357
    3
    and again:
    Code:
    ...
    41.36C	1243519
    3	41.36C	1243529
    3	41.36C	1243539
    3			skW:33739
    41.36C	1918429
    4	40.70C	1918439
    4	40.70C	1918449
    ...
    So something is going on with the Host/tSerMon side and have not found a 'sketch' way to avoid or correct::
    Code:
    // https://forum.pjrc.com/threads/68199-Teensy-4-1-Lockup?p=288611&viewfull=1#post288611
    void setup() {
      Serial.begin(115200);
      Serial.println("\n" __FILE__ " " __DATE__ " " __TIME__);
      while (!Serial) {}
      pinMode( 13, OUTPUT );
    }
    
    uint32_t writeSkip = 0;
    uint32_t skipLog = 0;
    void loop() {
      if ( Serial.availableForWrite() > 40 ) {
        if ( writeSkip > 0) {
          Serial.print("\t\tskW:");
          Serial.println(writeSkip);
          writeSkip = 0;
          skipLog++;
        }
        Serial.print( tempmonGetTemp() );
        Serial.print("C");
        Serial.print("\t");
        Serial.println(millis());
        if ( skipLog ) {
          Serial.print(skipLog);
          Serial.print("\t");
        }
      }
      else {
        writeSkip++;
        if ( Serial.available() ) {
          Serial.read();
          delay(50);
        }
        Serial.flush();
        delay(10);
      }
    
      delay(10);
      digitalToggleFast( 13 ) ;
    }
    For Reference just put same code on a second T_4.1 (no pins or heat sink, and twin PSRAM's) and it is running with TyCommander as SerMon - expect it will run fine forever with NO similar behavioral issues ... Time will tell ... As of now it shows:
    Code:
    C:\T_Drive\tCode\Serial\SerialTestBT\SerialTestBT.ino Sep 16 2021 12:21:24
    34.33C	1235
    ...
    45.67C	309792
    45.67C	309802
    		skW:1
    45.67C	309832
    1	45.00C	309842
    1	45.67C	309852
    ...
    1	46.33C	814962
    1	46.33C	814972
    ...
    1	47.67C	7234586  // Still running - no more skW==writeSkip or associated : skipLog++
    1	47.67C	7234596
    1	47.67C	7234606
    1	47.00C	7234616
    ...
    >> That "skW:1" does show it dropped TWO prints of 10ms - one because of the delay(10);

    <EDIT>: Since tSerMon was repeatedly failing the same way even with restarting ... and TyComm shows no propensity to Stall I did a quick EDIT to see if it changes anything::

    >> Duplicated the core code and Variables going to Serial and Compiled 528 MHz with Dual Serial with all prints and tests referring to : SerialUSB1. and writeSkip2 and skipLog2
    -> just about to point of prior failures - but nothing but normal prints so far ... at 500 Seconds
    Last edited by defragster; 09-16-2021 at 10:05 PM.

  17. #17
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Okay updated Dual Serial code below - Results the Serial to tSerMon Stalled - while the SerialUSB1. to TyComm is still running:
    TyCommander::
    Code:
    ...
    42.01C	672989
    42.01C	672999
    42.01C	673009
    42.01C	673019  // NO Break here - even with delay(10) in Serial loop() portion - so it didn't trigger?
    42.01C	673029
    42.01C	673039
    42.66C	673049
    ...
    42.01C	3808181
    42.01C	3808201
    42.01C	3808221
    ...
    tSerMon:
    Code:
    C:\T_Drive\tCode\Serial\SerialTestBT\SerialTestBT.ino Sep 16 2021 14:56:27
    41.36C	11866
    ...
    42.01C	673009
    42.01C	673019
    42.01C	673029
    Not sure what it shows/Adds except the T_4.1 is Running and Dual repeats results seen before from two T_4.1's - and the PC Host may be causing it - but if so TyCom recovers where tSerMon does not:
    Code:
    // https://forum.pjrc.com/threads/68199-Teensy-4-1-Lockup?p=288611&viewfull=1#post288611
    void setup() {
      Serial.begin(115200);
      Serial.println("\n" __FILE__ " " __DATE__ " " __TIME__);
      while (!Serial) {}
      pinMode( 13, OUTPUT );
    }
    
    uint32_t writeSkip = 0;
    uint32_t skipLog = 0;
    uint32_t writeSkip2 = 0;
    uint32_t skipLog2 = 0;
    void loop() {
      if ( Serial.availableForWrite() > 40 ) {
        if ( writeSkip > 0) {
          Serial.print("\t\tskW:");
          Serial.println(writeSkip);
          writeSkip = 0;
          skipLog++;
        }
        Serial.print( tempmonGetTemp() );
        Serial.print("C");
        Serial.print("\t");
        Serial.println(millis());
        if ( skipLog ) {
          Serial.print(skipLog);
          Serial.print("\t");
        }
      }
      else {
        writeSkip++;
        if ( Serial.available() ) {
          Serial.read();
          delay(50);
        }
        Serial.flush();
        delay(10);
      }
    
      if ( SerialUSB1.availableForWrite() > 40 ) {
        if ( writeSkip2 > 0) {
          SerialUSB1.print("\t\tskW:");
          SerialUSB1.println(writeSkip2);
          writeSkip2 = 0;
          skipLog2++;
        }
        SerialUSB1.print( tempmonGetTemp() );
        SerialUSB1.print("C");
        SerialUSB1.print("\t");
        SerialUSB1.println(millis());
        if ( skipLog2 ) {
          SerialUSB1.print(skipLog2);
          SerialUSB1.print("\t");
        }
      }
      else {
        writeSkip2++;
        if ( SerialUSB1.available() ) {
          SerialUSB1.read();
          delay(50);
        }
        SerialUSB1.flush();
        delay(10);
      }
    
      delay(10);
      digitalToggleFast( 13 ) ;
    }

  18. #18
    Senior Member+ mjs513's Avatar
    Join Date
    Jul 2014
    Location
    New York
    Posts
    7,546
    @defragster

    If I remember right the issue boils down to the SerMon implementation that is part of the current Arduino IDE 1.8.xxxx. Just as a hunch I downloaded IDE 2.0 just to test the Serial Monitor which is a different implementation than the current version:
    Code:
    57.06C	973865
    57.06C	973875
    57.06C	973885
    57.06C	973895
    57.06C	973905
    57.06C	973915
    57.06C	973925
    and its still running. Going to let it keep going.

  19. #19
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Quote Originally Posted by mjs513 View Post
    @defragster

    If I remember right the issue boils down to the SerMon implementation that is part of the current Arduino IDE 1.8.xxxx. Just as a hunch I downloaded IDE 2.0 just to test the Serial Monitor which is a different implementation than the current version:
    Code:
    57.06C	973865
    57.06C	973875
    57.06C	973885
    57.06C	973895
    57.06C	973905
    57.06C	973915
    57.06C	973925
    and its still running. Going to let it keep going.
    Interesting if the IDE 2.0 version works that well.

    This is running the PJRC Teensy Ports version of SerMon - which generally uses Paul's better code.

    Which gives me the idea to start it up using the IDE 1.8.16 native SerMon - at 100 short messages per second this can't be too overwhelming?

    Just closed Com18 tSermon and opened it on the IDE "Serial Ports" Com18 - will see if it stops. It started like this:
    Code:
    42.01C	680273
    42.01C	680283
    42.01C	680293
    		skW:607595
    42.01C	12834720
    1	42.01C	12834730
    1	42.01C	12834740
    1	42.01C	12834750
    And TyCommander still running like this on DUAL Serial Com17:
    Code:
     ...
    42.66C	12937170
    42.66C	12937180
    42.66C	12937190
    42.66C	12937200
    42.66C	12937210
    ...

  20. #20
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    IDE Sermon running fine long time:
    Click image for larger version. 

Name:	IDESerMonRVt.png 
Views:	15 
Size:	61.0 KB 
ID:	25875
    Code:
    ...
    1	42.66C	18175229
    1	42.01C	18175239
    1	42.66C	18175249
    1	42.66C	18175259
    1	42.01C	18175269
    ...
    Need to restart computer ...

    Computer restarted - put Dual SerMon code on two T_4.1's : IDE Sermon and TyComm long run good::
    Click image for larger version. 

Name:	SerMonTwoDual.jpg 
Views:	16 
Size:	149.9 KB 
ID:	25876

    @Paul - problem seems unique to t_sermon ?

    One Teensy did stutter "1" on each early as before - but the other did not and neither stalled.

    The upper right IDE SerMon has now indexed to a second "2" event - but still running. The same T_4.1 on TyComm is still only at "1"
    The second T_4.1 on the left shows no events at all on either USB port. Will let it run overnight ...
    Code:
    47.67C	8030041
    1	47.67C	8030051
    1	47.67C	8030061
    1	47.67C	8030071
    1	47.67C	8030081
    1	47.67C	8030091
    1	48.33C	8030101
    1			skW:1
    47.67C	8030132
    2	47.67C	8030142
    2	47.67C	8030152
    2	47.67C	8030162
    ...
    2	47.67C	9021690
    2	47.67C	9021700
    2	47.67C	9021710
    2	47.67C	9021720
    2	47.67C	9021730
    2	47.67C	9021740
    ...
    Plugged in and uploaded to a third T_4.1 - using CMDline teensy_seialmon.exe and it stalled here - and can't print :
    Code:
    1       46.64┬░C        1248394
    1       46.64┬░C        1248414
    1       46.64┬░C        1248434
    1       46.64┬░C        1248454
    1       46.64┬░C        1248474
    1       46.64┬░C        1248494
    Restarting it gave:
    Code:
    C:\T_Drive\Arduino_1.8.16_155\hardware\tools>teensy_serialmon.exe usb:0/140000/0/6/2
    Opened COM30 Dual Serial
    46.64┬░C        1260816
    1       46.64┬░C        1260836
    1       46.64┬░C        1260856
    1                       skW:19345
    47.91┬░C        1841227
    2       47.91┬░C        1841247
    2       47.91┬░C        1841267
    2       48.55┬░C        1841287
    ...
    As of now upper left showing "1" event not none, upper right "3" - both IDE SerMon - still running
    Lower left TyComm still no events and lower right still only the "1"
    Code:
    ...
    1	47.67C	12992988
    1	47.67C	12992998
    ...
    Last edited by defragster; 09-17-2021 at 07:30 AM.

  21. #21
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Final update until something else shows ...

    Ran overnight and IDE SerMon continues without a stall or stop, like TyCommander as Sermon with posted sketch running DUAL USB.
    > Host machine was put to 'sleep' - both T_4.1's were blinking on 'wake' then stopped blinking and resumed normal operation.

    Seems ::Problem is something unique to t_SerMon, not a problem with Teensy, or Host Windows computer in general.

    Code:
     ...
    1	41.36C	45200932
    1	41.36C	45200942
    1	41.36C	45200952
    1	41.36C	45200962
    1	42.01C	45200972
    ...
    And update on the FOUR SerMon screen shot - there were some added minor hits to finding "availableForWrite() > 40", but those output shortages did not result in any stalling.
    Click image for larger version. 

Name:	SerMonTwoDual2.jpg 
Views:	11 
Size:	150.4 KB 
ID:	25884

    Then :: Closed the two instances of IDE SerMon.

    Return to t_SerMon on left: STALLED in 46085286 - 45505100 ms
    Code:
    42.01C	45505090
    3	41.36C	45505100
    3	42.01C	45505110
    3			skW:2774
    42.01C	45560611
    4	41.36C	45560621
    4	41.36C	45560631
    ...
    4	41.36C	46085266
    4	42.01C	46085276
    4	42.01C	46085286
    4
    Return to t_SerMon on the right: STALLED in 46041126 - 45499535 ms
    Code:
    47.00C	45499535
    5	47.00C	45499545
    5	47.00C	45499555
    5			skW:842
    47.00C	45516408
    6	47.00C	45516418
    6	47.00C	45516428
    6	47.00C	45516438
    ...
    6	47.00C	46041106
    6	47.00C	46041116
    6	47.00C	46041126
    6

  22. #22
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    25,026
    It's been running continuously here for over 46 hours with MacOS.

    Click image for larger version. 

Name:	Screen.jpg 
Views:	13 
Size:	68.0 KB 
ID:	25885

  23. #23
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Quote Originally Posted by PaulStoffregen View Post
    It's been running continuously here for over 46 hours with MacOS.
    Yay for MAC!

    Just opened old ZIP IDE 1.8.15 w/TD 1.54 - Similar tSerMon Stall at:
    Code:
    ...
    40.70C	680017
    40.70C	680027
    40.70C	680037
    Put IDE 1.8.16 and TD 1.55 on Win 10 laptop ... Will update this post from that machine ...

    Ran to the following - then Stalled, on Win 10 Laptop with programmed T_4.1 brought over
    Code:
    ...
    43.32C	1308185
    42.66C	1308205
    43.32C	1308225
    43.32C	1308245
    Last edited by defragster; 09-17-2021 at 11:22 PM.

  24. #24
    Senior Member+ mjs513's Avatar
    Join Date
    Jul 2014
    Location
    New York
    Posts
    7,546
    Quote Originally Posted by PaulStoffregen View Post
    It's been running continuously here for over 46 hours with MacOS.

    Click image for larger version. 

Name:	Screen.jpg 
Views:	13 
Size:	68.0 KB 
ID:	25885
    Think the issue actually goes back to the T4 beta testing days. It was first identified in this post: https://forum.pjrc.com/threads/54711...l=1#post213179 and isolated to Windows. This was where you first started trying to speed up the Serial Monitor: https://forum.pjrc.com/threads/54711...l=1#post213179. It continues for the next several pages.

  25. #25
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,067
    Starting from here : /PaulStoffregen/USB-Serial-Print-Speed-Test

    Runs and quickly STOPS ...

    And back to IDE 1.8.16 w/TD 1.55 - building and upload w/IDE and tLoader w/t_Sermon:
    Code:
    ...
    count=65595445, lines/sec=845026
    count=65595446, lines/sec=845026
    count=65595447,
    Build and upload and open t_Sermon again:
    Code:
    ...
    count=10050314, lines/sec=0
    count=10050315, lines/sec=0
    count=10050316, lines/sec=0
    count=1

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •