LM8335: GUI downloads and extracts(unzips) but will not run; ends up in an endless loop

Hey Stanley,

Can you provide screenshots of what you mean?

I was able to extract the zipped file and able to open the GUI:

Are you saying you can't get to this window or are you saying that there is an error after this window?

Thanks,

-Bobby

Thank you for your response.

I can not get to the GUI window.

After unzipping the GUI download I get a file named snvc061 that contains Appl File folder, an application Manifest, and a setup.exe file. At this point if try any file I get: Cannot Start Application msg which says it is already installed in a different location.
The details are:
PLATFORM VERSION INFO
Windows : 6.2.9200.0 (Win32NT)
Common Language Runtime : 4.0.30319.36460
System.Deployment.dll : 4.0.30319.36366 built by: FX452RTMLDR
clr.dll : 4.0.30319.36460 built by: FX452RTMLDR
dfdll.dll : 4.0.30319.36366 built by: FX452RTMLDR
dfshim.dll : 6.3.9600.16384 (winblue_rtm.130821-1623)

SOURCES
Deployment url : file:///C:/Users/stan68/Documents/snvc061/551600850A_GUI.application

IDENTITIES
Deployment Identity : 551600850A_GUI.application, Version=1.0.0.4, Culture=neutral, PublicKeyToken=619e8a07ee75fe52, processorArchitecture=x86

APPLICATION SUMMARY
* Installable application.

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Users\stan68\Documents\snvc061\551600850A_GUI.application resulted in exception. Following failure messages were detected:
+ You cannot start application 551600850A_GUI from this location because it is already installed from a different location.
+ You cannot start application 551600850A_GUI from location file:///C:/Users/stan68/Documents/snvc061/551600850A_GUI.application it is already installed from location file:///C:/Users/stan68/AppData/Local/Temp/Temp1_snvc061.zip/551600850A_GUI.application. You can start it from location file:///C:/Users/stan68/AppData/Local/Temp/Temp1_snvc061.zip/551600850A_GUI.application or you can uninstall it and reinstall it from location file:///C:/Users/stan68/Documents/snvc061/551600850A_GUI.application. If you reinstall the application, be aware that you might lose any customizations that you made to the application.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [11/21/2018 1:50:55 PM] : Activation of C:\Users\stan68\Documents\snvc061\551600850A_GUI.application has started.
* [11/21/2018 1:50:55 PM] : Processing of deployment manifest has successfully completed.

ERROR DETAILS
Following errors were detected during this operation.
* [11/21/2018 1:50:55 PM] System.Deployment.Application.DeploymentException (DeploymentUriDifferent)
- You cannot start application 551600850A_GUI from this location because it is already installed from a different location.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ApplicationActivator.CheckDeploymentProviderValidity(ActivationDescription actDesc, SubscriptionState subState)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Deployment.Application.DeploymentException (DeploymentUriDifferent)
- You cannot start application 551600850A_GUI from location file:///C:/Users/stan68/Documents/snvc061/551600850A_GUI.application it is already installed from location file:///C:/Users/stan68/AppData/Local/Temp/Temp1_snvc061.zip/551600850A_GUI.application. You can start it from location file:///C:/Users/stan68/AppData/Local/Temp/Temp1_snvc061.zip/551600850A_GUI.application or you can uninstall it and reinstall it from location file:///C:/Users/stan68/Documents/snvc061/551600850A_GUI.application. If you reinstall the application, be aware that you might lose any customizations that you made to the application.
- Source:
- Stack trace:


COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

At this point I am lost.

What do you recommend?

Thank you,

Stan Knight

TRX Booby,
You are the MAN! Perfect.

Now the next issue is how do I get 3.3V onto one of the unused GPIO pins on J2? The device I have to be tested has the following IOs: 1.8V VIO, SCLK, SDATA, 3.3V and GND. The 3.3V (VDD) must be applied AFTER the VIO is applied. The spec on the device does indicated the minimum time delay. Probably low msec.

The GUI does not seem to provide an option for this. Is the code that drives the GUI and provides the USB interface accessible so that this can be setup?

Otherwise, I can make a jumper to pick up 3.3V from the 3 pin jumper (VDDIO).

What do you recommend?

Thanks again,

Stan

Hey Stan,

"The 3.3V (VDD) must be applied AFTER the VIO is applied."

Just to be sure. You are trying to make VDD of LM8335 see 3.3V?

Looks like this device is spec'd such that 2.2V is the maximum the VDD pin is allowed to see before damage occurs.

I assume you are actually trying to make VDDIO see 3.3V in which case you can do this using the VDDIO jumpers by shunting pin 3 and pin 2 together. This is done through the hardware and not the software (GUI).

VIO looks like it is controlled through software as the MSP430 P5.1 (pin6) supplies the 1.8V logic to it. You could probably bypass this by removing R19 and using a wire to connect directly to your own PSU if you wanted.

