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

fix(PeriphDrivers): Fix MAX32655 WDT clock source order #820

Merged
merged 3 commits into from
Dec 15, 2023

Conversation

hfakkiz
Copy link
Contributor

@hfakkiz hfakkiz commented Dec 8, 2023

Pull Request Template

Description

WDT1(LPWDT0) clock sources order of MAX32655 is wrong in user guide.

image

To test clock source selection feature on MAX32655 for LPWDT0, selected ERTCO(CLK1) as clock source and disabled it but WDT continued to work. Switched selected clock source to CLK2 which is INRO clock's slot according to the user guide and disabled ERTCO clock, then WDT stopped working. Given clock source order in user guide is wrong. Updated clock sources order for WDT1.

Checklist Before Requesting Review

  • PR Title follows correct guidelines.
  • Description of changes and all other relevant information.
  • (Optional) Link any related GitHub issues using a keyword
  • (Optional) Provide info on any relevant functional testing/validation. For API changes or significant features, this is not optional.

Order of WDT clock sources is wrong in user guide. Updated clock source order.

Signed-off-by: Furkan Akkiz <hasanfurkan.akkiz@analog.com>
@hfakkiz hfakkiz added the MAX32655 Related to the MAX32655 (ME17) label Dec 8, 2023
@github-actions github-actions bot added the MAX78000 Related to the MAX78000 (AI85) label Dec 8, 2023
@hfakkiz hfakkiz changed the title fix(PeriphDrivers): Fix MAX32655 WDT clock source order fix(PeriphDrivers): Fix MAX32655 WDT clock source order Dec 8, 2023
Copy link
Contributor

@Jake-Carter Jake-Carter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @hfakkiz

You can open a Jira ticket for the User Guide here: https://jira.analog.com/projects/MBUDOCS/

@hfakkiz
Copy link
Contributor Author

hfakkiz commented Dec 11, 2023

Thanks @hfakkiz

You can open a Jira ticket for the User Guide here: https://jira.analog.com/projects/MBUDOCS/

I opened following ticket.
https://jira.analog.com/browse/MBUDOCS-2235

hfakkiz and others added 2 commits December 14, 2023 12:28
clock_source_num parameter causes warning, fixed it.

Signed-off-by: Furkan Akkiz <hasanfurkan.akkiz@analog.com>
When MSDK_NO_GPIO_CLK_INIT being defined,
err variables become unused and warning occurs during build
The purpose of this commit is to remove this warning

Signed-off-by: Sadik Ozer <sadik.ozer@analog.com>
@github-actions github-actions bot added the MAX32665 Related to the MAX32665 (ME14) label Dec 14, 2023
@Jake-Carter Jake-Carter merged commit c9af9ee into main Dec 15, 2023
10 checks passed
@Jake-Carter Jake-Carter deleted the fix/wdt-max32655-clock-sources branch December 15, 2023 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MAX32655 Related to the MAX32655 (ME17) MAX32665 Related to the MAX32665 (ME14) MAX78000 Related to the MAX78000 (AI85)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants