"Blinky.axf": not in executable format: File format not recognized

lpcware · ‎06-15-2016

Content originally posted in LPCWare by snowball on Tue Jan 14 20:35:37 MST 2014
New user; I have the LPC800 Xpresso dev board, I'm following the instructions in the LPCXpresso user guide.

I'm running LPCXpresso v6.1.2 [Build 177] [2013-11-28] on Mac OS X 10.9.1.

I imported all of the example projects, plugged in the dev board via USB, build and debug and I get:

Error in final launch sequence
  Failed to execute MI command:
-file-exec-and-symbols /Volumes/Work/LPCexpresso/Blinky/Debug/Blinky.axf
Error message from debugger back end:
"/Volumes/Work/LPCexpresso/Blinky/Debug/Blinky.axf": not in executable format: File format not recognized
  "/Volumes/Work/LPCexpresso/Blinky/Debug/Blinky.axf": not in executable format: File format not recognized

Any ideas?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Wed Jan 15 08:33:03 MST 2014
Debugging the Blinky example from the LPC812 code bundle works fine for me here (though I'm still running Mac OS 10.7.5 on this particular machine).

One thing I can see in your log though is that your workspace is at "/Volumes/Work/LPCexpresso/ ". Presumably this isn't your main drive? What actually is it, and how is it formatted? For example - is it "Mac OS Extended (Case sensitive)" maybe?

And where is the new workspace that you are using compared to the original?

Regards,
LPCXpresso Support.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by snowball on Wed Jan 15 08:23:50 MST 2014
Hmmm ... I quit LPCXpresso, removed the workspace, restarted LPCXpresso with a new workspace, reimported, rebuilt and it seemed to work this time around.

BTW: I did have an issue running Blinky as LPCXpresso would get timeouts waiting for the LPC-Link, but I found a Red Code support document that talked about Mac OS USB problems and it suggested trying a different USB port or connecting through a hub. I moved the LPCLink to one of the USB ports on my display (instead of the Mac) and it worked.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by snowball on Wed Jan 15 07:48:41 MST 2014
I haven't changed any build settings, this is a new install -- I followed the instructions from the LPCXpresso user guide.

I had already tried a "Clean 'Blinky'" followed by "Build 'Blinky'" (both for debug) but I still have the same problem. Here's the contents of the build console:

09:42:55 **** Build of configuration Debug for project Blinky ****
make all 
Building file: ../src/cr_startup_lpc8xx.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -DDEBUG -D__CODE_RED -D__USE_CMSIS=CMSIS_CORE_LPC8xx -D__LPC8XX__ -I"/Volumes/Work/LPCexpresso/lpc800_driver_lib" -I"/Volumes/Work/LPCexpresso/CMSIS_CORE_LPC8xx" -I"/Volumes/Work/LPCexpresso/CMSIS_CORE_LPC8xx/inc" -I"/Volumes/Work/LPCexpresso/lpc800_driver_lib/inc" -Os -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"src/cr_startup_lpc8xx.d" -MT"src/cr_startup_lpc8xx.d" -o "src/cr_startup_lpc8xx.o" "../src/cr_startup_lpc8xx.c"
Finished building: ../src/cr_startup_lpc8xx.c
 
Building file: ../src/crp.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -DDEBUG -D__CODE_RED -D__USE_CMSIS=CMSIS_CORE_LPC8xx -D__LPC8XX__ -I"/Volumes/Work/LPCexpresso/lpc800_driver_lib" -I"/Volumes/Work/LPCexpresso/CMSIS_CORE_LPC8xx" -I"/Volumes/Work/LPCexpresso/CMSIS_CORE_LPC8xx/inc" -I"/Volumes/Work/LPCexpresso/lpc800_driver_lib/inc" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"src/crp.d" -MT"src/crp.d" -o "src/crp.o" "../src/crp.c"
Finished building: ../src/crp.c
 
Building file: ../src/main.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__REDLIB__ -DDEBUG -D__CODE_RED -D__USE_CMSIS=CMSIS_CORE_LPC8xx -D__LPC8XX__ -I"/Volumes/Work/LPCexpresso/lpc800_driver_lib" -I"/Volumes/Work/LPCexpresso/CMSIS_CORE_LPC8xx" -I"/Volumes/Work/LPCexpresso/CMSIS_CORE_LPC8xx/inc" -I"/Volumes/Work/LPCexpresso/lpc800_driver_lib/inc" -O0 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -mcpu=cortex-m0 -mthumb -MMD -MP -MF"src/main.d" -MT"src/main.d" -o "src/main.o" "../src/main.c"
Finished building: ../src/main.c
 
Building target: Blinky.axf
Invoking: MCU Linker
arm-none-eabi-gcc -nostdlib -L"/Volumes/Work/LPCexpresso/CMSIS_CORE_LPC8xx/Debug" -L"/Volumes/Work/LPCexpresso/lpc800_driver_lib/Debug" -Xlinker -Map="Blinky.map" -Xlinker --gc-sections -mcpu=cortex-m0 -mthumb -T "Blinky_Debug.ld" -o "Blinky.axf"  ./src/cr_startup_lpc8xx.o ./src/crp.o ./src/main.o   -llpc800_driver_lib -lCMSIS_CORE_LPC8xx
Finished building target: Blinky.axf
 
make --no-print-directory post-build
Performing post-build steps
arm-none-eabi-size "Blinky.axf"; # arm-none-eabi-objcopy -O binary "Blinky.axf" "Blinky.bin" ; checksum -p LPC812 -d "Blinky.bin";
   text   data    bss    dec    hexfilename
   2544      4    132   2680    a78Blinky.axf
 

09:42:56 Build Finished (took 569ms)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Wed Jan 15 01:09:56 MST 2014
This implies that something has corrupted the executable (axf) file after it was built.

Did you change something in the build settings?

Suggest you clean the project and rebuild it, and if it still does no work, then Post the contents of the Build console here, so we can see if there are any build steps corrupting the file after it is created by the linker.