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.

DS90UB947-Q1: Best way for SER '947 to put DES '926 into BIST

Part Number: DS90UB947-Q1

So we have a SER DS90UB947 to a DES DS90UB926. The '926 is on a remote display without smarts. We want to test the link as part of our BIST sequence at boot.

The kickers are: the BIST can only be started by the DES, there are no smarts (MPU) at the DES end.

We have considered a number of options. The leading candidates are

1. using an I2C "bus extender" (basically an I2C-driven register) on the DES side to assert BISTEN

1a. do the same, but with the SPI link

2. configuring a GPIO on the DES (via actions on the SER side) that we can set the GPIO on the DES to loop back to BISTEN

3. Configuring the INTB on the DES (via actions on the SER side) that we can set the INTB on the DES to loop back to BISTEN

Whatever way we get BIST started, the BIST should not prevent us from stopping the BIST.

To determine the status of the BIST, we should be able to look at the error count register. On the DES side, we could latch any roisters on the PASS output and use GPIO (or the bus extender register) to read the latch (the only reason for the latch is apparently PASS will pulse low between BIST runs if you continue another BIST run...)

We will be cutting hardware soon, so we would like to get this nailed while at the schematic stage. Unfortunately, I don't have hardware to play with this.

  • Hello-

    Either of the three options should be OK.

    Regards,
    Davor
  • We are in the process of ordering eval boards. I will try them out - I only need one to work.

    For now, I will assume my issue is resolved.

    I do have a question: (so maybe not fully resolved): I cannot find appnotes on how to do any of the three methods - ignoring my reason for doing so. Are there appnotes on how to setup GPIO on the DES from the SER? The documentation seems pretty clear, but until one starts down the path, anything looks easy.

    thanks! ... bandit

  • Hello-

    Unfortunately, we don't have a document that discusses this particular issue, but we will consider the topic for future publications.

    Regards,
    Davor
  • Quote: Unfortunately, we don't have a document that discusses this particular issue, but we will consider the topic for future publications.

    Thank you. App notes or "HowTo" docs can really help increase user satisfaction because control of hardware often has "gotchas" in terms of order of operation, or settings which are mutually exclusive, but the datasheet does not call those out. I have forehead-shaped holes in walls all around the country because of these - I have done at least a hundred device drivers at this point in my career. (Some for control loops on bare-iron, some on RTOSs, and for all three major versions of UNIX plus various versions of Linux.) Some were easy. Most were painful for various levels of pain. Some were *very* painful.