Yes, the ATmega4809 is a great micro for heavy lifting. Lots of memory & better priced than the older mega parts (& certainly a much bigger bang for your dollar over similar Microchip PIC16F parts).
As my involvement is mainly around the ATtiny parts (for lightish lifting), I think someone more experienced with the mega range should make the recommendations for which of these parts should be first off the rank to support.
Perhaps someone familiar with the mega range (including the new parts) should start a new thread to discuss this further?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Leadership support comes from the Microchip VP 8-bit. This includes insights and support. The insights I share when I can. In terms of support he is an excellent single point of contact into the rest of the Microchip organisation.
For support I now have access to priority support - as we are finding and reporting lots of interesting features and issues. This means that I get faster responses to support tickets.
So, re the configuration files. I have been talking with Microchip to automatically provided the information to aid us create the dat files. I am awaiting a response from the product division. They are not fast!
In the recent past. We have conf calls every 3 months to exchange ideas and what we are up to - this aids the relationship and creates clarity between Great Cow BASIC and my other venture of PICKitPlus (these are two very difference enagagements with Microchip - different business divisions!).
Hope this helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hopefully over time, Microchip will see Great Cow BASIC as a very worthy 3rd Party support Platform for their micros & list GCB on many of their "Support Tools" webpages & Application Notes in a similar way that STM used to list the Actum Solutions Realizer Compiler.
New users looking to learn how to write code for the Microchip parts (including the AVR parts) often look at the fiddleness of Assembly & the unfriendliness of the very cryptic C & end up shaking their heads, saying to themselves "it is all too hard".
Great Cow BASIC has the opportunity to turn that around, which over time, will add to Microchip's sales.
I'm slow off the mark as Chuck Hellebuyck realised this 5 or 6 years ago when he moved from microEnginnering Labs Pic BASIC Pro to Great Cow BASIC. I'm now following in his footsteps (better late than never).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Derek, maybe I could get my head back in game on the Tiny's again?
1. Is the main focus still on the tiny406? Do you have the chip?
2. What peripherals are you most interested in, or most likely to use?
3. Do you have a Pickit 4, or UPDI programmer?
4. Are you willing to verify or help development?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@kent_twt4 1. Is the main focus still on the tiny406? Do you have the chip?
Yes, the ATtiny406 is the most interesting micro in Microchip's new AVR range for us. Yes, I have some micros here in SOIC-20 package.
2. What peripherals are you most interested in, or most likely to use?
10 bit ADC, E2, I2C, comparator, WDT.
3. Do you have a Pickit 4, or UPDI programmer?
We have 5 or 6 of the microEngineering USB programmers. These will allow us to program the AVR parts with the latest version of MPLAB, however I'm quite taken with Anobium's PICKitPlus & would give that a run as the software looks very nice indeed.
4. Are you willing to verify or help development?
Certainly, where I can. I'm hopeless at C & assembly language, but use Actum Solution's Realizer programming software extensively & have some experience with microEngineering's Pic Basic Pro.
In the early days I programmed & designed boards using STM ST6 & ST7 parts, then later moved to several of Microchip's 8 bit parts (PIC16F716, PIC16F72, PIC17F73, PIC16F722, PIC16F723 & PIC16F506).
For our latest product I had hoped to move over to the ATtiny406, but not wanting to put pressure on anyone, I have designed in the STM8S103 part (SOIC-20).
What drives us is the price of production. The new AVR parts from Microchip are very good value.
The best value chips are probably the STM8S value-line fine pitch micros. We don't like pin spacings less than 0.85mm as it increases the amount of rework required (for mass production) & our engineers time is more productive being spent on new products.
So, I will certainly help you where I am able to.
Last edit: Derek 2019-03-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Derek
3. I don't think either of the Pickit2/3 Plus or the MELabs USB programmer is going to program UPDI devices (i.e. attiny 0, 1 and mega 0 series). So starting at the low end up, there is the attiny416-Xnano which can be hacked/cut and used with Atmel Studio. Then onto MCHP Start and the Pickit4 to be used with MPLABX or maybe MPLABX IPE.
Here is pics of the Attiny817-Xmini, UNO Multifunction board, Attiny416-Xnano which has been cut to free the UPDI programmer part
10 bit adc with attiny817-Xmini plus UNO multifunction board. . With a few mods, this is not too bad for a development setup. That pot is a real pain, 25 turns!
At first look the register locations "mostly" looks to be the same, whether device is tiny202 or a tiny817. So renamed experimental tiny817 dat file to tiny416 and blinky led works on the nano.
Edit: sorry about that, I am adding pics as attachments now.
Realizer uses MPLABX as the code compiler but I would probably prefer to use Atmel Studio for the AVR parts.
Normally I design our production board, then program that board to see if everything works as expected.
Some years ago we used a Microchip ICD programmer (it was in a round case). We found it not to be reliable (no idea why), so moved over to using the microEnginnering Labs USB programmers which have worked really well for us for close to 20 years.
I'm quite willing to use a programmer you recommend. Something off the shelf that just works with these new AVR parts would suit us best. I'm not worried about a couple of dollars here or there.
If you want me to buy a spare to send to you for your testing, just ask :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Currently I use the PK2+ and PK3+ for the PICS. For the AVR I use AVRISP MkII, but it won't do UPDI. On the rare occasion I use the Dragon for HVP. The cut apart ATtiny416-Xnano UPDI programmer thru Studio will more than suffice for my hobby needs for now, thanks for the offer though.
I am not familiar with production programmers like the ICD and ICE. Have to say for myself, if I did not already have my current stable of PK's etc. I would be leaning to the PK4 , if only because it handles both PIC and AVR. Really like the PK2/PK3 standalone GUI interfaces, unsure of PK4?, so it that would be very difficult to give up on them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do have some news. But, if you have been following my attack on Microchip on Twitter this would be old news. :-)
Microchip - specially the VP of the 8 Bit Business - Jacob Lunn Lassen - employee ID M43943 - has opened my email this yesterday at 22:27. No response.
My ask is the same ask as Jan 2nd 2019. Please provide support so that we can gain access to a robust data source to create automatically the complete set of AVR data files for the new AVR products. Twitter is clearly helping as Jacob Lunn Lassen opened the email.
We have to wait some more unless someone has a bright idea how we can automate the production of the DAT files - we cannot and should not use the datasheets and erratas - well I guess you can but this is something I dont have time to do.
So, watch Twitter - this Friday will be fun ( for me!)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have files - now need someone to help write the converter.
We have the tool that converts the existing information to DAT. This is the method - so, we need to adapt the code to support the new data format.
The tool is written in FreeBASIC by Hugh and this could be simple adapting the existing method of reading the XML file and then the rest of the tool will do it work. The worse case is that is harder than that. :-)
So, what we have is the working tool for the existing datasets, the new XML data and someone needs to sort out the converter.
Anyone?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
They are the ATDF files from Studio - I guess. I was sent a ZIP.
Still need to integrate into the conversion tool. Are are you thinking two tools ? I am ok with two tools - we just need to generate the additional dat files needed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think there would be more work trying to integrate with Hugh's code, then just going with a clean break?, in whatever form that may take.
I took a bit of a stumble when trying to pry out the register bits from the .atdf files, so need to revisit. Was able to get the register bits from the .inc files, but they lack some of the device detail that the .atdf files include.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
is this a part (and its family of parts ) to be added to the list of parts we need to support?
See https://sourceforge.net/p/gcbasic/discussion/579125/thread/a5d8fd5cab/#1c1e
I did not ask for this with my request to Microchip.
Yes, the ATmega4809 is a great micro for heavy lifting. Lots of memory & better priced than the older mega parts (& certainly a much bigger bang for your dollar over similar Microchip PIC16F parts).
As my involvement is mainly around the ATtiny parts (for lightish lifting), I think someone more experienced with the mega range should make the recommendations for which of these parts should be first off the rank to support.
Perhaps someone familiar with the mega range (including the new parts) should start a new thread to discuss this further?
@kent_twt4
@Anobium
Hi, I was just wondering how much support you received from Microchip?
You mentioned Microchip was "sorting the configuration files for use by the automation tools."
Many thanks.
Good question.
Leadership support comes from the Microchip VP 8-bit. This includes insights and support. The insights I share when I can. In terms of support he is an excellent single point of contact into the rest of the Microchip organisation.
For support I now have access to priority support - as we are finding and reporting lots of interesting features and issues. This means that I get faster responses to support tickets.
So, re the configuration files. I have been talking with Microchip to automatically provided the information to aid us create the dat files. I am awaiting a response from the product division. They are not fast!
In the recent past. We have conf calls every 3 months to exchange ideas and what we are up to - this aids the relationship and creates clarity between Great Cow BASIC and my other venture of PICKitPlus (these are two very difference enagagements with Microchip - different business divisions!).
Hope this helps.
Great news Anobium. Thanks for the update.
Hopefully over time, Microchip will see Great Cow BASIC as a very worthy 3rd Party support Platform for their micros & list GCB on many of their "Support Tools" webpages & Application Notes in a similar way that STM used to list the Actum Solutions Realizer Compiler.
New users looking to learn how to write code for the Microchip parts (including the AVR parts) often look at the fiddleness of Assembly & the unfriendliness of the very cryptic C & end up shaking their heads, saying to themselves "it is all too hard".
Great Cow BASIC has the opportunity to turn that around, which over time, will add to Microchip's sales.
I'm slow off the mark as Chuck Hellebuyck realised this 5 or 6 years ago when he moved from microEnginnering Labs Pic BASIC Pro to Great Cow BASIC. I'm now following in his footsteps (better late than never).
Hi Anobium. I just thought I would touch base & ask if you had heard back from Microchip's Product Division & if so, how is your progress going?
My oversight. I have just emailed back to Microchip. Sorry for delay.
All good. It is the future direction of Great Basic Cow for the latest AVR parts :)
I'm really hanging out for the updated targets :)
Next week... if no progress. Then, I move to Twitter..... raising the lack of progress on Twitter with help. Watch this space....
@Derek, maybe I could get my head back in game on the Tiny's again?
1. Is the main focus still on the tiny406? Do you have the chip?
2. What peripherals are you most interested in, or most likely to use?
3. Do you have a Pickit 4, or UPDI programmer?
4. Are you willing to verify or help development?
@Anobium - thanks heaps.
@kent_twt4
1. Is the main focus still on the tiny406? Do you have the chip?
Yes, the ATtiny406 is the most interesting micro in Microchip's new AVR range for us. Yes, I have some micros here in SOIC-20 package.
2. What peripherals are you most interested in, or most likely to use?
10 bit ADC, E2, I2C, comparator, WDT.
3. Do you have a Pickit 4, or UPDI programmer?
We have 5 or 6 of the microEngineering USB programmers. These will allow us to program the AVR parts with the latest version of MPLAB, however I'm quite taken with Anobium's PICKitPlus & would give that a run as the software looks very nice indeed.
4. Are you willing to verify or help development?
Certainly, where I can. I'm hopeless at C & assembly language, but use Actum Solution's Realizer programming software extensively & have some experience with microEngineering's Pic Basic Pro.
In the early days I programmed & designed boards using STM ST6 & ST7 parts, then later moved to several of Microchip's 8 bit parts (PIC16F716, PIC16F72, PIC17F73, PIC16F722, PIC16F723 & PIC16F506).
For our latest product I had hoped to move over to the ATtiny406, but not wanting to put pressure on anyone, I have designed in the STM8S103 part (SOIC-20).
What drives us is the price of production. The new AVR parts from Microchip are very good value.
The best value chips are probably the STM8S value-line fine pitch micros. We don't like pin spacings less than 0.85mm as it increases the amount of rework required (for mass production) & our engineers time is more productive being spent on new products.
So, I will certainly help you where I am able to.
Last edit: Derek 2019-03-01
@Derek
3. I don't think either of the Pickit2/3 Plus or the MELabs USB programmer is going to program UPDI devices (i.e. attiny 0, 1 and mega 0 series). So starting at the low end up, there is the attiny416-Xnano which can be hacked/cut and used with Atmel Studio. Then onto MCHP Start and the Pickit4 to be used with MPLABX or maybe MPLABX IPE.
Here is pics of the Attiny817-Xmini, UNO Multifunction board, Attiny416-Xnano which has been cut to free the UPDI programmer part
10 bit adc with attiny817-Xmini plus UNO multifunction board. . With a few mods, this is not too bad for a development setup. That pot is a real pain, 25 turns!
At first look the register locations "mostly" looks to be the same, whether device is tiny202 or a tiny817. So renamed experimental tiny817 dat file to tiny416 and blinky led works on the nano.
Edit: sorry about that, I am adding pics as attachments now.
Last edit: kent_twt4 2019-03-04
Realizer uses MPLABX as the code compiler but I would probably prefer to use Atmel Studio for the AVR parts.
Normally I design our production board, then program that board to see if everything works as expected.
Some years ago we used a Microchip ICD programmer (it was in a round case). We found it not to be reliable (no idea why), so moved over to using the microEnginnering Labs USB programmers which have worked really well for us for close to 20 years.
I'm quite willing to use a programmer you recommend. Something off the shelf that just works with these new AVR parts would suit us best. I'm not worried about a couple of dollars here or there.
If you want me to buy a spare to send to you for your testing, just ask :)
Currently I use the PK2+ and PK3+ for the PICS. For the AVR I use AVRISP MkII, but it won't do UPDI. On the rare occasion I use the Dragon for HVP. The cut apart ATtiny416-Xnano UPDI programmer thru Studio will more than suffice for my hobby needs for now, thanks for the offer though.
I am not familiar with production programmers like the ICD and ICE. Have to say for myself, if I did not already have my current stable of PK's etc. I would be leaning to the PK4 , if only because it handles both PIC and AVR. Really like the PK2/PK3 standalone GUI interfaces, unsure of PK4?, so it that would be very difficult to give up on them.
Hello everyone, especially to Anobium, do you have any information regarding the ATmega4809 Family?
Thanks
I see the PICKIT4 programmer now has beta support for these new AVR parts.
The complete list of supported targets can be found on the Microchip webpage below:
http://ww1.microchip.com/downloads/en/DeviceDoc/Device_Support.pdf
I do have some news. But, if you have been following my attack on Microchip on Twitter this would be old news. :-)
Microchip - specially the VP of the 8 Bit Business - Jacob Lunn Lassen - employee ID M43943 - has opened my email this yesterday at 22:27. No response.
My ask is the same ask as Jan 2nd 2019. Please provide support so that we can gain access to a robust data source to create automatically the complete set of AVR data files for the new AVR products. Twitter is clearly helping as Jacob Lunn Lassen opened the email.
We have to wait some more unless someone has a bright idea how we can automate the production of the DAT files - we cannot and should not use the datasheets and erratas - well I guess you can but this is something I dont have time to do.
So, watch Twitter - this Friday will be fun ( for me!)
thank you very much for the update ..... for twitter I will watch through my son I don't like social media
Have a good time
I have been provided with some information from Microchip. It seems at first glance to be what we need.
Next week I will review in detail.
This is excellent news. It seems that social media does have an influence afterall.
Oh yes. Who would want something like this every Friday.
News.
I have files - now need someone to help write the converter.
We have the tool that converts the existing information to DAT. This is the method - so, we need to adapt the code to support the new data format.
The tool is written in FreeBASIC by Hugh and this could be simple adapting the existing method of reading the XML file and then the rest of the tool will do it work. The worse case is that is harder than that. :-)
So, what we have is the working tool for the existing datasets, the new XML data and someone needs to sort out the converter.
Anyone?
How do these files differ from the .inc and .atdf from Studio? Could you zip me your new files files?
They are the ATDF files from Studio - I guess. I was sent a ZIP.
Still need to integrate into the conversion tool. Are are you thinking two tools ? I am ok with two tools - we just need to generate the additional dat files needed.
I think there would be more work trying to integrate with Hugh's code, then just going with a clean break?, in whatever form that may take.
I took a bit of a stumble when trying to pry out the register bits from the .atdf files, so need to revisit. Was able to get the register bits from the .inc files, but they lack some of the device detail that the .atdf files include.