<![CDATA[The dreaded "T" of death...]]>I'm working on a Micropython program to log MQTT results, and it needs the current time to do so.

I'm working in uPyCraft, with the typical write-download-run cycle, and eventually I get to the point where all my program appears to do is print a 'T', and then hang. I can ^C out of the program, and get back to the >>> prompt, and try running the program again, but the only thing that seems to clear the problem is to power-cycle the M5Stack Fire.

Any idea what's happening?

]]>https://community.m5stack.com/topic/2002/the-dreaded-t-of-deathRSS for NodeWed, 29 Apr 2026 18:16:08 GMTSat, 30 May 2020 00:55:34 GMT60<![CDATA[Reply to The dreaded "T" of death... on Sun, 31 May 2020 06:52:35 GMT]]>@robalstona Thanks, I'll give that a try.

]]>https://community.m5stack.com/post/8882https://community.m5stack.com/post/8882Sun, 31 May 2020 06:52:35 GMT<![CDATA[Reply to The dreaded "T" of death... on Sat, 30 May 2020 14:10:48 GMT]]>It's probably part of the word "Traceback." From what I noticed, the builtin terminal from uPyCraft does not cope with the connection during the hangs or interruption of the program and does not display / receive any data from esp. Using another terminal like linux screen or windows term this information is displayed without a problem.

]]>https://community.m5stack.com/post/8875https://community.m5stack.com/post/8875Sat, 30 May 2020 14:10:48 GMT