BASCOM Version ist veröffentlicht

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • BASCOM Version ist veröffentlicht…e=viewtopic&p=77723#77723

      BASCOM-AVR History
      (c) 1995-2019 MCS Electronics
      the history items are very short descriptions of changes. it is only intended
      to allow you to find the info in the help.
      - log files are stored user\appdata\roaming\mcs electronics
      - xml settings file is also located in this folder
      - xml settings file has a new name with the version in it : bascavr2082.xml
      - samples can be located in user\documents folder or bascom application folder. Specify during setup
      - xmega timer resolution :
      In version up to 2081:
      BYTE or 8
      SPLIT or 16 or 32

      In version 2082
      BYTE or 8
      SPLIT or 32
      NORMAL or 16
      Thus when using 16 before, change your code to use SPLIT or 32

      - rearranging memory order for usb support caused a bug in config clock : the date time bytes are not mapped after each other. Fixed.
      - START/STOP statements worked on the wrong register for the TINY1634
      - i2c_twi_multi lib had a problem in the readbyte function.
      - SPIMOVE added for Xmega
      - split screen did not allow copy & paste
      - USI slave support added for tiny1634
      - All DAT files are now stored in a sub folder named DAT. This means you need to copy your DAT file to this folder if you made custom DAT files.
      - some registers of tcc1 were missing in xmega D3 series
      - read only files could not be opened anymore. fixed.
      - On win10 you could get a HID error message.
      - w5500 tcp lbx : removed RST status bit check since the bit never becomes 0 and hangs the code
      - url2ip bug fix. one byte of the IP address could get trashed
      - url2ip added to w5500
      - new samples for w5500 wiznet chip
      - accessing a zero based array inside a sub coulld result in an index error.
      - simulator did not support writing to xmega portx_CLR _SET and TGL registers
      - using search in files function could result in 'out of bound' error.
      - manchesterEnc and manchesterDec functions added for manchester coding/decoding
      - assigning a byte with a string constant with spaces, resulted in 0, not 32.
      - VARPTR() function returned &H1000 too much for Xmega ERAM data type.
      - using getadc() with 2 numeric parameters or constants like : getadc(4,&H20) would not set the right bits.
      - i2csend and i2creceive updated for xmega. after the start/slave address, the status is now checked and does not send data in case of a bus problem. this to prevent a hangup in the twi logic.
      - printing supports selection of text and page range now. you need to use print preview for this.
      - OUT instruction did not clear RAMPZ for Xmega with ROM > 64KB and normal SRAM.
      - PS2MOUSEXY accepts an additional optional parameter for mouse wheel support. Notice that you MUST download an update of the ps2 lib add on
      - config spi on non xmega did not support the extended mode for HW SPI
      - config tcpip now supports SPI1 for the SPI bus
      - windows 10 DEP and ASLR support added.
      - printbin: when using automatic rs485 and printing a long/dword constant on a chip with extended port register, R23 was trashed. Example : printbin &HABCDEF00
      - FLIP() function resulted in an error about $REGS
      - terminal emulator component is replaced in order to support windows DEP/ASLR. This means that some features from the terminal emulator have changed.
      - printbin can print a variable amount of bytes now. while ; is used to separate multiple variables, the comma can be used to specify the amount of bytes
      like : printbin ar(1) , numbytes ; othervar
      this makes the syntax compatible with the old syntax. We recommend to use the new syntax
      - terminal emulator custom messages extended to 16
      - UPDI programmer added for new AVR processors with UPDI interface.

      With DOS things were simple : all files could go in a folder and sub folder. To make a backup all you had to do was using XCOPY.
      With Windows things are not so simple : files are located all over the PC. Some folders are write protected and to make a backup is not so simple.
      A lot of customers are looking for the SAMPLE files. These are put in the documents folder and can be accessed using the File, Open Sample option.
      In 2082 the preferred folder for installation is C:\MCS\BASCAVR2082
      But of course you are free to install in any other folder of your choice.
      The samples are installed in a sub folder of the application folder too. But you can install in any other folder as well.
      In the Environment Options of the IDE you can specify which folder you want to use for the sample files.
      Code first, think later - Natural programmer :D
    • Hab ich mir schon gedacht...nur, auf meinem Rechner gibt es keine BCSAVR.dll
      Seit vielen Jahren läuft bis zur letzten Version BASCOM-AVR lizensiert und läuft auch immer noch. Aber eine BSCAVR.dll existiert bei mir nicht! :?: Ich kann nur mit einer BASC-AVR.dll dienen. Sehr komisch das Ganze.