| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
I was reversing the 'target' vs 'image' names in the error message,
leading to a bit of confusion.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
|
| |
The code to validate the usb id and product name had some debug hacks
left enabled, which caused it to fail. The short -f version of the
force flag was also not getting parsed correctly.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
|
|
| |
Instead of blindly loading firmware, go get the old device's name and
make sure it matches the new firmware.
Add --force option to allow this to be overridden.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
| |
This waits forever for USB writes to complete, instead of timing out
after five seconds. Useful when debugging the device.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
| |
For devices which report the range of valid flash addresses from their
boot loader, check the loaded image to make sure it fits within that range.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
|
| |
ao-stmload only uses stlink, ao-usbload only uses self-flashing, so
clear up the options in the two programs. The new --raw option skips
the serial and radio cal rewriting when flashing the boot loader.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
| |
These use openocd to download boot loaders to the arm-based products
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
Leave ao-stmload using just stlinkv2
Signed-off-by: Keith Packard <keithp@keithp.com>
|
