You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2022/02/16 16:58:08 UTC

[GitHub] [mynewt-core] kasjer commented on pull request #2773: hw/mcu/dialog: Reset UART before reconfiguration

kasjer commented on pull request #2773:
URL: https://github.com/apache/mynewt-core/pull/2773#issuecomment-1041878085


   > Changes look good. Question: were these changes made in case hal_uart_config was called when the fifos had data in them or something like that (to prevent garbage being transmitted or received, for example)? If that is the case I am wondering about the ordering of some things in this function. For example, maybe NVIC interrupts should be disabled and cleared before setting the clock registers. If not, all good.
   
   It come out when I prepared changes for 6MHz UART; Main purpose was to have high speed UART debug traces that could be used for analyzing BLE related-timing (or at least I thing it was the purpose).
   I did it to trace stuff going on USB and timing of data was supposed to be as fast as possible so basically debugging code did not use hal UART code at all just wrote single bytes to UART data register.
   It turned out that USB (when cable was connected) started to generate events before main function had time to open UART, then when main started configuration, UART already had something in the TX FIFO and during configuration BUSY interrupt fired.
   So in real usage it will not be a problem I guess.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@mynewt.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org