Is the peer functionality related to RTC?

RE: Is the peer functionality related to RTC?

tony55723 — Tue, 02 Apr 2024 08:22:34 GMT

Thank you very much. Your previous responses have taught me a lot. Now, all I need to do is fill in my custom data, and this product will be complete. If possible, I'll set it to 'Verify Answer'.

RE: Is the peer functionality related to RTC?

Vidar Berg — Tue, 02 Apr 2024 08:08:17 GMT

Excellent. Yes, most have now returned to the office.

RE: Is the peer functionality related to RTC?

tony55723 — Tue, 02 Apr 2024 07:59:08 GMT

Finally, with this code added, I can send the data.

ble_nus_c_on_db_disc_evt(&m_ble_nus_c, p_evt);

Has Easter holiday ended?

No one has answered any questions these days...

RE: Is the peer functionality related to RTC?

Vidar Berg — Tue, 02 Apr 2024 07:45:03 GMT

What is the 'ret_val' value returned by ble_nus_c_string_send? The data will only be sent if it is NRF_SUCCESS ('0').

RE: Is the peer functionality related to RTC?

tony55723 — Wed, 27 Mar 2024 09:23:36 GMT

Thank you so mush.

The 'NRF_ERROR_INVALID_LENGTH' issue has been resolved because it requires powers of 2, such as 2, 4, 8, 16, 32, 64.

#define UART_TX_BUF_SIZE                32                                         /**< UART TX buffer size. */
#define UART_RX_BUF_SIZE                32                                         /**< UART RX buffer size. */

I'd like to ask a new question. I added NUS and NUS_C in ble_app_multirole_lesc and removed HRS. Both devices have downloaded the same program.

The connection setup is as follows: Phone -> A -> B. At this point, the phone sends data to A. In the nus_data_handler of A, I receive data from the phone, and inside it, I execute ret_val = ble_nus_c_string_send(&m_ble_nus_c, ReceiveData, 20);. Unfortunately, B did not receive the data sent by A.

static void nus_data_handler(ble_nus_evt_t * p_evt)	
{
	uint32_t ret_val;
	uint8_t i;
	
	if (p_evt->type == BLE_NUS_EVT_RX_DATA)
    {
		uint8_t ReceiveData[20];

		
        NRF_LOG_DEBUG("Received data from BLE NUS. Writing data on UART.");
        NRF_LOG_HEXDUMP_DEBUG(p_evt->params.rx_data.p_data, p_evt->params.rx_data.length);

        for (uint32_t i = 0; i < p_evt->params.rx_data.length; i++)
        {
			ReceiveData[i] = p_evt->params.rx_data.p_data[i];
        }
			
		NRF_LOG_INFO("data[0] = %d, data[1] = %d, data[2] = %d, data[19] = %d", ReceiveData[0], ReceiveData[1], ReceiveData[2], ReceiveData[19]);
		
		
		do
		{
			ret_val = ble_nus_c_string_send(&m_ble_nus_c, ReceiveData, 20);
			
			if ( (ret_val != NRF_ERROR_INVALID_STATE) && (ret_val != NRF_ERROR_RESOURCES) )
			{
				APP_ERROR_CHECK(ret_val);
			}
		} while (ret_val == NRF_ERROR_RESOURCES);
		
		
		for (i = 0 ; i < 20 ; i++)
		{
			if(i == 19)
				app_uart_put(0xa0);
			else
				app_uart_put(ReceiveData[i]);
		}
    }
}

Additionally, there is one more note: if Device B is connected to J-Link, RTT will provide feedback:

 <info> app: CENTRAL: Already connected to this device as PERIPHERAL (handle: 0), disconnecting.

But if Device A is connected to J-Link, RTT will provide feedback:

<info> app: PERIPHERAL: Already connected to this device as CENTRAL (handle: 1), disconnecting.

I want to use NUS to send data. Does it conflict with the additional information?

Thank you

RE: Is the peer functionality related to RTC?

Vidar Berg — Tue, 26 Mar 2024 05:49:48 GMT

Is it your advertising start function that returns with NRF_ERROR_INVALID_LENGTH?

