<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Screen stopped working, nonsense AXP data]]></title><description><![CDATA[<p dir="auto">Hi,<br />
I've got two pieces of M5StickC a few days ago. After trying out some of the example codes, the display stopped working in one of them (similar to the "M5StickC screen don't work" topic). I uploaded a small test program into it, which writes to serial port, to see if the other parts were still operating. Incidentally this program dumps data from the AXP chip and the results were surprising:</p>
<p dir="auto"><strong>Output from the one without working display:</strong></p>
<p dir="auto">GetBatState: 1<br />
GetCoulombchargeData: -1<br />
GetCoulombdischargeData: -1<br />
GetCoulombData: 0.0000</p>
<p dir="auto">GetBatVoltage: 4.7685<br />
GetBatCurrent: 0.0000<br />
GetVinVoltage: 7.3695<br />
GetVinCurrent: 2709.3750<br />
GetVBusVoltage: 7.3695<br />
GetVBusCurrent: 1625.6250</p>
<p dir="auto">GetTempInAXP192: 288.8C</p>
<p dir="auto">GetBatPower: 2362232.0000<br />
GetBatChargeCurrent: 2167.5000<br />
GetAPSVoltage: 6.0690<br />
GetBatCoulombInput: 23860.5645<br />
GetBatCoulombOut: 23860.5645</p>
<p dir="auto">GetWarningLevel: 1</p>
<p dir="auto"><strong>Output from the correctly working one:</strong></p>
<p dir="auto">GetBatState: 1<br />
GetCoulombchargeData: -1<br />
GetCoulombdischargeData: -1<br />
GetCoulombData: 0.0000</p>
<p dir="auto">GetBatVoltage: 3.5805<br />
GetBatCurrent: -58.5000<br />
GetVinVoltage: 2.6520<br />
GetVinCurrent: 0.0000<br />
GetVBusVoltage: 0.0000<br />
GetVBusCurrent: 0.0000</p>
<p dir="auto">GetTempInAXP192: 20.0C</p>
<p dir="auto">GetBatPower: 266.9931<br />
GetBatChargeCurrent: 0.0000<br />
GetAPSVoltage: 3.5784<br />
GetBatCoulombInput: 23860.5645<br />
GetBatCoulombOut: 23860.5645</p>
<p dir="auto">GetWarningLevel: 0</p>
<p dir="auto">Both outputs were generated while the stick was running on its internal battery.<br />
The source is on github: <a href="https://github.com/mdevel1/M5StickC_Battery_Monitor" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/mdevel1/M5StickC_Battery_Monitor</a></p>
<p dir="auto">After finding and removing two loose magnets inside the case (see "Loose magnets inside can short the battery and other components" topic), and power cycling the stick, the AXP chip somehow returned into a working state, the dumped values are back to normal (except which didn't make sense before), and the display is working too.</p>
]]></description><link>https://community.m5stack.com/topic/1634/screen-stopped-working-nonsense-axp-data</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 19:11:35 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/1634.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 19 Jan 2020 15:05:46 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Screen stopped working, nonsense AXP data on Sun, 09 Feb 2020 08:35:45 GMT]]></title><description><![CDATA[<p dir="auto">For the record: the coulomb counter data is fixed, but still undocumented in the newest version of the library (not released yet, only on Github).<br />
There was another issue with the newest version, with a fix that is not yet merged, and available only as a <a href="https://github.com/m5stack/M5StickC/pull/93" target="_blank" rel="noopener noreferrer nofollow ugc">pull request</a>.</p>
]]></description><link>https://community.m5stack.com/post/7326</link><guid isPermaLink="true">https://community.m5stack.com/post/7326</guid><dc:creator><![CDATA[mdevel1]]></dc:creator><pubDate>Sun, 09 Feb 2020 08:35:45 GMT</pubDate></item></channel></rss>