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

pwmout is 16bit only which means a max period of .2s #42

Open
jacobrosenthal opened this issue Jan 26, 2016 · 8 comments
Open

pwmout is 16bit only which means a max period of .2s #42

jacobrosenthal opened this issue Jan 26, 2016 · 8 comments
Labels

Comments

@jacobrosenthal
Copy link

Using my target, but Ive confirmed this on the mkit-gcc target as well.

PERIOD is defined as a uint16_t even though NRF_TIMER_Type.CC is defined as a uint32_t
PERIOD thus maxes out at 65535 or 0.26214f which seems short as the PWMOUT example sets a 4.0f, or 4 second period

I think theres more broken than that though, because even if I

An LED still blinks way to fast. So I think theres more issues in here than Ive currently found.

@ciarmcom
Copy link
Member

ARM Internal Ref: IOTSFW-1911

@ghost
Copy link

ghost commented Jan 26, 2016

@jacobrosenthal : how does this compare to the same code in https://github.com/mbedmicro/mbed ? I don't have time to investigate myself, but worth a look.

@jacobrosenthal
Copy link
Author

The same, as I presume it was copied from there. There dont appear to be
any real changes in the history of this file either.

On Tue, Jan 26, 2016 at 2:29 AM, Johnny Robeson [email protected]
wrote:

@jacobrosenthal https://github.com/jacobrosenthal : how does this
compare to the same code in https://github.com/mbedmicro/mbed ? I don't
have time to investigate myself, but worth a look.


Reply to this email directly or view it on GitHub
#42 (comment)
.

@ghost
Copy link

ghost commented Jan 26, 2016

I wonder if that would also help fix this issue ARMmbed/mbed-os#1378

I still am not sure of the way fixes in these yotta modules propagate to and/or from mbedmicro/mbed, since such a fix would be needed there as well.

@jacobrosenthal
Copy link
Author

Is timer0 (the one reserved by the softdevice) the 32 bit timer?

@ghost
Copy link

ghost commented Feb 5, 2016

I think that's what it says about timer0 here: http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.pdf.ps/nRF51822_PS_v3.1.pdf

@ghost
Copy link

ghost commented Feb 19, 2016

can someone from mbed describe how a fix here should make its way to mbedmicro/mbed ?

@jacobrosenthal jacobrosenthal changed the title pwmout is broken pwmout is 8bit only which means a max period of .2s Mar 13, 2016
@jacobrosenthal
Copy link
Author

No comment from the team, but my guess is this looks to be 'fixed' by the introduction of the nrf52
http://infocenter.nordicsemi.com/pdf/nRF52_Series_Migration_v1.0.pdf

Additional timer instances are added, TIMER3 and TIMER4. All timers now support all bit
modes (8, 16, 24, and 32 bits)

@jacobrosenthal jacobrosenthal changed the title pwmout is 8bit only which means a max period of .2s pwmout is 16bit only which means a max period of .2s Mar 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants