<Fist0urs>
Info : DEPRECATED target event trace-config; use TPIU events {pre,post}-{enable,disable}
<Fist0urs>
srst_only separate srst_nogate srst_open_drain connect_assert_srst
<Fist0urs>
I guess options in the .cfg are not good, any clue where to search in openocd source code/documentation to fix this? :)
<PaulFertser>
Fist0urs: hi
<PaulFertser>
Fist0urs: why isn't that adapter config submitted to upstream?
<PaulFertser>
Fist0urs: sure you should just read the OpenOCD User Guide where all of those events and options are documented.
<PaulFertser>
Fist0urs: is there anything unclear about the guide's contents?
<Fist0urs>
<PaulFertser> Fist0urs: why isn't that adapter config submitted to upstream? // I don't know, maybe because it is using the buspirate configuration so this would be redundant? If you feel the hydrabus devs should PR in openocd with this cfg I can tell them if you want
<Fist0urs>
<PaulFertser> Fist0urs: sure you should just read the OpenOCD User Guide where all of those events and options are documented. // seems I haven't rtfm enough, I'll give it another try and if something is still unclear I'll get back here
<Fist0urs>
thx!
<PaulFertser>
Fist0urs: please ask if you have any issues
<Fist0urs>
thx :)
<PaulFertser>
Fist0urs: btw, I recommend to always use _online_ documentation which means the files that were installed to your computer along with the application binary you're using.
<Fist0urs>
ok
<PaulFertser>
Fist0urs: btw, make sure you use target config that came with your binary. I think the error message suggests you're doing something else.
<PaulFertser>
(because the hydrabus config doesn't have any trace-config)
<Fist0urs>
I've used openocd from the git and compiled it, so I guess I have the up to date target (?)
<PaulFertser>
Fist0urs: should be so, but probably it picks configs from somewhere else too? Check -d3 output, you'll see where it gets all the files from.
<PaulFertser>
Or probably some config wasn't updated.
<Fist0urs>
I've put absolute file path to be sure :p
<Fist0urs>
(I tried the -d and it finds them)
<PaulFertser>
Fist0urs: indeed, trace-config is present in upstream target configs.
<PaulFertser>
Fist0urs: you can just ignore the warning.
<Fist0urs>
ok thx!
The_Jag has joined #openocd
The_Jag has quit [Client Quit]
The_Jag has joined #openocd
The_Jag has quit [Client Quit]
The_Jag has joined #openocd
The_Jag has quit [Client Quit]
The_Jag has joined #openocd
The_Jag has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<borneoa_>
Hmmm.... trace-config in upstream configs.... I will check
Bertl is now known as Bertl_oO
<PaulFertser>
borneoa_: thank you!
diddly has quit [Read error: Connection reset by peer]
diddly has joined #openocd
nerozero has quit [Ping timeout: 268 seconds]
Haohmaru has quit []
diddly has quit [Read error: Connection reset by peer]
emeb has joined #openocd
diddly has joined #openocd
tarekb has quit [Quit: Leaving.]
Slide-O-Mix has joined #openocd
<Slide-O-Mix>
Is there a way to use an AXI MEM-AP in OpenOCD? I was looking at the commands available and didn't see anything. I could be completely blind though, its been a rough day :D
<Slide-O-Mix>
ARM AXI MEM-AP
<PaulFertser>
Slide-O-Mix: try searching on Gerrit for message:axi
<Slide-O-Mix>
thanks
<Slide-O-Mix>
ok, it looks more simple than I was expecting thanks for the pointer