On 16/09/15 02:07, Angus Gratton wrote: > On Tue, Sep 15, 2015 at 06:16:49PM +0200, Andrzej Telszewski wrote: >> It's not about the bad SWD connection, but rather about the bug in the >> chip. The chip is: nRF51822 QFAACA. >> >> The problem is that, in some revisions of the chip, if you enter >> SYSTEMOFF mode, it's not possible for the debugger to connect to the >> chip any more. To connect again, you either have to wake-up the chip or >> recover the chip using Nordic's nrfjprog. > > Thanks for explaining. > > In addition to checking for a zero read result and erroring out cleanly if > that happens, is seems to me that a good long-term fix for this problem would > be to have openocd detect and recover from a SYSTEMOFF state, as part of > either the nrf examine routine or the reset routine. > > Do you know anything about the recovery steps that nrfjprog does to wake up > the chip?
Dear lord, you're reading in my minds!;) I was about to ask if it could be implemented. Have a look here: https://github.com/hlnd/nrf51-pure-gcc-setup/blob/master/template/Makefile.posix and look for: recover.jlink I don't know the exact procedure, but it's all about correct SWD bitbanging. I'll ask Nordic's support, maybe they could give me the exact first-hand procedure. > > > Angus > -- Best regards, Andrzej Telszewski ------------------------------------------------------------------------------ Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
