Thank you very much Peter for your promptest response! Target is our custom board and chip msp430f1611 as mentioned in subject. When I build with latest tool mspgcc-20110716 Olimex says that data addresses unavalable in the device and if I write it to device nevertheless it's works fine for the first time. By the way, I removed all routines that could write to flash, but after several power reset cycles program stops working right and seems became broken because it outputs on the LCD screen of device garbage. Unfortunateley Olimex does not says which exactly addresses it thinks unavailable in the device. Though when I load .elf through gdb, it (gdb) not tells me anything about address problems but the story repeats. I've tryed to read programm and data memory by Olimex and saved it to file immediatley after reprogramming device while it works good and compare it with data in device when it became broken and Olimex says that the data in flash the same.
Now I'll copy flags from my makefile: the g++ flags are -mmcu=msp430x1611 -MD -Wa -fomit-frame-pointer -fno-exceptions -fno-rtti -ffunction-sections -fdata-sections -funsigned-bitfields -fshort-enums -fno-threadsafe-statics -std=c++0x -Wall -Wimplicit -Wcast-align -Wpointer-arith -Wshadow -Wcast-qual -Wcast-align -Wredundant-decls -pedantic -save-temps assembler flags: -D_GNU_ASSEMBLER_ -DL_reset_vector__ -DL_ctors ld flags: -mmcu=msp430x1611,--sort-common,--cref,--gc-sections I've tryed to remove --gc-sections and -fdata-sections and it makes no sense... PS I'm using -mdisable-watchdog and have not implemented __low_level_init to disable watchdog. 21.08.2011 14:58, Peter Bigot пишет: > Based on "the firmware became broken after power-cycling" I have no idea > what the problem is. In the past, another poster here has suggested > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. > > Relevant information would include what hardware you're targeting > (launchpad? ez430-rf5200? other? which MSP430 chip?), how you're building > the application (complete compiler and linker commands), what the program > does when it works (does it write flash memory?), what it does when it > doesn't work, what addresses Olimex says are there that you don't think > should be, and whether the data it shows looks meaningful. Use > msp430-objdump to examine the differences between mspgcc4 and > mspgcc-20110716 built executables. > > Peter ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
