Dear Juan and Hauke
Thank you for the suggestions.
To answer Juan's questions, I am not too sure about whether the vectors will
change or not. It is likely but I might have to get a better understanding to
know whether that is the case or not. The peripherals will definitely change
though,
Hi Ashim,
the LPC2387 is unfortunately a very bad example, as this CPU is not very
well maintained and does not comply with the best practices of structure
and style that newer CPUs in RIOT use.
The general approach for porting CPUs in RIOT is to rely as much as
possible on shared code.
Assim, Hauke,
To comment a bit on Hauke's suggestion.
On 29/5/19 08:47, Hauke Petersen wrote:
The general approach for porting CPUs in RIOT is to rely as much as
possible on shared code...
That's very important, try to take advantage of what's already in RIOT.
> . All the specific CPU
Dear Juan
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:
https://github.com/ashimasharaph/SmartFusion2_riot_port
I see now that the makefile in makefiles/arch/cortexm.inc.mk has
Dear RIOT Developers
I am currently working on a port for RIOT to the Microsemi SmartFusion2 board
which has a Cortex M3. I see that most of the CPUs have a vectors.c file which
specify all the interrupt vectors. Some of the other boards have an assembly
file for startup such as the lpc2387
