cancel
Showing results for 
Search instead for 
Did you mean: 

PDSC schema issues when downloading CMSIS 5.7.0 in STM32CubeMX 5.6.1

kj.obara
Associate III

 Hi,

I've recently started using STM32CubeMX and I tried installing newest Arm CMSIS 5.7.0, but whenever I do that I get the following error.

 Errors: 
 
 - Ërror: Line= 633 : cvc-enumeration-valid: Value 'Cortex-M55' is not facet-valid with respect to enumeration '[SC000, SC300, Cortex-M0, Cortex-M0+, Cortex-M1, Cortex-M23, Cortex-M3, Cortex-M33, Cortex-M35P, Cortex-M4, Cortex-M7, ARMV8MBL, ARMV8MML, ARMV81MML, Cortex-R4, Cortex-R5, Cortex-R7, Cortex-R8, Cortex-A5, Cortex-A7, Cortex-A8, Cortex-A9, Cortex-A15, Cortex-A17, Cortex-A53, Cortex-A57, Cortex-A72, Cortex-A73, other]'. It must be a value from the enumeration.
- Ërror: Line= 633 : cvc-attribute.3: The value 'Cortex-M55' of attribute 'Dcore' on element 'processor' is not valid with respect to its type, 'DcoreEnum'.
 - Ërror: Line= 1037 : cvc-enumeration-valid: Value 'Cortex-M55' is not facet-valid with respect to enumeration '[SC000, SC300, Cortex-M0, Cortex-M0+, Cortex-M1, Cortex-M23, Cortex-M3, Cortex-M33, Cortex-M35P, Cortex-M4, Cortex-M7, ARMV8MBL, ARMV8MML, ARMV81MML, Cortex-R4, Cortex-R5, Cortex-R7, Cortex-R8, Cortex-A5, Cortex-A7, Cortex-A8, Cortex-A9, Cortex-A15, Cortex-A17, Cortex-A53, Cortex-A57, Cortex-A72, Cortex-A73, other]'. It must be a value from the enumeration.
- Ërror: Line= 1037 : cvc-attribute.3: The value 'Cortex-M55' of attribute 'Dcore' on element 'accept' is not valid with respect to its type, 'DcoreEnum'.
 - Ërror: Line= 1185 : cvc-enumeration-valid: Value 'Cortex-M55' is not facet-valid with respect to enumeration '[SC000, SC300, Cortex-M0, Cortex-M0+, Cortex-M1, Cortex-M23, Cortex-M3, Cortex-M33, Cortex-M35P, Cortex-M4, Cortex-M7, ARMV8MBL, ARMV8MML, ARMV81MML, Cortex-R4, Cortex-R5, Cortex-R7, Cortex-R8, Cortex-A5, Cortex-A7, Cortex-A8, Cortex-A9, Cortex-A15, Cortex-A17, Cortex-A53, Cortex-A57, Cortex-A72, Cortex-A73, other]'. It must be a value from the enumeration.
 
 - Ërror: Line= 1185 : cvc-attribute.3: The value 'Cortex-M55' of attribute 'Dcore' on element 'require' is not valid with respect to its type, 'DcoreEnum'.
 
 - Ërror: Line= 1189 : cvc-enumeration-valid: Value 'Cortex-M55' is not facet-valid with respect to enumeration '[SC000, SC300, Cortex-M0, Cortex-M0+, Cortex-M1, Cortex-M23, Cortex-M3, Cortex-M33, Cortex-M35P, Cortex-M4, Cortex-M7, ARMV8MBL, ARMV8MML, ARMV81MML, Cortex-R4, Cortex-R5, Cortex-R7, Cortex-R8, Cortex-A5, Cortex-A7, Cortex-A8, Cortex-A9, Cortex-A15, Cortex-A17, Cortex-A53, Cortex-A57, Cortex-A72, Cortex-A73, other]'. It must be a value from the enumeration.
 - Ërror: Line= 1189 : cvc-attribute.3: The value 'Cortex-M55' of attribute 'Dcore' on element 'accept' is not valid with respect to its type, 'DcoreEnum'.
- Ërror: Line= 1190 : cvc-enumeration-valid: Value 'Cortex-M55' is not facet-valid with respect to enumeration '[SC000, SC300, Cortex-M0, Cortex-M0+, Cortex-M1, Cortex-M23, Cortex-M3, Cortex-M33, Cortex-M35P, Cortex-M4, Cortex-M7, ARMV8MBL, ARMV8MML, ARMV81MML, Cortex-R4, Cortex-R5, Cortex-R7, Cortex-R8, Cortex-A5, Cortex-A7, Cortex-A8, Cortex-A9, Cortex-A15, Cortex-A17, Cortex-A53, Cortex-A57, Cortex-A72, Cortex-A73, other]'. It must be a value from the enumeration.

Obviously there is a problem since CMSIS schema changed to 1.6.3, whereas Schema 1.6.2 which this gets validated against doesn't contain eg. Cortex-M55. CMSIS 5.6.0 installs fine.

Is there any way that I can change the file that is used for this validation?

This is happening on MacOS 10.15.4 with STMCubeMX 5.6.1. I tried looking for the right file inside the app folder and in my ~/.stmcubemx and ~/.stcufinder but couldn't find the right file.

Thank you in advance.

6 REPLIES 6

Hello @kj.obara​ 

Thanks for the feedback, issue detected.

It will be fixed next STM32CubeMX version.

Best regards,

Nesrine

PNM.1
Associate

I am also getting same error still when i try to install CMSIS with either STM32CubeMX or STM32CubeIDE.

When will be the next version release? Please comment

PNM.1
Associate

Is there way to work around with this issue?

I'm facing the same issue, when will it be fixed? can you please give us an idea?

Thanks,

Andrea

Same issue here.

Hello,

Issue reported to the tool development team that will plan the correction.

Best regards,

Nesrine