This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

A Question For Atmel Chip Users

I actually had a question for Atmel chip users.

I've seen a number of posts for people using Atmel chips and was curious as to why you use Keil. I've used their AVR Studio tool and found it to be a very good tool and their support at AVR Freaks is second to none (no offense, Keil forum people). So my question is why would you choose to pay money to buy Keil (or even if you have that tool already) rather than use AVR Studio, which is specifically designed for use with Atmel chips?

I was just curious.

Parents
  • Actually, that makes perfect sense. I guess I overestimated how much I thought AVR Studio actually supported (and underestimated what is supported by Keil when it comes to AVR chips).

    Good point about software consolidation though. I jump between Cypress, Atmel, Texas Instruments, and VB.NET (I know that's not embedded but it's coding) fairly regularly so I can definitely see the advantage of having a single software package (though it is annoying you have to pay for each package separately through Keil but I guess that's more reason to pick a single architecture and stick with it). Especially when you leave a large piece of code alone for a while and then have to come back to it later and remember the individual differences of each compiler!

    Thanks for clearing that up!

Reply
  • Actually, that makes perfect sense. I guess I overestimated how much I thought AVR Studio actually supported (and underestimated what is supported by Keil when it comes to AVR chips).

    Good point about software consolidation though. I jump between Cypress, Atmel, Texas Instruments, and VB.NET (I know that's not embedded but it's coding) fairly regularly so I can definitely see the advantage of having a single software package (though it is annoying you have to pay for each package separately through Keil but I guess that's more reason to pick a single architecture and stick with it). Especially when you leave a large piece of code alone for a while and then have to come back to it later and remember the individual differences of each compiler!

    Thanks for clearing that up!

Children
No data