How to use USART2 instead of USART1 in BLE_p2pServer example?

ledi7 · ‎2025-01-22

I am using the BLE_p2pServer example with NUCLEO-WBA55 and want to use USART2 instead of USART1. If I use USART1 and send a byte via HTerm, the task UTIL_SEQ_SetTask( 1<<CFG_TASK_SEND_NOTIF_ID, CFG_SEQ_PRIO_0); should be executed as soon as an RxCpltCallback event (in file usart_if.c) is triggered.

static void UsartIf_RxCpltCallback(UART_HandleTypeDef *huart)
{
  /* USER CODE BEGIN UsartIf_RxCpltCallback 1 */
	UTIL_SEQ_SetTask( 1<<CFG_TASK_SEND_NOTIF_ID, CFG_SEQ_PRIO_0);
  /* USER CODE END UsartIf_RxCpltCallback 1 */

  RxCpltCallback(&charRx, 1, 0);
  HAL_UART_Receive_IT(&huart1, &charRx, 1);

  /* USER CODE BEGIN UsartIf_RxCpltCallback 2 */

  /* USER CODE END UsartIf_RxCpltCallback 2 */
}

When I establish a BLE connection with the “nRF Connect” app, I receive the corresponding notification (Same effect as when I press button1)

and I also receive the corresponding logs via HTerm.

But if I now change “serial links for logs” to USART2 and configure USART2 exactly the same as USART1, I get confused characters as log information like this:

Andrew Neil · ‎2025-01-22

Follow-on from:

https://community.st.com/t5/stm32-mcus-wireless/send-trace-information-to-usart2-instead-of-usart1-in-ble/td-p/764007