The problem I have is that I am unable to place a breakpoint in any of the C files in the project. To be more specific, I can add a breakpoint in a C file while in the edit perspective. However, once I click on the Debug button and switch over to the debug perspective, I get the yellow triangle with an exclamation mark telling me that it is an unresolved breakpoint. The same thing happens if I try to add a breakpoint to a C file while debugging is currently taking place too.
I can place breakpoints in any xc file and those will get resolved by the debugger. I can also step into the C library after breaking on the caller that resides in an xc file. However, there are times I would like to break on a very specific location that are a few levels deep and having to always step into the location of interest at such a high level is cumbersome. The fact that I can eventually step into the C library gives me a clue that debugging info for the C modules are being created, but the debugger perspective does not resolve it for some reason.
Below is my MakeFile. You'll notice that it is basically the same one that is provided with the example except that I've stripped out sections that do not apply to my board and I have removed optimization and added "-g" to produce the debugging info.
Code: Select all
# The TARGET variable determines what target system the application is
# compiled for. It either refers to an XN file in the source directories
# or a valid argument for the --target option when compiling.
# In this case, the target depends on the build configuration.
TARGET = XUE216-512-TQ128-C20
# The APP_NAME variable determines the name of the final .xe file. It should
# not include the .xe postfix. If left blank the name will default to
# the project name
APP_NAME = app_test_and_measurement
# The flags passed to xcc when building the application
# You can also set the following to override flags for a particular language:
#
# XCC_XC_FLAGS, XCC_C_FLAGS, XCC_ASM_FLAGS, XCC_CPP_FLAGS
#
# If the variable XCC_MAP_FLAGS is set it overrides the flags passed to
# xcc for the final link (mapping) stage.
# These flags define two build configurations - one for U-series and one for
# the xCORE-200 series.
XCC_FLAGS_X200 = -Wall -g -report -DXUD_SERIES_SUPPORT=XUD_X200_SERIES
VERBOSE = 1
# The USED_MODULES variable lists other module used by the application.
USED_MODULES = lib_gpio lib_logging lib_usb lib_xassert
#=============================================================================
# The following part of the Makefile includes the common build infrastructure
# for compiling XMOS applications. You should not need to edit below here.
XMOS_MAKE_PATH ?= ../..
include $(XMOS_MAKE_PATH)/xcommon/module_xcommon/build/Makefile.common
Thanks!!