[RTEMS Project] #4982: Add support for TMS570LC4357 for the arm/tms570 BSP

[RTEMS trac]

#4982: Add support for TMS570LC4357 for the arm/tms570 BSP
-----------------------------+------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  enhancement      |      Status:  assigned
 Priority:  normal           |   Milestone:  6.1
Component:  arch/arm         |     Version:  6
 Severity:  normal           |  Resolution:
 Keywords:                   |  Blocked By:
 Blocking:                   |
-----------------------------+------------------------------

Comment (by Adrien Chardon <adrien@…>):

 In [changeset:"b1fdf753387189afe720d3fa1ac13af5fb9943c2/rtems"
 b1fdf75/rtems]:
 {{{
 #!CommitTicketReference repository="rtems"
 revision="b1fdf753387189afe720d3fa1ac13af5fb9943c2"
 bsp/tms570: Fix console receive interrupts

 `tms570_sci_interrupt_handler()` is called when an RX interrupt fires. It
 checks
 in the register `FLR`, the `RXRDY` bit (Receiver ready flag - indicate
 that the
 SCIRD contains new data). If it is set, it calls
 `tms570_sci_read_received_chars()`.

 `tms570_sci_read_received_chars()` checks the register `RD` against 0. If
 it is
 non zero, it returns 1 to indicate that one byte was read.

 In the old behavior, if it is zero, the function returns 0 to indicate
 that no
 data was read.

 The new behavior is to not silently drop 0x00 bytes. Ignoring 0x00 bytes
 is fine
 when working with printable text (which, I assume, is how this driver was
 tested), but as soon as the UART is used in non canonical (raw) mode, with
 potentially 0x00 bytes, these bytes will be silently dropped, causing
 issues in
 the data/protocol layer above.

 Update #4982.
 }}}

--
Ticket URL: <http://devel.rtems.org/ticket/4982#comment:51>
RTEMS Project <http://www.rtems.org/>
RTEMS Project