Hi Team,
We are using AM263x_09_00_01_00.
When compiled, Dio_Priv.c throws compilation error as follows.
for the Dio_GPIOPortAddr array definition STATIC is unknown type.
.
Could you please look into this?
Hi Aswathy,
Are you compiling the MCAL example in CCS or via makefiles?
If you use makefile, please go through the description in readme.txt
Steps to build
==============
- Open Rules.make
- Edit paths for the below variables according to your system environment
In case of windows machine edit below paths,
TOOLCHAIN_PATH_R5 := $(abspath ../../../..)/Compilers/ti-cgt-armllvm_1.3.0.LTS
mcal_PATH := $(abspath ..)/$(mcal_RELPATH)
mcal_demo_PATH := $(abspath ..)/$(mcal_demo_RELPATH)
UTILS_INSTALL_DIR := $(abspath ../../../..)/ccs1210/ccs/utils/cygwin
GMAKE_DIR := $(abspath ../../../..)/ccs1210/ccs/utils/cygwin
By default the above are for CLANG compiler, modify respective paths accordingly for using other compilers.
In case of linux machine edit the similar linux path
IMPORTANT:
Make sure the paths specified above DO NOT have any spaces in them.
- Make sure "gmake" is in your system path.
Typically when XDC is installed "gmake" is installed along with it and
it becomes part of the system path by default.
========================= How to Build =========================================
- Open command prompt and go to $MCAL_INSTALL_DIR/build directory and type below
gmake -s all
This will and build all MCAL drivers as well as all MCAL
examples
gmake -s allclean
This will clean all MCAL drivers as well as all MCAL
examples
- TIP: Always use "-s" option with make to see user friendly prints
during build.
- Optionally before build, edit the below in Rules.make file,
depending on the kind of build you want to do:
PLATFORM:=am263
PROFILE:=release/debug
Valid values for PLATFORM are:
am263 - AM263
Valid values for PROFILE are:
debug - Debug build with NO compiler optimizations
and symbolic debug info included
release - Release build with FULL compiler optimizations
and symbolic debug info included
- The generated files are placed in the below folders,
Executables - $(DEST_ROOT)/<APP_NAME>/bin/$(PLATFORM)/<APP_NAME>_<CORE>_$(PROFILE).xer5f
Libraries - $(DEST_ROOT)/<MODULE_RELPATH>/lib/$(PLATFORM)/r5f/$(PROFILE)/*.aer5f
Objects - $(DEST_ROOT)/<MODULE_RELPATH>/obj/$(PLATFORM)/r5f/$(PROFILE)/*.oer5f
Dependancies - $(DEST_ROOT)/<APP_NAME>/obj/$(PLATFORM)/r5f/$(PROFILE)/.deps/*.P
- During development the below "gmake" targets can be also used be used for
convenience:
gmake -s examples - incrementally builds MCAL drivers
and all examples
gmake -s platforms - incrementally builds for all supported PLATFORMs
gmake -s profiles - incrementally builds for all supported PROFILEs
gmake -s all - clean all and build all drivers, examples for default platform <am263>
gmake -s allall - incrementally builds for all supported PLATFORMs
AND PROFILEs
gmake -s clean - clean all drivers, examples
gmake -s examples_clean - clean all examples ONLY
gmake -s platformsclean - cleans for all supported PLATFORMs
gmake -s profilesclean - cleans for all supported PROFILEs
gmake -s allclean - cleans for all supported PLATFORMs AND PROFILEs
gmake -s <examplename> - incrementally builds MCAL drivers
and the specific example ONLY.
Values for <examplename> can be,
adc_app
can_app
dio_app
eth_app
fls_app
gpt_app
i2c_app
icu_app
ipc_notify_app
ipc_rpmsg_app
mcspi_app
mcu_app
port_app
pwm_app
uart_echo_dma_app
wdg_app
gmake -s help - Prints the help menu
I just built DIO app example, there is no problem:
I also built all the MCAL drivers, didn't see any issue:
gmake -s all
