en-sc has quit [Remote host closed the connection]
Hawk777 has quit [Quit: Leaving.]
lxsameer has joined #openocd
Foxyloxy has quit [Read error: Connection reset by peer]
<gamiee>
Hi, well, I am dealing with something very strange... again. After reset, when JTAG chain examination is being done, the ID code returned by chip is good. But after just resetting OpenOCD, when the JTAG chain examination runs again... The IDcode is different. Any ideas what this could be?
<antto>
is it FF or 00?
<gamiee>
Instead of 0x10000B6F, it's 0x04400000000
<gamiee>
although, during scan, I notice that there is no IR update
<PaulFertser>
gamiee: yes, after JTAG state machine reset the standard says IR should be pre-loaded with IDCODE instruction.
<gamiee>
PaulFertser: it seems on T-Head cores this is not case. Else I do not know how to explain current behavior
<PaulFertser>
gamiee: sometimes vendors do very odd things
<PaulFertser>
gamiee: is it the same for you both with and without physical TRST?
<gamiee>
PaulFertser: The chip (BL618) does not support physical TRST
<PaulFertser>
OK
<PaulFertser>
So OpenOCD should be doing TestLogicReset state transition then reading DR should be giving IDCODE if the hardware is sane.
<gamiee>
I see OpenOCD is triggering TestLogicReset. But, hardware is not outputting the IDcode, but some garbage. (I am checking this with logic analyzer)