Content originally posted in LPCWare by MikeSimmonds on Sat Jan 31 21:56:07 MST 2015
As far as I can see, the layout and content etc. of the various debugger peripheral views are defined in files with an
extension of '.xme'. I am guessing that these are encrypted xml files.
Is there any good reason for the secrecy (given that the register descriptions etc. are plainly stated in the various
user manuals)?
In the case of mistakes, the knowledgeable users have no posibility of correcting the errors.
Some peripheral blocks are not covered at all. E.g the USB host register block (for LPC1778 at least).
It would be useful to supply un-encrypted files (and a brief format description) so that
(a) Errors and ommisions can be corrected without having to wait an unspecified amount of time for an update.
(b) A peripheral view could be tailored for a particular user's preference/way of working. [E.g. to group related
PIO registers by port rather than all ports for each register, or to put the most important (to the user) registers
at the top.
(c) [Given that a peripheral register is 'just a memory address'] Create user/project specific views of user data
structures. E.g. my UART control blocks.
If un-encrypted files are not to be forth comming, could you at least allow for user created 'extensions' to be handled
by the debugger.
Regards, Mike
