Quantcast
Channel: Tools
Viewing all articles
Browse latest Browse all 91752

Forum Post: RE: AM3352 CCS SYS/BIOS example hello does not compile and link

$
0
0

I tried reinstalling CCS (I downloaded and installed CCS5.4.0.00091_win32.zip and did a complete install). I installed nothing else from TI yet. I deleted the project and started over.

Our board is going to be using and AM3352 so, this is the selections I made.

I want to eventually to use SYS/BIOS (and the NDK) and started the with Hello World SYS/BIOS example to make sure I have everything installed and configured properly. 

This was the build result… Which seemed to have build successfully. Despite the platform not matching and being a AM3359 (I don't have a AM3352 choice, why?).

 

 

**** Build of configuration Debug for project rtoshello ****

 

"C:\\ti\\ccsv5\\utils\\bin\\gmake" -k all

'Building file: ../hello.cfg'

'Invoking: XDCtools'

"C:/ti/xdctools_3_25_00_48/xs" --xdcpath="C:/ti/bios_6_35_01_29/packages;C:/ti/ccsv5/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.A8Fnv -p ti.platforms.evmAM3359 -r release -c "C:/ti/ccsv5/tools/compiler/arm_5.0.4" --compileOptions "-g --optimize_with_debug" "../hello.cfg"

making package.mak (because of package.bld) ...

generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...

configuring hello.xea8fnv from package/cfg/hello_pea8fnv.cfg ...

generating custom ti.sysbios library makefile ...

Starting build of library sources ...

making C:/Users/aaron/workspace_v5_4/rtoshello/src/sysbios.aea8fnv ...

clea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/BIOS.c ...

asmea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/arm/IntrinsicsSupport_asm.asm ...

asmea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/arm/TaskSupport_asm.asm ...

asmea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/arm/exc/Exception_asm.asm ...

asmea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/arm/a8/TimestampProvider_asm.asm ...

asmea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/arm/a8/Mmu_asm.asm ...

asmea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/arm/a8/Cache_asm.asm ...

asmea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/arm/a8/intcps/Hwi_asm.s470 ...

asmea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/arm/a8/intcps/Hwi_asm_switch.s470 ...

asmea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/timers/gptimer/Timer_asm.s470 ...

asmea8fnv C:/ti/bios_6_35_01_29/packages/ti/sysbios/timers/dmtimer/Timer_asm.s470 ...

area8fnv BIOS.obj arm_IntrinsicsSupport_asm.obj arm_TaskSupport_asm.obj exc_Exception_asm.obj a8_TimestampProvider_asm.obj a8_Mmu_asm.obj a8_Cache_asm.obj intcps_Hwi_asm.obj intcps_Hwi_asm_switch.obj gptimer_Timer_asm.obj dmtimer_Timer_asm.obj ...

Build of libraries done.

clea8fnv package/cfg/hello_pea8fnv.c ...

'Finished building: ../hello.cfg'

' '

        1 file(s) copied.

making ../src/sysbios.aea8fnv ...

gmake[1]: Nothing to be done for `all'.

'Building file: ../hello.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv5/tools/compiler/arm_5.0.4/bin/armcl" -mv7A8 --code_state=32 --abi=eabi -me -g --include_path="C:/ti/ccsv5/tools/compiler/arm_5.0.4/include" --define=am3352 --define=omap3503 --define=am3354 --diag_warning=225 --display_error_number --diag_wrap=off --preproc_with_compile --preproc_dependency="hello.pp" --cmd_file="./configPkg/compiler.opt"  "../hello.c"

'Finished building: ../hello.c'

' '

'Building target: rtoshello.out'

'Invoking: ARM Linker'

"C:/ti/ccsv5/tools/compiler/arm_5.0.4/bin/armcl" -mv7A8 --code_state=32 --abi=eabi -me -g --define=am3352 --define=omap3503 --define=am3354 --diag_warning=225 --display_error_number --diag_wrap=off -z --stack_size=0x800 -m"rtoshello.map" --heap_size=0x800 -i"C:/ti/ccsv5/tools/compiler/arm_5.0.4/lib" -i"C:/ti/ccsv5/tools/compiler/arm_5.0.4/include" --reread_libs --warn_sections --display_error_number --diag_wrap=off --xml_link_info="rtoshello_linkInfo.xml" --rom_model -o "rtoshello.out" -l"./configPkg/linker.cmd"  "./hello.obj" -l"libc.a"

<Linking>

'Finished building target: rtoshello.out'

' '

 

**** Build Finished ****

 Why do I see AM3354s in there as well?

Given these results is this the recommended way to configure the setup. For our own custom AM3552 board, I can create a xyz.cmd linker file and lay out the address map. Is there recommend way of doing this? 

 

Thanks,

Aaron

 


Viewing all articles
Browse latest Browse all 91752

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>