NishanthMenon changed the topic of #openocd to: this is the place to discuss all things OpenOCD | Logs: https://libera.irclog.whitequark.org/openocd/
JTAGnuub has joined #openocd
<JTAGnuub> hello is anyone there that can help me with a cisco MR18 JTAG hacking quest?
<JTAGnuub> hello?
<JTAGnuub> echo
<jn> hey, be patient!
<jn> JTAGnuub: welcome to IRC, where people take a while to respond because they might live in another timezone :)
<jn> JTAGnuub: anyway, what's your request?
JTAGnuub has quit [Quit: Client closed]
renrelkha has quit [Ping timeout: 260 seconds]
renrelkha has joined #openocd
olerem has joined #openocd
Hawk777 has joined #openocd
olerem has quit [Ping timeout: 260 seconds]
JakeSays_ is now known as JakeSays
nerozero has joined #openocd
MGF_Fabio has joined #openocd
olerem has joined #openocd
Hawk777 has quit [Quit: Leaving.]
olerem has quit [Ping timeout: 268 seconds]
gzlb has quit [Ping timeout: 240 seconds]
gzlb has joined #openocd
Haohmaru has joined #openocd
JakeSays has quit [Remote host closed the connection]
JakeSays has joined #openocd
olerem has joined #openocd
olerem has quit [Quit: WeeChat 3.8]
olerem has joined #openocd
defiant has joined #openocd
crabbedhaloablut has quit []
crabbedhaloablut has joined #openocd
defiant has quit [Quit: defiant]
JTAGnuub has joined #openocd
<JTAGnuub> sry im pretty new to all this
<PaulFertser> JTAGnuub: hi
<PaulFertser> JTAGnuub: you connected and then disconnected right away.
<PaulFertser> JTAGnuub: this makes no sense as you won't see the reply if you're not connected.
<PaulFertser> JTAGnuub: so, what's the question about MR18? I developed that procedure few years ago.
soundfox1 has quit [Read error: Connection reset by peer]
soundfox has quit [Read error: Connection reset by peer]
Haohmaru has quit [Quit: saionara]
MGF_Fabio has quit [Ping timeout: 256 seconds]
Hawk777 has joined #openocd
<JTAGnuub> I basically keep getting an error while trying the MR18 method with a Ras Pi 1 where I can halt the device, but the config file appears to have deprecated stuff, and also It seems always to show "Failed to Enter Debug Mode". Was just hoping to get some advice on why that may be happening
<PaulFertser> JTAGnuub: you need to use some pastebin to show full output from OpenOCD and all your additional files.
<JTAGnuub> Ok, I will do it next week sometime, traveling the rest of the week now.
<PaulFertser> JTAGnuub: where did you get config file from and what did you change in it?
<PaulFertser> JTAGnuub: also how come you can halt the device but at the same time you say it fails to enter debug mode? At what point?
nerozero has quit [Ping timeout: 268 seconds]
JTAGnuub has quit [Quit: Client closed]
slobodan has joined #openocd
<NishanthMenon> at the risk of self promotion, but more on the interest of "if anyone in EOSS, seattle next week wants to talk OpenOCD, lets get together" https://sched.co/1aBGL -> I will be talking OpenOCD recently added dmem support a bit.. if anyone wants to sync up, lets do it..
<NishanthMenon> my slides should be online atm..
<PaulFertser> Promotions like that are always good!
<NishanthMenon> yup.. I hope we see more OpenOCD talks.. but anyways.. threw it in there..
<NishanthMenon> thank you all for the help and guidance (again)..
<PaulFertser> Yeah, the slides are there.
<PaulFertser> NishanthMenon: may I make a suggestion about the config.gz line?
<NishanthMenon> Paul, sure
<PaulFertser> NishanthMenon: zgrep /proc/config.gz DEVMEM
slobodan_ has joined #openocd
<NishanthMenon> sure, will update. thank you. I was a bit distracted when I copy pasted from history to slide " cat /proc/config.gz |gunzip|grep DEV|grep MEM"
<NishanthMenon> just need to see if zgrep was installed by default in beagleboard.org minimal images..
<PaulFertser> First I thought why gunzip when you could have used zcat. Then I saw it pipes into grep, so there's zgrep. Then I saw it filters for something unrelated so includes a V4L option where MEM comes before DEV.
<NishanthMenon> yep..
<NishanthMenon> thanks for catching it.. :)
slobodan has quit [Ping timeout: 252 seconds]
<PaulFertser> NishanthMenon: I wonder if you normally need mem.devmem=1 kernel parameter too.
<PaulFertser> And hm, probably STRICT_DEVMEM doesn't actually prevent access to MMIO peripherals on Arm.
<NishanthMenon> I am not sure, actually - had'nt dug deeper.. However, i know this: autosd from fedora for Arm64 did'nt work out of box (and i went searching why) Vs debian build from beagleboard.org just worked..
<NishanthMenon> s/fedora/redhat/
<PaulFertser> ./bootstrap should automatically fetch submodules
<NishanthMenon> aah ok
<PaulFertser> And /usr/local is default prefix anyway.
<NishanthMenon> ok
<PaulFertser> Do you actually mind all this nitpicking probably?
<NishanthMenon> i always love it :)
<NishanthMenon> thank you once again.. you know the effect that one cant see one's own little things.. so it helps.. (i also was organizing booth and working on another paper at the same time.. so probably could have done better..)
<PaulFertser> The next one is that it was installed already to /usr/local/bin so it should be just "sudo openocd" since you count on it using the installed configs anyway.
<NishanthMenon> aarghh.. ofcourse :)
<PaulFertser> Sure, it's really hard to proofread one's own work.
<PaulFertser> And then you do not need ./ before board/ti...
<NishanthMenon> ack
<PaulFertser> Talking about the DAP ROM table, glad to see TI parts finally started to have it :)
<NishanthMenon> hehe - yeah - we have been verifying it during presilicon as well - except for one little crap.. i think it tends to come out fine.. the problem i have is that ROM entries are integrated at subsystem level, so if the power domain is down, you dont see the ROM entry (as the bus segment will be down). kinda irritating when you want a complete dump of the full SoC.. but you only get the segments that have been powered on..
<NishanthMenon> but meh, anything is better than crappy or no data..
<PaulFertser> Indeed
<PaulFertser> Yes, OpenOCD had some rudimentary trace buffer support but that was even before Cortex.
<NishanthMenon> yeah - i have'nt had time to dig at CTI and ETB implementations in OpenOCD.. hoping to take it some day if time permits
<PaulFertser> NishanthMenon: CTI is obviously there for aarch64 breakpoints to work. But ETB just not implemented anyhow if you do not count rudimentary ARM9 stuff.
<NishanthMenon> aah ok - i didn't know that.
<PaulFertser> NishanthMenon: I'm not sure about the target audience there, I would probably consider an overview slide about why one might need to debug M4 or R5 cores there at all. And I'm not sure if I get it right but normally they only run code supplied to them from Linux by remoteproc, right? How would that play along with debugging and could one upload new code with "load" in GDB?
<PaulFertser> BTW, why do you need to set architecture explicitly for gdb-multiarch, isn't it getting it right from the XML file while negotiating with OpenOCD?
<PaulFertser> Thank you so much about all you kind words and endorsements for OpenOCD community, really appreciated.
<NishanthMenon> yeah - I did do a different session for R5 and m4f debug :( -> trouble was trying to figure out what depth do we go.. for gdb-multi-arch - you are right, i dont need to set arch specifically.. but with everything else I do (pattern of which u noticed above) - i like to do things redundantly to make sure I recollect what the heck was happeneing.. just an overkill - i will add a note. thanks for noticing it
<NishanthMenon> in terms of endorsement - that is the very least I can do.. you guys really rock.. I do enjoy just hanging around and catching up every morning.. always something new to learn :)
<PaulFertser> It's just that the more info on slides the harder to read them, especially from a distance. OTOH it's good to have extra hints when reviewing the slides later on a computer.
<NishanthMenon> hmmm... true..
<NishanthMenon> let me try and take your feedback in tomorrow morning and see if i can move more stuff to backup slides.. i did have a feel it was a bunch of busy slides.. but i will make an effort.. thanks for suggesting, Paul.
<PaulFertser> I wonder where does ITM from M4 go.
<NishanthMenon> there is a trace funnel path
<PaulFertser> And how to get data from it? I am just curious.
<NishanthMenon> i have'nt dug into that either.. the trace path itself is a deep area as well - TRM seems to have some details on it.. on lauterbach at least (native), I had itm data stream out per channel..
<NishanthMenon> i have'nt tried that on OpenOCD.. :(
<PaulFertser> I think it wouldn't hurt to add a slide or two with a quick mention something like "typically the R core is running a RTOS to provide guaranteed timely response to external events; and M4 is used for (idk, talking to power controller of motherboard?)" We also saw people (ab)using them for crazy stuff like (something unorthodox).
<PaulFertser> Something to make people think that debugging those cores is not only fun but also useful :)
<NishanthMenon> Thanks Paul - Good point, yeah makes sense.. let me get that in as well..
<PaulFertser> I have a similar "meme" picture for my linkedin profile :)
<PaulFertser> I'd also mention watchpoints in addition to breakpoints. They're so nice especially on a controller without MPU when one task corrupts another.
slobodan_ has quit [Ping timeout: 252 seconds]
Hawk777 has quit [Quit: Leaving.]