CC2642R: MTU update problem on simplelink starter APP

Hi Aslam,

I have assigned this thread to an expert to help with your queries. In the meantime, can you provide the SDK version you are working? You mentioned that the project worked previously, but now the app does not work properly with the project, were any changers made to the project? Is the same smartphone being used? Are you using iOS or Android for your smartphone? If you use an unmodified simple_peripheral OAD example, is the MTU update processed properly on the app side as well?

Best Regards,

Jan

Hi Jan,

question 1:can you provide the SDK version you are working? 

answer:simplelink_cc13x2_26x2_sdk_5_20_00_52

Question 2:You mentioned that the project worked previously, but now the app does not work properly with the project, were any changers made to the project?

Answer: The changes made in example project:

               1. MTU size increased to 251

               2.connection interval changes:min-10ms and max-12ms

               3.And my application code integrated which is independently working on different task which has nothing to do with OAD part

Question 3:Are you using iOS or Android for your smartphone?

Answer: Android

Question 4:If you use an unmodified simple_peripheral OAD example, is the MTU update processed properly on the app side as well?

Answer: Yes, its working

    Jan, I observed strange behavior which I given below:

    1. First, I am flashed OAD example project (unmodified).

    2. Then with the help of the project, I am uploaded my modified OAD project through OAD.

    3. AT this stage, my device is running on modified OAD project.

   4. Now, I am able to upload images through modified OAD project.

I observed that If I flashed my modified OAD project in a new device and tries the OAD process, MTU is not updating in app side. But If i do like the above process, App is working fine(I am able to upload images).

Please help us on resolve this issue

Regards,

Aslam

Hey Aslam,

Thanks for the extra details. If I read correctly, you only see an issue with the MTU size not updating when you flash the modified OAD project directly to the device. Is this a correct understanding? Do you have any sniffer log of this behavior?

As the unmodified example is working, can you detail the changes done in #1 and #2? How exactly where those modifications made?

Hi Ammar,

Thanks for your reply.

If I read correctly, you only see an issue with the MTU size not updating when you flash the modified OAD project directly to the device. Is this a correct understanding? 

Yes, absolutely correct.

 Do you have any sniffer log of this behavior?

No, I am not having sniffer log. Can you give me the procedure to take sniffer log?

As the unmodified example is working, can you detail the changes done in #1 and #2? How exactly where those modifications made?

Both changes were made through sysconfig tool.

MTU size -61(actual)/251(changed value)  [PDU-4 =MTU]

Connection interval:

actual -->min:500, max:1000

changed value ---->min:10,max:12

Regards,

Aslam

Hey Aslam,

I don't see why the modifications you made in particular would lead to such an issue.

To rule out an issue with the mobile application, can you perform the test using an additional launchpad (compiled with host_test) and connect using BTOOL?