Who ate it? What happened to it?
Or are we supposed to use the "production file" programming interface which does NOT seem as flexible as the old Auto mode?
Ampertronics Pty. Ltd.
* Electronic Design * Custom Products * Contract Assembly
Your question seems to go along with the built-in programmer discussion here:
I don't see the going along here. The other thread is about the modality of the programming window - i.e. an aspect of how you can "navigate" in the UI.
It seems to me that John is asking about actual functionality offered: In the AS4 Auto tab you can choose verification (or not) for individual steps. In AS6 you have the option to verify everything that has been programmed on nothing. Less granularity..
As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here.
No guarantees, but if we don't report problems they won't get much of a chance to be fixed! Details/discussions at link given just above.
"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]
The Auto tab is how I program small runs of board, maybe up to a dozen or so.
Simply preset the other tabs with files location, fuse and lockbits settings, preset the Auto tab with the actions required and then program the chips.
By the way this is the main reason I don't like the Auto read fuse function and disable it.
For large runs I use the same setup to preprogram my keyfob programmers, I have 3 of them which I can now throw away as they are no longer recognised in AS6 as an AVRISP :evil: but that's another story.
For large runs I use the same setup to preprogram my keyfob programmers, I have 3 of them which I can now throw away as they are no longer recognised in AS6 as an AVRISP but that's another story.
Don't throw them away - use AVRDUDE or another command line programmer instead. There are GUIs available on the web.
Right now the production format is just ELF files, where the individual fuse, lock, EEPROM and FLASH data is extracted and programmed in. Adding a dedicated GUI to replicate the AS4 dialog shown above has been added as a future enhancement as there are situations where this is better (such as combining application and bootloader data).
I wonder if I should make a "chip image" utility to read in the various data with AVRDUDE and then use objcopy to create a production ELF? Hrm...
- Dean :twisted:
Make Atmel Studio better with my free extensions. Open source and feedback welcome!
use AVRDUDE or another command line programmer instead
I will simply keep on using AS4 as long as I can, hey I don't have that much longer to live according to the doctor, I'll be really lucky if I last another 30 or 40 years according to his calculations...
I will simply keep on using AS4 as long as I can
© 2019 Microchip Technology Inc.