• State Resolved
  • Locked Locked
  • Replies 30 replies
  • Answers 8 answers
  • Subscribers 45 subscribers
  • Views 3982 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.

Can I use a MMBO from ADS1262EVM-PDK with a DAC1220EVM so I can evaluate DAC1220 with DXP?

Peter Gaal
Prodigy 160 points
Other Parts Discussed in Thread: DAC1220, ADS1262, DXP, ADCPRO

I bought a DAC1220EVM module and want to evaluate it using the DXP software.  Can I just buy another ADS1262EVM-PDK and use the MMBO motherboard for evaluation of the DAC1220EVM?  I don't see a way to just get the MMBO and there is no DAC1220EVM-PDK available at least as far as I can see.  I don't want to hook up the DAC1220 to the MMBO I got with the ADS1262 with out understanding if it might damage one or both as I don't know if the MMBO is generic.

I went through the schematics for the MMBO rev D and did not find a show stopper for hooking up the DAC1220 so I did with no results.  Also when I run DXP it brings up the DXP DAC Config File Downloader and show multiple DACs but when I try to download any of them I get an error pop up that says it was unable to download file XXX.xml.  The green light indicating internet is working but no banana.  I also tried to scan for devices and it shows nothing.  The ADCpro works fine with the ADS126x EVM module.

I googled DAC1220.xml and found it using google.

I copied it to the device directory and the program runs with it so far.  The down loader seems to be not working on my win7 64bit professional operating system.

What I found is that the program runs but is not communicating with the device or the MMBO as configured.  How do I get this thing working?  The driver shows up in the device manager but I keep getting USB Connection time out and no communications.  ADCpro works no problem so what is the problem with this and is it because the MMBO for the ADS1262 will not work with the DAC1220?

Any help would be appreciated. 

 Best Regards

 Peter

  • 0
    TI__Guru** 113155 points

    Hi Peter,

    It sounds like there was some kind of administrative block on the DXP program getting access to the internet.  FYI, you can find all of the DXP xml files for the available devices by cutting and pasting the following link into your browser window:

    ftp.ti.com/.../Devices

    Unfortunately we do not sell the MMB0 by itself.  You can only get one by purchasing as a part of an EVM-PDK.  You do not need to purchase another ADS1262EVM-PDK unless you want another ADS1262EVM.  A less expensive option would be to purchase a less expensive EVM-PDK that uses the MMB0 motherboard (for example the DAC8881EVM-PDK).  Make sure that you pick an EVM-PDK that uses the MMB0 as not all EVM-PDKs use the MMB0 (some use the MMB3 for example).

    You should be able to use both MMB0s on your computer, however you must start each system one at a time as both of the boards will initially enumerate as MMB0.  Once you have downloaded the firmware file for the EVM connected, then the board will re-enumerate based on the application.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points
    Bob,
    Thanks for your info. I am ordering the DAC8881EVM-PDK. I still am having issues with getting the DXP to see the MMBO with the DAC1220EVM hooked to it. Any suggestions? The ADCpro program sees the ADS126xEVM-PDK but I get no USB connectivity error with DXP program and it says it can't download firmware. I have been swapping the MMBO between the two EVM modules. Is there a special sequence or do I need to reinstall stuff?
    Thanks for your help!
    Peter
  • 0 in reply to Peter Gaal
    TI__Guru** 113155 points

    Hi Peter,

    The DAC1220EVM is a 5V system whereas the MMB0 is 3.3V.  This should be ok unless you try to read data from the DAC1220.  At this point the only suggestions I have is verify all the voltage and jumper/switch settings.  One thing that can be an issue is the clock switch setting as the DAC1220 must have a clock.  The switch S2 should be in the XTAL position.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points
    Bob,
    I get exactly the same response from the DXP software when I do not put the DAC1220EVM on the MMBO as when the DAC1220EVM is installed. It looks like the MMBO is not seeing the DAC1220EVM and not downloading the correct code for it to run. When I run ADCpro it downloads code and then posts an error as the DAC1220EVM is hooked up. What I do see is that the MMBO is talking to the host when ADCpro is run but not when DXP. Is this because this MMBO rev D works with the ADS126xEVM? Do I just need towait for the MMBO from the DAC8881EVM-PDK?
    I have checked and rechecked jumpers and supply voltages and see no problem.
    Thanks again!
    Peter
  • 0 in reply to Bob Benjamin
    TI__Guru** 113155 points

    Hi Peter,

    It has been a while since I have used DXP, but you should be able to start DXP without the EVM connected at all.  The DXP firmware should download assuming the installation and required files have been downloaded.  The firmware for DXP is generic firmware and doesn't care which EVM is attached.  What it does care about is that an MMB0 is found.  For example, you cannot load the firmware for the ADS1262EVM and then try to run DXP without resetting or repowering the MMB0.

    Can you send me a screen shot of the error?

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points

    Bob,

    This morning I tried running DXP with eval system not hooked up and then hooked up the MMBO with DAC1220EVM and the exact same error as before popped up(see screen capture).  I will try and install and run the DAC1220 on a laptop that has win7 64 bit professional on it.  I will let you know what happens.

    Thanks!

    Gary

  • 0 in reply to Peter Gaal
    Prodigy 160 points
    Bob,
    I tried installing DXP on my laptop and it installed and initially it ran without USB Connection timeout but did not update the DAC. I put a scope on the SCLK going to the DAC1220(pin 3 labeled as CLKX on J2 the digital header) and no activity ever. Then I exited DXP and un plugged the MMBO and plugged the MMBO into another USB slot and now it fails to download code at various byte lengths. I am now trying to install the DXP software in a virtual XP machine to see if this works.
    So far in two different machines with win7 64 bit professional DXP with the DAC1220 and the MMBO from the ADS126xEVM-DPK does not work.
    Help Mr Wizard!!!!
    Best Regards,
    Peter
  • 0 in reply to Peter Gaal
    Prodigy 160 points
    Installing in a XP virtual machine did not work. I am out of ideas here. DXP does not work on either of the two win7 64 bit professional nor does it work in a virtual XP machine. There is no activity on either platform on the SPI clock line.
    Best Regards
    Peter
  • 0 in reply to Peter Gaal
    TI__Guru** 113155 points

    Hi Peter,

    I too have a Win7 64-bit pro operating system, but I'm not seeing the same issues that you are.  I will have to do some more investigating at to why your MMB0 is not being recognized.  I did not write the DXP software nor am I that familiar with it so give me some time to check it out to see if we can isolate your problems.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points
    Bob,
    Thanks for your support. I have had issues in the past with USB drivers and getting RF Studio to work. I look forward to seeing what you find.
    Best Regards
    Peter
  • 0 in reply to Peter Gaal
    TI__Guru** 113155 points

    Hi Peter,

    This issue has got us a bit perplexed.  One of my colleagues just received a new computer and we loaded ADCPro first, then the ADS1262EVM plugin followed by DXP.  Everything worked as expected.

    I actually discovered that I have one port on my PC that is acting in the same way as yours, but only one port.  The others work fine.  Basically there are some instances where DXP just totally ignores what is connected to the USB port. 

    One possibility for this to happen is based on how LabView is handling the opening and closing of resources.  It is possible that if you unplug the MMB0 once DXP has recognized the MMB0 prior to closing DXP, the VISA resources are left open and cannot be reopened until the PC is restarted.  So this is one possibility.

    However, there is the odd instance where one USB port works, but another does not.  You might try a different USB port to see if it is recognized.  I'm still looking into why this is happening but I'm not sure how quickly we can find the resolve.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    TI__Guru** 113155 points

    Hi Peter,

    I believe the problem on my computer is related to the USB3.0 hub.  The problem port is connected to this hub.  I downloaded driver updates and the latest bios for my computer, but I still have the same issues.  My colleague only has USB3.0 ports on his computer and sees no issues.  As his computer is a couple of years newer than mine they may have the driver/chipset issues resolved.

    I will keep investigating this issue as I have time.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points

    Bob,

    I tried to use the DAC8881EVM-PDK with exactly the same results.  I have uninstalled both DXP and ADCpro and the uninstaller does not delete the files in C:\Program Files (x86)\DXP nor ADCpro.  IT does not clean the registry either.  Is there a program you guys have that is a special full uninstall for both of these programs?  This is like the way Norton anti virus used to uninstall and you had to get a "special program" to uninstall all the files,dlls etc.

    I want to start over with a clean uninstalled DXP and ADCpro and try again this time installing only DXP and see if it works.  I want to completely get rid of the drivers etc.  How do I do this?  

    Regards

    Peter

  • 0 in reply to Peter Gaal
    TI__Guru** 113155 points

    Hi Peter,

    I will have to get someone else that is more closely connected with the installation/uninstallation process to help with this question.  As I said before, I too have the same issue with the USB3 combo hub on my computer.  As long as I use one of the other ports not on that hub it works fine. The driver file for both ADCPro and DXP are the same so I don't think that is your problem.  It does appear to be related to how the port addressing is reported to the DXP program.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points

    Bob,

    I also had to install the following after installing ADCpro as it did not find the driver for the TMS DSP chip.

    mmb0_driver_install_x64-v1.0.0.0.msi

    I have tried all the USB ports on two machines one Dell and one ACER with the exact same results with DXP.

    I really need to get this squared away as it is costing me allot of time.  I appreciate your help and understand I am not a tier 1 customer.

    Have a great weekend!

    Best Regards

    Peter

  • 0 in reply to Peter Gaal
    TI__Guru** 113155 points

    Hi Peter,

    Sorry for the delayed response.  Just so you know we take each post/customer issue seriously no matter who/where the customer.  The problem is we have many devices to support and only a handful of people to support them.  We are trying to understand what might be going on as you are the first customer to my knowledge that has ever had this particular issue.  I spent a good deal of time going over this with one of the software developers and making a list of possible places to check.  After spending a lot of time comparing why some ports work and other don't there are a couple of differences in how the ports are registered as well as how they connect to the hub.

    What the developer and I find that is interesting is ADCPro is connecting whereas DXP is not.  Basically the device is reporting properly in one case and not the other.  The method of checking for the device is similar, but does not use the same libraries.  Going back to my situation where some ports work and others do not, I believe that there may be a reporting issue as the port that doesn't work also has some other lines included in the registry that may affect how the device is being reported.  This might be something as simple as case sensitivity.  If we new for sure we could fix it or find a work around.  In any case, what may be happening on my machine may be totally different than what is happening on your machine.

    The ADCPro installation does have issues on some customer machines with the driver install.  Due to this issue is why we have the separate installer and the one you used is appropriate.

    You also asked about the uninstall process and that some items are not removed.  I also ran the uninstall process for both programs and some folders are left as there are some separate uninstallers for the various components (NI drivers, runtime etc.).  As far as the drivers are concerned, we can uninstall the driver location we provided, however windows has a hierarchy of searching for drivers as a part of the plug and play manager.  The inf files are copied and renamed from the original and placed in the INF folder under root\windows\inf.  The installation file is kept in the system32/driver store.  These files are named by windows and are difficult to find and remove.

    I'm still working on it and have a couple of more things I can try.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    TI__Guru** 113155 points

    Hi Peter,

    As DXP requires .NET, can you look and tell me which version of .NET is installed on your computer?

    Thanks,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points

    Bob,

    Here is what control panel shows for NET:

    This was all the NET Framework information.

    Really appreciate your help!  ADCpro seems to be working pretty good with the ADS1262EVM module.

    Best Regards,

    Peter

  • 0 in reply to Peter Gaal
    Prodigy 160 points

    Bob,

    Any news on a solution to the non functional DXP?  It has been a week sense I sent .NET information.

    Best Regards,

    Peter 

  • 0 in reply to Peter Gaal
    TI__Guru** 113155 points

    Hi Peter,

    Sorry, but there was no news to report and thus no update.  I too have spent a ridiculous amount of time on this (including personal time on the weekends), but haven't quit.  I have others looking into this as well.

    It does not appear to be a .net issue, but rather some communication issue relative to how the hub is reporting back to the driver and enabling a line of communication.  In my specific case the MMB0 is not recognized at all.  We have also seen a case that appears to be very similar where the MMB0 is recognized and the initial DXP firmware is downloaded, but when the device is reset the device is recognized but the communication cannot be established.

    We have not yet found the common thread.  In your case we have no idea why none of your ports are being recognized by DXP unless we have the second case mentioned above where the initial process is started with the initial FW download, but the DXP communication fails.  You can verify this by determining if the USB connection changes to DXP (as opposed to MMB0) at the timeout condition. 

    There is also some log files that are created under the library folder \documents\dxp\saved.  You could zip those files and attach and we could see if we can find either an installation issue or some other commonality.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points

    Bob,

    I am trying to upload a zip file with the DXP logs in it.  Currently I am going through using a FTDI doggle to bit bang SPI to the DAC1220.  Of course it combines MOSI and MISO together with a direction control(output enable so that makes it a little harder with the DAC1220EVM module.  I don't know why this shows up this way but let me know if you get it.

    Regards

    Peter

    DXP_log_files.zip

  • 0 in reply to Peter Gaal
    TI__Guru** 113155 points

    Hi Peter,

    Yes, I got the log files, but unfortunately they do not show me anything new.  I was hoping that I would see some difference from my log files.  They actually look the same as mine when I connect the MMB0 to the USB3 hub.  Essentially the board cannot open a communications session, even though the device is recognized.

    We did communicate with the original developer, and the thought was perhaps there is a windows update that created a problem that may be in conflict with the driver.  If this were the case it seems a bit odd that I can successfully run this using the exact identical patches/security updates on one machine and not another.

    I personally think that there is a driver issue related to the Intel chipset being used and the communication between chipset and the MMB0 driver.  Or at least that appears to be the case on my computer.  I find it very interesting that you cannot resolve the issue using a different computer or by using a different USB port (unless all connections route through the same hub).  I'm wondering if there is an additional issue that is unique in your case.

    At this point I'm not sure what else to try or do.  We have had DXP running for several years now, and this is the first time we have seen this kind of problem.  I would not have noticed this issue either if I hadn't used a different USB port than I normally use due to this investigation.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points
    Bob,
    The computers you are using are the next thing I want to know. Like model number make all accessories in other words, I want a computer that is exactly what you use to run these programs. I have all ready spent more time mucking with this than what a computer costs.
    Then I can talk to my boss and see what he wants to do. Currently I am assuming no solution from Ti and I will continue writing my interface using FTDI dongles to the DAC1220EVM.
    On another note, I have written and compiled win32 console applications that run talking to FTDI FT232H devices and FT2232H devices on Intel I7 quad core and AMD FX 8 core and a AMD XP quad core machine and using gcc compiler at the command prompt works, CodeBlock IDE works, Visual studio 2005 works as well ans Visual Studio Express 2015. They all compile and communicate with the FTDI devices with no problem.
    I do not feel it is a problem with the computers I have and their updates. What is the difference between your drivers for the MMBO boards and all the FTDI chip drivers that work on all platforms I have tested on? Also I have tested them on 3.0 ports, 2.0 ports and probably 1.1 USB ports - no problem seeing and reporting all information back. Here are results from my TIAO USB MultiProtocol Adapter and a program I wrote in VSE community 2015:
    C:\GCCtestVC\GCCtestVC082215\GCCtest\SPI\SPI>VSDAC1220.exe
    We have devices hooked up
    Number of devices from FT_CreateDeviceInfoList is 2
    Number of devices from FT_GetDeviceInfoList is 2
    Dev 0:
    Flags=0x2
    Type=0x6
    ID=0x4038a98
    LocId=0x0
    SerialNumber=TIM00631A
    Description=TIAO USB Multi-Protocol Adapter A
    ftHandle= 00000000
    Dev 1:
    Flags=0x2
    Type=0x6
    ID=0x4038a98
    LocId=0x0
    SerialNumber=TIM00631B
    Description=TIAO USB Multi-Protocol Adapter B
    ftHandle= 00000000
    i done - status from FT_GetDeviceInfoList = 0x0
    made it through the i loop
    Made it to the end
    Visual Studio Express worked great!

    Regards
    Peter
  • 0 in reply to Peter Gaal
    TI__Guru** 113155 points

    Hi Peter,

    There are a lot of differences between the FTDI driver and the MMB0 driver as it relates to communication.  The bigger question is why ADCPro will communicate and not DXP.  Both GUIs run the same protocol and use the same communication method.  In both cases the native winusb driver is used.  What does differ is the communication layer that opens a channel.  ADCPro can open a channel whereas DXP cannot.  DXP sees that the device has enumerated, but cannot open a channel for communication.  It could be related to timing, reporting, or denial for some reason not understood.  It could also be related to conflicts with installed drivers and/or services running.  This is at a very low level, and very difficult to troubleshoot.  At this time I believe you are taking the correct course of action.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    TI__Guru** 113155 points

    Hi Peter,

    I have one further thought.  One thing that has really bothered me is the fact that you cannot get DXP to run and be recognized on any computer USB port.  You asked about why the FTDI driver works but DXP does not.  The USB portion is rather straightforward, but opening the communication channel requires opening the device as a virtual pathway to a device and file system.  The MMB0 operates as a styx (also known as Plan9, Inferno, etc.) virtual file subsystem.  Opening this file system and redirecting communication may be interpreted by your anti-virus software as a threat and deny the connection.  It could be that the security on your computer is set so high that this communication is disallowed. 

    I realize you have already spent a lot of time on this and want to move on, but I thought I would share this info with you. 

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points

    Bob,

    Your thought is reasonable except why does ADCpro work?  They both use the MMBO and I assume the same virtual file system.

    Best Regards

    Peter

  • 0 in reply to Peter Gaal
    TI__Guru** 113155 points

    Hi Peter,

    I agree that the issue is baffling as to why one works and the other does not.  One of the differences between the two is DXP uses a connection approach through Visual Studio whereas ADCPro uses an open source approach.  The short answer as to the switch was due to OS compatibility moving forward.

    There may be other issues related to inter driver communication, so there may not be a single answer to the problem.  In all cases where we have observed a problem internally within TI, it has been an issue with some ports working while others do not.  To my knowledge you are the first person to have reported a problem with establishing communication.  I would not have seen an issue if not directly looking for it, so there is something more unique about your situation with not getting any communication at any port.

    Best regards,

    Bob B

  • 0 in reply to Bob Benjamin
    Prodigy 160 points
    Bob,
    It has me baffled also as my win 7 64 bit laptop only has Microsoft security essentials and the other machine has bit defender on it. They are both Intel machines and the one with bit defender was just bought for this project. I am making progress on my interface to the DAC1220EVM using the an FTDI 232H VA800A dongle. I just finished the reset algorithm using bit banging on the SCLK line. I just finished the bus drive control(WgateB) - I call it that as it goes to FSR on J2 so I can use the MPSSE on the FT232H dongle. It is interesting that it works on AMD machines, Intel machines with win 7 64 bit and an older AMD machine with XP on it.
    Best Regards
    Peter
  • 0 in reply to Peter Gaal
    Prodigy 160 points

    Bob,

    I finally got the DAC1220EVM module to work.  I could not get it to work using chip select as it would give me unreliable results.  I went through all the timing diagrams and verified my timing and still it would not work until I tied chip select to ground.  I will consider this product as a backup plan but I need to find a much newer product that is much easier to interface with.  Also I am disappointed with the evaluation software DXP.  The FTDI FT232H and FT2232H worked fine with all the systems I tried it with. 

    Best Regards

    Peter

  • 0 in reply to Peter Gaal
    TI__Guru** 113155 points

    Hi Peter,

    I feel really bad that you have had such a struggle getting the DAC1220EVM to work.  I still have no clue as to the specific reason as to why DXP does not work on your computers.  There is a big difference between using the FTDI chip and what is being done with the MMB0.  The DXP software and ADCPro both use very similar methods so it is very difficult to ascertain why one is allowed to create access while the other is not.

    The product line I support has 4 DACs and only one of them can work with DXP.  The remaining DAC portfolio is handled by a different group.  I have passed this thread on to them and hopefully they will do further analysis and discover what is causing this issue as I would think this will happen again.

    Best regards,

    Bob B