3 ms·
I always thought it should be called USRT when strictly synchronous, but indeed, everyone else called it USART, so I called it the "USART controller" For insta
by byuu 10y ago
I always thought it should be called USRT when strictly synchronous, but indeed, everyone else called it USART, so I called it the "USART controller"
For instance, this is the code I use to emulate it (also includes pin connection list in the comments): https://gitlab.com/higan/higan/blob/master/higan/sfc/controller/usart/usart.cpp https://gitlab.com/higan/higan/blob/master/higan/sfc/control...
(Seems silly to emulate this device, but it allows for testing and debugging the code you want to run on real hardware.)
- crb3 10y ago> I always thought it should be called USRT when strictly synchronous, but indeed, everyone else called it USART, so I called it the "USART controller" Because the chips that do synchronous serial IME also do asynchronous, hence USART. Which makes sense: asynchronous is a far more widely accepted and used protocol, so one chip-placement covers connecting to those devices as well.