Re: MSP430F5528 - Clock and UART

"Onestone [email protected] [msp430]" <[email protected]> Wed, 18 Feb 2015 09:58:16 +1030
Newsgroups gmane.comp.hardware.texas-instruments.msp430.discuss
Message-ID <[email protected]>
Who's bullying, I'm pointing out a simple fact, and asking a valid 
question, over the years I've been in this group one point seems to 
dominate here. The vast majorioty of people are scared of using 
interrupts, especially C programmers.

Bullying requires some form of abuse. Get your facts right before you 
make pointless off topic comments.

Al

On 18/02/2015 9:46 AM, Martin Bruner [email protected] 
[msp430] wrote:
>
>
> Spelling is important when bullying someone online.
>
> From: "msp430@yahoogroups. com" <[email protected] 
> <mailto:[email protected]>>
> Reply-To: "msp430@yahoogroups. com" <[email protected] 
> <mailto:[email protected]>>
> Date: Tuesday, February 17, 2015 at 4:02 PM
> To: "msp430@yahoogroups. com" <[email protected] 
> <mailto:[email protected]>>
> Subject: Re: [msp430] MSP430F5528 - Clock and UART
>
> Well typing can be difficult when you only have limited use of your 
> hands. I'll try to do better next time.
>
> Al
>
>
> On 18/02/2015 8:46 AM, Martin Bruner [email protected] 
> [msp430] wrote:
>>
>>
>>  I believe you were looking for “frightening” not “fightening".
>>
>> From: "msp430@yahoogroups. com" <[email protected] 
>> <mailto:[email protected]>>
>> Reply-To: "msp430@yahoogroups. com" <[email protected] 
>> <mailto:[email protected]>>
>> Date: Tuesday, February 17, 2015 at 3:07 PM
>> To: "msp430@yahoogroups. com" <[email protected] 
>> <mailto:[email protected]>>
>> Subject: Re: [msp430] MSP430F5528 - Clock and UART
>>
>> Why oh why are you bit banging this when the MSP430 has an extremely 
>> simple UART in hardware. Are interrupts that fightening?
>>
>> Al
>>
>> On 18/02/2015 2:21 AM, [email protected] [msp430] wrote:
>>>
>>>
>>>
>>> Hello, I'm trying to communicate with my RF module through UART 
>>> interface. However, I get many errors even with low load. I suspect 
>>> that I have an issue with the way that I configure the clock or the 
>>> UART.
>>>
>>>
>>> Basically, for the UART functionality I use 
>>> http://glitovsky.com/blog/?p=300
>>>
>>> (I configured the connection as 8N1 at 115200).
>>>
>>>
>>> The clock configuration below is used with MCLK = 25 MHz ( when I 
>>> use it with MCLK=16 MHz I cannot communicate with the UART module at 
>>> all ) .
>>>
>>>
>>>  P5SEL |= 0x0C;
>>>
>>>   /* Select REF0 for FLL reference. */
>>>
>>>  UCSCTL3 &= ~SELREF_7;
>>>
>>>  UCSCTL3 |= SELREF_2;
>>>
>>>
>>>  /* Set ACLK to use REF0CLK.
>>>
>>>    * Set SMCLK to use the DCO.
>>>
>>>   */
>>>
>>>   UCSCTL4 &= ~SELA_7 & ~SELS_7 & ~SELM_7;
>>>
>>>   UCSCTL4 |= SELA_2 | SELS_4 | SELM_4;
>>>
>>>    /* Initialize FLL. */
>>>    Init_FLL_Settle(mclk/1000L, mclk/32768);
>>>
>>>    XT2_Start(XT2DRIVE_0);
>>>
>>>    UCSCTL4 &= ~SELA_7;
>>>     UCSCTL4 |= SELA_2;
>>>    UCSCTL8 |= SMCLKREQEN | MCLKREQEN | ACLKREQEN;
>>>    /* Enable interrupt for TBCCR0. */
>>>     TBCCTL0 = CCIE;
>>>   /* Number of ticks per millisecond. */
>>>     clock.aclk = 32768;
>>>     clock.ticks_per_interrupt = clock.aclk / 1000;
>>>     TBCCR0 = clock.ticks_per_interrupt;
>>>
>>>     /* Use ACLK, set timer to up-count mode, and start timer at zero. */
>>>     TBCTL = TBSSEL_1 | MC_2 | TBCLR;
>>>
>>>    /* Enable interrupts. */
>>>     __bis_SR_register(GIE);
>>> Thanks,
>>> Mike
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>