Welcome to the Raisonance Support Website

Topic : RFlasher says it's programmed STM32 but hasn't.

Forum : ARM

Original Post

Post Information	Post
August 25, 2010 - 5:05pm Guest	Folks, I have written code for an STM32 with Rowley's Crossworks. I am nowt attempting to program the software into the device. It works perfectly if I use Rowley's Crossconnect. If I take the hex file and program the device using RFlasher it claims it has programmed the flash, but something is not right because the unit does exactly nothing! I have tried both .hex and .bin files both generated from Crossworks, but to no avail. Anyone seen this behaviour before? Anyone have any pointers? It says I am connected, I can verify the code, run the processor and it says it's running, but the unit simply doesn't run. I hope and trust that RFlasher doesn't use some proprietary hex and bin format that no-one else generates. Many thanks, Rob

Replies

Post Information	Post
+1 0 -1 August 25, 2010 - 5:44pm Raisonance Support Team	Hi, Yes RFlasher uses the standard hex format spec. Forget about bin files. They work in RFlasher but it's easy to make errors when manipulating them. What you describe could happen for many possible different reasons. We will need more information for helping you... Please first confirm that you are using the latest versions of both the Ride7 and RKit-ARM software. (available on the Raisonance website) Do you see the code in the RFlasher memory view at address 0 or 0x08000000 after loading the hex file in the memory of RFlasher? (RFlasher only programs the Flash, not the RAM) Please try to cross-verify between RFlasher and CrossConnect: Program with one and verify with the other. (try both ways) That will tell you if the problem is in the programming (if the verify fails) or in the launching of the execution. (if the verify succeeds) Please also try to see if the program executes after power-on. If the programming is fine but the problem is in the launching, then it should work after power-on. Try both after programming with CrossConnect and with RFlasher. If all this doesn't help, then we will need you to send us (support@raisonance.com) a hex file that shows the problem, and the schematic of the board. (at least the STM32 with power, clock, reset and JTAG connector) Best Regards, Vincent
+1 0 -1 August 25, 2010 - 10:57pm Guest	Many thanks for the reply, Vincent. I sussed it. I hadn't set the #define in the startup file to run from reset. I could have sworn that I had a board running without Crossconnect attached but maybe I didn't. Once I'd done that it worked fine. Thanks again. :)