Topic : Problem with RFlasher 7 and STR731

Forum : ARM

Original Post
Post Information Post
May 5, 2011 - 12:06pm

Hello All

We have problems with programming our boards when using the newest tools.
The development was done using Ride 6 (BN 747) and Rlink-Pro and all worked well.

The situation is now:
Board 1: STR710FZ2, RFlasher 6, "old" RLink-Pro, --> works well
Board 2: STR731FV2, RFlasher 6, "old" RLink-Pro, --> works well

We have already delivered many such boards to customers and our service personal has to do software updates from time to time. To do so, they bought new Rlink-Standard which only work with RFlasher 7.
Now, we have this problem:
Board 1: STR710FZ2, RFlasher 7, "new" RLink-Standard, --> works well
Board 2: STR731FV2, RFlasher 7, "new" RLink-Standard, --> does not work!

When connecting to Target we get an error message that it can not read the Debug controller status.

I found out that I can get it working by removing the transistor which pulls down "JTRST" when "RESET" is low.
We introduced this circuit in our design according to some application note or reference designs. It guarantees that "JTRST" is low as long as "RESET" is low.

--> Has something changed in the programming routine from RFlasher 6 to 7 ?
--> Has something changed in the programming routine from "old" RLink-Pro to "new" RLink-Standard ?

--> Is there a way to solve this issue by Software? (It is not very convenient to remove SMD transistors on customer site...)

Thanks for the help.

Post Information Post
May 16, 2011 - 10:54am
Raisonance Support Team


TRST (=JTRST) and RST (=RESET) are two independent signals and they MUST NOT be connected to each other. Doing what you did prevents the RLink from accessing the JTAG while keeping the CPU under reset, which is required in the normal procedure. Indeed some reference designs do that, but usually they include a jumper for cutting the connection. A few of them don't do this, but these are designed to prevent reprogramming and debugging. (and few of the older ones are just wrong!)

So your schematic is not valid, and I'm surprised that it works with the old tools. In theory they should not work.

Moreover, there is no reason why the new RLink wouldn't work with the old software.

Also, I see no reason to have a different behavior between these two sets of tools.

To go further we need to understand how your old tools worked on this board...

Please tell us the versions of your old and new software. (Help/About)

Please try your new RLink with your old software and tell us if it works. If not tell us how. (error message, etc.)

Please also try your old RLink with the new software and tell us if it works. If not tell us how. (error message, etc.)

Please inspect the old RLink and its adapter and see if something was modified. (pin cut off...)

Then we will know if the difference lies in the software or in the hardware, and I will have other questions...

Best Regards,