Good idea, but could be a paperweight with GCB, until these much newer devices (tiny and mega 0 and 1-series) get incorporated . Have the tiny104 nano, but it also needs incorporating into GCB. Like the board being USB powered and the integrated UPDI integrated programmer.
I can say that the Mega Board (i.e. mega2560) seems to be pretty well supported in GCB if you want more of everything. The Chinese clones can be had for around the same price.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The ATtiny102 & ATtiny104 will probably be a hard call to support with Great Cow Basic as they only contain 32 bytes of RAM but it has been done before with the ATtiny28, ATtiny4, ATtiny5, ATtiny9 & ATtiny10.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm liking what Microchip is doing, in terms of bringing some of the PIC advanced peripherals over to the AVR core architecture. I think it's creative and openminded ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree, I like the AVR CPU core but the PIC peripherals have always been superior (subjective I guess) but I do see the current trend as positive, the best of both worlds.
The downside is that they are not, last time I asked, planning on releasing any of the new AVR devices in DIP or SIP packaging, so those of us too old and blind to use Surface mount are excluded.
On the up side I did get to play with the 6800 / 6801 / 6809 devices way back in the 70’s and that is the root of the AVR - The 6802 team left motorola to create the 6502 - the rest is history.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found this serial test program on AVR Freaks, and generated a serial example in C for testing only. Make sure debugger firmware is most current verson ...
MplabX is at 5.1. I will have real hardware to test on soon. I wonder if some of the Logic Analyzer functions in AVR Studio have made it over to MplabX yet?
Yes, it is unfortunate that footprint miniaturisation is making it harder for the average maker to play around with these parts.
For production we prefer SOIC with 1.27 spacing as it makes any re-work viable (time wise).
The ATmegas with 0.85 spacing is also OK, but we find for volume production that the 0.65 & 0.5 pin spacing is becoming too fine pitch for "economical" rework.
It seems Microchip are moving towards V-QFN/QFN for more of their new releases. I'm assuming this is a combination of further miniaturisation demands by high volume customers & the (slightly) lower cost of manufacture.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was able to update the nedbg debugger component, but was forced to upgrade the latest AVR Studio, which is fraught with terror over my fragile driver setup on Windows 10.
Installed Packages: Atmel Kits - 7.0.122
C:\Users\randa\Desktop\nedbg_fw-1.5.322>atfw.exe -t nedbg -a nedbg_fw-1.5.322.zip
Found nedbg:ATML3094051800001809
Upgrading nedbg:ATML3094051800001809
Upgrading MCU firmware: [==========]
Verifying MCU firmware: [==========]
Successful upgrade
My test project worked OK, couple of odd error messages regarding fuses, and the progamming could have been faster but... all's well that ends well.
I think the ATmega4809 has some sort of intrinsic protection from the fuses locking out programming, good by debug wire. The 4 serial ports could prove very useful.
I was suprised (delighted) to see the debugger component was an ARM chip. SAMD21 flavor, I guess it was necessary to update the technology for
UPDI programming
CMSIS-DAP (open source?)
USB Mass storage programming (drop and add)
USB CDC serial emmulation
2 channel logic analyzer (??? new to me, specific to AVR Studio ???)
Again a step up, and a look in the go forward direction
Howdy All!,
Hoping every one had a fine holiday, I sure did.
Does anyone have any experience with this? Very inexpensive.
https://www.microchip.com/DevelopmentTools/ProductDetails/DM320115#additional-summary
Best,
Randy
Good idea, but could be a paperweight with GCB, until these much newer devices (tiny and mega 0 and 1-series) get incorporated . Have the tiny104 nano, but it also needs incorporating into GCB. Like the board being USB powered and the integrated UPDI integrated programmer.
I can say that the Mega Board (i.e. mega2560) seems to be pretty well supported in GCB if you want more of everything. The Chinese clones can be had for around the same price.
Supporting Kent. We have are working with Microchip to support new AVR parts.
This part in currently not supported.
The ATtiny102 & ATtiny104 will probably be a hard call to support with Great Cow Basic as they only contain 32 bytes of RAM but it has been done before with the ATtiny28, ATtiny4, ATtiny5, ATtiny9 & ATtiny10.
I'm liking what Microchip is doing, in terms of bringing some of the PIC advanced peripherals over to the AVR core architecture. I think it's creative and openminded ...
I agree, I like the AVR CPU core but the PIC peripherals have always been superior (subjective I guess) but I do see the current trend as positive, the best of both worlds.
The downside is that they are not, last time I asked, planning on releasing any of the new AVR devices in DIP or SIP packaging, so those of us too old and blind to use Surface mount are excluded.
On the up side I did get to play with the 6800 / 6801 / 6809 devices way back in the 70’s and that is the root of the AVR - The 6802 team left motorola to create the 6502 - the rest is history.
I found this serial test program on AVR Freaks, and generated a serial example in C for testing only. Make sure debugger firmware is most current verson ...
https://www.avrfreaks.net/comment/2588511#comment-2588511
MplabX is at 5.1. I will have real hardware to test on soon. I wonder if some of the Logic Analyzer functions in AVR Studio have made it over to MplabX yet?
Last edit: Randall Young 2019-01-07
Yes, it is unfortunate that footprint miniaturisation is making it harder for the average maker to play around with these parts.
For production we prefer SOIC with 1.27 spacing as it makes any re-work viable (time wise).
The ATmegas with 0.85 spacing is also OK, but we find for volume production that the 0.65 & 0.5 pin spacing is becoming too fine pitch for "economical" rework.
It seems Microchip are moving towards V-QFN/QFN for more of their new releases. I'm assuming this is a combination of further miniaturisation demands by high volume customers & the (slightly) lower cost of manufacture.
I was able to update the nedbg debugger component, but was forced to upgrade the latest AVR Studio, which is fraught with terror over my fragile driver setup on Windows 10.
Installed Packages: Atmel Kits - 7.0.122
C:\Users\randa\Desktop\nedbg_fw-1.5.322>atfw.exe -t nedbg -a nedbg_fw-1.5.322.zip
Found nedbg:ATML3094051800001809
Upgrading nedbg:ATML3094051800001809
Upgrading MCU firmware: [==========]
Verifying MCU firmware: [==========]
Successful upgrade
My test project worked OK, couple of odd error messages regarding fuses, and the progamming could have been faster but... all's well that ends well.
I think the ATmega4809 has some sort of intrinsic protection from the fuses locking out programming, good by debug wire. The 4 serial ports could prove very useful.
I was suprised (delighted) to see the debugger component was an ARM chip. SAMD21 flavor, I guess it was necessary to update the technology for
UPDI programming
CMSIS-DAP (open source?)
USB Mass storage programming (drop and add)
USB CDC serial emmulation
2 channel logic analyzer (??? new to me, specific to AVR Studio ???)
Again a step up, and a look in the go forward direction
Last edit: Randall Young 2019-01-10
Here's what the 2-channle "Data Gateway Interface" looks like in AVR Studio 7.
Struggling with the logic in this example, which is Byzantine at best. C code gives me hives!
Last edit: Randall Young 2019-01-11
Oof... the sheer number of registers to keep track of and their configuration and use is way different than the old devices. I guess not having to OR the ports to change a bit is progress?
http://leoninstruments.blogspot.com/2014/05/xmega-tutorial-ports-04.html
https://github.com/GreatCowBASIC/Demonstration_Sources/tree/main/TestSolutions/AVRDX_implementation/mega4809
Latest GCStudio supports mega4809. The libraries will need adapting but the basic IO, memory etc all works great.
Enjoy
Available on DEV 1.01.143 and scheduled for mainstream on 08/17/2024