tag:blogger.com,1999:blog-8922440028126506489.post2111279262990851987..comments2024-03-21T05:45:16.381-04:00Comments on Blog de Joe Freeman: MSP430 Fading and other long running activities using TwoMsTimer instead of delay()Joe Freemanhttp://www.blogger.com/profile/13642403834748872077noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8922440028126506489.post-18427621968267254892014-09-06T06:52:44.983-04:002014-09-06T06:52:44.983-04:00hello Joe,
thanks for the great library.
conside...hello Joe,<br /><br />thanks for the great library.<br /><br />consider me as a noob in MSP430 programming (2533 mcu), so I have some questions. your timer works great for considerable time delay, for example 10 or 15 seconds. <br /><br />1. is there any max limit (in seconds)? because in some programs I can run it at 20 s, but with others (which are larger in size), 20 s doesn't work anymore?<br /><br />2. it looks that your library uses some free space, is that correct? like, with smaller projects bigger delays work and vice versa ...<br /><br />3. I need the delay for example 30 s or 60 s, so I tried one more thing ... I'm running the interrupt at constant delay, lets says 10 s, which works for sure. and then I have one internal counter, which counts how many times interrupt occured - so if it occured once or twice, nothing happens, and when it occurs for the third time (if I want 30 s delay), some code is executed and that counter resets.<br /><br />4. but this also works for 30 s, also for 31, 32 and 33 s, but no more for 34 s ... and I'm not sure why?! since the interrupt is happening at constant delay ... any idea?<br /><br />I put my example code here: https://www.dropbox.com/s/yg0ykcfjjxy45zh/twomstimer_test.ino?dl=0<br /><br />thank you for help and best regardsAnonymoushttps://www.blogger.com/profile/15874658740710953685noreply@blogger.comtag:blogger.com,1999:blog-8922440028126506489.post-55190614421337610432012-09-27T22:14:29.782-04:002012-09-27T22:14:29.782-04:00Did you set the cpu type in energia preferences? T...Did you set the cpu type in energia preferences? That determines which timers are available. I wrote this for the 2553 processor.Joe Freemanhttps://www.blogger.com/profile/13642403834748872077noreply@blogger.comtag:blogger.com,1999:blog-8922440028126506489.post-59501594398622339542012-09-15T22:37:29.064-04:002012-09-15T22:37:29.064-04:00Hi Joe,
I'm using energia in Mac OS and when ...Hi Joe,<br /><br />I'm using energia in Mac OS and when I build the project I'm having this problem:<br /><br />woMsTimer.cpp: In function 'void TwoMsTimer::start()':<br />TwoMsTimer.cpp:68:3: error: 'TA1CCR0' was not declared in this scope<br />TwoMsTimer.cpp:69:3: error: 'TA1CTL' was not declared in this scope<br />TwoMsTimer.cpp:70:3: error: 'TA1CCTL0' was not declared in this scope<br />TwoMsTimer.cpp: In function 'void TwoMsTimer::stop()':<br />TwoMsTimer.cpp:77:3: error: 'TA1CCTL0' was not declared in this scope<br />TwoMsTimer.cpp: At global scope:<br />TwoMsTimer.cpp:96:26: error: 'TIMER1_A0_VECTOR' was not declared in this scope<br />TwoMsTimer.cpp: In function 'void Timer_A_int()':<br />TwoMsTimer.cpp:97:6: error: interrupt vector offset must be an even non-negative integer constant<br /><br />It seems that original Timer0 Registers, such as TA1CCR0 are not recognized!!!!<br /><br />Any ideas to solve this issue?<br /><br />Best RegardsDas Butcherhttps://www.blogger.com/profile/11586477082684410140noreply@blogger.com