Pairing code examples for an NRF51822 based peripheral.

RE: Pairing code examples for an NRF51822 based peripheral.

Robin — Fri, 04 Jan 2019 17:23:01 GMT

Hello Susheel,

I am closing this case. Most of the question have been resolve and we are on to the next set of concerns. I have generalized where we are and what needs to be done next and the help we could use in case # 220048.

Thank you for your continued assistance. I look forward to your responses in the mentioned case.

Robin@TL

RE: Pairing code examples for an NRF51822 based peripheral.

Susheel Nuguru — Wed, 26 Dec 2018 17:58:05 GMT

Most of us on holidays until New year. We will get back to you once we are back to office after 2nd January. I will clean up this case and make it public as soon as i am back to work.

RE: Pairing code examples for an NRF51822 based peripheral.

Robin — Sat, 22 Dec 2018 21:15:26 GMT

Hello Susheel,

I am closing this case I have changed the scope and added a new case for adding secure pairing/bonding to a ble_uart based application. Please remove all attached files and make this case public.

Thanks

Robin@TL

RE: Pairing code examples for an NRF51822 based peripheral.

Susheel Nuguru — Tue, 18 Dec 2018 21:50:26 GMT

I missed to see that, I will see if there is any initialization of peer manager in that project tomorrow, Its late here in Norway now.

RE: Pairing code examples for an NRF51822 based peripheral.

Robin — Tue, 18 Dec 2018 17:02:45 GMT

Hello Susheel,

I believe peer manager is in the code. Do you not see it in the uploaded project?

Robin

RE: Pairing code examples for an NRF51822 based peripheral.

Susheel Nuguru — Tue, 18 Dec 2018 12:46:22 GMT

Hello Robin,

You need to add peer manager to your code in SDK12.3. Please look at its usage documentation to be able to include it in your project.

RE: Pairing code examples for an NRF51822 based peripheral.

Robin — Thu, 13 Dec 2018 15:07:09 GMT

Hello again Susheel,

Just to be sure you know, we still need to get pairing up and running on our board. Please do not let the last post detract you from that. The critical point of needing data on the PC is imminent, so I am exploring other avenues to do so until we are there, but the goal is to get both uart and pairing running on our board so we can finalize the code before we release to production. Any guidance you can offer on the most direct path to this end is greatly appreciated.

Thanks again, awaiting guidance,

Robin

RE: Pairing code examples for an NRF51822 based peripheral.

Susheel Nuguru — Thu, 13 Dec 2018 08:18:13 GMT

Thanks for the feedback on this Robin, if things are not clear in the documentation, then we should know about it so that we can make it clearer. Creating a new case with that sounds perfect.

RE: Pairing code examples for an NRF51822 based peripheral.

Robin — Wed, 12 Dec 2018 20:19:24 GMT

Hello again Susheel,

Just a note to let you know that I have found reference to SES have an alternative to printf for development. Not sure what will happen when we go to production code, with all the printf's in the sdk stuff, but for now I an not concerned about retarget. I am however having issues trying to use our newly acquired pca10031 dongle to redirect the data stream from our uart to a terminal emulator on our pc. There is a tutorial for this, but the terminology used does not match the latest nrf connect gui, so interpreting gets very guessing. I will open a new case for this one in hope we can get the data we need from our board to a pc for analysis.

Thanks

Robin@TL

RE: Pairing code examples for an NRF51822 based peripheral.

Robin — Wed, 12 Dec 2018 15:00:50 GMT

Hello Susheel,

Our code does not use printf, but all of the sdk logging functions do.

What needs to be done to make this retarge work so we can see errors that may occur?

This seems it could be very helpful in debugging. I see that the sdk 12.3 retarget.c is considerably different. Are there any known problem with the sdk 11 version?

RE: Pairing code examples for an NRF51822 based peripheral.

Susheel Nuguru — Wed, 12 Dec 2018 14:20:17 GMT

this is to retarget your printf to UART instead of __stdout.

If you do not use printf, then remove it without hesitation.

RE: Pairing code examples for an NRF51822 based peripheral.

Robin — Wed, 12 Dec 2018 00:26:17 GMT

Hello again Susheel,

In anticipation of your answer regarding the "retarget.c" file necessity for pairing, I did get the app to build, However, I see no advertisement for pairing, nor does the uart path work any longer. I can easily go back and forth just by including/excluding the appropriate main.c file, so if you have any suggestions to try, I am prepared. One of the things I did note is that the RAM definition for the gls app is considerably higher than the for the uart app. I am not sure if it is required, but it does build and upload at the lower memory setting, but still wont run.

On a more general point, I am not sure how to determine the memory size requirement and then to make sure that the IDE properly allocates appropriately. If you can help me learn these details it of of this, it would be greatly appreciated.

Thanks again,

Robin@TL

RE: Pairing code examples for an NRF51822 based peripheral.

Robin — Tue, 11 Dec 2018 17:57:04 GMT

Hello Susheel,

Thank you for getting me straight on this one. I guess my old school thinking had me looking for a header or linker directive in an ld file, not in an xml.. Oh well,...

So now to the next problem:

There is a "retarget.c" file in the build list that will not compile. I am not sure what is being retargeted. Please explain. I had it excluded to get to where I was. When I include it here is the error messages:

storage size of '__stdout' isn't known

storage size of '__stdin' isn't known

at these lines:

FILE __stdout;
FILE __stdin;

I am not sure if this file is "needed" for pairing/bonding, but thought I should ask before moving on to test.

Thanks

Robin@TL

RE: Pairing code examples for an NRF51822 based peripheral.

Susheel Nuguru — Tue, 11 Dec 2018 09:18:25 GMT

You just needed to add one line in flash_placement.xml file in your project

  <MemorySegment name="$(FLASH_NAME:FLASH)">
    ....
    ....
	<ProgramSection alignment="4" keep="Yes" load="Yes" name=".fs_data" address_symbol="__start_fs_data"  end_symbol="__stop_fs_data" />
  </MemorySegment>

After that your project compiles fine.

...

RE: Pairing code examples for an NRF51822 based peripheral.

Robin — Mon, 10 Dec 2018 19:15:42 GMT

Ok friends, I am crying uncle, I cannot understand or find the cause of these errors. Attached is the project and SDK with source files embedded. The "SES" folder w/project resides under my documents folder, the iDrinkNRF folder has the source in the (ver 11) SDK ble_uart example folder. The upload would not take the full sdk directory structure, so I am uploading the components folder separately. Any help at all is greatly appreciated. Let me know ASAP if anything else is needed.

devzone.nordicsemi.com/.../components.zip

Robin@TL

devzone.nordicsemi.com/.../1376.SES.zip

RE: Pairing code examples for an NRF51822 based peripheral.

Robin — Mon, 10 Dec 2018 06:49:20 GMT

An update: I have taken the advice of a related ticket and merged our code into the ble_app_gls example to attempt pairing.

However, although all modules compile independently, there appears to be a memory segmentation problem when linking. It appears to be associated with the fstorage for fds code, but I cannot determine the fix. The initial error messages are as follows:

Output/Debug/Exe/iDrink.elf section `.fs_data' will not fit in region `UNPLACED_SECTIONS'

Subsequently several errors ensue...

region `UNPLACED_SECTIONS' overflowed by 16 bytes

Output/iDrink Debug/Obj/fstorage.o: In function `check_config':

undefined reference to `__start_fs_data'

undefined reference to `__stop_fs_data'

... and on ad-nauseam...

What file might I be missing to define this unplaced section in memory?

Thanks again, in advance,

Robin@TL