This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Startup files - porting builds between SES and GCC

Sorry in advance if this is an FAQ or maybe two

Situation is this - for regulatory reasons, production/release software here is built using a known version of arm-gcc, and has been built on SDK14.2 up to now.

I need to start a new project - (re-using some previous source), but ported to SDK15.3  IMHO The SES IDE is very helpful during code development, so I want to use it, but I will be forced to export back to GCC "make" for testing and pre-production. (PITA.)

I know I am conflating two issues here (update the SDK, and port between build environments), but I don't believe SES was supported until SDK15 anyway.

So - here's the problem, the SES "new project" wizard, and the SES examples in SDK15.3 have very different startup, linker and system files than the GCC production makefiles that I already have. 

Now - the peripheral examples in SDK15.3 seem to be configured to use the gcc compiler but don't use the gcc_startup_nrf52.s etc. files.

Is there perhaps an idiot's guide to the files in the IAR/GCC/ARM, and SES options in nrfx/mdk?  Compare and contrast? "An SES build will use x,y and z, but a GCC make project will need A and B instead)

Thanks for any/all advice.

Parents Reply Children
Related