From 4f4b26c429f2bb12d80a649356961450a262e5ac Mon Sep 17 00:00:00 2001 From: Markus Date: Sat, 13 Jun 2020 11:34:09 +0200 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5193f71..886fdf0 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ These files can be flashed with either Didier Méquinon's flasher available from **WARNING: with BaS_gcc installed, do not try to flash anything from EmuTOS with Didier's flasher tool if you do not have a BDM pod. This will not work currently and leave you with a bricked Firebee. This is not EmuTOS' fault but a "feature" (rather a missing one) of BaS_gcc that currently does not run from RAM (it could, but this has been disabled for now for the sake of easier debugging). It runs from flash and its (required) interrupt handlers reside there as well. Didier's flasher tool does not disable interrupts while flashing, so you will most likely run into a situation where Didier's flasher tool erased the flash to rewrite it and (innocent) EmuTOS will try to call an interrupt handler that is not there. Unfortunately, there is no way to remedy from this situation other than BDM.** -Note that this does not apply when flashing from FireTOS which is safe (as FireTOS replaces BaS_gcc's interrupt handlers with it's own copy in RAM. +Note that this does not apply when flashing from FireTOS which is safe (as FireTOS replaces BaS_gcc's interrupt handlers with it's own copy in RAM). Bottom line: if you want to flash BaS_gcc with Didier's tool, do it from FireTOS ONLY! Unless you have a BDM device (which I'd personally recommend under all circumstances anyway), that is.