ATtiny417 / ATtiny814 / ATtiny816 / ATtiny817

Go To Last Post
321 posts / 0 new

Pages

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

theusch wrote:

Who-me wrote:
Q: can USB-UARTS really manage that 0.1ms inter-char spacing ??. There are many buffers in play here.. plus the 1ms USB quanta effects. Seem more optimistic than realistic ?

 

I guess it would depend on how you feed it, wouldn't it?

 

The Python code seems to be attempting to space the bytes 100us apart, which is what is fed into the channel.

My point is the USB buffers and USB packet quanta, will not keep anything like 100us byte spacing.

The average data rate can be paced (assuming Python can deliver a 0.1ms delay), but the buffering means there is no guarantee of 100us between each byte.

Anyone got a Tiny817 + Python, who can comment out that delay and check operation ?

 

theusch wrote:

[without doing any research] I'd think that if my AVR fed my FT232R a continuous "packet" of bytes that the FT wouldn't send each individually 1ms apart. 

Well yes, however that's going in the other direction. The FS USB frame is 1ms, and the PC will read multiple bytes in that time, if they are waiting. The highest FS USB UART speed in theory, is around 9MBd (12MBd-overhead)

HS USB has a 125us frame (and larger buffers)

Last Edited: Wed. Apr 26, 2017 - 09:58 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

donotdespisethesnake wrote:
Still seem to be some supply issues, but I think I can get the various bits without waiting with a combination of suppliers.
Mouser did sell all of their stock of tiny817; Mouser has placed orders for 2 reels of tiny817 (both temperature ratings) with an ETA of about one month from now.

In the meantime, microchipDIRECT has 3 reels of tiny817 125C with a low minimum (25) plus the partial reel fee.

tiny1617 - microchipDIRECT has more than 3 reels (low minimum, partial reel fee)

donotdespisethesnake wrote:
I guess I also need to bite the bullet and get an ATMEL-ICE while I am at it ...
Surprised that microchipDIRECT sold all their stock of the full kit; it has a one three month lead.

 


http://www.mouser.com/Semiconductors/Embedded-Processors-Controllers/_/N-6hpef?Keyword=attiny817

http://new.microchipdirect.com/ProductSearch.aspx?keywords=attiny817

http://new.microchipdirect.com/ProductSearch.aspx?keywords=attiny1617

http://new.microchipdirect.com/ProductSearch.aspx?keywords=atatmel-ice

 

Edit : strikethru

 

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

Last Edited: Mon. May 22, 2017 - 10:57 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Surely the clearing out of the ICE was intentional. They sold off at a discount so they can fill up with a new batch where the housing does not say "Atmel"..

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: Thu. Apr 27, 2017 - 03:59 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It is quite plausible that the "ibdly" inter-char spacing is a relic from early debugging, or from before the correct two stop-bits configuration was in place.  UPDI can handle a much tighter byte-stream.

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

mraardvark wrote:

It is quite plausible that the "ibdly" inter-char spacing is a relic from early debugging, or from before the correct two stop-bits configuration was in place.  UPDI can handle a much tighter byte-stream.

 

Did jump out at me...

Did you confirm removing it ? Does removing it give a useful speed gain on larger downloads ?

I think the half duplex is managed by the data blocks, as the host knows when the remote will reply. 

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

Atmel START User Guide

Change Log

http://atmel-studio-doc.s3-website-us-east-1.amazonaws.com/webhelp/GUID-4E095027-601A-4343-844F-2034603B4C9C-en-US-1/index.html?GUID-DC086BFD-7DA2-43E8-8AE0-457F2351FF4C

2017 - April:

Content: New devices:

...

  • ATtiny3214
  • ATtiny3216
  • ATtiny3217
  • ...

...

 

New examples:

...

  • Secure AVR BLE IoT Node (ATtiny1617)

 

...

http://start.atmel.com/#examples/CustomBoard-ATtiny1617-MNR 

 

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

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