If you want to power VDD seperately, it looks like you would need to remove R11 and solder a wire to that separately. This would allow you to power VIO first then VDD.

"how do I get 3.3V onto one of the unused GPIO pins on J2?"

Easiest option would probably be to do it directly with a wire/jumper wire tied to 3.3V.

Thanks,

-Bobby

Bobby,
I am using the EVM as interface to test a programmable UHF filter that uses MEMS capacitors as the tuning element. The interface is MIPI RFFE. The 3.3 V is for the Filter under test. All of the above signals are outputs to the filter. The 3.3Vpowers a charge pump within the MEMS.
I need the SDATA and SCLK to be in the 1.8V (VIO) domain.
So I would set the jumper to 1.8V and run a jumper from the 3.3V VDDIO pin to the filter under test.

It would be a neater setup if the 3.3 V came from one of the J2 pins.

So can the GUI be modified to say become a tunable filter GUI? Basically an interface between a input of CH# and a lookup table whose output drives the variable capacitors of the filter.

Thank you for your help,

Stan

Bobby,

Yet another issue with this EVM:

Upon connecting up to a USB port, 3 lights come on indicating that there is 3.3V, 1.8V and VIO. However, there is no 1.8V nor 3.3V on the VDDIO connector pins 1 and 3 respectively. I thought that maybe the GUI needed to brought up so I did so and found that after opening, the Serial # and Firmware version are read AOK. The 1.8V box is green and if the VIO box is checked, the IO status is green. But still the VDDIO pins show no voltage at all. Is there something else that needs to be initialized to bring the DC voltages (1.8V and 3.3V) to the VDDIO connector?

what is the purpose of the reset button? And the purpose of the software reset button on the GUI?

I will appreciate your thoughts.

Thanks,

Stan

Hey Stan,

Lets just do a sanity check to see if VDDIO pin 1 and Pin 3 are connected to GND somehow by doing a continuity check with a DMM on those pins and the GND pin. (They shouldn't be else we have a short circuit). If no then move to the next check below:

"However, there is no 1.8V nor 3.3V on the VDDIO connector pins 1 and 3 respectively."

Can you do a continuity check with a DMM on VDDIO pin 1 (the 1.8V rail) and U5 B1? This will be closest to the R10 (left pad) and U5. We should see that the connection here is low impedance (a short) and then check the Voltage on U5 B1 (R10 pad closest to U5). This should read 1.8V

We should also check continuity between VDDIO pin 3 (3.3V rail) and U4 pin 5. You can probe R9 (left pad) to do this. This should also show that the signal is low impedance. Then probe left side of R9 to see if the pad shows 3.3V.

"Is there something else that needs to be initialized to bring the DC voltages (1.8V and 3.3V) to the VDDIO connector?"

From what I can see, the only thing you need to do to get the 3.3V and 1.8V is the USB Vcc needs to be connected. We may want to see what C11 (top pad) reads in terms of voltage. It should read about 5V if I am correct. If it does then U4 and U5 pin 5 and pin B1 should both be 3.3V and 1.8V respectively.

"what is the purpose of the reset button?"

This will reset the MSP430 which is the MCU used to communicate to the LM8335.

(NFET Q1 sees a positive bias on its gate and turns on which drives the RESET net LOW until the reset switch is released)

"And the purpose of the software reset button on the GUI?"

This sounds like it resets the LM8335, though I am looking at the schematic and trying to figure out how it is doing this. The datasheet mentions if VIO drops below a certain threshold, the LM8335 resets it's state machine and it's internal registers to its default values. It looks like the MSP430 does this by driving P6.0 (or maybe P5.0) low which drives VIO low then drives it back high again. I would have to put these pins on a scope probe and monitor what it does when we do a software reset and see what happens to VIO.

EDIT: Just realized you asked the purpose of a software reset on LM8335, this is incase something happens to the state machine of the device and it ends up out of sync/stuck and the device appears to be unresponsive. Ideally something like this shouldn't happen but stuff like cross talk or noise could couple onto the clock signal and potentially make the device see a rising/falling edge which get it out of sync with the MCU communicating with it. The software reset actually performs a hardware reset to the state machine of the LM8335 and restores it's default register state.

This device/EVM does not get much traffic and this is the first time I've had to support it since we inherited this part from another group in TI. I actually don't have the EVM on hand right now so I am working to see if I can order some to try to get you better support here.

Thanks,

-Bobby

Bobby,

This morning very early I decided to connect the EVM to my RFFE controlled filter and lo and behold the voltages did magically appear at the filter's input pins!!!?? So I am now ready to send some data to the filter. More later ...

I had to go out before I received your msg above. I would have pursued your directions but at this point the EVM seems to be behaving as it should. I am mystified as to why the DVM did not see voltages on the EVM when all 4 green LEDs were lit up.

Thanks for your efforts.

Stan