• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 22 subscribers
  • Views 1468 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Parity simulation for UART input in debug function

Kirill Novoskoltsev

Hi all!

For example, I set disable parity generation and checking at UART0 Line Control Register.
Then I could write "S0IN = 0xAB" to simulate uart input, and it's ok.

But I neen to use UART with parity (even). How could I correct init S0IN? I tried "S0IN = 0xAB" and "S0IN = 0x1AB", anyway Keil say parity error.

Parents
  • 0 in reply to Kirill Novoskoltsev

    I could use "real_device <---> com_port_terminal" and "keil_debugger <---> serial_window".
    For example I type one symbol at keyboard.

    If I use uart with no_parity, both variants work equal.

    If I use uart with even_parity, "real_device <---> com_port_terminal" work correct (the same as befor with no_parity). But "keil_debugger <---> serial_window" generate Parity Error (PE) after any symbol typing.

    So, how could I adjust Keil Serial Window to correct send symbol with parity? Or how I could use S0IN to correct send symbol with parity?

Reply
  • 0 in reply to Kirill Novoskoltsev

    I could use "real_device <---> com_port_terminal" and "keil_debugger <---> serial_window".
    For example I type one symbol at keyboard.

    If I use uart with no_parity, both variants work equal.

    If I use uart with even_parity, "real_device <---> com_port_terminal" work correct (the same as befor with no_parity). But "keil_debugger <---> serial_window" generate Parity Error (PE) after any symbol typing.

    So, how could I adjust Keil Serial Window to correct send symbol with parity? Or how I could use S0IN to correct send symbol with parity?

Children