I started using this microcontroller but I am dealing with the lack of documentation. First of all this is the datasheet. It describes registers and their usage but not a workflow. Which one to set first, which second etc. The ASF Get Started quick guides are very limited to high level staff, like USB protocol etc. At last, there are existing examples which demonstrate but it is a mess with out a documentation.

  • 1
    \$\begingroup\$ Have you never worked with microcontrollers before? This is a pretty typical datasheet. \$\endgroup\$ – Matt Young Jan 27 '16 at 13:18
  • \$\begingroup\$ I have experience with PIC microcontrollers and things were much simpler than that. There is no documentation on how to set things. Only existing examples. \$\endgroup\$ – Oh hi Mark Jan 27 '16 at 13:20
  • \$\begingroup\$ PIC datasheets only call out specific orders to do things when it matters, eg. EEPROM writes. How is this one any different? \$\endgroup\$ – Matt Young Jan 27 '16 at 13:21
  • \$\begingroup\$ @MattYoung Well can you find any quick guides on how to use this microcontroller? How to properly set ADC? Because I can't. \$\endgroup\$ – Oh hi Mark Jan 27 '16 at 13:24
  • 2
    \$\begingroup\$ In that EXACT datasheet there is a whole bleeding section on the ADC that has a functional description, conversion timing, register description with full explanation of what each bit does and means. If that's not good enough for you in terms of a datasheet you're shit out of luck in the industry, because I have only seen less documentation than that in 20 years of work with (semi-)professional devices. \$\endgroup\$ – Asmyldof Jan 27 '16 at 14:20

Good datasheets tell you what the part does, not how to use it for whatever your particular purpose is. It turns out your link is not to a datasheet, some product page apparently, so I can't comment on this particular datasheet directly.

If datasheets provided the hand-holding you are asking for, they would get irritating very fast to everyone that didn't care to use the part in whatever particular way the paint-by-numbers instruction say. Not only would that dilute the real information that everyone else is there to get, but any particular recipe will be wrong in a number of circumstances.

The correct procedure is to read the datasheet to understand how the part works. Then you can synthesize your own method of harnessing those capabilities to achieve what you want. Information beyond that really doesn't belong in a datasheet.

This is what app notes are for. They are examples of how to use parts in particular ways. Go look for app notes related to what you are trying to do.

  • \$\begingroup\$ The page is the devices documents page. The first pdf is the datasheet. \$\endgroup\$ – Oh hi Mark Jan 27 '16 at 13:37
  • \$\begingroup\$ @George: Exactly. The link is to some product page, not a datasheet. No, I'm not going to go digging around to discover the "first pdf" is what I'm actually looking for. Don't be so lazy. \$\endgroup\$ – Olin Lathrop Jan 27 '16 at 13:39
  • \$\begingroup\$ Here you are atmel.com/Images/doc32058.pdf \$\endgroup\$ – Oh hi Mark Jan 27 '16 at 13:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.