• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 33 subscribers
  • Views 1249 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DS125DF111 and SMBus interface for analog launchpad

Bernie Schrenk
Prodigy 70 points

Other Parts Discussed in Thread: ALP, DS125DF111, DPS-DONGLE-EVM

Hi,


I am trying to use the DS125DF111 eval board with a SiliconLabs CP2112 SMBus-to-USB bridge to run the SMBus Slave mode in combination with the Analog Launchpad software. However, the ALP cannot detect SMBus connectivity although the CP2112 bridge works and I cannot set the USB-SMBus adapter at the ALP settings. It seems that some TI custom-made ALP dongle is required. First of all, is this correct that the software just works with some TI dongle in combination with this Eval Board?

If so, how to retrieve such an ALP dongle? I cannot find anything about it on the webpage.

Thanks,

Bernie

  • 0
    TI__Mastermind 29655 points

    Hi Bernie,

    ALP only works with the DS125DF111 if you have a SPA dongle adaptor board. Unfortunately, this is a separate board that is not available on the TI eStore.

    We are in the final stages of releasing a new software GUI for the DS125DF111 called SigCon Architect. This software uses an MSP430 MCU to communicate between PC and device via the SDA/SCL/GND lines. You will need a separate board called a DPS-DONGLE-EVM (as opposed to the SPA Dongle Board) with an on-board MSP430 to interface between PC and device as you program through SigCon Architect.

    SigCon Architect currently exists as a general framework, where you install an profile updater in order to add different device profiles into SigCon Architect, depending on the which ICs you are evaluating. While the SigCon Architect framework is available today, we have not yet finalized the release of the DS125DF111 profile updater on TI.com. I expect this to happen in the coming week or two.

    In the meantime, we can work to get a DPS-DONGLE-EVM to you so that when the software is available, you can begin testing. The DPS-DONGLE-EVM is only available by making the proper requests to our local sales team, as it is not publicly available on TI.com. Do you have a TI sales representative contact that we can get in touch with?

    Thanks,

    Michael

  • 0 in reply to Michael Lu (Santa Clara)
    Prodigy 70 points
    Hello Michael,

    first of all, thanks for the very quick reply that already provides a way for a solution. It's impressive to see a technical support forum working at this pace.
    I have contacted a local representative that should be able to act as authorized TI sales contact. Give them some workday to get back to me.

    Thanks,
    Bernhard
  • 0 in reply to Bernie Schrenk
    TI__Mastermind 29655 points
    Hi Bernie,

    We have received contact from Markus to follow up on your request for a DPS-DONGLE-EVM board. In the meantime, I want to let you know that as of the last 24 hours, the DS125DF111 profile has now become available for download on TI.com by going to the SigCon Architect Tools Folder.

    Thanks,

    Michael
  • 0 in reply to Michael Lu (Santa Clara)
    Prodigy 70 points

    Hello Michael,

    Markus got in touch with me and the issues is about to be solved. Thanks for your quick repsonse!

    Thanks for the effort,

    Bernhard

  • 0 in reply to Michael Lu (Santa Clara)
    Prodigy 70 points

    Dear Michael,


    although there was an initial contact with the local TI support, this contact did unfortunately break for some reason since I did not receive a reply within the last month (despite answering again to their questions). Is there an alternative way to proceed? Does the SigCon Architect generate EPROM files that I can write to a ROM chip and insert into the testboard?

    br,
    Bernhard

  • 0 in reply to Bernie Schrenk
    TI__Mastermind 29655 points

    Hi Bernie,

    That is unfortunate regarding the board! I'll follow up with Markus to see what happened there.

    In the meantime, to answer your question, yes, SigCon Architect can be used to generate EEPROM hex files! You will need to go to either the High Level or Low Level Page while in Demo Mode and program the desired settings so that the demo device has the settings you want the DS125DF111 to load upon default.

    After you have set the device up with the desired register settings, navigate to the EEPROM page, setup the size and number of devices to include in the EEPROM (in your case, I think everything should fit easily on a 256-Byte (2Kb) EEPROM for just 1 device). When ready, click "Update Slot From Device." The two live-update tables on the bottom and right side will then show the values that are programmed into the EEPROM as a result of your programmed settings. To save to an EEPROM hex file when finished, click "Write to EEPROM Hex," and you will be prompted to provide a file-name to save the .hex output.

    Note that SigCon Architect only has support for EEPROMs as an EEPROM hex file generation tool. You will need a third-party EEPROM programmer tool to load the hex file to an EEPROM. We have had success locally with using the TotalPhase Aardvark adapter to do this. After you have programmed the EEPROM, set the DS125DF111 in SMBus Master Mode and pull READEN# low to initiate the EEPROM load. When finished loading, the DS125DF111 DONE# pin will assert low to indicate a successful EEPROM load.

    Thanks,

    Michael

  • 0 in reply to Michael Lu (Santa Clara)
    Prodigy 70 points

    Hello Michael,

    thanks again for the continuous and very quick support!

    It's good to see that you guys have thought about integrating HEX file generation in the SigCon Architect. Programming of E2PROMs will not be an issue and is obviously de-coupled from the generation of HEX file.

    Regards,

    Bernhard

  • 0 in reply to Michael Lu (Santa Clara)
    Prodigy 70 points

    Dear Michael,


    I have tried the configuration with EEPROM today, using the Hex File generated with the SigCon Architect. In order to keep things simple and being able to test the plan was to exploit the built-in PRBS generator. Hex File generation did work and the file got programmed into a 24LC01B EEPROM that should suit the eval board.

    There the jumpers have been set accordingly: ENSMB float, VODA as the READEN# pin was pulled to low before switching on the supply for the eval board. What happens next is that the DONE# signal at ADDR1 jumper block does *not* go low but remains high. The current consumption of the eval board remains low with 25 mA. This indicates to me that there is no valid configuration achieved.

    In order to solve the issue step by step, can you provide a pre-programmed hex file that is known to work so I can avoid the problem of a misconfiguration and be sure that EEPROM + eval board work together? Is there any other explanation what can be wrong? The jumper settings on the eval board should be fine from what I read from the manual of the eval board. Do the 25 mA supply current provide any hint what is going wrong or is it normal for an unconfigured device?

  • 0 in reply to Bernie Schrenk
    TI__Mastermind 29655 points

    Hi Bernie,

    If the DONE# signal does not go low, then the EEPROM was not read properly.

    To help with your debugging, I've attached an example .hex file. In this example, there are two devices to be programmed. I presume that your DS125DF111 is set to default address 0x30, so it should take from the first device program set, starting from Address 0x33 and ending at 0x71. Please try this example set and check whether the DS125DF111 accepts this.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/138/DS125DF111_5F00_Example1.hex

    Thanks,

    Michael

  • 0 in reply to Michael Lu (Santa Clara)
    Prodigy 70 points

    Hello Michael,

    thanks for the continued support, which is as fast as in the old year.

    Indeed by switching EEPROM and using your Hex file the DONE# pin did go low. I am still evaluating the reasons what caused the difference.

    Thanks for the moment,

    Bernhard