View previous topic :: View next topic |
Author |
Message |
uhrmacher
Joined: 15 Sep 2005 Posts: 60 Location: Donauwoerth
|
Posted: Sat Jul 04, 2020 9:02 pm Post subject: bascom bootloader run well for years but error messages now |
|
|
Hi bascom colleagues,
since many years i use the bootloader and there was no problem with that.... now, with a new application i had very small edited the filename and compiled the bootloader and BÄM! Unexpected a error message occurs.
Compiler error says:
Error : 1 Line : 419 Unknown statement [LDS R30 , {Z}] , in File : K:\PoolControl ATMega2561_VFD\Flashware\Poolcontrol Flashware\poolcontrol_III_Bootloader_v1.1.bas
Error : 1 Line : 420 Unknown statement [LDS R31 , {Z + 1}] , in File : K:\PoolControl ATMega2561_VFD\Flashware\Poolcontrol Flashware\poolcontrol_III_Bootloader_v1.1.bas
that surprises me because this code for years was never changed and runs in former application perfect. I#m not an assembler freak but the LDS syntax for me "looks good" and it has run perfect in the past.
I use the BASCOM 2.0.8.0, compiler 2.0.8.0.001, IDE version 2.0.8.0.006 ( licensed)
I have noticed, that the Bascom update wizard does not show me the update to 2.0.8.2, he says no update necessary.
I dunno how thats two separate problems or they have a relationship.
Any ideas an comments are very wellcomed, i struggle since many hour about the problem. My bootloader code please find below:
[b][color=red](BASCOM-AVR version : 2.0.8.0 , Latest : 2.0.8.2 )[/b][/color] |
|
Back to top |
|
|
Evert :-)
Joined: 18 Feb 2005 Posts: 2156
|
|
Back to top |
|
|
MWS
Joined: 22 Aug 2009 Posts: 2262
|
Posted: Sun Jul 05, 2020 8:23 am Post subject: |
|
|
Evert wrote: | ...must been now between this; |
alternatively each opcode has to be preceded with an exclamation mark, !LDS .... |
|
Back to top |
|
|
uhrmacher
Joined: 15 Sep 2005 Posts: 60 Location: Donauwoerth
|
Posted: Sun Jul 05, 2020 9:02 am Post subject: ! solved :-) |
|
|
Goedemorgen Evert, Hello MWS // solved
With the kindly help of you both i was able to fix the problem:
for, ...i don't know the reason, in this file the $asm and $end asm codes gone lost.... i cannot recognize why, its long time ago and i used most only the .hex...
Anyhow guys, i thank you to gave me the right "bril" so sharpen my watching to the code !!
I corrected it and - snap - runs !
Ontzettend bedankt, thank you so much and have a nice sunny sunday !
Ingolf
------------------------------------
.....>
Bitwait Spmcsr.0 , Reset
Bitwait Eecr.1 , Reset
$Asm
lds r30,{Z}
lds r31,{Z+1}
'#IF Loaderchip = 128
#IF _romsize > 65536
lds r24,{Z+2}
sts rampz,r24
#ENDIF
lds r0, {vl}
lds r1, {vh}
$end asm
Spmcsr = Spmcrval
$asm
spm
nop
nop
$end asm |
|
Back to top |
|
|
albertsm
Joined: 09 Apr 2004 Posts: 5913 Location: Holland
|
Posted: Fri Jul 10, 2020 11:40 am Post subject: |
|
|
when you update it is highly recommended to read the history notes. Or the 'what is new in xxxx' from the help.
the asm domain allows to use asm help with CTRL+SPACE. Because some mnemonics share the same name like sub and out, it was more practical to have a specific asm identifier.
when you look at the updates samples you also would have found the new syntax. _________________ Mark |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
|
|