Commit ca483eb2 authored by David Boddie's avatar David Boddie
Browse files

Qualify statements about resets

parent 76092b85
Pipeline #52166 passed with stage
in 1 minute and 44 seconds
......@@ -32,8 +32,9 @@ Issues
driver.
See `dvk-mx8m-bsb issue 3 <https://source.puri.sm/Librem5/dvk-mx8m-bsb/issues/3>`_
for details.
* The board may reset when under heavy load, either due to processor-intensive
software or peripherals that draw large currents.
* When running older versions of the system software the board could reset when
under heavy load, either due to processor-intensive software or peripherals
that draw large currents.
See :ref:`imx8_devkit_troubleshooting_resets` for possible workarounds for
this behavior.
......
......@@ -3,7 +3,11 @@
Spurious Resets
===============
The development board may spuriously reset when under heavy load. This can be due to processor-intensive software (see `this issue <linux-emcraft issue 22_>`_) or when power-intensive peripherals are active (see `this issue <linux-emcraft issue 27_>`_).
The development board may spuriously reset when under heavy load when running
older versions of the system software. This can be due to processor-intensive software (see `this issue <linux-emcraft issue 22_>`_) or when power-intensive peripherals are active (see `this issue <linux-emcraft issue 27_>`_).
Updating the system image to the latest version can help to avoid these issues
-- see :ref:`imx8_devkit_flashing_emmc` for instructions on how to do this.
If your development board does not unexpectedly reset during use then there is no need to take action. However, if it becomes an issue then the following information may be useful.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment