NFC does not scan when Soft device is loaded and section placement macros are changed.

RE: NFC does not scan when Soft device is loaded and section placement macros are changed.

Joakim Jakobsen — Tue, 02 Mar 2021 11:52:45 GMT

Great.

You are welcome to create a new ticket if you have any more questions.

Br,
Joakim

RE: NFC does not scan when Soft device is loaded and section placement macros are changed.

Shruthi K R — Mon, 01 Mar 2021 10:53:38 GMT

Ok. Thank you. Will start with one of the central examples and modify if I can achieve NFC with beacon scanner.

RE: NFC does not scan when Soft device is loaded and section placement macros are changed.

Joakim Jakobsen — Mon, 01 Mar 2021 09:28:19 GMT

Hi.

[quote user="Shruthi K R"] Can NFC and BLE scanner(which has soft device 132 ) co-exist on same program[/quote]

Yes, they can co-exist.

[quote user="Shruthi K R"]Can I get any example with combined NFC and BLE[/quote]

Altough experimental, there are several available in the latest version of the nRF5 SDK;

Experimental: BLE Pairing Using NFC - Peripheral Reference Example

Experimental: BLE Pairing Using NFC - Central Reference Example

Experimental: Heart Rate Application with BLE Pairing Using NFC Pairing Library

Experimental: HID Keyboard Application with BLE pairing using NFC

Experimental: BLE Heart Rate Collector Example with NFC Pairing

Br,
Joakim

RE: NFC does not scan when Soft device is loaded and section placement macros are changed.

Shruthi K R — Fri, 26 Feb 2021 10:56:11 GMT

FLASH_START=0x26000

FLASH_SIZE=0x5a000

RAM_START=0x20001DB8

RAM_SIZE=0xe248

Im using nRF52832 DK with s132 v7.2.0. I dont see any debug statements. The program is not downloading to the kit at all. While the RAM and FLASH sizes are being initialized, PC is loaded with some value and program stops.

My first clarification needed is - Can NFC and BLE scanner(which has soft device 132 ) co-exist on same program. Can I get any example with combined NFC and BLE. That would be of great help.

RE: NFC does not scan when Soft device is loaded and section placement macros are changed.

Joakim Jakobsen — Fri, 22 Jan 2021 08:54:50 GMT

It's very hard for me to say what memory settings will work for your application, as I don't have any knowledge about it.

But if you debug the application, in the debug window you should get suggested values for RAM and Flash if not sufficient.

You can't see that?

RE: NFC does not scan when Soft device is loaded and section placement macros are changed.

Shruthi K R — Tue, 19 Jan 2021 07:15:35 GMT

Hi,

Apologies for late response. I'm trying to change the flash and RAM address of softdevice. I saw the tutorial here. When I debug, there is an error in loading the soft device. Is there anywhere else to make changes for memory ?

I have downloaded s132 v 7.2.0. What should be the minimum RAM_START and FLASH_START ?

I'm new to this. Also Please let know what is FLASH_PH_START and FLASH_START difference ?

RE: NFC does not scan when Soft device is loaded and section placement macros are changed.

Joakim Jakobsen — Thu, 17 Dec 2020 09:15:33 GMT

Thank you.

I see that you get a PC value. Maybe you can check what specific function that correlates to the PC value?

Br,
Joakim

RE: NFC does not scan when Soft device is loaded and section placement macros are changed.

Shruthi K R — Mon, 14 Dec 2020 05:00:51 GMT

There are no errors while downloading the program. But when I debug, it is getting stuck at one of the commands - ldr r1,[sp, #24] please find the screen shot of debug window and registers. Debug is stopping here and consuming large number of cycles.

This is my main.c file.

devzone.nordicsemi.com/.../08641.main.c

RE: NFC does not scan when Soft device is loaded and section placement macros are changed.

Joakim Jakobsen — Sun, 13 Dec 2020 22:10:26 GMT

Hi.

You have checked that your code runs? Apart from not beeing able to scan NFC. You don't get stuck in an error handler or something similar?

I can forward your ticket to one of our NFC experts, and ask If they have some suggestions. I don't immediately see what the cause of this might be.

Br,
Joakim