nicksydney has quit [Remote host closed the connection]
nicksydney has joined #qi-hardware
uwe_ has quit [Ping timeout: 258 seconds]
uwe_ has joined #qi-hardware
wej_ has joined #qi-hardware
wej has quit [Ping timeout: 250 seconds]
pcercuei has joined #qi-hardware
wej_ has quit [Ping timeout: 250 seconds]
wej has joined #qi-hardware
atommann has joined #qi-hardware
<wpwrak>
sigh. sometimes i wish back the good old times where a man would slay a dragon or, if unavailable, a lion, to prove his worth.
<wpwrak>
but then ARM came and invented their debug interface ...
atommann has quit [Ping timeout: 240 seconds]
atommann has joined #qi-hardware
atommann has quit [Ping timeout: 245 seconds]
wej has quit [Read error: Connection reset by peer]
wej_ has joined #qi-hardware
porchaso0 has joined #qi-hardware
porchao has quit [Ping timeout: 245 seconds]
wej_ has quit [Ping timeout: 250 seconds]
<DocScrutinizer05>
huh?
<DocScrutinizer05>
what's wrong with ARMs debug interface? (except of the nasty 300$ cables you need to attach Lauterbach to it)
wej has joined #qi-hardware
<wpwrak>
the complexity. it's orders of magnitude more complex than anything else i've seen in that area. you have a complex chain of subsystems, several protocol layers (though not described as such), each with its own failure and reporting modes. and so on.
<wpwrak>
arm's documentation also doesn't lead you straight to the solution. it rather stops at a polite distance from the next territory, makes some vague allusions of what you may want to look for over there, then go away and leave you alone.
<wpwrak>
furthermore, none of the stuff is really up to date or applicable. so you need to find out what the concept evolved to on your own.