嗨，支持团队，
我试着测试默认闪烁和uart的例子，我不能看到终端和FTDI电缆上的任何东西
软件开发包：6.0.12.1020.2
EVK:DA1453100FXDEVKT-P
Keil:图像已加载直接从keil调试模式
1. Example:UART, Default example without change, Location \projects\target_apps\peripheral_examples\uart\
用户\u periph \u setup.h
#define UART1_TX_PORT GPIO_PORT_0
#define UART1_TX_PIN GPIO_PIN_6
#定义UART1\U RX\U端口GPIO\U端口\U 0
#定义UART1\U RX\U引脚GPIO\U引脚7
#define UART2_TX_PORT GPIO_PORT_0
#定义UART2\U TX\U引脚GPIO\U引脚6
#定义UART2\U RX\U端口GPIO\U端口\U 0
#定义UART2\U RX\U引脚GPIO\U引脚7
Pin connection on DK board as per (UM-B-119_DA14585-DA14531_SW_Platform_Reference)
Target
UART TX销
UART TX引脚DK连接
UART RX引脚
UART RX引脚DK connection
FTDI电缆
RX PIN - J2.10(P05)
TX引脚-J2.12（P07）
DA14531
第5页
连接J1.17-J2.27
第7页
Connect J1.15 - J2.28
并将FTDI电缆接地与J2接地连接。
请参考随附图片中的针脚连接。
Please let me know, If I need to change anything in SDK or any confusion in pin connection to test UART example.
2示例Blinky
用户\u periph \u setup.h
#define UART UART2
//定义UART2 Tx Pad
#if defined (__DA14531__)
#define UART2_TX_PORT GPIO_PORT_0
#定义UART2\U TX\U引脚GPIO\U引脚6
#其他
#define UART2_TX_PORT GPIO_PORT_0
#定义UART2\U TX\U引脚GPIO\U引脚4
#结束
Not able to see any print on Terminal. Didn't attach any pin cable on DK.
谢谢，
PS
嗨，品图。不是与对话的工作人员，但可能能够协助。这里有同样的工具。
1） 确认有2个COM端口从板载FTDI FT2232H双UART控制器链接到该套件。确保你的操作系统有来自FTDI网站的最新驱动程序。
2) You do not require an external FTDI serial adapter to test out these examples - the DK will enable 2 fresh COM ports and the LOWER com port on your box is the UART used for these examples for I/O. From the shared picture of your DK, it appears that you are adding an external adapter onto P0.5 & P0.7 of J2 - is this correct? This is not required. Please remove these connections as you may be causing the demo to fail due to 2 UARTs fighting for the same signals (onboard DK & your external FTDI cable).
3) Baud rate on Tera Term (or similar tool) @ 115200 bps.
4) Next load the default factory firmware using their ONLINE tools - to rule out any local compilation issues. See the attached screen grabs.
5) After using the DIALOG online firmware on your setup, you should note a blinking LED. Proceed to use Tera Term @ 115200 and your lower COM port on your box to check on the output log.
Summary:
For the attached daughter board you are showing in your posted picture - only the following fly wires are required:
连接J1.17-J2.27
Connect J1.15 - J2.28
Now, if you source the DA14531 MODULE add-on adapter, the jumper settings will change and NO FLY WIRES are necessary.
The above is from memory but fairly confident to be correct. If you still fail to get it working, post back and can check the details again once in the lab.
一旦你确认工厂的blinky固件为你工作，继续测试你的Keil编译版本。
希望这有帮助。
周一2
你好，星期二，
As per your suggestion and followed instruction given in your attached image, tested online Blink example from Dialog SmartBond Flash Programmer.
Observation:
1LED闪烁事件在Keil编译版本中为真。（请检查所附图片中的针脚连接和LED闪烁）
2在这两种情况下都没有登录UART（Online Blinky和Keil Blinky）
三。终端使用TeraTerm（Windows）、RealTerm（Windows）、Minicom（linux）进行测试，因此DA14531的UART示例代码中存在问题
软件开发包：6.0.12.1020.2
EVK:DA1453100FXDEVKT-P。
1在此之前，你可以提供样本外围应用程序，可以与外部UART需要与外部FTDI连接工作。
2外部UART至FTDI连接引脚
当做，
Pintu
1） 将外部ftdi uart电缆从该测试中完全移除。请勿将此额外的uart电缆插入电脑或本DK。
2） 仅使用USB电缆和DK，设备管理器上显示多少com端口？哪个驱动程序版本映射到每个ftdi com端口？分享这些细节的图片。
3） 确认您的终端正在使用较低的com端口并链接到此DK。DK将添加2个新的com端口到您的盒子由于FT2232H控制器。
Suggest to right click each com port, remove the port AND check the box to delete the driver for this ftdi serial port. Do this for both ports. Then remove the USB cable on the DK and download and install a fresh driver from the ftdi website. Believe latest windows driver is from 2017.
Our local office opens in about 5 hours, can check more on the details upon reaching the lab. It has to work. Since you can reflash the firmware, at least 50% of the FT2232H is working ok. Unless the uart used by the terminal is damaged due to electrical conflict, has to work.
ftdi电缆的细节是什么？电缆上有RS232收发器吗？如果是，可能是套件上的FT2232H损坏，因为信号处于3v3水平。
Is the FT2232H on the DK warm or hot to touch?
古玛
你好，星期二，
1) There is no extra FTDI cable attached to PC or DK, Only connection on DK is连接J1.17-J2.27和J1.15-J2.28
2） 我正在观察2 COM端口，“驱动程序版本2.12.14.0”
From TeraTerm
设备友好名称：USB串行端口（COM13）
设备实例ID: FTDIBUS\VID_0403+PID_6010+6&2507F1F0&0&2&1\0000
Device Manufacturer: FTDI
Provider Name: FTDI
司机日期：2016年1月22日
Driver Version: 2.12.14.0
3） 是的，仅使用较低的COM端口。
我还测试了示例“da14531-da14585-586\u changing\u advertising\u methods”以满足我的需求，并惊讶地发现它给出了登录终端，其中UART TX：将J2上的P21连接到J1上的UTX pin17Connected J1.17-J2.21. Same Driver as above detail in TeraTerm.
所以，我猜，在SDK示例中，DK板上的连接或UART配置都有问题。
嗨，品图，
Please follow the instructions in the following document strictly:
http://lpccs-docs.dialog-semiconductor.com/UM-B-117-DA14531-Getting-Started-With-The-Pro-Development-Kit/06_Your_First_DA145x_Applications/Your_First_DA145x_Applications.html
让我知道它是否有效。
And, pls tell me the screen printing of your 531 chip, for example: 531 937 AA
Br, Yibin
Pintu，这篇文章是为了确认我们的实验室设置与您的子板相同（DA14531 IC），如图28所示（根据宜宾上面的文章），使用Tera Term@115200 bps设置。确保您的跳线如图28所示。
Figure 28
http://lpccs-docs.dialog-semiconductor.com/UM-B-117-DA14531-Getting-Started-With-The-Pro-Development-Kit/06_Your_First_DA145x_Applications/Your_First_DA145x_Applications.html
亲爱的支持团队，
Same issue with same hardware.
I had a hard time trying to make the blinking test and UART working. And it appears UART is now working by connecting P1.17 to P2.26 (not P2.28).
这是正确的吗？为什么？
顺致敬意，
Pascal
Hi Pascal,
Thanks for your comments. I have replied you in this forum thread:
https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-tools/incorrect-uart-communication-pro-kit
谢谢，PM_Dialog