nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Fri, 22 Mar 2024 07:24:14 GMT

Hi Vidar,

I used the nRF Connect app on Android.
Thank you for the suggestion and I will take the NUS as a reference for my custom service.
Thank you again for the long and professional guidance and support. I close this ticket.

Best regards,
Yanpeng Wu

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Vidar Berg — Thu, 21 Mar 2024 09:43:31 GMT

Hi Yanpeng,

Glad to hear that you were able to make it work. The client must be subscibed to the characteristic in order for the server to be able to send notifications, and this subscription is not retained across connections unless your devices are bonded.

[quote user="Yanpengwu"]I also found when disconnect and reconnct from the mobile app, the default state of 'Notifications and indications' is enabled, but it is actually disabled.[/quote]

Is this with the nRF Connect app on Android or iOS?

[quote user="Yanpengwu"]Next I will construct my BLE services and Characteristics for my application data. Could you help suggest a sample for this? In the sample 'peripheral_uart', I had not found the code for defining the Services and Characteristics. Thank you very much.[/quote]

You can use the NUS implementation as a reference for creating your own custom service: https://github.com/nrfconnect/sdk-nrf/blob/main/subsys/bluetooth/services/nus.c

Best regards,

Vidar

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Wed, 20 Mar 2024 13:45:21 GMT

Hi Vidar,

Thank you so much for your professional support:). I found the send-data error is caused by the unproper operation sequences.

1. I flashed the HEX you provided to my DK and tried to send/receive data and connect/disconnect. It can work well except in one situation: when the 'TX Characterristic Descriptors - Notifications and indications disabled' in the mobile APP, the 'ble_host: Failed to send data over BLE connection' will be reported.

I'm not sure if this is a small bug, if the central(the mobile APP) connected with the peripheral (my nRF5340 DK) but disabled the 'Notifications and indications', that just means the central does not subscribe to the notification, the GAP server should send data as usual and should not report a failure, is it right?

I also found when disconnect and reconnct from the mobile app, the default state of 'Notifications and indications' is enabled, but it is actually disabled. The send data error will occur in this situation too. That's the reason why sometimes only after disconnect/reconnct the error will appear.

2. In addition, in my application, I created threads on both appCore and netCore, and the priority=7,

K_THREAD_DEFINE(thread_check_id, LED_THREAD_STACKSIZE, blink_led, NULL, NULL, NULL,
K_PRIO_COOP(7), 0, 100);

and the ble_write_thread' priority also is 7

K_THREAD_DEFINE(ble_write_thread_id, STACKSIZE, ble_write_thread, NULL, NULL,
NULL, PRIORITY, 0, 0);

I'm not sure if it will affect the BLE data sent. I changed my thread's priority to 9 now.

After that, the BLE data bidirectional data exchange works well now.
Maybe I can say I get the robust BLE connection now:). Next I will construct my BLE services and Characteristics for my application data. Could you help suggest a sample for this? In the sample 'peripheral_uart', I had not found the code for defining the Services and Characteristics. Thank you very much.

Best regards,
Yanpeng Wu

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Vidar Berg — Wed, 20 Mar 2024 12:27:39 GMT

Hi Yanpeng,

No worries. But I'm not seeing any errors when sending data here. Please try the attached hex file I built and see if you get the same result. This is built with the original hci_rpmsg sample.

devzone.nordicsemi.com/.../3527.merged_5F00_domains.hex

Best regards,

Vidar

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Wed, 20 Mar 2024 12:06:44 GMT

Hi Vidar,

Sorry for the mistake. When I did a Pristine Build, the rpmsg_nrf53_sram was created properly in partitions.yml.
But when I flash the image to DK, still can see 'ble_host: Failed to send data over BLE connection', sending data from appCore terminal failed. (the data flow from mobile app to appCore terminal is ok)

It failed in bt_gatt_notify_cb():

in bt_gatt_notify_cb:

data.err = -ENOTCONN;
data.type = BT_GATT_CCC_NOTIFY;
data.nfy_params = params;

LOG_WRN("[in bt_gatt_notify_cb - 7.1], data.err=%d", data.err); //data.err=-128
bt_gatt_foreach_attr_type(data.handle, 0xffff, BT_UUID_GATT_CCC, NULL,
1, notify_cb, &data); //failed in notify_cb when Notify all peers configured
LOG_WRN("[in bt_gatt_notify_cb - 7.2], data.err=%d", data.err); //data.err=-128

