Topic : problem using RLink and uPSD3254A

Forum : 8051

Original Post
Post Information Post
September 16, 2009 - 8:47pm
Guest

Hi,

I´m trying to program a upsd3254A device with a Rlink programmer and Ride 6.1. When I try to connect with the RLINK the test is ok but when i try to connect to target the error "Unable to read device ID for checking." is showed. I try to load the JCI file from psdsoft Express that was ok with a flashlink programmer. When i defined the jci the error showed was " Unknown device number".

help please.

Replies
Post Information Post
+1
0
-1
September 17, 2009 - 2:50pm
Raisonance Support Team

Hi,

Please try to connect using RLink and PSDSoft. If your version of PSDSoft doesn't allow that, you'll need to update it, because it is very old.

The "Unknown Device Number" message says that the number that you entered in the "PSD's ID" field in the options is not found in the jci file. You must select a JTAG device number that appears in the jci file. See this file for more information:
\EXAMPLES\8051\DERIVATIVES\ST_UPSD\AN48-uPSD.pdf

Also in the example applications you will see how to configure the debug options.

Best Regards,

Vincent

+1
0
-1
September 17, 2009 - 3:43pm
Guest

Hi Vincent,

When i try to connect using PSDSoft in HW Setup the connection with RLink was OK but with target shows the error " Communication (0303) Unable to read device ID for checking". I´m using the PSDSoft version 8.66 and my JCI file is:

[JTAG-Chain]
Chain_Device1=uPSD3254A,"C:\Documents and Settings\peccin\Desktop\controlador v060 002\PSDsoft\psdproj.osf",3,0,FFFFFFFF,5,2

[DeviceID]
DeviceID_1=08540047,18540041

[SectorsSizes]
Device1_MAIN_SECTOR0=0x8000
Device1_MAIN_SECTOR1=0x8000
Device1_MAIN_SECTOR2=0x8000
Device1_MAIN_SECTOR3=0x8000
Device1_MAIN_SECTOR4=0x8000
Device1_MAIN_SECTOR5=0x8000
Device1_MAIN_SECTOR6=0x8000
Device1_MAIN_SECTOR7=0x8000
Device1_BOOT_SECTOR0=0x2000
Device1_BOOT_SECTOR1=0x2000
Device1_BOOT_SECTOR2=0x2000
Device1_BOOT_SECTOR3=0x2000
Device1_PLD=0x3760
Device1_USERCODE=0x20

thanks

+1
0
-1
September 17, 2009 - 4:22pm
Raisonance Support Team

Hi,

This message means there is no answer from the uPSD device when the RLink tries to read the JTAG IdCode, which is the very first operation performed when connecting. This message usually comes when there is a power or connection problem. Or when the JTAG chain config is wrong but we ruled that out already.

Note that the fact that you can connect using FLashLink does not mean that there is no problem on the target board: FlashLink and RLink use different output stages, and RLink uses some signals (like TRST) that FlashLink might be not using.

Do you have other target boards to try the RLink? (demo boards from ST, etc.)
That would tell us if the RLink is damaged.

Can you please check that the RST and TRST signals are both connected from the RLink to the uPSD, but that they are NOT connected together? (they are different signals, both required)
Please also check that no other component can interfere on the JTAG signals, especially RST. RLink must be able to drive this signal high or down during the different stages of the communication. Big capacitors and/or serial resistors can cause problems, and reset managers even more.

Best Regards,

Vincent

+1
0
-1
September 17, 2009 - 7:02pm
Guest

Hi,

In the file AN48 (bottom page 3) says that:

"Note that you only need to connect these pins for the ?PSD:
RST, GND, VCC, TCK, TMS, TDI and TDO.
The current version of RIDE does not use the other pins."

Can you confirm if realy need to conect another pins in may target?

+1
0
-1
September 18, 2009 - 10:18am
Raisonance Support Team

Hi,

Yes, you are right, I checked the code and we don't use TRST anymore. I didn't remember doing this. ;/
You must just make sure that TRST remains always low, but I guess it does because otherwise FlashLink wouldn't work.

