1 year ago
无法测试闪烁和UART外围示例
Posted bypintu0分 8 repliesHi Support Team,
我试图测试默认闪烁和uart示例，我无法在终端和FTDI电缆上看到任何内容
SDK:6.0.12.1020.2
EVK:DA1453100FXDEVKT-P
Keil:Image loaded 直接从keil调试模式
1. Example:UART, Default example without change, Location \projects\target_apps\peripheral_examples\uart\
user_periph_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_PIN GPIO\u引脚7
#define UART2_TX_PORT GPIO_PORT_0
#define UART2_TX_PIN GPIO_PIN_6
#define UART2_RX_PORT GPIO_PORT_0
#定义UART2_URx 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 connection | UART RX引脚 | UART RX引脚DK connection |
|---|---|---|---|---|
| FTDI cable | RX PIN - J2.10(P05) | TX引脚J2.12（P07） | ||
| DA14531 | 第5页 | 连接J1.17-J2.27 | 第7页 | Connect J1.15 - J2.28 |
并将FTDI电缆接地接J2 GND。
请参阅附图中的插脚连接。
Please let me know, If I need to change anything in SDK or any confusion in pin connection to test UART example.
2.闪烁示例
user_periph_setup.h
#define UART UART2
// Define UART2 Tx Pad
#if defined (__DA14531__)
#define UART2_TX_PORT GPIO_PORT_0
#define UART2_TX_PIN GPIO_PIN_6
#其他
#define UART2_TX_PORT GPIO_PORT_0
#define UART2_TX_PIN GPIO_PIN_4
#endif
Not able to see any print on Terminal. Didn't attach any pin cable on DK.
谢谢，
PS
| Attachment | Size |
|---|---|
| DA14531DK_Connection.pdf | 749.66 KB |
1 year ago
嗨，蒙2，
As per your suggestion and followed instruction given in your attached image, tested online Blink example from Dialog SmartBond Flash Programmer.
Observation:
1.LED闪烁事件，Keil编译版本为真(请检查插脚连接，并在附图中显示LED闪烁）
2.两种情况下均不登录UART（在线闪烁和Keil Blinky）
3.终端测试采用了Terterm（Windows）、RealTerm（Windows）、Minicom（linux），因此在DA14531的UART示例代码中存在问题
SDK:6.0.12.1020.2
EVK:DA1453100FXDEVKT-P。
1.在这一工作之前，您可以提供一个示例外围应用程序，该应用程序可以与外部UART一起工作，而外部UART需要连接外部FTDI。
2.外部UART至FTDI连接引脚
当做，
Pintu
| Attachment | Size |
|---|---|
| DA14531 U J1.15 U J2.28 U J1.17 U J2.27.pdf | 94.42 KB |
1 year ago
1） 从本测试中完全卸下外部ftdi uart电缆。请勿将此额外的uart电缆插入您的PC或此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.
What are the details of the ftdi cable? Is it with RS232 transceiver onboard the cable? If yes, likely the FT2232H on the kit is damaged as the signals are at 3v3 levels.
Is the FT2232H on the DK warm or hot to touch?
古玛
1 year ago
嗨，蒙2，
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）
设备在stance 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方法”，并惊讶地发现，它正在给登录终端，其中UART TX:将J2上的P21连接到J1 as上的UTX引脚17Connected J1.17-J2.21. Same Driver as above detail in TeraTerm.
所以，我想，在SDK示例中，DK板上的连接或UART配置都存在问题。
1 year ago
Hi pintu,
Please follow the instructions in the following document strictly:
如果有效，就告诉我。
And, pls tell me the screen printing of your 531 chip, for example: 531 937 AA
Br, Yibin
1 year ago
Pintu，此帖子是为了确认我们的实验室设置与您的（DA14531 IC）相同，带有图28所示的单飞线（根据宜宾的帖子）的相同的子板，正在使用Tera Term@115200 bps设置。确保您的跳线符合图28。
Figure 28
10 months ago
Hi Pascal,
Thanks for your comments. I have replied you in this forum thread:
谢谢，PM_Dialog
1 year ago
嗨，平图。不与对话人员一起，但可能能够提供帮助。这里有同样的工具。
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.
一旦您确认工厂闪烁固件对您有效，继续测试您的Keil编译版本。
希望这有帮助。
蒙2