NishanthMenon changed the topic of #openocd to: this is the place to discuss all things OpenOCD | Logs: https://libera.irclog.whitequark.org/openocd/
Krazubu has quit [Quit: My Mac Pro has gone to sleep. ZZZzzz…]
tsal has quit [Ping timeout: 256 seconds]
tsal has joined #openocd
xantoz has quit [Read error: Connection reset by peer]
xantoz has joined #openocd
nerozero has joined #openocd
Bertl_oO is now known as Bertl_zZ
Haohmaru has joined #openocd
Krazubu has joined #openocd
Hawk777 has quit [Quit: Leaving.]
xantoz has quit [Read error: Connection reset by peer]
xantoz has joined #openocd
renrelkha has quit [Quit: bye]
renrelkha has joined #openocd
<Krazubu> hi, please could someone tell me what this error means ? http://pastie.org/p/3aNwh8Z67vkTMPV200RvSG
<Krazubu> I have communication issues but I wonder if there's not also something else
<PaulFertser> Krazubu: on jtag state machine reset IDCODE instruction is autoloaded and when scanning the chain jtag compliant devices expose their JTAG TAP IDs.
<PaulFertser> Krazubu: if you get it consistently it might mean the real idcode is ver 6, that might mean it's not cortex-m3 but cortex-m4 or something like that.
<Krazubu> hmmm I suspected something like that
<Krazubu> well the datasheet reads it's a cortex m33
<PaulFertser> Krazubu: ok, that's fine
<Krazubu> the chip is an EFR32MG21, I've seen that efm32.cfg contains stuff for efr series but not this exact model, I don't know if it needs to
<Krazubu> but I get this unexpected error consistently
<PaulFertser> Krazubu: then it's ok.
Bertl_zZ is now known as Bertl
emeb has joined #openocd
Haohmaru has quit [Ping timeout: 240 seconds]
Krazubu has quit [Quit: My Mac Pro has gone to sleep. ZZZzzz…]
Krazubu has joined #openocd
Bugies has joined #openocd
Krazubu has quit [Ping timeout: 240 seconds]
nerozero has quit [Ping timeout: 268 seconds]
Hawk777 has joined #openocd
Krazubu has joined #openocd
sbach has quit [Ping timeout: 256 seconds]
gnom has quit [Quit: leaving]
gnom has joined #openocd
<karlp> is that a "series two" radio?
<karlp> like https://review.openocd.org/c/openocd/+/6173 has preliminary support for the series two parts, which are m-33
<Krazubu> hi karlp, well I know it's a m33 but no idea about the "series 2"
<karlp> it should be fairly obvious fromt he docs... it's a silabs term,
<karlp> from the name and number I'd say 99% that it's a series two radio :)
<karlp> also, I just searched "efrmg21" and the first result is "EFR32MG21 Series 2 Multiprotocol Wireless SoC"
<karlp> so yeah...
<karlp> my series there is in complete, but it might get you a loooottt closer.
<Krazubu> nice :)
<karlp> iirc, you wereonly using the efr21mg to test your tooling though? didn't you have some other target? or am I mixing you up with someone else?
<Krazubu> hmmm no I just want to talk with this one
<karlp> nvm then.
<karlp> like I said, it's not complete, but it should get you closer...
<Krazubu> btw I'm not sure I've not damaged it with my tests
<karlp> unless you're overvolting or using a hammer, it's probably fine...
<Krazubu> is it possible that I still get the TAP ID with fried TMS pin ?
gnom has quit [Quit: leaving]
gnom has joined #openocd
<PaulFertser> Krazubu: nope
<Krazubu> yesterday I swapped something, I don't really remember what, it went damn hot
<Krazubu> and I notice it's acting weird with another debugger
<Krazubu> it's an ESP32 and it won't turn on if I leave the SWDIO plugged
<Krazubu> then I tried the same with an other identical chip, it's ok
<karlp> esp32 doesn't have swd?
<Krazubu> sorry I meant esp8266
<karlp> it doesn't either?
<karlp> so that's the debugger you're using then, ok...
<karlp> not sure I follow what you mean by "another debugger" or identical chip, but whatever.
<karlp> series 2 wont' work out of the box, you need either a) my preliminary work, or b) something you cook up yourself....
<Krazubu> yeah not really clear sorry, I meant I turned to the esp with this software instead of openocd and raspberry
<karlp> right, ok, well, I have zero clue on where series two support is in black magic sorry :)
<Krazubu> and identical chip is just another EFR32
<karlp> or even efm32 in general :)
<Krazubu> yeah sure, I'm not asking for this
<karlp> ok, well, you're probably just complicating things a bit then :)
<Krazubu> I just describe what happened that makes me think I might have damaged the hardware
<karlp> you can ask the black magic people if it should work, and then just move forwrds with that?
<karlp> also, I can't/won't help you much furtehr with the code, that was a work time project for evaluating some parts, I'm not real excited about spending lots of time on it over christmas sorry
<Krazubu> sure I'm gonna have a look at it anyway
<Krazubu> I just DL em32.c, replace the original with it and recompile ?
<Krazubu> hmmm. I don't know how to use this updated code, build fails with it
<Krazubu> ok I've managed to build… now it detects DPIDR 0xdeadbeef
<Krazubu> don't know if it's good or not, guess not
<Krazubu> ok, I confirm the chip is damaged, SWD is ok with the other one
Bugies has quit [Ping timeout: 260 seconds]
emeb has quit [Quit: Leaving.]