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.

Slew rate problems with HPI

We are using a DM648 DSP connected to a P1022 powerpc (via the HPI). Due to a lack of chip-select pins, we generate the chip-select signal for the DSP in a Xilinx CPLD. When we continuously read from the data register with auto-increment, the address is sometimes (about every 3000000 accesses) incremented twice. So it seems that the DSP recognizes two read accesses instead of one. We analyzed the bus communication on the protocol level and could not find any unintended DSP access or any other protocol violations.

Eventually we discovered a correlation of the error with the slew rate of the chip select signal (Which is connected to HDS1 & HCS, HDS2 is connected to 3V3). By increasing the gradient of the chip select signal, the occurrence rate of the error can be reduced. Our assumption is now that the slew rate provided by the CPLD is too slow for the DSP. In an older system with the same DSP we do not have any problem and in this case the chip select signal is provided by the powerpc directly - with a steeper slew rate!

Is there anywhere a requirement for the steepness of the edges of the chip select signal? I could only find transition time requirements for the clock inputs of the DSP.

Thank you and best regards,

Peter Brunmayr

  • Hi Peter,

    Moving your post to the correct forum, DM64x DaVinci Video Processor .

     

    Regards,

    Shankari

  • Anyone an idea where I can find slew rate requirements for the HPI?

    Thank's
    Peter Brunmayr

  • Hi Peter,

    Do you have some plots that show the timings of the HDS1\ and HCS\ signals generated by the FPGA?
    What is the fastest/slowest rise/fall time that can be programmed on the FPGA side?

    Looking at the datasheet it does not seem that we specify the rise/fall time for the HPI signals.
    I will check if we do have some additional information about it.

    If you look in section 6.1.2 of the DM648 datasheet - SPRS372H we do specify the slew rate value used for the testing of the inputs during device production testing. This can help to assess how close your slew rate is from the test signal we use.

    Anthony

  • Hi Anthony!

    Thanks for your reply! Here are two plots (rising and falling edge) of the chip select signal connected to HDS1 & HCS, measured at the pin of HDS1.

    By modifying the CPLD, we can slightly increase the slew rate. However, even if we can increase the slew rate so that no error occurs during our tests, how can we be sure, that we are on the save side without a specifciation?

    Thanks & BR

    Peter

  • Hi Peter,

    Peter Brunmayr said:
    By modifying the CPLD, we can slightly increase the slew rate. However, even if we can increase the slew rate so that no error occurs during our tests,

    Just to be sure: are the plot above the modified one that do not show the failure? or the original one when you get failure on the HPI transaction?

    We unfortunately do not specify the slew rate for the HPI signals. As already mentioned the information of the test signal we use might help to get an order of magnitude of what can be used.

    Anthony

  • Hi Anthony,

    the plots are from the original configuration, where we get the failure on the HPI transaction.

    BR
    Peter