Forum Rule: Always post complete source code & details to reproduce any issue!
Page 173 of 173 FirstFirst ... 73 123 163 171 172 173
Results 4,301 to 4,311 of 4311

Thread: Teensy 4.0 First Beta Test

  1. #4301
    Senior Member
    Join Date
    Dec 2016
    Location
    Montreal, Canada
    Posts
    3,070
    True, I will look into it this week since CANFD is pretty much in public testing phase now to find any bugs that may exist. This will give me time to work on watchdog before going back to work on CAN2.0

  2. #4302
    Great! Mjs513 posted some info in the Teensy4 software restart thread. It seems that every attempt to restart the T4 results in a shutdown? Not clear what the reason is and if there is already a solution for it.

  3. #4303
    Senior Member
    Join Date
    Dec 2016
    Location
    Montreal, Canada
    Posts
    3,070
    Click image for larger version. 

Name:	Screenshot_20191003-151935_Adobe Acrobat.jpg 
Views:	17 
Size:	74.0 KB 
ID:	17773

    Wonder if this is relevant
    Btw, wdt doesnt work in low power modes or deep sleep
    In any case it is suggested the best wtd reset is via an external pin controlled by the wdt (tied to hardware reset pin)

  4. #4304
    Senior Member+ manitou's Avatar
    Join Date
    Jan 2013
    Posts
    2,193
    Quote Originally Posted by tonton81 View Post

    Wonder if this is relevant
    Btw, wdt doesnt work in low power modes or deep sleep
    In any case it is suggested the best wtd reset is via an external pin controlled by the wdt (tied to hardware reset pin)
    The NXP 1060 SDK has an example that works and does reset with WDOG1 on NXP 1060 eval board. So i think T4 problems might relate to T4 bootloader and/or core startup procedure or ?
    ref: https://forum.pjrc.com/threads/57810...l=1#post217524


    EDIT: i had only tested on NXP 1050 eval board, but confirmed wdog01 example does work on NXP 1060 eval board.

    I made a teensy version ( wdog1.ino ) of the SDK WDOG1 example. The sketch works on T4B1 (1050), but fails to restart on production T4 (1060).
    Last edited by manitou; 10-05-2019 at 11:10 AM.

  5. #4305
    Senior Member
    Join Date
    Dec 2016
    Location
    Montreal, Canada
    Posts
    3,070
    According to nxp threads i glimpsed over, they claim the dev boards are tied via hardware via trigger pin to reset pin , t4 version was made from the 1050 sdk

  6. #4306
    Senior Member+ manitou's Avatar
    Join Date
    Jan 2013
    Posts
    2,193
    Quote Originally Posted by tonton81 View Post
    According to nxp threads i glimpsed over, they claim the dev boards are tied via hardware via trigger pin to reset pin , t4 version was made from the 1050 sdk
    the 1060 eval board schematic is complex, and there is a RESET button to POR pin, but i don't see a "trigger pin to reset pin"

  7. #4307
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,695

    Notes on testing USB Host OverClocking and Current and Temp:

    Measuring current a 15s restore results in T4 booting blink at 55 and 56 mA. Sound right to suggest my DMM is reading right.

    Working with USB Host and Ethernet LAN adapter on two T4's with a heat sink { copper .25" high not quite .5" square } it lets the T4 run at 912 Mhz.
    > One is PJRC Ribbon final Beta T4 - the other is direct soldered on the initial @loglow board.
    > one code set not printing temp - current a bit diff - both seem to have same 912 MHz behavior.

    Room is cooler now - idling at 73C - room was warmer earlier and temp hit 78 and stayed running down to current 73C alive and Ping working.

    { interesting because with boards.txt edited so 1008 MHz does 1008 not 996 - a sketch posted was FAULTING under 70C - @mjs513 T4-TEMPMON_buddabrot.ino using the debug_tt that reactivates the Fault code }

    So back to USBHost - running the ASIXEthernet_Test.ino for the LAN - without LAN USB adapter attached:

    >> Starting two T4's hit 208 or 215 mA as it comes up before USB LAN adapter is connected.
    - nothing else connected PJRC beta has a green LED - otherwise current is just higher MCU MHz and USBHost device active.
    - Did this measure because if the USB LAN adapter is connected at startup it fails to ever connect when OC'd to 912 MHz

    >> To the running T4 connect the USB Adapter and current goes to 368 to 384 mA and connect to LAN
    - This is where running temp with heat sink hits 73-78 degrees C


    Under 912 MHz USBHost LAN works - it also works when plugged into Powered Hub plugged into T4.
    >> Running through Powered HUB the T4 is only drawing 110 mA

    The MSC HDD USBHost code also works to HDD at 960 MHz - but that is through powered HUB

    Connecting the PJRC board through powered hub to LAN USB adapter works at 960 MHz
    > Current is at .111 Ma
    > reported temp is 76, where it was last 73 at 912 MHz

  8. #4308
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,695
    NOTE on temps:

    Running at 960 MHz the T_4 with active USBHost noted above to LAN through powered hub maintained 78C today not problem.

    Going to another sketch @luni intervaltimer posted - and running at 1008 MHz ( actually 996 as it is a fresh TD 1.48 on IDE 1.8.9 ) USB print issues show up about 65C. Occasional extra chars. Noted elsewhere I got a FAULT to occur that was trapped - but just from OC/Temp issue. Not sure now of temp on that or the situation.

    But for the above when OC speeds go higher - wondering if it make sense to drop the threshold on TempMon in some fashion? Would have to add heat to get to 80 from the 78 observed. All this OC was with solid Copper heat sink (with square blob top surfaces) and static air. Blowing across the 65C test case with bad prints dropped temp and printing no longer showed issues. A bit warmer and it just QUIT with no Fault reported at 996 MHz.

    Perhaps the Arm_Clock set code could adjust the temp down - at least for warning High as once it gets hot it seems to run away - well below 80 at 996 - better cooling keeps the temp down and function at 60C seems like it might be okay.

  9. #4309
    Senior Member+ mjs513's Avatar
    Join Date
    Jul 2014
    Location
    New York
    Posts
    4,101
    Quote Originally Posted by defragster View Post
    NOTE on temps:

    Running at 960 MHz the T_4 with active USBHost noted above to LAN through powered hub maintained 78C today not problem.

    Going to another sketch @luni intervaltimer posted - and running at 1008 MHz ( actually 996 as it is a fresh TD 1.48 on IDE 1.8.9 ) USB print issues show up about 65C. Occasional extra chars. Noted elsewhere I got a FAULT to occur that was trapped - but just from OC/Temp issue. Not sure now of temp on that or the situation.

    But for the above when OC speeds go higher - wondering if it make sense to drop the threshold on TempMon in some fashion? Would have to add heat to get to 80 from the 78 observed. All this OC was with solid Copper heat sink (with square blob top surfaces) and static air. Blowing across the 65C test case with bad prints dropped temp and printing no longer showed issues. A bit warmer and it just QUIT with no Fault reported at 996 MHz.

    Perhaps the Arm_Clock set code could adjust the temp down - at least for warning High as once it gets hot it seems to run away - well below 80 at 996 - better cooling keeps the temp down and function at 60C seems like it might be okay.
    @defragster - could drop it but probably better just not have it as a option. Think we verified at above 960Mhz we are running into operating issues. At 1Ghz 65C will get reached rather rapidly.

  10. #4310
    Senior Member DD4WH's Avatar
    Join Date
    Oct 2015
    Location
    Central Europe
    Posts
    448
    @defragster @mjs513 , just for your records

    My experience with overclocking is the following:

    Yesterday, I could run your Buddhabrot example at 1008MHz for more than one hour without problem (I use set_arm_clock in the sketch and inserted a line for a TFT printout of F_CPU_ACTUAL in the sketch, so I think it was "real" 1008MHz, does that make sense?). I have a massive 10x10mm copper heatsink [Alphacool 17426 GPU RAM Copper heatsink] glued to the T4 processor with thermal glue [Silverbead Thermal Glue Adhesive SG100X]. The Buddhabrot sketch @1008MHz never exceeds 70 degrees with that heatsink and stays around 42 degrees C @600MHz and around 57 degrees C @996MHz.

    Click image for larger version. 

Name:	T4 heatsink DD4WH.JPG 
Views:	8 
Size:	135.2 KB 
ID:	17915

    However, when I tried the sketch again today, I was unable to use 1008MHz, the sketch would not run, max CPU freq useable was 996MHz with max temp of about 57 degrees.

    When I use the T4 Convolution SDR sketch, the maximum useable CPU frequency is 948MHz [temperature rises to 66 degrees C] (set during runtime with an encoder and set_arm_clock). With 960MHz I see problems with displaying on the TFT ILI9341 and after a while the sketch crashes and holds. With more than 960MHz the script almost immediately crashes, even with CPU temperatures around 68 degrees C.

    It seems that overclocking is a little unstable above 948MHz and also dependent on processor load and temperature?
    Last edited by DD4WH; Yesterday at 08:11 PM. Reason: added glue type and heatsink type

  11. #4311
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,695
    Quote Originally Posted by DD4WH View Post
    @defragster @mjs513 , just for your records

    My experience with overclocking is the following:

    Yesterday, I could run your Buddhabrot example at 1008MHz for more than one hour without problem (I use set_arm_clock in the sketch and inserted a line for a TFT printout of F_CPU_ACTUAL in the sketch, so I think it was "real" 1008MHz, does that make sense?). I have a massive 10x10mm copper heatsink glued to the T4 processor with thermal glue. The Buddhabrot sketch @1008MHz never exceeds 70 degrees with that heatsink and stays around 42 degrees C @600MHz and around 57 degrees C @996MHz.

    ...
    However, when I tried the sketch again today, I was unable to use 1008MHz, the sketch would not run, max CPU freq useable was 996MHz with max temp of about 57 degrees.

    When I use the T4 Convolution SDR sketch, the maximum useable CPU frequency is 948MHz [temperature rises to 66 degrees C] (set during runtime with an encoder and set_arm_clock). With 960MHz I see problems with displaying on the TFT ILI9341 and after a while the sketch crashes and holds. With more than 960MHz the script almost immediately crashes, even with CPU temperatures around 68 degrees C.

    It seems that overclocking is a little unstable above 948MHz and also dependent on processor load and temperature?
    Good feedback - the Buddhabrot sketch is courtesy of @mjs513. The IDE setting of 1008 actuals codes to 996 through the TD 1.48 setup. It can be changed there.

    Seems noteworthy that over 75C works at 960 MHz and passing 60-65C at higher speeds is failing in odd in what should be a usable temp range. The voltage overboost is either not enough to run some portion - or too much for some other portion of the MCU?

    Interesting your 10mmx10mm heat sink worked that well. Heat sink here noted below is 6 gm in weight and 0.5" square and has a thermal tape to attach - the glue probably better?

    Different sketch stress can run differently - my 960MHz test mostly with USBHost - once through USB Hub it seemed stable - even at 78C.

    Quote Originally Posted by mjs513 View Post
    @defragster - could drop it but probably better just not have it as a option. Think we verified at above 960Mhz we are running into operating issues. At 1Ghz 65C will get reached rather rapidly.
    Seems right - comment or remove 996/1008 as a speed option. 960 MHz seems to run on two here even up to 78C in normal room temp with a simple copper heat sink that weighs 6 grams.

    912 seems to have more headroom than 960 for current to feed HostUSB - but even 912 won't always feed USBHost LAN adapter directly where the 816 MHz option seems to without going to powered USB HUB. But even going through HUB where T_4's LDO is pushing just over 100 ma instead of over 250-350 - the 1Ghz range seems to fail.

    So it seems over 912 or 960 seems on the edge of losing function when temps rise as noted into the 65C range.

Posting Permissions

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