Messages

1

NXP^TM M522XX, KINETIS and i.MX RT / Re: DMA Timer Configuration Problem

« on: December 26, 2008, 02:19:18 PM »

Hi Mark,

     That was the problem!   

     Thanks again for your help!

      - Rick

2

NXP^TM M522XX, KINETIS and i.MX RT / DMA Timer Configuration Problem

« on: December 26, 2008, 12:32:50 AM »

Hi,

     I seem to be having some problems when I try to use DMA Timer 2 without interrupts.  I simply configure DMA Timer 2 to count at a 1MHz rate as follows:
   

   DTMR2 = (UINT16)0x3B03;   // Config DMA Timer 2 used to count 1us
   DTCN2 = 0;                      // Reset DMA Timer 2 count   
   
     When I include this code in my MCF52233 project, I end up with a default interrupt handler after a very short period of time.  If I comment this code out, my code runs fine.  I have tried DMA Timer 1, but got the same result.  I tried deciphering how I got into the default interrupt handler using "undefined interrupt during startup" post, but was unable to decipher the problem.   I also made sure this interrupt source was masked, but this didn't seem to help either.

     Any suggestions would be greatly appreciated.  I am working on a project which adds on to the uTaskerV1.3 application and have service pack 8 installed. 

     Thanks,

       Rick
      

3

NXP^TM M522XX, KINETIS and i.MX RT / Debounce

« on: November 20, 2008, 03:05:10 PM »

Hi Mark,

   Any suggestions for how to best handle debounce on the interrupt test that works off of SW1?  I can get a couple of the test messages from one press of SW1.

    Thanks,
   
           Rick

4

NXP^TM M522XX, KINETIS and i.MX RT / Re: DMA Timer Configuration

« on: November 20, 2008, 03:02:51 PM »

Hi Mark,

   Definately some operator error on my part here.  Both your suggestions work 100% on my 52233DEMO, and I greatly appreciate the support.  I finished up with no clock divider and used:

dma_timer_setup.count_delay =  DMA_TIMER_US_DELAY(1,1,500);

   Thanks again for your outstanding support!

       - Rick

5

NXP^TM M522XX, KINETIS and i.MX RT / DMA Timer Configuration

« on: November 10, 2008, 03:28:51 PM »

Hi Mark,

   I want to use DMA Timer 3 to generate an interrupt every 500us.  I spent some time working with the DMA timer configuration and finally had to cheat by stuffing a value into the DTRR register after doing the configuration.  I got it working, but would like to do it in proper uTasker style.   Can you take a quick look and let me know what you think please?  I tried your macros for setting the delay time, but the output pulse was WAY off.  I'm using real hardware MCF52233Demo board.

    Thanks,

            Rick

static void rsn_DMA_timer_int(void)
{
    static int iTimerTest = 0;
    PORTAN ^= PORT_AN_BIT0; // toggle output
   
}

static void fnConfigure_DMA_Timer(void)
{
    DMA_TIMER_SETUP dma_timer_setup;  // interrupt configuration parameters
    CONFIG_TEST_OUTPUT();
    dma_timer_setup.int_type = DMA_TIMER_INTERRUPT;
    dma_timer_setup.int_handler = rsn_DMA_timer_int;
    dma_timer_setup.channel = 3;                         // DMA timer channel 3
    dma_timer_setup.clock_divider = 0;                                         
    dma_timer_setup.int_priority = CAN13_INTERRUPT_PRIORITY; // define interrupt priority
    dma_timer_setup.mode =  (DMA_TIMER_INTERNAL_CLOCK | DMA_TIMER_RESTART_ON_MATCH | DMA_TIMER_PERIODIC_INTERRUPT | DMA_TIMER_INTERNAL_CLOCK_DIV_16 );
    dma_timer_setup.count_delay = 100;          // 500us delay using no dividers
    fnConfigureInterrupt((void *)&dma_timer_setup);  // enter interrupt for DMA timer test
   
    DTRR3 = 1849; // set for 2KHz

}

6

µTasker general / Scheduler behavior on interrupt event

« on: November 09, 2008, 04:21:28 PM »

Assume we have a uTasker system with 10 tasks running, the order of the tasks in the main task table is simply #1 through #10.  The scheduler has allowed task #2 to run, and an asynchronous hardware interrupt arrives.  The interrupt service routine sends an interrupt event message to task #8. 

What happens next?  What does the scheduler do when task #2 is done?  Does it go on to task #3 or does it jump down to task #8, that has an interrupt event message waiting? 

I'm trying to make sure I understand the basic scheduler behavior here with respect to interrupt latencies.

Thanks in advance,

   Rick