[SOLVED]I can’t get Flasher Arm to work in Standalone Mode STM32F103VE.

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

  • [SOLVED]I can’t get Flasher Arm to work in Standalone Mode STM32F103VE.

    I can’t get Flasher Arm to work in Standalone Mode STM32F103VE.



    I am trying to program a ST STM32F103VE in standalone mode. I have set the Target device setting for this processor and my Target settings are as follows – Speed before init set for 5 KHz , Speed after init 4000Khz. Using the detailed config (# 0 Dev Name- Cortex M3 ID-0x3ba00477 IRlen -4 , #1 Dev Name- Unknown JTAG Dev ID-0x06414041 IRlen-5). I have downloaded this to the programmer using the option in the file menu of J-FLASH.



    I am able to program the part fine as long as I am programming through the computer. When I disconnect from the computer and only use the USB for Power, I get a not ready FAIL light after about 15 or 20 seconds. I power up the Flasher before the target board is powered up.

    Thanks in advance for any help

  • Hi Jim,

    we had a similar support case with a customer who is using a STM32F101C6T6.

    My questions to you:
    1. Do you use JTAG as target interface?
    2. Do you use a JTAG-isloator?

    If 1. and 2. apply: This is a known limitation, currently there is a problem
    when using JTAG interface + stand-alone + JTAG isolator with a Cortex-M3 target.
    We will fix this as soon as possible and get back to you when a fixed version is available.


    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.

  • Alex,

    The answer to both of your questions is yes.

    The plan is to use this as a production programmer for a new high volume line. We are under the gun to have progamming capibility for production.

    My questions are -

    1) Will you be able to come up with a solution?

    2) If there is a solution, what is the time line?

    Thanks,

    Jim

  • device: ST STR710FZ02

    Hi Alex

    I have a simulair problem that I can make everything work with "J-Flash Arm" Software but not stand alone.

    I always get the following error on the com port:

    ERROR: Unable to halt ARM core
    ERROR: Unable to halt ARM core
    ERROR: Unable to halt ARM core
    ERROR: RAM check failed @ address 0x20000000.

    But then with a device: ST STR710FZ02 via the Jtag
    Can you please let me know if it is the seem root cause or something else?
    I have attached the used files

    Hope to hear from you soon

    Thanks in advance.
    Files

    • segger.zip

      (130.47 kB, downloaded 1,197 times, last: )

  • Hello.

    I seem to have the exact same issue. I wanted to use the stand-alone mode to program the STM32103RB in the production. Unfortunately it doesn't seem to work. When I remove the isolation board, I can program the board (including the option bytes) through the J-Flash ARM. But when I use the "Download to programmer" option and afterwards try to do the programming in standalone, the fail light immediately goes on. I purchased this programmer solely for this purpose, and it's very unfortunately, that the programmer doesn't work as intended.
    So my question goes in the same lines are Jim's:
    1) Will you be able to come up with a solution?

    2) If there is a solution, what is the time line?



    Any quick response will be highly appreciated.


    Best regards,
    Hans

  • Hi.

    I did some further testing this morning. It seems the problem is related to the option bytes. When I have my option bytes placed at 0x06000000 as specified in "UM08003_JFlashARM.pdf" page 59, I get the following response on the comport:

    #STATUS:INITIALIZING<CR>
    #STATUS:CONNECTING<CR>
    #STATUS:UNLOCKING<CR>
    #STATUS:UNSECURING<CR>
    #STATUS:CONNECTING<CR>
    #STATUS:ERASING<CR>
    #STATUS: PROGRAMMING<CR>
    #ERR255: Programming failed @ address 0x08000000 (program error)


    If I however create a firmware without any option bytes, I get the following message:

    #STATUS:INITIALIZING<CR>
    #STATUS:CONNECTING<CR>
    #STATUS:UNLOCKING<CR>
    #STATUS:UNSECURING<CR>
    #STATUS:CONNECTING<CR>
    #STATUS:ERASING<CR>
    #STATUS: PROGRAMMING<CR>
    #OK (Total 2.038s, Erase 0.025s, Prog 1.897s)<CR>

    So in this case the programming seems to work as intended in stand-alone mode. Unfortunately my firmware won't work properly without option bytes programmed...

    Any quick help will be highly appreciated.

    Best Regards,
    Hans

  • Just to give a short update from my side, if anyone should find them self in the same situation.

    I have had some communication with Segger through mail and it seems the Flash can not at this time perform standalone programming through the JTAG. Segger claims SWD is working at the moment though.
    Last update I received an estimated time for a new release should be end of april.

  • Hi Hans,

    sorry for the delay...
    Regarding JTAG interface + stand-alone + JTAG isolator with a Cortex-M3: We are still working on this.
    Regarding option bytes: We will check this again, but in general we are not aware of
    any problems when programming the option bytes (regardless of if this is performed via J-Flash or in stand-alone mode).

    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.

  • Hi Hans,

    sorry for not getting back to you earlier.
    We still do not see any issues with the option byte programming in stand-alone mode.

    Regarding JTAG interface + stand alone + JTAG isolator:
    It is fixed in the latest firmware of Flasher ARM.
    Simply downloaded the latest release / beta version and start J-Link commander in order to update the firmware of your flasher.


    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.

  • It's great that you got the flasher to work with the isolation board. Then we might finally get this programmer put to work.
    But I still have problems with actually programming the board. I'm lost how to get this to work. For debugging, the tool I work with needs the option bytes placed at 0x1FFFF800, but this memory location is rejected by the flasher. How shall these option bytes be specified for the project? Also I want the flash read protected, so verification should be done, before programming of the option bytes. Any idea what I'm doing wrong?
    I have selected the board to "ST STM32F103R8 internal optbytes".

  • You seem to be wrong Alex. Just found this in your latest manual from the 17.2.2011:


    [IMG]http://i55.tinypic.com/152nprd.png[/IMG]

    Apparently you don't support programming of option bytes for STM32. That practically makes the jflash useless for me...

    Best Regards,
    Hans

  • Hi Hans,

    no, we support the programming of the option bytes.
    The J-Link manual needs to be updated regarding this section. I agree that it might the not the best
    solution to have a device specifics section in both user guides because it causes problems like this.

    UM08003 (J-Flash User Guide) chapter "Device specifics" explains what needs to be done to program the option bytes.


    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.