megaAVR 0-series

Go To Last Post
286 posts / 0 new

Pages

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

Product Change Notification - RMES-27EGDU414 - 22 Nov 2019 - CCB 3634 Final Notice: Qualification of MMT as an additional assembly site for selected Atmel products available in 32L VQFN (5x5x0.9mm) package.

...

 

Estimated First Ship Date:
December 22, 2019 (Date Code: 1952)

 

...

 

Revision History:
January 03, 2019: Issued initial notification.
November 22, 2019: Issued final notification. Attached the Qualification Report. Revised the affected parts list. Provided estimated first ship date to be on December 22, 2019.

 

...

MMT - Microchip Thailand

 

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

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

The 48-pin QFN pads will be taller by probably the middle of next year ('20)

Product Change Notification - RMES-19QWFS608 - 26 Nov 2019 - Memo # ML112019001A Initial Notice: Introduction of new package for existing ATMEGA3209 and ATMEGA4809 device families available in 48L UQFN (6x6x0.5mm) package.

...

 

Affected CPNs:

 

...

 

Pre Change:
Available in 48L UQFN (6x6x0.5mm)  

Post Change:
Available in 48L VQFN (6x6x0.9mm)  

 

...

 

Reason for Change:
To improve manufacturability by qualifying new package for existing device families affected.

 

...

 

Estimated Qualification Completion Date:
April 2020

 

...

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

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

I have questions, LOTS of them. Hope that answers will be generally useful to others. I recognize that there MAY be (and probably are) answers to some of these questions in the documentation, but I've not been able to sort them out, so far.

 

1) What is PORTMUX? Is it "just" a cross-point switch or does it alter the functionality of the pins (input vs output, pullup/down, etc)? That is, does the peripheral take over the full function of the pin, as in M328P? Does more have to be done for pin control with PORTMUX compared to AVR-standard?

 

2) EVSYS? Can someone describe the broad behavior of this thing? I see a block diagram with gates and flipflops but that does not give me any sense of what it really does.

 

3) I'm struggling to understand differences between TCA and TCB peripherals. Can anyone help with a high-level overview?

 

4) CRC - it appears that the hardware CRC module only works on data being written to flash as part of programming. In other words, it appears to NOT be available for generation of serial message CRCs. Is this correct?

 

5) AVR-standard generally have an interlock between the SPI and the SS pin; to do certain things, the SS pin has to be configured a certain way. It is not at all clear whether there are similar requirements for the USART in SPI mode. Any help, here?

 

Thanks

Jim

 

Until Black Lives Matter, we do not have "All Lives Matter"!

 

 

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

ka7ehk wrote:

2) EVSYS? Can someone describe the broad behavior of this thing? I see a block diagram with gates and flipflops but that does not give me any sense of what it really does.

 

3) I'm struggling to understand differences between TCA and TCB peripherals. Can anyone help with a high-level overview?

 

4) CRC - it appears that the hardware CRC module only works on data being written to flash as part of programming. In other words, it appears to NOT be available for generation of serial message CRCs. Is this correct?

 

5) AVR-standard generally have an interlock between the SPI and the SS pin; to do certain things, the SS pin has to be configured a certain way. It is not at all clear whether there are similar requirements for the USART in SPI mode. Any help, here?

 

The Event System (EVSYS) basically allows one peripheral to control another. On devices with DMA you can do stuff like have the DMA copy data from a USART when a byte received event is generated, replacing the usual interrupt handler. Since these don't have DMA the system is a bit more limited. You can clock counters from other peripherals, say a pin change event on a GPIO or the custom logic.

 

TCA has waveform generation (advanced PWM) capability, TCB has the ability to timestamp inputs which lets you measure periods or determine frequency. The latter can be quite handy for stuff like MODBUS where the end of a frame is a gap, which you can use TCB to measure. Actually you can use the pin change event to do that with TCA too I think, I haven't looked at it.

 

CRC does seem to have been nerfed a bit compared to the XMEGA, you kinda wonder why they bother having it just for flash and not adding a CPU interface that would have been incredibly useful.

 

USART in SPI mode is master only, so there is no SS pin. The main advantage is that it's buffered, where as the SPI peripherals are not.

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

ka7ehk wrote:
1) What is PORTMUX? Is it "just" a cross-point switch or does it alter the functionality of the pins (input vs output, pullup/down, etc)?

That's a good question. I think when you enable event output in the PORTMUX, it does take control of the pins. But when you use it to multiplex peripherals to different ports, I think this depends on the peripheral, not PORTMUX itself. Frankly, this requires testing.

 

ka7ehk wrote:
2) EVSYS? Can someone describe the broad behavior of this thing? I see a block diagram with gates and flipflops but that does not give me any sense of what it really does.

On each peripheral chapter, you will find an "events" section. This will explain whether this peripheral can generate or use events. For example, for TCB it says:

 

The TCB is an event generator. (...)

The peripheral accepts one event input. (...)

This means TCB both generates and accepts events. The event generator routes these events between peripherals. Basically, it allows some simple actions, that would normally be executed by an ISR, to happen fully in hardware.

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

Thanks,

 

There is some useful help here!

 

Jim

 

Until Black Lives Matter, we do not have "All Lives Matter"!

 

 

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

mojo-chan wrote:
... you kinda wonder why they bother having it just for flash ...
Flash is one transistor per bit whereas SRAM is four or six transistors per bit; SRAM is more tolerant of ionizing radiation and high temperature.

Some MCU for geo-physical have a boot ROM and SRAM; fire the internal battery, bootload, then down the bore hole.

MRAM has some radiation tolerance though its temperature range is for most automotive applications and some avionics.

mojo-chan wrote:
... and not adding a CPU interface that would have been incredibly useful.
There might be an arbitration impact versus CRC connected to I/O (UART, USART, etc as CRC is common for communication protocols)

ADC has an accumulator; somewhat similar complexity could be additional for that CRC interface.

 


RIP Opportunity | The Embedded Muse 368

HT-DAB-1 Reference Design Kit - VORAGO | Mouser

Aerospace | Everspin (MRAM)

 

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

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

This is my thinking on the event system:

On the 328p you might write an interrupt handler, triggered by an "input" peripheral, to change the state of an "output" peripheral.  The event system lets you shortcut the function of the interrupt handler.  And in some cases I believe the behavior is asynchronous.

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

What is PORTMUX? Is it "just" a cross-point switch or does it alter the functionality of the pins (input vs output, pullup/down, etc)? That is, does the peripheral take over the full function of the pin, as in M328P? Does more have to be done for pin control with PORTMUX compared to AVR-standard?

In general, the peripherals on the Mega-0 seem to be less "take over" than they were in previous Mega parts.  For instance, in UART initialization, you need to set the TX pin as an output, and maybe set it to ONE as well (the datasheet doesn't say you need to set it to ONE, but it's in the example.)

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

Thanks on that. I thought that I had seem some posts that suggested that (about PORTMUX), hence the question.

 

Jim

 

Until Black Lives Matter, we do not have "All Lives Matter"!

 

 

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

Microchip Thailand will be the second assembly site for megaAVR 0-series in TQFP-32 and TQFP-48 at MSL 1 (unlimited floor life at elevated relative humidity and warm room temperature)

Product Change Notification - KSRA-20BGKY389 - 23 Dec 2019 - CCB 4023.001 and 4023.002 Initial Notice: Qualification of MTAI as an additional assembly site for selected Atmel products available in 32L (7x7x1.0mm) and 48L TQFP (7x7x1.0mm) package using gold (Au) wire.

...

 

Estimated Qualification Completion Date:
January 2020

 

...

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

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

If anyone is interested I just made my code for running the 4808/4809 available on GitHub: 

