Hi, is it possible to use the timers T12 and T13 from CAPCOM6 as generel purpose timers (C164CI)? The description of the CAPCOM6 unit is quite heavy stuff and to me its not clear if I can use those timers as normal timers to generate a periodic interrupt. Thx for help Bert
Hi Bert, I think you can do it. E.g. you could use "Single Shot Mode and Interrupt on a Period Match", but also other combinations, as e.g. Zero Match and Period Match.... CCU6 outputs can be configured as 'not used'. Depending of what you choose, you have to care of how to retrigger the timer. ( No because autoreload, manually by software, with shadowtransfer ...) So, as you note, it is heavy stuff, and you will have to spend some time with reading. It is one of the most complex module. As hint I can recommend to take the time to read about: What Zero-Match, Period Match and so on mean. Which interrupts you can generate, and the counting rules. ( Yes, I know, thats why you asked here ) A really help for me, to become more familar was DAvE - so I could play around with the settings and figure out how to generate interrupts ( and of course signals ). Don't worry - the reading and the look over in parallel to the diagrams can be done relative quickly, if you invest some time you have no stress and pressure from outside. But in general, yes you can do. Stefan
Hi Stefan, I read your answer to the CAPCOM6 question. I have a very simple question to the same module: Is it posible, to use pin CC61 as a kind of fast external input? In dave I found that it should do, when I enable rising and falling interrupts on pin CC61. But I never get an int and the interrupt request bit does not toggle. Is there a known bug in C164CI-LM with this part of CAPCOM61 or do I oversee some thing? Thanks a lot, Mike
Hello Mike, yes it works. Since I am not familar with C164CL I wrote a test program and it works very fine with the simulator. So it should also works with hardware. I took only care of the functionality, but not for the timings itself. It seems, that something in your DAvE setup must be wrong. From the "bug side" there is nothing related to this topic. Either we must compare your settings against my or I can e-mail you the simulator program, which works regarding your expected functionality. Stefan
Hi Stefan, my solution also works in the simulator but not at the hardware. A simular case I had as I wanted to move CAN-Pins from P5 to P8, which also works in simulator and is described in Infineons PDFs. A half year later a friend, working at Infineon in munich told us that this feature never worked at th c164ci. So I guessed, I am in the same sort of pitfall. My hope is, that there is another reason for the difference between simulator and hardware. Any suggestions? Mike
Hi Mike, unfortunately I have no hardware, that I can test. Normaly the behaviour you speak about occours, if there are differences in simulator setup and hardware setup. ( Because sometimes for the simulator some settings are not relevant, which you must take care about for running in hardware ) What I remember for the Xc16x devices is, that we have some problems, if we used the CAPCOM6 and did accesses in parallel to the bus. Than the CAPCOM6 was not worked as expected. For this cases the errata only says, that an software access overwrites the hardware. ( What I am a little bit in doubt of, because the bus controller is from my point of view a piece of hardware ) In my case the problems came from wrong EBC -settings. That is the only suggestion at the moment I have. Sorry, Stefan