View previous topic :: View next topic |
Author |
Message |
albertsm
Joined: 09 Apr 2004 Posts: 5913 Location: Holland
|
Posted: Sat Jan 24, 2015 10:08 pm Post subject: |
|
|
zofikke : just make sure the DAT files and LIBS were updated as well.
I would advise to download the full setup. Then install it into a NEW folder and run that version from a link on your desktop.
Or use the update wiz to update the LIB and DAT files to make sure all is properly updated.
mmarlet: i did mention in the help that the errors form code explorer are a beta option. By default it is off and i only enabled it since it can be very useful.
we use it to check the parser from the IDE. It requires that all DAT files have 100% CONFIG sections, otherwise it will give 'errors'.
In any case, all errors should point to the error origin. a file or project should always give the same (amount) of errors. No matter the time of the day. At a later stage there will be time to report possible problems but now it does not make sense since i already know the cause. _________________ Mark |
|
Back to top |
|
|
rsavas
Joined: 10 Aug 2010 Posts: 197 Location: Baldwin, Ontario
|
Posted: Sun Jan 25, 2015 2:58 am Post subject: |
|
|
I discovered that if I define a variable in the past such as
DIM R1 as Byte
I now get the following
Error : 25 Line : 513 Variable already dimensioned [Variable already dimensioned] , in File : C:\Projects\Elektor\100126-DSP Radio\DSPradioMega(neu)\Elektor DSPradio new(xmega) 1.1.4.bas
I looked in the Keyword reference list and they do not show up there. |
|
Back to top |
|
|
mmarlette
Joined: 30 Nov 2007 Posts: 311 Location: Delano, MN
|
Posted: Sun Jan 25, 2015 3:29 am Post subject: |
|
|
One(repeated many times) of my code explorer errors were if the IF statement, expression type mismatch.
Reported line error in code explorer:
If lngTimeDelta => 4 then
....
End if
Fix: Just exchange the => to >=
Error then gone in code explorer. |
|
Back to top |
|
|
aphawk
Joined: 23 Jan 2010 Posts: 168 Location: Brazil
|
Posted: Sun Jan 25, 2015 4:29 am Post subject: |
|
|
Rsavas,
R0, R1, ......., R31 are the name of the registers used when in ASM mode. Until the last version, Bascom don't reserves this variable names.
But in this actual version, these registers are reserved. Maybe Mark will update the manual about this.
Try change the name to Ra0, Ra1, etc, and your program will compile without error.
Paulo |
|
Back to top |
|
|
rsavas
Joined: 10 Aug 2010 Posts: 197 Location: Baldwin, Ontario
|
Posted: Sun Jan 25, 2015 4:40 am Post subject: |
|
|
Sure, changing the DIM R... names is exactly what I did and it fixed that problem!
I upgraded to try to fix another problem where the compiler (2.0.7.7) reported an error when I was using a program that used these definations $eeprom and $eepromhex directives for a xmega target, using 2.0.7.8 fix that problem. The same code when compiled with 2.0.7.7 for a M644 target worked okay.
Error : 377 Line : 3971 Unexpected non numeric characters found [2087: [] , in File : C:\Projects\Elektor\100126-DSP Radio\DSPradioMega(neu)\eeprom_test-v1.0.0.bas
Error : 377 Line : 3971 Unexpected non numeric characters found [2151: [] , in File : C:\Projects\Elektor\100126-DSP Radio\DSPradioMega(neu)\eeprom_test-v1.0.0.bas |
|
Back to top |
|
|
EDC
Joined: 26 Mar 2014 Posts: 971
|
Posted: Sun Jan 25, 2015 9:56 am Post subject: |
|
|
I allways read Changelog or History to know about them. For example I use "Config Lcd = 20x4" because "x" is new preffered style to do this.
Bigger or equal it`s a basic mathematical "stuff". When I read once again about "R1..." or that >= instead => then I think one rule should be added.
Please read Changelog again before posting Don`t be mad, but someone spend time to wrote this instructions. |
|
Back to top |
|
|
|