Throughput ATT MTU Test stuck after "Notifications enabled"

[nothingmuchyou]

Hi, 

I am running the example ble_app_att_mtu_throughput with the nRF5 SDK on two nRF52840-DK dev kits. I have flashed both dev kits with S140 soft devices prior to flashing the program. I am using the armgcc toolchain. 

The problem I am seeing is that the test gets stuck after the printout "Notifications enabled". On the dev kit side (both the tester and responder) we are stuck with LED2 (this is 

BSP_BOARD_LED_1 in the SDK, LED2 on the PCB silk screen) lit up on both dev kits, which I believe is the LED that indicates that the test is ready to go. 

Can someone help point where to debug? I noticed that one of the flags in is_test_ready is probably not getting set but I don't know why. 

Thank you!

[Simonr]

Hi

Have you followed the steps for setup and testing in the example documentation? After this message I think the device is waiting for the other DK, so I don't think it is stuck, but rather waiting. Please make sure that you've put one DK in responder mode and one in the tester mode.

Have you made any changes to the example project at all?

Best regards,

Simon

[nothingmuchyou]

Yes I followed the entire setup, and no I didn't change anything in the example project. I don't think it's waiting, because LED2 is lit up. LED1 seems to be the waiting LED. I pressed button 3 and button 4 on each board to put them in tester and responder mode. 

[Simonr]

Can you also provide the logging of the other DK? Does it "stop" in a similar place? I will run a test on my day on Monday, when I am in office and have the required amount of DKs available.

Best regards,

Simon

[nothingmuchyou]

Do you mean switch the roles of tester and responder and see if I get the same result?

[Simonr]

Not exactly. It should be possible to see the log from the responder as well as the tester. I just tested the throughput example in a fresh version of the SDK v17.0.2, and I was able to run it successfully. Here is a screenshot of both tester and responder. Can you also provide a log of your responder so we can see if it stops at the same point as well? If so, I think you should open an RTT viewer to see the debug log on your devices. The test should run by itself as long as you have an active responder and type run in the tester terminal.

Best regards,

Simon