LAUNCHXL-CC2640R2: Simple_profile project with SIMPLEPROFILE_CHAR4_LEN more then 20

AlexHome

Hello!
I set up a job with Characteristic 4 Value according to e2e.ti.com/.../764078

And now I can send more bytes, but only once or a little more.
Please help with the following points:
1) I assumed that the Simple_profile project uses the AUTOHEAPSIZE define, i.e. there is no need to set HEAPMGR_SIZE manually. I'm right?
2) According to the recommendations, I tried to track HEAPMGR_SIZE after changing MAX_PDU_SIZE from 69 to 255, but the result is the same - 5163 bytes. In my opinion, he had to change, because AUTOHEAPSIZE mode is used. Or should not?
3) I tried to increase SBP_TASK_STACK_SIZE even 1500 (now SIMPLEPROFILE_CHAR4_LEN == 251) - to no avail ... I think I need to increase SBP_TASK_STACK_SIZE but only slightly more than 250 bytes according to the new SIMPLEPROFILE_CHAR4_LEN. I'm right?
4) After sending 251 bytes or several smaller packages, the program no longer sends packets and issues HAL_ASSERT_CAUSE_ICALL_TIMEOUT. How to fix it?
5) I can not get the parameters of the Tasks STACK in debug mode using TI-RTOS. Gives the message: Target memory read failed at address: 0x20002ccc, length: 76
Target memory read failed at address: 0x20002ccc, length: 76
Something with an overflowing stack? How to fix it?
6) Can BTool / LAUNCHXL-CC2640R2 with the host_test project receive and output to Btool log 251 byte packets? I think so, because in preprocessor define MAX_PDU_SIZE = 255. I'm right?

over 6 years ago

0 Ammar N over 6 years ago

TI__Mastermind 25810 points

Hello,

Let's take a step back. What are you trying to do?

To answer your original question, have you taken a look at our Debugging guide? http://dev.ti.com/tirex/content/simplelink_cc2640r2_sdk_2_40_00_32/docs/blestack/ble_user_guide/html/ble-stack-3.x-guide/debugging-index.html

AlexHome said:
1) I assumed that the Simple_profile project uses the AUTOHEAPSIZE define, i.e. there is no need to set HEAPMGR_SIZE manually. I'm right?
2) According to the recommendations, I tried to track HEAPMGR_SIZE after changing MAX_PDU_SIZE from 69 to 255, but the result is the same - 5163 bytes. In my opinion, he had to change, because AUTOHEAPSIZE mode is used. Or should not?

If your application requires more memory, you may want to adjust the HEAPMGR_SIZE. Take a look at the Debugging Common Heap Issues section for details on enabling HEAPMGR_METRICS to determine if this is needed.

AlexHome said:
3) I tried to increase SBP_TASK_STACK_SIZE even 1500 (now SIMPLEPROFILE_CHAR4_LEN == 251) - to no avail ... I think I need to increase SBP_TASK_STACK_SIZE but only slightly more than 250 bytes according to the new SIMPLEPROFILE_CHAR4_LEN. I'm right?

It may be helpful for you to take a look at the .map file after building your project to get an idea of how things are being allocated and what may need more memory. Additionally, you can use the Memory Allocation tool to see an overview of your memory usage. Again, take a look at the debugger's guide for more information.

AlexHome said:
4) After sending 251 bytes or several smaller packages, the program no longer sends packets and issues HAL_ASSERT_CAUSE_ICALL_TIMEOUT. How to fix it?

http://dev.ti.com/tirex/content/simplelink_cc2640r2_sdk_2_40_00_32/docs/blestack/ble_user_guide/html/ble-stack-3.x-guide/debugging-index.html#hal-assert-causes-and-explanation

AlexHome said:
5) I can not get the parameters of the Tasks STACK in debug mode using TI-RTOS. Gives the message: Target memory read failed at address: 0x20002ccc, length: 76
Target memory read failed at address: 0x20002ccc, length: 76
Something with an overflowing stack? How to fix it?

You can use the ROV (explained in the user's guide) to take a look at individual task usage. If you have memory issues, then this is likely the cause.

AlexHome said:
6) Can BTool / LAUNCHXL-CC2640R2 with the host_test project receive and output to Btool log 251 byte packets? I think so, because in preprocessor define MAX_PDU_SIZE = 255. I'm right?

Correct!

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Hello, Ammar! Thanks for links!

I try to follow them but still can't solve my problems...

0 Ammar N over 6 years ago in reply to AlexHome

TI__Mastermind 25810 points

Let's take a step back first. What are you trying to accomplish?

If you simply want to increase the length of a characteristic past 20, you can do so without altering the allocated memory (in the default project).

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Ammar, thanks! But why when trying to send 251 bytes or a little less, ICALL issues assert?
And if I want to create a separate service for this characteristic, will I need to altering the allocated memory in this case?

0 Ammar N over 6 years ago in reply to AlexHome

TI__Mastermind 25810 points

Take a look at the data service in Project Zero. It implements a characteristic of LEN 40, but it should still work for larger bytes. This also can help answer your second question too.

In short, you shouldn't need to allocate memory to create a new service. Creating a new service (and setting it up for long characteristic writes) are covered in our Custom Profile SimpleLink Academy lab.

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Ammar, thanks! But 40 is still lower then define MAX_PDU_SIZE==69 in Project Zero... Why larger bytes (251 and some lower values) cause ICALL asserts (even after setup MAX_PDU_SIZE = 255)?

0 Ammar N over 6 years ago in reply to AlexHome

TI__Mastermind 25810 points

Well, 40 is just the size chosen for that example, but it can definitely go higher.

Can you share your code? ICALL asserts happen for various reasons and usually are a result of some configuration (or potential memory) mismatch.

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Ammar, I use clear simple_pfofile project with next changes (may be problem in this code?):

***in simple_gatt_profile.c and .h :

// Length of Characteristic 4 in bytes
#define SIMPLEPROFILE_CHAR4_LEN 200

// Characteristic 4 Value
static uint8 simpleProfileChar4[SIMPLEPROFILE_CHAR4_LEN];

simpleProfileChar4 instead &simpleProfileChar4 in simpleProfileAttrTbl

***in SimpleProfile_SetParameter:

if ( len == SIMPLEPROFILE_CHAR4_LEN )
{
VOID memcpy( simpleProfileChar4, value, SIMPLEPROFILE_CHAR4_LEN );

// See if Notification has been enabled
GATTServApp_ProcessCharCfg( simpleProfileChar4Config, simpleProfileChar4, FALSE,
simpleProfileAttrTbl, GATT_NUM_ATTRS( simpleProfileAttrTbl ),
INVALID_TASK_ID, simpleProfile_ReadAttrCB );
}

***in SimpleProfile_GetParameter:

VOID memcpy( value, simpleProfileChar4, SIMPLEPROFILE_CHAR4_LEN );

***in simpleProfile_ReadAttrCB

case SIMPLEPROFILE_CHAR4_UUID:
*pLen = SIMPLEPROFILE_CHAR4_LEN;
VOID memcpy( pValue, pAttr->pValue, SIMPLEPROFILE_CHAR4_LEN );
break;

***in simple_peripheral.c :

uint8_t charValue4[SIMPLEPROFILE_CHAR4_LEN] = {0};
SimpleProfile_SetParameter(SIMPLEPROFILE_CHAR4, SIMPLEPROFILE_CHAR4_LEN,
charValue4);

0 Ammar N over 6 years ago in reply to AlexHome

TI__Mastermind 25810 points

Hey Alex,

Take a look at project zero for implementation details. You're almost there. I made similar changes to the data service (DS_STRING_LEN = 200).

The main thing I realized, and I apologize for this oversight, is that we need to also update the rxMTU size as well. Using host_test, I sent a GATT_ExchangeMTU() command and increase the rxMTU to 250. I then performed a GATT_WriteLongCharValue command with the packet information. I was able to read this value back similarly with all the data retained.

More details here: e2e.ti.com/.../543331
Hope this helps!

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Ammar, thanks!
But I perform GATT_ExchangeMTU with parameter 251. Is it anougth to change rxMTU to 251?

[49] : <Tx> - 07:46:33.409
-Type : 0x01 (Command)
-OpCode : 0xFD82 (GATT_ExchangeMTU)
-Data Length : 0x04 (4) byte(s)
ConnHandle : 0xFFFE (65534)
ClientRxMTU : 0x00FB (251)

[50] : <Rx> - 07:46:33.458
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x06 (6) bytes(s)
Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
Status : 0x00 (0) (SUCCESS)
OpCode : 0xFD82 (GATT_ExchangeMTU)
DataLength : 0x00 (0)

Ok, I look at project zero for implementation details...

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Ammar, now i can read 200 byte but can send only one notification . After enabling notifications for Char4 and perform first SimpleProfile_SetParameter(SIMPLEPROFILE_CHAR4, SIMPLEPROFILE_CHAR4_LEN, &data)

project asserts:

:>> DEFAULT SPINLOCK!

Need i check if ICALL is free to send new notification? And how can i do it?

0 Ammar N over 6 years ago in reply to AlexHome

TI__Mastermind 25810 points

That's great to hear. I'm glad you were able to write 200 bytes to your characteristic.

Yes, you should allocate enough memory to also handle the notifications as well. Take a look at this thread that has done this successfully: e2e.ti.com/.../723273 .

Let me know if you have any questions.

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Ammar, thanks for link! I'll look at it surely!
So I set MAX_NUM_PDU=3 and #define SBP_TASK_STACK_SIZE 800
so now i can get 200 notifications but sometimes they are lost. I think that gatt server can't hold alot of notifications.
Need I check if ICALL ready to get new notifications before call GATTServApp_ProcessCharCfg() ? And how?

0 Ammar N over 6 years ago in reply to AlexHome

TI__Mastermind 25810 points

If you can provide sniffer logs, we can see what's happening over the air to narrow down why they are getting lost.

How often are you sending the notifications? One way to guarantee that you receive each notification is to use indications instead. The difference here is that the slave sends a notification which the master acknowledges. Once you have the acknowledgement, you know you can send another notification.

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Ammar, thanks! I apologize for the long answer.

//If you can provide sniffer logs
Ok i'll make sniffer (with host_test) logs.

//How often are you sending the notifications?
Now i send 128 byte notifications every 40 ms and almost 100% notifications come. If you reduce the sending time to 7.5ms, the ICALL freezes

//One way to guarantee that you receive each notification is to use indications instead.
i want to get maximum throughput, so indications is wery slow fo this purpose

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Ammar, i've done logs with next two configs of project:

MAX_PDU_SIZE=162

#define SIMPLEPROFILE_CHAR4_LEN 128

MAX_NUM_PDU=3

and

MAX_PDU_SIZE=255

#define SIMPLEPROFILE_CHAR4_LEN 200

MAX_NUM_PDU=3

I send notifications every 10 ms. With first config all right. With second - only two packet received and then HAL_ASSERT_CAUSE_ICALL_TIMEOUT occur:

Fullscreen simple.txt Download

Every 10 ms

MAX_PDU_SIZE=162
#define SIMPLEPROFILE_CHAR4_LEN           128
MAX_NUM_PDU=3



[1] : <Tx> - 04:01:43.374
-Type           : 0x01 (Command)
-OpCode         : 0xFD92 (GATT_WriteCharValue)
-Data Length    : 0x08 (8) byte(s)
 ConnHandle     : 0x0000 (0)
 Handle         : 0x0021 (33)
 Value          : 0C:00:00:00
Dump(Tx):
0000:01 92 FD 08 00 00 21 00 0C 00 00 00             ......!.....
--------------------------------------------------------------------
[2] : <Rx> - 04:01:43.396
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x06 (6) bytes(s)
 Event          : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
 Status         : 0x00 (0) (SUCCESS)
 OpCode         : 0xFD92 (GATT_WriteCharValue)
 DataLength     : 0x00 (0)
Dump(Rx):
0000:04 FF 06 7F 06 00 92 FD 00                      .........
--------------------------------------------------------------------
[3] : <Rx> - 04:01:43.538
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x06 (6) bytes(s)
 Event          : 0x0513 (1299) (ATT_WriteRsp)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x00 (0)
Dump(Rx):
0000:04 FF 06 13 05 00 00 00 00                      .........
--------------------------------------------------------------------
[4] : <Rx> - 04:01:43.549
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x88 (136) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x82 (130)
 Handle         : 0x002B (43)
 Value          : FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF
Dump(Rx):
0000:04 FF 88 1B 05 00 00 00 82 2B 00 FF FF FF FF FF .........+......
0010:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080:FF FF FF FF FF FF FF FF FF FF FF                ...........
--------------------------------------------------------------------
[5] : <Rx> - 04:01:43.560
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x88 (136) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x82 (130)
 Handle         : 0x002B (43)
 Value          : FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF
Dump(Rx):
0000:04 FF 88 1B 05 00 00 00 82 2B 00 FF FF FF FF FF .........+......
0010:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080:FF FF FF FF FF FF FF FF FF FF FF                ...........
--------------------------------------------------------------------
[6] : <Rx> - 04:01:43.641
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x88 (136) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x82 (130)
 Handle         : 0x002B (43)
 Value          : FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF
Dump(Rx):
0000:04 FF 88 1B 05 00 00 00 82 2B 00 FF FF FF FF FF .........+......
0010:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080:FF FF FF FF FF FF FF FF FF FF FF                ...........
--------------------------------------------------------------------
[7] : <Rx> - 04:01:43.663
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x88 (136) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x82 (130)
 Handle         : 0x002B (43)
 Value          : FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF
Dump(Rx):
0000:04 FF 88 1B 05 00 00 00 82 2B 00 FF FF FF FF FF .........+......
0010:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080:FF FF FF FF FF FF FF FF FF FF FF                ...........
--------------------------------------------------------------------
[8] : <Rx> - 04:01:43.674
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x88 (136) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x82 (130)
 Handle         : 0x002B (43)
 Value          : FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF
Dump(Rx):
0000:04 FF 88 1B 05 00 00 00 82 2B 00 FF FF FF FF FF .........+......
0010:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080:FF FF FF FF FF FF FF FF FF FF FF                ...........
--------------------------------------------------------------------
[9] : <Rx> - 04:01:43.741
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x88 (136) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x82 (130)
 Handle         : 0x002B (43)
 Value          : FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF
Dump(Rx):
0000:04 FF 88 1B 05 00 00 00 82 2B 00 FF FF FF FF FF .........+......
0010:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080:FF FF FF FF FF FF FF FF FF FF FF                ...........
--------------------------------------------------------------------
[10] : <Rx> - 04:01:43.763
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x88 (136) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x82 (130)
 Handle         : 0x002B (43)
 Value          : FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF
Dump(Rx):
0000:04 FF 88 1B 05 00 00 00 82 2B 00 FF FF FF FF FF .........+......
0010:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080:FF FF FF FF FF FF FF FF FF FF FF                ..........






MAX_PDU_SIZE=255
#define SIMPLEPROFILE_CHAR4_LEN           200
MAX_NUM_PDU=3



--------------------------------------------------------------------
[397] : <Tx> - 04:12:02.391
-Type           : 0x01 (Command)
-OpCode         : 0xFD92 (GATT_WriteCharValue)
-Data Length    : 0x08 (8) byte(s)
 ConnHandle     : 0x0000 (0)
 Handle         : 0x0021 (33)
 Value          : 0C:00:00:00
Dump(Tx):
0000:01 92 FD 08 00 00 21 00 0C 00 00 00             ......!.....
--------------------------------------------------------------------
[398] : <Rx> - 04:12:02.427
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x06 (6) bytes(s)
 Event          : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
 Status         : 0x00 (0) (SUCCESS)
 OpCode         : 0xFD92 (GATT_WriteCharValue)
 DataLength     : 0x00 (0)
Dump(Rx):
0000:04 FF 06 7F 06 00 92 FD 00                      .........
--------------------------------------------------------------------
[399] : <Rx> - 04:12:02.570
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0x06 (6) bytes(s)
 Event          : 0x0513 (1299) (ATT_WriteRsp)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0x00 (0)
Dump(Rx):
0000:04 FF 06 13 05 00 00 00 00                      .........
--------------------------------------------------------------------
[400] : <Rx> - 04:12:02.602
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0xD0 (208) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0xCA (202)
 Handle         : 0x002B (43)
 Value          : FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF
Dump(Rx):
0000:04 FF D0 1B 05 00 00 00 CA 2B 00 FF FF FF FF FF .........+......
0010:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0090:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00A0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00B0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00C0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00D0:FF FF FF                                        ...
--------------------------------------------------------------------
[401] : <Rx> - 04:12:02.613
-Type           : 0x04 (Event)
-EventCode      : 0x00FF (HCI_LE_ExtEvent)
-Data Length    : 0xD0 (208) bytes(s)
 Event          : 0x051B (1307) (ATT_HandleValueNotification)
 Status         : 0x00 (0) (SUCCESS)
 ConnHandle     : 0x0000 (0)
 PduLen         : 0xCA (202)
 Handle         : 0x002B (43)
 Value          : FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:
                  FF:FF:FF:FF:FF:FF:FF:FF
Dump(Rx):
0000:04 FF D0 1B 05 00 00 00 CA 2B 00 FF FF FF FF FF .........+......
0010:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0020:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0030:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0040:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0050:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0060:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0070:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0080:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0090:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00A0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00B0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00C0:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
00D0:FF FF FF                                        ...
--------------------------------------------------------------------

0 Ammar N over 6 years ago in reply to AlexHome

TI__Mastermind 25810 points

Have you tried debugging to see the usage of your task's stack to check for a memory overflow? I believe that is what may be causing this issue.

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Hello Ammar!

I found stack size of simple profile task when no ASSER accurs when I can try to send via SimpleProfile_SetParameter() a 200 byte nonifications every 10ms. But now none of the packages are transferred. Stacks are not crowded (see attached screenshot). What could be in this case? Maybe I need to set smaller values of TX and RX buffers? If so, how to do it right?

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Ammar, will ypu able to check my map file? I don't see any problem in it...
Thank you very much in advance !ble_simple_peripheral_cc2640r2lp_app_FlashROM_StackLibrary.zip

0 Ammar N over 6 years ago in reply to AlexHome

TI__Mastermind 25810 points

Can you share the code changes you've made? It's difficult to assist without being able to reproduce this issue on my end. Additionally, it may help to see sniffer logs (this is different than the output of the host test console).

As for the stack usage, it looks fine, as does the map file.

0 AlexHome over 6 years ago in reply to Ammar N

Intellectual 990 points

Ammar, I made some changes in code (delete large arrays) and now all works. Thanks for your help!
If you can help with another my trouble - i'll be wery glad : e2e.ti.com/.../2856381

Bluetooth®︎

Bluetooth forum

LAUNCHXL-CC2640R2: Simple_profile project with SIMPLEPROFILE_CHAR4_LEN more then 20