Forums

Jim,

It appears you're using Windows 7. Currently the ADS1298 evaluation software does not support Windows 7.

Kevin,

            yes, in the picture, the PC is Win7, but when I use the WinXP(SP3) system, still can't acquire the data , and have the same phenomenon

Hi Jim,

This sounds like either a jumper issue, or an old software issue. Please verify that you have the latest code from the PDK link and double check that your jumpers are configured correctly.

Regards,

Michael

Michael,

            thanks for your reply, the software is the latest which I download from TI website yesterday. As the Jumper I doubt that also and change some ,but it sounds no good  progress.

          So,do you know which jumper will cause this issue?

Hi Jim,

Hopefully this forum post will help clear things up.

http://e2e.ti.com/support/data_converters/precision_data_converters/f/73/p/60434/217707.aspx#217707

Regards,

Michael

Michael,

             I set the jumper as the forum you mentioned,but still the same error.  what's the 6004 error code mean? do it take 10 minutes or more to reading register when connect the EVM to the PC  is normal ? will the USB line cause this issue? I feel so confued. pls help me.

thanks.

Jim

Jim,

Error code 6004 essentially means something unexpected happened during the PC Software to Embedded Firmware communication. In the case of DSP based mother boards there is a virtual filesystem masked over the register map of a device under evaluation that we use to interface the device in a more human intuitive way than manipulating shadow registers and bit fields in the PC client.

When we see error code 6004 it specifically either means there is no firmware flashed to the MMB0 (DSP), the incorrect firmware was flashed to the MMB0, drivers are not functioning, or that the DSP encountered a problem while trying to communicate with the device under evaluation. The last case being pretty rare, since the interface to the devices rarely changes after a part is in production and we test these lowest level communications pretty exhaustively, but sometimes a wrong jumper setting can sever a vital line for communicating with the device.

Can you tell me exactly when the failure occurs? In your pictures from your Windows 7 machine it seems like you get the error while you're running an acquire cycle. Do you see these errors when you're writing to registers on the device as well, or only during an acquire? If you only see it during an acquire, what are the configurations under which you're trying to do the acquire cycle?

Kevin，

           this error just happen when I click the acquire. I can change the register that's means I can write the register with no such error.

something you should know, I did not  put any signal to the ADS1298 input, will this cause the error?

Jim,

This is running under a true Windows XP machine right? Not a virtual machine or "compatibility mode" from a Windows 7 computer?

Jim,

Very glad to hear you got everything working and you are satisfied with the EVM. Sometimes remotely debugging these kind of problems can take a long time, there's lots of common mistakes we have to sort through first to get down to what's wrong.

The only problem the software would have faced on a Windows 7 machine is compatibility with our USB driver, but there are some work arounds that have been discussed on this forum. If you didn't do anything extra to get the plug-in working this would be the first case of the EVM working on Windows 7 by default (i.e. it worked right out of our installer) I've seen or heard of. Interesting to say the least.

I have read lots about ADS1298 EVM Card and wanted to share an experience of mine. Those who cannot use EVM Card with Windows 7, install the latest software version and run the program in "Run as administrator" mode. It worked for me, I hope you can use this information,

All best.