boru has quit [Killed (NickServ (GHOST command used by boru`))]
boru` is now known as boru
tsal has joined #openocd
Hawk777 has joined #openocd
Bertl_oO is now known as Bertl_zZ
nerozero has joined #openocd
Hawk777 has quit [Quit: Leaving.]
Haohmaru has joined #openocd
<Fleck>
so, ocd supports J-link?
<boru>
Yes.
<boru>
I don't recall if there's a configuration supplied with the default install which supports jlink in swd, but it's trivial to write one.
<PaulFertser>
Default configuration is fine, no need to write any.
<boru>
The default forces jtag unless you specify otherwise though, does it not?
<PaulFertser>
Any debug adapter that supports both jtag and swd defaults to jtag, yes, but tht's not a matter of configuration file really.
<boru>
Hmm, just looking at the configuration in 0.11; has it changed? ISTR there being a `transport select jtag` in there prior. I guess you can just select swd with that configuration now then.
<PaulFertser>
Yes, but that's board configuration level.
<boru>
I'm probably misremembering.
<PaulFertser>
transport select certainly doesn't belong to an interface config.
<boru>
I suppose it should be removed from the 11 interface configurations that contain it in the default install, then.
<boru>
10, rather.
<boru>
Actually, no, 8 of them, since it's in stlink-dap.cfg three times.
<PaulFertser>
boru: it's commented out
<boru>
In that file, yeah, but not the others.
<PaulFertser>
I think those other config files are really for the interface hardware that is based on something generic enough to support jtag but implemented in a way that only SWD works.
<boru>
I see.
<PaulFertser>
E.g. ftdi/olimex-arm-jtag-swd.cfg is a special addon that you connect to an FTDI debugger (that's normally doesn't support SWD out of the box).
<boru>
Yes, seems reasonable in that case.
boru has quit []
<Fleck>
cool, I should try it! I need SWD tho
<karlp>
well, you're in luck, that works...
Bertl_zZ is now known as Bertl
JakeSays has joined #openocd
zjason has quit [*.net *.split]
HelloShitty has quit [*.net *.split]
c4017w has quit [*.net *.split]
_franck_ has quit [*.net *.split]
urja has quit [*.net *.split]
xantoz has quit [*.net *.split]
HelloShitty has joined #openocd
xantoz has joined #openocd
urja has joined #openocd
c4017w has joined #openocd
zjason has joined #openocd
_franck_ has joined #openocd
captain_morgan2 has joined #openocd
uramhoaH has joined #openocd
klys_ has joined #openocd
sud_ has joined #openocd
Haohmaru has quit [*.net *.split]
captain_morgan has quit [*.net *.split]
sud has quit [*.net *.split]
klys has quit [*.net *.split]
captain_morgan2 is now known as captain_morgan
uramhoaH is now known as Haohmaru
Haohmaru has quit [Remote host closed the connection]
jeeebz is now known as jybz
nerozero has quit [Ping timeout: 264 seconds]
<c4017w>
Any tricks to speed up incremental builds? Linking takes ~5 minutes
<karlp>
are you building on a broken nfs share?
<karlp>
touching and rebuilding here takes about 2 seconds?
<c4017w>
2 seconds to link everything?
<c4017w>
it's all on a local SSD
<c4017w>
My CPU is pegged the entire time
HelloShitty has quit [Read error: Connection reset by peer]
HelloShitty has joined #openocd
<karlp>
make -j 5 or something ,jus for starters, right? but that shouldbn't be the difference to _minutes_
<urja>
i'm thinking... lto?
<c4017w>
`make -j8`. I don't know if .configure options would have any effect? Didn't really look into what all was being linked
alefir has joined #openocd
<karlp>
make clean, time make -j1 here is ~1m34
<karlp>
remake with -j1 is 0.3seconds. touching src/target/arm* and make (j1) is still onyl 10 seconds...
<karlp>
what are you building on? what os? what version of oocd, what else is running? that definitelty soudns wildly wrong to take that long.
<c4017w>
damn, a full build took like 40 minutes last I tried
<c4017w>
Xeon E3-1240 v5, Win 10 with MinGW 64, master(ish), not much else running
<karlp>
are you actually building openocd? or are you in teh wrong channel right now? :)
<karlp>
that sounds like openwrt build times or something...