https://github.com/flitebits/rclib

 

This is a basic example of bringing up the ATMega 4808/4809 and enabling the most common hardware. I wrote this so I could use it to control various features in RC aircraft (telemetry and lights mostly).

 

It has support for:

  • SBus protocol (channel information from radio, inverted serial)
  • S.Port Protocol (only for volts/amps reporting, bi-directional 1-wire inverted serial)
  • DSHOT 600 (bit bang) to set motor speed and get telemetry from newer ESCs
  • Analog to Digital conversion (to read battery volts/amps)
  • PWM for controlling 'dumb' leds
  • APA102 (via SPI) & WS2812 (via bit bang)
  • Serial used by several protocols above as well as for debugging
  • Some simple RGB functions for LED control
  • Very minimal debugging log/print support
  • RTC clock
  •  

Licensed under the Apache 2.0 license (see the file LICENSE-2.0 for details).

Please let me know if you decide to use it.

 

I also have some small board designs for the 4808/4809 that I may include as well at some point if there is interest.

 

Warmest Regards,

Flite Bits flitebits@gmail.com

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

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

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

El Tangas wrote:
Apparently the mega32U4 has definitelly been abandoned as interface and replaced by a SAMD11 in this new Arduino nano.
mega32U4 UPDI to/from mega4809 in Seeed Studio's board with an ETA of 20-Mar'20 at Mouser.

Seeeduino Crypto Board - Seeed Studio | Mouser

...

  • Based on the ATmega4809 microcontroller
  • Incorporates ECC608 high-security encryption chip:
    • Supports SHA-256 and HMAC hash / AES-128

...

  • 5V USB type C power supply
  • 8V to 15V jack input voltage range
  • 16MHz clock speed [mega32U4, mega4809 has a 32KHz crystal]

...

 

ADDITIONAL RESOURCES

 

...

Didn't add the board's URL at Seeed Studio.

Seeeduino Crypto (ATmega4809 & ECC608) - Seeed Studio

 


ATMEGA4809 - 8-bit Microcontrollers

ATmega32U4 - 8-bit AVR Microcontrollers

http://wiki.seeedstudio.com/Seeeduino-Crypto-ATmega4809-ECC608/

 

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

Last Edited: Fri. Jan 24, 2020 - 11:11 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

gchapman wrote:

mega32U4 UPDI to/from mega4809 in Seeed Studio's board

 

I'm guessing they ported MuxTO to the mega32U4. Personally I think it would make more economic sense to port to a STM32, they have 5V tolerant pins, so the level shifters present on the Uno WiFi R2 would also not be needed (like they are not needed with the mega32U4). The difference is that a STM32 would probably be cheaper.

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

I'm guessing imEDBG mEDBG.

