How to get the reference of the SoC library API?

RE: How to get the reference of the SoC library API?

Hamza — Fri, 01 Sep 2017 13:59:44 GMT

Ok, the problem has been solved, I've installed the wrong version. 5.4 works fine. Thanks for you answers.

RE: How to get the reference of the SoC library API?

Torsten Robitzki — Fri, 01 Sep 2017 12:51:17 GMT

I think you should better focus on the actual linker error messages: Why are there unresolved external symbosl to a function that is created by a macro as static function. Installing different compilers and SDKs is just poking around. Have you had a look at the preprocessor output? Any chance that the SVCALL_AS_NORMAL_FUNCTION macro is defined?

RE: How to get the reference of the SoC library API?

Nguyen Hoan Hoang — Fri, 01 Sep 2017 12:40:46 GMT

Most of the time Nordic makefile doesn't work out of the box, if not to say never worked. What I do is create Eclipse project and import require source files. It is tedious to set all the include path at first but after that it would be a lot easier to maintain and you can debug too. I can compile all Nordic example with this. Have a look at this blog for more info.

RE: How to get the reference of the SoC library API?

endnode — Fri, 01 Sep 2017 12:32:05 GMT

So let's do step back: are you able to compile ANY example from that SDK with Makefile and GCC? If not then debugging stock examples will be much easier, everyone (mainly Nordic support team) can do the same and compare the outputs with you...

RE: How to get the reference of the SoC library API?

Hamza — Fri, 01 Sep 2017 12:28:51 GMT

Ok, I've just installed 5.4 and tried, same compile errors....

RE: How to get the reference of the SoC library API?

Nguyen Hoan Hoang — Fri, 01 Sep 2017 11:39:56 GMT

I did tried v6 a few months back. Had a lot of compile error and runtime issue. I didn't have time to look at it so I went back to 5.4. Don't know if it has been improved with 6.3 or not. For sure 5.4 work so may be you can try that first.

RE: How to get the reference of the SoC library API?

Hamza — Fri, 01 Sep 2017 11:25:49 GMT

I tried using anterior version, but it didn't solve anything

RE: How to get the reference of the SoC library API?

Hamza — Fri, 01 Sep 2017 09:34:49 GMT

I've tried to compile using extern "C" {}, the compiler didn'nt like. and I made the compiler with the -std=c99 option. Yes the same

RE: How to get the reference of the SoC library API?

Torsten Robitzki — Fri, 01 Sep 2017 09:31:15 GMT

Did you compiled the SDK sources with the very same compiler?

RE: How to get the reference of the SoC library API?

Torsten Robitzki — Fri, 01 Sep 2017 09:27:47 GMT

Are you sure, that your compiler thinks so too? But you are right, at least the sources that are missing the external symbols are within the SDK and thus should be pure C. Maybe you can check your Compiler switches and see if C is really used.

RE: How to get the reference of the SoC library API?

endnode — Fri, 01 Sep 2017 09:24:18 GMT

Also note that if from whatever reason you need to use so old SDK version you should read release notes and stick to compiler version tested by Nordic during release which is GCC: gcc-arm-embedded 4.9 2015q1. That might solve some of your issues as well.

RE: How to get the reference of the SoC library API?

Hamza — Fri, 01 Sep 2017 09:22:53 GMT

We are not using C++, only C code.

RE: How to get the reference of the SoC library API?

Torsten Robitzki — Fri, 01 Sep 2017 09:11:17 GMT

The functions you are missing are created by some macro magic in the headers of the SDK. The functions must be declared somewhere, or otherwise, your compiler would have complained already. My best guess is, that you are mixing C++ with C and that the old SDK version is not aware of C++ and thus you have to wrap the include of the SDK headers with an extern "C" {} to tell the compiler that the SDK functions have C binding.

RE: How to get the reference of the SoC library API?

Hamza — Fri, 01 Sep 2017 09:07:03 GMT

SVCALL(SD_FLASH_WRITE, uint32_t, sd_flash_write(uint32_t * const p_dst, uint32_t const * const p_src, uint32_t size)); Indeed, but I think the compiler can't find the code of the function sd_flash_write(uint32_t * const p_dst, uint32_t const * const p_src, uint32_t size)

RE: How to get the reference of the SoC library API?

endnode — Fri, 01 Sep 2017 09:02:31 GMT

Well you find them in a second if you simply do full-text search on entire nRF51 SDk V8.1.0 package: components\softdevice\s110\headers\nrf_soc.h. Anything else?

RE: How to get the reference of the SoC library API?

Hamza — Fri, 01 Sep 2017 08:46:29 GMT

Yes, I'm using the same sdk, and all the paths are set in the Makefile. Acctually I got undefined references from functions of the sdk, I included the ones I needed in the Makefile source variable, the errors have gone, there is only this one. It couldn't found the sd_flash_xxx functions defintion.

RE: How to get the reference of the SoC library API?

endnode — Fri, 01 Sep 2017 08:38:24 GMT

It seems to be missing some references to SoftDevice API, are you sure you are using the same version of SDK and SD header files as you used in IAR? Also that all the paths in your Makefile are present so sd_flash_xxx calls from pstorage module could be resolved?

RE: How to get the reference of the SoC library API?

Hamza — Fri, 01 Sep 2017 08:16:57 GMT

It's indeed gcc 6.3 (I edited the question), but the path is set.

Do you think the version of gcc could change something ?

RE: How to get the reference of the SoC library API?

Torsten Robitzki — Fri, 01 Sep 2017 08:07:23 GMT

How should a not installed compiler emit error messages?

RE: How to get the reference of the SoC library API?

Nguyen Hoan Hoang — Thu, 31 Aug 2017 19:26:38 GMT

It looks like your are compiling with GCC 6.3. Do you have it install in your system ? Check you PATH settings. It could be the root of the cause. GCC 5.4 works fine.