Pumpkin, Inc.

Pumpkin User Forums

starting problems using salvo in IAR

For issues specific to Atmel's AVR and MegaAVR microcontrollers, including Atmel AVRStudio and ImageCraft's ICCAVR C compiler.

starting problems using salvo in IAR

Postby mirkash » Sat Jul 31, 2004 9:16 am

When I tried to build tutorial project tu1
I got this linker message
Warning[w45]: Memory attribute info mismatch between modules portiaravr ( C:salvolibiaravr-v3sfiaravr1t-m.r90 ) and main ( C:salvo ut u1sysacDebugObjmain.r90

I'm using Salvo Lite and Embedded Workbench 3.2 Evaluation for AVR

What to do?

mirkash
 
Posts: 3
Joined: Fri Jul 30, 2004 11:00 pm
Location: Belgrade

Re: starting problems using salvo in IAR

Postby aek » Sat Jul 31, 2004 9:27 am

Hello.

Using Salvo Lite v3.2.4-a and IAR AVR EW v3.2, I get a successful build:

code:
Rebuilding configuration: tu1lite - Debug

0 file(s) deleted.

main.c
iccavr.exe --cpu=8515 -mt -o C:salvo ut u1sysacDebugObj -D SYSAC -D MAKE_WITH_FREE_LIB -lCN C:salvo ut u1sysacDebugList -lA C:salvo ut u1sysacDebugList --initializers_in_flash -z9
--no_cross_call --debug -e -I C:salvo ut u1sysac -I c:salvoINC -I c:salvoTUTTU1 -I C:Program FilesIAR SystemsEmbedded Workbench 3.2avrINC -I C:Program FilesIAR SystemsEmbedded
Workbench 3.2avrINCCLIB --eeprom_size 512 C:salvo ut u1main.c

IAR Atmel AVR C/EC++ Compiler V3.10A/W32
Copyright 1996-2003 IAR Systems. All rights reserved.

6 bytes of CODE memory

Errors: none
Warnings: none

mem.c
iccavr.exe --cpu=8515 -mt -o C:salvo ut u1sysacDebugObj -D SYSAC -D MAKE_WITH_FREE_LIB -lCN C:salvo ut u1sysacDebugList -lA C:salvo ut u1sysacDebugList --initializers_in_flash -z9
--no_cross_call --debug -e -I C:salvo ut u1sysac -I c:salvoINC -I c:salvoTUTTU1 -I C:Program FilesIAR SystemsEmbedded Workbench 3.2avrINC -I C:Program FilesIAR SystemsEmbedded
Workbench 3.2avrINCCLIB --eeprom_size 512 C:salvosrcmem.c

IAR Atmel AVR C/EC++ Compiler V3.10A/W32
Copyright 1996-2003 IAR Systems. All rights reserved.

0 bytes of CODE memory (+ 6 bytes shared)
17 bytes of DATA memory

Errors: none
Warnings: none

Linking
xlink.exe C:salvolibiaravr-v3sfiaravr1t-m.r90 C:salvo ut u1sysacDebugObjmain.r90 C:salvo ut u1sysacDebugObjmem.r90 -o C:salvo ut u1sysacDebugExe u1lite.d90 -rt -l C:salvo ut u1
sysacDebugList u1lite.map -xms -IC:Program FilesIAR SystemsEmbedded Workbench 3.2avrLIB -f C:Program FilesIAR SystemsEmbedded Workbench 3.2avrsrc emplatecfg8515.xcl
-D_..X_HEAP_SIZE=10 -D_..X_CSTACK_SIZE=20 -D_..X_RSTACK_SIZE=20 -e_small_write=_formatted_write -e_medium_read=_formatted_read -f C:Program FilesIAR SystemsEmbedded Workbench 3.2avr
src emplatecfg1t.xcl -D_..X_FLASH_BASE=_..X_INTVEC_SIZE -H1895 -h(CODE)0-(_..X_INTVEC_SIZE-1) -D_..X_EXT_SRAM_BASE=_..X_SRAM_BASE -D_..X_EXT_SRAM_END=_..X_SRAM_BASE
-D_..X_EXT_ROM_BASE=_..X_SRAM_BASE -D_..X_EXT_ROM_END=_..X_SRAM_BASE -D_..X_EXT_NV_BASE=_..X_SRAM_BASE -D_..X_EXT_NV_END=_..X_SRAM_END
-D_..X_EXT_CSTACK_BASE=_..X_SRAM_BASE -D_..X_EXT_CSTACK_END=_..X_SRAM_BASE -D_..X_EXT_RSTACK_BASE=_..X_SRAM_BASE -D_..X_EXT_RSTACK_END=_..X_SRAM_BASE C:Program
FilesIAR SystemsEmbedded Workbench 3.2avrlibclibcl1t.r90

IAR Universal Linker V4.56F/386
Copyright 1987-2003 IAR Systems. All rights reserved.

316 bytes of CODE memory (+ 24 range fill )
71 bytes of DATA memory

Errors: none
Warnings: none


Total number of errors: 0
Total number of warnings: 0


The eval versions of IAR's compilers are normally identical in function to the standard versions, so I'm not sure where your problem is ...

------------------

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: starting problems using salvo in IAR

Postby aek » Sat Jul 31, 2004 9:29 am

Ah, maybe your problems is that you're using an AVR other than the '8515?

If so, please refer to the Salvo Compiler Reference Manual for an appropriate choice of Salvo library.

http://www.pumpkininc.com/content/doc/manual/rm-iaravr.pdf

------------------

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: starting problems using salvo in IAR

Postby mirkash » Sun Aug 01, 2004 5:09 am

these are the results I'm getting. I don't see any differnce except in warnings
-----------------------------------------
code:
main.c
iccavr.exe --cpu=8515 -mt -o C:salvo ut u1sysacDebugObj -D SYSAC -D MAKE_WITH_FREE_LIB -lCN C:salvo ut u1sysacDebugList -lA C:salvo ut u1sysac
DebugList --initializers_in_flash -z9 --no_cross_call --debug -e -I C:salvo ut u1sysac -I c:salvoINC -I c:salvoTUTTU1 -I C:Program FilesIAR Systems
Embedded Workbench Evaluation versionavrINC -I C:Program FilesIAR SystemsEmbedded Workbench Evaluation versionavrINCCLIB --eeprom_size 512 C:
salvo ut u1main.c

IAR Atmel AVR C/EC++ Compiler V3.20A/W32, Evaluation Version
Copyright 1996-2004 IAR Systems. All rights reserved.
Time limited license: 17 days left

6 bytes of CODE memory

Errors: none
Warnings: none

mem.c
iccavr.exe --cpu=8515 -mt -o C:salvo ut u1sysacDebugObj -D SYSAC -D MAKE_WITH_FREE_LIB -lCN C:salvo ut u1sysacDebugList -lA C:salvo ut u1sysac
DebugList --initializers_in_flash -z9 --no_cross_call --debug -e -I C:salvo ut u1sysac -I c:salvoINC -I c:salvoTUTTU1 -I C:Program FilesIAR Systems
Embedded Workbench Evaluation versionavrINC -I C:Program FilesIAR SystemsEmbedded Workbench Evaluation versionavrINCCLIB --eeprom_size 512 C:
salvosrcmem.c

IAR Atmel AVR C/EC++ Compiler V3.20A/W32, Evaluation Version
Copyright 1996-2004 IAR Systems. All rights reserved.
Time limited license: 17 days left

0 bytes of CODE memory (+ 6 bytes shared)
17 bytes of DATA memory

Errors: none
Warnings: none

Linking
xlink.exe C:salvolibiaravr-v3sfiaravr1t-m.r90 C:salvo ut u1sysacDebugObjmain.r90 C:salvo ut u1sysacDebugObjmem.r90 -o C:salvo ut u1sysacDebug
Exe u1lite.d90 -rt -l C:salvo ut u1sysacDebugList u1lite.map -xms -IC:Program FilesIAR SystemsEmbedded Workbench Evaluation versionavrLIB -f C:Program
FilesIAR SystemsEmbedded Workbench Evaluation versionavrsrc emplatecfg8515.xcl -D_..X_HEAP_SIZE=10 -D_..X_CSTACK_SIZE=20 -D_..X_RSTACK_SIZE=20
-e_small_write=_formatted_write -e_medium_read=_formatted_read -f C:Program FilesIAR SystemsEmbedded Workbench Evaluation versionavrsrc emplate
cfg1t.xcl -D_..X_FLASH_BASE=_..X_INTVEC_SIZE -H1895 -h(CODE)0-(_..X_INTVEC_SIZE-1) -D_..X_EXT_SRAM_BASE=_..X_SRAM_BASE
-D_..X_EXT_SRAM_END=_..X_SRAM_BASE -D_..X_EXT_ROM_BASE=_..X_SRAM_BASE -D_..X_EXT_ROM_END=_..X_SRAM_BASE
-D_..X_EXT_NV_BASE=_..X_SRAM_BASE -D_..X_EXT_NV_END=_..X_SRAM_END -D_..X_EXT_CSTACK_BASE=_..X_SRAM_BASE
-D_..X_EXT_CSTACK_END=_..X_SRAM_BASE -D_..X_EXT_RSTACK_BASE=_..X_SRAM_BASE -D_..X_EXT_RSTACK_END=_..X_SRAM_BASE C:Program FilesIAR
SystemsEmbedded Workbench Evaluation versionavrlibclibcl1t.r90

IAR Universal Linker V4.58H/386
Copyright 1987-2004 IAR Systems. All rights reserved.
Warning[w45]: Memory attribute info mismatch between modules portiaravr ( C:salvolibiaravr-v3sfiaravr1t-m.r90 ) and main ( C:salvo ut u1sysacDebugObjmain.r90
)
Warning[w45]: Memory attribute info mismatch between modules portiaravr ( C:salvolibiaravr-v3sfiaravr1t-m.r90 ) and main ( C:salvo ut u1sysacDebugObjmain.r90
)

316 bytes of CODE memory (+ 24 range fill )
71 bytes of DATA memory

Errors: none
Warnings: 2


Total number of errors: 0
Total number of warnings: 2



-----------------------------------------

[This message has been edited by aek (edited August 01, 2004).]

mirkash
 
Posts: 3
Joined: Fri Jul 30, 2004 11:00 pm
Location: Belgrade

Re: starting problems using salvo in IAR

Postby aek » Sun Aug 01, 2004 8:46 am

Hmmm... it looks like IAR has perhaps changed something in the v3.20 compiler vs. the v3.10 compiler --- we'll have to take a more detailed look after downloading the v3.20compiler.

In spite of the warning, does the code run? It may not be a serious issue ... Best to test tu4lite in the C-SPY simulator ...

------------------

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: starting problems using salvo in IAR

Postby mirkash » Mon Aug 02, 2004 1:41 am

as far as I can see the code runs correctly in C-Spy
mirkash
 
Posts: 3
Joined: Fri Jul 30, 2004 11:00 pm
Location: Belgrade

Re: starting problems using salvo in IAR

Postby aek » Mon Aug 02, 2004 1:49 am

Unless IAR changed the calling convention, register usage, etc. between the 3.10 and 3.20 compilers, it's probably not an issue ...

As soon as we can evaluate with the v3.20 compiler we may have an answer (IAR's download server appears to be down) ...

------------------

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: starting problems using salvo in IAR

Postby bjaenke » Thu Sep 02, 2004 4:44 am

Was this problem ever fixed?
bjaenke
 
Posts: 2
Joined: Wed Sep 01, 2004 11:00 pm
Location: Elyria,OH,44036

Re: starting problems using salvo in IAR

Postby aek » Thu Sep 02, 2004 7:48 am

Working on it .. will report back when we have more data.

------------------

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: starting problems using salvo in IAR

Postby MiM » Wed Oct 20, 2004 2:30 am

I'm just starting with Salvo Lite AVR (v3.2.4-dev2) and IAR EWAVR (Evaluation Version v3.20C) to evaluate if worth to use for a new real project. Unfortunately I encountered exactly the same problem like mirkash, i.e. warnings [w45] with all tutorial and example projects.

Isn't the problem worked out yet ? Please report. Thanks.

MiM
 
Posts: 4
Joined: Tue Oct 19, 2004 11:00 pm
Location: Bratislava, SK, EU

Next

Return to Atmel AVR and MegaAVR

Who is online

Users browsing this forum: No registered users and 0 guests

cron