Serial logging does not work with Dev kit DA14585 Pro

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
ohmi
Offline
Last seen: 3 years 4 months ago
Joined: 2019-03-28 08:21
Serial logging does not work with Dev kit DA14585 Pro

Hello support team,

I'm trying to use serial logging with the DA145858 pro dev kit, while changing the prox_reporter project.

UART2 works as I was able to receive messages with the Blinky project.

I've enabled the logging by defining CFG_PRINTF in da14585x_config_basic.h
uart2.c is present in sdk_driver and uart.h in sdk_driver_api

What did I miss?

By the way, I find it difficult to get into the development process as, if I understand well, I need to hook into various places.
But those places are not really obvious to me (even after going through UM-B-079).
For example, what is the difference between a user callback (code being called at specific point in your framework) and the user_default_app_operations.default_operation_adv

If I'd like to completely manage the timing and the content of the advertising could you confirm that user_default_app_operations.default_operation_adv is the place to write my own code?

Thanks.

 

Device: 
PM_Dialog
Offline
Last seen: 7 months 1 week ago
Staff
Joined: 2018-02-08 11:03
Hi ohmi

Hi ohmi

I would suggest you to use the arch_printf () API from arc_console.h library.

  1. #define CFG_PRINTF in the da1458x_config_basic.h
  2. Change the uart ports of the fw and assign the UART_TX port/pin to P04 and UART_RX port/pin to P05 (make sure that the configuration that you have changed is under the HW_CONFIG_PRO_DK and that this the board declared in the HW_CONFIG definition). Make sure that you have correctly connected the UART jumpers in Pro-DK

    #elif HW_CONFIG_PRO_DK

 

        #define UART2_TX_GPIO_PORT  GPIO_PORT_0

 

        #define UART2_TX_GPIO_PIN   GPIO_PIN_4

 

        #define UART2_RX_GPIO_PORT  GPIO_PORT_0

 

        #define UART2_RX_GPIO_PIN   GPIO_PIN_5

 

  1. Include the arch_console.h
  2. Invoke arch_printf()
  3. Change the baud rate of the serial terminal to 115200.

Thanks, PM_Dialog

ohmi
Offline
Last seen: 3 years 4 months ago
Joined: 2019-03-28 08:21
Thanks,

Thanks,

I've added

        #define UART2_TX_GPIO_PORT            GPIO_PORT_0
        #define UART2_TX_GPIO_PIN                GPIO_PIN_4
        #define UART2_RX_GPIO_PORT            GPIO_PORT_0
        #define UART2_RX_GPIO_PIN                GPIO_PIN_5   

in user_periph_setup.h under #elif HW_CONFIG_PRO_DK
jumpers are correct (same setings as for blinky)

I did the rest arch_printf() + includes

Same result call to NMI_HandlerC.

When I explore the code, I don't see any reference to UART2_TX_GPIO_PORT, UART2_TX_GPIO_PIN.

 

PM_Dialog
Offline
Last seen: 7 months 1 week ago
Staff
Joined: 2018-02-08 11:03
Hi ohmi,

Hi ohmi,

I checked the prox_reporter and you should do the modifications as described in the attached file. Jumpers should be placed on P04 - JL_RxD and jumping wiring for JL_TxD on P13 (the P05 is used for the SPI flash). Be aware that these notifications should be done only in prox_reporter project. For example, in ble_app_peripheral project you should do the steps that I had provided you in my previous post.

Thanks, PM_Dialog

Attachment: