vfazio has quit [Remote host closed the connection]
Hawk777 has joined #openocd
tsal_ has joined #openocd
tsal has quit [Ping timeout: 256 seconds]
tsal_ has quit [Ping timeout: 260 seconds]
tsal has joined #openocd
gzlb has quit [Ping timeout: 264 seconds]
gzlb has joined #openocd
nerozero has joined #openocd
Hawk777 has quit [Quit: Leaving.]
urja has quit [Read error: Connection reset by peer]
urja has joined #openocd
crabbedhaloablut has quit []
crabbedhaloablut has joined #openocd
renrelkha has quit [Quit: bye]
renrelkha has joined #openocd
Hawk777 has joined #openocd
crabbedhaloablut has quit []
crabbedhaloablut has joined #openocd
nerozero has quit [Ping timeout: 256 seconds]
urja has quit [Read error: Connection reset by peer]
urja has joined #openocd
crabbedhaloablut has quit []
crabbedhaloablut has joined #openocd
lh has quit [Ping timeout: 255 seconds]
lh has joined #openocd
gzlb has quit [Ping timeout: 240 seconds]
gzlb has joined #openocd
sevan has joined #openocd
<sevan>
Hi
<PaulFertser>
Hi
<sevan>
the docs refer to a gerrit instance for submitting patches but url doesn't seem to be working
<sevan>
can I just raise a bug report on SF with the patch attached?
<PaulFertser>
Hm indeed
<sevan>
it's a trivial 1 line fix
<PaulFertser>
Let me check first
<sevan>
ah, ok :)
<PaulFertser>
sevan: weird story, Apache was OOM'd and it's just a forward proxy there... Please retry with Gerrit.
<sevan>
nice, ok :)
<sevan>
I have OpenOCD 0.12.0 built on ancient OS X (10.4 Tiger)
<PaulFertser>
How about current HEAD? ;)
<PaulFertser>
0.12.0 is old, there should be a new release soon.
<sevan>
heh
<PaulFertser>
When you send a patch to Gerrit a mail is automatically sent to the mailing list too, so it's both visible and discoverable via Internet Search.
<sevan>
ack
<sevan>
I should try, had to commit some minor bodges to get it going, can follow up with what, just in the middle of getting it to work with either stm32 boards I have
<PaulFertser>
stm32 should be easy, especially with SRST connected and "reset_config srst_only connect_assert_srst".
<sevan>
ah, I'm really a very green newcomer to openocd & I've been relying on the bundled scripts (haven't written my own ocd file)
crabbedhaloablut has quit []
<sevan>
I have a st-link v2 adapter (can't make out the model of MC) & an separate stm32-discovery board which has an stm32f100 MC
crabbedhaloablut has joined #openocd
<PaulFertser>
sevan: correct, you do not need to change the bundled scripts to use that.
<PaulFertser>
stm32f100 really? The very old discovery board with stlinkv1 ?
<sevan>
for sure, I'm just fishing out stuff from the drawer to test :)
<sevan>
bleh, paste debian net is down.
<sevan>
board/stm32vldiscovery.cfg seems to be the right config
<sevan>
(matches device id)
geep has quit [Remote host closed the connection]
lh has quit [Remote host closed the connection]
bryanb has quit [Remote host closed the connection]
<PaulFertser>
sevan: it is, just do not forget stlinkv1 is super odd, trying to pretend it's a USB mass storage device.
<sevan>
ahh
<PaulFertser>
sevan: Debug: 124 43 stlink_usb.c:3381 stlink_usb_usb_open(): claim interface failed <-- some problem on usb level, probably OSX incompatibility.
<PaulFertser>
sevan: it might be that OSX hogs it as a "storage device" at least it was the case with Linux so adding a driver quirk setting was needed.
<sevan>
well, the reason was that it did actually show up as a storage device with an html file on it
<sevan>
the file would redirect to the devices product page on the ST website
<sevan>
I wiped the firmware on this device I think & flashed it with FORTH I think. hmmm
<PaulFertser>
Yes, I see people were using a special kext to work with stlinkv1 so that's not going to be fruitful.
<PaulFertser>
That stlinkv2 clone should work, yes.
<sevan>
I think the special kext is for later OS X's?
<PaulFertser>
I have one like that repurposed as FIDO2/WebAuthn device.
<sevan>
yes
<sevan>
I repurposed a token back into a debugger (not the one I'm trying)
<PaulFertser>
sevan: you're the OS X user, not me. I suspect stlinkv1 is hogged by a kernel mass storage driver and that's why usb claim interface fails.
<PaulFertser>
But that's an educated guess, not fact.
<sevan>
for much later OS versions, I saw a kext in stlink repo as macos scsi driver would bind to the device and prevent the usb dev from attaching
<sevan>
that's the one
<PaulFertser>
If it works for "texane stlink" tool then it should help any other libusb client.
<sevan>
ack
<PaulFertser>
It talks about SIP for later versions. Doesn't mean it's not needed at all on earlier versions.
<sevan>
I'm on OS X 10.4, the kext is for macOS 10.12
<PaulFertser>
Or just use stlinkv2
<sevan>
there's no concept of SIP here, just an ancient powerpc system :)
<sevan>
yep, I'll try with the newer st-link v2 device
<PaulFertser>
OpenOCD tries hard to be compatible with Big Endian systems.
<sevan>
good stuff :)
<PaulFertser>
sevan: please feel free to ping me later, need to sleep now.
<PaulFertser>
Thanks for the report and the patch and I hope you'll have a working system really soon, you should be close now.
<sevan>
thanks for getting the gerrit service back up.
<sevan>
when I run openocd -f board/stm32f334discovery.cfg -d3 I see "Info : 128 62 stlink_usb.c:1438 stlink_usb_version(): STLINK V2J37S7 (API v2) VID:PID 0483:3748