No boot after programming STM32 with JFlash

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • No boot after programming STM32 with JFlash

    Hi guys,

    I'm using JFlashARM.exe in command line with these options :

    Source Code

    1. JFlashARM.exe -openprj"****.jflash" -unsecurechip -open"****\firmware.bin",0x8000000 -auto -disconnect -exit


    The programming is OK, but the STM32F407VE never boot after that. JFlash say that the application is started. I must unpower and power again to start the board.
    I have the same problem with STM32F103VE.
    I'm using the latest version of JFlashARM (4.80) and JLink v8.0
    The project file is attached and here is the log from JFlashARM:
    Connecting ...
    - Connecting via USB to J-Link device 0
    - J-Link firmware: V1.20 (J-Link ARM V8 compiled Nov 25 2013 19:20:08)
    - JTAG speed: 4000 kHz (Fixed)
    - Initializing CPU core (Init sequence) ...
    - Executing Reset (0, 0 ms)
    - Initialized successfully
    - JTAG speed: 4000 kHz (Fixed)
    - Connected successfully
    Auto programming target (195504 bytes, 1 range) ...
    - Unsecure chip ...
    - Disconnecting ...
    - Disconnected
    - Connecting via USB to J-Link device 0
    - Chip unsecured successfully
    - Erasing affected sectors ...
    - Connecting ...
    - Connecting via USB to J-Link device 0
    - J-Link firmware: V1.20 (J-Link ARM V8 compiled Nov 25 2013 19:20:08)
    - JTAG speed: 4000 kHz (Fixed)
    - Initializing CPU core (Init sequence) ...
    - Executing Reset (0, 0 ms)
    - Initialized successfully
    - JTAG speed: 4000 kHz (Fixed)
    - Connected successfully
    - 6 of 8 sectors affected, 1 range
    - Affected sectors 0 to 5 (0x8000000 - 0x803FFFF)
    - RAM tested O.K.
    - Erase operation completed successfully
    - Programming target (195504 bytes, 1 range) ...
    - Target programmed successfully
    - Verifying CRC of affected sectors ...
    - 6 of 8 sectors affected, 1 range
    - Affected sectors 0 to 5 (0x8000000 - 0x803FFFF)
    - CRC of affected sectors verified successfully (CRC = 0x3706E77B)
    - Secure chip ...
    - Chip secured successfully
    - De-initializing CPU core (Exit sequence) ...
    - De-initialized successfully
    - Target erased, programmed and verified successfully - Completed after 19.634 sec
    - Starting application ...
    - Disconnecting ...
    - Disconnected
    - Connecting via USB to J-Link device 0
    - Target application started
    Many thanks for your help

    Best regards

    Patrick
    Files
    • project.jflash

      (1.89 kB, downloaded 669 times, last: )
  • Hi,

    Be patient... we all have work to do...

    I have seen this behavior on the STM32 devices before.
    After securing the device, it seems they need a power on reset in order to boot correctly.
    It seems to have something to do with changing from unsecured state to secured state.
    So far, there is nothing J-Link can do to work-around this. A power-cycle is simply necessary to start the application, in case target state is changed from "unsecured" to "secured".


    - Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hi Patrick,

    Sounds like a good plan to have this done at boot time.
    Anyhow, I do not think there is a real work-around for this
    but this problem is not a blocking problem, it is just a uncomfortable behavior.
    So right now, just something users of these devices have to live with...


    Best regards
    Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.