NishanthMenon changed the topic of #openocd to: this is the place to discuss all things OpenOCD | Logs: https://libera.irclog.whitequark.org/openocd/
ahorvat has quit [Ping timeout: 256 seconds]
crabbedhaloablut has quit [Ping timeout: 245 seconds]
noarb has quit [Quit: ZNC 1.8.2 - https://znc.in]
noarb has joined #openocd
noarb has quit [Quit: ZNC 1.8.2 - https://znc.in]
noarb has joined #openocd
vampirefrog has quit [Remote host closed the connection]
nerozero has joined #openocd
IoT-Maker has joined #openocd
vampirefrog has joined #openocd
bvernoux has joined #openocd
MGF_Fabio has joined #openocd
csanchezdll has joined #openocd
<csanchezdll> good day all!
<csanchezdll> quick question about gerrit process: after my contribution review iterations are done and upvotes are in, I guess I am not supposed to do anything else, right? The "submit" button is greyed out for me so my understanding is the actual merge is done by some project admin
<csanchezdll> asking because I received a notification as if action was needed from my side after last upvote, but AFAIU there is nothing else I can/have to do
<Hawk777> Yes, someone with proper permissions does the merge, I believe generally after someone with the ability to write a “+2” review has done so.
Hawk777 has quit [Quit: Leaving.]
<csanchezdll> The +2 is already there, hence my question. No hurries, I just wanted to confirm there's nothing else I have to do.
<csanchezdll> Thanks!
<karlp> which item? normally plus two's ar emerged minutes later, it's normally a merger giving them the second ...
<karlp> 8012 I guess?
<karlp> thomas might have been busy and meant to come back to it with some other merges?
<karlp> does https://review.openocd.org/c/openocd/+/8012/8/tcl/target/s32k.cfg#49 apply to s32 as well? or was that carried over from a kinetis target file?
<csanchezdll> karlp: yup that is the isue
crabbedhaloablut has joined #openocd
<csanchezdll> s32k.cfg is also part of the patchset. It is the file you use to actually connect to a s32k1xx evb or simple board. It is heavily based on kx.cfg, as the file header states
MGF_Fabio has quit [Ping timeout: 255 seconds]
<csanchezdll> I did not know what the process was, that's why I asked. Gerrit says "your turn" like implying I had something to do, but I guess that is an artifact of Thomas issuing the +2 vote
<csanchezdll> as I said, no hurries, I can wait until he is ready. As you say, he might want to merge something else before this
<karlp> yeah, no I meant, in that file, the warning you print about kinetis and mdm-ap, is taht also applicable to s32?
MGF_Fabio has joined #openocd
<csanchezdll> the MCU has the MDM-AP, so my understanding is it applies. It is very similar HW to Kinetis series, really. I have not tested with stlink, only with Jlink, so I cannot be 100% sure, but my understanding is it applies
<csanchezdll> kx.cfg had this logic in, so I kept it
<csanchezdll> I mean, the same code from kinetis.c is used, so if stlink cannot access it in kx.cfg case, the same is true here
<csanchezdll> and mdm commands do work, that I have tested
<borneoa___> csanchezdll: usually we let the patch stay in Gerrit for 1~2 weeks in case some other reviewer want to adds comments or additional vote, then it get merged. But the process is not automatic so it can happen something get lost; in that case a message in IRC or in mailing-list can be a helpful reminder
<csanchezdll> borneoa___: perfect, I will wait then :) I will ping again if it is still there in 2 weeks
slobodan has joined #openocd
bvernoux has quit [Quit: Leaving]
merethan has joined #openocd
ahorvat has joined #openocd
bvernoux has joined #openocd
slobodan has quit [Read error: Connection reset by peer]
slobodan has joined #openocd
csanchezdll has quit [Quit: leaving]
merethan has quit [Quit: Leaving]
IoT_Maker has joined #openocd
IoT-Maker has quit [Ping timeout: 252 seconds]
Hawk777 has joined #openocd
nerozero has quit [Ping timeout: 256 seconds]
shibboleth has joined #openocd
shibboleth has quit [Remote host closed the connection]
shibboleth has joined #openocd
shibboleth has quit [Remote host closed the connection]
shibboleth has joined #openocd
slobodan has quit [Ping timeout: 252 seconds]
ahorvat has quit [Ping timeout: 264 seconds]
IoT_Maker has quit [Ping timeout: 246 seconds]
bvernoux has quit [Quit: Leaving]
MGF_Fabio has quit [Ping timeout: 255 seconds]
shibboleth has quit [Quit: shibboleth]
<karlp> maybe someone here knows, if you have an ft2232h type dongle, it needs a "resistor hack" to do SWD, but can yuou then use it to capture SWO as well? or do you have to use the other channel for that?
<karlp> I'm hoping for a setup that only uses one 2x5x1.27mm pitch connector, and can do jtag _and_ swd+swo capture.
<karlp> (I know orbtrace is one of those, I'm just being too cheap to buy a second one)
<PaulFertser> karlp: SWO capture on another channel
<PaulFertser> karlp: also, you can go without resistor if you have bare ftdi chip, the current version turns off the driver.
<karlp> yeah, if it's another channel, it ends up on a different header at that point.
<karlp> was looking at this one as a readilyh available, cheap, ft2232h, https://docs.espressif.com/projects/espressif-esp-dev-kits/en/latest/other/esp-prog/user_guide.html
<karlp> but the appeal is having _one_ 2x5x1.27mm cable, not spaghetti
<PaulFertser> Why not route the UART Rx of the second interface of ft2232h to the same connector?
<karlp> but that's excellent to know though, I could just use that esp-prog as a plain jtag _and_ swd dongle,
<karlp> because I don't want to build my own ft2232h dongle?
<PaulFertser> karlp: or by other channel you mean another chip?
<karlp> no, I mean, like ft2232h has these two "channels" right?
<PaulFertser> Yes, they call them Interface A and B.
<PaulFertser> Or something
<karlp> right.
<karlp> so, with swd on a ftdi, you use tms, tck and ... tdi? or tdo?
<karlp> tdo normally is what's muxed with swo isn't t?
<PaulFertser> Yes, you use both TDI and TDO for that trick.
<karlp> but either way, if you need to go to the other "interface" it doesn't matter, none of these ft2232h dongles are setup for using two channels to make _one_ swd+jtag+swo interface.
<karlp> so, you can do sw_d_ with a plain ft2232h dongle? or does it need the resistor between the two?
<PaulFertser> But probably you can just manually add a wire to bridge the Rx to unused pin on jtag header?
<PaulFertser> If you have no buffers then you can just short TDO and TDI with current version, yes.
<karlp> and if you have buffers?
<karlp> oh, and you still need to short them when you want swd?
<karlp> and not short them for jtag?
<PaulFertser> Yes
<karlp> yeah, ok, so ft2232h based dongles are still .... "sub optimal" then :)
<karlp> I think I should stop looking at them.
<PaulFertser> SWD is implemented by sending on TDI and receiving on TDO
<karlp> tigard looks like it works, has a hardswitch to do swd vs jtag.
<karlp> but it's $50 plus shipping,
<PaulFertser> Well there're proper devices like BusBlaster with CPLD for buffering.
<PaulFertser> It's properly switching between JTAG and SWD modes.
<karlp> at that price I'd rather just get a second orbtrace.
<karlp> busblaster can't do swo though right?
<PaulFertser> I didn't check that, can't tell.
<PaulFertser> I wonder if stlinkv3 reflashed to cmsis-dap is sane.
<karlp> you can reflash stlinkv3?
<karlp> that's... not an option I was aware of.
<karlp> lol, clicked link on dangerous prototypes for busblaster to buy, -> blocked for security reasons...
<karlp> ok, busblasterv4 says it supports swv, but it's unavailable, no stock, no estimated delivery.
<karlp> 4 years ago? has sstlinkv3 been aroudn that old?
<karlp> holllly shit.
<PaulFertser> Times flies by
<PaulFertser> :/
<karlp> ok, v3mini is... interesting option at this point.
<karlp> I'm also looking at a renesas dev board with an onboard jlink ob that supports offboard connections.
<karlp> usb-hs. 13€ on mouser, cmsis-dap. supports swd, jtag, and swo...
<karlp> actually, no. it .. doesn't do jtag? cute.
noarb has quit [Ping timeout: 245 seconds]
<karlp> well, schematic implies it probably actrually works just fine for jtag...
<karlp> think I'll get one :)
noarb has joined #openocd