Sysbios locks for about 2 seconds after using gateAll functions

Adam,

How long are you locking the CPU (either via GateAll_enter() or Hwi_disable())?  How long does it take to write/read those FRAMs?

Also, have you enabled Clock tick suppression (http://processors.wiki.ti.com/index.php/SYS/BIOS_for_the_MSP430#Clock_Tick_Suppression)?  In the SYS/BIOS release you’re using it should be disabled by default.  But I wonder if you’ve enabled it.  If some of the constraints for the DYNAMIC tick mode are violated (http://processors.wiki.ti.com/index.php/SYS/BIOS_for_the_MSP430#Important_Notes_Regarding_Clock_Tick_Suppression) then the timer interrupt may not be generated until the timer count wraps around, which is 2 seconds for a 16-bit timer running at 32KHz.  But… this wraparound condition will only affect the timer peripheral being used by the Clock module, and will not affect other timers or interrupt sources.  So it doesn’t sound like this is the issue… but your mention of “about 2 seconds” in the thread title got me wondering.  If you have enabled Clock tick suppression… can you try disabling it (http://processors.wiki.ti.com/index.php/SYS/BIOS_for_the_MSP430#Switch_Clock_module_from_using_TickMode_DYNAMIC_to_TickMode_PERIODIC) to see if that makes a difference?

Thanks,
Scott

Hi Scott,

Thanks for your quick answer.
I do not have clocks enabled in my project. I am using an instance of the timer module to call the interrupt function that implements the timers in my application.
It takes about 5 ms to write on the FRAMs. My timer is set to generate an interrupt every 1 ms.

I disabled the timer module and setup the clock module with default values, added a tick period of 1000us and created a clock instance that calls my timer function every 1ms. I made sure Clock.tickMode = Clock.TickMode_PERIODIC in my config file.

And nothing…. Same behavior as when I used the timer module. I am now sure that the timer interrupt does not fire in those 2 seconds.
I went back to using the timer module and disabled the clock module.

Thanks to your advice I did a few more tests (created an Idle function that toggles a port and a HWI that also toggles a different port when an interrupt on port P1.1 occurs.

It would seem that both the idle function and the HWI work while the device is "locked" (the ports toggle) but the timer interrupt is not called. Most of the events that are generated on my system in someway use the variables in the timer interrupt. This is why at first I thought that the system was "locking"

I then set my Input clock source to SMCLK (I was using ACLK) compiled and everything worked perfectly! If I set it back to ACLK then the timer interrupt is not called after the gateAll fucntion calls.

I must be doing something wrong when I setup ACLK or somewhere else... I use code that TI has used on one of the demo boards (CC1120 development kit) to startup XT1. On my custom hardware the external crystal and capacitors are on the same ports as on the demoboard and have the same values. The code works with out sysbios.

This is the code I use to setup XT1 and I call it before calling BIOS_start()  (if I call it in a task there is no difference)...

void hal_mcuStartXT1(void)
{
    /* Set up XT1 Pins to analog function, and to lowest drive */
    P7SEL |= 0x03;
    UCSCTL6 |= XCAP_3 ;                       /* Set internal cap values */
 
    while(SFRIFG1 & OFIFG) {                  /* Check OFIFG fault flag  */
        while ( (SFRIFG1 & OFIFG))            /* Check OFIFG fault flag  */
        {
            /* Clear OSC fault flags  */
            UCSCTL7 &= ~(DCOFFG + XT1LFOFFG + XT1HFOFFG + XT2OFFG);
            SFRIFG1 &= ~OFIFG;                    /* Clear OFIFG fault flag  */
        }
        UCSCTL6 &= ~(XT1DRIVE1_L+XT1DRIVE0);    /* Reduce the drive strength */
    }
}

Grateful for any help you can give me.
Thanks for your time
Adam

Hi Scott,

I've been busy lately and haven't had time to read the documentation thoroughly. 

I disabled the clock configuration by boot as you suggested: (in my .cfg file)

Boot.configureDCO = false;

and setup the clock frequencies:

ClockFreqs.SMCLK = 20000000;

ClockFreqs.ACLK = 32768;

Guess what. Nothing... Timer interrupt fires only about 2 seconds after a gateAll call...

Thanks for your help and time

Adam

Adam,

OK, thanks.  And sorry for the slow reply.

I don’t know what would be causing the behavior you describe, and am not too familiar with the UCS itself.  It may be that we need some help from someone on the device or apps teams.

Have you been able to verify that ACLK is indeed running at 32768Hz after your initialization code?

Also, have you tried disabling your code that sets up clocks, and use just the default setup by the Boot module?

And do you see the same behavior on multiple boards?

Thanks,
Scott