MSP-FET: Error initializing emulator

Part Number: MSP-FET

Hi Team,

This inquiry is related to the other threads below. It is from the same customer.

https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1070624/rf430f5978evm-spi-is-not-working

https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp-low-power-microcontrollers---internal/f/msp-low-power-microcontrollers---internal-forum/1072322/bsl-connection-of-rf430f5175 

According to our customer,

I still believe that I will get an answer to my BSL question.
And that's what worries me except that WAKE does not work.
I have an MSP-FET in the photo I attached earlier you can see it.

From your link I downloaded the DLL and ran the test application
example.exe
I see an error message on the screen
and the strangest thing is that if I run 2 programs Example.exe

then I see an inscription that MSP-FETUIF is not found.
But I only have MSP-FET without UIF.

Does this mean MSP-FET cannot work with MSP430.dll ?
And if it's not, why am I getting error 10 ?

and further, I am interested in connecting via BSL, since there is no complete information about what and where should be connected.

if i use SBW with MSP430Flasher.exe you can see that Vcc is being applied, which means my MSP-FET is working correctly.

PS:
RF430F5978 still doesn't work and I would like to see the EOBA signal for analysis, but I didn't manage to do that either. I really hope for your support.

Regards,

Danilo

Error 10 is because there is some problem related to setting VCC, however I don't see this problem with MSP430Flasher so I guess that everything is OK. If setup in both cases is identical.

Error 57 is because device related to MSP-FET (or UIF or eZ-FET) is not enumerated by PC side (device with related PID / VID). There is only UIF in error message, but it is related to all FET's.

Try it with new installation of MSP430Flasher on clean PC, with last MSP430.dll version.

Hi Jace and Zrno,

Thank you for your feedback. According to our customer,

Regarding MSP430.dll

Only a msp430fx5xx is used as a load, the supply current is very small.
The same behavior occurs without connecting the msp430fx5xx.

UniFlash Version: 7.0.0.3615
MSPFlasher Version: 1.3.20
CCS Version: 11.1.0.00011
msp430.dll_developer_package_rev_3.05.000.001

If possible, give more detailed instructions on what I should check.
MSP-FET works under CSS.
also it works with MSPFlasher
does not work only with msp430.dll

I had no experience with the TI MSP430 before, so I can do something wrong.
I need BSL as a programming tool, I have an MSP-FET, I am looking for a working solution.

Nothing works out for me again with TI :(
but I'll start in order.

So I have RF430F5175 and I am sure it will work.
But he has LOCK SBW JTAG.

I have an MSP-FET and I hope to clear the RF430F5175 and UNLOCK SBW JTAG

I found that only BSL_Scripter (SLAU655G) works with MSP-FET (BSL)
so i connected with target as per
Table 3. Connection of MSP-FET and MSP430FR5739 LaunchPad Development Kit
BSL-RX signal I connected on pin 14 (P3.6)

I used script file:
MODE 5xx UART COM7
MASS_ERASE
RX_PASSWORDBSL_PASSWORD.txt
RX_DATA_BLOCK BSL_UNLOCK.txt
RX_DATA_BLOCK JTAG_UNLOCK.txt

where BSL_PASSWORD.txt
ff ff ff ff
q

BSL_UNLOCK.txt
@0182
03
q

JTAG_UNLOCK.txt
@17FC
00 00 00 00
q

All signals are verified by logic analyzer control.
Commands and format conform to MSP430F5xx

But JTAG is still in the LOCK state.

I'm attaching the script files, I hope I'm wrong somewhere.

BSL-Scripter.rar

in addition, I also tried to send 32 bytes FF as a password
in script
RX_PASSWORD
and I checked it with a logic analyzer.

After I decided to check if everything is in order with my understanding, and connected the BSL to the RF430F5978
it has P1.5 Rx and P1.6 Tx
I saw that in this case everything works

I disconnected the TX so that the acknowledgment signal did not come, programmed the RF430F5978 and checked the reset.
deletion also happened.

thus, the presence of a TX signal is not mandatory, which made me happy.
But my RF430F5175 is still not reset.
I ask you to once again ask the engineer who answered the question on BSL RF430F5175 to check if everything is correct.

I ordered new RF430F5175 from Aliexpress 2 weeks ago but they haven't even shipped yet.
I'm hoping to clean up my existing RF430F5175 to get started with it, since the RF430F5978 seems to have some kind of bug.

by MSP430.dll
By scientific pointing my finger at the sky, I found a problem with the DLL.
so the latest version available for download msp430.dll is 3.5.0.1
If you receive a package via UniFlash, there is a folder with
msp430.dll - 3.15.1.1
and MSPFlasher.exe 1.3.16
they are in the same folder, but when running MSPFlasher.exe, an error occurs.
reason - msp430.dll - 3.15.1.1
If you download MSPFlasher.exe separately
then after installing it it has version 1.3.20
and located in his folder msp430.dll - 3.14.0.0

you understand how illogical everything is
UniFlash offers a newer version of msp430.dll with an older version of MSPFlasher.exe which do not work together.
The msp430.dll SDK offers an older DLL, but Example.exe does not work with its msp430.dll.

And only msp430.dll - 3.14.0.0 from MSPFlasher.exe 1.3.20 package works with Example.exe.

It looks funny, but it's very sad.

Regards,

Danilo

Hello Danilo,

The standard tools for MSP430 may or may not support the RF430F5175. I'm alerting the team that knows more about this part so they can comment on it. 

Danilo, Jace,

the RF430F5175 is supported by in CCS.

As far as I know JTAG unlock via BSL is not possible due to the missing TX pin.

Danilo,

was the JTAG locked with a password and do you know the password?

If so, then you can alternatively unlock the JTAG in CCS with the corresponding TargetConfig modification.

Best regards,

Andreas.

Hi Andreas,

We have received this feedback from our customer,

Let's talk about connection.
The general picture shows and says that pin 14 BSL_RX is an output signal,
and it must be connected to the RX target.
For RF430F5978 it is P1.5
for RF430F5151 it is P3.6
for RF430F5175 it is P3.6

The Tx signal returns the ACK as well as the BSL version and is used for that read.
I wrote that I checked everything on RF430F5978 and it works.
And I also checked everything without connecting BSL_TX
and it still works!

And the question remains the same, what am I doing wrong.
Let me remind you that I also tried 32 bytes of the FF password.

In CCS, I did not find where you can set the password for JTAG
I ask you to show me this place.
But it seems to me that if a password is used for JTAG, then we should talk about FRAM And in our case this is not so.
Everything would be easier with documentation, but I try to search from available sources.
Therefore, I can perceive everything incorrectly, therefore I ask for a broader answer.

Regards,

Danilo

Danilo,

you are mixing up devices here too much.

Automotive devices are not handled in this public forum.

If this RF430F5175 device requires failure analysis, then please let the customer send it back through the TI quality channels.

Best regards,

Andreas.