Hi,
I'm using SYS/BIOS v6.35.04.50 on AM3359 chip. The default Clock module instance uses hardware DMTimer2 and everything works fine. However, if I try using the Timer module with different HW timer it all stops working.
For example, while having the following line in configuration file:
Clock.timerId = 0; // Use DMTimer2
it works fine. But replacing it with:
Clock.timerId = 1; // Use DMTimer3 (or any of 4..7)
Generates "data abort" exception on first attempt of dmtimer module to write the timer registers:
timer->tclr = 0; in Timer_initDevice()
which attempts writing address 0x48044038 and generates the exception.
1. First I suspected it is caused by the MMU, but it does not seem to be the problem.
2. Can the be related to some clocks configuration? When I think about it, where does SYS/BIOS program PRCM module to activate TIMER2 clock?
What do I miss? What can cause this problem?
Regards,
Vasili
