You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is Issue 1021 moved from a Google Code project.
Added by 2012-08-30T01:28:11.000Z by [email protected].
Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Defect, Priority-Medium
Original description
Am I correct in understanding the code from HardwareSerial.cpp allocates either 16 or 64 bytes (based on the size of RAM) for a ring buffer based on the existence of the UBRRxH register?
This seems presumptuous.
Perhaps the user better knows which USARTS he's using.
Could the code be revised to allow user defined symbols before inclusion of HardwareSerial.cpp to specify the USARTs to be used.
Similarly, perhaps the user might define SERIAL_BUFFER_SIZE (based on USART speed, F_CPU and application experience) to be used instead of the default.
While we're reducing RAM, should the head & tail be 8 bit.
The text was updated successfully, but these errors were encountered:
This is Issue 1021 moved from a Google Code project.
Added by 2012-08-30T01:28:11.000Z by [email protected].
Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Defect, Priority-Medium
Original description
Am I correct in understanding the code from HardwareSerial.cpp allocates either 16 or 64 bytes (based on the size of RAM) for a ring buffer based on the existence of the UBRRxH register?
This seems presumptuous.
Perhaps the user better knows which USARTS he's using.
Could the code be revised to allow user defined symbols before inclusion of HardwareSerial.cpp to specify the USARTs to be used.
Similarly, perhaps the user might define SERIAL_BUFFER_SIZE (based on USART speed, F_CPU and application experience) to be used instead of the default.
While we're reducing RAM, should the head & tail be 8 bit.
The text was updated successfully, but these errors were encountered: