Sign in

username:

password:



Not a member?

Search msp430



Search tips

Subscribe to msp430



Ads

Discussion Groups

Discussion Groups | MSP430 | Reboot problem when Timer A is active

The purpose of this group is to foster exchange of information on the Texas Instruments MSP430 family of microcontrollers and related tools. Everyone welcome, all levels of familiarity/expertise.

Reboot problem when Timer A is active - oliver at mettrix - Aug 8 8:51:59 2008

Hi to all,

We have a small problem that is racking our brains.
We've designed a small system that includes an MSP430F2234. We use pins P2.6 AND P2.7 to drive a 32.768 KHz crystal/cap combination to generate an Aclk

When the clock is off, i.e. we set TACL = o and TACCTL0 = o the processor does what it us supposed to do except for functions that rely on the Aclk

When we start up the Aclk, the processor just loop through reboot continuously. We monitor this by placing a break point (IAR) at the call for the CPU_init function which we keep hitting.

We feel this is probably a setup/initialization problem but have not figured it out.

Any help and ideas is greatly appreciated.

Thanks

Oliver
Mettrix Technology

[Non-text portions of this message have been removed]
------------------------------------



(You need to be a member of msp430 -- send a blank email to msp430-subscribe@yahoogroups.com )


Re: Reboot problem when Timer A is active - bb_stefan - Aug 8 10:25:11 2008

With this plenty of information it's really easy to help.....

1.) You don't need a cap for 32kHz crystal!
It's already inside your MSP (select proper XCAPx in BCSCTL3)

2.) TACTL and TACCTL0 have nothing to do with basic cock settings.
You cannot en-/disable ACLK with this.
These are control registers for Timer_A

3.) Disable the watchdog, to get rid of reboots

--- In m...@yahoogroups.com, "oliver at mettrix" wrote:
>
> Hi to all,
>
> We have a small problem that is racking our brains.
> We've designed a small system that includes an MSP430F2234. We use
pins P2.6 AND P2.7 to drive a 32.768 KHz crystal/cap combination to
generate an Aclk
>
> When the clock is off, i.e. we set TACL = o and TACCTL0 = o the
processor does what it us supposed to do except for functions that
rely on the Aclk
>
> When we start up the Aclk, the processor just loop through reboot
continuously. We monitor this by placing a break point (IAR) at the
call for the CPU_init function which we keep hitting.
>
> We feel this is probably a setup/initialization problem but have not
figured it out.
>
> Any help and ideas is greatly appreciated.
>
> Thanks
>
> Oliver
> Mettrix Technology
>
> [Non-text portions of this message have been removed]
>

------------------------------------



(You need to be a member of msp430 -- send a blank email to msp430-subscribe@yahoogroups.com )

Re: Reboot problem when Timer A is active - bb_stefan - Aug 8 10:26:37 2008

With this plenty of information it's really easy to help.....

1.) You don't need a cap for 32kHz crystal!
It's already inside your MSP (select proper XCAPx in BCSCTL3)

2.) TACTL and TACCTL0 have nothing to do with basic clock settings.
You cannot en-/disable ACLK with this.
These are control registers for Timer_A

3.) Disable the watchdog, to get rid of reboots

--- In m...@yahoogroups.com, "oliver at mettrix" wrote:
>
> Hi to all,
>
> We have a small problem that is racking our brains.
> We've designed a small system that includes an MSP430F2234. We use
pins P2.6 AND P2.7 to drive a 32.768 KHz crystal/cap combination to
generate an Aclk
>
> When the clock is off, i.e. we set TACL = o and TACCTL0 = o the
processor does what it us supposed to do except for functions that
rely on the Aclk
>
> When we start up the Aclk, the processor just loop through reboot
continuously. We monitor this by placing a break point (IAR) at the
call for the CPU_init function which we keep hitting.
>
> We feel this is probably a setup/initialization problem but have not
figured it out.
>
> Any help and ideas is greatly appreciated.
>
> Thanks
>
> Oliver
> Mettrix Technology
>
> [Non-text portions of this message have been removed]
>

------------------------------------



(You need to be a member of msp430 -- send a blank email to msp430-subscribe@yahoogroups.com )