There are several reasons why the mEDBG does not perform to the same level as the EDBG/Atmel-ICE.
I can't really list everything here, but the short answer is that the EDBG/Atmel-ICE are more polished products than the mEDBG.
It has nothing to do with deliberately keeping it slower for the sake of sales, but rather the time spent on the mEDBG implementation vs the EDBG/Atmel-ICE implementation.
Edit: Even though the firmware binary is 28657 bytes, keep in mind that there is also a 4k bootloader in there, which leaves about 15 bytes of flash :)
Ah-ha. That was my understanding. i.e. the 32u4 was full.
.
At some time in the past, I had an XMINI that or AS version that would not update the firmware.
I had to solder a 0.05" header and replace the firmware directly with an ATMEL-ICE. As far as I can remember the binary was almost the full 32kB.
.
Anyway the XMINI updated properly after this. In practice it is easier to develop with ATMEL-ICE and regular external AVR board.
For a trivial mod, the XMINI works well enough.
.
David.
The STK500 has only got an 8kB AVR. To fit encrypted bootloader as well as the application firmware.
.
The real mystery is the Dragon. It seems to have "big enough" chips. But moderate performance.
.
David.
This datasheet doesn't have the memory map diagram in section 6.2, while this one has a ridiculously small diagram. These are the new Microchip style datasheets, I suppose they decided they must be less than 500 pages at any cost. I'm all for more compact documents, but not sacrificing readability like this.
I guess they use the same cut and paste guy as Atmel :(
Fig 8-4 has addr of registers (that don't exist), so this is still cut and past cut and paste ............
About the encryption, it seems only the "good stuff", like Atmel-ICE firmware, is encrypted.
Oh no, you figured out our big secret that the mEDBG is not encrypted :)
vidmo wrote:
Atmel gave us all answer:
Though, there is minor "thing" with EEPROM, which I'm gonna save for myself for now...
This may or may not be the EEPROM map for the mEDBG, the aboslute address for each field in the EEPROM is (512 * bank) + address.
The important one to get right for homebrews is FIRE register which tells Atmel Studio which firmware image to use when the tool is upgraded.
The serial number, kit name, manufacturer name and target name are ASCII '\0' terminated strings.
Posted by JohanEkdahl: Sat. Nov 11, 2017 - 07:21 PM
1
2
3
4
5
Total votes: 0
Sheet, page 19:
General Purpose I/O Registers
The ATtiny417/817 devices provide four General Purpose I/O Registers. These registers can be used for storing any information, and they are particularly useful for storing global variables and interrupt flags. General Purpose I/O Registers, which recide in the address range 0x1C - 0x1F, are directly bit-accessible using the SBI, CBI, SBIS, and SBIC instructions.
(The spelign eror is Microchip/Atmels, not mine.)
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]
Add support for the UPDI interface. This programming and debugging interface is used in the AVR8X (2017->) series of devices and is supported in JTAGICE3, AtmelICE, EDBG, mEDBG, nEDBG and PowerDebugger.
Specification is located here: (will post a link when it finally goes public)
By adding support for UPDI it opens up for supporting the AVR8X range of devices; ATtiny212 - ATtiny416 - ATtiny817 - ATtiny1617 - ... (To be continued)
The chip programmer now supports AVRISP MkII, AVR Dragon, STK600, JTAGICE mKII, JTAGICE3 and AT ATMELICE without the need for Atmel Studio to be installed
(my bold)
#1 This forum helps those that help themselves
#2 All grounds are not created equal
#3 How have you proved that your chip is running at xxMHz?
#4 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand." - Heater's ex-boss
I found a small error in the datasheet, in the UPDI chapter.
This is part of the procedure to program the User Row on a locked chip, via UPDI:
But in the relevant register, this bit is described as read only. This is an error; I've verified that this bit is indeed reset by writing a '1' to it, so it should be R/W in the datasheet, with the usual note that it is cleared by writing a '1', like several other AVR flags.
I found a small error in the datasheet, in the UPDI chapter.
Nice. Assuming that the procedure was written correctly to begin with, and that the error is indeed an error based on that assumption, then the same applies to the ATtiny1614/1616/1617 datasheet as well.
You found it, have you written up a support ticket yet?
EDIT: Morten please add the ATtiny1614/1616/1617 datasheet to the report.
"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick
Actually, I'm not exactly sure of the best way to report datasheet errors. I don't feel so comfortable sending this to some generic Microchip mail, will they read it?
I know some former Atmel people are active here, so I report them here, at least they are visible to everyone.
Posted by JohanEkdahl: Thu. Feb 1, 2018 - 06:10 PM
1
2
3
4
5
Total votes: 0
There is a specific "channel" for reporting errors in technical documentation. Go to microchip.com, then Contact Us (at bottom of page), then under Literature Requests there is a specific link for reporting document errors.
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]
#3 How have you proved that your chip is running at xxMHz?
#4 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand." - Heater's ex-boss
Make sure you are looking in the latest, Microchip branded, datasheets. Not the original Atmel one.
#1 This forum helps those that help themselves
#2 All grounds are not created equal
#3 How have you proved that your chip is running at xxMHz?
#4 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand." - Heater's ex-boss
I'm using attiny814 as my target dev. I'm in progress to build programmer for updi mode.
I had design 5 modes (ISP, HVPP, HVSP, PDI,TPI[lo & hv]). UPDI is the last mode.
I need more avr chip for testing and added to programmer database. I'ts hard for me to get samples where I leave (in Indonesia), may be anyone can help me to get sample from Microchip.
I'll publish lite version after finishing UPDI mode.
PC software created using Lazarus (can be compiled for windows, linux, mac), for now I had only windows.
Also I hope can build for Android too, that support usb host (usb otg)
There are several reasons why the mEDBG does not perform to the same level as the EDBG/Atmel-ICE.
I can't really list everything here, but the short answer is that the EDBG/Atmel-ICE are more polished products than the mEDBG.
It has nothing to do with deliberately keeping it slower for the sake of sales, but rather the time spent on the mEDBG implementation vs the EDBG/Atmel-ICE implementation.
Edit: Even though the firmware binary is 28657 bytes, keep in mind that there is also a 4k bootloader in there, which leaves about 15 bytes of flash :)
- Log in or register to post comments
TopAh-ha. That was my understanding. i.e. the 32u4 was full.
.
At some time in the past, I had an XMINI that or AS version that would not update the firmware.
I had to solder a 0.05" header and replace the firmware directly with an ATMEL-ICE. As far as I can remember the binary was almost the full 32kB.
.
Anyway the XMINI updated properly after this. In practice it is easier to develop with ATMEL-ICE and regular external AVR board.
For a trivial mod, the XMINI works well enough.
.
David.
- Log in or register to post comments
TopThat's still 11 bytes more than the STK500 has free - put it to good use!
- Log in or register to post comments
TopThe STK500 has only got an 8kB AVR. To fit encrypted bootloader as well as the application firmware.
.
The real mystery is the Dragon. It seems to have "big enough" chips. But moderate performance.
.
David.
- Log in or register to post comments
TopThis datasheet doesn't have the memory map diagram in section 6.2, while this one has a ridiculously small diagram. These are the new Microchip style datasheets, I suppose they decided they must be less than 500 pages at any cost. I'm all for more compact documents, but not sacrificing readability like this.
- Log in or register to post comments
Top[never mind...]
"Experience is what enables you to recognise a mistake the second time you make it."
"Good judgement comes from experience. Experience comes from bad judgement."
"Wisdom is always wont to arrive late, and to be a little approximate on first possession."
"When you hear hoofbeats, think horses, not unicorns."
"Fast. Cheap. Good. Pick two."
"We see a lot of arses on handlebars around here." - [J Ekdahl]
- Log in or register to post comments
Tophttp://start.atmel.com/#examples/attiny416
Edit: URL
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopI guess they use the same cut and paste guy as Atmel :(
Fig 8-4 has addr of registers (that don't exist), so this is still cut and past cut and paste ............
- Log in or register to post comments
TopI made EEPROM files for UPDI, TPI, SWD and DW/ISP according to duzern's map. UPDI and ISP works, I didn't test rest. They are uploaded with FLASH files on my google drive: https://drive.google.com/open?id=0B3VyJZzWwjj5UU5xem1mUDRHaUU
- Log in or register to post comments
TopI think that's not the right binary, it seems like a test file.
- Log in or register to post comments
TopI edited link in previous post. You have to upload FLASH hex first, and than corresponding EEPROM binary dat file.
@edit I added elf files for simplicity. They contain both FLASH and EEPROM.
- Log in or register to post comments
TopThe board itself with a coupon code that expires 30-Nov-2017 :
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopSo, anyone knows what are those? How many are they?
- Log in or register to post comments
TopSheet, page 19:
(The spelign eror is Microchip/Atmels, not mine.)
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]
- Log in or register to post comments
TopMan, how did I miss it?...
- Log in or register to post comments
Topvia http://lists.nongnu.org/archive/html/avrdude-dev/2017-11/msg00010.html
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopLet's see how it goes. I'm working on something like that too, but if the avrdude guys make it talk UPDI, so much the better.
- Log in or register to post comments
Topa fyi to all :
https://www.avrfreaks.net/forum/enabling-xtiny-updi
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopNew arrivals at Mouser :
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topvia
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topvia https://plus.google.com/+MicrochipTech/posts/LmVrNEGxVz7
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopAnd further down that release note...
#1 This forum helps those that help themselves
#2 All grounds are not created equal
#3 How have you proved that your chip is running at xxMHz?
#4 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand." - Heater's ex-boss
- Log in or register to post comments
TopMicrochip New tinyAVR Microcontroller Series promo page http://www.microchip.com/promo/t...
"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick
"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc
"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3
"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." - Marcus Aurelius
- Log in or register to post comments
TopWell, that shows what THEY think is important.
Jim
Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net
- Log in or register to post comments
TopI found a small error in the datasheet, in the UPDI chapter.
This is part of the procedure to program the User Row on a locked chip, via UPDI:
But in the relevant register, this bit is described as read only. This is an error; I've verified that this bit is indeed reset by writing a '1' to it, so it should be R/W in the datasheet, with the usual note that it is cleared by writing a '1', like several other AVR flags.
- Log in or register to post comments
TopReported (TPUBSTINY-441).
:: Morten
(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)
- Log in or register to post comments
TopYou found it, have you written up a support ticket yet?
EDIT: Morten please add the ATtiny1614/1616/1617 datasheet to the report.
"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick
"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc
"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3
"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." - Marcus Aurelius
- Log in or register to post comments
TopActually, I'm not exactly sure of the best way to report datasheet errors. I don't feel so comfortable sending this to some generic Microchip mail, will they read it?
I know some former Atmel people are active here, so I report them here, at least they are visible to everyone.
- Log in or register to post comments
TopThere is a specific "channel" for reporting errors in technical documentation. Go to microchip.com, then Contact Us (at bottom of page), then under Literature Requests there is a specific link for reporting document errors.
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]
- Log in or register to post comments
TopAh, ok, i see it.
- Log in or register to post comments
TopAnd if you do, include the tracking number I mentioned (just so that support can connect the dots).
:: Morten
(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)
- Log in or register to post comments
TopIt's ok, you already reported, so no need to duplicate. I'll remember the procedure for the next error I find.
- Log in or register to post comments
TopIf you look in the microchip AVR selector guide these xtinys EEPROMs are called HEF where all others are just EEPROMS.
I checked the data sheet but it don't have HEF in the text!
Does anyone know what it stands for?
- Log in or register to post comments
TopHEF = High Endurance Flash
edit:http://www.microchip.com/design-...
David (aka frog_jr)
- Log in or register to post comments
Toptiny414 is a new arrival at Mouser :
https://www.mouser.com/new/microchip/microchip-attiny414-mcus/
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top"HEF" just died, didn't he? https://en.wikipedia.org/wiki/Hu...
I'm glad you got what you really needed from the frog, sparrow, as when I used Google for the "hef" I found all kinds of meanings...
No flash memory among the choices. ;)
You can put lipstick on a pig, but it is still a pig.
I've never met a pig I didn't like, as long as you have some salt and pepper.
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopComplete guess: High Endurance Flash perhaps?
- Log in or register to post comments
Top"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick
"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc
"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3
"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." - Marcus Aurelius
- Log in or register to post comments
TopHi All,
Anyone know device id for ATtiny417/814/816/817 ?
I can't find information about it in datasheet.
Thanks
- Log in or register to post comments
TopDatasheet
6. MEMORIES
-6.9 FUSES
or page 20 in Full datasheet.
- Log in or register to post comments
Top6.7 Signature Bytes
- Log in or register to post comments
TopThanks for replied.
Still can,t find it.
I mean signature bytes.
Ex. 1E9315 for Attiny841
Thanks
- Log in or register to post comments
Top#1 This forum helps those that help themselves
#2 All grounds are not created equal
#3 How have you proved that your chip is running at xxMHz?
#4 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand." - Heater's ex-boss
- Log in or register to post comments
TopMake sure you are looking in the latest, Microchip branded, datasheets. Not the original Atmel one.
#1 This forum helps those that help themselves
#2 All grounds are not created equal
#3 How have you proved that your chip is running at xxMHz?
#4 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand." - Heater's ex-boss
- Log in or register to post comments
TopThe data sheet of microchip was not made in time.
- Log in or register to post comments
TopYou can also get all the signatures for the new chips from the latest version of avrdude.conf.
I extracted these with grep:
family tinyAVR-0: # ATtiny202 signature = 0x1E 0x91 0x23; # ATtiny204 signature = 0x1E 0x91 0x22; # ATtiny402 signature = 0x1E 0x92 0x23; # ATtiny404 signature = 0x1E 0x92 0x26; # ATtiny406 signature = 0x1E 0x92 0x25; # ATtiny804 signature = 0x1E 0x93 0x25; # ATtiny806 signature = 0x1E 0x93 0x24; # ATtiny807 signature = 0x1E 0x93 0x23; # ATtiny1604 signature = 0x1E 0x94 0x25; # ATtiny1606 signature = 0x1E 0x94 0x24; # ATtiny1607 signature = 0x1E 0x94 0x23;family tinyAVR-1: # ATtiny212 signature = 0x1E 0x91 0x21; # ATtiny214 signature = 0x1E 0x91 0x20; # ATtiny412 signature = 0x1E 0x92 0x23; # ATtiny414 signature = 0x1E 0x92 0x22; # ATtiny416 signature = 0x1E 0x92 0x21; # ATtiny417 signature = 0x1E 0x92 0x20; # ATtiny814 signature = 0x1E 0x93 0x22; # ATtiny816 signature = 0x1E 0x93 0x21; # ATtiny817 signature = 0x1E 0x93 0x20; # ATtiny1614 signature = 0x1E 0x94 0x22; # ATtiny1616 signature = 0x1E 0x94 0x21; # ATtiny1617 signature = 0x1E 0x94 0x20; # ATtiny3214 signature = 0x1E 0x95 0x20; # ATtiny3216 signature = 0x1E 0x95 0x21; # ATtiny3217 signature = 0x1E 0x95 0x22;family megaAVR-0: # ATmega3208 signature = 0x1E 0x95 0x52; # ATmega3209 signature = 0x1E 0x95 0x53; # ATmega4808 signature = 0x1E 0x96 0x50; # ATmega4809 signature = 0x1E 0x96 0x51;- Log in or register to post comments
TopThank you for all of you who replied.
I'm using attiny814 as my target dev. I'm in progress to build programmer for updi mode.
I had design 5 modes (ISP, HVPP, HVSP, PDI,TPI[lo & hv]). UPDI is the last mode.
I need more avr chip for testing and added to programmer database. I'ts hard for me to get samples where I leave (in Indonesia), may be anyone can help me to get sample from Microchip.
I'll publish lite version after finishing UPDI mode.
PC software created using Lazarus (can be compiled for windows, linux, mac), for now I had only windows.
Also I hope can build for Android too, that support usb host (usb otg)
Thaks
- Log in or register to post comments
TopIs it possible to program attiny817 / 1616 via eclipse?
- Log in or register to post comments
TopPages