Hi Dialog,
我们拥有现有的设计，基于DA14583，使用DSP，如UM-B-038所示，UART Comms In / Out是H / W流量控制在115200波特。通信始终从DA14583到自定义Android应用程序，其中应用程序始终启动与广告DA14583的连接。
We are now switching to the Inventek DA14585 based module and latest DSPS as detailed in UM-B-088. Initial tests have not been very successful. We have comms in 1 direction (Android application to DA14585 and out of the UART TX) but data into the DA14585 does not seem to be transmitted and the h/w flow control stops.
我们没有修改自定义应用程序，并希望您的意见请。
1.您是否期望基于UM-B-038的现有Android应用程序与最新的DSPS和DA14585无缝工作（GPIO分配当然适合H / W）
2. Has w/h flow control sense changed between versions ?
3. Are there any default compile switches that should be disabled to allow compatibility with existing android applications ?
4. Is there any version migration document I have missed?
任何帮助都有很大欣赏，编译交换机和配置的数量很大，我们正在达到这个工作的时间压力，我们认为与GPIO适应的简单编译。
非常感谢
Garry Jackson
Hi Delta-GRJ,
Thanks for your question online. Please find my comments below :
请您注明您是否能够与您的自定义移动应用程序连接？只有问题是DA14585无法通过BLE将UART传入数据传输？如果是，我假设这是由于UART错误配置。您是否使用了我们的任何Pro-DK？
谢谢，PM_DIALOG.
Hi PM_Dialog,
感谢您的回复，我们希望有助于以下内容：
1. I am using Keil project for DA14585 DSPS Device with extended sleep and remote config enabled.
2. I am using a new custom development PCB using the Invertek module (585 based) which has the UART taken to pads for hooking up to an external existing board I designed a while ago. The external board has a STM32 connected to a DA14583 which was running DSPS (UM-B-038 based). I removed the DA14583 linking TX,RX,CTS,RTS to the new board with the invertek module. The DA14585 UART signals, as defined in user_periph_setup.h are:
#define gpio_uart1_tx_port gpio_port_0 //（da到stm）
#define GPIO_UART1_TX_PIN GPIO_PIN_2
#define GPIO_UART1_RX_PORT GPIO_PORT_0
#define gpio_uart1_rx_pin gpio_pin_3.
#define GPIO_UART1_RTS_PORT GPIO_PORT_0
#define gpio_uart1_rts_pin gpio_pin_1
#define GPIO_UART1_CTS_PORT GPIO_PORT_0
#define GPIO_UART1_CTS_PIN GPIO_PIN_5
该GPIO配置由对话框SmartConfig应用程序（我可以连接到），我也将DA Smartterminal挂钩Tx / Rx一起使用，并在键入各个CAHRACTERS时确认数据循环。
3.我可以与DA14585确定的BLE连接.-从自定义应用程序和对话框工具中。
4.我可以从我的自定义Android应用程序发送到DA14585，看看UART上的30个字节数据包被STM32正确解释。
5. 1S在自定义应用程序中到达STM32的30个字节之后，STM32将开始在尺寸为100ms延迟的大小的大小发送DataBucks，始终等待DA到下RTS，并且在其升高时始终暂停在每个字节上发送。
6.我已经挂钩了一个逻辑分析仪，可以看到DA推出30个字节RX有效负载，然后1S稍后开始STM32开始推出其数据。DA保持低电平为约21ms，将其提高55US，然后将其降低到另一个21ms（在此期间从STM32发送数据）。在此之后，DA提升RTS，并且剩余连接的状态仍然存在。这通常代表115200波特的约420-480个字符。注意RTS的55us升高似乎是来自STM32的中音字节，因此这并不正确。
7.一些微小的变化来支持Invertek DA实施，这些我认为没有与此问题有关。
我同意它感觉像UART握手问题，但逻辑分析仪的交互似乎如预期的（除了阻止40ms左右推动的任何数据）。我不知道这个DSP的当前版本是否与历史悠久的Android应用程序兼容。
I will review the docs you signposted but any obvious issues please advise. This is, as always, time critical for me.
Many thanks
Garry J
Hi PM_Dialog
更多信息，我希望您能与我以前的帖子进行审核，并为我们提供其他建议：
The core question we had, we have now investigated and answered and confirm that the latest DSPS 6.150.4.50 will work with historical Android apps, specifically thouse developed using DSPS 5.150.2 (SDK for DA14583) - however I continue to have a problem with one specific custom application that only works with DSPS 5.150.2. This application connects as expected but always presents handshaking as I previously described, ie. RTS from DA is set to low for 21mS and data starts from the UART into the DA but after 200-250 bytes it raises for 55uS then lowers again for a further 21mS before returning hi for the remainder of the connection blocking all data to send over BLE.
I have tried delaying the inbound data after the connection is established without effect.
如果版本与我可以调试此操作的任何方式，请您提出建议。我没有Android源或访问始发的Android开发人员。
Is this the only way to get technical support from Dialog ?
Many thanks
Garry Jackson
Hi PM_Dialog
更多信息，我希望您能与我以前的帖子进行审核，并为我们提供其他建议：
The core question we had, we have now investigated and answered and confirm that the latest DSPS 6.150.4.50 will work with historical Android apps, specifically thouse developed using DSPS 5.150.2 (SDK for DA14583) - however I continue to have a problem with one specific custom application that only works with DSPS 5.150.2. This application connects as expected but always presents handshaking as I previously described, ie. RTS from DA is set to low for 21mS and data starts from the UART into the DA but after 200-250 bytes it raises for 55uS then lowers again for a further 21mS before returning hi for the remainder of the connection blocking all data to send over BLE.
I have tried delaying the inbound data after the connection is established without effect.
如果版本与我可以调试此操作的任何方式，请您提出建议。我没有Android源或访问始发的Android开发人员。
Is this the only way to get technical support from Dialog ?
Many thanks
Garry Jackson
嗨加里杰克逊，
谢谢你的评论。让我在内部检查这个，我会尽快回复你。
谢谢，PM_DIALOG.
Hi PM_Dialog
Its been 11 days do you have any comments internally that may help with this issue ?
我进一步调查了，另外证实了最新的DSP 6.150.4.50与我的3个现有的自定义Android应用程序中的2个合作，那么发生了第一轮我的测试与不起作用的应用程序。亚博国际官网平台网址
第三个应用程序是很重要的,perfe工作ctly well with the original DSPS on the '583. From looking at the limited debug available via android studio (remembering we do not have the source) I can not see an obvious difference between this app working with my old hardware and not working with the new hardware. It looks as though the connection parameters are the same and registered notification of RX is setup correctly but nothing is ever sent to it. All I can think is a difference in startup/setup that on connection is preventing UART RX and BLE TX ?
Please advise, we need confidence to switch to the '585 for production as soon as possible.
Thanks
Garry J
Hi Delta-GRJ,
我为延迟道歉。这3rd.您开发的自定义应用程序？此应用程序是否可免费下载？
由于它正在使用我的3个现有自定义Android应用程序中的2个，因此我假设特定问题与移动应用程序有关。亚博国际官网平台网址
Would it be possible to use a BLE Sniffer tool, and share a sniffer capture, so that we can understand what is happening over the air?
Could you please test this also with the Dialog DSPS mobile application? It is available both for Android and iOS. You can also find the source code In the DSPS portal:
//www.xmece.com/products/dialog-serial-port-service-dsps
谢谢，PM_DIALOG.
Hi PM_Dialog
The custom application is not public and all applications relate to our hardware use case, which is sending 2K datablocks over the connection from DA14585 to the Android applications. This is in response to the application sending commands to our board (BLE->DA14585->STM32) to initiate the transfer. In each the failure I can indeed see the command arrive and the STM32 begin to send data to the DA14585 but this data never seems to get pushed over BLE.
我会调查我是否可以使用BLE数据包嗅探器捕获。看起来没有简单的答案，虽然问题可能是在这个失败的Android应用程序中，它是突出显示这种移动应用程序缺陷的DSP项目/平台的变化。我希望它将是一个已知的问题和序列/时序相关。
Thanks
Garry J