why this is useful:
as of now i collected all information about the registers in the wiki which is "information with inconsistent markup".
every block looks a bit different, sometimes with a few spaces more or less etc.
in case we need it in machine-readable format we cannot simply parse it from the wiki.
where we need it in machine readable format:
- tools like adtg_gui that shows logs with description (as of now handcoded)
- ML firmware where we sometimes access registers in a ugly, hardcoded way. e.g. MEM(0xC0F0ABCD) = 1; better would be SIO0.TXDATA = 1
- this requires us to generate header files that define the structs and enumf and base addresses. which is an simple 1-afternoon work if we had the register map in machine readable format.
- for our emulators we use to test some new code or optimized assembly, everything related to registers is still handcraftet and error prone.
it is also part of householding. when you make your notes, you first start writing it onto a scratchpad.
later on, if the information is valuable, you try to sort, preserve and archive it so it is valuable for a longer period.
(i dont trust data that is stored in someone else's wiki)
and i am asking the community because there are so many people willing to help, but cannot because e.g. arm opcode tinkering is indeed a bit complex.
those who just want to spend 1-2 hours and do good things (and potentially learning about the backgrounds) will find this task an ideal solution.
sure, will do tonight when i am at home again. did you try it with 'mono'? should work much better.
i would say, if someone is going to start a section, just post it here. (=locking)
as soon it is finished, just edit your post
I am going to transfer "SIO"
edit: done, here the XML: