# Raw Synchronous Serial

**URL:** <https://forums.digi.com/t/raw-synchronous-serial/13790>\
**Category:** Rabbit\
**Tags:** serial-synchronous-h\
**Created:** [October 22, 2014, 8:52am UTC](https://forums.digi.com/t/raw-synchronous-serial/13790 "2014-10-22T08:52:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dbt3481](https://avatars.discourse-cdn.com/v4/letter/d/c2a13f/32.png) [@dbt3481](https://forums.digi.com/u/dbt3481)\
**Post date:** [October 22, 2014, 8:52am UTC](https://forums.digi.com/t/raw-synchronous-serial/13790/1 "2014-10-22T08:52:52Z")

</div>

I need to send and receive synchronous serial data in raw mode. There is no 0x7e header and there is no termination frame or bits. Merely a continuous stream of serial data and a clock with a sync pattern every 270 “words” with a word being 12 bits.

It appears Serial Ports E&F are hardware constrained to only handle asyn or HDLC? I thought this was based on the older Zilog serial processors which indeed did support raw serial modes.

I am using a RCM4310 and I want to avoid using ports A&B due to clock sharing and the programming port with other devices. I need C&D as well and the CLK lines are doubled up with E&F so it is really difficult to change paths.

My processor is preceded with a FPGA so I suppose I could do a sync serial to async converter or sync to HDLC but what a pain.

Surely this processor can support raw serial mode?

---

<div class="post-metadata">

**Author:** ![trooper2](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@trooper2](https://forums.digi.com/u/trooper2)\
**Post date:** [October 22, 2014, 9:47am UTC](https://forums.digi.com/t/raw-synchronous-serial/13790/2 "2014-10-22T09:47:31Z")

</div>

See TN213 Rabbit Serial Port Software at this link [http://www.digi.com/support/productdetail?pid=4978&amp;type=documentation](http://www.digi.com/support/productdetail?pid=4978&amp;type=documentation)

We have RS232.lib which is the stream-based driver and packet.lib which is the frame-based driver.

---

<div class="post-metadata">

**Author:** ![dbt3481](https://avatars.discourse-cdn.com/v4/letter/d/c2a13f/32.png) [@dbt3481](https://forums.digi.com/u/dbt3481)\
**Post date:** [October 22, 2014, 11:23am UTC](https://forums.digi.com/t/raw-synchronous-serial/13790/3 "2014-10-22T11:23:39Z")

</div>

Except these are asynchronous protocols?

---

<div class="post-metadata">

**Author:** ![trooper2](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@trooper2](https://forums.digi.com/u/trooper2)\
**Post date:** [October 22, 2014, 3:44pm UTC](https://forums.digi.com/t/raw-synchronous-serial/13790/4 "2014-10-22T15:44:25Z")

</div>

For complete details on the serial ports see the Rabbit 4000 processor user manual.

Synchronous is HDLC.

---

<div class="post-metadata">

**Author:** ![dbt3481](https://avatars.discourse-cdn.com/v4/letter/d/c2a13f/32.png) [@dbt3481](https://forums.digi.com/u/dbt3481)\
**Post date:** [October 23, 2014, 10:31am UTC](https://forums.digi.com/t/raw-synchronous-serial/13790/5 "2014-10-23T10:31:22Z")

</div>

No, synchronous is not HDLC. HDLC is a serial synchronous protocol but so is SPI for example. HDLC packets are framed with a 0x7e before and after the packet and include a 16 bit CRC.

0x7e-data-crc-crb-0x7e.

I have seen many HDLC controllers that support Raw mode in which the data is not framed nor requires the start stop flags.

Back to the drawing board.
