Forum : ARM
Original Post
| Post Information | Post |
|---|---|
|
September 22, 2016 - 5:13am
|
Ride version is 7.60.15.0327. RKit-ARM version is 1.64.16.0245. I am having a problem with programming/debugging an STM32F303 part after installing the latest version of RKit-ARM. Previous version 1.62.15.0334 is fine. Current version 1.64.16.0245 erases the micro, appears to program the micro, then the debugger faults with error 82 and exits. That may be error x82, I am not sure. Tried it on more than one board/project. After several complete removals and installs I got it to work but had to use the earlier 1.62.15.0334. (Not sure if I am in the right forum because I am not seeing a complete web page. Some links have no info graphic, just a grey rectangle.) |
Hello,
Thank you for the feedback.
The Ride7 version wasn't updated, please try to install the right version of Ride7 (http://support.raisonance.com/content/ride) and the Rkit-ARM (http://support.raisonance.com/content/rkit-arm) then try again to program your device F303.
If you still encounter some programming issue, could you please give us more information about it:
Are you using Ride7 or RFlasher or Cortex_pgm.exe to flash the micro? could you provide the entire error message? a screen shot? could you describe the steps you are doing to reproduce the issue
Concerning the grey rectangle, I don't understand, could you provide us a screen shot?
Thanks
Regards,
My web page problem went away for some reason.
I didn't get the Ride7 update. My bad. I use F-Link.
So I did. Ride7_7.64.16.0244.exe, RKit-ARM_1.64.16.0245.exe.
And I still get this using RFlasher7 or Ride7.
Sorry I don't know F-Link, could you give us more information about it?
You have to know tha Ride7 and Rkit-ARM support only R-Link or ST-Link debugger
Regards,
Sorry, typo. Should say R-Link. (Too much late night stuff) I am using the standard package with R-Link as provided. I can roll back to February(?) edition and everything is fine.
Could you please fill the form provided in our FAQ http://support.raisonance.com/content/what-information-should-i-collect-requesting-rlink-support and send it at support@raisonance.com
Thanks
Regards,
I experienced the same problem.
I uninstalled and reinstalled 1.62.15.0334
Please notify when fixed. We have a project that requires STM32L4 and we need the latest version soon.
Thanks
Hello,
We need to have more information about your issue. could you fill the form http://support.raisonance.com/content/what-information-should-i-collect-requesting-rlink-support and send it at support@raisonance.com
Did you encounter problems with STM32F3 or STM32L4 devices?
Best regards,
The problem was with 2 projects that use the STM32F303
Unfortunatleyl I dont have much more info than what I posted here. After building, the code downloads and at the end pops the window that the other user posted above.
It does appear that the code did download into the MCU. I am fairly sure that after cycling the power, the MCU was running.
We need to have more information about your issue,
It can be an hardware issue (Rlink), software issue (Ride7 and Rkit-ARM), both issue or none of them. The form (link provided above) will help us to know if it is an hardware issue and ask for software thing. without these informations we can do nothing.
We test the STM32F3 device and we didn't encounter any problems.
Best regards,
We loaded the new Ride on another PC and we see the same issue. The problem even happens when using RFlasher. Programming completes but the error happens at verification. So to date we've seen this on 2 different Win10 PCs with two different ST-Links. Problem happens when target is F303. It works OK with F103.
I am sending the full report form.
Looking forward to a fix. We cannot delay moving to the new version much longer. Thank you
Hello,
We are doing our best to solve this issue. I will send you a patch as soon as possible.
BR
Hi,
I have the same problem on F334x8. (NUCLEO-F334R8)
Hello,
When the solution might be available? We can not start a project on the target device :-)
Best regards
Hello,
A beta version of the next release of RKit-ARM is in pre-validation and will be available in the coming days for cutomers who wish to participate in the testing.
This version will both correct F3 and support L4, but will not be officially fully validated before several weeks.
You could be interested in participating in the testing if you need to work with these two devices on the same PC in the short term, at the risk of bugs or regressions inherent to beta status. (If you only need F3 but not L4, using version 1.62.15.0334 should be fine. if you only need L4 but not F3, 1.64.16.0245 should do it. keep one f these until the next official release unless you really need both)
All customers interested in the beta are invited to send an email to with a link to this topic in the text.
Best Regards,
Vincent,
Raisonance support