Quantcast
Channel: MCS Electronics Forum
Viewing all 20606 articles
Browse latest View live

BASCOM-AVR : AtTiny 202 : REPLY

$
0
0
[quote:f5f630231a="svein.berg@ccd.as"]Any support for the AtTiny 202?[/quote:f5f630231a] Did you undertake the minimum effort to look up Bascom's root directory for a ...202..dat? [quote:f5f630231a]Or could I use the AtTiny20.dat??[/quote:f5f630231a] 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.

BASCOM-AVR : AtTiny 202 : REPLY

$
0
0
Hello I'am less "strong" than MWS :wink: but 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 SPIS? 6 speeds? 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

BASCOM-AVR : AtTiny 202 : REPLY

$
0
0
I wouldn't call the question not a 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 [b:04b18dcac4]new[/b:04b18dcac4] 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.

BASCOM-AVR : AtTiny 202 : REPLY

$
0
0
[quote:3c0d84df52="laborratte"]I wouldn't call the question not as stupid as others.[/quote:3c0d84df52] Nobody so far called it stupid, while I called it lazy.

Share your working BASCOM-AVR code here : 2.8inch 65K FullColorLCD 240x320dot [ILI9341] : NEWTOPIC

$
0
0
The graphic instructions (LINE, BOX, LCDAT, etc) of BASCOM-AVR are limited to byte addressing (0-255) for LCD. Because of that limitation, other users have created a function for the [ILI9341] (240x320 dot) LCD. However, I and some users would like to use BASCOM's standard graphics instructions. Thereat, for LCDs with more than 256 dots, we added offsets to the screen addressing to enable BASCOM standard graphics instructions. Although there are restrictions on instruction execution, this is another approach to large screen LCDs. how to use To specify a position where the screen address exceeds 255, put (1) in the variable [Offset256]. An address can not be drawn across 255 and 256. If the address specification of each instruction is 256 or more, the description of the address value is the same whether 256 or 0. Circuit diagram https://drive.google.com/file/d/1e-ByaqDKedDtw5EJp9cQcHmUnOcFMrbn/view?usp=sharing

BASCOM-AVR : AtTiny 202 : REPLY

$
0
0
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:b17ac157c1]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. [/quote:b17ac157c1] 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.

Share your working BASCOM-AVR code here : 2.8inch 65K FullColorLCD 240x320dot [ILI9341] : REPLY

$
0
0
Hello O-Family Thank you for sharing this smart solution. Maybe it would be a good idea to add an option so the compiler can pass words instead of bytes. This would only work with custom libs like this. If you think this is a good idea then please contact me.

BASCOM-AVR : AtTiny 202 : REPLY

$
0
0
Hello, I'm a lucky man. I test the 8082 beta. I did'nt found any problem Thanks Mark :wink:

Share your working BASCOM-AVR code here : nRF24 simple to use, multilink library : REPLY

$
0
0
sure you can pass an array to a sub. that is no problem.

Share your working BASCOM-AVR code here : 2.8inch 65K FullColorLCD 240x320dot [ILI9341] : REPLY

$
0
0
Hi, Mark Graphic LCD functions created by other users have many functions and high performance, which is very nice. However, the instructions (function names) and parameters differ depending on the author of the function and the LCD, so learning and understanding are required for each. This loses the advantage of the standard command language, which is an advantage of the BASIC language, and is similar to how to handle C language. Furthermore, I think that it will be necessary to have a detailed manual for each beginner. It is probably the best option for the compiler to pass the graphic LCD instruction's word address and word color information to the library. I think that will create a new library, so I want that option. O-Family

Share your working BASCOM-AVR code here : Proportional Fonts for GLCDs + TrueType Converter : REPLY

$
0
0
I have problem with this lib...no text is displayed on LCD SSD1963 900x400. See on picture...should be ABCD1234, bu ABCD is not displayed....any sugestion? I used this set pixel sub and font like attachement. [code:1:95c4aaf1e1]'------------------------------------------------------------------------------- ' Set Pixel '------------------------------------------------------------------------------- Sub Lcd_set_pixel(byval X1 As Word , Byval Y1 As Word , Byval Color As Word) Rgb16_ssd1963 = Color : Temp_x_ssd1963 = X1 : Temp_y_ssd1963 = Y1 #if Portrait = 0 Data_disp_low = &H2B #else Data_disp_low = &H2A #endif Send_com '------ Y Data_disp_low = Temp_y_ssd1963_h : Send_data Data_disp_low = Temp_y_ssd1963_l : Send #if Portrait = 0 Data_disp_low = 1 : Send : Data_disp_low = &HDF : Send #else Data_disp_low = 3 : Send : Data_disp_low = &H1F : Send #endif #if Portrait = 0 Data_disp_low = &H2A #else Data_disp_low = &H2B #endif Send_com '------ X Data_disp_low = Temp_x_ssd1963_h : Send_data Data_disp_low = Temp_x_ssd1963_l : Send #if Portrait = 0 Data_disp_low = 3 : Send : Data_disp_low = &H1F : Send #else Data_disp_low = 1 : Send : Data_disp_low = &HDF : Send #endif Data_disp_low = &H2C : Send_com Data_disp_high = Rgb16_ssd1963_high : Data_disp_low = Rgb16_ssd1963_low Send_data #if Portrait = 0 Ssd1963_write_reg &H36 , Landscape_mode 'Normal X/Y order #else Ssd1963_write_reg &H36 , Portrait_mode #endif End Sub[/code:1:95c4aaf1e1]

