AM3352 CCS SYS/BIOS example hello does not compile and link

Additional note: I installed the latest XDC and tools now... Deleted the project and retried with similar results.

**** 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_02_70/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.M3 -p ti.platforms.stellaris:AM3352 -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.xem3 from package/cfg/hello_pem3.cfg ...
The AM3352 device is not currently supported.
The following devices are supported in the ti.catalog.arm.cortexm4 catalog:
LM4F110B2QR LM4F110C4QR LM4F110E5QR LM4F110H5QR LM4F110T9QR
LM4F111B2QR LM4F111C4QR LM4F111E5QR LM4F111H5QR LM4F111T9QR
LM4F112C4QC LM4F112E5QC LM4F112H5QC LM4F112H5QD LM4F112T9QC
LM4F112T9QD LM4F114T9QC LM4F114T9QD LM4F11AT9QR LM4F11BT9QR
LM4F11CT9QC LM4F11CT9QD LM4F120B2QR LM4F120C4QR LM4F120E5QR
LM4F120H5QR LM4F121B2QR LM4F121C4QR LM4F121E5QR LM4F121H5QR
LM4F122C4QC LM4F122E5QC LM4F122H5QC LM4F122H5QD LM4F130C4QR
LM4F130E5QR LM4F130H5QR LM4F130T9QR LM4F131C4QR LM4F131E5QR
LM4F131H5QR LM4F131T9QR LM4F132C4QC LM4F132E5QC LM4F132H5QC
LM4F132H5QD LM4F132T9QC LM4F132T9QD LM4F134T9QC LM4F134T9QD
LM4F13AT9QR LM4F13BT9QR LM4F13CT9QC LM4F13CT9QD LM4F191T9QR
LM4F194T9QC LM4F194T9QD LM4F210B2QR LM4F210C4QR LM4F211B2QR
LM4F211C4QR LM4F212C4QC LM4F230E5QR LM4F230H5QR LM4F230T9QR
LM4F231E5QR LM4F231H5QR LM4F231T9QR LM4F232E5QC LM4F232H5BB
LM4F232H5QC LM4F232H5QD LM4F232T9QC LM4F232T9QD LM4F234T9QC
LM4F234T9QD LM4F23BT9QR LM4F23CT9QC LM4F23CT9QD LM4F290P9PDT
LM4F290P9ZAD LM4F291T9QR LM4F292P9PDT LM4F292P9ZAD LM4F294P9PDT
LM4F294P9ZAD LM4F294T9QC LM4F294T9QD LM4F29BT9QR LM4F29CP9PDT
LM4F29CP9ZAD LM4F29CT9QC LM4F29CT9QD LM4F29DP9PDT LM4F29DP9ZAD
LM4F29EP9PDT LM4F29EP9ZAD LM4FB15P9ZAD LM4FS01P9ZAD LM4FS11H5BB
LM4FS19H5BB LM4FS1AH5BB LM4FS1BH5BB LM4FS1GE5BB LM4FS1GH5BB
LM4FS1PE5QK LM4FS1PH5QK LM4FS200MPDT LM4FS200MZRB LM4FS210MPDT
LM4FS210MZRB LM4FS230MPDT LM4FS230MZRB LM4FS250MPDT LM4FS250MZRB
LM4FS270MPDT LM4FS270MZRB LM4FS2H0MPDT LM4FS2H0MZRB LM4FS2J0MPDT
LM4FS2J0MZRB LM4FS2K0MPDT LM4FS2K0MZRB LM4FS99H5BB LM4FS99H5QD
LM4FSXHH5BB LM4FSXLH5BB OMAP5430 SC01120E5QR SC01230H5QR
SC01231H5QR SC01232H5BB SC01232H5QC TM4C1230C3PMI TM4C1230D5PMI
TM4C1230E6PMI TM4C1230H6PMI TM4C1231C3PMI TM4C1231D5PMI TM4C1231D5PZI
TM4C1231E6PMI TM4C1231E6PZI TM4C1231H6PGEI TM4C1231H6PMI TM4C1231H6PZI
TM4C1232C3PMI TM4C1232D5PMI TM4C1232E6PMI TM4C1232H6PMI TM4C1233C3PMI
TM4C1233D5PMI TM4C1233D5PZI TM4C1233E6PMI TM4C1233E6PZI TM4C1233H6PGEI
TM4C1233H6PMI TM4C1233H6PZI TM4C1236D5PMI TM4C1236E6PMI TM4C1236H6PMI
TM4C1237D5PMI TM4C1237D5PZI TM4C1237E6PMI TM4C1237E6PZI TM4C1237H6PGEI
TM4C1237H6PMI TM4C1237H6PZI TM4C123AE6PMI TM4C123AH6PMI TM4C123BE6PMI
TM4C123BE6PZI TM4C123BH6PGEI TM4C123BH6PMI TM4C123BH6PZI TM4C123BH6ZRBI
TM4C123FE6PMI TM4C123FH6PMI TM4C123GE6PMI TM4C123GE6PZI TM4C123GH6PGEI
TM4C123GH6PMI TM4C123GH6PZI TM4C123GH6ZRBI TM4C1290NCPDT TM4C1290NCZAD
TM4C1292NCPDT TM4C1292NCZAD TM4C1294NCPDT TM4C1294NCZAD TM4C129CNCPDT
TM4C129CNCZAD TM4C129DNCPDT TM4C129DNCZAD TM4C129ENCPDT TM4C129ENCZAD
TM4E1231H6ZRB TM4E1237H6ZRB TM4E123GH6ZRB TM4E129BNCZAD TM4E129SNCZAD
Vayu
js: "C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/arm/Settings.xs", line 458: Error: Unsupported device!
"C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/arm/Settings.xs", line 552
"C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/Settings.xs", line 209
"C:/ti/bios_6_35_01_29/packages/ti/sysbios/family/Settings.xs", line 121
"C:/Users/aaron/workspace_v5_4/rtoshello/hello.cfg", line 12
"./package/cfg/hello_pem3.cfg", line 180
gmake.exe: *** [package/cfg/hello_pem3.xdl] Error 1
js: "C:/ti/xdctools_3_25_02_70/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake: Target `all' not remade because of errors.

