<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: HDLC packets are not coming from processor but line protocol is up in T-Series</title>
    <link>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1236373#M3988</link>
    <description>&lt;P&gt;We are using T1040D4RDB board and using sethdlc utility to send HDLC packets.&lt;/P&gt;&lt;P&gt;Log of the commands that we are using for sending HDLC packets:&lt;/P&gt;&lt;P&gt;root@t1040d4rdb:~# sethdlc hdlc0 hdlc&lt;BR /&gt;fsl_ucc_hdlc.c ucc_hdlc_attach 982&lt;BR /&gt;root@t1040d4rdb:~# sethdlc hdlc0 cisco interval 10 timeout 25&lt;BR /&gt;fsl_ucc_hdlc.c ucc_hdlc_attach 982&lt;BR /&gt;root@t1040d4rdb:~# ifconfig hdlc0 10.100.100.15 up&lt;BR /&gt;hdlc0: Carrier detected&lt;BR /&gt;hdlc.c:76 hdlc_start_xmit()&lt;BR /&gt;Cisco HDLC for non ARP H/W&lt;BR /&gt;Tx data skb-&amp;gt;len:22&lt;BR /&gt;Transmitted data:&lt;BR /&gt;8f&lt;BR /&gt;00&lt;BR /&gt;80&lt;BR /&gt;35&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;02&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;01&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;BD status value: 14000000&lt;BR /&gt;BD status value: 9c000016&lt;/P&gt;</description>
    <pubDate>Thu, 25 Feb 2021 06:47:09 GMT</pubDate>
    <dc:creator>suchitasharma</dc:creator>
    <dc:date>2021-02-25T06:47:09Z</dc:date>
    <item>
      <title>HDLC packets are not coming from processor but line protocol is up</title>
      <link>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1231837#M3978</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We are using T1040 based board and we are trying to send HDLC packets from our processor to cisco router via V.35 interface.&lt;/P&gt;&lt;P&gt;On cisco router line protocol is up but packets are not flowing from the processor. And it is not receiving the packets from cisco router also.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Log of cisco router:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Router#show interfaces serial 0/0&lt;BR /&gt;Serial0/0 is up, line protocol is up&lt;BR /&gt;Hardware is PowerQUICC Serial&lt;BR /&gt;Internet address is 10.100.100.30/24&lt;BR /&gt;MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,&lt;BR /&gt;reliability 255/255, txload 1/255, rxload 1/255&lt;BR /&gt;Encapsulation HDLC, loopback not set&lt;BR /&gt;Keepalive set (32767 sec)&lt;BR /&gt;Last input never, output 00:00:03, output hang never&lt;BR /&gt;Last clearing of "show interface" counters 04:06:16&lt;BR /&gt;Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0&lt;BR /&gt;Queueing strategy: fifo&lt;BR /&gt;Output queue :0/40 (size/max)&lt;BR /&gt;5 minute input rate 0 bits/sec, 0 packets/sec&lt;BR /&gt;5 minute output rate 0 bits/sec, 0 packets/sec&lt;BR /&gt;0 packets input, 0 bytes, 0 no buffer&lt;BR /&gt;Received 0 broadcasts, 0 runts, 0 giants, 0 throttles&lt;BR /&gt;18 input errors, 0 CRC, 8 frame, 0 overrun, 0 ignored, 9 abort&lt;BR /&gt;36 packets output, 11628 bytes, 0 underruns&lt;BR /&gt;0 output errors, 0 collisions, 417 interface resets&lt;BR /&gt;0 output buffer failures, 0 output buffers swapped out&lt;BR /&gt;40 carrier transitions&lt;BR /&gt;DCD=up DSR=up DTR=up RTS=up CTS=up&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can u please suggest what we can do rectify this issue.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2021 08:30:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1231837#M3978</guid>
      <dc:creator>suchitasharma</dc:creator>
      <dc:date>2021-02-18T08:30:44Z</dc:date>
    </item>
    <item>
      <title>Re: HDLC packets are not coming from processor but line protocol is up</title>
      <link>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1235711#M3986</link>
      <description>&lt;P&gt;How are you trying to send HDLC packets from T1040 processor. Which T1040 based board? What software are you using?&lt;/P&gt;</description>
      <pubDate>Wed, 24 Feb 2021 11:32:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1235711#M3986</guid>
      <dc:creator>r8070z</dc:creator>
      <dc:date>2021-02-24T11:32:29Z</dc:date>
    </item>
    <item>
      <title>Re: HDLC packets are not coming from processor but line protocol is up</title>
      <link>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1236373#M3988</link>
      <description>&lt;P&gt;We are using T1040D4RDB board and using sethdlc utility to send HDLC packets.&lt;/P&gt;&lt;P&gt;Log of the commands that we are using for sending HDLC packets:&lt;/P&gt;&lt;P&gt;root@t1040d4rdb:~# sethdlc hdlc0 hdlc&lt;BR /&gt;fsl_ucc_hdlc.c ucc_hdlc_attach 982&lt;BR /&gt;root@t1040d4rdb:~# sethdlc hdlc0 cisco interval 10 timeout 25&lt;BR /&gt;fsl_ucc_hdlc.c ucc_hdlc_attach 982&lt;BR /&gt;root@t1040d4rdb:~# ifconfig hdlc0 10.100.100.15 up&lt;BR /&gt;hdlc0: Carrier detected&lt;BR /&gt;hdlc.c:76 hdlc_start_xmit()&lt;BR /&gt;Cisco HDLC for non ARP H/W&lt;BR /&gt;Tx data skb-&amp;gt;len:22&lt;BR /&gt;Transmitted data:&lt;BR /&gt;8f&lt;BR /&gt;00&lt;BR /&gt;80&lt;BR /&gt;35&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;02&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;01&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;00&lt;BR /&gt;BD status value: 14000000&lt;BR /&gt;BD status value: 9c000016&lt;/P&gt;</description>
      <pubDate>Thu, 25 Feb 2021 06:47:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1236373#M3988</guid>
      <dc:creator>suchitasharma</dc:creator>
      <dc:date>2021-02-25T06:47:09Z</dc:date>
    </item>
    <item>
      <title>Re: HDLC packets are not coming from processor but line protocol is up</title>
      <link>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1237280#M3990</link>
      <description>&lt;P&gt;I assume you run the nxp QorIQ Linux SDK based software. The nxp Linux SDK 2.0 provides ucc_hdlc driver. This driver routes HDLC frame to the T1040 TDM and require X-TDM-DS26522 card installed on the T1040RDB. The TDM-DS26522 drives the T1040 TDM bus clocks and syncs. ucc_hdlc can work in normal or loopback mode. You can see details in The QorIQ SDK V2.0-1703 Documentation. It is avaialable on &lt;BR /&gt;&lt;A href="https://www.nxp.com/design/software/embedded-software/linux-software-and-development-tools/linux-sdk-for-qoriq-processors:SDKLINUX" target="_blank"&gt;https://www.nxp.com/design/software/embedded-software/linux-software-and-development-tools/linux-sdk-for-qoriq-processors:SDKLINUX&lt;/A&gt; &lt;BR /&gt;For Verification in Linux it says:&lt;/P&gt;
&lt;P&gt;1. After u-boot startup,set "qe-hdlc" parameter in hwconfig.&lt;/P&gt;
&lt;P&gt;2. After bootup kernel, Kernel boot log for hdlc:&lt;BR /&gt;hdlc: HDLC support module revision 1.22&lt;/P&gt;
&lt;P&gt;3. QE HDLC T1/E1 test&lt;BR /&gt;a. Make X-TDM-DS26522 card connected to T1040RDB board Slot.&lt;BR /&gt;b. To test tdm external ports, please plugin tdm t1/e1 loopback cable in the related port.&lt;BR /&gt;The following is HDLC port mapping with X-TDM-DS26522 card:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;HDLCPort&amp;nbsp; X-TDM-DS26522 Port&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Port A CH1;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Port B CH2;&lt;/FONT&gt;&lt;BR /&gt;c. HDLC test using E1.&lt;BR /&gt;Use the default dts to test E1 function. Test module can receive ucc_num as parameter. This number should be 1/3&lt;BR /&gt;related to the tdm port.&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;root@t1040rdb:~# mount /dev/mmcblk0 /mnt &amp;amp;&amp;amp; cp /mnt/sethdlc ./sethdlc &amp;amp;&amp;amp; ./sethdlc hdlc0&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;hdlc &amp;amp;&amp;amp; \&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;192.168.0.1 hdlc0 &amp;amp;&amp;amp; \&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;ping 192.168.0.2&amp;gt; ifconfig hdlc0 192.168.0.1 up &amp;amp;&amp;amp; \&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;gt; route add -net 192.168.0.0 netmask 255.255.255.0 gw 192.168.0.1 hdlc0 &amp;amp;&amp;amp; \&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&amp;gt; ping 192.168.0.2&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;hdlc0: Carrier detected&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;PING 192.168.0.2 (192.168.0.2): 56 data bytes&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Tx data skb-&amp;gt;len:86&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Transmitted data:&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;ff&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;44&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;45&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;00&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;00&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;54&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;cf&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;71&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;40&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;00&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;40&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;01&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;e9&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;e3&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;c0&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;a8&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;irq ucce:20000&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;TxBD: 1c00&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Received data length:88&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;while entry times:0&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Received data:&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;ff&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;44&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;45&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;00&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;00&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;54&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;cf&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;71&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;40&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;00&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;40&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;01&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;e9&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;e3&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;c0&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;a8&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;skb-&amp;gt;protocol:800&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;irq ucce:80000&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Feb 2021 12:41:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1237280#M3990</guid>
      <dc:creator>r8070z</dc:creator>
      <dc:date>2021-02-26T12:41:37Z</dc:date>
    </item>
    <item>
      <title>Re: HDLC packets are not coming from processor but line protocol is up</title>
      <link>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1237900#M3992</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; In our case , we are using FCC HDLC driver in &lt;STRONG&gt;NMSI&lt;/STRONG&gt; mode .So, in that case tdm related changes and&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; X-TDM-DS26522 device is not required . We have one transceiver SP505, which is connected to processor in one side&amp;nbsp; and another side cisco router is connected.&lt;/P&gt;&lt;P&gt;Is it possible that UCC hdlc work in standalone mode (NMSI ).&lt;/P&gt;&lt;P&gt;And also please find the attached diagram which is having the connection of our board with cisco router, which we are using for testing. TxCLK and RxCLK are shorted are we are using external clock CLK9 for TxCLK and CLK12 for RxCLK.&lt;/P&gt;&lt;P&gt;All the line protocol signals are up (DCD, DSR, DTR, RTS, CTS). But while probing TxD, we are not finding any data coming out from the processor.&lt;/P&gt;&lt;P&gt;Please suggest if we can do something for the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Mar 2021 06:29:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1237900#M3992</guid>
      <dc:creator>suchitasharma</dc:creator>
      <dc:date>2021-03-02T06:29:34Z</dc:date>
    </item>
    <item>
      <title>Re: HDLC packets are not coming from processor but line protocol is up</title>
      <link>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1240193#M3996</link>
      <description>&lt;P&gt;I think it is impossible that ucc hdlc work in standalone mode (NMSI ). The SDK document says: &lt;SPAN class="fontstyle0"&gt;"The HDLC/TDM driver is implemented by UCC and TSA(HDLC is upper layer protocol of TDM)." &lt;/SPAN&gt;&lt;SPAN class="fontstyle0"&gt;Also device tree node for the ucc_hdlc has TDM specific values:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="fontstyle0"&gt;fsl,rx-sync-clock = "rsync_pin";&lt;BR /&gt;fsl,tx-sync-clock = "tsync_pin";&lt;BR /&gt;fsl,tx-timeslot = &amp;lt;0xfffffffe&amp;gt;;&lt;BR /&gt;fsl,rx-timeslot = &amp;lt;0xfffffffe&amp;gt;;&lt;BR /&gt;fsl,tdm-framer-type = "e1";&lt;BR /&gt;fsl,tdm-mode = "normal";&lt;BR /&gt;fsl,tdm-id = &amp;lt;0&amp;gt;;&lt;BR /&gt;fsl,siram-entry-id = &amp;lt;0&amp;gt;;&lt;BR /&gt;fsl,tdm-interface;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Mar 2021 10:08:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1240193#M3996</guid>
      <dc:creator>r8070z</dc:creator>
      <dc:date>2021-03-04T10:08:30Z</dc:date>
    </item>
    <item>
      <title>Re: HDLC packets are not coming from processor but line protocol is up</title>
      <link>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1240681#M3997</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Thanks for the quick response. We have modified the device tree to make ucc work in hdlc mode .The modified device tree is given below:&lt;/P&gt;&lt;P&gt;ucc_hdlc: ucc@2000 {&lt;BR /&gt;compatible = "fsl,ucc_hdlc";&lt;BR /&gt;rx-clock-name = "clk12";&lt;BR /&gt;tx-clock-name = "brg2";&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;Please correct me if I m wrong .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 04:24:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1240681#M3997</guid>
      <dc:creator>suchitasharma</dc:creator>
      <dc:date>2021-03-05T04:24:36Z</dc:date>
    </item>
    <item>
      <title>Re: HDLC packets are not coming from processor but line protocol is up</title>
      <link>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1241009#M4000</link>
      <description>&lt;P&gt;So it seems the HDLC driver without tdm parameters in the device tree does not connect UCC to the SI. It can be done by programming the QE registers. However&amp;nbsp; NMSI and TDM bus need for the same pins and these pins are configured in the RCW. &lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 13:05:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1241009#M4000</guid>
      <dc:creator>r8070z</dc:creator>
      <dc:date>2021-03-05T13:05:59Z</dc:date>
    </item>
    <item>
      <title>Re: HDLC packets are not coming from processor but line protocol is up</title>
      <link>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1241535#M4003</link>
      <description>&lt;P&gt;Yes. We have done the same way as you said but internal loopback is working whereas hdlc driver tx and rx in normal mode is not working . could you please suggest what could be the reason for this?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Mar 2021 06:41:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/T-Series/HDLC-packets-are-not-coming-from-processor-but-line-protocol-is/m-p/1241535#M4003</guid>
      <dc:creator>suchitasharma</dc:creator>
      <dc:date>2021-03-08T06:41:12Z</dc:date>
    </item>
  </channel>
</rss>