IIRC, Seeed Studio has a wiki (didn't search therefore not answering the question of what firmware is in the mega32U4)

There is one 3.3V linear voltage regulator on that board to the connectors; IIRC, mega32U4's internal voltage regulator sets the USB common-mode voltage.

A jelly bean 1117 so a lot of 3.3V current is available.

Otherwise, all is 5V (USB Vbus or external)

330 ohm series termination on UPDI between mega32U4 and mega4809.

No UPDI break-out though 0 ohm resistors are present (patch to connect to an Atmel-ICE, MPLAB Snap, or MPLAB PICkit 4)

 


GitHub - MCUdude/microUPDIcore: Arduino core for flashing mEDBG firmware onto the microUPDI programmer

due to https://www.avrfreaks.net/forum/standalone-medbg-updi-programmer-and-issues-avrdude#comment-2743461

 

edit : mEDBG

https://github.com/arduino/ArduinoCore-megaavr/blob/master/programmers.txt

 

 

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

Last Edited: Sun. Jan 26, 2020 - 06:58 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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

Last Edited: Thu. Feb 13, 2020 - 02:35 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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

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

Product Change Notification - SYST-30ZYYO574 - 06 Feb 2020 - Data Sheet - ATmega808/809/1608/1609 Data Sheet

...

 

Description of Change:
...

          b. Electrical Characteristics section changes:        
             – Minimum and maximum values added

...

          c. Typical  Characteristics section changes:
            – Added more graphs to the Power Consumption section

 

...

 

Attachment(s):

[datasheet URL]

 

...

 

edit : likewise

Product Change Notification - SYST-30XVYQ059 - 05 Feb 2020 - Data Sheet - ATmega4808/4809 Data Sheet

Product Change Notification - SYST-30JPEF324 - 05 Feb 2020 - Data Sheet - ATmega3208/3209 Data Sheet

 

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

Last Edited: Fri. Feb 7, 2020 - 02:00 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

a new arrival 

Arduino Nano Every - Pack - New Products

...

If you are in the situation of needing many boards for your classroom, or if you need to present a complex prototype with many functional blocks, this pack will offer you exactly what you need: a series of Arduino Nano Every boards at a discounted price.

...

The pack is available in two sizes with either 3 or 6 boards of Arduino Nano Every without headers.

...

 

Get to Know More

 

To know more about the history of the Nano Every don’t miss the interview with Dario Pennisi, Arduino’s hardware and firmware development manager, who led the development of this board.

 

...

"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

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

Last Edited: Thu. Mar 12, 2020 - 07:16 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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

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

Product Change Notification - SYST-30NCYM152 - 30 Mar 2020 - ERRATA - ATmega3208/3209 Silicon Errata and Data Sheet Clarification

...

 

Description of Change: 1) Added Silicon Revision D1.

...

4) The ADC errata, ADC Functionality Cannot be Ensured with ADCCLK Above 1.5 MHz for All Conditions, has been split into two separate erratas and rewritten.

...

 

Estimated First Ship Date: 30 April 2020

 

...

 

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

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

from a banner on Microchip's home page

Working From Home?

50% Off + Free Shipping for Select IoT Boards

https://www.microchipdirect.com/product/promo/Learn-IoT-from-home

 

"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

While I have a deep appreciation for Rube Goldberg machines, pointless creations 'just because', and other unnecessarily complex apparatuses, something about a Useless Machine made with anything other than a simple brushed DC gear motor, a DPDT switch, a limit switch, and a battery, just makes my teeth itch.

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

 

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

yes

David

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

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

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

Product Change Notification - SYST-19FKNH955 - 22 Jun 2020 - Data Sheet - ATmega4808/4809 Data Sheet

"Removed the content of the Instruction Set Summary section. This section now refers to the external Instruction Set Manual instead."

 

Hmmph.  I like having the summary in the datasheet (although I liked the old and briefer Atmel-style summary better.)

 

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

westfw wrote:
I like having the summary in the datasheet
as the evidence suggests they have quite a trouble keeping it accurate in the one main reference I'm not sure multiple copies elsewhere, in need of similar maintenance, is necessarily a good idea.

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

I keep a laminated copy handy on the bench.

#1 Hardware Problem? https://www.avrfreaks.net/forum/...

#2 Hardware Problem? Read AVR042.

#3 All grounds are not created equal

#4 Have you proved your chip is running at xxMHz?

#5 "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

"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

Assembly of mega808 and mega1608 in QFN will be moving to Microchip Thailand.

GBNG-20XTKS327 | Product Change Notification | Microchip

...

 

Description of Change: 
Qualification of MMT as an additional assembly site for selected Atmel products available in 32L VQFN (5x5x0.9mm) package with MSL 1 classification.  

 

...

 

Estimated First Ship Date:
November 15, 2020 (date code: 2047)

 

...

 

Revision History:
November 3, 2020: Issued final notification. Attached the Qualification Report. Provided estimated first ship date to be on November 15, 2020.

 

...

 

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

Pages