Workflow for Creating an Xmega Project and Legality

Go To Last Post
5 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all,

 

I am wondering what your workflow is for creating an Xmega project.

Do you use the ASF Wizard modules to get, say, your clock or SPI initialized, or do you do it from scratch?

Is your Xmega workflow different from your Tiny/Mega workflow? If so, how?

 

I'm also curious about legalities in case anyone is aware

Is it okay to use Atmel modules to create a saleable product?

 

Thanks.

 

Let me know if I'm posting a bit much on the Xmega forum.

Last Edited: Wed. Aug 2, 2017 - 07:01 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I don't bother with the ASF for anything other than the USB stack, and even that I'm moving away from now. It's easier to just program the peripheral registers directly than to try to figure out the poorly documented APIs that Atmel created for setting them up.

 

You can sell products with ASF code in them. I do.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I guess the question is do you want to spend you time/effort learning registers/bits from a datasheet or learning what API there are and how to invoke them.

 

ASF comes into its own when you want to use a peripheral that is so complex that it would be very difficult to work out how to operate it from reading the datasheet alone. I think only USB and CAN really fall into that category.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The datasheet is much clearer and easier to use than the API documentation.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

And, of course, all xMega projects are illegal

274,207,281-1 The largest known Mersenne Prime

Measure twice, cry, go back to the hardware store