Seriarization (UART) Read blob Failure

RE: Seriarization (UART) Read blob Failure

Sigurd — Mon, 28 Feb 2022 17:08:24 GMT

[quote user="H.O"]If it is changed to "Release", this problem doesn't occur. [/quote]

Good!

[quote user="H.O"]Can you explain the reason of this difference?[/quote]

Could be some timing issue / race condition.

RE: Seriarization (UART) Read blob Failure

H.O — Thu, 17 Feb 2022 02:00:42 GMT

Hi,

I add this verification result.

The build configration was "Debug" under this problem.

If it is changed to "Release", this problem doesn't occur.

Can you explain the reason of this difference?

B. R.

RE: Seriarization (UART) Read blob Failure

H.O — Tue, 15 Feb 2022 06:35:53 GMT

Hi,

Could you reproduce this problem?

I must solve it by the end of this week.

If you have any updated information, please let me know.

B.R.

RE: Seriarization (UART) Read blob Failure

H.O — Mon, 31 Jan 2022 04:29:35 GMT

I use attached simple script for python with pyserial.

devzone.nordicsemi.com/.../TP_5F00_Readblob_5F00_MK71521.py

RE: Seriarization (UART) Read blob Failure

Sigurd — Fri, 28 Jan 2022 09:59:38 GMT

Hi,

[quote user="H.O"]The command sequence for the UART is emulated from script on PC.[/quote]

Did you use pc-ble-driver-py? https://github.com/NordicSemiconductor/pc-ble-driver-py

or pc-ble-driver? https://github.com/NordicSemiconductor/pc-ble-driver

Or some other type of script? Can you share the script that reproduces this?

RE: Seriarization (UART) Read blob Failure

H.O — Fri, 28 Jan 2022 01:01:25 GMT

I debug on nRF52832 Board with PC via USB-serial(UART). nRF52832 Board.

nRF52832 firmware is connectivity of Serialization that modified UART port.

The command sequence for the UART is emulated from script on PC.

For this problem, can you explain the cause on command sequence of this ticket?

Can you reproduce this problem on your equipment?

RE: Seriarization (UART) Read blob Failure

Sigurd — Tue, 25 Jan 2022 09:15:32 GMT

Hi,

As far as I can see from the log, after the ATT_READ_BLOB_REQ with offset 88, sent from the master, the slave just stopped responding, and the link seem to have been lost. Likely it run into some issue in the application. You would have to debug the nRF52 application to see why it failed.

RE: Seriarization (UART) Read blob Failure

H.O — Sun, 23 Jan 2022 23:55:52 GMT

Hi, thank you for your reply.

I uploaded the below file.

devzone.nordicsemi.com/.../nRF52832_5F00_ReadBlob_5F00_Failure.zip

RE: Seriarization (UART) Read blob Failure

Sigurd — Fri, 21 Jan 2022 10:42:45 GMT

Hi,

Could you zip and upload the sniffer file as well?

RE: Seriarization (UART) Read blob Failure

H.O — Fri, 21 Jan 2022 00:21:02 GMT

I have BPA low energy of Teledyne. Can you find the below?

Peripheral (Slave) device is nRF52832.

RE: Seriarization (UART) Read blob Failure

Sigurd — Thu, 20 Jan 2022 11:57:50 GMT

Hi,

[quote user=""]nRF52832 Serialization UART command sequence is below.[/quote]

It's a bit difficult to understand what's happening with only this command sequence. Could you capture a sniffer trace?

https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE