<![CDATA[Difference between reset and soft reboot]]>The SiPy freezes (REPL unresponsive) on this line after a soft reboot but works fine after a reset.
sd = SD()

]]>https://forum.pycom.io/topic/1885/difference-between-reset-and-soft-rebootRSS for NodeTue, 08 Sep 2026 06:46:37 GMTMon, 02 Oct 2017 20:35:57 GMT60<![CDATA[Reply to Difference between reset and soft reboot on Mon, 02 Oct 2017 20:35:57 GMT]]>The SiPy freezes (REPL unresponsive) on this line after a soft reboot but works fine after a reset.
sd = SD()

]]>https://forum.pycom.io/post/11518https://forum.pycom.io/post/11518Mon, 02 Oct 2017 20:35:57 GMT<![CDATA[Reply to Difference between reset and soft reboot on Sun, 05 Nov 2017 11:43:22 GMT]]>@pmulvey it is my experience, though haven't had it confirmed from anyone else, that soft reset will introduce all kinds of weird problems (compared to a hard reset) eg, for me - I get OS errors that different resources aren't available. Like ADC and Network.. I'm on a Lopy btw.

]]>https://forum.pycom.io/post/12391https://forum.pycom.io/post/12391Sun, 05 Nov 2017 11:43:22 GMT<![CDATA[Reply to Difference between reset and soft reboot on Sun, 05 Nov 2017 12:09:44 GMT]]>@soren Soft reset clear mostly the micropython space. The underlying OS, the network stack and the hardware modules are not reset. For instance, when you have sockets open and do a soft reset, you'll get an error to use these sockets again. Definitely reliable is a hard reset by pulling the reset input low, e.g. by pushing the reset button. Close to that is using machine.reset().
If you are tracing errors and need a clear repeatable state, starting with a hard reset is recommended.

]]>https://forum.pycom.io/post/12392https://forum.pycom.io/post/12392Sun, 05 Nov 2017 12:09:44 GMT<![CDATA[Reply to Difference between reset and soft reboot on Mon, 06 Nov 2017 22:25:08 GMT]]>@robert-hh Is there a software way to do a hard reset? You say machine.reset() is close but we all know what close is good for.

]]>https://forum.pycom.io/post/12411https://forum.pycom.io/post/12411Mon, 06 Nov 2017 22:25:08 GMT<![CDATA[Reply to Difference between reset and soft reboot on Tue, 07 Nov 2017 06:32:46 GMT]]>@ssmith Unless you find something specific, machine.reset() is as good as it can get. It seems to do everything software does after hard reset.

]]>https://forum.pycom.io/post/12413https://forum.pycom.io/post/12413Tue, 07 Nov 2017 06:32:46 GMT<![CDATA[Reply to Difference between reset and soft reboot on Tue, 07 Nov 2017 08:19:39 GMT]]>@pmulvey
I have the same feeling as you
i have reported issue about SD card reset few months ago
https://github.com/pycom/pycom-micropython-sigfox/issues/18

]]>https://forum.pycom.io/post/12414https://forum.pycom.io/post/12414Tue, 07 Nov 2017 08:19:39 GMT<![CDATA[Reply to Difference between reset and soft reboot on Tue, 07 Nov 2017 08:29:00 GMT]]>@ssmith If you need a hard reset, you could connect a GPIO pin to Reset and pull that low. I have experienced the SD card issue too, which seems to require a pyhsical reset signal. But I dod not follow up that yet, whther it's a missimng software init of the SD card interface/driver, or a pysical reset signal missing.

]]>https://forum.pycom.io/post/12415https://forum.pycom.io/post/12415Tue, 07 Nov 2017 08:29:00 GMT