Hi Support Team,
I tried to test default blink and uart example, I am not able to see anything on terminal and FTDI cable
SDK: 6.0.12.1020.2
EVK:DA1453100FXDEVKT-P
Keil:Image loaded directly from keil debug mode
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_RX_PORT GPIO_PORT_0
#define UART1_RX_PIN GPIO_PIN_7
#define UART2_TX_PORT GPIO_PORT_0
#define UART2_TX_PIN GPIO_PIN_6
#define UART2_RX_PORT GPIO_PORT_0
#define UART2_RX_PIN GPIO_PIN_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 PIN
UART RX PIN DK connection
FTDI cable
RX PIN - J2.10(P05)
TX PIN - J2.12(P07)
DA14531
P0_5
Connect J1.17 - J2.27
P0_7
Connect J1.15 - J2.28
and connected FTDI cable GND with J2 GND.
Please refer pin connection in attached image.
Please let me know, If I need to change anything in SDK or any confusion in pin connection to test UART example.
2. Example Blinky
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
#else
#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.
Thanks,
PS
Hi Pintu. Not with Dialog staff but may be able to assist. Have the same tools here.
1) Confirm that you have 2 x COM ports linked to this kit from the onboard FTDI FT2232H Dual UART controller. Be sure you have the latest drivers from FTDI website for your OS.
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:
Connect 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.
Once you have confirmed the factory blinky firmware works for you, proceed to test out your Keil compiled version.
Hope this helps.
Mon2
Hi Mon2,
As per your suggestion and followed instruction given in your attached image, tested online Blink example from Dialog SmartBond Flash Programmer.
Observation:
1. LED is blinking event that is true in Keil compiled version. (Please check Pin connection and LED blink in attached image)
2. No log in UART in both case (Online Blinky and Keil Blinky)
3. Terminal tested with TeraTerm(Windows), RealTerm(Windows), Minicom(linux), So there is issue in UART example code for DA14531
SDK: 6.0.12.1020.2
EVK:DA1453100FXDEVKT-P.
1. Until this get works can you please provide sample peripheral application which can work with external UART which needs to connect with external FTDI.
2. External UART to FTDI connection pin
Regards,
Pintu
1) remove your external ftdi uart cable completely from this test. Do not plug this extra uart cable to your PC or this DK.
2) using only the USB cable and your DK, how many com ports are shown on your device manager? Which driver version is mapped to each ftdi com port? Share the pics for these details.
3) confirm your terminal is using the lower com port and is linked to this DK. The DK will add 2 new com ports to your box due to the FT2232H controller.
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?
Kumar
Hi Mon2,
1) There is no extra FTDI cable attached to PC or DK, Only connection on DK isConnect J1.17 - J2.27 and Connect J1.15 - J2.28
2)我observing 2 COM port, "Driver version 2.12.14.0"
From TeraTerm
Device Friendly Name: USB Serial Port (COM13)
设备实例ID: FTDIBUS\VID_0403+PID_6010+6&2507F1F0&0&2&1\0000
Device Manufacturer: FTDI
Provider Name: FTDI
Driver Date: 1-22-2016
Driver Version: 2.12.14.0
3) Yes, using a lower COM port only.
I also test example "da14531-da14585-586_changing_advertising_methods" for my requirement and surprised it's giving log in Terminal where UART TX: connect P21 on J2 to UTX pin 17 on J1 asConnected J1.17-J2.21. Same Driver as above detail in TeraTerm.
So, I guess, there is an issue in either connection on DK board or UART configuration in SDK example.
Hi pintu,
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 let me know if it works.
And, pls tell me the screen printing of your 531 chip, for example: 531 937 AA
Br, Yibin
Pintu, this post is to confirm that our lab setup with the same daughterboard as yours (DA14531 IC) with a single fly-wire as shown in Figure 28 (as per post above by Yibin) is working with Tera Term @ 115200 bps setting. Be sure that your jumpers are as per Figure 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
Dear Support Team,
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).
Is this correct and why ?
Best regards,
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
Thanks, PM_Dialog