version 2083

albertsm · Joined: 09 Apr 2004 Posts: 5915 Location: Holland

After long testing the 2083 version is now released.
If you already had the 2083, check the version in the help about. It should be 2083.003

Like always this version fixes bugs and offers new features.
But the most important changes is support for the xtiny AVR range. Read more about xtiny in the help. While dat and sample files are included, it will not compile since it requires an add on.
We had a long internal discussion about charging for support, for updates, or both. I think charging for a new platform that is not needed by everyone is a good alternative.

Bugs you can report to support. As always, make sure you include all important info.

Here is the change list:

- new option SAFE for variables. Dim b as bit SAFE , see help.
- added BOOTONLY option to $LOADER directive. $loader bootaddress[,BOOTONLY] this will write just the boot loader code to the BIN file. The HEX remains as is.
- you can select the Options_Select_Settings_File now. This setting is stored in the registry.
- project files are stored with absolute files names inside the prj file. An absolute file name is relative to the location.
- simulator bug fixed where SI file simulation data was not processed properly.
- MemFill added.
- using instr() with {xxx} for the search string does not work : pos=instr(someAString,"{065}")
- using compare_a/compare_b=clear for timer0 resulted in SET instead of CLEAR.
- bascomp command line utility updated to support new file structure
- multiple instances bug fixed.
- mcs.lbx was not in sync with mcs.lib (it was not compiled when a last minute change was made)
- when using channel specifier without # you will get an error
- stk500v2 based programmers like mkII and stk500v2 could give a program error when your code contains empty blocks And the processor has multiple 64KB segments. applies to normal mega only.
- crc8 overloaded version added for big strings.
- 2082 broke the default printing function
- added DES asm instruction.
- added DesEncrypt and DesDecrypt which are also supported by the simulator
- inputbin accepts an optional variable for the number of bytes to receive. delimited by a ;
- simulator update.
- simulator double click cycles, will reset cycles
- simulator allows to load a custom serial data file from file
- Xtiny support, requires a commercial add on
- CTS/RTS bug fixed : only part of the buffer was used
- added PA version of dat files M88PAdef,M644PAdef,M48PAdef,M168PA. These are almost the same as the P versions. They are binary compatible and have the same ID
- searching in files would not search in the specified folder when the folder name contained a space. Instead the root folder was used.
- $programmer option did not support conditional compilation. It was global. Now supports #IF/#ENDIF. but only when 'Use new method' is used in environment IDE options.
- CLEAR serialinx buffer did not clear the RTS pin when cts/rts was used for xmega uarts 4-7.
- xmega high baud calculation > 2MB and higher did not support double rate flag resulting in a wrong baud rate
- for next using a step for bytes could fail when the byte boundary was crossed.
- xmega num2str code rewritten and xmega routine rewritten that used _XmegaFix_Rol_R1014 and _XMEGAFIX_CLEAR. These routines are not used anymore!
- using a string function with select case, could result in improper branching, depending on the user function.
select case mid(someString,start,len) for example.
- bascom-AVR and the SETUP are now code signed.
- CONFIG XPIN for the E-series : slewrate will be set the whole port, not for an individual pin
- crc16uni can handle 65535 bytes
- low/high can be used as a procedure too for BASCOM-8051 compatibility.
- UPDI programmer can write fuses

(BASCOM-AVR version : 2083 , Latest : 2.0.8.3 )

KenHorse · Joined: 16 Jul 2004 Posts: 523

After installing the upgrade (over the top of the existing 2.0.8.2), when I try to launch I receive the error (even when trying to run as Admin) as attached. Same error even if launching directly from the installation directory

Printpix52 · Joined: 18 Jun 2014 Posts: 282 Location: D.F.

After updates 2.0.8.3 it does not recognize atmega 328P. Rolling Eyes

[img][/img]

SZTRAD · Joined: 30 Dec 2019 Posts: 165

Thank you, Mark
so where can i buy extensions for xttins? I have one project here where I am forced to use these processors and I am slowly going crazy from "c". Writing down all the libraries (especially communication) slowly but surely stops entertaining me. I'd like to use what I've been used to for 20 years. I was forced to buy a microbacis, but the way of programming suits me even less than "c".
So how do I pay?
Otherwise, I was able to run it compared to my colleagues without a problem, I just did not find sample examples.
RS

albertsm · Joined: 09 Apr 2004 Posts: 5915 Location: Holland

