MSP-FET430UIF -- FPA selector not found

MSP-FET430UIF is an old product that we have not maintain now. Recommend to use MSP-FET instead. By the way, what's the FPA do you mean? I have not see it before.

Hi Gary,

Razly has replied by email (noreply-e2e@mail.ti.com) with a screen shoot attached.

Let me top up on behalf of my colleague Razly over this forum.

Yes, it is an old model that being used in our test power PC for almost ten years, but sudden cannot detect it with f_openinstancesandfpas( "*# *" ).

Fyi, the PC is connected to one MSP-FET430UIF device, not in multiple. 

1) "FPAs-setup.ini" - configure with "FPA-1   *", which mean any MSP-FET430UIF device.

2) When run with FP430-commandline.exe, the f_openinstancesandfpas( "*# *" ) is getting 0 instead of 1. And the f_initialization() is getting 4 instead of 1.

3) Same issue goes either with msp430 demo or selftest exe, which not showing its FPA SN#.

4) But can do the programming by execute FET-Pro430.exe or FET-Pro430-Lite.exe without issue.

Our testing software script been written using command "f_openinstancesandfpas( "*# *" )" and f_initialization() for device detection and run the MSP430 library for auto programming. It has been used since 10years back until recent detection issue.

Pls do help advice. Appreciate that. TQ.

It seems you are using a script developed by yourself on the PC side, right? What if using CCS or Uniflash, or FET-Pro430 to do the firmware download with MSP-FET430UIF?

Hi Gary,

Yes, we using a script developed by us but being running almost 10years without issue. The issue is not about our script now.

But more toward how to detect the device using your command f_openinstancesandfpas( "*# *" )"  and  f_initialization() between PC and the device, without running our script.

As i mentioned in previous with item#2, we did use your TI FP430-commandline.exe but getting respond 0 instead of 1, refer to "FP430-CommandLine.pdf".

Same as if use with your demo or selftest exe tool.

So, we need to know what is the possible cause. Is it related to either MSP430FPA.dll or MSPFET430UIF1.dll or MSP430FPA.lib?? 

Or any window such as system32 where related usb detection goes wrong...???

I know that MSP-FET430UIF is an old product that you have not maintain now but use MSP-FET instead. But I believe even using MSP-FET, it is still using f_openinstancesandfpas( "*# *" )"  and  f_initialization() for device detection in command line. So what could be the causes if unable to detect the device.

Pls do respond ASAP as our tester is down currently. Appreciate your help and advice. TQ.

Horng-Tak Kang said:

Or any window such as system32 where related usb detection goes wrong...???

That is why I ask you to try other software like CCS to exclude the hardware problem first 

Hi Gary,

I managed to find a FlashPro-430 with PN# USB-FPA 6.0 and SN# 20111308. And it detected by window XP with its driver. 

Then use the same demo/selftest/commandline exe which execute f_openinstancesandfpas( "*# *" )"  and  f_initialization(), managed to detect FPA SN:20111308.

But if plug back MSP-FET430UIF, then not detect any FPA as usual. 

I did try on another two spare MSP-FET430UIF with same issue.

And I did try to setup another WinXP PC, the result is same where can detect FlashPro-430 with SN# 20111308, but not to MSP-FET430UIF.

Seem not relate to window system32 where related usb device.

Pls do advise where could be goes wrong. Appreciate your fast respond. Really appreciate that. TQ.

Does it possible to update the windows to WIN10? Or can you try your software with WIN10. I not sure if that related with PC system.