On Mon, Mar 27, 2023 at 03:38 PM, Bill Cromwell wrote:
Anything beyond a nonjudgmental suggestion should be left out. I am a long time Linux user and I can testify that Linux has its own pitfalls, just as the other popular operating systems.
The tool must be adapted to the purpose, but the bottom line is to get new FW onto the tinySA without damaging the device or the PC.? And if Windows is too much of a hassle, you can also use Linux on a RasPi, which many hobbyists have in their drawers:
===========================================
If you just want to load new firmware, download it on the RasPi or transfer it from your Windows PC to the RasPi.?
Open a terminal window (either directly on the RasPi if keyboard and screen are connected) or via SSH (e.g. via putty from Windows). Install the tool dfu-util (you need to do this only once):?
? ? sudo apt install dfu-util
?
Change to the directory where the *.bin file is located, (name is e.g. tinySA_v1.4-77-gae025eb.bin), switch the tinySA into dfu mode and type (use the correct name of your bin file):
? ??dfu-util -d 0483:df11 -a 0 -s 0x08000000:leave -D tinySA_v1.4-77-gae025eb.bin
READY===========================================If you want to build your own binaries from Eriks source code and flash them - do this:
In a terminal window (either directly on the RasPi if keyboard and screen are connected) or via SSH (e.g. via putty from Windows):
1. installation of the necessary programs
? ? sudo apt install gcc-arm-none-eabi git dfu-util
2. fetch source and submodule.
? ? git clone https://github.com/erikkaashoek/tinySA.git
? ? cd tinySA
? ? git submodule update --init --recursive
?
3. then connect the tinySA, switch it on and either
3a. create the program for tinySA
? ? make clean
? ? make && make flash
3b. or the program for tinySA Ultra
? ? make clean
? ? TARGET=F303 make && make flash
?
READY?
?
1. and 2. are only necessary once to init the build system - 1. may take some time.
?
If there are new versions on Erik's GitHub, update them on the RasPi.
? ? cd tinySA
? ? git pull
?
After that, you can continue directly with 3a or 3b.
?
The best way to do this is to copy/paste the commands into a terminal.
HTH
Martin
?