demos(3avr)

📦
version 2.2.1 · 4 versions
, in ubuntu resolute, ubuntu stonking

💖 demos — the AVR-LibC demo projects page, bestie edition 💖

okay so real talk, this is demos(3avr) from the AVR-LibC manual, and it's basically the tour bus of tiny example projects for AVR microcontrollers. hop in 🚌✨

🌸 NAME 🌸

demos — Demo projects. that's it. that's the whole name. iconic, concise, no notes 💅

✨ SYNOPSIS ✨

🎀 Topics 🎀

  • Combining C and assembly source files
  • A simple project
  • Using the standard IO facilities
  • Example using the two-wire interface (TWI)

🦋 Detailed Description 🦋

So the whole deal here is: there's a bunch of lil demo projects provided to show off several aspects of using the opensource utilities for the AVR controller series. 🫶

⚠️ Keep this in mind and keep it in your heart: these demos serve mainly educational purposes, and are normally not directly suitable for use in any production environment. Usually they've been kept as simple as sufficient to demonstrate one particular feature. so yes bestie, learn from them, don't ship them 🙈

The simple project is somewhat like the "Helloworld!" application for a microcontroller — about the most simple project that can be done. It is explained in good detail, so you, the reader, can understand the basic concepts behind using the tools on an AVR microcontroller. it's giving baby's first blink sketch and honestly? we love her 🌟

The more sophisticated demo project builds on top of that simple project, and adds some controls to it. On its way, it touches a number of AVR-LibC's basic concepts. glow-up arc 🔥

A comprehensive example on using the standard IO facilities intends to explain that complex topic, using a practical microcontroller peripheral setup with one RS-232 connection, and an HD44780-compatible industry-standard LCD display. it's giving full setup energy 😭💖

The Example using the two-wire interface (TWI) project explains the use of the two-wire hardware interface (also known as "I2C") that is present on many AVR controllers.

Finally, the Combining C and assembly source files demo shows how C and assembly language source files can collaborate within one project. While the overall project is managed by a C program part for easy maintenance, time-critical parts are written directly in manually optimized assembly language for shortest execution times possible. Naturally, this kind of project is very closely tied to the hardware design, thus it is custom-tailored to a particular controller type and peripheral setup. As an alternative to the assembly-language solution, this project also offers a C-only implementation (deploying the exact same peripheral setup) based on a more sophisticated (and thus more expensive) but pin-compatible controller. C and asm being besties in one project?? collaboration of the century 🤝💜

Okay so hardware gossip time, because not every demo runs on every board and you NEED to know this 👑

While the simple demo is meant to run on about any AVR setup possible where a LED could be connected to the OCR1[A] output, the large and stdio demos are mainly targeted to the Atmel STK500 starter kit, and the TWI example requires a controller where some 24Cxx two-wire EEPPROM can be connected to.

🚨 For the STK500 demos, the default CPU (either an AT90S8515 or an ATmega8515) should be removed from its socket, and the ATmega16 that ships with the kit should be inserted into socket SCKT3100A3.

The ATmega16 offers an on-board ADC that is used in the large demo, and all AVRs with an ADC feature a different pinout than the industry-standard compatible devices. see? the chip swap is not a vibe choice, it's a pins choice 🧚

In order to fully utilize the large demo, a female 10-pin header with cable, connecting to a 10 kOhm potentiometer will be useful.

For the stdio demo, an industry-standard HD44780-compatible LCD display of at least 16x1 characters will be needed. Among other things, the LCD4Linux project page describes many things around these displays, including common pinouts. LCD lore goes deep fr fr 🌈

👑 Author 👑

Generated automatically by Doxygen for AVR-LibC from the source code. not a human author, just doxygen doing its lil autogen thing, and we respect the hustle 🤖💖

and that's the whole page bestie!! 🎀 this was demos(3avr) — part of AVR-LibC Version 2.2.1, and the footer said demos(3avr) too, so yeah, we came full circle. slay, bye 💅✨🦋

📦 where this page comes from