docs: flashing: Emphasize potential loss of data
Internal flashing can result in corrupted or lost OS data. Make this more explicit for internal flashing, and make it a point for external flashing. Signed-off-by: Tim Crawford <tcrawford@system76.com>
This commit is contained in:
parent
d36cf981fe
commit
dab3a24fcb
@ -4,8 +4,9 @@
|
||||
|
||||
Use this method for flashing a system already running System76 EC.
|
||||
|
||||
This will trigger a watchdog reset causing the system to immediately power off.
|
||||
Save and close all applications before flashing.
|
||||
This will trigger a watchdog reset causing the system to **immediately power
|
||||
off**. OS data may be lost or corrupted as a result. Save and close all
|
||||
applications before flashing.
|
||||
|
||||
```
|
||||
make BOARD=<vendor>/<model> flash_internal
|
||||
@ -13,7 +14,11 @@ make BOARD=<vendor>/<model> flash_internal
|
||||
|
||||
## External programmer
|
||||
|
||||
Use this method for first-time flashing or flashing a bricked controller.
|
||||
Use this method for:
|
||||
|
||||
- flashing from proprietary firmware to System76 EC firmware
|
||||
- flashing without risking loss of OS data
|
||||
- flashing a bricked controller
|
||||
|
||||
This requires:
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user