February 25, 2008 - 5:25pm
Guest |
The following is an instance of a program compiling followed by the failure:
==========
Building Q:\Software Design Library\5900 Truck Scale\SCRPRS.C
Running : GCC
\"C:\Program Files\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-gcc.exe" -MD -D_STM32F101CBT6_ -D_STM3x_ -D_STM32x_ -mthumb -mcpu=cortex-m3 "Q:\Software Design Library\5900 Truck Scale\SCRPRS.C" -o "Q:\Software Design Library\5900 Truck Scale\SCRPRS.o" -I "C:\Program Files\Raisonance\Ride\Lib\ARM\include" -I "." -I "Q:\Software Design Library\5900 Truck Scale\drivers" -I "Q:\Software Design Library\5900 Truck Scale\STM32F10xFWLib\FWLib\library\inc" -c -funsigned-char -g -fshort-enums -ffunction-sections -pedantic -Wall -Wswitch -Wshadow -Wunused -mlittle-endian
\"C:\Program Files\Raisonance\Ride\Bin\rexrdr.exe" "Q:\Software Design Library\5900 Truck Scale\SCRPRS.lst" 0 "C:\Program Files\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-objdump.exe" --disassemble -all --source "Q:\Software Design Library\5900 Truck Scale\SCRPRS.o"
\"C:\Program Files\Raisonance\Ride\Bin\rexrdr.exe" "Q:\Software Design Library\5900 Truck Scale\SCRPRS.o.sizetmp" 0 "C:\Program Files\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-size.exe" "Q:\Software Design Library\5900 Truck Scale\SCRPRS.o"
Building Q:\Software Design Library\5900 Truck Scale\screen.c
Running : GCC
\"C:\Program Files\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-gcc.exe" -MD -D_STM32F101CBT6_ -D_STM3x_ -D_STM32x_ -mthumb -mcpu=cortex-m3 "Q:\Software Design Library\5900 Truck Scale\screen.c" -o "Q:\Software Design Library\5900 Truck Scale\screen.o" -I "C:\Program Files\Raisonance\Ride\Lib\ARM\include" -I "." -I "Q:\Software Design Library\5900 Truck Scale\drivers" -I "Q:\Software Design Library\5900 Truck Scale\STM32F10xFWLib\FWLib\library\inc" -c -funsigned-char -g -fshort-enums -ffunction-sections -pedantic -Wall -Wswitch -Wshadow -Wunused -mlittle-endian
\"C:\Program Files\Raisonance\Ride\Bin\rexrdr.exe" "Q:\Software Design Library\5900 Truck Scale\screen.lst" 0 "C:\Program Files\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-objdump.exe" --disassemble -all --source "Q:\Software Design Library\5900 Truck Scale\screen.o"
Build failed
==========
It is unclear why the build failed. The failing file is 6247 lines long; the passing one is 1076 lines long. Of the eleven project files, all compile without error except this one.
|
Hello
We made some test here with different size of files and we also meet a build failure for a very big file
Your conclusion seems to be the good one
But yet we can not say which parameter of the folder size is concerned and where is the limit
So we are going to work on that issue and we will let you know as soon as possible its evolution
Matloub
Hi Larry,
can you please tell us the version numbers and installation dates available in the Help->About window from Ride7?
Thank you
Lionel
Ride7 IDE: 7.01.0002
RKitARM for RIDE7: 1.03.0004
Incidentally, the failure is of "C:\Program Files\Raisonance\Ride\Bin\rexrdr.exe" which is not strictly a compiler failure -- but you've probably figured that out.
I get a similar problem, but when linking and sometimes when compiling. It looks more like there is a timeout in RIDE which gives a Build Failed error if the compile or link being attempted does not complete in a certain time e.g with large source files or large links. I sometimes get a build failed when compiling, but if I do the build again immediately afterwards it builds OK. If it fails during the link it has created the binary, but not completed the dwf2xml, so I am unable to debug in RIDE.
Running : LD
\"C:\Program Files\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-gcc.exe" -mcpu=arm9tdmi -Wl,-T -Xlinker "C:\Sapphire_II\quartz.elf.ld" -u _start -Wl,-static -Wl,--gc-sections -nostartfiles -Wl,-Map -Xlinker "C:\Sapphire_II\quartz.map"
\"C:\Program Files\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-objcopy.exe" "C:\Sapphire_II\quartz.elf" --target=ihex "C:\Sapphire_II\quartz.hex"
\"C:\Program Files\Raisonance\Ride\Bin\rexrdr.exe" "C:\Sapphire_II\quartz.elf.sizetmp" 0 "C:\Program Files\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-size.exe" "C:\Sapphire_II\quartz.elf"
\"C:\Program Files\Raisonance\Ride\Bin\dwf2xml.exe" "C:\Sapphire_II\quartz.dbi" "C:\Sapphire_II\quartz-globals.Standard.xml" "C:\Sapphire_II\quartz.Standard.xml"
Build failed
Hi, Does anyone have a solution to this timeout problem yet? It is a severe headache for us, in particular one module is very hard to get it to compile.
Yes, I've also been coming to that conclusion.
Yes, that's exactly what I see.
It usually happens to me on the 1st build after opening a project - presumably, the next time stuff has been cached so it all works quickly enough to keep RIDE happy?
I'm not using large files at all!
It does seem that RIDE somehow "loses communication" with the actual compiler - presumably this "rexrdr.exe" is some sort of redirector that "pipes" the compiler output to RIDE...?
Hi 'awneil' my colleague has exactly the same symptoms that you do, but for some reason I just cannot get one of the modules to compile, unless I copy the project to my local drive, then its OK. All our project files are stored on a file server, which slows things down somewhat.
Cheers,
Bart
Hello everyone, and sorry for the late answer.
In a future version of RIDE, there will be a way for you to modify the length of the timeout independently for each tool. (GCC, AS, LD, etc.) We are working on it.
For now, I'm afraid the only option is for you to create Makefiles or batch files (or any other kind of script) that will run the command-lines in place of RIDE.
Anyways I suggest that you make sure that your RIDE7 and ARM kits are the latest versions, available for download on our website:
http://www.raisonance.com/download/
Best Regards,
Vincent
Thanks Vincent,
Any estimate on when the new release of RIDE may be ready?
Regards,
Bart
Hi,
We need to investigate the issue some more before we know how long we will need to solve it. Several developers are involved, so it will need time to get validated.
So we cannot commit on any date for this fix for now.
Best Regards,
Vincent