| View previous topic :: View next topic |
| Author |
Message |
svberg
Joined: 07 Nov 2011
Posts: 48
|
 Posted: Sat May 25, 2019 11:06 pm Post subject: AtTiny 202 |
 |
|
Hi all.
Any support for the AtTiny 202?
Or could I use the AtTiny20.dat??
regards svein
(BASCOM-AVR version : 2.0.8.1 ) |
|
| Back to top |
|
 |
MWS
Joined: 22 Aug 2009
Posts: 2262
|
| Posted: Sun May 26, 2019 11:13 am Post subject: Re: AtTiny 202 |
|
|
| svein.berg@ccd.as wrote: | | Any support for the AtTiny 202? |
Did you undertake the minimum effort to look up Bascom's root directory for a ...202..dat?
| Quote: | | Or could I use the AtTiny20.dat?? |
Did you undertake the minimum effort to compare datasheets of both controllers?
Any of these efforts, especially the second one, would have answered your question. |
|
| Back to top |
|
|
Duval JP
Joined: 22 Jun 2004
Posts: 1161
Location: France
|
| Posted: Mon May 27, 2019 2:29 pm Post subject: |
|
|
Hello
I'am less "strong" than MWS  but my answers is nearly same
I'm sorry, I can't understand this kind of question: there are at least 100 possible AVRs that can be used with Bascom.
Before making an application I have some questions
1) operating voltage ?
2) number of pin I/O ?
3 UART and how many ?
4 I2C ?
5 SPI ?
6 speed ?
7...
Ditto for the displays, before buying I check if there is a library, or if I am able to get by with the datasheet
did you do that ?
JP
_________________
pleasure to learn, to teach, to create |
|
| Back to top |
|
|
laborratte
Joined: 27 Jul 2005
Posts: 299
Location: Berlin
|
| Posted: Mon May 27, 2019 5:19 pm Post subject: |
|
|
I wouldn't call the question not as stupid as others.
Of course, taking the question 1:1, the correct answer would be "if is not listed in *.dat, it is not supported".
But I think for most uf us english is not the native language and I can imagine the question was thought as something like "could (and maybe will) BASCOM support the new ATtiny202". This is not a silly question as some ATtiny could be supported and other not.
The naming system of Atmel (and even more Microchip) follows the exact same system I used to sort my lego bricks when I was four years old. There is simply no way to figure out from name if the chip could be supported. So you have to check in datasheet:
- there must be 32 working registers
- there must be SRAM
- the count of instrucions should be >100.
At that point there is a chance that BASCOM will run with the chip.
Now you can
- create a .dat file by yourself
- (as a profesional) pay Mark for creating a .dat file for you
- kindly ask Mark for putting this on his to do list and then
- wait until a .dat file is published. |
|
| Back to top |
|
|
MWS
Joined: 22 Aug 2009
Posts: 2262
|
| Posted: Tue May 28, 2019 12:42 am Post subject: |
|
|
| laborratte wrote: | | I wouldn't call the question not as stupid as others. |
Nobody so far called it stupid, while I called it lazy. |
|
| Back to top |
|
|
albertsm
Joined: 09 Apr 2004
Posts: 5922
Location: Holland
|
| Posted: Tue May 28, 2019 8:34 am Post subject: |
|
|
Some info about these chips. laborratte is right about the conditions: 32 registers and internal sram.
I dont want to spoil things but : these tiny AVR are very different to the normal AVR and Xmega. For starters they have a different programming interface.
So we had to add yet another programmer and a new kind of setting for the fuses (there are lot of fuses and programmable spaces)
This was required in order to test the chips. In the upcoming 2082 version there is build in support for updi programming.
But that is the only good news. What i wrote in the help what is new for 2082 about updi :
| Quote: | About UPDI
The new UPDI processors have a total different architecture compared to normal AVR. In fact the differences are similar to XMEGA. For this reason we refer to these processors as XTINY since they are tiny Xmega processors.
Because of the work and support for XMEGA fresh in mind, the actual UPDI compiler/DAT support will be available very soon in a next update as an add on.
The TINY816/817 will be the first processor to be supported.
|
Just have a look at the datasheets to see what these chips are about and i think you understand the decision.
I should have done the same for Xmega since one xmega is not the other.
We do not give release dates but 2082 beta testing period is closed.
_________________
Mark |
|
| Back to top |
|
|
Duval JP
Joined: 22 Jun 2004
Posts: 1161
Location: France
|
| Posted: Tue May 28, 2019 9:10 am Post subject: |
|
|
Hello,
I'm a lucky man. I test the 8082 beta.
I did'nt found any problem
Thanks Mark
_________________
pleasure to learn, to teach, to create |
|
| Back to top |
|
|
LotadaC
Joined: 02 Oct 2008
Posts: 7
|
| Posted: Fri May 31, 2019 5:12 pm Post subject: |
|
|
| albertsm wrote: | | laborratte is right about the conditions: 32 registers ... |
Bascom will not (never?) support the TPI-Tinies (ATtiny4/5/9/10, ATtiny102/104, ATtiny20, ATtiny40 - I don't think that Atmel/Microchip will develop any other TPI-Tiny)
Correct?
| albertsm wrote: | | and internal sram. |
Hmm… it looks like some old µCs without SRAM are supported: ATtiny12 and if I correctly(!) remember some of the AT90S-Series...
There was a $Tiny-Directive...
Ok...
The ATtiny202 is a X0-Core-ATtiny - the ATtiny816/817 is a X1-Core-ATtiny.
One of the X1-Core-feaures is an integrated Peripheral Touch Controller (PTC) - and there's no datasheet, the usage of this module 's documented in it... (this is the first module, an ASM-programmer (and a Bascom-user too I think) cannot use. Atmochip says, that you have to Import a C-library to use it.
Import into ASM or BAS-Code  )
Are there any plans to use the PTC with Bascom, in future? |
|
| Back to top |
|
|
|
FAQ
Search
Register
Log in
