Skip to content
This repository has been archived by the owner on Sep 6, 2023. It is now read-only.

Implement MCPWM module support #94

Open
MrSurly opened this issue May 19, 2017 · 8 comments
Open

Implement MCPWM module support #94

MrSurly opened this issue May 19, 2017 · 8 comments

Comments

@MrSurly
Copy link
Contributor

MrSurly commented May 19, 2017

I'm going to begin development on a thin wrapper around MCPWM, starting with implementation of capture.

@eugenio
Copy link

eugenio commented Jun 7, 2017

The MCPWM link is dead... new link is MCPWM

@MrSurly
Copy link
Contributor Author

MrSurly commented Jun 7, 2017

Updated URL.

@nickzoic
Copy link
Collaborator

nickzoic commented Aug 3, 2017

Sounds like a great idea. Someone earlier (LinuxConfAU, I think) brought up the idea of using the MCPWM "RMT" function to clock bits out to NeoPixel type LEDs, which seems like it might work too.

@bskp
Copy link

bskp commented Sep 24, 2019

Since I needed 6 PWM channels with independent frequencies, I extended the esp32-module with MCPWM support: https://github.com/bskp/micropython_esp32_mcpwm.
Currently, only basic functionality is covered and I do not plan to dive much deeper. However, I'm happy if it helps someone else!

@dpgeorge
Copy link
Member

@bskp FYI this repository is no longer active. All activity is now at https://github.com/micropython/micropython, and also at https://forum.micropython.org

@bskp
Copy link

bskp commented Sep 24, 2019

@dpgeorge thank you for the notice.
Is there a chance for this feature being merged upstream, even though the API deviates from the one of machine.PWM? If so, I'll open a pull request.

@nickzoic
Copy link
Collaborator

G'day @Bksp for what it's worth I still think this is a great hardware feature to have exposed in MicroPython :-)

The work in this repo has now been merged back into the main micropython/micropython repo, and it'd be well worth opening this issue over there and working towards an agreement on an API change to allow support for this. I'm happy to help if I can.

@damien did we work out how to lock this repo to prevent confusion?

@dpgeorge
Copy link
Member

did we work out how to lock this repo to prevent confusion?

It's possible to archive a repository to make it read-only, but I think it's good to keep this un-archived so we can close/update issues/PRs here as they are resolved upstream. (And we rarely get comments on this repo anymore anyway.)

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

No branches or pull requests

5 participants