#qi-hardware IRC log for Sunday, 2015-02-08

DocScrutinizer05((<wpwrak> maybe a fresh pair of eyes will find it in minutes ...))  Link, and instructions what's the problem to look for, please!11:47
DocScrutinizer05whitequark: are you meanwhile ready to emigrate before the frontiers close and arms are pointing direction west?11:49
wpwrakDocScrutinizer05: it's  a hard piece of work. the question is: why is my implementation of SWD unreliable ? my implementation is here: https://gitorious.org/anelok/anelok/source/swdlib12:41
wpwrakthere are some links to resources in https://gitorious.org/anelok/anelok/source/swdlib/swdlib.c12:41
wpwraknote that there is more out there, and some of the material is contradictory. so the first step is to develop consistent conceptd12:42
DocScrutinizer05sdwlib is conecting to the anelok "debug port" to program the chip? From ben?12:59
wpwrakyes. ben -> ubb -> anelok -> "debug port" of the kinetis14:53
wpwraki think most arms nowadays have some form of swd14:53
wpwrakswd then talks to the debug port or the AP. on the AP you have one entity that does a few flash things and another one that gives access to the AHB (system bus). so you basically have: 1) a wire protocol to move data to the debug interface. 2) a protocol to talk to the debug port. 3) a protocol to talk to the AHB port. 4) a protocol (which is also used by software) to command flash operation.15:05
wpwrakplus a few bits and pieces, e.g. the protocol on the MDM-AP, which is the critter that does the additional flash operations, such as checking security status, commanding a mass erase, etc.15:07
--- Mon Feb 9 201500:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!