Throughput test coded PHY

RE: Throughput test coded PHY

Vidar Berg — Wed, 31 Jul 2019 08:07:20 GMT

Yes, this looks correct. However, it was not the error I expected to see. Softdevice asserts are quite rare and are usually caused by erroneous code in the app. Please try with the pre-compiled hex attached below and see if you get the same result. I have not been able to replicate this assert here.

devzone.nordicsemi.com/.../ble_5F00_app_5F00_att_5F00_mtu_5F00_throughput_5F00_pca10056_5F00_s140.hex

RE: Throughput test coded PHY

mercimek — Mon, 29 Jul 2019 14:15:20 GMT

Thank you for your answer, I think I set it as you told and now I have a more specific problem. What do you think about it?

RE: Throughput test coded PHY

Vidar Berg — Mon, 29 Jul 2019 08:42:24 GMT

Your screenshot shows the available build configurations, but it does not show what build flags each of them has. Did you find the list of Preprocessor Definitions as shown in my previous reply?

RE: Throughput test coded PHY

mercimek — Mon, 29 Jul 2019 08:20:03 GMT

And this is one time I got no error but test didn't established

RE: Throughput test coded PHY

mercimek — Mon, 29 Jul 2019 06:50:20 GMT

I think it was already defined. Am I right?

RE: Throughput test coded PHY

Vidar Berg — Mon, 29 Jul 2019 06:44:16 GMT

No, your screenshot indicates that the project is compiled without the debug flag. Please try to set it manually in project options (common) -> Preprocessor -> Preprocessor Definitions:

RE: Throughput test coded PHY

mercimek — Mon, 29 Jul 2019 06:29:27 GMT

Yes I did, as you can see from the first image's Debug terminal, I was debugging and at the same time I was using putty. After the first image I rebuilt the code and with the Debug target, I was sent to the code you can see from next two screenshots

RE: Throughput test coded PHY

Vidar Berg — Mon, 29 Jul 2019 06:05:37 GMT

Hi, looks like the "DEBUG" is not defined based on your screenshots. Did you re-build and debug with the Debug target?

RE: Throughput test coded PHY

mercimek — Mon, 29 Jul 2019 05:50:07 GMT

Hello, it's not giving anything other than fatal error. Here is the debug and putty screen. And it sends me to this function

RE: Throughput test coded PHY

Vidar Berg — Fri, 26 Jul 2019 06:19:15 GMT

Hello, The screenshot below shows where you can select the build target in SES. You should still use putty to control the test.

RE: Throughput test coded PHY

mercimek — Fri, 26 Jul 2019 06:11:32 GMT

Hello, I'm setting Coded phy from putty so I didn't figure out how to debug the system from SES. Can you please explain it a little bit more?

RE: Throughput test coded PHY

Vidar Berg — Thu, 25 Jul 2019 12:34:39 GMT

Hi,

I didn't manage to reproduce it here. I used the sample from SDK 15.3.0 and two nRF52840 dev kits. Could you try to build the project with 'DEBUG' in the list of preprocessor symbols(or select Debug target if you use SES)? It will give a more detailed crash log, not just "Fatal error".

Here is another project that should let you measure throughput with coded PHY as well: https://devzone.nordicsemi.com/f/nordic-q-a/47073/general-questions-about-notifications-low-level-ble-packets-and-softdevice-phy-connection-interval-connection-event-length-att-mtu-and-dle/186303#186303

Best regards,

Vidar