Closed flit closed 2 years ago
Updated with suggestions and items we discussed at the last partner meeting, and rebased on main
.
I don't have any strong opinions on this matter, consider it approved by IAR.
The schema and API have been updated to remove default device support.
If a partner wishes to achieve similar reusability of a plugin without code changes, the <config>
section of the manifest can be used to specify device-specific parameters.
Looks good. Just a small comment about sdmDirectoryPath.
Some small changes from yesterday based on observations as I started to update the Python based host's manifest support:
<manifest>
sub-element to the root element. Originally I had been trying to keep symmetry between the format version and API version declarations. But the format version should really be in the root, determining how all subelements are structured.<secure-debug-manager>
to <manifest>
. This prevents issues if someone decide to rename the SDM API to something less easily confused with ADAC's SDM.enable
attribute is optional.os
and arch
attributes are required.
Defined an XSD schema and DTD for the manifest XML file. The
example-manifest.xml
file was updated to match changes in the schema.There are probably some errors or mismatches between DTD/XSD/example that need to be fixed.