NishanthMenon changed the topic of #openocd to: this is the place to discuss all things OpenOCD | Logs: https://libera.irclog.whitequark.org/openocd/
tsal has quit [Ping timeout: 245 seconds]
tsal has joined #openocd
tsal has quit [Ping timeout: 272 seconds]
tsal has joined #openocd
tsal has quit [Ping timeout: 252 seconds]
tsal has joined #openocd
Hawk777 has joined #openocd
<zapb_> PaulFertser, thanks!
nerozero has joined #openocd
Haohmaru has joined #openocd
mcf has joined #openocd
alkane has quit [Ping timeout: 276 seconds]
alkane has joined #openocd
Hawk777 has quit [Quit: Leaving.]
<Hammdist> are 2x7 JTAG cable connectors in any way keyed for polarity?
<Hammdist> that is, it seems not so to me if I were to just put a 2x7 grid of square pins on the pcb, nothing would prevent it being connected the wrong way around
<jeanthomas> Hammdist: I often see boards with keyed IDC connectors instead of simple headers
Guest98 has joined #openocd
<Guest98> HI all,
<Guest98> Is it possible to ask here and get some help regarding OpenOCD setup for RiscV CPU. What I am using is RTL simulation via JTAG and on TB side I have JTAG VPI instantiated in UVM environment.
<Guest98> Now I am facing some issues and help would be good in case someone has experience in that ?
<Guest98> Thanks,
Guest98 has quit [Quit: Client closed]
Guest98 has joined #openocd
nashpa has quit [Ping timeout: 260 seconds]
dliviu has joined #openocd
<PaulFertser> Guest98: hey. It's ok to ask here but probably your question is a rather hard one. What exactly is the issue you see?
<PaulFertser> Hammdist: 2x7 sounds like EJTAG so it must be MIPS you're working with?
<PaulFertser> Hammdist: square pins means SMT but SMT IDC sockets are keyed too.
<PaulFertser> I misread pins for pads because I thought you're talking about PCB itself. So not necessarily SMT.
<PaulFertser> Reverse connection polarity is safe with a reasonable JTAG adapter anyway.
dliviu has quit [Ping timeout: 244 seconds]
dliviu has joined #openocd
Guest98 has quit [*.net *.split]
dliviu has quit [Ping timeout: 272 seconds]
dliviu has joined #openocd
Deneb^ has joined #openocd
JoseT has joined #openocd
<JoseT> Hi, I have an issue in getting device halted with TI CC2340R5. I am using VS Code and OpenoCD.
<JoseT> Run to Main works fine, device get halted in main. But after run is issued from main, device is not getting halted. I am seeing the below error message,
<JoseT> Info : [cc2340r5.cpu] external reset detected
<JoseT> Info : The target is not running when halt was requested, stopping GDB.
<JoseT> Error: [cc2340r5.cpu] not halted (gdb fileio)
<JoseT> I tried to print the target state and I can see that OpenOCD is assuming target is in TARGET_RESET state. But from led blinking its clear that fw is running. Checking further showed that RESET,RETIRE bits in dhcsr register is set.
<JoseT> Info : cortex_m->dcb_dhcsr_cumulated_sticky 0x3070003, cortex_m->dcb_dhcsr 0x3040001
<JoseT> However, no reset has actually happened.
<JoseT> I would highly appreciate if anyone can explain whats happening or directions on how to resolve this.
<JoseT> Thanks in advance.
Deneb^ has quit [Quit: Leaving]
<Haohmaru> JoseT, what debugger are you using?
<Haohmaru> could it be that your debugger is not actually seeing the RESET signal
<JoseT> I am using XDS110. You mean RESET from device?
<Haohmaru> no idea what that is, but typically i think the debugger/openocd wants to see/control the RESET
<Haohmaru> at least in my experience ;P~
<Haohmaru> to say it another way, are your connections "proper" ;P~
<JoseT> Issue is not happening with all firmwares. Unfortunately I cant figure out exact difference between firmwares, but could be related to sleep. Some firmwares are working absolutely fine.
<JoseT> My connections are proper as far as I checked
<Haohmaru> ah, so you're doing the same thing on multiple "same" devices, and this only happens on some of them?
<JoseT> Not multiple devices. Single device, proble with some firmwares
<Haohmaru> can a firmware disable some debugging-related things like RESET or what not
<Haohmaru> but you probably wanna wait for someone more familiar with that stuff than me
<PaulFertser> JoseT: I'd step through main to see what exactly makes it behave like that.
<PaulFertser> JoseT: guess it's some internal hardware getting reconfigured in a way that's confusing.
<PaulFertser> JoseT: also I can imagine it getting reset and then run and if you judge just by the blink you can not know if it was reset or not.
Haohmaru has quit [Quit: saionara]
<JoseT> Yes that make sense. so you are suspecting likely there is a reset happening internally which is making debugger loose connection ? I can check that. My dissassembly is also not getting loaded, I dont have source code but i can try to get that.
<JoseT> PaulFertser, I will be able to continue tomorrow and give an update. thanks
JoseT has quit [Quit: Client closed]
Hammdist88 has joined #openocd
BuldiBaerBeer has joined #openocd
gpol has quit [Ping timeout: 260 seconds]
gpol has joined #openocd
nerozero has quit [Ping timeout: 272 seconds]
Hammdist88 has quit [Quit: Client closed]
Hammdist1 has joined #openocd
Hammdist1 has quit [Quit: Client closed]
BuldiBaerBeer has quit [Quit: Leaving]
noarb has quit [Ping timeout: 276 seconds]
noarb has joined #openocd