<PaulFertser>
NishanthMenon: hey :) do you know git blame?
<NishanthMenon>
PaulFertser: yes ;) at least tracked it down to 3f8f5839641f target: rename cortex_m3.[ch] to cortex_m.[ch] (2011) :) -> so it is older than that..
<PaulFertser>
Wow, it really was added in 09883194f86725f4eae7e6db9eabcf6b3d1511de by Dominic himself.
<PaulFertser>
In 2007 :)
<NishanthMenon>
jeez
<PaulFertser>
git blame 02cd1e39cc^ -- cortex_m.c
<NishanthMenon>
aah thanks.. did'nt know that :D
<antto>
is it like a "this should be a well-chosen constant, but i don't know what right now, so i'll just temporarily put 50... just temporarily!"
gzlb has quit [Ping timeout: 258 seconds]
<NishanthMenon>
heh.. kinda curious with sys_reset how folks get past ROM and crystal stabilization delays to get cpu to halt.. :D I was going to play around with this a bit, but wanted to be sure i was'nt going against some "thou shalt not toucheth this val" that i could'nt see clearly..
<NishanthMenon>
anyways, thanks folks..
gzlb has joined #openocd
<PaulFertser>
NishanthMenon: normal way on cortex_m is to setup a vector catch on reset handler, then trigger reset by any means other than power on reset.
<PaulFertser>
A proper cortex_m target doesn't reset debug unit
<PaulFertser>
Good target shouldn't mind stopping in ROM...
<NishanthMenon>
WAIT_IN_DEBUG that the h/w folks have provided..
<PaulFertser>
Oh my
<NishanthMenon>
:( yeah, I know.. i weep at my own code :(
<PaulFertser>
Why your chip engineers just do not allow stopping in ROM?..
<NishanthMenon>
they seem to have documented the option - but does'nt seem to work for me at least. I looked at the TI "CCS" -> from what I see they did'nt seem to have bothered with it either..
<NishanthMenon>
I think some security folks might have gone a bit bonkers.. or something I suspect.. dunno how to get it right atm..
<PaulFertser>
:/
slobodan has quit [Read error: Connection reset by peer]
slobodan has joined #openocd
slobodan has quit [Read error: Connection reset by peer]