ATtiny417 / ATtiny814 / ATtiny816 / ATtiny817

Go To Last Post
338 posts / 0 new

Pages

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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 :)

Last Edited: Wed. Nov 1, 2017 - 11:09 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

That's still 11 bytes more than the STK500 has free - put it to good use!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

[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."

"When you hear hoofbeats, think horses, not unicorns."

"Fast.  Cheap.  Good.  Pick two."

"Read a lot.  Write a lot."

"We see a lot of arses on handlebars around here." - [J Ekdahl]

 

Last Edited: Thu. Nov 2, 2017 - 12:58 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

"Dare to be naïve." - Buckminster Fuller

Last Edited: Thu. Nov 2, 2017 - 12:01 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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 ............ 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

duzern wrote:

El Tangas wrote:

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.

 

I 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

Last Edited: Mon. Nov 6, 2017 - 07:52 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think that's not the right binary, it seems like a test file.

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

El Tangas wrote:

I think that's not the right binary, it seems like a test file.

I 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.

Last Edited: Mon. Nov 6, 2017 - 08:03 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0
  • Precise ULP Timing P4 (ATtiny416)

The board itself with a coupon code that expires 30-Nov-2017 :

Microchip Technology Inc

Microchip

AVR P4 Field Engagement Board (FEB)

http://www.microchip.com/Developmenttools/ProductDetails.aspx?PartNO=ATAVRFEB-P4

 

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So, anyone knows what are those? How many are they?

 

 

 

  • 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]

Last Edited: Sat. Nov 11, 2017 - 07:22 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Man, how did I miss it?...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

El Tangas wrote:
Then we could use avrdude to program these new chips.

AVR Downloader/UploaDEr - Patches: patch #9482, Add support for UPDI and AVR8X

http://savannah.nongnu.org/patch/?9482

by Jan Egil Ruud

...

 

09 Nov 2017

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)

 

...

via http://lists.nongnu.org/archive/html/avrdude-dev/2017-11/msg00010.html

 

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Let'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.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

New arrivals at Mouser :

https://www.mouser.com/new/microchip/microchip-avr-devel-boards/

ATAVRBLE-IoT Development Board (tiny1617)

ATAVRFEB-P4 Development Board (tiny416)

ATtiny416 Xplained Nano Evaluation Kit

https://www.mouser.com/new/microchip/microchip-attiny416-816-mcus/

 

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

http://www.avr-asm-tutorial.net/gavrasm/v37/ReadMe.Txt

...

 

Versions and Changes
--------------------

...

October 2017: Version 3.7

...

- Added: Support for several newer AVR types

(tinyAVR 1-series, 2kB to 32kB inclusive)

 

Januar 2017: Version 3.6
- Added: Support for ATtiny80 und 840 (datasheet not yet available),
  ATtiny102, 104, 417, 814, 816 und 817, def.inc as of Studio version
  7.0-1188

...

via

Logo

Gerd's AVR Assembler

http://www.avr-asm-tutorial.net/gavrasm/index_en.html

...

 

Features

View the ReadMe.Txt for more informations on features. ...

 

...

 

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

YouTube

Microchip Technology

New AVR® ATtiny MCUs Increase System Throughput & Lower Power Consumption in Embedded Applications

Nov 22, 2017

https://www.youtube.com/watch?v=pG7eoXYyC94 (1m7s)

via https://plus.google.com/+MicrochipTech/posts/LmVrNEGxVz7

 

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

KitCarlson wrote:
CodeVisionAVR plans to support the new parts.

HP InfoTech

CodeVisionAVR V3 Revision History

http://hpinfotech.ro/cvavr_revision3.html

V3.32 Commercial Release

  • Compiler
    • Added compiler support for the ATtiny212/214/414/416/1614/1616/1617/3214/3216/3217 and ATA8510 chips
    • ...

 

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

gchapman wrote:

KitCarlson wrote:
CodeVisionAVR plans to support the new parts.

 

 

And further down that release note...

 

Quote:

  • Chip Programmer
    • Added support for the USBASP programmer
    • 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)

"This forum helps those that help themselves."

"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."

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Microchip New tinyAVR Microcontroller Series promo page http://www.microchip.com/promo/t...

"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

"Make XMEGA Great Again!"  - Greg Muth

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well, that shows what THEY think is important.

 

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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.

 

Last Edited: Thu. Feb 1, 2018 - 05:05 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Reported (TPUBSTINY-441).

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

El Tangas wrote:
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.

"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

"Make XMEGA Great Again!"  - Greg Muth

Last Edited: Thu. Feb 1, 2018 - 05:39 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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.

  • 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]

Last Edited: Thu. Feb 1, 2018 - 06:13 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ah, ok, i see it.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

And 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)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It's ok, you already reported, so no need to duplicate. I'll remember the procedure for the next error I find.

Last Edited: Thu. Feb 1, 2018 - 09:15 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

If 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? 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

HEF = High Endurance Flash

 

edit:http://www.microchip.com/design-...

David (aka frog_jr)

Last Edited: Thu. Feb 1, 2018 - 10:21 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

sparrow2 wrote:
Does anyone know what it stands for?

"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...

HEF

From Wikipedia, the free encyclopedia

Hef or HEF may refer to:

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.

Pages