Reporting bugs in SVD files

[ri]

Hi, 

Where should we report issues in SVD files, e.g, incorrect offset or missing fields. Is there any place to submit a patch file?

[ri]

Hi,

I've found some issues for the mke04z4.svd file when going through the KE04 Sub-Family Reference Manual. I've attached a csv where each row is one issue. If another format is more useful, I can follow that for future reports.

- RI

[Celeste_Liu · Accepted solution]

Hello @ri ,

Thanks for your feedback.

I just want to confirm that you know mke04z4.svd corresponds to MKE04P24M48SF0RM, not MKE04P80M48SF0RM.

Arm Cortex-M0+|Kinetis KE04 48 MHz 32-bit 5V MCUs | NXP Semiconductors

The latter should use the MKE04Z1284.svd file instead.

I have checked the FTM2CLKPS bit in MKE04P24M48SF0RM, and it appears to be correct. 

So I suspect that you might have referenced the wrong reference manual. If you still encounter any issues, feel free to contact me again.

BR

Celeste

[ri]

Thank you for the clarification! I did have the other RM. Is there a naming convention the SVD files follow that relate to the devices listed in the RM?
As the devices listed in MKE04P24M48SF0RM are MKE04Z8VTG4(R), MKE04Z8VWJ4(R) and
MKE04Z8VFK4(R).

[Celeste_Liu]

Hello @ri ,

You can refer to the corresponding system_MKE04Zx.h or MKE04Zx.h files, where you can find the related Reference Manual information.

Hope it helps.

BR

Celeste

[Celeste_Liu]

Hello @ri ,

Thanks for your post.

You can report issues here in the Community.

If you already have a patch file but prefer not to expose it in a public channel, you’re also welcome to send the patch to us via private support case. You can create a case here:

If you encounter any issues while creating the case, please feel free to reach out to me, I’ll be happy to help.

Once you provide the detailed information, I can take a look on my side. If I confirm that it’s a real issue, I’ll help report it to the internal team for further investigation and tracking.

Thanks again for the feedback.

BR

celeste