avr_signature(3)

πŸ“¦ version 2.2.1, in fedora 43, fedora 44, opensuse-leap 16.0

πŸŽ€ NAME πŸŽ€

avr_signature β€” the lil' header that tucks your chip's signature into your ELF file, bestie πŸ’…


✨ SYNOPSIS ✨

Detailed Description

Introduction

okay so, the <avr/signature.h> header file is here to let you automatically and easily include the device's signature data in a special section of the final linked ELF file. no manual labour, no drama, it just happens 🫢

and then? that value can be used by programming software to compare the on-device signature with the signature recorded in the ELF file β€” like a lil' vibe check to look for a match before programming the device. match found? slay. no match? we don't proceed πŸ’€

API Usage Example

usage is genuinely so simple, it's giving effortless. just include the header file:

#include <avr/signature.h>

that's it. that's the whole thing 🌈

what does it do tho? it declares a constant unsigned char array, and that array gets initialized with the three signature bytes, MSB first, that are defined in the device I/O header file. then that array is placed in the .signature section in the resulting linked ELF file. iconic behaviour, honestly ✨

the three signature bytes used to initialize the array are these defined macros in the device I/O header file, from MSB to LSB:

  • SIGNATURE_2
  • SIGNATURE_1
  • SIGNATURE_0
πŸ’– heads up bestie: this header file should only be included once in an application. once. one time. do not make it a recurring character πŸ™ˆ

πŸ‘‘ AUTHOR πŸ‘‘

Generated automatically by Doxygen for avr-libc from the source code.


and that's the whole page, angel πŸ¦‹ this one's from avr-libc, version 2.1.0, dated Sat Jan 29 2022 β€” go forth and let your ELF files know who they are πŸ’…β­

πŸ“¦ where this page comes from