I can't get the external host example to work. My configuration is as follows:
Board: DA14531-00FXDEVKT-P
SDK 6.014.1114
项目:项目/ target_apps ble_examples / prox_reporter_ext/Keil_5/prox_reporter_ext.uvprojx
Project Target: DA14531
UART Configuration: followed UM-B-114, "DA14531 Deveopment Kit Pro Hardware User Manual" page 31, Table 9 & Fig. 25 jumper settings for 2-Wire UART.
Windows10 Host Application: binaries/host/windows/proximity/monitor/monitor_585.exe
Build and run prox_reporter_531 in Keil Uvision5 IDE
Run monitor_585.exe in Windows
Windows command shell is displayed and asks for COM port number.
I enter the COM port number and command shell succesfully opens port
####################################################
# DA14585 Proximity Monitor demo application #
####################################################
No command line arguments.
Enter COM port number (values: 1-65535, blank to exit): 4
Connecting to COM4
COM4 successfully opened, baud rate 115200
Waiting for DA14585 Device
Nothing else happens! Please let me know what the problem is.
Thanks
Hi OTLABS,
Thanks for posting online. Please try to use Full UART configuration – same as Figure 26: Full UART (4-wire) Connectivity. Then make sure that the correct COM port is selected. Please let me know if it is know working.
According to user_periph_setup.h header file :
UTX : P0.0
URX: P0.1
RTSN: P0.3
CTSN: P0.4
Thanks, PM_Dialog
With 4-wire UART configuration, which flow-control setting should be used for Windows COM port
none, xon-xoff or hardware?
Thanks
Hi OTLABS,
By this way, the Hardware UART Flow control (UTX, URX, RTS, CTS) is activated.
Thanks, PM_Dialog
Dialog,
Still doesn't work for me, same behavior as before. Is there any way to debug this?
Thanks
Ηι OTLABS,
Could you please check again the connections and the cables? I have ran it in my side. Same behaviour with the reporter_585.exe too?
Thanks, PM_Dialog
Still doesn't work for me. Blinky and ble_app_barebone work with my board but prox_monitor_ext doesn't work. Please see attachment showing the UART connections are consistent with UM-B-114 Fig. 26. Also, I'm using hardware flow control for the Windows COM port. What else can I check on my setup? Are there additional defines needed when building the project in Keil?
Thanks
Hi OTLABS,
Could you please perform a quick test with the prox_reporter_ext ? I have tested it in my side. No, you should not do any other changes in the project.
I checked your attached images and the wiring seems to be correct and according to Figure 26: Full UART (4-wire) Connectivity.
Thanks, PM_Dialog
prox_reporter_ext works but prox_monitor_ext still doesnt' work!
Hi OTLABS,
Finally I replicated this by using the prox_monitor_ext. You are right!
I’ve managed to run this project by changing the RTS / CTS wiring position on the Pro-DK! Please try to cross the wiring.
The configuration of the RTS / CTS was not correct and the prox_monitor_ext is configured in extended sleep mode by default, so it was unable to wake up! The prox_reporter_ext is not configured in extended sleep mode by default, so Hardware flow control is not a problem.
My apologies for the confusion and thank for your feedback.
Please let me know if the prox_monitor_ext is working after crossing the RTS / CTS.
In that project you should run thebinaries\host\windows\proximity\monitor\monitor_585.exe.
Thanks, PM_Dialog
It works after swapping RTS/CTS.
Thanks!
Hi OTLABS,
Glad that you got it working and thanks for accepting my answer. If you have any other issue, please raise a new forum thread.
Thanks, PM_Dialog