In Eclipse IDE with CMSIS-Zone plugin installed:
- Select File → New → Project... → CMSIS → CMSIS-Zone Project
- Set the project name in "Project name"
- Select "Select device to ..." and select an existing device, for example: an ARMCM33 device.
After the above steps, the following errors occur:
Processor description: missing or invalid DnumInterrupts attribute for TrustZone device
Processor description: missing or invalid DnumSauRegions attribute for TrustZone device
These errors are described in the CMSIS-Zone documentation:
https://arm-software.github.io/CMSIS-Zone/latest/ErrorMessages.html
After supplying the missing information on how many Interrupts and how many SAU regions there are for the selected device in the respective .rzone file, the errors disappear.
This is not a particularly nice user experience. It would be perhaps better if the DnumInterrupts and DnumSauRegions attributes were already set in the .rzone file for such devices, e.g., to whatever the default behaviour is for the device, or provide a less scary-looking message, e.g., a remark that recommends setting these attributes appropriately. The documentation could also be updated to explain what these attributes should be set to and how they are mapped in terms of automatic code generation.
In Eclipse IDE with CMSIS-Zone plugin installed:
After the above steps, the following errors occur:
These errors are described in the CMSIS-Zone documentation:
https://arm-software.github.io/CMSIS-Zone/latest/ErrorMessages.html
After supplying the missing information on how many Interrupts and how many SAU regions there are for the selected device in the respective .rzone file, the errors disappear.
This is not a particularly nice user experience. It would be perhaps better if the DnumInterrupts and DnumSauRegions attributes were already set in the .rzone file for such devices, e.g., to whatever the default behaviour is for the device, or provide a less scary-looking message, e.g., a remark that recommends setting these attributes appropriately. The documentation could also be updated to explain what these attributes should be set to and how they are mapped in terms of automatic code generation.