I just try may times, (_baud * 2.025) can work normally both 9600 and 115200.
(_baud * 2) - 5 NOT work at 115200, but (_baud * 2) - 7 is ok, so I think is either (_baud * 2.025) or (_baud * 2) - 7
I just try may times, (_baud * 2.025) can work normally both 9600 and 115200.
(_baud * 2) - 5 NOT work at 115200, but (_baud * 2) - 7 is ok, so I think is either (_baud * 2.025) or (_baud * 2) - 7
Could you please go with the - 7 instead of the multiplication? Physically, the PIO is running the same clock for all bauds and the same number of instructions, so I can kind of understand a fixed offset like -7 vs -5, but I can't justify a variable one.
Could you please go with the `- 7` instead of the multiplication? Physically, the PIO is running the same clock for all bauds and the same number of instructions, so I can kind of understand a fixed offset like `-7` vs `-5`, but I can't justify a variable one.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
fix SerialPIO receive large data error at 115200
update board flyboard2040core pin definition
Can you explain how you got the 2.025 factor, please?
I just try may times, (_baud * 2.025) can work normally both 9600 and 115200.
(_baud * 2) - 5 NOT work at 115200, but (_baud * 2) - 7 is ok, so I think is either (_baud * 2.025) or (_baud * 2) - 7
Could you please go with the
- 7instead of the multiplication? Physically, the PIO is running the same clock for all bauds and the same number of instructions, so I can kind of understand a fixed offset like-7vs-5, but I can't justify a variable one.Already done