anneser@pwa-b.UUCP (Dean Anneser) (02/18/88)
Help ! Has anyone out in netland had experience with the 8036 counter/timer chip that is used on DEC's KXJ11-CA/KXT11-CA single board computer. I have a problem that I cannot resolve. I've talked with the KXJ11 product group at DEC, AMD (Advanced Micro Devices), and ZILOG, to as of yet, no avail. The task I'm attempting is to measure the inter-pulse interval of a signal from 10 Hz to 5000 Hz, using the 16 bit counter_timer_2, linked with the 16 bit counter_timer_1, to create a 32 bit counter_timer (counter_timer_2 is the most significant word, and counter_timer_1 is the least significant). The clock is a 2MHz clock. At higher, frequencies, the inter-pulse interval at a 2MHz time base can be represented in one 16 bit word (counter_timer_1). At lower frequencies, the count value reguires more than 16 bits to be represented. The problem I'm seeing, is that counter_timer_2 is not decremented with the FIRST transition through zero, of counter_timer_1. As the input signal's frequency decreases, and counter_timer_1 makes an additional transition through zero, counter_timer_2, then will decrement (what appears to be) correctly, but its value is one greater than it should be. Is there anyone out there at ZILOG, DEC, SGS, AMD, SHARP, or anywhere else, who could be of assistance. Thanks in advance. Dean W. Anneser Pratt & Whitney Aircraft East Hartford, CT 06108 {philabs,utah-gr}!pwa-b!anneser -- Dean W. Anneser Pratt & Whitney Aircraft East Hartford, CT 06108 {philabs,utah-gr}!pwa-b!anneser
curry@nsc.nsc.com (Ray Curry) (02/21/88)
In article <157@pwa-b.UUCP> anneser@pwa-b.UUCP (Dean Anneser) writes: >Help ! Has anyone out in netland had experience with the 8036 counter/timer > >The problem >I'm seeing, is that counter_timer_2 is not decremented with the FIRST >transition through zero, of counter_timer_1. As the input signal's frequency >decreases, and counter_timer_1 makes an additional transition through zero, >counter_timer_2, then will decrement (what appears to be) correctly, but its >value is one greater than it should be. > If I can remember back that far, there are some programming problems with the CIO mostly with the manner of programming the link. This may be related to the problem you see and I will have to spend a couple of hours with the manual to try to remember the exact problem. As I remember off the top of my head, care must be taken in programming the registers and setting the link. As a rule of thumb, only handle one flag at a time and the last two steps are to link the two and enable the count. Like I say, I can't remember all of the recommended proceedures. If I can remember more, I will let you know. I may be able to get a hold of the original designer of the chip.
gene@cooper.cooper.EDU (Gene (the Spook) ) (02/25/88)
in article <157@pwa-b.UUCP>, anneser@pwa-b.UUCP (Dean Anneser) says: > Xref: cooper comp.sys.dec:392 comp.arch:2452 > > Help ! Has anyone out in netland had experience with the 8036 counter/timer > chip that is used on DEC's KXJ11-CA/KXT11-CA single board computer. I have > a problem that I cannot resolve. I've talked with the KXJ11 product group > at DEC, AMD (Advanced Micro Devices), and ZILOG, to as of yet, no avail. > > Is there anyone out there at ZILOG, DEC, SGS, AMD, SHARP, or anywhere else, > who could be of assistance. I'm having a b*tch of a time trying to mail anything from here, so I'll just post my message. Sorry... Anyway, although I'm not at all familiar with the chip in question, I might suggest trying either GE/Intersil, Standard Microsystems Corp, or Exar/Exel for some help. You didn't mention which company put the bugger out (maybe by the logo on the chip, if there is any), so I can't be sure. If all else fails, you might try your local "IC Master". You know, that foot-thick collection of chip listings, companies, and their addresses? That might very well be your best bet. Spookfully yours, Gene ...!ihnp4!philabs!phri!cooper!gene "In this world we're living in, we have our share of sorrow. Answer now is don't give in; aim for a new tomorrow!" - Robert John Aurthur Halford