Then I suggest you check for interferences from other components on these signals, especially RST.

Trying the RLink on other boards would be interesting too.

Best Regards,

Vincent

+1
0
-1
May 19, 2010 - 5:35pm
Guest

Hi,
I have an old RLink-ST that works fine with PSDSoft (latest version) on an XP machine. Now I want to move all my software onto a Windows 7 machine. From your ftp site I downloaded the "Tested for Windows 7" driver. The driver seems to work, after connection of the dongle the Busy light goes off. Unfortunately, PSDSoft does not recognize the device, even when run in Windows XP compatibility mode.

Next thing I tried was to install everything on the virtual XP machine (XP mode), that Windows 7 provides. No problem there in installing PSDSoft, but install of the driver failed. Can you provide some hint on how to solve this problem? My XP machine is eight years old now, and I would hate to have to buy a new computer with XP again.

Thank you,
Ralph

+1
0
-1
May 19, 2010 - 6:13pm
Raisonance Support Team

Hi,

PSDSoft is years old and I would not expect it to work in Windows7 (or Vista), regardless of RLink driver issues.

Still, here is the update of the Raisonance APIs that PSDSoft calls, which is the source of the first error that you report:
ftp://www.raisonance.com/pub/forum/uPSD/PSD2DNG_100519.zip

Find the files with these names in the PSDSoft install and replace them.
You will not find RLinkWinUSB.dll in PSDSoft. It must be placed in the same directory as PSD2DNG.dll.

However, there is absolutely no guarantee that the rest of the software will work in Win7. (or even Vista)

If that happens, you should ask ST if they plan an update of PSDSoft.

If not I'm afraid you will have to keep an XP machine in a corner of your office.

I hope it helps. Please keep us informed of the results of your tests, positive or negative.

Best Regards,

Vincent

+1
0
-1
May 21, 2010 - 11:00am
Guest

Hi VincentC,
thank you for the files, it works now!

What I did was:

- Copy all four files to C:\PSDExpress
- Set all *.bat and *.exe to be handled compatible to Windows XP SP2

After that RLink was recognized, but Easysoft.exe showed a runtime error on termination. I changed compatibility of that program to Windows NT, then there were no more error messages.

Test:
I copied one of my projects to the Win7 machine, and went through the design steps. Everything seems to work. In the end I flashed my hardware: all OK!

Now that we have come so far, I have another question:
Do you know, if the Windows 7 driver would also work on a 64 bit Windows 7 system?

Best regards
Ralph

+1
0
-1
May 21, 2010 - 11:40am
Raisonance Support Team

Hi,

Glad to know that it works.

Thank you for the testing and reporting.

The Raisonance APIs should work in Win7-64. I don't know about PSDSoft.

In any case, I would recommend NOT to install in the default directory from Windows, as it contains parentheses ("Program Files (x86)") and many old applications don't support this.
"c:\PSDExpress" is fine. You'll probably have to change the access rights, owner or other things, because Windows will "make your life interesting" in this folder.

Best Regards,

Vincent

+1
0
-1
May 21, 2010 - 1:14pm
Guest

Hi,

in case I have to run PSDSoft in the virtual XP machine of a 64 bit Windows 7:

Do you have any suggestion, why the XP driver does not work in this machine? After connecting RLink and finalizing installation, I get a message: "Device could not be started, Error code 10". In Device Manager I see the Jungo driver installed with a questionmark.

Thank you,
Ralph

+1
0
-1
May 21, 2010 - 1:39pm
Raisonance Support Team

Hi,

XP64 is not supported at all.

You will have more chances of success in 'pure' Win7-64.

Vincent

+1
0
-1
May 21, 2010 - 2:36pm
Guest

Hi,

may be a misunderstanding?

If I remember correctly, there never was a 64 bit version of Windows XP. I was refering to "XP Mode", a virtual Windows XP (32 bit) Computer, that can be run under 64 bit Windows 7, see
http://www.microsoft.com/windows/virtual-pc/default.aspx

