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.

AM1808: uPP has 64-bytes shifting in receive mode

Part Number: AM1808


Hello,

I am using AM1808 device in our productions. uPP interfaces connect with a piece of fpga,working in duplex mode,8BIT mode,operaction clock 100MHz.

most of the time,uPP work fine.But rarely,the data recevied from uPP has 64-bytes shifting and once the shifting occurs,it will remain,

the data such as:

in normal condition:(start with 0x5555aaa,end with 0x3333cccc)

0000: 55 55 aa aa a0 1a 00 ba 5c 00 ce 00 ff ff ff ff

0010: ff ff 00 22 15 c4 06 80 08 00 45 00 00 4e 78 d0

0020: 00 00 40 11 85 19 c0 a8 fd 64 c0 a8 fd ff 00 89

0030: 00 89 00 3a 4e 37 8f fb 01 10 00 01 00 00 00 00

0040: 00 00 20 45 45 46 43 43 4f 46 44 45 48 43 4f 45

0050: 43 45 42 45 4a 45 45 46 46 43 4f 45 44 45 50 45

0060:4e 41 41 00 00 20 00 01 2a a5 75 bf 33 33 cc cc

And in error condition:(0x5555aaaa start in address 0x0040)

0000: dc 16 ea 01 03 00 cc cc 3c 00 96 34 ff ff ff ff

0010:ff ff 54 ee 75 65 ab 86 08 06 00 01 08 00 06 04

0020: 00 01 54 ee 75 65 ab 86 de 6f 70 65 00 00 00 00

0030: 00 00 de 6f 70 bc 00 00 00 00 00 00 00 00 00 00

0040: 55 55 aa aa a0 44 00 e4 04 01 98 34 ff ff ff ff

0050: ff ff 54 ee 75 65 ab 86 08 00 45 00 00 f4 21 cb

0060: 00 00 80 11 75 f7 64 64 64 6f 64 64 64 ff 00 8a

there are some problems:

1.  which conditions can lead to this 64-bytes shifting?

2. once this shifting occurs,what should we do to resolve this shifting? such as empty the uPP fifo?

Does anyone have similar experiences,ideas,or advises to resolve my issue?

Thanks.

  • Hi,

    What software is this?

    Best Regards,
    Yordan
  • Hi
    The max IO clock supported for uPP is 75 MHz , if you are running it at 100 MHz, you maybe violating the timing spec

    www.ti.com/.../peripheral_information_and_electrical_specifications

    Have you tried to reduce the frequency to see if you still see the failures?

    Regards
    Mukul
  • Hi Yordan,

    I am using vxWorks system and I have written my own uPP driver.

    Kind regards 
    Junhuan

  • Hi Mukul,
    Thanks for prompt reply. The 64-bytes shifting is hard to show up, the upp(100MHz) may run steadily for more than two weeks . We are testing the upp Running in 50MHz.It is my understanding that upp working in 100M may lead to data crc error. ,not the shifting.
  • Hi

    >>It is my understanding that upp working in 100M may lead to data crc error. ,not the shifting.

    You may be right on the type of failure you are seeing may not be directly related to the clock speed, however I still have to strongly caution you that if you are running at 100 MHz, you are running it out of spec. We closed timings at 75 MHz and cannot guarantee working beyond that specification. You should not be using 100 MHz in mass production for your end application.

    If the failure occurs some time after running for 2 weeks, you maybe dealing with some other problem, perhaps some noise or any other momentary glitch in hardware/software/power supply that could be causing the failure? Maybe things like this are corrupting the internal data pointers?
    I am assuming this is a stand alone test and there is no change in data traffic, peripherals/masters involved on the chip while running this test , that could cause the issue?

    Keep us posted if you see the issue /failures running at 50 MHz.

    Regards
    Mukul