• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 62 subscribers
  • Views 1325 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

UCD92xx device detection with Fusion GUI

Han Bui
Prodigy 30 points
Other Parts Discussed in Thread: UCD9248

Hello, 

I am having a similar problem. However, I am only using address 52d and 53d. When I used the address scanner tool, only address 52d was found. I've checked the 3.3V input to the second controller, and it is stable. Is there any other diagnostic tools that I can use to see why my second device is not found? Any help is greatly appreciated.

Thanks,

Han

  • 0
    Intellectual 290 points

    Han,

    What values of resistors are connected to Addr0 (pin 77) and Addr1 (pin 76) of UCD9248 devices? For 52d, the resistors should be Addr0 - 75K and Addr1 - 75K. For 53d, they must be Addr0 - 86.6K and Addr1 - 75K. Please check this.

    Alternately, you can disable one device and search for other device on PMbus. You can connect nRESET (pin 13) of one device to Ground and scan the bus. The second device should show up. You can repeat this with other device. 

    Hope this helps.

    Thanks,

    Naveen

  • 0 in reply to Naveen HN
    Prodigy 30 points

    Hi Naveen,

    Thank you for responding to my question. Sorry, I did not get back to you earlier, but I was out of the office. To verify, yes, I am using both 75K resistors for Addr0 and Addr1 for 52d. And for 53d, I am also using 86.6K for Addr0 and 75K for Addr1. I performed your suggestion, grounding the nRESET pin on the 52d device. When I launched the Fusion application, no devices were detected by the program. When I reattached the pullup resistor to the 52d nRESET signal, the Fusion application was able to detect 52d. 

    My conclusion is that there is something wrong with the 53d device. Are there any other troubleshooting tips that you can provide? We have been building this design for a while, and in every batch, we would get a handful of boards with this problem. We usually will just send it back to the CM and have them replace the two controllers. When they come back to us, they usually work. I am just trying to understand what happens and why.

    Thanks,

    Han

  • 0 in reply to Han Bui
    TI__Genius 13700 points

    Is the CM loading the UCD92xx configuration prior to shipping it to you?

    It may be something in their process, or decoupling around the controller.

    Open the UCD3xxx & UCD9xxx Device GUI in the Fusion GUI software folder

    Click the "Scan Device in ROM Mode" link at the top of the Tools section that opens.

    If a device is found in ROM mode, let me know.

  • 0 in reply to Brad
    Prodigy 40 points

    Hi Naveen,

    I have the same problem,Click the "Scan Device in ROM Mode",and than

    how could I do?

  • 0 in reply to Brad
    Prodigy 40 points

    Hi Naveen

    I have the same problem,I Click the "Scan Device in ROM Mode",than 

    How can I do to this?Thanks

  • 0 in reply to qi ning
    TI__Genius 13700 points

    I suppose there is the potential for a soldering issue with the bias voltage or the PMBus pins?

    Is it possible to measure the input current on the 3V3 rail that biases the controller?

  • 0 in reply to Brad
    Prodigy 105 points

    I was downloaded my Firmware in the target via UCD3xxx & UCD9xxx Device GUI .
    but I lost access to the ROM (ROM not detected) . The following figure shows you what you get when doing a Scan Device in ROM Mode

    But when you click Scan For Device in Program Mode we get this:

    At this stage, it is blocked it does not have the right to appoint another Firmware or the possibility of recovering the Flash program. It seems like I was be locked in Flash mode.

    So , How can i get back to ROM mode 

    Regards 
    Thanks