**** Build Finished ****

Hi Aaron,

the AM3352 is a cortex A8 not am m3.    Can you please explain the steps you are taking?   Can you send/explain your target configuration.

Best Regards,
Lisa 

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

Hi Aaron,

I would not worry about this.  All of these am3x parts are closely enough related you should be able to use that platform etc.  In fact all it means is the BIOS team has not provided on for your variant, however, you can use that one or creat one if you are ambitious.

So I hope this helps clarify and glad you have your code building and the settings are now much better.

Best Regards,

Lisa

That gets me through step one...

Now I want use the functionality in hsi2c.h so, I created another test app the code compiles but does not link. What is recommended library or settings should I use and how should I point the tools to find the library.

I want SYS/BIOS functionality plus the AM335x drivers (I2C, SPI, GPIO, UART, and eventually the LW IPStack)

Thanks,

Aaron

**** Build of configuration Debug for project simple ****

"C:\\ti\\ccsv5\\utils\\bin\\gmake" -k all
making ../src/sysbios.aea8fnv ...
gmake[1]: Nothing to be done for `all'.
'Building file: ../main.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" --include_path="C:/ti/AM335X_StarterWare_02_00_01_01/platform/evmAM335x" --include_path="C:/ti/am335x_sysbios_ind_sdk_1.1.0.1/sdk/starterware/include/hw" --include_path="C:/ti/am335x_sysbios_ind_sdk_1.1.0.1/sdk/starterware/include/armv7a/am335x" --include_path="C:/ti/am335x_sysbios_ind_sdk_1.1.0.1/sdk/starterware/include" --define=am3352 --diag_warning=225 --display_error_number --diag_wrap=off --preproc_with_compile --preproc_dependency="main.pp" --cmd_file="./configPkg/compiler.opt" "../main.c"
"../main.c", line 287: warning #179-D: variable "configData" was declared but never referenced
"../main.c", line 288: warning #179-D: variable "ptrReg" was declared but never referenced
"../main.c", line 265: warning #179-D: function "I2CRegRead" was declared but never referenced
'Finished building: ../main.c'
' '
'Building target: simple.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 --diag_warning=225 --display_error_number --diag_wrap=off -z --stack_size=0x800 -m"simple.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="simple_linkInfo.xml" --rom_model -o "simple.out" -l"./configPkg/linker.cmd" "./main.obj" -l"libc.a"
<Linking>

undefined first referenced
symbol in file
--------- ----------------
I2C1ModuleClkConfig ./main.obj
I2CAutoIdleDisable ./main.obj
I2CDataCountGet ./main.obj
I2CMasterControl ./main.obj
I2CMasterDataGet ./main.obj
I2CMasterDataPut ./main.obj
I2CMasterDisable ./main.obj
I2CMasterEnable ./main.obj
I2CMasterInitExpClk ./main.obj
I2CMasterIntClearEx ./main.obj
I2CMasterIntDisableEx ./main.obj
I2CMasterIntEnableEx ./main.obj
I2CMasterIntRawStatus ./main.obj
I2CMasterIntStatus ./main.obj
I2CMasterSlaveAddrSet ./main.obj
I2CMasterStart ./main.obj
I2CMasterStop ./main.obj
I2CPinMuxSetup ./main.obj
I2CSetDataCount ./main.obj
IntAINTCInit ./main.obj
IntMasterIRQEnable ./main.obj
IntPrioritySet ./main.obj
IntRegister ./main.obj
IntSystemEnable ./main.obj

error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "simple.out" not built

>> Compilation failure
gmake: *** [simple.out] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

Hi Aaron,

you are likely missing a library however the device forum is best to answer this so I am going to move this there for you.

Best Regards,

Lisa

Since I did not hear from anyone yet I tried an experiment...

I copied... 

am335x_indcomm_i2c.c from C:\ti\am335x_sysbios_ind_sdk_1.1.0.1\sdk\platform\am335x\src
am335x_indcomm_i2c.h from C:\ti\am335x_sysbios_ind_sdk_1.1.0.1\sdk\platform\am335x\include
am335x_indcomm_startup.h from C:\ti\am335x_sysbios_ind_sdk_1.1.0.1\sdk\platform\am335x\include
hsi2c.c from C:\ti\am335x_sysbios_ind_sdk_1.1.0.1\sdk\starterware\drivers
hsi2c.h from C:\ti\am335x_sysbios_ind_sdk_1.1.0.1\sdk\starterware\include

The issues included that am335x_indcomm_i2c.c uses APIs that are not defined in hsi2c.c and also seems to not play with the one located in C:\ti\am335x_sysbios_ind_sdk_1.1.0.1\sdk\starterware\platform\evmAM335x.  

It looked like the APIs in am335x_indcomm_i2c.c were the ones we are expected to call.

I expect this is not the method and/or API I am supposed to use for these drivers.

Aaron