The flashed FW I used was straight from the DSPS device side sample code I obtained from the Dialog Web portal. I was able to build and flash the DSPS peripheral mode firmware via JTAG to the basic kit. The DSPS Android App discovered the board. I selected it on the app and tried to send it some characters but nothing printed on the terminal. Regarding the terminal, I tried all three Flow Control with Xon/Xoff, hardware and none and Baud rate set to 115200. None of these options worked.
However, I also have an TDK eval kit with the 580 onboard. I was able to flash that unit via UART per their instructions since I guess they don't have the ATMEL (Debug Chip) as in the case with the Basic Kit. The same FW flash on the TDK board works flawlessly with the Android DSPS app. With the TDK board, I had to changed the FW user_periph_setup.h by
#define CFG_UART_SW_CTRL
#undefine CFG_UART_HW_CTRL.
The app found this board and I was able to send it characters and displayed on the terminal with Flow Control set to Xon/Xoff.
Any idea why I was able to get characters on the terminal with the DA580 board?
Thanks,
--Khai
嗨kqtrinh,
There are instructions in the DSPS application note regarding how to run the DSPS application on the basic kit, The problem with the basic kit and the DSPS is that the basic kit doesn't have an FTDI chip and uses the ATMEL (that acts as a debugger) in order to printout the characters, the problem is that the Jlink fw that runs in the ATMEL doesn't fully support hw flow control over UART. So in the instructions on section 8 in document UM-B-038 suggest to use am additional FTDI chip in order for the DSPS to operate properly. So are you using an additional FTDI chip or you are using the UART from the ATMEL to print out characters.
Thanks MT_dialog