From davidbonnin at free.fr Thu Aug 6 22:04:16 2009 From: davidbonnin at free.fr (davidbonnin at free.fr) Date: Fri, 7 Aug 2009 00:04:16 +0200 (CEST) Subject: write to flash 52235EVB with light edition Message-ID: <1473587203.2679071249596256736.JavaMail.root@spooler1-g27.priv.proxad.net> Hello, Does the next version of SCG++ lite will can write to flash? Is there an external tool on linux that can do it? Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From fklaric at koncar-institut.hr Wed Aug 19 11:16:13 2009 From: fklaric at koncar-institut.hr (=?iso-8859-2?Q?Filip_Klari=E6?=) Date: Wed, 19 Aug 2009 13:16:13 +0200 Subject: m5329 compiling and linking questions Message-ID: <74DEA4DCF5979F4CB7661A427E85E983F542FFF3@ATHENA.koncar-institut.local> I have COBRA5329 board and I am a bit new to embedded programming so few questions When I compile my source with m68k-uclinux-gcc -mcpu=5329 -Wl,-elf2flt -o exec_file file I get working executable When i do it with m68k-uclinux-gcc -o obj_file -c file & m68k-uclinux-ld -L(to m5329 libc.a) -elf2flt -o exec_file obj_file It gives 'Illegal instruction' error on target, acctualy it doesn't work with any libc library i select or with -msep-data or -mid-shared-library options What is the catch? What happens when I use -mcpu option and auto-link file to compiler differently then when i do it manually? ALSO I get 'Unable to mmap process text, errno 12' a lot of times and it shouldn't be free memory problem because my buddyinfo gives "Node0, zone Normal 3 1 1 1 1 1 1 0 0 1 1 0" It happens with any application that i compile with -msep-data option, even for those with few kBs in size Is something wrong with my linker scripts (tried default and some changes it didn't work)? Could it be that fault is in msep-data libraries? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan at codesourcery.com Wed Aug 19 12:02:35 2009 From: dan at codesourcery.com (Daniel Jacobowitz) Date: Wed, 19 Aug 2009 08:02:35 -0400 Subject: [coldfire-gnu-discuss] m5329 compiling and linking questions In-Reply-To: <74DEA4DCF5979F4CB7661A427E85E983F542FFF3@ATHENA.koncar-institut.local> References: <74DEA4DCF5979F4CB7661A427E85E983F542FFF3@ATHENA.koncar-institut.local> Message-ID: <20090819120234.GG19715@caradoc.them.org> On Wed, Aug 19, 2009 at 01:16:13PM +0200, Filip Klari? wrote: > I have COBRA5329 board and I am a bit new to embedded programming > so few questions > > When I compile my source with > > m68k-uclinux-gcc -mcpu=5329 -Wl,-elf2flt -o exec_file file > I get working executable > > When i do it with > m68k-uclinux-gcc -o obj_file -c file > & > m68k-uclinux-ld -L(to m5329 libc.a) -elf2flt -o exec_file obj_file Don't try to use ld directly. We strongly recommend using GCC to link. If you want to see what it's doing behind the scenes, you can add -v to the compiler command line. -- Daniel Jacobowitz CodeSourcery