*** RATING – 3.0 Out of 5 Stars ***
*** For additional comments, see my early review ***
I was looking forward to evaluating the Atmel AVR Xplain EVK because of its long list of features:
• ATxmega128A1 MCU
• AT90USB USB Gateway (w/ USB bootloader)
• 8MB SDRAW
• 8MB Serial (SPI) Data Flash
• Temperature Sensor
• Potentiometer (to ADC)
• DAC-driven Speaker
• 8 Pushbuttons
• 8 LEDS
• 1 8 Bit Digital Port
• 1 Analog (ADC/DAC/AC) Port (8 lines)
From the User's Guide, the EVK purpose is to "enable the XMEGA user to get started using the XMEGA's peripherals right away and to get an understanding of how to integrate the XMEGA in their own design".
In addition, the Element-14 describes the kit as "not yet available to buy, so the lucky recipients will be among the very few members of the public to actually possess them." So, I was excited, but my excitement was short lived.
1st Disappointment: This is not a "new" kit that is not currently available. It is the 4th version of the Xplain EVK. What's new is programmability through the USB gateway and an embedded bootloader on the AT90USB. The embedded USB bootloader is a good feature. Previous versions used 2 JTAG ports, one for the main MCU and the other for the USB gateway. A warning is given to avoid the JTAG for the AT90USB, so to not overwrite the bootloader.
From Atmel’s website, the kit I received is also described as the motherboard for a series of add-on evaluation boards, like the QTouch Xplained and the Display Xplained (not available yet).
1) CD Content (including e-file documentation) –
The kit did not include a CD, but instead a box label references a website (www.atmel.com/xplain). Aside from the initial User's Guide, it was very hard to find useful information on the EVK. After a few days, I came up with a list of the following documents:
• AVR1907: Xplain Hardware User's Guide (includes USB driver in separate zip file)
• AVR1922: Xplain Board Controller Firmware (includes source code in separate zip file)
• AVR1921: Reprogramming the Xplain AT90USB1287 & ATxmega128A1 firmware
• AVR1000: Getting Started Writing C-Code for XMEGA
• AVR1005: Getting Started with XMEGA
• AVR1016: AVR Training QTouch Xplained (example code)
SUGGESTION: Since many newer kits include a USB port, could a NAND memory chip be added and the documentation be distributed there?
Most of the EVK related documents have not been updated for version 4, but is usable. There is no documentation for evaluating the board features, aside from instructions on how to remove a resistor for making current measurements.
2) Box Content (including written documentation) –
As mentioned in my early review, the only content of the box was the evaluation board itself. The board uses the USB port for power and the interface cable was not included, but it does use a standard mini-B connection (I borrowed a cable from another project). The only information was printed on the box.
3) Evaluation Hardware –
• The hardware is comprised of a main PCB with the above mentioned components/features.
• The full 8 bit analog and digital expansion ports are useful for evaluating the board.
• The serial data flash was useful for evaluating the SPI bus, but it would have been nice to have the SPI available on an expansion port.
• The audio is limited to short sounds and of poor quality.
• The current measurement requires the removal of a zero ohm resistor. Could a removable jumper is used instead?
• Although included, there is no functional implementation of the temperature or potentiometer controls.
4) Software –
• There is no feature demo software. It may be possible to create a virtual COM terminal program, using the USB port, to examine feature like the temperature sensor or potentiometer ADC measurement.
• Two full function IDEs are referenced in the documentation, AVR Studio 4.0(www.atmel.com/dyn/products/tools_card_v2.asp?tool_id=2725) and WinAVR (winavr.sourceforge.net). Both are free. Although the source code files supplied with app note AVR1922, are in neither program's project file format, so you must import them manually.
• Once the source code is compiled, the program can be loaded with the 1) Atmel FLIP software through the USB gateway and bootloader or 2) through the JTAG ports using an Atmel JTAGICE mkll.
5) Closing Comments –
Although, in my opinion, the EVK has some limitations, could be more useful and the documentation could be greatly improved, it does demonstrates the basic features of the Atmel AVR ATxmega128 microcontroller. I hope this is useful feedback and I thank Alistair again for the opportunity to try something new!
Gordon Margulieux
Salem, OR USA
*** RATING – 3.0 Out of 5 Stars ***
*** For additional comments, see my early review ***
I was looking forward to evaluating the Atmel AVR Xplain EVK because of its long list of features:
• ATxmega128A1 MCU
• AT90USB USB Gateway (w/ USB bootloader)
• 8MB SDRAW
• 8MB Serial (SPI) Data Flash
• Temperature Sensor
• Potentiometer (to ADC)
• DAC-driven Speaker
• 8 Pushbuttons
• 8 LEDS
• 1 8 Bit Digital Port
• 1 Analog (ADC/DAC/AC) Port (8 lines)
From the User's Guide, the EVK purpose is to "enable the XMEGA user to get started using the XMEGA's peripherals right away and to get an understanding of how to integrate the XMEGA in their own design".
In addition, the Element-14 describes the kit as "not yet available to buy, so the lucky recipients will be among the very few members of the public to actually possess them." So, I was excited, but my excitement was short lived.
1st Disappointment: This is not a "new" kit that is not currently available. It is the 4th version of the Xplain EVK. What's new is programmability through the USB gateway and an embedded bootloader on the AT90USB. The embedded USB bootloader is a good feature. Previous versions used 2 JTAG ports, one for the main MCU and the other for the USB gateway. A warning is given to avoid the JTAG for the AT90USB, so to not overwrite the bootloader.
From Atmel’s website, the kit I received is also described as the motherboard for a series of add-on evaluation boards, like the QTouch Xplained and the Display Xplained (not available yet).
1) CD Content (including e-file documentation) –
The kit did not include a CD, but instead a box label references a website (www.atmel.com/xplain). Aside from the initial User's Guide, it was very hard to find useful information on the EVK. After a few days, I came up with a list of the following documents:
• AVR1907: Xplain Hardware User's Guide (includes USB driver in separate zip file)
• AVR1922: Xplain Board Controller Firmware (includes source code in separate zip file)
• AVR1921: Reprogramming the Xplain AT90USB1287 & ATxmega128A1 firmware
• AVR1000: Getting Started Writing C-Code for XMEGA
• AVR1005: Getting Started with XMEGA
• AVR1016: AVR Training QTouch Xplained (example code)
SUGGESTION: Since many newer kits include a USB port, could a NAND memory chip be added and the documentation be distributed there?
Most of the EVK related documents have not been updated for version 4, but is usable. There is no documentation for evaluating the board features, aside from instructions on how to remove a resistor for making current measurements.
2) Box Content (including written documentation) –
As mentioned in my early review, the only content of the box was the evaluation board itself. The board uses the USB port for power and the interface cable was not included, but it does use a standard mini-B connection (I borrowed a cable from another project). The only information was printed on the box.
3) Evaluation Hardware –
• The hardware is comprised of a main PCB with the above mentioned components/features.
• The full 8 bit analog and digital expansion ports are useful for evaluating the board.
• The serial data flash was useful for evaluating the SPI bus, but it would have been nice to have the SPI available on an expansion port.
• The audio is limited to short sounds and of poor quality.
• The current measurement requires the removal of a zero ohm resistor. Could a removable jumper is used instead?
• Although included, there is no functional implementation of the temperature or potentiometer controls.
4) Software –
• There is no feature demo software. It may be possible to create a virtual COM terminal program, using the USB port, to examine feature like the temperature sensor or potentiometer ADC measurement.
• Two full function IDEs are referenced in the documentation, AVR Studio 4.0(www.atmel.com/dyn/products/tools_card_v2.asp?tool_id=2725) and WinAVR (winavr.sourceforge.net). Both are free. Although the source code files supplied with app note AVR1922, are in neither program's project file format, so you must import them manually.
• Once the source code is compiled, the program can be loaded with the 1) Atmel FLIP software through the USB gateway and bootloader or 2) through the JTAG ports using an Atmel JTAGICE mkll.
5) Closing Comments –
Although, in my opinion, the EVK has some limitations, could be more useful and the documentation could be greatly improved, it does demonstrates the basic features of the Atmel AVR ATxmega128 microcontroller. I hope this is useful feedback and I thank Alistair again for the opportunity to try something new!
Gordon Margulieux
Salem, OR USA
I recently got introduced to Atmel through a Qtouch seminar that a distributor was offering. The equipment used was this kit, plus a QTouch XPlained add-on board to illustrate capacative touch - very nice btw. I also won (in a raffle) a QT600 kit which was being given away at the end of the seminar. Later on I was also given a XPlain, QTXplain, AVR Dragon and lent an STK600.
I figured, wow, with all this kit theres no way I can't get ALL my projects done. From having no experience w/atmel I went to having six different MCU's and several touch panels. Since the current project I'm working - and probably all future ones - is wireless I purchased an RZ600 to top it off. At first glance there seemed to be a large amount of documentation, app notes and source code. Once I began looking at all of it - for the last month and a half - the docs began to look more vague and the source code was poorly documented. I went to avrfreaks to see if there was anything to fill in the gaps - there is some - but it seems that quite regularly ppl post there and they get hardly more than "RTFM" and "go check google". Sometimes it's well deserved, but it gives the forum the feel that the ppl there just dont wanna be bothered with anything less than expert questions. With such vagueness in alot of the literature entry-level questions are bound to appear.
So, after all this time slogging through App Notes and Data Sheets I have obtained a basic competence with these MCU's and am writing a program to control the radio registers and functions with an STK600/Xmega128a1 and an XPlain board to comminucate back and forth. I thought it would be much easier with all the supposed documentation available but it doesn't go quite far enough.
Coming from the point of view of using Renesas and TI MCU's I am very disappointed with what ATsmell has available. If I had been using Renesas or TI I probably wouldn't have had to code very much at all and a weeks worth of research, or less, would have gotten me straightened out. Whereas currently I am still not quite sure I know all that I need.
So, at this point with all I've seen I would have to agree w/the 3 out of 5 star rating, although the hardware looks like it is top-notch. If you know exactly how to do it, then this is the way to go, if you don't please RTFM before buying to make sure you can get up to speed.
BadHabit,
Documentation and training for new MCU (and their development kits) seems to be an increasing problem for most manufacturers. As more and more functionality is add to these components, their datasheets and manuals can range up to 500 or more pages. Some companies like TI and Microchip (as well as many others) have even started posting YouTube videos to demo their product. As prices for these demo/development kit drop (TI MSP430 value line demo board is only $4.30), some of these video are nothing more than commercials. How many of TI (or Atmel) demo boards will set on the someone's bench due to lack of documentation.
It would be very helpful if websites were not only an afterthought in a marketing phase, but a organizer of product documentation
But the bottom line will always be that experience will only come through digging, coding, testing, digging some more, coding some more, then testing some more.
Regards,
Gordon Margulieux
Garmin AT - Salem, OR USA