John Finley bb1add3390 Unprotect option (#1)
* readout unprotect is not done unless explicitly enabled

New command line option "-u" must be supplied or the readout unprotect
will not be done on erase failure. If the erase fails and readout
unprotect is not enabled (i.e. -u was not supplied) then the program
just terminates with an error (nonzero) exit status.

The intent is for the caller to be able to do a few retries to see if
the erase failure is transient, then do an update with readout unprotect
enabled as a last resort.

* explicit logging in case of initChip error

Also test code to simulate initChip error.
2016-04-26 18:23:06 -07:00
2016-04-26 18:23:06 -07:00
Description
Open Solo: Life After 3DR! All open sourced Solo systems including the sololink, shotmanager, Artoo STM32, IMX6, Vagrant VM, and Solo-Builder
20 MiB
Languages
C 77.7%
Python 11.4%
C++ 8.6%
Shell 1.6%
BitBake 0.4%
Other 0.2%