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
At high baud rate (4M tested in this case), the uart send implementation on device side (TM4C), fails to send beyond 22 bytes. It doesn't panic or crash. simply fails to send more than 22 bytes. Some messages (eg - get_registers and pc (23 byte response)) have relatively larger response packets.
steps to reproduce
increase baud to 4M on device and host
TUI crashes when invoking get_registers_and_pc
Also isolated and tested a simple response of > 22 bytes and it caps off
Happens only with release optimization (was ok when tested with isolated example without optimization). the full device implementation does not fit without optimization
where
device-support/rpc/transport/uart*
log with isolated test expecting a 33 byte response:
what
At high baud rate (4M tested in this case), the uart send implementation on device side (TM4C), fails to send beyond 22 bytes. It doesn't panic or crash. simply fails to send more than 22 bytes. Some messages (eg - get_registers and pc (23 byte response)) have relatively larger response packets.
steps to reproduce
where
device-support/rpc/transport/uart*
log with isolated test expecting a 33 byte response:
environment information
The text was updated successfully, but these errors were encountered: