[riot-devel] RIOT vectors for Smartfusion2 port
AAsharaph at csir.co.za
Wed May 29 10:58:24 CEST 2019
The board is the sf2-starter-kit and the CPU is the m2s010, which contains a Cortex M3.
I have made a publicly accessible repo with all the code available at:
I see now that the makefile in makefiles/arch/cortexm.inc.mk has the code
# Explicitly tell the linker to link the startup code.
# Without this the interrupt vectors will not be linked correctly!
VECTORS_O ?= $(BINDIR)/cpu/vectors.o
export UNDEF += $(VECTORS_O)
and the Makefile.include in the m2s_xxx cpu folder has:
How should I go about removing that code and do I need to replace it with anything? Any help would be appreciated.
>>> Juan Ignacio Carrano <j.carrano at fu-berlin.de> 05/28/19 5:01 PM >>>
[The e-mail server of the sender could not be verified (SPF Record)]
I assume you are basing your SmartFusion port on some existing CPU. If
that's the case, it would be useful to know which one. Even better if
you can link us to a publicly accessible repo.
> I have tried including this file in the new cpu folder I
> created but get the following error when trying to make:
> arm-none-eabi-gcc: error:
> No such file or directory
The first question is why the build system is expecting to find
vectors.o. Not all CPUs generate that file (in your case you would
compile startup_m2sxxx.S into startup_m2sxxx.o) I believe the answer to
this question lies in the CPU you started with.
For example: you mention the LPC2387. If you compile any example with
BOARD=msba2 (which uses that cpu) and look inside "bin/msba2/cpu" you
will not find any vectors.o and that's OK.
> How do I use the above file correctly in the RIOT port? Is there some
> configuration that should be changed to use the file properly or should
> I convert it to a vectors.c file? If so, how do I go about doing so?
AFAIK you should not need to convert anything, just place the .S file in
your CPU directory, but without knowing the full contents of the dir it
is hard to tell what is happening.
devel mailing list
devel at riot-os.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel