Reply not received while sending a create_db message in the empty_template_ext project

Hi tsgowtham,

My apologies but for me it’s nor clear what is the issue. Could you please clarify your question?

If I understood correctly, you would like to print debugging messages over UART? If yes, please try to use the arch_printf() function. Take a look at CFG_PRINTF macro in da1458x_config_basic.h header file.

Thanks, PM_Dialog

Hi tsgowtham,

My apologies - it was a misunderstanding in my side. Let me check it and I'll get back to you..

Thanks, PM_Dialog

Hi tsgowtham,

My recommendation would be to follow the pxp_reporter_ext in order to add the custom profile. In the pxp_reporter_ext project, you can follow how the proximity Monitor and the DISC profiles are enabled. Then, you should run it in debug mode, try to send to send the appropriate commands over UART and check is the app_custs1_create_db() is executed. Please add a breakpoint there and check if that function is getting triggered.

Thanks, PM_Dialog

Hi tsgowtham,

My apologies – it was a typo, I meant the prox_reporter_ext project of the SDK.

Let me ask you some questions in order to understand the steps that you have already done :

In case of prox_reporter_ext project, the custom 1 profile is not included – only the proximity Monitor and the DISC profiles are enabled.

To do so, you modified the pro_reporter_ext project and added the custom 1 profile.

In this step, if I understood correctly there is not any problem - the app_custs1_create_db() is executed correctly.

Did you add a break point to verify it?

So, in case of empty_template_ext, you have followed exactly the same steps in order to include the custom1 profile. Is that correct?

However, the app_custs1_create_db() is never executed – (this is the problem). Please correct me if it is anything wrong.

Can you please run the empty_template_ext project in debug mode and add a break point in that function? What is the behavior? Does the break point hit, or does the firmware get stack anywhere (WDOG, NMI , any assertion etc) ?

Thanks, PM_Dialog

Hi tsgowtham,

Just to summarize : In case of prox_reporter_ext, did you add a BKPT into the app_custs1_create_db() ? Can you please indicate if the app_custs1_create_db() is getting triggered?

If yes, can you verify the same into the empty_template_ext() ?

I assume that the app_custs1_create_db() should be called. Would it be possible to share both projects with the modifications you have done?

Thanks, PM_Dialog

Hi tsgowtham,

Apologies for my late response. Just run your projects, so find below my comments :

In case of prox_reporter_ext, the project is running properly ( as you have already mentioned ) – the device starts advertising - I can connect and see the PROXR, DISS , SPOTAR and CUSTS1 profiles. I am running both \binaries\host\windows\proximity\reporter\host_proxr_sdk.exe and your provided application.

In case of empty_template_ext, the device cannot start advertising neither with the usage of SDK host_proxr_sdk.exe nor your provided Windows application.

你能在你身边请检查如果是开始吗advertising?

This can be replicated in the prox_reporter_ext if you comment out the following includes in the user_profiles_config.h :

#include "proxr.h"

#include "diss.h"

#include "spotar.h"

This is expected because the host_proxr_sdk.exe send GTL commands for the creation of the aforementioned profiles too. If you include all the above profiles in your provided empty_template_ext project, you will see that the device will start advertising and the Custom 1 profile is also included.

If you are interested in including only the Custom 1 profile, then you should modify the host_proxr_sdk.exe by yourself and send the GTL commands only for the specific profile. This is not a straight forward implementation because you should remove many GTL commands. For example you could use a logic analyzer on the UART signals and check what commands you should send or not. To do so, my suggestion would be to base your project on the prox_reporter_ext.

Thanks, PM_Dialog