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
When creating a cookiecutter deployment for ATmega, the ATmegaSerialDriver component is started with a baud rate of 115K in the Topology.cpp file. It would be beneficial to have an option added for starting the UART driver with a different baud rate by default, that way it is one less step to remember when trying to get a deployment functioning out of the box with GT-2 or ATmegas with clock speeds of 8MHz.
Requesting this feature after discovering that the GDS does not work with a 115K baud rate for the GT-2 ATmega modules, so anyone developing for GT-2 has to manually change the baud rate in their Topology.cpp file. It would be nice as we continue to make deployments in the future to avoid this to streamline our development process and avoid any unecessary headaches because people forget this one small detail.
The text was updated successfully, but these errors were encountered:
When creating a cookiecutter deployment for ATmega, the ATmegaSerialDriver component is started with a baud rate of 115K in the Topology.cpp file. It would be beneficial to have an option added for starting the UART driver with a different baud rate by default, that way it is one less step to remember when trying to get a deployment functioning out of the box with GT-2 or ATmegas with clock speeds of 8MHz.
Requesting this feature after discovering that the GDS does not work with a 115K baud rate for the GT-2 ATmega modules, so anyone developing for GT-2 has to manually change the baud rate in their Topology.cpp file. It would be nice as we continue to make deployments in the future to avoid this to streamline our development process and avoid any unecessary headaches because people forget this one small detail.
The text was updated successfully, but these errors were encountered: