defragster
Senior Member+
@MM - instructions will be handy - there was a recent note about those close pins to battery holder needing trimmed/attended to in some fashion.
Interesting - you guys got one already - USPS says something to be here 12/12, tomorrow from MA.
That is very unfortunate DerekR I lost One T4 - but that was having the IDE running at 960 MHz OC for a T4 with heat sink - and plugging in a fresh T4 without one … and sending a sketch not being aware of that SPEED setting. It was i2c ssd1306 display so it sat powered up and reprogrammed as I opened the driver and read code for settings and reprogrammed a time or two - all the while it was running hot. That one happened to be a Purple OSH T4.
As far as long term use and T4 stability - I have on my desk the three 1062 Beta units PJRC evolved - all still functional since Feb to June? The first in Jan 2019 was the 1052 - and I put that away working. So the three here I use and trust and have left running for days or weeks one way or another over 6+ months show no troubles. Then I have original TallDog Beta , the Tindie Ult Breakout ( used the least ), another T4 on a PJRC Purple display test board , one on a FRDM4236 breakout - so just 7 of them in my sample set - but all have been working fine since two of those came from first production run before they were released. They have been through many hours of USB Host testing, various Display testing.
I worked them hard in Beta and only issue was solved during beta where external power on pins was preventing proper shutdown - 7 Rx and Tx lines of 3.3V during testing, and that was a one wire change Paul made with no issues other than that.
Not sure what it could be there giving bad behavior … T4 Is allergic to 5V, and running overclocked can cause heat damage. Have you tried the 15 second Restore? Holding Program button 15 secs watching RED LED for it to flash then release and it will restore base level settings within the MCU - I have had to do that at times it seemed when displays or other things in development during Beta could set it odd.
Interesting - you guys got one already - USPS says something to be here 12/12, tomorrow from MA.
...
But right now that's academic because disaster hit!
...
That is very unfortunate DerekR I lost One T4 - but that was having the IDE running at 960 MHz OC for a T4 with heat sink - and plugging in a fresh T4 without one … and sending a sketch not being aware of that SPEED setting. It was i2c ssd1306 display so it sat powered up and reprogrammed as I opened the driver and read code for settings and reprogrammed a time or two - all the while it was running hot. That one happened to be a Purple OSH T4.
As far as long term use and T4 stability - I have on my desk the three 1062 Beta units PJRC evolved - all still functional since Feb to June? The first in Jan 2019 was the 1052 - and I put that away working. So the three here I use and trust and have left running for days or weeks one way or another over 6+ months show no troubles. Then I have original TallDog Beta , the Tindie Ult Breakout ( used the least ), another T4 on a PJRC Purple display test board , one on a FRDM4236 breakout - so just 7 of them in my sample set - but all have been working fine since two of those came from first production run before they were released. They have been through many hours of USB Host testing, various Display testing.
I worked them hard in Beta and only issue was solved during beta where external power on pins was preventing proper shutdown - 7 Rx and Tx lines of 3.3V during testing, and that was a one wire change Paul made with no issues other than that.
Not sure what it could be there giving bad behavior … T4 Is allergic to 5V, and running overclocked can cause heat damage. Have you tried the 15 second Restore? Holding Program button 15 secs watching RED LED for it to flash then release and it will restore base level settings within the MCU - I have had to do that at times it seemed when displays or other things in development during Beta could set it odd.