I wanted to try all the sample codes under dk_apps\keil_projects just to verify and use it as a starting point for our new project. As i mentioned above, only two of them (template and throughput_eval) responded on my simple BLE app on my Android phone which sniff for BLE advertises.
For a detail on my setup, i have one BASIC DK that is setup to use UART; then i got two BLE module boards made by our vendor with your BLE chip, which is interfaced via J-link OB.
All these boards works OK with template and throughput_eval_peri from keil_projects, but why proximity and prod_test doen't?
For proximity, i use the reporter_fh for i don't have the USB dongle.
The proximity reporter_fh should work. Some of the sample apps enter either deep sleep or extended sleep which conflicts with the J-Link debugger. You have to stop the debugger for the device to start advertising. You can also disable (undefine) both sleep modes in the da14580_config.h file of each project, this will allow you to also use the debugger.
As I've said at my other post, thanks for your help, now my phone app can see the BLE advertise.
Btw another question, for the proximity monitor, i only got a BASIC DK, can i use this together with the the PC app? or is the PC app only designed to work only with the USB dongle? But if it does work with BASIC DK, which keil_project should i use, is it the monitor_fe?
I tried this as proximity monitor: BASIC DK using monitor_fe, then run PC app. Enter the appropriate port no. Then it only stays at "Waiting for DA1458x Device", which device does it wait for, the monitor or the reporter? Also, is the monitor_fe doable with BASIC DK + host_proxm_sdk.exe PC app?
You are using the right project (reporter_fe). The indication "Waiting for DA1458x device" indicates that the PC host is waiting for serial port activity from the Dev Kit.
Here are a list of things to look out for:
1. Selecting the right COM port on your PC is crucial
2. Make sure that the jumpers on the Dev Kit are set to UART
3. The PC Host must be started before you load the software onto the Dev Kit
Thanks for these list and yes I've considered these steps. But the fix was still the same as my previous post, i disabled sleep configuration and now i get the expected result, thanks! :)
Hi Geo
Please refer to documenthttp://support.dialog-semiconductor.com/basic-dev-kit-um-b-025-user-manu...。你能请explain more detial for project like proximity not working?
Regards
FH
Hi FH,
I wanted to try all the sample codes under dk_apps\keil_projects just to verify and use it as a starting point for our new project.
As i mentioned above, only two of them (template and throughput_eval) responded on my simple BLE app on my Android phone which sniff for BLE advertises.
For a detail on my setup, i have one BASIC DK that is setup to use UART; then i got two BLE module boards made by our vendor with your BLE chip, which is interfaced via J-link OB.
All these boards works OK with template and throughput_eval_peri from keil_projects, but why proximity and prod_test doen't?
For proximity, i use the reporter_fh for i don't have the USB dongle.
BR,
Geo
Hi Geo,
The proximity reporter_fh should work. Some of the sample apps enter either deep sleep or extended sleep which conflicts with the J-Link debugger. You have to stop the debugger for the device to start advertising. You can also disable (undefine) both sleep modes in the da14580_config.h file of each project, this will allow you to also use the debugger.
Hi MHv,
As I've said at my other post, thanks for your help, now my phone app can see the BLE advertise.
Btw another question, for the proximity monitor, i only got a BASIC DK, can i use this together with the the PC app? or is the PC app only designed to work only with the USB dongle?
But if it does work with BASIC DK, which keil_project should i use, is it the monitor_fe?
I tried this as proximity monitor:
BASIC DK using monitor_fe, then run PC app. Enter the appropriate port no.
Then it only stays at "Waiting for DA1458x Device", which device does it wait for, the monitor or the reporter?
Also, is the monitor_fe doable with BASIC DK + host_proxm_sdk.exe PC app?
Thanks in advance.
BR,
Geo
Hi Geo,
You are using the right project (reporter_fe). The indication "Waiting for DA1458x device" indicates that the PC host is waiting for serial port activity from the Dev Kit.
Here are a list of things to look out for:
1. Selecting the right COM port on your PC is crucial
2. Make sure that the jumpers on the Dev Kit are set to UART
3. The PC Host must be started before you load the software onto the Dev Kit
I hope that helps you move forward.
Hi MHv,
Thanks for these list and yes I've considered these steps. But the fix was still the same as my previous post, i disabled sleep configuration and now i get the expected result, thanks! :)
BR,
Geo
Glad to hear that you got it working.