Error Failed Execute Bin31 Armcc
30 Days In the Last 90 Days In the Last 6 Months Technical Support Overview Search Contact Assistance Request Feedback Support Resources Support Knowledgebase Article Index Top 10 Articles Product Manuals Application Notes Downloads Product Updates Discussion Forum Books Product Information Software & Hardware Products ARM Development ToolsC166 Development ToolsC51 Development ToolsC251 Development ToolsDebug AdaptersEvaluation Boards Product Brochures Newsletters Home/Technical Support AARM: CAN'T EXECUTE ARM ASSEMBLER Information in this article applies to: CARM All Versions QUESTION When I try to build a project I receive the following message: assembling Startup.s... --- Error: can't execute 'D:\ARM\ADSV1_2\BIN\ArmAsm' Target not created Don't the Keil tools come with an assembler? ANSWER Yes. An assembler is included with the Keil tools. However, from the error message, it appears that your project is configured to use the ARM ADS/RealView tools. If RealView is not installed, you will receive this message. Check your project Environment settings (Project — Components, Environment, Books — Select ARM Development Tools) to see if they are set to Use RealView Compiler. If so and if the ARM MDK-RealView toolkit is not installed, you will receive this message. Note that the ARM MDK-RealView tools are not included with Keil tools. To use the Keil tools, select the Use Keil Compiler checkbox. This directs µVision3 to use the included Keil ARM compiler. Last Reviewed: Thursday, January 18, 2007 Did this article provide the answer you needed? Yes No Not Sure Products Development Tools ARM C166 C51 C251 µVision IDE and Debugger Hardware & Collateral ULINK Debug Adaptors Evaluation Boards Product Brochures Device Database Distributors Downloads MDK-ARM C51 C166 C251 File downloads Support Knowledgebase Discussion Forum Product Manuals Application Notes Contact Distributors Request a Quote Sales Contacts Cookie Settings | Terms of
30 Days In the Last 90 Days In the Last 6 Months Technical Support Overview Search Contact Assistance Request Feedback Support Resources Support Knowledgebase Article Index Top 10 Articles Product Manuals Application Notes Downloads Product Updates Discussion Forum Books Product Information Software & Hardware Products ARM Development ToolsC166 Development ToolsC51 Development ToolsC251 Development ToolsDebug AdaptersEvaluation Boards Product Brochures Newsletters Home/Technical Support ARM: TARGET NOT CREATED - CAN'T EXECUTE MESSAGE Information in this article applies to: Keil Development Tools for ARM any Version QUESTION I am using Keil µVision3 for simulating an ARM processor. I have http://www.keil.com/support/docs/2868.htm included startup.s and one C file called main.c which is a simple test program without using any peripherals. But when I build the target for Philips LPC2104, I receive the following message: --- Error: Can't execute 'arm-uclibc-as' Target not created When I try to translate only the C source file, I receive the following message: --- Error: Can't execute 'arm-uclibc-gcc' What is the reason for this problem? ANSWER http://www.keil.com/support/docs/2942.htm µVision3 supports three different toolsets: Keil CARM, ARM ADS, and GNU. Based on the error messages you listed, it appears you have selected the GNU tools. The error indicates that the GNU tools are not installed. To use the Keil CARM Compiler, select Use Keil ARM Tools from the Project - Components, Environment and Books dialog and replace the GNU-specific STARTUP.S file with the Keil CARM version (available in the \KEIL\ARM\STARTUP\ folder ). To use the GNU toolset, you must install the GNU toolchain. It may be downloaded from www.keil.com/demo - Download the Keil ARM Evaluation Tools. MORE INFORMATION Getting Started User's Guide, Development Tools, Select the Toolset SEE ALSO ARM: STARTUP.S FILE TRANSLATES WITH MANY ERRORS CARM: CONVERTING PROGRAMS FROM GNU FORUM THREADS The following Discussion Forum threads may provide information related to this topic. Not able to use gcc in keil microvision 4 ragarding LPC2100_UARTIrq.zip compilation error Last Reviewed: Monday, October 17, 2005 Did this article provide the answer you needed? Yes No Not Sure Products Development Tools ARM C166 C51 C251 µVision IDE and Debugger Hardware & Collateral ULINK Debug Adaptors Evaluation Boards Product Brochures Device Database Distributors Downloads MDK-ARM C51 C166 C251 File download
last months will be deleted periodically to fight SPAM! Home Help Search Login Register Wiki Code::Blocks » User forums » General (but related http://forums.codeblocks.org/index.php?topic=11495.0 to Code::Blocks) » A bug in complier setting « previous next » Send this topic Print Pages: [1] Go Down Author Topic: A bug in complier setting (Read 3247 times) ilcvm Single posting newcomer Posts: 8 A bug in complier setting « on: November 11, 2009, 05:13:04 am » Hi, it seems there is a bug in Global complier settings error failed dialog.I want to use the ARM complier of the Realview MDK toolchain.So I type the "E:\Keil\ARM\BIN40" in the directory text box and "armcc.exe" in C complier text box in the "Toolchain executables" tag. But it fail when I try to complier. The fail msg is as belowarmcc.exe --device DARMST --diag_style=gnu -c E:\fcl\Source_Code\CB_MDK_test\main.c -o obj\Debug\main.oExecution of 'armcc.exe --device DARMST --diag_style=gnu error failed execute -c E:\Source_Code\CB_MDK_test\main.c -o obj\Debug\main.o' in 'E:\fcl\Source_Code\CB_MDK_test' failed.Nothing to be done.And if I add "E:\Keil\ARM\BIN40" in "Additional Paths", the building will succeed.This really confuse me.Thanks. Logged MortenMacFly Administrator Lives here! Posts: 9403 Re: A bug in complier setting « Reply #1 on: November 11, 2009, 06:31:54 am » Quote from: ilcvm on November 11, 2009, 05:13:04 amAnd if I add "E:\Keil\ARM\BIN40" in "Additional Paths", the building will succeed.This is correct. Look: What you have to provide in the toolchain path is the base path to the compiler. For GCC, its the top-level path with sub-folders called "bin" with the executables, "include" with headers, "lib" with libraries. C::B will try to search for the compiler in the sub-folder "bin". In your case I assume the folder structure is not standard GCC conform and the sub-folder with the executables is strangely called "BIN40" here. So that's what the additional path's selection was made: To add strangely non-conform sub-folders to the list of directories where C::B looks for the compiler.So everythig is right except that you have to change the base folder to "E:\Keil\A