cancel
Showing results for 
Search instead for 
Did you mean: 

STM32Cube_FW_L4_V1.10.0 : UART Example Not functional

amir
Associate II
Posted on January 22, 2018 at 10:09

Hello,

I tried the example UART_TwoBoards_ComPolling from the  STM32Cube_FW_L4_V1.10.0 on the STM32L476RG-Nucleo boards, and it seems it doesn't work as expected.

I followed the readme.txt file for the wiring.

But i noticed after in the main.h file that the pins are not the same as described in the readme.txt file, even the instance is not the same. Is it normal?

4 REPLIES 4
Posted on January 22, 2018 at 16:39

I don't know, I haven't reviewed the readme.txt vs code.

The code, and settings there, are going to be definitive in regards to what the hardware ultimately does, so review those settings in the context of the user manual and schematic.

From a hardware side you'd want a common ground between two boards and the RX/TX pair switch over, so USART_TX on one side goes to USART_RX on the other.

On the NUCLEO-64 be aware that the Arduino D0/D1 pins share common use with the ST-LINK VCP and that solder bridges may need to be changed for USART2 PA2/PA3 operation

Tips, buy me a coffee, or three.. PayPal Venmo Up vote any posts that you find helpful, it shows what's working..
Posted on January 22, 2018 at 18:15

You can do simple test with a single board connecting tx and rx. 

Generate HAL based code, then in the main loop use HAL_UART_Transmit, then HAL_UART_Receive to test. Turn on led when you get different values.

BTW. Todat CubeMX 4.24.0 was released and new L4 library  - v1.11.0

amir
Associate II
Posted on January 23, 2018 at 09:33

Hi,

The problem was, that the pins described in the readme.txt are not the same used in the project, I changed them and it works.

Kind regards,

Guenael Cadier
ST Employee
Posted on February 21, 2018 at 14:55

Hi

Boughnimi.Amir

I confirm a discrepancy exists on this example between readme.txt and code. Issue has been logged and will be addressed for further L4 packages deliveries.

Regards

Guenael