Which is the latest version of the Jungo XP driver and where can I find it? I followed the instructions for driver removal several times and installed different version from your FTP-Server, but it always is 6.2.0.

Best regards,
Ralph

+1
0
-1
May 21, 2010 - 4:14pm
Raisonance Support Team

Hi,

Yes there has been a XP64, but it never catched. (no drivers, no software, no users, etc.)

I wonder if the XP emulation of Win7-64 is XP-32 or XP-64.
From what you report, it might be XP-64.

If not, then the problem might be that the emulation is not as transparent as you expect.

Did you run the installer or did you try to point Windows to the inf? (the second option cannot work and would give the result you describe, even on a "real", non-emulated XP32)

Try also installing the WinUSB driver, designed for Win7 and Vista, rather than the Jungo that is for XP. Run the install of the driver in normal Win7 mode, not emulated XP. The problem with the WinUSB driver in XP is the installation. But it works in XP, if you manage to install it.

The driver that we provide is version 7.0.0, but we plug to it in legacy mode 6.2.0.
As a result it can appear as version 6.2.0, depending on how you display its version.
Anyways, the problem you describe is not something that happens with 6.2.0 but not with 7.0.0.

Best Regards,

Vincent

+1
0
-1
May 21, 2010 - 5:02pm
Guest

Hello Vincent,

right now I am trying this on a 32 bit Windows 7, which surely has a 32 bit Windows XP. This is why XP Mode was introduced, to make old software and drivers run on Windows 7, preferably in seamless mode, using Win7 desktop with the virtual machine running in the background providing XP services.

I have used the installer.

I have also tried the Win7 package from your website, which I already successfully installed in Windows 7. There is no such thing as Win 7 mode in the virtual XP machine: it is a licensed Windows XP SP3, the user is connected to it via a sort of Remote Desktop Technology. On top of the XP desktop there is a "USB" button, which opens a list of devices one can choose to connect to XP. RLink shows up there. See
http://blogs.technet.com/windows_vpc/
for further info, also about USB architecture.
So, when I run the Win 7 driver package, it discovers that it is on a XP machine and installs accordingly. Only thing is, it does not work. Is there a way to have the real Win 7 driver installed in XP?

Best regards,
Ralph

+1
0
-1
May 21, 2010 - 6:15pm
Raisonance Support Team

Hi,

You can install the WinUSB driver in XP, but for that you have to patch the kernel with the core WinUSB driver, which requires a quite complex procedure because you must sign the dll. (even though it comes from Microsoft)

For that you need to have the Windows Driver Development Kit installed on the PC, and know how to use it.
I don't recommend it unless you are experienced in Windows drivers.

And I'm doubt very much that it will work in a virtual OS.

On our side we never managed to have anything work properly with USB in virtual versions of Windows, and of course we don't guarantee that our tools can work at all in these context.

Sorry, but you'll probably have to stick with real Windows, not virtual.

Best Regards,

Vincent

+1
0
-1
February 1, 2011 - 11:31am
Guest

Hi, I've got the same problem as Ralphc, I must use PSDSoft Express 8.66 on Windows 7 but it doesn't recognise my Rlink. I wanted to try the update of the Raisonance APIs that you gave to make it work like ralphc did but I can't get the .zip file.
Would it be possible to upload the file again or maybe send it to me via email ?
Thank you, I'm looking forward to your answer, as it is very important for my company !

+1
0
-1
March 21, 2011 - 5:30pm
Guest

VincentC,

the ftp link is not working. Can you update or repost the files please?

TIA

+1
0
-1
March 21, 2011 - 5:39pm
Raisonance Support Team

Hi,

Indeed it seems that someone was over-enthusiastic in cleaning our ftp. ;(
Sorry RémiB I didn't see your post before.

Here are the files:
ftp://www.raisonance.com/pub/forum/uPSD/PSD2DNG_100519.zip

I will also correct the link in the older post.

Best Regards,

Vincent