Topic : Rlink connection problem to non Raisonance eva-board

Forum : ARM

Original Post
Post Information Post
November 18, 2009 - 7:27am
Guest

I have a Reva kit v2.0, that works very well.

I then bought some STM32-P103 eva bords from Olimex, that I cant program with the R-link shipped with my Reva 2.0 starter kit.
When I start a debug session, I do get up the debug window, (In running state).
If I then klick stop or reset, in the message window message "Out of code" is displayed and the PC is 0xFFFF somthing...
If I have a program in flash, it's erased, but the new program is not loaded.

My code is very tiny, it just flashes a LED, so it's not the 32k limit.

I have notised that JTCK have a pull up on the olimex bord, I changed that, I also changed BOOT1 from low to high (even if it should not matter when BOOT0 is set to low). So no the to boards should be rather simular.

I borrowed a frends emulater (a I-One from I-system) that works fine with both my old R-eva and my new Olimex boards, with the same code as faild with R-link!!

None of my home made target system's works with the R-link either, despite they work with my frends I-One.

Is there some kind of hardware lock in the R-eva kit, so I cant use R-link to another board??
I have not been able to find out any other differences.
Replies
Post Information Post
+1
0
-1
November 18, 2009 - 9:57am
Guest

Hi

Have checked this post http://raisonance-forum.xsalto.com/viewtopic.php?id=2497
With Olimex boards it is often the issue.

Regards,
Matloub
+1
0
-1
November 18, 2009 - 10:06am
Raisonance Support Team

Hi,

There should be no problem for doing this. Just make sure that you keep the two jumpers on the RLink part in JTAG configuration, as they were when you used the REva board. Also make sure that either you break the RLink from the eval part of the REva board, or that you remove everything from it (jumpers, daughterboard, cables, etc.)

I looked at the schematic of the board and found two possible sources for the problem.

1. The R-T jumper MUST NOT be set. It connects RST to TRST, which should never ever be done as it will prevent correct JTAG (or SWD) communication.

2. The U2 component might be interfering on the RST signal. Do you have its reference? Would you be able to unsolder it cleanly, just to see if it makes a difference?

I don't think the pullups would be a problem, but you can remove them if you want, as the RLink includes some too. (4K7)

You should also try both JTAG and SWD modes. (turn power Off and ON when switching)

I suggest you make your tests using RFlasher. You'll have easier access to the options and basic operations (Erase/Program/Verify/Run) and probably clearer error messages too.

Please let me know if that helps.

Best Regards,

Vincent
+1
0
-1
November 19, 2009 - 7:53am
Guest

Thanks Vincent,

It turned out that the reset circuit U2, was causing all the problems!

Best regards
Ola