Forum : ARM
Original Post
Post Information | Post |
---|---|
April 28, 2010 - 9:37am
|
Dear Sirs, I had become crazy trying to debug the application cause the rlink in SWD mode break the connection to the mcu. Then I tried the JTAG connection. The rlink don't loss the link but when the application is in stop mode when I try to read some dinamyc variables (varables locate in stack), the ride change is state in application running but the application itself don't run..... Then I found that the rlink stop woking fine when it access the last 8 byte of the RAM, also just after a poweron reset. Anyone has issued this behavior before? |
Hi,
This kind of problem was never reported before.
For sure on my boards I can access the last 8 bytes of RAM, but it's not supposed to go on debugging if a power-on reset occurs.
We will need more details for helping you. (software version, connections, error messages, etc.)
Please answer the questions from this form:
http://raisonance-forum.xsalto.com/viewtopic.php?id=2231
Best Regards,
Vincent
Reading your list of messages I've found the device is driven by the RLinkWinUSBDevice driver. Now I try the Jungo One (Rlink USB). I'm running under Window 7.
Hi,
DO NOT try this:
If you had the wrong USB driver, you would not be able to connect at all. It would not make problems like you describe.
Moreover, RLink+Jungo cannot work under Windows 7. not the slightest chance.
Finally, there is a good chance that while trying to change the driver, you break the previous one, which is working fine: the problem is somewhere else. (probably in the PC software, or in the target board or RLink hardware, but not in the USB driver)
Please send us the answers to the form.
Best Regards,
Vincent
OK. Thanks.
Another thing that i've found is that if I setup RIDE for ST32F101R6T6 device, all work fine, except that i can use only 6kiB of ram.