Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tinyAVR 2-series #309

Closed
a7hybnj2 opened this issue Feb 4, 2021 · 15 comments
Closed

tinyAVR 2-series #309

a7hybnj2 opened this issue Feb 4, 2021 · 15 comments
Milestone

Comments

@a7hybnj2
Copy link

a7hybnj2 commented Feb 4, 2021

They are here! I just ordered a tube of 10 1624's and 1626's 14 and 20 pin respectively.

Let me know if there is anything I can test on my end.

I got them from Mouser.

@SpenceKonde
Copy link
Owner

SpenceKonde commented Feb 4, 2021 via email

@a7hybnj2
Copy link
Author

a7hybnj2 commented Feb 4, 2021

Haha awesome. The full series isn't released but the 162x are out.

Most of that stuff sounds way beyond me. I will will play with them once they arrive and if I do anything useful I'll let you know.

If you need a tester for anything let me know.

@SpenceKonde
Copy link
Owner

SpenceKonde commented Feb 8, 2021

Also... goddamn, thanks for the tip about mouser vs digikey. Digikey is slipping! While Mouser? Mouser is shipping...
Not only does mouser have the new parts that digikey doesn't, their prices on the whole Microchip product line are better! I do hope they change their mind about the VQFN's being non-stock though.

The 1627 is listed as coming in the microscopic VQFN (3x3mm- same as the attiny841's small version and the 1616 (but not the 3216!) . Think we'll get the ultra small package for the 32k parts this time around? I hope so - you can put them on a breakout board that fits into a DIP socket : without wasting any pin positions (the 4x4mm like the 24-pin tinyAVRs) you lose the two middle pin positions to the chip. -P We're gonna be waiting a while I'm afraid for the 32k parts - they haven't even released the ATPack for them yet (I'm definitely a bit worried that they'll end up deciding they'd cannibalize sales of the high end AVR DD line, and cut it off at 16k (though I may be being too negative.

I'm pretty sure that all the tinyAVRs with more than 8 pins of a given flash size and series (0 vs 1) were the same die (and the 2 and 4k parts are the same die too, I think. They shipped a whole bunch of 402's with the wrong signature way back, and someone else here claims to have a 414 that insists that it's a 416, recently acquired. I think they. I always wonder what mechanism is used to do that sigrow writing, whether etching with laser is involved (maybe only for some parts), or if you need to contact part of the chip that's not exposed after the package goes on.... or maybe there's just some magic KEY value you can use via UPDI that will just let you write to the SIGROW! They have that "KEY" to enable chip erase, and another to enable the write userrow while locked, plus the one for NVMPROG - and they're 64-bit keys. Wouldn't be hard for them to have extra ones , and brute forcing a 64-bit keyspace with a non-trivial verification time wouldn't be practical...

@SpenceKonde SpenceKonde added this to the 2.3.0 milestone Feb 8, 2021
@freemovers
Copy link
Collaborator

freemovers commented Feb 8, 2021 via email

@gcormier
Copy link

gcormier commented Feb 9, 2021

Got my 1624 from Microchip direct but also noticed Mouser has stock too.

I asked Digikey, they were useless, said to ask Microchip. Asked Microchip, they were confused and said to ask the vendor. Disappointing indeed.

Put it on a test board, fired up atmel studio and looks good via atmel ice. Haven't dared to try avrdude, and I guess we're a way out from support for the 2 series.

@a7hybnj2
Copy link
Author

a7hybnj2 commented Feb 9, 2021

@gcormier I think you could copy the 1614 from avrdude and just change the IDs. I will be getting my chips sometime this week and will see how far I can get. Really I'll be waiting on Spence because the reason I am drawn to the 1626 over 1616 is the 2nd hardware uart...

@gcormier
Copy link

gcormier commented Feb 9, 2021

Yup I chose 1624 because of 2 Serial.

Now, using the second serial (Serial1) has proven problematic compiling for 1614.

@SpenceKonde
Copy link
Owner

github 'master' branch now hasI sketched in support (board defs made from 1-series with regex's, #ifdefs made less inclined to block compiles instead of spewing warnings, and tone got the new name for the clksel bitfield group codes).

I know all analog related stuff is broken, but please go determine what else is.

@SpenceKonde
Copy link
Owner

clock source for millis timekeeping needs to be TCA0, TCB0, or TCB1

@gcormier
Copy link

Just pulled master branch - Not seeing the 2 series

image

@SpenceKonde
Copy link
Owner

They're under the 0/1-series definitions with the same number of pins

@SpenceKonde
Copy link
Owner

Amended the boards.txt to make it more obvious where to look

@SpenceKonde
Copy link
Owner

SpenceKonde commented Feb 11, 2021

boards.txt also clarifies which timer options work are expected to work

@gcormier
Copy link

gcormier commented Feb 11, 2021 via email

@SpenceKonde
Copy link
Owner

Converting to a discussion topic :-)

Repository owner locked and limited conversation to collaborators Feb 12, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants