CDCE72010EVM: Error Installing Driver! Error 5

Hi Derek!

thanks for your message.

well I tried to follow that instructions But i still have a problem.

when I connect my  CDCE72010EVM to my windows 10 computer, the device is recognized with following details:

the details are : 

USB\VID_0451&PID_16F1\5&3835C29A&0&6

The TUSB3210 driver you sent me is not working for  for my PID_16F1

I think TUSB3210 works for PID_2136

That's why I am not able to update my driver.

please assist me on this? How can I update my driver? 

Thanks,

Sadegh

Hi Sadegh,

I admit I'm out of my depth on driver issues, so I'm grasping for a solution.

Maybe there is a way to set the Apploader PID manually to 16F1? Can you just add a line to the DeviceList section and the DeviceList.NTamd64 section which copies the 2136 line, but instead substitutes "VID_0451&PID_16F1"? Then upon searching the directory for the driver, it should recognize the correct driver for the differing PID.

Regards,

Dear Derek!

Thanks a lot for your message.

well I think we're having some improvement.

when I go to device manager to update the driver, unlike the last time, it recognize the file but it shows the following error. it asks for signature info from the company.

can you please assist on this? how can I get the singed info from the company?

Thanks,

Sadegh.

Hi Sadegh,

The whole point of the loader was to provide unsigned driver firmware that could be signed and certified by individual vendors, so we don't have a copy of the signed drivers. As far as I know, the only way to proceed is by disabling signature verification. There's an E2E thread that seems to have a method for doing this, for the 3410:

My guess is the process looks similar for the 3210 apploader package, but since the app loader drivers are used for manual installation and customer signing it would instead look like:

1. Run the command to disable driver signature verification
2. Restart PC
3. Connect the board and install the driver manually. Now there should be a warning about inability to verify driver signature, but it should install.
4. Run the command to re-enable driver signature verification
5. Restart PC

If that doesn't work, try the extended version:

1. Uninstall apploader package
2. Run the command to disable driver signature verification
3. Restart PC
4. Re-install apploader package
5. Modify apploader ini to point to the proper PID as before
6. Connect the board and install the driver manually. Now there should be a warning about inability to verify driver signature, but it should install.
7. Run the command to re-enable driver signature verification
8. Restart PC

Please let me know if this works.

Regards,

Hi derek

Thanks for your prompt reply.

Well I tried the extended method. and now while I am updating the driver another error comes up.

what does it mean by "driver is not intended for this platform"?

Thanks,

Sadegh

Sadegh,

Usually this error comes up when trying to install a 64-bit driver on a 32-bit system or vice versa. Maybe try removing the DeviceList.NTamd64 section and all keys from the apploader ini, forcing it to try to use it in 32-bit mode exclusively? Potentially the other way around?

If that doesn't work, I'm out of ideas. I can bring in someone with a little more knowledge on the TUSB and they might be able to provide support, but I'm not sure where to go from here.

Regards,

Hi Derek,

I am really sorry about the problem but unfortunately it still shows the same error. "driver is not intended for this platform"

I tried the both way. 32 and 64. but it didn't let my windows 10 to update the file.

my windows is 10 and 64-bit. 

I repeated all the procedures on another win7 PC too. But unfortunately it didn't recognize my driver for that either. 

If possible, please refer me to your other collogues.

Thanks,

Sadegh 

Hi Sadegh,

I'm sorry for all the trouble you've been having with the CDCE72010 GUI, the software support for a lot of the older CDC devices is lacking at the moment.

I've flagged the thread for a coworker that maintains TUSB device support, they should be available soon.

Regards,

Hi Sadegh,

Just to check you have changed TUSBXXXX.BIN locations in the corresponding locations INF, correct? In this case it would be useful to look at the driver install debug log.  This can be found at a location like C:\Windows\INF\ SetupAPI.dev.log. Please see this link for more information on this file.  

Hi Malik

Thanks for your message.

well I changed all the required sections in the apploader file as the following pic.

I checked the SetupAPI.dev file too. It seems that everything is ok in this file too. can you please check my setuoapi file?? is everything ok here in the attached file?

setupapi.dev.log

Hi Sadegh,

In the log, I see that the system is looking for "C:\WINDOWS\system32\drivers\ApLoader.sys", which may not be present in your windows directory. You should be able to copy it into your system32/drivers from the apploader package in "C:\Program Files (x86)\Texas Instruments Inc\TI USB Apploader Drivers\amd64" or the equivalent apploader install path you used.

Regards,

Hi Derek

thanks for your message. I checked that directory. I have the ApLoader.sys in my directory you said. as below.

I don't know why it's not working yet. I did all the procedures on different computers but I couldn't get it to work yet. 

Do you have any other idea that I can use it please?

Sadegh,

At this point, I'm not sure what else to try. The Windows 10 driver compatibility issues we're facing took us very much by surprise, and it's unlikely that we'll be able to fix the driver install process for these GUIs - the team that made this and other CDC device GUIs is no longer part of TI, and we're not sure what they did with the source code. We aren't experts in the driver software either, and the USB communication devices are now reaching EOL. We're currently working on creating some kind of workaround instructions to allow programming these devices through an external programmer. Very likely this will be a "legacy device programmer" tool implemented in TICS Pro (TICSPRO-SW) that accepts the text register file generated by the CDC GUIs as an input, and communicates over a discrete USB2ANY programmer which will need to be manually connected to the communication lines. But it will not be ready for a while, definitely not until after the holidays are over.

Right now, I think your best bet is to use some kind of external SPI programmer like an Aardvark, save the CDC GUI register file, and load the registers through the external programmer. You will need to lift the pins on the microcontroller SPI lines, attach wires to the SPI interface, and hook up the wires to an external programmer as shown below:

Regards,

Hi Derek.

I really appreciate your support, However I don't have any equipment to continue with your solution.

Thanks anyways. .