5. DA14585/586 Software Installation
This section describes the installation procedure for the drivers, the configuration of the serial port, and all necessary steps to verify the connection with the PC. It also provides solutions to problems that may occur.
5.1. Requirements of the Development PC
For proper evaluation and application development using the DA14585/586 SoC and the ProDev Kit, an external host is required. This external host must have a Microsoft Windows already installed and USB ports as described in Section Section 4.
5.2. Driver Installation
On first connection to a host PC running Microsoft Windows, the system will detect several devices and will automatically install all necessary drivers. If the system is configured to use Microsoft Windows Update, this may take several minutes to complete.
When the driver installation is complete, the system displays a Microsoft windows similar to the one presented in Figure 7.
Figure 7 Windows Driver Installation
There are two virtual COM ports created by the Windows driver. The first COM port (lower number, COM28 in this example) provides a UART interface (Used for printing) between the PC and the DA14585/586 devices. The second (higher number, COM29 in this example) is used to export measurement data from the current sense circuitry on the ProDev Kit to the Power Profiler tool. For more information on the Power Profiler, For further reading see the SmartSnippets Toolbox User Manual (UM-B-083).
Note
The COM port numbers assigned to the ProDev Kit motherboard might be different to the ones shown in Figure 7.
Note
If Your PC has a serial port on it, then that’s the COM1 you’re seeing. Hence you can’t make a communication between the ProDev Kit board and the Windows on that port. But you can do it only by using the other lowest COM port, COM28 in this case.
The COM port numbers can be found in the Windows Device Manager (Control Panel > Device Manager > Ports (COM & LPT)) as shown in Figure 8.
Figure 8 Device Manager Ports
5.3. Configuring the Serial Port for UART
Several development tools require UART to be routed to the FTDI serial port. Refer to Figure 31 in Appendix B for the ProDev Kit board connection verification and on how to properly configure the specific port.
5.3.1. Using Serial Port
To make sure that the communication between the ProDev Kit board and the Windows development host is properly established, it is necessary to verify the UART connection between the two nodes.
On the Windows host, Tera Term can be used to validate the connection to the ProDev Kit by following these steps:
Connect the ProDev Kit board to the PC via USB cable. The location of the board’s USB port is shown in Figure 5.
Use the Windows Device Manager to verify that the host discovered two serial ports – the first of which is connected to UART, see Figure 8.
Open Tera Term from the Windows Start menu as shown in Figure 9.
Figure 9 Start Tera Term
In the Tera Term: New connection dialog, select Serial, then select the COM Port to use, and click OK.
Select Setup > Serial Port and configure your UART port using the parameters shown in Table 3 (you need to be an administrator on your local machine), see Figure 10.
Settings |
Values |
|---|---|
Baud rate |
115200 |
Data bits |
8 |
Parity |
None |
Stop bits |
1 |
Flow Control |
None |
Figure 10 Setting Up the Port and Testing Connectivity via Tera Term
Warning
For the DA14585/586 P0_4 and P0_5 ports are used during the boot sequence. This pattern (printed characters) appearing in the terminal as shown in Figure 10 is due to the booting sequence itself.
5.4. Troubleshooting
If there any problems with the ProDev Kit connection to PC some possible solutions might be:
Make sure that your FTDI drivers are up to date. Drivers are available from the FTDI website.
Check for possible cabling issues by using a different USB cable.
Connect the two elements using a different USB port on the host PC.
Make sure that the hardware configuration is set for Pro development Kit, For further reading see Figure 30 in Appendix A.
Note
If none of these actions resolve the issue, please contact Dialog Tools Forums.