You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I looks like the request of xsbug to send additional data for @3FFFC79C triggers a reset of the MCU...
I captured the xsbug traffic using Wireshark
The data package the MCU collects & sends back to xsbug is almost 10kb heavy.
Assumption: While processing this data the MCU internally hits an exception (e.g. memory full) & resets.
The MCU streams the information it sends to xsbug. It is never entirely in memory at one time. It can be arbitrarily large and not fail because of limited memory. xsbug was designed for resource-constrained environments. ;)
Build environment: macOS
Target device: m5stack Atom Lite
Description
When trying to examine the debug status via the left hand panels,
xsbug
tends to close the status.See what happens when clicking on
this
.xsbug-1080.mov
This is the communication protocol between the MCU &
xsbug
:I looks like the request of
xsbug
to send additional data for@3FFFC79C
triggers a reset of the MCU...The text was updated successfully, but these errors were encountered: