Windows 10 PC <- BLE(DSPS) ->- UART(Rx/Tx引脚2_3和2_4)->CP2102 UART to USB bridge < USB->我使用c# . net应用程序在PC机和DA14580之间建立了连接,能够成功地发送和接收数据。
问题是,为了打开传感器和发送/接收数据/从它,我需要先打开传感器的串口。
有人知道这是否可行吗?如果可行,我会怎么做?< / p > < p >我用Da1458x_DSPS_v_5.150.2 < / p > < p >谢谢< / p > < / div > < / div > < / div > < div class =”字段field-name-field-forum-keywords field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >关键词:,< / div > < div class = "字段条目" > < div class =”field-item甚至“> < a href = " / resource-keywords / basic-da14580-dsps”typeof = " skos:概念”属性= " rdfs: label skos: prefLabel”数据类型= " " >基本DA14580需求方< / > < / div > < / div > < / div > < div class =”字段field-name-field-device field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >设备:,< / div > < div class = "字段条目" > < div class =”field-item甚至“> < a href = " / forum-post-device / DA14580”typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">DA14580 .
有没有办法减少通知之间的延迟?< / p > < p >谢谢< / p > < / div > < / div > < / div > < div class =”字段field-name-field-forum-keywords field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >关键词:,< / div > < div class = "字段条目" > < div class =”field-item甚至“> < a href = " / resource-keywords / basic-da14580-dsps”“=“skos:概念”属性=“rdfs: label skos: prefLabel”基本数据类型= " " > DA14580需求方< / > < / div > < / div > < / div > < div class =”字段field-name-field-device field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >设备:,< / div > < div class = "字段条目" > < div class =”field-item甚至“> < a href = " / forum-post-device / DA14580”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " > DA14580 < / > < / div > < / div > < / div >
成功安装Keil v5,并按照UM-B-048 Getting started文档中的描述运行blinky测试。
然后尝试运行DSPS (da14580_dsps_3.150.2 __13_2_2015),从我的分发服务器获得应用程序说明(v1.3)。
然后麻烦来了,当我试图遵循§8.4中的步骤:OK(0错误(s), 3警告(s)) < br / > FTDI RS232电缆相连,加上定期的USB线指示§8.1 < br / >在启动调试会话时,一个“不”Cortex-M SW设备发现弹出< br / >和日志:< br / >加载“…\ \ DA14580_DSPS_3.150.2 \ \ dk_apps \ \ keil_projects \ \ sps \ \ sps_device_K5 \ \ \ \ sps_device对象。axf"
* JLink Info: Device "DA14580" selected。
设置JLink项目文件为"…\DA14580_DSPS_3.150.2\dk_apps\keil_projects\sps\sps_device_K5\JLinkSettings.ini"
* JLink Info: Device "DA14580" selected。
JLink info:
------------
DLL: V5.02f, compiled Oct 2 2015年10月2日20:51:34
Firmware: J-Link OB-SAM3U128 V1 compiled 2015 Aug 28 19:26:23
Hardware: V1.00
S/N: 480055335
Error: Flash Download failed - Target DLL has been cancelled
Flash Load finished at 10:39:47
问题:如果我像fig14中那样更改跳线,SAM和DA之间就没有任何连接了,那么我如何通过串行链接而不是JLink下载hex文件呢?或者我错过了什么?
So I also tried with SmartSnippets:
This time the COM port opened is the serial link, but the reset button has no effect!!
[INFO @15-12-09 10:50:41] Read 19480 bytes from file…\DA14580_DSPS_3.150.2\dk_apps\keil_projects\sps\sps_device_K5\Objects\sps_device.hex. txt . txt
[INFO @15-12-09 10:50:41] COM40端口连接成功打开。
[INFO @15-12-09 10:50:41] start download procedure…
[ACTION @15-12-09 10:50:42] Please press the hardware reset button on the board to start the download process.
[ERROR @15-12-09 10:50:57] Timeout: Reset signal not detected for more than 16000 msecs.
[INFO @15-12-09 10:50:57] Successfully disconnected from port COM40.
[INFO @15-12-09 10:50:57] Failed downloading firmware file to the board.
What's next? I went through several forum threads, found several customers able to connect, and some not, but can't figure out the right/bad conditions.
BTW, I modified nothing in the original source code, and da14580_config.h defines CFG_UART_HW_FLOW_CTRL. Should I change that?
Thanks.
PS:
SmartSnippets v3.9 32b
And Keil Info:
IDE-Version:
µVision V5.17.0.0
Copyright (C) 2015 ARM Ltd and ARM Germany GmbH. All rights reserved.
Tool Version Numbers:
Toolchain: MDK-Lite Version: 5.17
Toolchain Path: C:\Keil\ARM\ARMCC\Bin
C Compiler: Armcc.exe V5.06 update 1 (build 61)
Assembler: Armasm.exe V5.06 update 1 (build 61)
Linker/Locator: ArmLink.exe V5.06 update 1 (build 61)
Library Manager: ArmAr.exe V5.06 update 1 (build 61)
Hex Converter: FromElf.exe V5.06 update 1 (build 61)
CPU DLL: SARMCM3.DLL V5.17
Dialog DLL: DARMCM1.DLL V1.12.0.0
Target DLL: Segger\JL2CM3.dll V2.99.16.0
Dialog DLL: TARMCM1.DLL V1.9.0.0