AVR Freaks

And I managed to confuse myself even further by looking at iotn212.h:

#define TCA0                  (*(TCA_t *) 0x0A00) /* 16-bit Timer/Counter Type A */
#define TCB0                  (*(TCB_t *) 0x0A40) /* 16-bit Timer Type B */
#define TCD0                  (*(TCD_t *) 0x0A80) /* Timer Counter D */

also

/* TCB (TCB0) - 16-bit Timer Type B */
#define TCB0_CTRLA  _SFR_MEM8(0x0A40)
#define TCB0_CTRLB  _SFR_MEM8(0x0A41)
#define TCB0_EVCTRL  _SFR_MEM8(0x0A44)
#define TCB0_INTCTRL  _SFR_MEM8(0x0A45)
#define TCB0_INTFLAGS  _SFR_MEM8(0x0A46)
#define TCB0_STATUS  _SFR_MEM8(0x0A47)
#define TCB0_DBGCTRL  _SFR_MEM8(0x0A48)
#define TCB0_TEMP  _SFR_MEM8(0x0A49)
#define TCB0_CNT  _SFR_MEM16(0x0A4A)
#define TCB0_CNTL  _SFR_MEM8(0x0A4A)
#define TCB0_CNTH  _SFR_MEM8(0x0A4B)
#define TCB0_CCMP  _SFR_MEM16(0x0A4C)
#define TCB0_CCMPL  _SFR_MEM8(0x0A4C)
#define TCB0_CCMPH  _SFR_MEM8(0x0A4D)

So that's actually setting blocks of registers at real physical SFR addresses which seems to strengthen the argument that it does have those peripherals.

 

Possibly even more definitive is the XML description in the ATDF file:

        <module id="I2117" name="TCA">
          <instance name="TCA0">
            <register-group address-space="data" name="TCA0" name-in-module="TCA" offset="0x0A00"/>
            <signals>
              <signal field="PORTMUX.CTRLC.TCA00" function="TCA0_ALT" group="WO" index="0" pad="PA7"/>
              <signal field="PORTMUX.CTRLC.TCA00" function="TCA0" group="WO" index="0" pad="PA3"/>
              <signal function="TCA0" group="WO" index="1" pad="PA1"/>
              <signal function="TCA0" group="WO" index="2" pad="PA2"/>
              <signal function="TCA0" group="WO" index="3" pad="PA3"/>
            </signals>
          </instance>
        </module>
        <module id="I2119" name="TCB">
          <instance name="TCB0">
            <register-group address-space="data" name="TCB0" name-in-module="TCB" offset="0x0A40"/>
            <signals>
              <signal function="TCB0" group="WO" pad="PA6"/>
            </signals>
          </instance>
        </module>
        <module id="I2129" name="TCD">
          <instance name="TCD0">
            <register-group address-space="data" name="TCD0" name-in-module="TCD" offset="0x0A80"/>
            <signals>
              <signal function="TCD0" group="WOA" pad="PA6"/>
              <signal function="TCD0" group="WOB" pad="PA7"/>
            </signals>
          </instance>
        </module>

EDIT that seems to suggest the outputs are muxable back to PA6/PA7 for B and D timers.

 

EDIT2: sorry, NOT muxable - the TCA0 signal W0 is muxable to EITHER PA3 or PA7 but for B and D it seems the output pin is fixed. But that does seem to suggest you could have A on PA3/PA7 and B on PA6

To be honest this is kind of what happens when you cramp yourself into 8 pin chips!

 

I'll bet in the higher pin count devices the MUXing is more extensive and you get to swap things around?

 

EDIT thought so - this is 1617:

 

while this is the same thing for 212:

 

I wrote #29 from a Tablet.

 

At a PC,   I have downloaded Tiny412, Tiny414 datasheets.   I had already got Tiny817 datasheet (and XMINI)

 

The 414 has got CTRLC.  The 817 has got CTRLC and CTRLD.     The 412 documentation might be intentional.

 

The Tiny817 peripherals are quite nice.   Tiny1617 and Tiny3217 have been added to the family.

 

For any cost sensitive project it is worth setting out your requirements and then looking at EVERY make of controller.    There is not much point in specifying a controller with EVSYS or DAC if you never use them.

Let's face it.   Any 8-pin 4kB project is not going to be very complex.    I bet that there are several suitable make and model of chip.

 

David.