Flash Loader Demonstrator Free Download

[Mirtha Shikles]

Iam not able to get the ST Flash loader to recognize the STM32 on the MP32. I get the following error: "No response from taget, the Boot loader can not be started. Please, verify the boot mode configuration and the flash protection status ...".

Regarding B, this seriel configuration is working when I connect to either of the usarts on the StmDiscovery board. In fact on the discovery board, with respect to usart#1, I am connecting to pins Pa9 & Pa10 (same as MP32).

I am noticing that when I press next on ST flash Loader I can see the Tx and Rx blip momentarily, and then the Rx led on the 232-ttl converter stays on slightly dim (until I press the reset button on the MP32).

I tried several different buad rates in Flash Loader, but didnt have any luck. Also, I tried all the above on my deskop (which has serial ports). I used the same level shifter at the end of the cable. In all the above I also tried switching the Rx and Tx going to the MP32 (in case I had them backworks)s. I even tried pressing the reset after powering the board up, before trying the use the Flash Loader.

The only thing I didn't think of until now (editing post) is that on the Discovery Board I powered the 232=ttl convertor at 3.3. When connected to the MP32 it is being powered at 5. What level is the usart at?

I am having a problem communicating with my board using flash bootloader. I am designing a breakout board for the STM32F103RB, I have the UART1 pins out so I can use flash programming rather than JTAG, but I am having no luck with ST flash programmer it gives me different problem messages..

1) "Unrecognized device...please, reset your device then try again"

2) "No response from the target, the boot loader can not be started. Please verify the boot mode configuration and the flash protection status, Reset your device then try again"

3) "Cannot get available commands, please, try to change echo selection, reset your device then try again"

Board:

====

I have a custom made board, which I confirm is working since I have the JTAG pins out as well and was able to connect and program it using Olimex ARM-USB-OCD + Eclipse

My 232-TTL level shifter did not like being powered on the 5v bus as depicted in the picture above. I guess the converter I bought isn't as smart as a max232. After getting some sleep I looked at the differences between the config above and the Discovery board, and realized the diff was that on the discovery board I was using 3v3 (NOT 5v).

I actually experience the same problem, i.e., the Flash Loader Demonstrator won't always recognize the MP32. Sometimes I have to try several times until it finally recognizes it. I am also using the 5V output of the MP32 as the power supply for the RS232/TTL converter.

Hint: There is a tool that will display all the communication of the serial/RS232/COM port(s) of your Windows PC. It is originally made by two very smart guys, who sold their company to Microsoft some time ago, so the tool can now be found there. However, the old web site still works (and gets redirected to MS): www.sysinternals.com - go to the Utilities Index and download the PortMon tool. No need to install, just unZIP and run.

We arrive in a situtation that the flash memory entire in a ReadProtection state because there was a power supply failure. After apower reset, the system is in Flash Read Protection and we would liketo disabled this protection without Flash Loader software and withoutto do an erase mass.

We arrive in a situtation that the flash memory entire in aRead Protection state because there was a power supply failure. Aftera power reset, the system is in Flash Read Protection

sounds strange, which chip?

and we would like to disabled this protection without FlashLoader software and without to do an erase mass.

the whole point in protection is that you can't disable it "withoutto do an erase mass" otherwise it would be worthless.

The IC is the STM32F103RG. This situation appear when from IDEuVision or directly from our application you are downloading yourprogram into the flash (writing) and suddently the power is switchoff because your input power is failted or another reason. At thenext power on, the flash is in the state "Read Protection mode". Inthis situation in our case, is cathastrofic also because the systemwhen you disable this protection, erase all de flash (mass erase),and because the only way to disbled the read protection is to changethe parameter (Options Bytes) with the Flash Loader demonstrator.

This situation appear when from IDE uVision or directly fromour application you are nloading your programo the flash(writing) and suddently the power is switch off because your inputpower is failted or another reason. At the next power on, the flashis in the state "Read Protection mode". In this situation in ourcase, is hastrofic

