A cross-point switch that arbitrates multi-masters (CPU I-stream, CPU D-stream, either UPDI controller or CRC); it's synchronous as there are cycle impacts due to accesses of specific parts of the unified memory space.
1. Cycle time for data memory accesses assume internal RAM access and are not valid for accesses to the NVM. A minimum of one extra cycle must be added when reading Flash and EEPROM.
2. One extra cycle must be added when accessing lower (64 bytes of) I/O space.
Hmm. SNAP now working, too. I don't know if that's because I restarted MPLAB, or had it plugged in wrong, or what...
Breakpoints are a little messed up. MPLAB claims that there is only a single HW breakpoint (the datasheet says 2.) And it doesn't seem to "re-arm" the breakpoint, so it'll get hit once after a reset, but not if it's in a loop that is continued thereafter. (Hmm. This may be a code optimization problem of some kind?)
That was my guess, but it specifically claims that with only 1 breakpoint, it can't do the things that I thought it would be considering "its own use."
#3 How have you proved that your chip is running at xxMHz?
#4 "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." - Heater's ex-boss
I ordered two nanos; and just ran my first led-binker program using gcc-8.3. I just connect to my USB port and execute "cp main.hex /media/matt/CURIOSITY" to download.
Yup, the Curiosity nano is pretty good, and, importantly, cheap, but lacks the marketing hype of Arduino.
Apparently the mega32U4 has definitelly been abandoned as interface and replaced by a SAMD11 in this new Arduino nano. The Curiosity nano has a SAMD21. So they seem pretty much the same thing with different branding.
edit: Well, the Microchip version has debugging and that's a big plus.
Yes, that's the relatively new over-equipped $45 Uno-format board. The very newly announced Nano-format board doesn't have it, AFAIK (it uses a SAMD11 as USB/Serial. So... Maybe? Schematics not released yet, but I didn't think that anyone was fitting debug code in as little as 16k of flash.)
(also, One instance: in a new-fangled "modular" schematic, I think. So it appears once as a module, and once withing the module as a chip.)
Yes, that's the relatively new over-equipped $45 Uno-format board. The very newly announced Nano-format board doesn't have it, AFAIK (it uses a SAMD11 as USB/Serial. So... Maybe? Schematics not released yet, but I didn't think that anyone was fitting debug code in as little as 16k of flash.)
Right, mEDBG runs on Mega32U4, while the Curiosity has a SAMD21 that runs nEDBG, which is apparently an upgrade of mEDBG. I doubt it can fit on a SAMD11.
I didn't think that anyone was fitting debug code in as little as 16k of flash
It would be an interesting coding challenge, though. I keep hope that the Arduino folk will come up with some sort of "simplified debugging" model that would fit their user base and still be interesting.
It looks like an i386 gdb stub is about 8k, for example...
It would be an interesting coding challenge, though. I keep hope that the Arduino folk will come up with some sort of "simplified debugging" model that would fit their user base and still be interesting.
It looks like an i386 gdb stub is about 8k, for example...
It must include USB code, debug code and programming code. Of those, I can say (since I wrote an example of such code) that the UPDI programming module should be about 3Kb on AVR, thumb code for a SAMD should be a bit larger. Not much larger, I expect, since thumb2 has good code density. This is using a simpler, older interface like STK600. The modern EDBG protocol is more complex, so it will take up more space, mostly protocol red tape. I'm, sure GDB is even more complex, because it must be more generic.
I estimate the debug code should be somewhat larger, let's say twice as large (6Kb). Still leaves plenty of room for the USB interface stuff.
So I guess it should be possible to fit a UPDI specialized debugger in 16k if you use a simplified protocol. I think I'd go for STK600, it's supposed to support UPDI.
Product Change Notification - SYST-28XMJB758 - 28 Apr 2019 - Data Sheet - ATmega808/1608/3208/4808 - 28-pin Data Sheet
Product Change Notification - SYST-28KSIT601 - 28 Apr 2019 - Data Sheet - ATmega808/1608/3208/4808 - 32-pin Data Sheet
Product Change Notification - SYST-28OWXE899 - 28 Apr 2019 - Data Sheet - ATmega809/1609/3209/4809 - 48-pin Data Sheet
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopIn all e cases:
NOTE: Please be advised that this is a change to the document only the product has not been changed.
Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net
- Log in or register to post comments
TopLooking at the block diagram, does anyone know what the Bus Matrix is?
- Log in or register to post comments
TopWild guess: a kind of bus-wide cross-point switch?
Jim
Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net
- Log in or register to post comments
TopA cross-point switch that arbitrates multi-masters (CPU I-stream, CPU D-stream, either UPDI controller or CRC); it's synchronous as there are cycle impacts due to accesses of specific parts of the unified memory space.
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopRe. support by avr-gcc, devices are not supported AFAIK, but core avrxmega3 and custom specs, crt, headers and devicelib should do with v8+.
For the different .rodata offset link with --defsym=__RODATA_PM_OFFSET__=0x4000
avrfreaks does not support Opera. Profile inactive.
- Log in or register to post comments
TopYeah, that's an ATmega4809 in DIP. I requested (and received!) samples...
Edit: It Blinks, using a PICKit4 to upload/debug code. My SNAP isn't working, though, even with an added 1k pullup on UPDI.
- Log in or register to post comments
TopCool!
Well done and thanks for your post.
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopHmm. SNAP now working, too. I don't know if that's because I restarted MPLAB, or had it plugged in wrong, or what...
Breakpoints are a little messed up. MPLAB claims that there is only a single HW breakpoint (the datasheet says 2.) And it doesn't seem to "re-arm" the breakpoint, so it'll get hit once after a reset, but not if it's in a loop that is continued thereafter. (Hmm. This may be a code optimization problem of some kind?)
- Log in or register to post comments
TopThe tools claim one of the HW breakpoints for their own use, leaving only one for you.
- Log in or register to post comments
TopThat was my guess, but it specifically claims that with only 1 breakpoint, it can't do the things that I thought it would be considering "its own use."
- Log in or register to post comments
TopThe mega4809 is coming in Nano format...
https://hackaday.com/2019/05/19/...
#1 This forum helps those that help themselves
#2 All grounds are not created equal
#3 How have you proved that your chip is running at xxMHz?
#4 "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." - Heater's ex-boss
- Log in or register to post comments
TopAlready came... without any Ardino fancy digitalWrite() but with integrated debugger on board
https://www.microchip.com/DevelopmentTools/ProductDetails/DM320115
Attachment(s):
extronic.pl
- Log in or register to post comments
TopI ordered two nanos; and just ran my first led-binker program using gcc-8.3. I just connect to my USB port and execute "cp main.hex /media/matt/CURIOSITY" to download.
- Log in or register to post comments
TopYup, the Curiosity nano is pretty good, and, importantly, cheap, but lacks the marketing hype of Arduino.
Apparently the mega32U4 has definitelly been abandoned as interface and replaced by a SAMD11 in this new Arduino nano. The Curiosity nano has a SAMD21. So they seem pretty much the same thing with different branding.
edit: Well, the Microchip version has debugging and that's a big plus.
- Log in or register to post comments
TopProblem Downloading code to Wifi Rev2 · Issue #33 · arduino/ArduinoCore-megaavr · GitHub
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topnew arrivals at Mouser :
ATmega1608 8-bit Microcontroller - Microchip Technology | Mouser (most are in stock, SSOP ETA 15-Jul'19)
ATmega1609 8-bit Microcontroller - Microchip Technology | Mouser (QFP in stock, QFN ETA is 28-Oct'19)
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopYes, that's the relatively new over-equipped $45 Uno-format board. The very newly announced Nano-format board doesn't have it, AFAIK (it uses a SAMD11 as USB/Serial. So... Maybe? Schematics not released yet, but I didn't think that anyone was fitting debug code in as little as 16k of flash.)
(also, One instance: in a new-fangled "modular" schematic, I think. So it appears once as a module, and once withing the module as a chip.)
- Log in or register to post comments
TopRight, mEDBG runs on Mega32U4, while the Curiosity has a SAMD21 that runs nEDBG, which is apparently an upgrade of mEDBG. I doubt it can fit on a SAMD11.
- Log in or register to post comments
Topnew arrival at Digi-Key :
ATMEGA4809-PF Microchip Technology | Integrated Circuits (ICs) | DigiKey
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopIt would be an interesting coding challenge, though. I keep hope that the Arduino folk will come up with some sort of "simplified debugging" model that would fit their user base and still be interesting.
It looks like an i386 gdb stub is about 8k, for example...
- Log in or register to post comments
Tophttps://www.avrfreaks.net/forum/megaavr-0-series?page=1#comment-2451106
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopIt must include USB code, debug code and programming code. Of those, I can say (since I wrote an example of such code) that the UPDI programming module should be about 3Kb on AVR, thumb code for a SAMD should be a bit larger. Not much larger, I expect, since thumb2 has good code density. This is using a simpler, older interface like STK600. The modern EDBG protocol is more complex, so it will take up more space, mostly protocol red tape. I'm, sure GDB is even more complex, because it must be more generic.
I estimate the debug code should be somewhat larger, let's say twice as large (6Kb). Still leaves plenty of room for the USB interface stuff.
So I guess it should be possible to fit a UPDI specialized debugger in 16k if you use a simplified protocol. I think I'd go for STK600, it's supposed to support UPDI.
- Log in or register to post comments
TopProduct Change Notification - LIAL-26IPJX688 - 01 Jul 2019 - CCB 3751 Initial Notice: Qualification of MTAI as an additional assembly site for selected Atmel industrial products of the 59.91k wafer technology available in 48L TQFP (7x7x1mm) package.
mega809 through mega4809, Microchip Thailand in addition to ASE Taiwan, likely late this year
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopQFN and QFP will be near future arrivals
ATmega808 8-bit Microcontroller - Microchip Technology | Mouser (QFN 7-Aug'19, QFP 2-Sep'19)
ATmega809 8-bit Microcontroller - Microchip Technology | Mouser (QFN 22-Nov'19, QFP 5-Aug'19)
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopIt's not a bug, it's a feature
- Log in or register to post comments
Topa new arrival :
ATMEGA4809-PF Microchip Technology | Mouser
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopPages