Warning: Grumpy Old Chuff. Reading this post may severely damage your mental health.
Oh, and it looks like they did a general documentation makeover. AVR1907 has a new release 4/10, and there is also a a new (for me) AVR1921.
Stealing Proteus doesn't make you an engineer.
Since the Xplain has been released, the competitors had introduced dozens of new MCUs (especially Cortex M0) supported with cheap and fully documented starter kits. I'm afraid the complete XMega line is doomed with such a "speedy" support.
We don't know if there isn't a secret extremely high volume buyer behind the scenes, so Atmel doesn't have to worry about sales of Xmegas.
But if there isn't, well, I have already written a few times what I think about Xmegas and Atmel's information policy (if someone wants to find out where Comical Ali ended up, I'd recommend to thoroughly check Atmel's PR department, esp. the management layer).
I am personally overwhelmed by the proliferation of offerings and the task of keeping up with what is real, what is vapor, and what is a flash in the pan.
I don't mean this to hijack the Xplain thread, its just that I'm not sure how to place the Xplain tools in perspective.
So where do we find out about who is really using the new stuff and what their reasons are?
flash in the pan
"I wish I were dumber so I could be more certain about my opinions. It looks fun." -- Scott Adams
let's restrict that to Spring 2010.
Ampertronics Pty. Ltd.
* Electronic Design * Custom Products * Contract Assembly
He means the real spring, not the fake aussie one. :D
The Board helps those that help themselves.
Hrmph. They copied my XPLAINBridge code idea with the mode switch jumper, but only implemented mass storage/serial bridge rather than a serial bridge/PDI programmer. Boo. For what it's worth, my LUFA Mass Storage demos will also work fine on the XPLAIN - if anyone thinks its worthwhile, I can integrate it into the XPLAINBridge firmware in addition to the serial port.
If you want to program the XPLAIN without an external programmer, my alternative firmware is still the best/only option.
Interestingly, it looks like they've rolled their own USB code for the demo, instead of using their own (or even my) framework.
- Dean :twisted:
Make Atmel Studio better with my free extensions. Open source and feedback welcome!
After finally having some time to look at the code, this does not look like the source code of the demo that comes on the Xplain. But there seems to be some interesting stuff included, including touchscreen software (QTouch Xplained?), and a tiny file system.
Has anyone here tried to build any of the applications using this source & framework (AVR1922) provided by Atmel?
I am getting tons of silly errors because the makefiles are not configured properly :cry:
even after using the support document AVR1913
Please let me know if you have tried this out.
The build system of AVR1922 is a good example of the road to hell being paved with good intentions. It is one or two orders of magnitude to complex for the task at hand (81 separate makefiles vs. just 87 C files to compile ...). I bet it is the baby of a single hero / lead programmer / lead architect at Atmel, personally exercising control over it.
There is at least one hidden bug somewhere in the mess, preventing one from separately compiling the uart-loopback example. You need to add V=1 to the command line to compile it
make V=1 CONFIG=xplain-bc
make V=1 CONFIG=xplain-bc
© 2020 Microchip Technology Inc.