return data.err;

Best regards,
Yanpeng Wu

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Vidar Berg — Wed, 20 Mar 2024 11:55:07 GMT

Hi Yanpeng,

By "build result being the same," do you mean that CONFIG_RPMSG_NRF53_SRAM_SIZE is still set to 0x0 in your .config output?

Best regards,

Vidar

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Wed, 20 Mar 2024 11:50:25 GMT

Hi Vidar,

I changed the overlay to

chosen {
/* /delete-property/ zephyr,ipc_shm;*/
nordic,nus-uart = &uart0;
};

but the build result and the send data behavior are the same. Could you help try the project on your nRF5340 DK and see the result?

Best regards,
Yanpeng Wu

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Vidar Berg — Wed, 20 Mar 2024 11:40:22 GMT

Hi Yanpeng,

Thanks for sharing the project. The problem is that you had deleted the ipc_shm node in your DT overlay:

Best regards,

Vidar

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Wed, 20 Mar 2024 10:51:32 GMT

Hi Vidar,

That's great, I minimized the project and attached it here:
devzone.nordicsemi.com/.../IOTDL.zip

I used SDK v2.5.2 on nRF5340 DK.
The child image used the default 'hci_rpmsg' and I just increased some stack size.

With this, you can reproduce:

(1) the build log "Dropping partition 'rpmsg_nrf53_sram' since its size is 0." and no 'rpmsg_nrf53_sram' in the partitions.yaml.

(2) The application can receive data via BLE, but can not send data(failed on calling bt_nus_send(), the trace was 'ble_host: Failed to send data over BLE connection').

Best regards,

Yanpeng Wu

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Vidar Berg — Wed, 20 Mar 2024 10:19:32 GMT

Hello,

I don't see anything wrong with your Kconfig settings. Can you submit your project here or via a private support ticket so that I can have a look at it?

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Wed, 20 Mar 2024 09:36:39 GMT

Update:
I enabled the IPC communication in my project currently. Maybe this part caused some conflicts?
In prj.conf:

# IPC communication
CONFIG_IPC_SERVICE=y
CONFIG_IPC_SERVICE_BACKEND_ICMSG=y
CONFIG_MBOX=y

In boards\nrf5340dk_nrf5340_cpuapp.overlay:

reserved-memory {
		/delete-node/ memory@20070000;

		sram_tx: memory@20070000 {
			reg = <0x20070000 0x400>;
		};

		sram_rx: memory@20078000 {
			reg = <0x20078000 0x0800>;
		};
	};

	ipc {
		/delete-node/ ipc0;

		ipc0: ipc0 {
			compatible = "zephyr,ipc-icmsg";
			tx-region = <&sram_tx>;
			rx-region = <&sram_rx>;
			mboxes = <&mbox 0>, <&mbox 1>;
			mbox-names = "tx", "rx";
			status = "okay";
		};
	};

When I remove these codes and build, there is still no rpmsg_nrf53_sram in the partitions.yml. And the system behavior changed:

(1). When I disconnect the BLE connection on the app 'nRF Connect for Mobile', the system does not crash as ASSERTION FAIL with opcode-0x200a-timeout.

(2). The nr5340 DK only can receive data via BLE, when it sends data, it fails when calling bt_nus_send(), and the trace is "Failed to send data over BLE connection".

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Wed, 20 Mar 2024 08:24:42 GMT

Hi Vidar,

I checked my prj.conf, there is no CONFIG_RPMSG_NRF53_SRAM_SIZE symbol.

I saw this symbol is dependent on CONFIG_PARTITION_MANAGER_ENABLED. I enabled it with cmake argument '-Dhci_rpmsg_OVERLAY_CONFIG="C:/ncs/v2.5.2/nrf/subsys/partition_manager/partition_manager_enabled.conf"', just as the sample 'peripheral_uart' did.

I attached my prj.conf for your information, in case there are conflicts inside.

devzone.nordicsemi.com/.../my-prj.conf

Best regards,

Yanpeng Wu

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Vidar Berg — Wed, 20 Mar 2024 07:31:41 GMT

