11:18 <Krazubu> hi, please could someone tell me what this error means ? http://pastie.org/p/3aNwh8Z67vkTMPV200RvSG

11:18 <Krazubu> I have communication issues but I wonder if there's not also something else

11:20 <PaulFertser> Krazubu: on jtag state machine reset IDCODE instruction is autoloaded and when scanning the chain jtag compliant devices expose their JTAG TAP IDs.

11:21 <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.

11:21 <Krazubu> hmmm I suspected something like that

11:21 <Krazubu> well the datasheet reads it's a cortex m33

11:24 <PaulFertser> Krazubu: ok, that's fine

11:24 <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

11:25 <Krazubu> but I get this unexpected error consistently

11:26 <PaulFertser> Krazubu: then it's ok.

21:04 <karlp> is that a "series two" radio?

21:05 <karlp> like https://review.openocd.org/c/openocd/+/6173 has preliminary support for the series two parts, which are m-33

21:08 <Krazubu> hi karlp, well I know it's a m33 but no idea about the "series 2"

21:11 <karlp> it should be fairly obvious fromt he docs... it's a silabs term,

21:12 <karlp> from the name and number I'd say 99% that it's a series two radio :)

21:12 <karlp> also, I just searched "efrmg21" and the first result is "EFR32MG21 Series 2 Multiprotocol Wireless SoC"

21:12 <karlp> so yeah...

21:12 <karlp> my series there is in complete, but it might get you a loooottt closer.

21:13 <Krazubu> nice :)

21:13 <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?

21:14 <Krazubu> hmmm no I just want to talk with this one

21:14 <karlp> nvm then.

21:14 <karlp> like I said, it's not complete, but it should get you closer...

21:14 <Krazubu> btw I'm not sure I've not damaged it with my tests

21:14 <karlp> unless you're overvolting or using a hammer, it's probably fine...

21:15 <Krazubu> is it possible that I still get the TAP ID with fried TMS pin ?

21:17 <PaulFertser> Krazubu: nope

21:17 <Krazubu> yesterday I swapped something, I don't really remember what, it went damn hot

21:17 <Krazubu> and I notice it's acting weird with another debugger

21:18 <Krazubu> it's an ESP32 and it won't turn on if I leave the SWDIO plugged

21:19 <Krazubu> then I tried the same with an other identical chip, it's ok

21:19 <karlp> esp32 doesn't have swd?

21:19 <Krazubu> sorry I meant esp8266

21:19 <karlp> it doesn't either?

21:20 <Krazubu> using this https://github.com/MattWestb/blackmagic-espidf

21:21 <karlp> so that's the debugger you're using then, ok...

21:21 <karlp> not sure I follow what you mean by "another debugger" or identical chip, but whatever.

21:22 <karlp> series 2 wont' work out of the box, you need either a) my preliminary work, or b) something you cook up yourself....

21:22 <Krazubu> yeah not really clear sorry, I meant I turned to the esp with this software instead of openocd and raspberry

21:23 <karlp> right, ok, well, I have zero clue on where series two support is in black magic sorry :)

21:23 <Krazubu> and identical chip is just another EFR32

21:23 <karlp> or even efm32 in general :)

21:23 <Krazubu> yeah sure, I'm not asking for this

21:23 <karlp> ok, well, you're probably just complicating things a bit then :)

21:23 <Krazubu> I just describe what happened that makes me think I might have damaged the hardware

21:23 <karlp> you can ask the black magic people if it should work, and then just move forwrds with that?

21:24 <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

21:24 <Krazubu> sure I'm gonna have a look at it anyway

21:25 <Krazubu> I just DL em32.c, replace the original with it and recompile ?

21:57 <Krazubu> hmmm. I don't know how to use this updated code, build fails with it

23:04 <Krazubu> ok I've managed to build… now it detects DPIDR 0xdeadbeef

23:05 <Krazubu> don't know if it's good or not, guess not

23:21 <Krazubu> ok, I confirm the chip is damaged, SWD is ok with the other one