Changed the MSP430 hwtimer implementation to use TimerB7 instead of Time... #171
Conversation
…imerA3. This allows us to have 7 hwtimer instances (instead of 3) on MSP430F16x MCU.
|
While this is true for the F16x models, some other MCU's like F12x, F11x, G2x, F21x, F22x, AFE2x, F41x, F42x, F51x and F643x will have no available hwtimers at all. I highly recommend to find a solution to use TimerA and TimerB instead of remove the use of TimerA, all MCU's have a TimerA but not all have a TimerB. |
|
Indeed; however, since RIOT only support MSPF16x for now, I made this as a quick fix to improve the current situation. Use of many timers is a very interesting solution, but it will probably require some changes in the hwtimer API. I'm gonna open a ticket about that. |
|
please rebase onto master, there is at least one conflict |
|
Actually, this PR won't be included. Work has begun on a more portable solution, that uses both TimerA and TimerB where appropriate (as overflowed suggested in a previous comment), and will work on any MSP430 device. It will supersede and replace this branch. |
Firmware storage
...rA3.
This allows us to have 7 hwtimer instances (instead of 3) on MSP430F16x MCU.