Bidirectional Communication between Android DSPS and DSPS v5.150.2 Sample Code

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
3 posts / 0 new
Last post
Fri, 2017-06-23 13:35
#1
gturnipseed720
Offline
Last seen:3 years 10 months ago
Joined:2017-06-06 15:08
Bidirectional Communication between Android DSPS and DSPS v5.150.2 Sample Code

Hi there. I'm trying to get your SPS sample code to work correctly, but I'm having trouble. I'm using the DA1458x_DSPS_v_5.150.2 sample code downloaded from your website loaded onto a DA14580 base (not pro) dev kit, and I'm talking to the DSPS app on my Android phone. I can get the dev kit to broadcast, and the phone can pair to it. I can then type on the computer and see the text show up on my phone; however, when I type on my phone, no text shows up on the computer. Am I doing something wrong, or is the sample code not designed to do that?

Thank you,
-Greg Turnipseed

Device:
DA14580
Fri, 2017-06-23 16:43
MT_dialog
Offline
Last seen:2 months 2 weeks ago
Staff
Joined:2015-06-08 11:34
Hi gturnipseed720,

Hi gturnipseed720,

The sample code is designed to emulate a serial port over USB, that means that you can transfer data from the phone application to your windows pc and from the PC to the phone application. There is a User Manual (UM-B-038:User Manual for Dialog Serial Port Profile.pdf) that describes the neseccary connections for the basic kit in order to properly work with the DSPS example, in short i will describe a few key configurations below:

  • You need an FTDI cable in order for the DSPS to properly work with the basic kit, the UART port used on the basic kit is from the Atmel MCU on board that it is used as the JTAG, and the hw flow control is not properly implemented in the SEGGER driver.
  • The reference design is preconfigured to work in sleep mode, thus it requires to operate with hw flow control, so the RTS/CTS signals should be connected.
  • Make sure that the terminal that you are using (Putty, Hercules, Tera Term, etc) has the RTS/CTS functionallity enabled otherwise you wont be able to transfer data.

Thanks MT_dialog

Accepted answer
Fri, 2017-06-23 21:25
gturnipseed720
Offline
Last seen:3 years 10 months ago
Joined:2017-06-06 15:08
谢谢你的帮助!The

谢谢你的帮助!通知用户手册ative (I didn't know it existed before), and after I shorted RTS and CTS together, I started getting bidirectional communication. Thank you very much.

-Greg Turnipseed