Proximity Application sample not working

Hello Aritec, in the next couple of days we are releasing a new SDK which has an improved proximity applciation included. This will be available from the resources section of the support site. The SDK will itself be a lot cleaner and more user friendly. This new SDK supports a new ROM revision of the DA14580 which we have released. I would suggest that for any future develoment, migrate to the new ROM revision and use the new SDK. (You can use the same motherboard, we just need to swap out your daughter board - I will contact you to arrange that). Best Regards, JE_Dialog

Dear all,

I am playing with full hosted proximity reporter on the evaluation board. However, I found something really strange.
In da14580_config.h, there are four lines:
#define CFG_PRF_BASS 1
#define CFG_PRF_DISS 1
#define CFG_PRF_PXPR 1
#define CFG_PRF_FMPL 1

I assume they are switches used to create profile database on evaluation board. But when I was going to disable any of them using #undef, I noticed that Android APPs always found these seven services there:
GENERIC ACCESS SERVICE
GENERIC ATTRIBUTE SERVICE
DEVICE INFORMATION
LINK LOSS
IMMEDIATE ALERT
TX POWER
BATTERY SERVICE

Do you know what's the reason? Thanks!

Let me reshape my question: in the proximity reporter application, if I modify
#define CFG_PRF_DISS 1
to this:
#undef CFG_PRF_DISS,

will DEVICE INFORMATION be created in database? If I am using an Android APP to list all BLE services running on evaluation board, will the APP see that Device Information Service?

Hi,

The issue you are having has to do with the fact that the DA14580 shuts off the M0 microcontroller as it enters sleep mode. This causes the J-Link to halt execution of the application. The debugger cannot be used while sleep mode is enabled. There is a configuration file for each project named da14580_config.h in which you can change the sleep mode behavior. Originally it is set like this:

Hello all,
I would like to known what happend with reporter_fe application in my DA14580 board. I have loaded the application in board ( Debug + Run + Debug to start) but when I search the device with the monitor application in USB-Dongle, it founds anything. This need a different configuration of Jumpers? How can I see if the reporter is correctly running?
Thanks you very much, I hope your answers.

Best regards,
JV

Hi JE_Dialog,
I tried the Proximity example in the new SDK 3.0.6, but the problem wsa still there.
Do you have any idea what was happened?

Beast regards,

I tried new SDK 3.0.6, but got the same messages on the windows terminal.
Here was the same message:

####################################################
# DA14580 Proximity Monitor demo application #
####################################################
No cmdline arguments.
Enter COM port number (values: 1-65535, blank to exit): 30
Connecting to COM30
COM30 succesfully opened, baud rate 115200
Waiting for DA14580 Device

...

Hi Xup,

Let's isolate the two issues for a bit.If you load the reporter_fh onto the devkit, (build/start debug/run/stop debug), can you see the device advertising using a smart phone? For iOS use the LightBlue app, for Android (4.3 or above) use BlueLoupe. Both tools should show you a device named DA1458x.

If you can see the device advertising, disconnect the debugger from the devkit and then build/debug/run the monitor_fe_usb on the USB stick. If you diconnect and reconnect the USB stick with the Windows Device Manager open, you can see which serial port to use - just to make sure.

是的,我跟着the procedures of the document "UM-B-010 - Proximity application.pdf" just like you said, but still cannot get it work.
I found there are some posts about this issue in the forum. Here are the lists:
http://support.dialog-semiconductor.com/proximity-application-not-workin...
http://support.dialog-semiconductor.com/proximity-reporter-not-working-help

Any further suggestion?

Hi Xup,

I need to know at what step you are stuck. Did you, or did you not, see the proximity reporter_fh advertising using your smart phone?

Hi MHv_Dialog,
I did every steps you mentioned, and I can see proximity reporter_fh advertising using your smart phone.
I also disconnected the debugger from the devkit and then build/debug/run the monitor_fe_usb on the USB stick. I diconnected and reconnected the USB stick with the Windows Device Manager open, and I can see serial port.
I entered the port number in the host application, but got nothing.

Here is the example of host application message:
####################################################
# DA14580 Proximity Monitor demo application #
####################################################
No cmdline arguments.
Enter COM port number (values: 1-65535, blank to exit): 30
Connecting to COM30
COM30 succesfully opened, baud rate 115200
Waiting for DA14580 Device

SDK 5.0.4\DA1458x_SDK_5.0.4\DA1458x_SDK\5.0.4\projects\target_apps\ble_examples\prox_monitor_ext

I'm test Demo Kit Basic .
It was working in the Kit with Keil ( Start / Stop Debug Session).
J5 Jump : 25-26 , 27-28 , P0_4,P0_5,P0_6,P0_7
Keil-Flash-Options for Target->Debug->"J-Link/T-TRACE Cortex" (SW)
PC: host_proxm_sdk.exe <----->"S" keyinput ===> " Display All Device Information"

*------------------------------------------------------------------------------------------------------*
J5 Jump : P0_4,P0_5,P0_6,P0_7
Next : Smartsnippets > Firmware > with J-TAG Mode -> SPI Writing
PC: host_proxm_sdk.exe <----->"S" keyinput ===> " Don't Display Anything"
Why It is ?
What the problem? Can you tell me How to do?

#define HW_CONFIG (2) : GPIO Setting Above----

#define UART1_TX_GPIO_PORT GPIO_PORT_0
#define UART1_TX_GPIO_PIN GPIO_PIN_4

#define UART1_RX_GPIO_PORT GPIO_PORT_0
#define UART1_RX_GPIO_PIN GPIO_PIN_5

#define UART1_RTSN_GPIO_PORT GPIO_PORT_0
#define UART1_RTSN_GPIO_PIN GPIO_PIN_6

#define UART1_CTSN_GPIO_PORT GPIO_PORT_0
#define UART1_CTSN_GPIO_PIN GPIO_PIN_7