BASCOM-AVR : Config Timer1 with optional parameter : NEWTOPIC

$
0
0
Hi, Config Timer1 with optional Parameter (configuration=mysetting) doesn't work correctly on ATmega8. Similar to [url=https://www.mcselec.com/index2.php?option=com_forum&Itemid=59&page=viewtopic&t=11867]this[/url] Topic, only TCCR1B is updated, and TCCR1A is not updated. On Mega8 TCCR1B contains the Clock Select Bits (Prescaler=blablub), some (the upper two) of the Waveform Generation Mode Bits (Config Timer1=blablub), the Input Capture Edge Select Bit (Edge=blablub) and the Input Capture Noise Cancleler Bit (I dont know, how to handle it with Config TimerN) TCCR1A contains the lower two WGM-Bits and the Output Compare Mode Bits from both Channels. Configuring the timer works, but if I try to change the configuration with [code:1:3023baa238]start Timer1 , settingname[/code:1:3023baa238] TCCR1A is not updated. Background: I tried to use two different Settings - one with activated PWM-Outputs (=clear down) and one with inactivated Outputs (=disconnect). Beside this, the Timer generates a timbase using the TOV1-Flag. As walkaround I can use both configs - reconfigurating the Timer each time - but with using [code:1:3023baa238]Start Timer1 , settingname [/code:1:3023baa238] the Code should look more clear... [b:3023baa238][color=red:3023baa238](BASCOM-AVR version : 2.0.8.1 )[/b:3023baa238][/color:3023baa238]

BASCOM-AVR : Config Timer1 with optional parameter : REPLY

$
0
0
as always, you best show some code that will produce the problem. this code should include the $regfile directive with the value of the processor you use.

Share your working BASCOM-AVR code here : 1.3inch 65K FullColorLCD 240x240dot [ST7789V] : NEWTOPIC

$
0
0
Various small color LCDs used for smart watches etc. are sold. Many of these LCD controllers are compatible devices, so it can be handled by slightly modifying the library. Circuit diagram https://drive.google.com/file/d/1mS4rSrtLoIP_L8QzUfV9Y7tOIfLnUDaD/view?usp=sharing

BASCOM-AVR : Config Timer1 with optional parameter : REPLY

$
0
0
[code:1:f652a9b164]$regfile = "m8def.dat" Config Timer1 = Pwm , Prescale = 1 , Compare A Pwm = Disconnect , Compare B Pwm = Disconnect , Configuration = Pwm_off '8-bit-dual-slope-PWM without output and prescaler=1 Config Timer1 = Pwm , Prescale = 64 , Compare A Pwm = Clear Down , Compare B Pwm = Clear Down , Configuration = Pwm_on 'same WGM with activated Outputs and Prescaler=64 'both configs modifies TCCR1A and TCCR1B NOP Start Timer1 , Pwm_off 'Prescaler is changed but Compare Output Mode is not changed NOP Start Timer1 , Pwm_on 'Prescaler is changed again End[/code:1:f652a9b164] Start Timer1 does not modify TCCR1A, only TCCR1B (the Register containing the prescaler) is modified. After this I tried some other configurations (ChannelA=on, ChannelB=off <-->ChannelA=off, ChannelB=on) -> same result The lower two WGM-Bits in TCCR1A arent changed by using diffrent Timer-Modes, the upper two un TCCR1B are changed correctly. Summary: Start Timer1 does not modify TCCR1A, only TCCR1B (the Register containing the prescaler) is modified using the "m8def.dat".

BASCOM-AVR : AtTiny 202 : REPLY

$
0
0
[quote:c7b333efad="albertsm"]laborratte is right about the conditions: 32 registers ...[/quote:c7b333efad] 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? [quote:c7b333efad="albertsm"]and internal sram.[/quote:c7b333efad] 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 :-s ) Are there any plans to use the PTC with Bascom, in future?

BASCOM-AVR : There are an equivalent to */ Basic Stamp or PicBasic oper : NEWTOPIC

$
0
0
Hello; There are an equivalent to */ Basic Stamp or PicBasic operator ? like this : http://www.emesystems.com/OLDSITE/BS2math1.htm [url]http://www.emesystems.com/OLDSITE/BS2math1.htm[/url] [b:d456f0c9ab][color=red:d456f0c9ab](BASCOM-AVR version : 2.0.8.1 )[/b:d456f0c9ab][/color:d456f0c9ab]

BASCOM-AVR : AVRISP II STK500.exe serial not recognized : NEWTOPIC

$
0
0
Hi, I've setup a new PC, windows 7 , and reinstalled bascom and avrstudio4 The USB AVR ISP works in avrstudio no problem. I want to use the stk500.exe flasher, like i did in the past, but in the serial number field it shos a weird string instead of the serial (like on my previous win7 machine) Any hints?? [b:484b0d344b][color=red:484b0d344b](BASCOM-AVR version : 2.0.8.1 )[/b:484b0d344b][/color:484b0d344b]

BASCOM-AVR : AVRISP II STK500.exe serial not recognized : REPLY

$
0
0
Hi, Have a look at this. https://avrhelp.mcselec.com/libusb.htm?zoom_highlightsub=avr%2Bmkii

BASCOM-AVR : There are an equivalent to */ Basic Stamp or PicBasic oper : REPLY

$
0
0
have a look at the data types SINGLE and DOUBLE.
Viewing all 20606 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>