This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Stellaris USART

Other Parts Discussed in Thread: LM3S5632

customer said:

Part of the design we’re working on is meant to support a pair of synchronous UART channels (clock received into the micro), operating at a high baud rate (1.6 MBaud). We’ve been unable to find a nice way of supporting this with the TI microcontrollers we’re considering (LM3S5632 or LM4F131E5QR), do you know if there’s a way to synchronize the UART ports on the device to an external clock? We’ve also looked at the SSI, but we are skeptical that we can make that work as the clock master is not providing a frame synching signal. The interface we’re receiving is really a synchronous UART with CLK, Rx and Tx signals only, and in order for the interface to work properly, we must clock out and receive our data with appropriate skew with regards to the CLK signal.

I would appreciate your thoughts on how either the LM3S5632 or the LM4F131E5QR may be configured to support such an interface.

The LM4F131E5QR controller includes eight Universal Asynchronous Receiver/Transmitter (UART) but no Universal Synchronous/Asynchronous Receiver/Transmitter (USART).  Synchronous serial communications would typically be done with the Synchronous Serial Interface (SSI). 

At first glance, I am not aware of a way to synchronize the UART ports on a device like the LM4F131E5QR to an external clock.

UARTSysClk is the system clock connected to the UART... By default, this will be the main system clock...  Alternatively, the UART may be clocked from the internal precision oscillator (PIOSC), independent of the system clock selection.
Stellaris LM4F131E5QR Microcontroller Data Sheet (Rev. B)
Page 823 of 1250

The programmable baud-rate generator allows for speeds up to 10 Mbps.

Stellaris LM4F131E5QR Microcontroller Data Sheet (Rev. B)
Page 820 of 1250

Will any of the devices be half-duplex, receive only or transmit only?

I'm not sure I understand exactly you communication plan?  Do you have a simple block diagram that would illustrate how you would like this to be configured?

Over what distance would each connection be?

  • Jason Work said:
    synchronous UART

    [/quote]

    That is a contradiction in terms!

    The 'A' in UART stands for Asynchronous - so, if it's synchronous, it's not a UART!!

    As noted, Stellaris parts have only UARTs - not USARTs.

     

  • Jason Work said:
    The interface we’re receiving is really a synchronous UART with CLK, Rx and Tx signals only

    This is a nice word picture - but suspect a legitimate timing diagram and/or spec/datasheet for this remote device will be required.  (devil in details)

    Distance issue raised should be answered as well.  Hazard a guess that Stellaris SSI module - properly mod'ed and perhaps imaginatively gated may "massage out" a working interface.

    Scratch my head over other post's contribution...  (point was previously stated)

     

  • Jason Work said:

    Will any of the devices be half-duplex, receive only or transmit only?

    I'm not sure I understand exactly you communication plan?  Do you have a simple block diagram that would illustrate how you would like this to be configured?

    Over what distance would each connection be?

    customer said:

    The device with which we are interfacing only provides a USART interface for communications, and it is the CLK master. The devices are full duplex, but not necessarily starting/stopping transmissions at the same time. The best description of the interface is that of a UART, that is synchronized to an external clock which is always running and generated at the device. The distance is minimal, between ICs on the PCB.

  • Earlier requested timing diagram not yet, "fact in evidence."  Not knowing set-ups/holds, edge/level sensitivities - humble forum assistants reduced to SWAGs.  (unfortunately that won't be a first...)

    Importantly - from a business standpoint - why does not mythical customer transact with the "exact same device" (which surely would work) - freeing this effort from a not too simple migration to Stellaris?  Customer/you have not yet made the case for Stellaris justification/utility -  cloak of secrecy delays and discourages...  (I am trying to be positive - believe this to be fair statement of your reality as we observe...) 

  • Jason Work said:
    The best description of the interface is that of a UART, that is synchronized to an external (sic?) clock which is always running and generated at the device

    "external" and "generated at the device" seems contradictory?

    Would it be sufficient to have both the Stellaris and this other device clocked from a single source?

    As already noted, we really need to see a timing diagram!

    Agree that this "chinese whispers" approach is impeding progress.

    Is it really not possible to name this mystery "external device"?!