gchapman wrote:

  • ATtiny3214
  • ATtiny3216
  • ATtiny3217
  • ...

 

http://start.atmel.com/#examples/CustomBoard-ATtiny1617-MNR 

I see it says 'Custom Board' and not 'Xplained Mini'

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

All of those are

  • STK600 with STK600-RC024T-103 routing card and STK600-QFN24 top card.

except for the

- Secure AVR BLE IoT Node Field Engagement Board

 


Introduction
============

This example demonstrates an AVR IoT node powered by ATtiny1617 and secured by
ATECC508A. RN4871 BLE module is also equipped on this kit to enable the
connectivity. The kit is battery powered and can be connected to smart phone
app via BLE at any time. The main MCU and BLE module are featured with low
power operation and fast wakeup response, the end customer will not notice
the difference between sleep mode operation and active mode operation. Open
the phone app, discover the node and connect it in one go. All the
authentication and connectivity functions run in background.

Related documents / Application notes
-------------------------------------

- Secure AVR BLE IoT Node with ATtiny1617

Supported evaluation kits
------------------------

- Secure AVR BLE IoT Node Field Engagement Board

Running the demo
----------------
1. Press Download Pack and save the .atzip file.
2. Import .atzip file into Atmel Studio 7, File->Import->Atmel Start Project.
3. Build and flash onto field engagement board.
4. Open phone app "Secure AVR BLE IoT Node" and connect to the selected node.
5. If passing node authentication, it will show the range between phone and node on the first page.
6. Swiping left, the second page shows the temperature log from the node.
7. Swiping left to the last page, it shows the tri-axial acceleration data from the node.

http://www.microchip.com/wwwproducts/en/attiny1617

http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=ATSTK600

http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=ATSTK600-RC24

http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=ATSTK600-SC62

http://www.microchip.com/wwwproducts/en/atecc508a

http://www.microchip.com/wwwproducts/en/RN4871

http://start.atmel.com/#examples/CustomBoard-ATtiny1617-MNR

http://www.microchip.com/development-tools/atmel-studio-7

 

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

Last Edited: Sat. Apr 29, 2017 - 02:24 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Microchip Technology Inc

Microchip

Product Change Notification - SYST-03XWQN160

http://www.microchip.com/mymicrochip/NotificationDetails.aspx?pcn=SYST-03XWQN160

...

Data Sheet - ATtiny1614/ATtiny1616/ATtiny1617 Datasheet Data Sheet Document Revision

...

Microchip has released a new DeviceDoc for the ATtiny1614/ATtiny1616/ATtiny1617 Datasheet of devices.

...

Reason for Change: To Improve Manufacturability

...

Date Document Changes Effective: 04 May 2017

NOTE: Please be advised that this is a change to the document only the product has not been changed.

...

 

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

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

hehe, I wonder how does a change to the document only result in To Improve Manufacturability  ?

 

Has anyone seen which packages are offered for the Atiny32xx series yet ?

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

how does a change to the document only result in To Improve Manufacturability  ?

Simple, if a bit of the silicon doesn't work then you remove any reference to that function is the datasheet...... devil

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

js wrote:

how does a change to the document only result in To Improve Manufacturability  ?

Simple, if a bit of the silicon doesn't work then you remove any reference to that function is the datasheet...... devil

Ahh yes, I've seen exactly that in action..... done by Philips for their CMOS Logic, when we reported some test values with a query.

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

Who-me wrote:
Has anyone seen which packages are offered for the Atiny32xx series yet ?
Likely same as for most of the other members of the tiny 1-series :

http://start.atmel.com/

CREATE NEW PROJECT

In "Filter on device..." enter attiny32

SOIC14

SOIC20

VQFN24

 

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

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

js wrote:
Simple, if a bit of the silicon doesn't work then you remove any reference to that function is the datasheet...

Like the second-last item, perhaps?

 

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.

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

Surprised that microchipDIRECT sold all their stock of the full kit; it has a one month lead.

In stock but very low quantity and the lead time is now nearly three months.

http://new.microchipdirect.com/ProductSearch.aspx?keywords=atatmel-ice

 

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

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

gchapman wrote:
tiny1617 - microchipDIRECT has more than 3 reels (low minimum, partial reel fee)
Zero stock

https://www.microchipdirect.com/ProductSearch.aspx?keywords=attiny1617

 

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

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

New stock is tiny1614 (16KB, narrow SOIC, 14 leads) with low minimum plus a partial reel fee :

https://www.microchipdirect.com/ProductDetails.aspx?Category=ATTINY1614

 

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

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

I'm concerned that tiny1614 will not stay in stock at microchipDIRECT for long.

Reasons :

  • tiny1617 was briefly available
  • distributors will become aware of tiny1614
  • Microchip's "Letter to our clients"
  • no hints of a tiny1617 Xplained Mini
  • tiny1614 is a match for 1.27mm pitch protoboard

I'm seeking interest in a group buy of tiny1614 before it goes out of stock.

No commitment in this thread.

Commitment occurs after I buy a snippet of a reel of tiny1614, create the group buy thread in Marketplace, then appear before a postmaster per your order.

Risk to me is due to minimum quantity, partial reel fee, unsold tiny1614, value for it's at cost, USPS vagaries, and currency conversion.

Risk to you is due to value (tiny1614, postage, package, any USPS delivery assurance); no minimum quantity with payment "in the mail" shortly after successful delivery.

 

If interested, please answer :

  • Are you in?  Yes, indeterminate, or unknown1
  • If yes, what quantity of tiny1614-SSFR?  Less than 100 for I'm not a distributor (I'm a third party of lesser relative means)

Thank you for considering this.

 


1 Logic's fourth state; akin to the fourth state of matter (plasma), game play (in, out, cogitating, WTF), or, you know what I don't know (that's an absolute truth)

http://www.microchip.com/docs/default-source/announcements-documents/letter-to-our-clients.pdf?sfvrsn=2

http://www.microchip.com/wwwproducts/en/attiny1614

https://www.microchipdirect.com/ProductSearch.aspx?keywords=attiny1614-ssfr

https://www.usps.com/

 

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

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

Mouser received one of two reels of tiny817; the other reel is due this week.

tiny1617 is zero stock; ETA at Mouser is 2017-Jun-16.

 


http://www.mouser.com/Semiconductors/Embedded-Processors-Controllers/_/N-6hpef?Keyword=attiny817

http://www.mouser.com/search/ProductDetail.aspx?R=0virtualkey0virtualkeyATtiny1617-MFR

 

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

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

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

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

Atmel START User Guide

Change Log

http://atmel-studio-doc.s3-website-us-east-1.amazonaws.com/webhelp/GUID-4E095027-601A-4343-844F-2034603B4C9C-en-US-1/index.html?GUID-DC086BFD-7DA2-43E8-8AE0-457F2351FF4C

2017 - May:

...

 

New examples:

  • Ultrasonic Distance Measurement (ATtiny817)
  • OLED1 Xplained PRO (ATtiny817)
  • ...
  • STK500 Serial Bootloader (ATtiny817)
  • NVMCTRL driver (ATtiny817)
  • ...
  • Parrot (ATtiny817)
  • Basic Peripherals (ATtiny817)
  • ...
  • Getting Started with the tinyAVR (ATtiny817)

 

Features:

Update of QTouch library and configurator (v 2.0)

  • Support for SAM D10, SAM D11, ATtiny814/816/817/1616/1617 and ATmega324PB/328PB

...

Graphical user interface for Configurable Custom Logic (CCL) with support for SAM L21, ATtiny417, ATtiny814/816/817/1616/1617 and ATtiny321x.


http://start.atmel.com/

 

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

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

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

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

Microchip Technology Inc

Microchip

Product Change Notification - SYST-06JWNH312

http://www.microchip.com/mymicrochip/NotificationDetails.aspx?pcn=SYST-06JWNH312

Date:

07 Jun 2017

...

Notification subject:

Data Sheet - ATtiny417/814/816/817 - Complete Datasheet

...

Attachment(s):

ATtiny417/814/816/817 - Complete Datasheet

...


http://www.microchip.com/wwwproducts/en/attiny817

 

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

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

Atmel-ICE full kit stock restored at microchipDIRECT; lead time is nearly three months :

http://new.microchipdirect.com/ProductSearch.aspx?keywords=atatmel-ice

 

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

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

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

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

Atmel START User Guide

Change Log

http://atmel-studio-doc.s3-website-us-east-1.amazonaws.com/webhelp/GUID-4E095027-601A-4343-844F-2034603B4C9C-en-US-1/index.html?GUID-DC086BFD-7DA2-43E8-8AE0-457F2351FF4C

2017 - June:

Content:

  • New devices:

...

  • ATtiny214
  • ATtiny414
  • ATtiny416
  • ATtiny1614

 

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

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

hmm this is a tiny214 according to Google....... http://thunderbirds.wikia.com/wi...

 

File:Tiny214.png

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

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

Last Edited: Mon. Jul 10, 2017 - 09:45 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

More tinyAVR 1-series in IAR EWAVR.

http://netstorage.iar.com/SuppDB/Public/UPDINFO/012229/avr/doc/infocenter/readme.ENU.html

Release notes

for IAR Embedded Workbench for Atmel AVR version 7.10.1

...

 

Support for new devices
ATtiny212, ATtiny214, ATtiny412, ATtiny414, ATtiny416, ATtiny1614, ATtiny3214, ATtiny3216, ATtiny3217, ...

 

...

 

The USB driver from Jungo has been replaced - customers who previously used the USB drivers from Jungo need to update to the new Windows USB driver, supplied in this installation ...

 

...

via https://www.iar.com/iar-embedded-workbench/#!?architecture=AVR

 

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

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

Microchip Technology Inc

Microchip

Product Change Notification - SYST-13EUSC355

http://www.microchip.com/mymicrochip/NotificationDetails.aspx?pcn=SYST-13EUSC355

Date:

17 Jul 2017

...

Notification subject:

Data Sheet - ATtiny417/817 - Complete Datasheet Data Sheet Document Revision

...

Attachment(s):

ATtiny417/817 - Complete Datasheet

...


http://www.microchip.com/wwwproducts/en/attiny817

 

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

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

Atmel-ICE full kit is low stock at Microchip; zero stock 2017-Aug-15.

Stock restored 2017-Aug-16 to 136.

Stock is plentiful at distributors.

 

http://new.microchipdirect.com/productsearch.aspx?Keywords=ATATMEL-ICE

https://octopart.com/atatmel-ice-microchip-77759562

 

Edits : zero, restored

 

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

Last Edited: Thu. Aug 17, 2017 - 03:01 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Atmel START User Guide

Change Log

http://atmel-studio-doc.s3-website-us-east-1.amazonaws.com/webhelp/GUID-4E095027-601A-4343-844F-2034603B4C9C-en-US-1/index.html?GUID-DC086BFD-7DA2-43E8-8AE0-457F2351FF4C

2017 - September:

...

New examples:

  • ADC Basics with tinyAVR 1-seriers (ATtiny817 Xplained Pro)
  • Pill Box Alarm for AVR P4 FEB (Field Engagement Board) (ATtiny817)
  • Noise Countermeasures for ADC Applications (ATtiny817)
  • ADC Oversampling with tinyAVR 1-series (ATtiny817)
  • ...

 

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

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

Atmel-ICE full kit is low stock at Microchip :

http://new.microchipdirect.com/product/search/all/ATATMEL-ICE

 

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

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

Atmel-ICE full kit is extremely low stock at Microchip :

http://new.microchipdirect.com/product/search/all/ATATMEL-ICE

 

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

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

 

Hi,

do i get it right, that reset pin is in RESET mode by default? I wanted to build my own mEDBG from ATmega32U4, but now I'm confused (pun intended).

Here's X16/X17 tinys' datasheet http://ww1.microchip.com/downloads/en/DeviceDoc/40001893B.pdf and here's its page 30:

 


@edit: I did my homework and it's in UPDI mode, and my home made mEDBG works like a charm with tiny1616 :)

Last Edited: Tue. Oct 31, 2017 - 04:20 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

vidmo wrote:

...do i get it right, that reset pin is in RESET mode by default?

 

I don't think it does, when I was looking at this a few months ago I found a note in, of all places, the JTAG-ICE3 manual. See this post...

 

http://www.avrfreaks.net/forum/u...

'This forum helps those who help themselves.'

 

pragmatic  adjective dealing with things sensibly and realistically in a way that is based on practical rather than theoretical consideration.

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

vidmo wrote:
do i get it right, that reset pin is in RESET mode by default?
Answer is somewhat ambiguous per [but see Brian's post above]

33.3.2.1  UPDI Enable with Fuse Override of RESET pin

When the RESET Pin Configuration (RSTPINCFG) bits in FUSE.SYSCFG0 are 0x1, the RESET pin will
be overridden, and the UPDI will take control of the pin and configure it as input with pull-up. When the
pull-up is detected by a connected debugger, the UPDI enable sequence, as depicted below, is started.

for a 16KB tinyAVR 1-series.

IIRC, UPDI is enabled as manufactured.

vidmo wrote:
I wanted to build my own mEDBG from ATmega32U4, ...
OCD may be difficult as that's hidden; maybe do-able as debugWIRE has been somewhat deduced.

What is open is the NVMCTRL and the UPDI instruction set; might inquire with Dean about adding UPDI to LUFA AVRISP as its hardware is ready for UPDI.

 

http://www.fourwalledcubicle.com/AVRISP.php

 

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

Last Edited: Tue. Oct 31, 2017 - 04:03 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I didn't saw replies and edited, sorry for that.

I did my homework and it's in UPDI mode, and my home made mEDBG works like a charm with tiny1616 :)

 

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

No problems.

vidmo wrote:
... and my home made mEDBG works like a charm with tiny1616 :)
Cool!

Will you FOSS it?

Reason: http://www.avrfreaks.net/forum/cant-figure-out-how-program-attiny817#comment-2034271 (pyupdi)

 

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

Last Edited: Tue. Oct 31, 2017 - 04:44 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Atmel gave us all answer:
how to program mEDBG 32U4 and where is fw: http://www.atmel.com/webdoc/atme...
schematic is in User Guide's software zip: http://www.atmel.com/tools/attin...

Though, there is minor "thing" with EEPROM, which I'm gonna save for myself for now...

I uploaded fw and eeprom .dat file on my google drive: https://drive.google.com/open?id=0B3VyJZzWwjj5UU5xem1mUDRHaUU

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

vidmo wrote:

I didn't saw replies and edited, sorry for that.

I did my homework and it's in UPDI mode, and my home made mEDBG works like a charm with tiny1616 :)

 

 

Excellent, I'm glad somebody tested it. I though about trying to upload the firmware, but I didn't have a 32U4 around. Besides, I didn't knew which one was the correct firmware, several versions come with AS7:

 

 

I'm guessing for the tinyX we should burn the UPDI version?

 

 

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

I had presumed that the firmwares were encrypted or protected in some way. e.g. like the STK500 upgrades from an encrypted bootloader.
But since these are complete images you can just write to any 32U4 and get the appropriate mEDBG.
medbg.hex for XMINI-328
medbgupdi.hex for XMINI-817
medbgsam.hex for XMINI-SAMD10
.
I don't know which XMINI uses TPI.
Note that mEDBG UPDI is reasonably fast. The other mEDBG are very SLOW compared to using a proper ATMEL-ICE.
.
From Atmel's point of view, they could have used a UC32 instead of an AVR. I suppose that the 32U4 is 5V tolerant and does not require external level shifting.
.
David.

Last Edited: Tue. Oct 31, 2017 - 10:46 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes, it's UPDI one, but unfortunately I had some communication issues. At first I could read ID, fuses and flash, but after writing led blinking project I cant connect any more.. I think, that might be some wires issues (uCs was on adapters on breadboard and sh***y USB cable) or EEPROM, which content I figured out myself.
So here's my question: Can anyone share EEPROM and flash contents of 32U4 mEDBG from tiny817 Xmini? I care more about EEPROM, because flash is included to AS.

Also 32U4 is 5V tolerant, as well as UPDI tinys. TPI is for tiny104 nano explained or similar name.

Last Edited: Tue. Oct 31, 2017 - 10:49 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think the TPI version is for this one: http://www.microchip.com/Develop...

 

About the encryption, it seems only the "good stuff", like Atmel-ICE firmware, is encrypted. Also I found this (nEDBG - nano-EDBG?) in the tools directory, anyone knows what it is?

 

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

No, the MCU has 32 pins, it must be a 32U2 and not a 32U4 like mEDBG.

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

nEDBG? Perhaps one of these...

 

 

It has a 32U4.

'This forum helps those who help themselves.'

 

pragmatic  adjective dealing with things sensibly and realistically in a way that is based on practical rather than theoretical consideration.

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

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.

# MEDBG EEPROM MAP

MEDBG_CONFIG_SERIAL_NUMBER_BANK = 0x00
MEDBG_CONFIG_SERIAL_NUMBER_ADDRESS = 0x04
MEDBG_CONFIG_SERIAL_NUMBER_LEN = 20
 

MEDBG_CONFIG_KIT_NAME_BANK = 0x00
MEDBG_CONFIG_KIT_NAME_ADDRESS = 0x18
MEDBG_CONFIG_KIT_NAME_LEN_MAX = 50
 

MEDBG_CONFIG_MANUFACTURER_NAME_BANK = 0x00
MEDBG_CONFIG_MANUFACTURER_NAME_ADDRESS = 0x4A
MEDBG_CONFIG_MANUFACTURER_NAME_LEN_MAX = 50
 

MEDBG_CONFIG_TARGET_NAME_BANK = 0x00
MEDBG_CONFIG_TARGET_NAME_ADDRESS = 0x7C
MEDBG_CONFIG_TARGET_NAME_LEN_MAX = 30

 

MEDBG_CONFIG_FIRE_BANK = 0x00
MEDBG_CONFIG_FIRE_ADDRESS = 0xFE
MEDBG_CONFIG_FIRE_LEN = 1
 

MEDBG_CONFIG_FIRE_ISPDW_VALUE = 0xFF
MEDBG_CONFIG_FIRE_SWD_VALUE = 0xFE
MEDBG_CONFIG_FIRE_TPI_VALUE = 0XFD
MEDBG_CONFIG_FIRE_UPDI_VALUE = 0xFC
 

MEDBG_CONFIG_SUFFER_BANK = 0x01
MEDBG_CONFIG_SUFFER_ADDRESS = 0x20
MEDBG_CONFIG_SUFFER_LEN = 1

 

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

@duzern,
.
I see that the debugWIRE version binary is only 28657 bytes.
I had always assumed that the 32u4 was very tight for Flash space. And the firmware had to make speed/size compromise.
.
Although the 16MHz 32u4 has less processing power, the debugWIRE comms should have a similar performance i.e. limited to the hardware protocol speed.
.
Of course it is up to Microchip/Atmel if they want to cripple the mEDBG versus the EDBG ATMEL-ICE.
.
David.

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

duzern wrote:
Oh no, you figured out our big secret that the mEDBG is not encrypted :)

 

Glad to see you're so cavalier about it. But let me save your post with the EEPROM stuff, just in case you change your mind...

Pages