this makes no sense whatsoever

1) how often does the power cut off while you are downloading.

2) since you can download, a mass erase followed by a download willtake care of it - hardly 'catastrophic'

3) I tried switching power off during a download to astm32f103 and - lo and behold - the chip did not get readprotected, I just repeated the download.

So a mass-erase is a well working solution for a developer. Butmay not help with shipped devices

if, indeed, this happens at a "customer upgrade" I do see theissue.

however, out of curiousity I tried cutting power during a download ofthe same chip and nothing happened.

Yes, I would think that it is common practice that thecharge-pumps in the chips holds enough memory to perform one flashwrite operation on stored power, in which case the chip shouldn't endup in some random lockup state.

verify sufficient decoupling, whatchdogging etc is inplace

I have seen strange effects from the above, e.g. I have seen anexample where a 3cm trace to the decoupling cap was enough to causeproblems. As a general rule, when someone exposes me to somethingunexplainable I ALWAYS check the decoupling and, if anything is notPERFECT, solder caps directly across the chips. this has "solved theunexplainable" more than once.

- In Circuit Programming(ICP), with tha JTAG or SWD protocol

- In Application Programming (IAP), with differents communicationschannels like UART,USB, etc.., in this cas the CPU must to be inSystem Memory boot.

- With intructions in your applicattion like FLASH_ProgramWord,etc..

With the uVision IDE during downloading the program with JTAG orSWD, if you switch off the power supply, immediately the flash memorychange to Read Protection State. The only way to disable the ReadProtection is with the Load Flash Demonstrator Software from ST.After to disable the read Protection the FLASH memory is erased (masserased).

Once restored the stock bootloader you will be asked for a License number that is calculated starting from your Hardware Serial number. In order to know it you can use the SYS FW 2.50 I modified to show you at startup the License number further to the Serial number.

you will be asked for a License number that is calculated starting from your Hardware Serial number. In order to know it you can use the SYS FW 2.50 I modified to show you at startup the License number further to the Serial number.

For those who want to save their current state including DFU / License data etc. it is nice to have an archived dump file for emergency use with the serial port flash technique. This is a bit easier than starting with a stock DFU.

Comment: In principle you can use any GUI version to flash any version of the firmware. However, a GUI which is of the same or higher version than the firmware provides easy access to the firmware via the selector fields on the [Flash Firmware] window.

Comment: We are talking here about the [Com Port] field in the [Flash Firmware] tab, not the [Port] field in the lower left of the main window.

Comment: If you are not sure which the correct COM port is, then disconnect the usb-ttl adapter from the PC, inspect the drop-down list and memorize the available COM ports, connect your adapter and wait until its enumerated by Win, and finally inspect the drop-down list and chose the newly added COM port.

Now a black window (DOS console) should open and run the flash loader program, as shown in the screenshot. Wait until it's finished (takes some seconds). If the program doesn't proceed and asks to "Press any key to continue" the board is write protected. See "Removing Write Protection" below.

12. The STorM32 board will be reset and start running. If this is the first-time flash of the firmware and if the board is connected via USB to a PC, then Win 7 will immediately start with installing the appropriate USB driver. This takes quite a while (several minutes). Please, be patient and wait until Win 7 reports that the device is ready for use. Do not disconnect the board from the PC or otherwise interrupt the driver installation process before it is completed. This can mess up things quite considerably, and installing the driver later can be a challenge.

The Micro STorM32 board doesn't provide BOOT0 and RESET buttons. Here, BOOT0 must be shortcut to 3.3 V by e.g. soldering a wire as shown in the picture below, and powering up the board to bring it into bootloader mode.

3. Start the Flash Loader Demonstrator, choose the correct COM port and then press the Boot0 and Reset buttons on the controller as described in step 10 under Flashing Firmware using a USB-TTL Adapter. Click next.

Some boards are unfortunately shipped with a read/write protection on the flash. As a result, storing parameters permanently in the board and flashing new firmware will fail. To remove the protections do the following:

3a8082e126