[quote user="tony55723"]First, I asked about the error. Now I ask about the UART. I don’t know if this will violate the rules.[/quote]

This is fine. Thank you for letting me know. The problem with duplicate questions is that we can end up with several engineers working on the same issue, which we want to avoid. However, the question you posted is not really a duplicate.

RE: Is the peer functionality related to RTC?

tony55723 — Mon, 25 Mar 2024 12:49:21 GMT

The error I encountered is 'NRF_ERROR_INVALID_LENGTH'.

I still feel very sorry, because of two things.

【1】First, I asked about the error. Now I ask about the UART. I don’t know if this will violate the rules.

【2】Yesterday I submitted a new question, and a few minutes ago the system prompted an engineer to accept it.

what should i do now....?（What I mean is, will this cause you trouble?）

Thank you

RE: Is the peer functionality related to RTC?

Vidar Berg — Mon, 25 Mar 2024 12:25:49 GMT

[quote user="tony55723"]Do you know how much RAM NUS and UART respectively occupy?[/quote]

I don't have any numbers on this. Generally, fitting a multirole application on the 52811 is challenging due to memory constraints. However, all memory is statically allocated, so you should receive an error at build time if there is insufficient memory. Have you checked the return code from your advertising start function?

RE: Is the peer functionality related to RTC?

tony55723 — Mon, 25 Mar 2024 11:22:38 GMT

sorry,

I give up on the RTT repetitive printing issue. I only have one J-Link in hand, and I lack experience in firmware upgrades. I fear more problems might arise.

May I ask a question?

examples \ ble_central_and_peripheral \ experimental \ ble_app_multirole_lesc

This is the example I've been using. I tried adding NUS and NUS_C, and deleted HRS and PEER. Finally, I ported it to 52811, all of which were successful. Eventually, I added UART functionality, successfully compiled it, and downloaded the program to 52811. However, after scanning with my phone, I couldn't find this device.

Do you know how much RAM NUS and UART respectively occupy?

Thank you

RE: Is the peer functionality related to RTC?

Vidar Berg — Mon, 25 Mar 2024 10:16:24 GMT

Did this updating the J-link drivers fix the issue with duplicate log messages?

[quote user="tony55723"] Above that is when 52811 is running. I connected and then disconnected with my phone, then after a short period of time, an 'app: Fatal error' occurred.[/quote]

In your debugger, can you read the error information passed to the error handler to find out where the error was raised?

RE: Is the peer functionality related to RTC?

tony55723 — Mon, 25 Mar 2024 07:55:56 GMT

I installed the new nRF command line tools, and it also asked me if I wanted to install J-Link 7.94e, to which I agreed.

The test results are divided into two sections, with the yellow text 'connection lost' in the middle. Above that is when 52811 is running. I connected and then disconnected with my phone, then after a short period of time, an 'app: Fatal error' occurred.

Below the yellow text is when 52811 is running. I didn't do anything, and after a short period of time, an 'app: Fatal error' also occurred.

RE: Is the peer functionality related to RTC?

Vidar Berg — Mon, 25 Mar 2024 07:25:02 GMT

The Softdevice will raise an assert if you start and stop exection as it will break it's real time requirements. So, this is to be expected. The ble_app_uart will also attempt to enter System OFF mode (deep sleep) when the advertiser times out after 3 minutes. But it is not possible to enter System OFF when the chip is in debug interface mode, so this will also trigger an error.

I see you are using an old Jlink version. Could you try to update your nRF command line tools package (https://www.nordicsemi.com/Products/Development-tools/nRF-Command-Line-Tools/Download) and see if that changes anything?

RE: Is the peer functionality related to RTC?

tony55723 — Mon, 25 Mar 2024 07:20:26 GMT

The current breakpoint in this main() function has only been reached once.

Something very strange is happening. When I start debugging, I execute 'run', then I click 'stop', but the code window doesn't display the current position where it stopped. Then, I repeatedly click 'run' and 'stop', and only register R7 is changing in the left register window. Eventually, it ends up in NRF_BREAKPOINT_COND error.

I just discovered an issue: after starting debugging, it keeps running continuously without me clicking 'stop'. After about 10 to 15 minutes, it also ends up in NRF_BREAKPOINT_COND.

Additional note: During the 'run' period, my phone can scan and receive broadcast information from the device.

RE: Is the peer functionality related to RTC?

Vidar Berg — Mon, 25 Mar 2024 06:39:50 GMT

I haven't experienced this issue here. I have a board with the nRF52811 and have tested it using the ble_app_uart pca10056e configuration. Please place a breakpoint at the beginning of main() and see if it is reached again after you start execution. This will help us determine whether the device is rebooting.

RE: Is the peer functionality related to RTC?

tony55723 — Fri, 22 Mar 2024 12:51:48 GMT

I made a significant discovery. After I extracted SDK 17.1.0 and placed it in a new folder, I believe the examples inside have been thoroughly tested by the official team. However, when I found the peripheral/uart example, compiled it, and downloaded it to the chip, I noticed that the RTT still had the issue of repetitive printing. Should we consider focusing on the hardware or perhaps the debugger?

RE: Is the peer functionality related to RTC?

Vidar Berg — Fri, 22 Mar 2024 12:34:56 GMT

It's a bit difficult for me to understand what the log is supposed to look like, as I'm not familiar with your application. However, I agree it could make sense to attempt to address the "Connection handle invalid" warning first.

RE: Is the peer functionality related to RTC?

tony55723 — Fri, 22 Mar 2024 11:13:50 GMT

I can still see repeated logs. I just want to find a pattern (if there is one) to see if it can help with the issue.

Perhaps I should focus on addressing the issue from the warnings in the RTT logs?

<warning> ble_nus_c: Connection handle invalid.

RE: Is the peer functionality related to RTC?

Vidar Berg — Fri, 22 Mar 2024 10:58:24 GMT

Sorry, I'm not sure I understand what you mean. Are you saying that you are not seeing duplicated log messages anymore?

RE: Is the peer functionality related to RTC?

tony55723 — Fri, 22 Mar 2024 09:36:00 GMT

I'm really sorry, but it seems that there is no pattern in the RTT. I just thought it would output a maximum of four commands.

RE: Is the peer functionality related to RTC?

tony55723 — Fri, 22 Mar 2024 09:22:47 GMT

I don't know if it executed a reboot or not.

data[1]" is a data I defined myself. The mobile app will send different data based on the UI button. But what I want to say is, this RTT seems to only record the last 4 sets of commands.

The left and right sides of the image respectively show the results of two tests. I clicked the UI button on the app several times, and there must be a lot of data in the RTT. However, I cleared the RTT view, then waited for it to repeat printing before capturing the effect.

RE: Is the peer functionality related to RTC?

Vidar Berg — Fri, 22 Mar 2024 08:42:33 GMT

Strange. You are also sure that the device is not rebooting?

RE: Is the peer functionality related to RTC?

tony55723 — Fri, 22 Mar 2024 08:34:50 GMT

Hello Berg,

I haven't modified log_init(), so I'm also puzzled why such an issue would occur.

RE: Is the peer functionality related to RTC?

Vidar Berg — Fri, 22 Mar 2024 08:24:25 GMT

Hello,

Thanks for confirming. Can you also show your implementation of log_init()?

RE: Is the peer functionality related to RTC?

tony55723 — Fri, 22 Mar 2024 07:48:43 GMT

Hello Berg,

In the main() function, LOG_INIT() is the first to be called.

I originally intended to count the interval time for repeated printing, but it was irregular. Sometimes it repeats printing after 10 seconds, and sometimes it takes over a minute before repeating.

This time, I won't use my phone to send data. After the device is powered on, I'll start RTT, and then I won't do anything else

The repetitive issue still occurred. Could you please assist me again? Thank you.

RE: Is the peer functionality related to RTC?

Vidar Berg — Fri, 22 Mar 2024 06:58:39 GMT

Hello,

I'm glad to hear that it fixed the problem. Regarding the duplicated log messages, are you initializing the logger at the very beginning of main()? I have seen instances where the log has been duplicated when LOG_INIT() was called too late.