Trying to get AT Command example to compile from Fanstel

[mbates14]

So I am brand new at this product line, and basically new at C in general, I come from VB land. So bare with me please

I purchased both a Nordic nrf52 dev kit evaluation board, as well as a Fanstel BT832XE mainly for its long range with its built-in amplifier IC. the link to get the AT commands project + SDK they have posted, is here: www.dropbox.com/.../nRF5_SDK_14.rar

the folder is in the examples directory, and has hc-05 or hc-08, something like that. 

So I am running into a plethora of issues. They posted their example AT command codes on their website under SDK 14. However that is all setup for IAR and I have the free Segger studio installed. I tried to use the existing project folder and did an import with Segger, I ran into problem after problem .So I gave up there. Most of their documentation was written for nRFGo studio which I cannot find anymore. probably discontinued?

So after giving up importing the project, I attempted to "template" it into a working project, so I downloaded SDK 15 at first from Nordic, and I copied the C file from the AT commands example and it wont compile, too many errors because of SDK changes I suppose. 

I rolled back to SDK 14.2, took the uart example, copied and again overwrote the main.c file from the AT commands example, it builds all the way up to this point: 

Output/ble_serial_pca10040_s132 Debug/Obj/main.o: In function `fds_test_init':

undefined reference to `fds_register'

and on and on it goes with a whole bunch of fds stuff being undefined which makes no sense to me. 

But, fds.h include is present! I also checked and made sure FDS was turned on in the sdk_config.h file. Made no difference. Tried clean, tried rebuild, tried build, it gives me the same error under all tries.

So I am at a complete loss, I cant figure it out. The ultimate end-game here is to make some changes to the example program so I can "log-in" to the module before it allows sending/receiving between the UART and the BLE. Right now its configured open relay, anyone can connect and send/receive. I dont like that. 

[Nguyen Hoan Hoang]

First off, people are taking their own time trying to help you here, please be nice.

Second, the .h can be provided in 2 ways.  With a library or with source code.

In the case of a library, you only need to add the lib to your linker no src code require.  On the other hand when provided as source code, which is the case of this SDK, you need to add the source code into your project to compile it.  You will find that there are a bunch of code that you need to add. 

If you wish to use something easier, try this Bluetooth LE with nRF5x the easy way.  It has most of needed source built into a library for you. 

[mbates14]

I am being nice. Am I not being nice? That is the trouble when trying to read emotion out of text. I didn't put any into it that I am aware of. Sorry...

I am just trying to make sense of it all, and honestly it doesn't make sense to me. It still does not. the Main.C file has a bunch of H file includes, they all work except for that one. Nobody can seem to answer why? Specifically to this SDK and Segger, Why. 

Again, no emotion, no disrespect intended. I am just a VERY down to the point guy with no small talk or irrelevent riffraff. Guess that is just one of my faults, so I may come off as cold shouldered, but its not intended. 

[awneil]

You did say that you got this code from Fanstel.

Fanstel are the only ones who can can tell you why they did whatever they've done.

Have you tried using Nordic's own examples with the Nordic nrf52 dev kit?

mbates14 said:

So I am brand new at this product line, and basically new at C in general

So it might be better to spend some time getting the hang of 'C' - the Nordic SDK isn't really a great place for a beginner to start ...

[mbates14]

Which all fanstel did was modify the SDK example UART code with the AT command structure they designed, plus the FDS storage. Yes, I am a beginner at C but not at programming. I came from the VB/Java world, with a touch of procedural PHP. its just the C syntax is different.