Hi Yanpeng,

[quote user="Yanpengwu"]I compared the CMakelists.txt in my project and the 'peripheral_uart', and did not find any difference for this. [/quote]

Please compare the prj.conf settings instead and make sure you haven't set the CONFIG_RPMSG_NRF53_SRAM_SIZE symbol.

Best regards,

Vidar

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Tue, 19 Mar 2024 17:46:08 GMT

Hi Vidar,

Thanks for the quick reply.
In my project, I unchecked the 'Use sysbuild' in the Build Configuration, and found the image on netCore became 'hci_rpmsg', but still no 'rpmsg_nrf53_sram' in the partitions.yml.
In the build log, there is 'Dropping partition 'rpmsg_nrf53_sram' since its size is 0.'

I compared the CMakelists.txt in my project and the 'peripheral_uart', and did not find any difference for this. Maybe I missed something in my appCore build script...?

Best regards,
Yanpeng Wu

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Vidar Berg — Tue, 19 Mar 2024 16:49:21 GMT

Hi Yanpeng,

'hci_rpmsg' is included as a child image by default when you enable Bluetoot in the parent application running on the application core. This is controlled by the CONFIG_NCS_INCLUDE_RPMSG_CHILD_IMAGE symbol.

Best regards,

Vidar

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Tue, 19 Mar 2024 16:38:47 GMT

Hi Vidar,

Thank you for your suggestion. I will try the way that uses 'hci_rpmsg' as the child image on netCore and add my code to it.

For the appCore, can I take the 'peripheral_uart' as a reference to try the multi-image build? I searched in this sample and did not find anywhere mentioned 'hci_rpmsg', where did it define the 'hci_rpmsg' as its child image on netCore? Could you help give some hints for this? Thank you very much.

Best regards,
Yanpeng Wu

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Vidar Berg — Tue, 19 Mar 2024 12:49:33 GMT

Hello Yanpeng,

Sysbuild is still an experimental feature with several limitations. For now, I would recommend using the nRF Connect SDK's specific Multi-image support. The easiest approach would be to directly modify the hci_rpmsg in the SDK tree.

Best regards,

Vidar

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Mon, 18 Mar 2024 14:20:10 GMT

Update: I found there is only one line code 'CONFIG_PARTITION_MANAGER_ENABLED=y' in the cmake argument '-Dhci_rpmsg_OVERLAY_CONFIG="C:/ncs/v2.5.2/nrf/subsys/partition_manager/partition_manager_enabled.conf"'. So I removed the cmake argument and added 'CONFIG_PARTITION_MANAGER_ENABLED=y' in my pj.conf. But the result is the same.

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Yanpengwu — Mon, 18 Mar 2024 14:03:07 GMT

Hello Vidar,

Thank you for your reply. I'm not using the original hci_rpmsg child image. In my application, I'm using a sysbuild and there is another small task on netCore, so I ported the code of hci_rpmsg to my application code on the netCore.

In the sample peripheral_uart, I did not find how it define the hci_rpmsg as its default child image. I guessed it should be the configuration 'config NRF_DEFAULT_BLUETOOTH default y' in the Kconfig.sysbuild, is it correct?

After I ported the code to my application, the first build had some errors with the flash partition, then I added the cmake argument '-Dhci_rpmsg_OVERLAY_CONFIG="C:/ncs/v2.5.2/nrf/subsys/partition_manager/partition_manager_enabled.conf"', just as the sample did. After this, the BLE communication is ok, but when I compare the partitions.yml files in the sample and my project, I found the difference of rpmsg_nrf53_sram.

Best regards,
Yanpeng Wu

RE: nRF5340 BLE: How to create the rpmsg_nrf53_sram in partitions.yml during porting the sample 'peripheral_uart'

Vidar Berg — Mon, 18 Mar 2024 13:37:44 GMT

Hello Yanpeng,

Could you provide a bit more information about how your project setup differs from the peripheral_uart sample? Do you still use the same hci_rpmsg child image in your build? The 'rpmsg_nrf53_sram' section should be added automatically by the build script here: https://github.com/nrfconnect/sdk-nrf/blob/d5a11bd8bd803fff7615f9b0c5227a60c761da27/subsys/partition_manager/CMakeLists.txt#L87

Best regards,

Vidar