Tivaware Assert Failed for TM4C1292NCPDT Timer 6, Timer 7 peripheral enable.

Dominic Valentino1

Prodigy 150 points

Other Parts Discussed in Thread: TM4C1292NCPDT, TM4C129CNCPDT

Hello,

I'm getting a Tivaware assert when I call the following 2 functions on a TM4C1292NCPDT.

SysCtlPeripheralEnable(SYSCTL_PERIPH_TIMER6);
SysCtlPeripheralEnable(SYSCTL_PERIPH_TIMER7);

The assert that fails is:

ASSERT(_SysCtlPeripheralValid(ui32Peripheral));

Which is understandable since this function does not have an entry for Timer 6 or Timer 7.

The data sheet says that it has 8 timer modules and the part header file has entries for 6 and 7, however, Tivaware and the PinMux utility do not seem to support enabling it.

Is that because these 2 timers are not mapped to any external CCP module?

Thanks,

Dominic

over 9 years ago

0 Petrei over 9 years ago

Guru 26105 points

Hi,

You can verify in the user manual for/at

General-Purpose Timer Peripheral Present (PPTIMER)

and see there if the timers 6 and 7 are defined (they are) so there is a simple omission in check table (you can use also the function SysCtlPeriperalPresent() to check before enabling the clock). Add by yourself ...

Petrei

0 Amit Ashara over 9 years ago

TI__Guru**** 244380 points

Hello Dominic

Which version of TIVAWare are you using?

Regards

Amit

0 Dominic Valentino1 over 9 years ago in reply to Amit Ashara

Prodigy 150 points

2.1.0.12573

0 Amit Ashara over 9 years ago in reply to Dominic Valentino1

TI__Guru**** 244380 points

Hello Dominic

This is a bug in the driverlib. The SysCtlPeripheralEnable calles the local function _SysCtlPeripheralValid(uint32_t ui32Peripheral) in which the two times are not mapped.

You would need to add the following lines in sysctl.c from line 420

(ui32Peripheral == SYSCTL_PERIPH_TIMER6) ||
(ui32Peripheral == SYSCTL_PERIPH_TIMER7) ||

and recompile the driverlib image file

Regards

Amit

0 Dominic Valentino1 over 9 years ago in reply to Dominic Valentino1

Prodigy 150 points

Seems like timer.c has the same issue>>>

#ifdef DEBUG
static bool
_TimerBaseValid(uint32_t ui32Base)
{
    return((ui32Base == TIMER0_BASE) || (ui32Base == TIMER1_BASE) ||
           (ui32Base == TIMER2_BASE) || (ui32Base == TIMER3_BASE) ||
           (ui32Base == TIMER4_BASE) || (ui32Base == TIMER5_BASE) ||
           (ui32Base == WTIMER0_BASE) || (ui32Base == WTIMER1_BASE) ||
           (ui32Base == WTIMER2_BASE) || (ui32Base == WTIMER3_BASE) ||
           (ui32Base == WTIMER4_BASE) || (ui32Base == WTIMER5_BASE));
}
#endif

0 Dominic Valentino1 over 9 years ago in reply to Amit Ashara

Prodigy 150 points

Amit,

I already did what you suggested, I just want TI to incorporates these changes in the next rev. of Tivaware.

Thanks!

0 Amit Ashara over 9 years ago in reply to Dominic Valentino1

TI__Guru**** 244380 points

Hello Dominic

Thanks for the timer.c misses as well, point noted and we will fix it for next TIVAWare...

Regards

Amit

0 Elder Costa over 9 years ago in reply to Amit Ashara

Intellectual 430 points

I am using the timer to trigger a uDMA channel and the check in uDMAChannelAssign is also failing, specifically on the line

ASSERT((ui32Mapping & 0xffffff00) < 0x00050000);

I believe it is related to the subject of this thread. I was going to apply the changes to sysctl.c and timer.c suggested above but I will use the six lower timers instead until an updated version of Tivaware is released.

0 Amit Ashara over 9 years ago in reply to Elder Costa

TI__Guru**** 244380 points

Hello Elder,

Is it TM4C123 or TM4C129 and what is the argument you are passing to the uDMAChannelAssign?

Regards

Amit

0 Elder Costa over 9 years ago in reply to Amit Ashara

Intellectual 430 points

Hello Amit, sorry for the late response.

It is TM4C129.Setting device to TM4C129CNCPDT (IAR Eclipse based environment). Also setting the following:

#define PART_TM4C129CNCPDT
#define TARGET_IS_TM4C129_RA2
#define TARGET_IS_TMC129

I have just ran a test to reproduce the problem. I am passing the value 0x0007000A to uDMAChannelAssign() which looks right to me (UDMA_CH10_TIMER6A in udma.h).

0 Amit Ashara over 9 years ago in reply to Elder Costa

TI__Guru**** 244380 points

Hello Elder,,

I confirm this to be an issue as well. It should have been < 0x00090000 as some of the channels were added later and the file did not get update.

Regards

Amit

0 Elder Costa over 9 years ago in reply to Amit Ashara

Intellectual 430 points

Hi Amit,

I will give it a try. However I am a little worried about applying these changes and unleashing unexpected bugs.

Any hint when the next release of Tivaware will be available? It has been a while since the latest one was released (February). On one hand this may signal it is a very stable one but still there might be small fixes such as these ones that your customers would benefit of.