This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Putty Displaying this weird character ▒▒0▒▒▒▒▒▒3^▒▒▒▒▒▒▒▒▒▒▒▒▒d▒▒▒▒▒ . How to solve it ??

I already follow the link for terminal in this link  https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_nrf5_v16.0.0%2Flib_cli.html&cp=6_1_3_10_3&anchor=lib_cli_terminal_settings .

From android apps sent message to mcu the message is not display in putty. While when sending from mcu  to android apps it display this weird character. 

Parents
  • Does it work at all? I'd check that your Speed is set right (and data and stop bits). 

  • everthing is right. Dont know what is wrong.Maybe I will uninstall putty and reinstall back.

  • Hi, 

    What is your speed of putty and the NRF_LOG_BACKEND_UART_BAUDRATE value in the sdk_config.h?

    ox00 said:
    Does not make sense because when installing at other computer is ok.

    I am not confident to have a solution. If the issue only happened to the specific computer instead of others, I would suggest using others.  

    What example are you using?

    Do you have nRF52840DK? If so, could you run the BSP Example? Also, follow the setting:

    Start a terminal emulator like PuTTY and connect to the used COM port with the following UART settings:

    • Baud rate: 115.200
    • 8 data bits
    • 1 stop bit
    • No parity
    • HW flow control: None

     

    Do you also see the same issue while executing the example?

     

    -Amanda H.

  • #define HCI_UART_BAUDRATE 30801920   in sdk_config.h 

    in putty is 115200. Do I need to change the speed in sdk_config.h ?

  • Hi, 

     

    ox00 said:
    #define HCI_UART_BAUDRATE 30801920   in sdk_config.h 

     In the sdk_config.h, 30801920 means 115200 baud.  

     

    ox00 said:
    in putty is 115200. Do I need to change the speed in sdk_config.h ?

    The setting should be fine on the both sides.  

    Could you share the sdk_config.h?

    -Amanda H

  • Hi, 

    If you want to use the terminal tool to see the log, please add the following setting in the sdk_config.h

    // <e> NRF_LOG_BACKEND_UART_ENABLED - nrf_log_backend_uart - Log UART backend
    //==========================================================
    #ifndef NRF_LOG_BACKEND_UART_ENABLED
    #define NRF_LOG_BACKEND_UART_ENABLED 1
    #endif
    // <o> NRF_LOG_BACKEND_UART_TX_PIN - UART TX pin 
    #ifndef NRF_LOG_BACKEND_UART_TX_PIN
    #define NRF_LOG_BACKEND_UART_TX_PIN 6
    #endif
    
    // <o> NRF_LOG_BACKEND_UART_BAUDRATE  - Default Baudrate
     
    // <323584=> 1200 baud 
    // <643072=> 2400 baud 
    // <1290240=> 4800 baud 
    // <2576384=> 9600 baud 
    // <3862528=> 14400 baud 
    // <5152768=> 19200 baud 
    // <7716864=> 28800 baud 
    // <10289152=> 38400 baud 
    // <15400960=> 57600 baud 
    // <20615168=> 76800 baud 
    // <30801920=> 115200 baud 
    // <61865984=> 230400 baud 
    // <67108864=> 250000 baud 
    // <121634816=> 460800 baud 
    // <251658240=> 921600 baud 
    // <268435456=> 1000000 baud 
    
    #ifndef NRF_LOG_BACKEND_UART_BAUDRATE
    #define NRF_LOG_BACKEND_UART_BAUDRATE 30801920
    #endif
    
    // <o> NRF_LOG_BACKEND_UART_TEMP_BUFFER_SIZE - Size of buffer for partially processed strings. 
    // <i> Size of the buffer is a trade-off between RAM usage and processing.
    // <i> if buffer is smaller then strings will often be fragmented.
    // <i> It is recommended to use size which will fit typical log and only the
    // <i> longer one will be fragmented.
    
    #ifndef NRF_LOG_BACKEND_UART_TEMP_BUFFER_SIZE
    #define NRF_LOG_BACKEND_UART_TEMP_BUFFER_SIZE 64
    #endif
    
    // </e>
     

    Also, enable NRF_LOG_ENABLED as

    // <e> NRF_LOG_ENABLED - nrf_log - Logger
    //==========================================================
    #ifndef NRF_LOG_ENABLED
    #define NRF_LOG_ENABLED 1
    #endif

    -Amanda H.

Reply
  • Hi, 

    If you want to use the terminal tool to see the log, please add the following setting in the sdk_config.h

    // <e> NRF_LOG_BACKEND_UART_ENABLED - nrf_log_backend_uart - Log UART backend
    //==========================================================
    #ifndef NRF_LOG_BACKEND_UART_ENABLED
    #define NRF_LOG_BACKEND_UART_ENABLED 1
    #endif
    // <o> NRF_LOG_BACKEND_UART_TX_PIN - UART TX pin 
    #ifndef NRF_LOG_BACKEND_UART_TX_PIN
    #define NRF_LOG_BACKEND_UART_TX_PIN 6
    #endif
    
    // <o> NRF_LOG_BACKEND_UART_BAUDRATE  - Default Baudrate
     
    // <323584=> 1200 baud 
    // <643072=> 2400 baud 
    // <1290240=> 4800 baud 
    // <2576384=> 9600 baud 
    // <3862528=> 14400 baud 
    // <5152768=> 19200 baud 
    // <7716864=> 28800 baud 
    // <10289152=> 38400 baud 
    // <15400960=> 57600 baud 
    // <20615168=> 76800 baud 
    // <30801920=> 115200 baud 
    // <61865984=> 230400 baud 
    // <67108864=> 250000 baud 
    // <121634816=> 460800 baud 
    // <251658240=> 921600 baud 
    // <268435456=> 1000000 baud 
    
    #ifndef NRF_LOG_BACKEND_UART_BAUDRATE
    #define NRF_LOG_BACKEND_UART_BAUDRATE 30801920
    #endif
    
    // <o> NRF_LOG_BACKEND_UART_TEMP_BUFFER_SIZE - Size of buffer for partially processed strings. 
    // <i> Size of the buffer is a trade-off between RAM usage and processing.
    // <i> if buffer is smaller then strings will often be fragmented.
    // <i> It is recommended to use size which will fit typical log and only the
    // <i> longer one will be fragmented.
    
    #ifndef NRF_LOG_BACKEND_UART_TEMP_BUFFER_SIZE
    #define NRF_LOG_BACKEND_UART_TEMP_BUFFER_SIZE 64
    #endif
    
    // </e>
     

    Also, enable NRF_LOG_ENABLED as

    // <e> NRF_LOG_ENABLED - nrf_log - Logger
    //==========================================================
    #ifndef NRF_LOG_ENABLED
    #define NRF_LOG_ENABLED 1
    #endif

    -Amanda H.

Children
Related