Moved to new repo: Coldcard/recovery-images
This commit is contained in:
parent
014953e2fa
commit
16d506fd9f
4
stm32/recovery-image/.gitignore
vendored
4
stm32/recovery-image/.gitignore
vendored
@ -1,4 +0,0 @@
|
||||
tmp.txt
|
||||
flist.txt
|
||||
output.img
|
||||
*.img.xz
|
||||
@ -1,32 +0,0 @@
|
||||
# (c) Copyright 2022 by Coinkite Inc. This file is covered by license found in COPYING-CC.
|
||||
#
|
||||
# Using "mtools" here. A weapon from a more civilized age...
|
||||
#
|
||||
|
||||
# NOTE: mtools.conf in current directory maps z: to ./output.img
|
||||
export MTOOLSRC=mtools.conf
|
||||
MFORMAT=mformat
|
||||
MCOPY=mcopy
|
||||
|
||||
RELEASES ?= $(wildcard ../../releases/*-mk4-*.dfu) $(wildcard ../*-mk4-RC1*.dfu) \
|
||||
$(wildcard ../../releases/*-q1-*.dfu) $(wildcard ../*-q1-RC1*.dfu)
|
||||
|
||||
OUTPUT ?= cc-recovery-$(shell date +%F).img.xz
|
||||
|
||||
all: output.img
|
||||
|
||||
output.img: $(RELEASES) Makefile
|
||||
dd if=/dev/zero of=output.img bs=1024 count=160
|
||||
$(MFORMAT) -v CCRECOVER -f 160 -N 2022 -C z:
|
||||
ls -1 $(RELEASES) | sort -n > flist.txt
|
||||
cat internal-readme.txt flist.txt > tmp.txt
|
||||
$(MCOPY) -bsmp tmp.txt z:README.TXT
|
||||
for f in $(RELEASES); do echo $$f ; dd if=$$f obs=512 conv=osync >> output.img; done
|
||||
xz -cv9 < output.img > $(OUTPUT)
|
||||
cat flist.txt
|
||||
ls -l $(OUTPUT)
|
||||
|
||||
dev:
|
||||
$(MAKE) RELEASES=../dev.dfu OUTPUT=dev-recovery.img.xz
|
||||
|
||||
# EOF
|
||||
@ -1,17 +0,0 @@
|
||||
|
||||
## Recovery Disk Image
|
||||
|
||||
The Mk4 bootloader is smart enough to read an SD card. However, you
|
||||
will only be able to trigger the SD card loading code, if the system
|
||||
is powered-down during the upgrade process. At that point, the
|
||||
intended (new) firmware image has been lost because it it held in
|
||||
PSRAM (volatile memory) during the flash writing process.
|
||||
|
||||
The bootloader will only install an image of exactly the same version
|
||||
as was being installed when interrupted. This is done by verifying
|
||||
the checksum vs. a value set in SE1 by the pin-holder. This prevents
|
||||
side-loading or up/downgrade attacks.
|
||||
|
||||
This directory holds data and code to build a special SD-card disk
|
||||
image with all possible releases. The goal is a single disk image that
|
||||
can be used restore a Coldcard of any (intended) version.
|
||||
@ -1,15 +0,0 @@
|
||||
Coldcard Mk4 Recovery Card
|
||||
==========================
|
||||
|
||||
DO NOT WRITE to this card.
|
||||
|
||||
You cannot see files here, but they are where they need to be.
|
||||
|
||||
Reformat this card when finished with it.
|
||||
|
||||
Do not believe what your tools say about the size of this card.
|
||||
|
||||
|
||||
Versions Included Here
|
||||
======================
|
||||
|
||||
@ -1,10 +0,0 @@
|
||||
# You need to:
|
||||
#
|
||||
# export MTOOLSRC=mtools.conf
|
||||
# OR
|
||||
# setenv MTOOLSRC mtools.conf
|
||||
#
|
||||
# to be able to use these settings interactively.
|
||||
#
|
||||
drive z: file="output.img"
|
||||
#MTOOLS_NAME_NUMERIC_TAIL=0
|
||||
Loading…
Reference in New Issue
Block a user