I'm strugling far too long now, with setting up the new Xscope functionality on a XC-2.
I have a XTAG-2 connected to it (just desoldered the small smd fuse) which works fine (and fast! :) for running, debugging and flashing.
Now I want to make use of the X0LA link, which appears to be wired on the XC-2 to its XSYS connector as it sould, when one wants to use it with the new XScope feature. Right?
I followed chapter 7 in the current xmos tools user guide closely. But I need to use makefile-based building, since I don't know how I would include all the makefile-based modules like "module_ethernet" etc. if I'd be using the XDE's internal build method.
So I added -lxscope to my makefile for linking in the xscope library:
Code: Select all
TARGET = XC-2
BASE_DIR = .
APP_NAME =
LOCAL_DIRS = folder1 folder2
SOURCE_DIRS += $(LOCAL_DIRS)
INCLUDE_DIRS += $(LOCAL_DIRS)
USED_MODULES = module_ethernet.1v3 module_xfifo.1v0
#XCC_FLAGS += -save-temps -g -report
#XCC_FLAGS += -save-temps -report
XCC_MAP_FLAGS += -lxscope
include $(lastword $(sort $(wildcard ../module_xmos_common.1v3)))/build/Makefile.common
all: $(BIN_DIR)/$(APP_NAME).xe
@echo Build Complete
clean: clean_common
Code: Select all
<Links>
<Link Encoding="2wire" Delays="4,4" Flags="SOD">
<LinkEndpoint NodeId="0" Link="X0LA" />
<LinkEndpoint RoutingId="0x8000" Chanend="1" />
</Link>
</Links>
after compiling, I still get this error, as if the neccessary XN file config is still missing:
Code: Select all
ccXQnm40.s: Error: Undefined reference to '__sodEnd' (using xscope but XN does not specify a suitable link?)
ccXQnm40.s: Error: Undefined reference to '__sodFlag' (using xscope but XN does not specify a suitable link?)
(Note: I need the "../" here, alltough the Makefile and the XC-2.xn file are both in the same, topmost project directory. Strange...)
Code: Select all
XCC_MAP_FLAGS += -lxscope --target-file ../XC-2.xn
Code: Select all
xcc: error: both target and xn source file supplied
I also messed around with XCC_DEVICE_PATH and the XCC_FLAGS "-target=" option, which didn't help either...
Any suggestions?
I slowly get the feeling, that there's maybe a little bit too much black magic involved with handling the .XN files behind the scenes...