@KenHorse : you should install into a new folder. installing over 2082 should also work but that is not tested. Installing from within bascom is tested and that works properly. Also manual installing by downloading, unzipping, and running setup was tested. Tests were done on Win7 and Win10.
You might want to try again. run bascom with admin rights so it has all rights to install and install into a new folder.

@Printpix52 : you have selected the SAMPLE ELECTRONICS programmer. This is the default. So my guess is that you did not made the changes to the options.
Under Options, there is a new option : Select Settings File
It allows to make a copy of an option file and to use that. So this way you can select your old 2082 file, and make a copy for 2083.
It also allows to select the option file location.

@SZTRAD : i will ask sales to enable the add on. So it should be there in a short while.

SZTRAD · Joined: 30 Dec 2019 Posts: 165

Thanks for the answer, Mark
I'll ask one more time, where can I find those examples? Or can't I see due to my age?

SZTRAD · Joined: 30 Dec 2019 Posts: 165

Oh, I get it. I'm sorry, Mark. Rolling Eyes

I overlooked an item in the store explaining how it is.
Payment will be made in the afternoon.

albertsm · Joined: 09 Apr 2004 Posts: 5915 Location: Holland

the samples are not included. they come with the add on.
but it is not really shocking. for example :

SZTRAD · Joined: 30 Dec 2019 Posts: 165

Thank you as I wrote I overlooked the offer with an explanation of xtiny add on.
Just for fun, are you going to implement AVR128 as well? If so, as you can see in time?

SZTRAD · Joined: 30 Dec 2019 Posts: 165

Otherwise, I'm glad that the entry looks standard according to the custom in Bascom. I was afraid that you went the way of a competitive environment where everything is set manually for these processors and it is extremely confusing and you can't even program without knowledge of the data sheet.

albertsm · Joined: 09 Apr 2004 Posts: 5915 Location: Holland

everything is done the bascom way. but as microchip renamed the hardware, you need to use the new hardware names as well. for example, TWI was TWIC/TWID for xmega but is now TWI0/TWI1 (did not found a xtiny with more than one TWI) but you get the idea.
And some hardware does not have the same options, or more options.

AVR128 : that has been asked before. It depends on 2 things : if there is sufficient interest in the xtiny and in this new AVR128.
From architectural point, the processors are similar. But reading the sheets, implementing support, testing, documentation and user support while maintaining the old range, it is a lot of work. So we will decide later.
There are lot of other things in progress too and that was all delayed because of xtiny.

SZTRAD · Joined: 30 Dec 2019 Posts: 165

If we have fun openly Mark. I'm pushed down by prices and there's no other solution than to reach for new processors that are simply cheaper. As for the piece quantity, it doesn't matter how much it costs in the beginning, but my products are produced in larger quantities and then the differences begin to show.
Likewise, support for 808.9 atmegs and their clones would be interesting. Unfortunately, Microchip has built a pricing policy so that everything new is sometimes even cheaper.
If I can reach for the older Atmegs, but if it costs me atmega808 0.75eur and atmega8 1.75eur, then the choice is quite clear.
For my part and I agree with the gentlemen involved in the development and testing that fell here before, so it is not a problem to buy an extension. I believe and I know that there is a lot of work. I can imagine how many hours a person spends on it, especially when something goes wrong. I'm a programmer for a PLC and SCADA system, among other things, so I also often tear my hair out of nervous systems.
To this day, your system was enough for every job I did (as you can see in my license number), the only flaw in the beauty was the incorporation of new processors. Which I've changed now. And to tell the truth, I didn't even need to touch the xmegs to this day, because they are useless to me. If I need something with performance as a superstructure, I go the same way with Rasp and similar boards or purely ARM. But still because I do a lot of sensors and other similar things where I only need 8bit, so I reach for the AVR. STM8 and PIC somehow didn't get to my heart.
So thank you for the long years of your good work and I hope that you will continue to do so.
RS
ps forgive me english is not my native language and i have always had problems learning languages.

olhexy · Posted: Wed Jul 15, 2020 10:24 pm Post subject:

Money payments go fast these days. Got my Xtiny Add-on and working.
It took 5 mails, but they came within only a few minutes.
It includes a license check of your Bascom.

You have to do 2 installs: first the Add-on, then with a separate mail comes AVRUPDI.license and install that as well.

I did a quick test, and now my Samples directory is cluttered with compiler outputfiles... (old problem).

Paulvk · Joined: 28 Jul 2006 Posts: 1257 Location: SYDNEY

There is now a XTINY3216 & XTINY3217 so more to add!
Regards Paul

six1 · Joined: 27 Feb 2009 Posts: 553