NishanthMenon changed the topic of #openocd to: this is the place to discuss all things OpenOCD | Logs: https://libera.irclog.whitequark.org/openocd/
boru` has joined #openocd
boru has quit [Killed (NickServ (GHOST command used by boru`))]
boru` is now known as boru
thinkfat_ has joined #openocd
thinkfat has quit [Ping timeout: 252 seconds]
tsal has quit [Ping timeout: 252 seconds]
tsal has joined #openocd
dliviu has quit [Quit: Going away]
dliviu has joined #openocd
borneoa_ has joined #openocd
<antto> anyone wanna suggest a few arm cortex chips/series to fiddle with their SVDs
<Steffanx> Samd
<antto> i am already mainly testing with same54 (where samd51 is on the same datasheet)
<antto> do you mean the samd2x (that seems to be used in some crapdiuno)?
<antto> i tried some big-ish GD32, and a big-ish stm32f4.. the stm32 makes my parser abort
<antto> both stm32 and gd32 .svd files contain pesky multi-line <description> elements, but i solved that
<clever> antto: dual cortex m0+, 125mhz, 264kb of ram, SWD, $4 on a board: https://www.sparkfun.com/products/17829
<antto> let's see
<antto> okay, this one is "interesting"
<clever> how so?
<antto> my parser throws warnings about an unknown element bitRange, many many many places
<clever> ah
<antto> and then it also errors out during processing like with the stm32
<clever> <bitRange>[3:3]</bitRange>
<clever> looks like a lot of fields within a register are tagged like this
<antto> i don't think i've seen that in the SVD docs
<clever> and on this subject, are there any good tools to convert SVG into decent looking docs?
<antto> oh, it's there, i haven't implemented it yet
<antto> no idea
<antto> what kind of docs?
<clever> like what you would find in a datasheet
<antto> datasheets typically have lots of explanations and sh*t
<antto> .svd is mostly data with some short descriptions
<clever> currently ive just been writing .md files
<clever> but having it in svd form would be nice
<clever> antto: and the rp2040, has a 6 line <description> on nearly every field
<antto> i know from .svd you could generate device headers, schematic symbols
<antto> true
<clever> antto: oh, and check out the picoreg tool in this post
<clever> its a full gui, to browse every register, see the docs for each, and you can click a button to read/write it over SWD
<clever> and it decodes the sub-fields within a reg
<antto> i mean, i'm currently generating the whole thing as a single .hpp file, so you can see it all there
<antto> btw, why .md?
<clever> mostly to make it look pretty on the github ui
<clever> but i have been wanting something that converts to pdf, and looks like a proper datasheet
<antto> how about asciidoc
<clever> antto: this is most of what my headers look like, they came like this in the original broadcom header release
<clever> for each field, the bit range is defined twice, once as seperate start/stop values, then again as a single 29:27 value
<clever> and then as bit masks
<clever> so reg = reg & GP_FSEL0_FSEL09_CLR; will clear the FSEL09 field
<antto> i recently rewrote one of my user manuals with asciidoc so i can have both an online .html version and also a .pdf
<clever> `reg | (n << GP_FSEL0_FSEL09_LSB)` will set it (but not enforce the set bits)
<antto> it's like markdown but more powerful
<clever> and `(reg & GP_FSEL0_FSEL09_SET) >> GP_FSEL0_FSEL09_LSB` can read
<clever> i'll have to look into it
<clever> the official docs from RPF also made the switch to asciidoc recently
<clever> and in the process, they broke every single URL into the docs
<clever> and then just went E_WONT_FIX
<antto> urls inside docs are like <<some_name, optional text here>>
<antto> ..in asciidoc
<clever> the problem, is links to the docs on the forums, and other 3rd party sites
<antto> oh
<antto> no idea
<clever> they restructured the whole doc layout, and broke all of those
<antto> yeah, my rewritten user manually is not 100% compatible with the old one (which is html-only)
<clever> and its 5am, i should get some sleep
zjason` is now known as zjason
wolfshappen has quit [Quit: later]
nerozero has joined #openocd
<olerem> borneoa_: hi, so what do we do with the vdebug? there is no sence to hold it without requesting any changes
wolfshappen has joined #openocd
wolfshappen has quit [Ping timeout: 252 seconds]
wolfshappen has joined #openocd
<borneoa_> olerem: hi. Please hold on. I want to review it. Sorry I had a bad week and I could not focus on openocd.
<PaulFertser> Hi borneoa_ :) anything I can do to make your week a little bit better?
<borneoa_> PaulFertser: hi. It's some family problem that is talking all my time. Thanks, anyway :)
emeb has joined #openocd
<olerem> borneoa_: in case it will make you feel better - you are not alone.. :)
nerozero has quit [Ping timeout: 260 seconds]
sbach has quit [Read error: Connection reset by peer]
sbach has joined #openocd
PaulFertser has quit [Ping timeout: 260 seconds]
PaulFertser has joined #openocd
crabbedhaloablut has quit [Write error: Connection reset by peer]
cp- has quit [Read error: Connection reset by peer]