We received at Raisonance the following message from 'dzingoni'. It could hellp some other users:
<<Thank you for your reply.
Yes, there are news ... after trying for hours to revive the Primer 2 I finally
succeeded. I thought that the problem was during the startup phase because
after a "false start" the Primer 2 actually
did not start (low power red led blinkng fast ... and then nothing). It was
impossible to have the unit ON when launching commands to re-program it or to
download software.
So I tried to start a "debug" of a demo application just after pressing the
button on the unit (during the false startup phase in other words ....) and
miraculously the Ride7 was able to
download the software. Then I reprogrammed the unit to factory setting ... and
now it works ....
The problem is: am I going into the same troubles if I try to install some
other app or debug ?
As a further information please note that the "low voltage" error appeared the
first time when I first tried the unit ... Initially I thought there was a
problem with the Ride7, so I reinstalled it,
then I thought that maybe I was using the wrong demo (maybe one for the
ST7 ...) .... the error appeared for some time, then a "debug start" went OK ..
and then the lock ...
Looks like some problem is present in the driver for the auxiliary
microcontroller. My suggestion, in any case, would be to modify the driver
software in order to be able, in the extreme case, to
bypass the voltage level check and to force the reprogramming of the unit.>>
The problem could be that the application shuts down the power supply by clearing PC13. If the application starts by shutting down the power supply, the embedded RLink cannot controls the Cortex M3. The only solution is to keep the button pressed until the debug session is launched and the FLASH erased.
