-
Notifications
You must be signed in to change notification settings - Fork 12
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
Comments
ARM Internal Ref: IOTSFW-1911 |
@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. |
The same, as I presume it was copied from there. There dont appear to be On Tue, Jan 26, 2016 at 2:29 AM, Johnny Robeson [email protected]
|
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. |
Is timer0 (the one reserved by the softdevice) the 32 bit timer? |
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 |
can someone from mbed describe how a fix here should make its way to mbedmicro/mbed ? |
No comment from the team, but my guess is this looks to be 'fixed' by the introduction of the nrf52
|
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.
The text was updated successfully, but these errors were encountered: