However, if you look deeper, you will see that the underlying ATmega4809 (data sheet ATmega4808\/4809<\/a>) as a member of the megaAVR\u00ae series differs significantly from the ATmega328P. And it is precisely this look “under the hood” that this article is about.<\/p>\n In addition to the original Arduino Nano Every, I will also look at an interesting brother from China, which is based on the ATmega4808 and is known as the “Nano Thinary” or “Nano 4808”. The ATmega4808 is very similar to the ATmega4809. For this reason, the manufacturer Microchip has described both microcontrollers together in a data sheet<\/a>. And it also makes sense to cover both boards in one article.<\/p>\n What topics I will cover:<\/p>\n The available options of the boards and their limitations depend on three factors:<\/p>\n Here are some key data for the Arduino Nano Every board:<\/p>\n The same applies to the “Nano 4808” (Nano Thinary), with the following exceptions:<\/p>\n You can get the Arduino Nano Every from the Arduino Store<\/a>. I paid \u20ac12.50 plus tax and shipping, which is relatively cheap for the original boards. For comparison: The Arduino Nano costs \u20ac20.50 in the Arduino Store (as of 10\/23).<\/p>\n I found the “Nano 4808” for about \u20ac7.50 on AliExpress. But allow a few weeks for delivery, at least if you live in Europe.<\/p>\n\n The Arduino Nano Every uses the 48-pin version of the ATmega4809, the “Nano 4808” is based on the 32-pin version of the ATmega4808:<\/p>\n\n Both microcontrollers belong to the megaAVR\u00ae0 series, which differs fundamentally from the “traditional” AVR\u00ae series. For example, programming is done via UPDI (Unified Program Debug Interface) and not as usual via ISP or using the Optiboot bootloader via the UART interface. This is why the boards discussed here do not have a USB-to-serial adapter, but a UPDI programmer. UPDI is a 1-wire interface that you may recognize from my article about the megaTinyCore<\/a> package from Spence Konde. <\/p>\n\n As you can see, the pins of the ATmega4809 are only partially available on the Arduino Nano Every Board. The rest is lost. In some cases, however, you can use PORTMUX to reassign the functions of non-available pins to existing pins.<\/p>\n The pin designations and pin numbers (light blue \/ pink) essentially correspond to those of the ATmega328P-based Arduino Nano. However, there are some differences:<\/p>\n The port pins Pxy <\/em>on which the Arduino pins are based are entirely different from those of the Arduino Nano or Arduino UNO. Sketches that address the ports directly must be rewritten if you transfer them to the Arduino Nano Every.<\/p>\n We will come to the other functions, such as TCA0-x<\/em> or EVENTy<\/em>, in the course of this article.<\/p>\n\n The pinout diagram of the “Nano 4808” differs from the Arduino Nano Every as follows:<\/p>\n I will not explain here in detail how to install board packages. Instructions can be found here<\/a>, for example.<\/p>\n\n The easiest way is to install the “Arduino megaAVR Boards” package, as you do not need to enter an additional board manager URL in the settings. After installation, select the Arduino Nano Every as the board and set the option “None (ATMEGA4809)” under Tools \u2192 “Registers emulation”.<\/p>\n As an alternative, I recommend the MegaCoreX<\/a> package, as it contains libraries for many of the ATmega4809 functions that the standard package does not have. This is particularly useful for those who do not want to deal with registers. You can apply many more settings with this package, such as conveniently converting the reset pin into a normal I\/O pin or changing the clock rate. The documentation on GitHub is exemplary. You can find installation instructions here<\/a>. Don’t worry, it’s done in just a few minutes.<\/p>\n After installation, make the following settings in the Tools menu:<\/p>\n The rest is best left unchanged for now.<\/p>\n\n I tried two options for the “Nano 4808”. One of them was again the MegaCoreX<\/a> package, but I also tried the ThinaryArduino<\/a> package. Do yourself a favor and take the MegaCoreX package!<\/p>\n I do not recommend the ThinaryArduino package, as it is apparently not really maintained. It works in principle, but has some special features:<\/p>\n You can use the AREF pin as a GPIO without any further action. The only limitation: It has a higher capacitance than other pins and is therefore somewhat less responsive. The MegaCoreX package has assigned its own number for the pin, namely 39 for the Arduino Nano Every and 25 for the “Nano 4808”. When using the megaAVR package, you could use it directly via port manipulation (PD7).<\/p>\n Since the ATmega4808\/4809 is flashed via UPDI, you do not need the reset pin to upload the sketches. The MegaCoreX allows you to set the pin as a GPIO via the Tools \u2192 Reset menu. But be careful: If you configure the pin as OUTPUT and press the reset button, you will create a short circuit!<\/p>\n With the megaAVR package, you can apply this change in the boards.txt file. On my computer it is under: “C:\\Users\\Ewald\\AppData\\Local\\Arduino15\\packages\\arduino\\hardware\\megaavr\\1.8.8”. Replace the following line in the file:<\/p>\n This clears the RSTPINCFG bit (no. 3) in the SYSCFG0 register as part of the next upload. As the register can only be written to via UPDI, you have to take the detour via boards.txt. But only go for it if you know exactly what you’re doing!<\/p>\n\n If you limit yourself to the Arduino functions, your sketches should work as usual. It all “feels like Arduino Nano”.<\/p>\n This could be the end of this article. But there is still the exciting world of the megaAVR0 series to discover beneath the Arduino surface. Nevertheless, a little familiarization is required, even if you should already have experience with register programming of AVR microcontrollers. Here is a simple blink sketch as a taster (Arduino Nano Every):<\/p>\n\n For the “Nano 4808”, replace PORTE with PORTC to make the board LED flash.<\/p>\n A statement like I will now try to explain the register programming briefly. For more details, please refer to the application note TB3262<\/a> from Microchip. <\/p>\n The register concept of the megaAVR series can also be found for the megaTiny\u00ae series. If you have worked through this article, you can also use your knowledge there.<\/p>\n\n The registers are organized as structures (data type struct), which you can see from the dot notation in the blink sketch. The name of the structure is the module, the registers are elements of this structure, e.g.<\/p>\n To understand bit masks and bit group configuration masks, let’s take a look at the Control A Register (CTRLA) of Timer B1 as an example. The module is called TCB. However, as the ATmega4809 has four identical Timer B (0, 1, 2, 3), the number is appended to the module name, in general term: “MODULNAMEn<\/strong>.REGISTERNAME”. The CTRLA register of Timer B1 is therefore called: TCB1.CTRLA.<\/p>\n The TCBn.CTRLA registers contain various bits and the CLKSEL bit group:<\/p>\n\n Bit masks are used to set single bits. Their names are formed according to the following scheme:<\/p>\n The module number is omitted. To set the ENABLE bit for Timer B1:<\/p>\n The bit group configuration masks are used for bit groups (also known as bit fields), the names of which are formed as follows:<\/p>\n As an example, we set the TCA clock as clock source for Timer B1:<\/p>\n CLKTCA corresponds to the CLKSEL value 0x2 or 0b10. In the register, CLKSEL is located at bit position 1 and 2, i.e. it is shifted 1 bit to the left. This is why the value of TCB_CLKSEL_CLKTCA_gc is 0x4 or 0b100.<\/p>\n If you want to mask the bit group TCB_CLKSEL, you can use the bit group mask. Here in the general form:<\/p>\n The value of TCB_CLKSEL_gm is 0x6 or 0b110, as you can easily check with In addition, there are the bit and bit group positions:<\/p>\n Unsurprisingly, they indicate the position of the bit or bit group in the register. So if you want to determine the current CLKSEL value of timer TCB1, you could do it like this:<\/p>\n It may all sound a little complicated at first, but you soon get used to this type of notation. It involves a certain amount of writing, but it pays off because the code is still easy to understand even after a few months.<\/p>\n\n If you want to see how the structures for the modules and registers are set up, then take a look at “C:\\Program Files (x86)\\Arduino\\hardware\\tools\\avr\\avr\\include\\avr\\iom4809.h” or “…iom4808.h”.<\/p>\n\n This new way of programming registers takes some getting used to at first. The ATmega4808\/4809 data sheet will help you find your way around. It is organized according to the modules and for each module there is a “Register Summary” with links to the individual registers. <\/p>\n\n As demonstrated by the register summary above, there are a number of registers whose names begin with “DIR” or “OUT”. The “DIR …” registers control which pins are used as INPUT or OUTPUT. With the help of the “OUT …” registers you set the pin level, i.e. HIGH or LOW. The second part of the name means:<\/p>\n You can also write directly to the DIR and OUT registers, but the beauty of OUTSET, OUTCLR, OUTTGL and their “DIR” counterparts is that the instructions are pin-selective. Example:<\/p>\n You can read the status of the pins from the IN registers ( Each pin has its own control register, namely PINxCTRL:<\/p>\n\n The INVEN bit allows you to invert the INPUT and OUTPUT values. PULLUPEN activates the internal pull-up resistor. With ISC you can define the interrupt conditions or switch off the digital function of the pin completely (INPUT_DISABLE):<\/p>\n\n I’ll come back to the blink sketch and show that there are other ways to achieve the same effect:<\/p>\n\n I think the alternatives are fairly self-explanatory. And as already mentioned, to adapt the code to a “Nano 4808”, swap PORTE for PORTC. <\/p>\n\n Here is an example of how you can read the level of individual pins:<\/p>\n\n The following is a simple example of an external interrupt at PB2 (=D5 on the Nano Every). Note that the interrupt is not automatically cleared by calling the ISR. You must “manually” clear the bit in the relevant interrupt flag register.<\/p>\n\n If you use port manipulation like The same code, only with VPORTE instead of PORTE took 503 milliseconds. These are not major differences, but they are differences nonetheless.<\/p>\n The VPORT registers available are DIR, OUT, IN and INTFLAGS.<\/p>\n\n The registers of the PORTMUX module allow you to assign a series of inputs and outputs to alternative pins. Here is the register summary:<\/p>\n\n As an example, we redirect the Timer A outputs. The relevant PORTMUX register is TCAROUTEA. The bit group configuration mask for TCA0[2:0] is PORTn with n = A to F. You would therefore assign the Timer A output pins to Port B in this way:<\/p>\n And this is exactly what is implemented on the Arduino Nano Every, both with the megaAVR and the MegaCoreX package. On the “Nano 4808”, the Timer A outputs are redirected to Port D.<\/p>\n\n If you want to redirect other inputs or outputs, you only need to search for the corresponding bit masks or bit group configuration masks.<\/p>\n\n The event system is really cool! It allows the peripherals, i.e. timers, ADC, USART, etc., to send signals to other peripherals without involving the CPU. Later, I will show you an example of how a timer can regularly trigger ADC measurements. Normally, you would realize this via 8 channels (Channel0 to Channel7) are available for transmitting the signals. The sender of the signal is called the generator, the receiver is the user. Most users have their own event control register in which further settings can be made. These registers are part of the peripheral modules.<\/p>\n\n In the CHANNELn registers (with n = 0 to 7) you define the generator:<\/p>\n\n Most generators can utilise all channels. But there are also exceptions. For example, the pins of Port A can only use channels 0 and 1. Here is a small extract from the table in the data sheet (section 14.5.2):<\/p>\n\n You define the event users in the USERn tab:<\/p>\n\n Replace the “n” in USERn with the name of the user. The complete table can be found in the data sheet in section 14.3.2.4. Here is a snippet:<\/p>\n For a better understanding, let’s take a look at a small example. For the Arduino Nano Every, connect a button to PB0 (D9) that pulls the pin to LOW when pressed. Connect a suitable LED to PB2 (D5).<\/p>\n Now we use the PB0 as event generator and EVOUTB (PB2 \/ D5) as event user. Channels 0 and 1 are available for Port B. In the example, we use Channel 0.<\/p>\n\n PB5, or EVOUTB, reflects the status of PB0. The LED lights up in the normal state and switches off when the button is pressed. This may not be impressive at first glance, but at second glance it is. We do not query the level of PB0, nor have we set up an external interrupt for this purpose. In addition, there are no instructions for switching the LED in the running program. The processes are all controlled in the background without your running program having to do anything. More useful applications will follow later. <\/p>\n\n Rewriting the sketch for the “Nano 4808” is not difficult. This would be an option:<\/p>\n\n The ATmega4809 has:<\/p>\n The ATmega4808 differs only in that it has three Timer B.<\/p>\n\n First, a few general comments on Timer A:<\/p>\n Some registers are identical in Normal and Split Mode. I have noted this accordingly.<\/p>\n This article is not a complete register documentation. I recommend that you also take a look at the data sheet when reading this article.<\/p>\n\n In the control register CTRLA you set the clock divider and enable Timer Counter A.<\/p>\n\n The CLKSEL (Clock Select) bit group defines the divider. The following bit group configuration masks are available for selection:<\/p>\n Use the ENABLE bit to enable TCA0. You can check the setting of CTRLA with Setting the Compare n Enable Bits (CMPnEN) enables the Compare Channel outputs. I will not go into the Auto Lock Update Bit (ALUPD) here. The bit group WGMODE[2:0] defines the Wave Form Generation Mode:<\/p>\n Take it as it is for now, it will become clearer later.<\/p>\n\n The Split Mode is set in the Control D register. It is not relevant whether you make the setting via TCA0.SINGLE.CTRLD or TCA0.SPLIT.CTRLD.<\/p>\n\n In the Interrupt Control Register, you set which interrupts are to be activated. Interrupts are available for compare matches and overflow:<\/p>\n\n The Interrupt Flag Register INTFLAGS is similar to INTCTRL and uses the same bit names and positions.<\/p>\n\n\n
\n
Features of the Arduino Nano Every \/ “Nano 4808”<\/h2>\n\n
\n
Technical data of the boards<\/h3>\n\n
\n
\n
\n
\n
Sources of supply<\/h3>\n\n
Pinout<\/h3>\n\n
![\"The](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/ATmega4808_4809_IC-1024x541.webp\")
<\/a>Pinout Arduino Nano Every<\/h4>\n\n
![\"\"](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2024\/03\/nano_every_pinout-1024x473.webp\")
<\/a>\n
Pinout “Nano 4808”<\/h4>\n\n
![\"Pinout](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/nano_every_4808_pinout-1-1024x563.webp\")
<\/a>\n
Board packages<\/h2>\n\n
Board packages for the Arduino Nano Every <\/h3>\n\n
\n
Board packages for the “Nano 4808” (Thinary)<\/h3>\n\n
\n
analogWrite()<\/code> is only available on pins A6 and A7.<\/li>\nUsing Reset and AREF pins as GPIO<\/h3>\n\n
nona4809.bootloader.SYSCFG0=0xC9<\/code> by:<\/p>\n nona4809.bootloader.SYSCFG0=0xC1<\/code>.<\/p>\nGetting Started<\/h2>\n\n
void setup() {\n PORTE.DIRSET = PIN2_bm; \/\/ set PE2 (D13, LED_BUILTIN) to OUTPUT\n}\n \nvoid loop() {\n PORTE.OUTSET = PIN2_bm; \/\/ set PE2 to HIGH \n delay(200);\n PORTE.OUTCLR = PIN2_bm; \/\/ set PE2 to LOW\n delay(200);\n}<\/pre>\n\nPORTE |= (1<<PE2)<\/code> generates an error message that “PE2” is not defined.<\/p>\n\nRegister programming in C for the megaAVR\u00ae series<\/h2>\n\n
Register<\/h4>\n\n
\n
\n
Bit Masks and Bit Group Configuration Masks<\/h4>\n\n
![\"Arduino](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/10\/TCBn_CTRLA_example-1024x268.png\")
<\/a>\n
TCB1.CTRLA |= TCB_ENABLE_bm;<\/code><\/p>\n\n
TCB1.CTRLA |= TCB_CLKSEL_CLKTCA_gc;<\/code><\/p>\n\n\n
Serial.println(TCB_CLKSEL_gm, BIN)<\/code>.<\/p>\n\nBit Positions and Bit Group Positions<\/h4>\n\n
\n
Serial.println( ((TCB1.CTRLA & TCB_CLKSEL_gm) >> TCB_CLKSEL_gp) );<\/code><\/p>\n\nOrientation in the Data Sheet <\/h4>\n\n
![\"tinyAVR](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/reg_summary_portx-1.webp\")
<\/a>I\/O Control – PORTx Module<\/h2>\n\n
PORTx Register <\/h3>\n\n
DIR, OUT and IN registers<\/h4>\n\n
\n
\n
PORTx.OUT = PINy_bm;<\/code> sets pin y of port x to HIGH and all other pins of port x to LOW.<\/li>\nPORTx.OUTSET = PINy_bm;<\/code> only acts on pin y, i.e. the statement corresponds to PORTx.OUT |= PINy_bm;<\/code>.<\/li>\n<\/ul>\ndigitalRead()<\/code>, so to speak). However, if you write a bit to the PORTx.IN register, the corresponding bit is toggled in PORTx.OUT. The IN register is the counterpart to the PINx register of traditional AVR microcontrollers. <\/p>\n\nControl Register PINxCTRL <\/h4>\n\n
![\"Arduino](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/Reg_PORTx_PINx_CTRL-1024x82.png\")
<\/a>![\"ISC[2:0]](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/PINxCTRL_ISC_table.webp\")
<\/a>Example Sketches for PORTx<\/h3>\n\n
Switching Pins<\/h4>\n\n
void setup() {\n PORTE.DIRSET = PIN2_bm; \/\/ set PE2 (D13) to OUTPUT\n \/\/ PORTE.DIR |= (1<<2);\n \/\/ PORTE.DIR |= (1<<PIN2_bp); \/\/ bp = bit position\n}\n\nvoid loop() {\n PORTE.OUTSET = PIN2_bm; \/\/ set PE2 to HIGH\n \/\/ PORTE.OUT |= PIN2_bm;\n delay(200);\n PORTE.OUTCLR = PIN2_bm;\n \/\/ PORTE.OUT &= ~PIN2_bm; \n delay(200);\n \n \/\/ Alternative: toggle pin:\n \/\/ PORTE.OUTTGL = PIN2_bm;\n \/\/ delay(200); \n}<\/pre>\n\nReading Pin Levels <\/h4>\n\n
void setup() {\n Serial.begin(115200);\n PORTB.DIRCLR = PIN2_bm; \/\/ PB2 = D5 (for the Nano4808 select a different pin)\n}\n\nvoid loop(){\n if(PORTB.IN & PIN2_bm){\n Serial.println(\"HIGH\");\n }\n else{\n Serial.println(\"LOW\");\n }\n delay(1000);\n}<\/pre>\n\nSetting up Interrupts<\/h4>\n\n
volatile bool event = false;\n\nISR(PORTB_PORT_vect){\n PORTB.INTFLAGS = PIN2_bm; \/\/ clear interrupt\n event = true;\n}\n\nvoid setup() {\n Serial.begin(115200);\n PORTB.DIRCLR = PIN2_bm; \/\/ redundant in this case\n PORTB.PIN2CTRL = PORT_PULLUPEN_bm | PORT_ISC_BOTHEDGES_gc; \n}\n\nvoid loop(){\n if(event){\n Serial.println(\"Interrupt!\");\n event = false;\n }\n}<\/pre>\n\nVirtual Ports<\/h4>\n\n
PORTB.OUT = (1 << 2);<\/code>, you should use the virtual port registers instead of the port registers. To do this, simply place a “V” before PORTx, i.e.: VPORTB.OUT = (1 << 2);<\/code>. The virtual ports are copies of the ports in the lower address space. Port manipulations are performed faster with virtual ports. It took 629 milliseconds to execute the following code:<\/p>\nfor(unsigned long i=0; i<1000000;i++){\n PORTE.OUT = 0;\n PORTE.OUT = (1<<2);\n}<\/pre>\n\nReassigning Inputs \/ Outputs – PORTMUX Module<\/h2>\n\n
![\"Register](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/Reg_Summary_PORTMUX.png\")
<\/a>\n
PORTMUX.TCAROUTEA = PORTMUX_TCA0_PORTB_gc;<\/code><\/li>\n<\/ul>\nThe Event System – EVSYS Module<\/h2>\n\n
delay()<\/code>, millis()<\/code> or interrupts. All these options take a certain amount of time and can make the code complex.<\/p>\nEVSYS Register<\/h3>\n\n
CHANNELn Register – Definition of the Generator <\/h4>\n\n
![\"Arduino](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/Reg_EVSYS_CHANNELn-1024x85.webp\")
<\/a>![\"Event](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/EVSYS_generators.webp\")
<\/a>Register USERn – Definition of Users<\/h4>\n\n
![\"Register](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/Reg_EVSYS_USER-1024x88.webp\")
<\/a>![\"Event](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/EVSYS_users.webp\")
<\/a>A simple Event System Example<\/h3>\n\n
void setup() {\n PORTB.DIRSET = PIN2_bm; \/\/ PB2 (D5) as OUTPUT\n PORTB.DIRCLR = PIN0_bm; \/\/ PB0 (D9) as INPUT\n PORTB.PIN0CTRL = PORT_PULLUPEN_bm;\n \n EVSYS.CHANNEL0 = EVSYS_GENERATOR_PORT1_PIN0_gc; \/\/ PB0 is event generator for channel 0\n EVSYS.USEREVOUTB = EVSYS_CHANNEL_CHANNEL0_gc; \/\/ EVOUTB is user of event channel 0\n}\n\nvoid loop(){}<\/pre>\n\nVariant for the “Nano 4808”<\/h4>\n\n
void setup() {\n PORTA.DIRSET = PIN2_bm; \/\/ PA2 (D4)\n PORTA.DIRCLR = PIN0_bm; \/\/ PA0 (D2)\n PORTA.PIN0CTRL = PORT_PULLUPEN_bm;\n \n EVSYS.CHANNEL0 = EVSYS_GENERATOR_PORT0_PIN0_gc; \n EVSYS.USEREVOUTA = EVSYS_CHANNEL_CHANNEL0_gc;\n}\n\nvoid loop(){}<\/pre>\n\nThe Timers of the Arduino Nano Every \/ “Nano 4808”<\/h2>\n\n
\n
Timer A – Module TCAn<\/h2>\n\n
\n
millis()<\/code> or delay()<\/code>. You should therefore not change the divider if you are using the Arduino megaAVR package.<\/strong> The Timer A clock is thus set to 16000000 MHz \/ 64 = 250 kHz. The MegaCoreX package also uses Timer B3 (or B2 for the “Nano 4808”) for delay()<\/code> and millis()<\/code>. However, Timer B3 uses the system clock, so you can adjust the Timer A divider without side effects on Timer B.<\/li>\nTimer A Registers for Normal (Single) Mode<\/h3>\n\n
Control A Register TCAn.CTRLA<\/h4>\n\n
![\"TCAn.CTRLA](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/10\/Reg_TCA_CTRLA-1024x82.png\")
<\/a>![\"Arduino](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/TCA0_CLKSEL_options.png\")
<\/a>Serial.println(TCA0.SINGLE.CTRLA)<\/code>. The output should be 0b1011, i.e. the timer is enabled, and the divider is 64, so you do not need to enable the timer yourself. And once again: When using the megaAVR package, you should not change this setting.<\/p>\n\nControl B Register TCAn.CTRLB<\/h4>\n\n
![\"TCAn.CTRLB](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/10\/Reg_TCA_CTRLB-1024x83.png\")
![\"Arduino](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/TCA0_WGMODES.png\")
Control D Register TCAn.CTRLD<\/h4>\n\n
![\"Arduino](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/10\/Reg_TCA_CTRLD-1024x78.png\")
<\/a>Interrupt Control Register TCAn.INTCTRL<\/h4>\n\n
![\"Arduino](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/10\/Reg_TCA_INTCTRL-1024x79.png\")
<\/a>Event Control Register TCAn.EVCTRL<\/h4>\n\n
![\"Arduino](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/Reg_TCA_EVCTRL-1024x89.webp\")
<\/a>![\"EVACT](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2023\/11\/TCA0_EVCTRL_EVACT_table.webp\")