Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad content in handler.S when converting a SVD file for CortexM7. #80

Closed
NicoPy opened this issue Dec 17, 2020 · 3 comments
Closed

Bad content in handler.S when converting a SVD file for CortexM7. #80

NicoPy opened this issue Dec 17, 2020 · 3 comments

Comments

@NicoPy
Copy link
Contributor

NicoPy commented Dec 17, 2020

Hi,
When converting a SVD file for a CortexM7 µP, the generated content of handler .S is not correct :

	.syntax unified
	.cpu cortex-m4
	.thumb

Any fix or workaround ?

Regards,
Nicolas

@Fabien-Chouteau
Copy link
Member

Hello @NicoPy ,

Why do you consider it not correct? cortex-m7 is backward compatible with cortex-m4, specially for such simply ASM code.

@NicoPy
Copy link
Contributor Author

NicoPy commented Dec 18, 2020

Hi @Fabien-Chouteau ,
Sure, cortex-m7 is a superset of cortex-m4, but...

  • Will the compiler be happy when you tell it you compile for cortex-m7 while the asm file tells it is made for cortex-m4 ?
  • This is not Ada spirit. A signal space can make the compiler complain. Why should we accept such a non coherency ?

@Fabien-Chouteau
Copy link
Member

  • Will the compiler be happy when you tell it you compile for cortex-m7 while the asm file tells it is made for cortex-m4 ?

Yes.

  • This is not Ada spirit. A signal space can make the compiler complain. Why should we accept such a non coherency ?

As explained above the there is no incoherency here.

You can contribute to this pull-request if you want to work on different behavior for the tool: #50
The main problem being that SVD files do not document the CPU core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants