ATtiny417 / ATtiny814 / ATtiny816 / ATtiny817

Go To Last Post
322 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.)

Happy 75th anniversary to one of the best movies ever made! Rick Blane [Bogart]: "Of all the gin joints, in all the towns, in all the world, she walks into mine."

 

"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

Pages