Anonymous
Not applicable
Jun 27, 2013
04:32 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 27, 2013
04:32 PM
Hardware = BCM920732 tagHost = Linux (ubuntu 13.04) x86_64Toolchain = CodeSourcery arm-none-eabi 2013.05gcc version 4.7.3 (Sourcery CodeBench Lite 2013.05-23) Compiling the sample program bleprox that came as part of the ADK I get a error that gcc does not recognize -falign-arrays. I had to compile w/o using that option.1. Are there any problem w/ not using -falign-arrays2. The app note says use the latest GCC version from CodeSourcery. What is the verison of gcc that is recommended? Is 4.7.3 ok? ThanksSrini-----------------make BLD=A_20732A0 BASE_IN=rom SPAR_IN=ram DIR=brcm/bleprox GCC_TOOL_DIR=/usr/share/enimai/arm-2013.05/bin/ TC=gcc clean cgs/usr/share/enimai/arm-2013.05/bin/arm-none-eabi-gcc -DBCM20732 -DBB_20732A0 -DGPIO_NUMBER_OF_PINS=40 -DGPIO_MAX_PINS_PER_PORT=16 -DGPIO_NUMBER_OF_PORTS=3 -DBLE_LRK_LIST_SIZE=4 -DBLEAPP -funsigned-char -falign-arrays -c -DCOMPILER_ARM -mlittle-endian -mcpu=cortex-m3 -mthumb -Os -g -Wa,-adhln -ffreestanding -DSPAR_CRT_SETUP=bleprox_spar_crt_setup -DSPAR_APP_SETUP=bleprox_spar_app_setup -D__TARGET_CPU_CORTEX_M3 -D__ARMCC_VERSION=220438 -ffunction-sections -Ibrcm/bleprox -I. -I../inc -I../cfa -I../bsp/inc -I../bleapp -I../bleapp/app -I../bleapp/drivers -I../bleapp/utils -I../misc -I../rtos/threadx -I../rtos/threadx/cm3 -I../bleapp/lestack/att -I../bleapp/lestack/l2cap -I../bleapp/lestack/blecm -I../bleapp/lestack/gatt -I../bleapp/lestack/profile -I../bleapp/lestack/smp -I../bleapp/lestack/ap -I. -Icommon -Ibrcm/bleprox -I../tier2/brcm/bleprox/bld/A_20732A0/.. -I../tier2/patch/inc -o brcm/bleprox/obj-A_20732A0-rom-ram/spar_setup.o common/spar_setup.c > brcm/bleprox/obj-A_20732A0-rom-ram/spar_setup.sarm-none-eabi-gcc: error: unrecognized command line option -falign-arraysmake: *** [brcm/bleprox/obj-A_20732A0-rom-ram/spar_setup.o] Error 1
Solved! Go to Solution.
- Tags:
- -adhln
- 4.7.3
- [brcmbleproxobj-a_20732a0-rom-ramspar_setup.o]
- arm-none-eabi-gcc
- bleapp
- bleappapp
- bleappdrivers
- bleapplestackap
- bleapplestackgatt
- bleapplestackprofile
- bleapplestacksmp
- brcmbleproxobj-a_20732a0-rom-ramspar_setup.o
- brcmbleproxobj-a_20732a0-rom-ramspar_setup.s
- bspinc
- clean
- codesourcery
- command
- commonspar_setup.c
- d__armcc_version=220438
- d__target_cpu_cortex_m3
- dbb_20732a0
- dbcm20732
- dble_lrk_list_size=4
- dbleapp
- dcompiler_arm
- dgpio_max_pins_per_port=16
- dgpio_number_of_pins=40
- dgpio_number_of_ports=3
- dspar_app_setup=bleprox_spar_app_setup
- dspar_crt_setup=bleprox_spar_crt_setup
- error
- falign-arrays
- ffreestanding
- funsigned-char
- gcc_tool_dir=usrshareenimaiarm-2013.05bin
- ibrcmbleprox
- icommon
- inc
- line
- make
- mcpu=cortex-m3
- mlittle-endian
- mthumb
- option
- tc=gcc
- tier2brcmbleproxblda_20732a0
- tier2patchinc
- unrecognized
- usrshareenimaiarm-2013.05binarm-none-eabi-gcc
- version
- wa
1 Solution
Jul 25, 2013
09:50 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jul 25, 2013
09:50 AM
This is a valid option with CodeSourcery G++ Lite version 2011.03-42. So you have two options, use this version of CodeSourcery or edit <adk>/spar/makecm3_gcc.inc and remove the -falign-arrays option from C_SPECIFIC_FLAGS. This will not affect the way the application gets built. The next version of the SDK will have a fix for this issue.
2 Replies
Anonymous
Not applicable
Jul 24, 2013
07:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jul 24, 2013
07:47 AM
any ideas on this? we see the same error. thanks.
Jul 25, 2013
09:50 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jul 25, 2013
09:50 AM
This is a valid option with CodeSourcery G++ Lite version 2011.03-42. So you have two options, use this version of CodeSourcery or edit <adk>/spar/makecm3_gcc.inc and remove the -falign-arrays option from C_SPECIFIC_FLAGS. This will not affect the way the application gets built. The next version of the SDK will have a fix for this issue.