[SOVED] Unable to program in stand-alone mode

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

  • [SOVED] Unable to program in stand-alone mode

    Hi,

    I'm trying to configure the Flasher Portable PLUS in stand-alone mode.
    It works when it's connected to PC but I can't make it work in stand alone.
    I've configured all related settings and downloaded config & data files to flasher. Then, when I try to flash it, flasher gets stucked showing 'Connecting...' in the screen. When this occurs I can see that the device is reset -if I've previously flashed my app-

    I've tried to erase the device before performing the stand alone flashing but the same occurs.
    The log file is blank so I don't have any clue.

    My target is a Renesas R7FS7G27G and here is the J-Link commander output:

    SEGGER J-Link Commander V6.14d (Compiled Apr 19 2017 18:26:24)
    DLL version V6.14d, compiled Apr 19 2017 18:25:54

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link / Flasher Portable Plus V1 compiled Dec 22 2016 17:34:56
    Hardware version: V1.00
    S/N: 811000038
    License(s): JFlash, GDB
    VTref = 3.201V


    Type "connect" to establish a target connection, '?' for help
    J-Link>connect
    Please specify device / core.
    : R7FS7G27G
    Type '?' for selection dialog
    Device>
    Please specify target interface:
    J) JTAG (Default)
    S) SWD
    TIF>
    Device position in JTAG chain (IRPre,DRPre)
    : -1,-1 => Auto-detect
    JTAGConf>
    Specify target interface speed [kHz].
    : 4000 kHz
    Speed>
    Device "R7FS7G27G" selected.


    TotalIRLen = 4, IRPrint = 0x01
    TotalIRLen = 4, IRPrint = 0x01
    AP-IDR: 0x24770011, Type: AHB-AP
    AHB-AP ROM: 0xE00FF000 (Base addr. of first ROM table)
    Found Cortex-M4 r0p1, Little endian.
    FPUnit: 6 code (BP) slots and 2 literal slots
    CoreSight components:
    ROMTbl[0] @ E00FF000
    ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS
    ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
    ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
    ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
    ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
    ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
    ROMTbl[0][6]: E0042000, CID: B105900D, PID: 002BB908 CSTF
    ROMTbl[0][7]: E0043000, CID: B105900D, PID: 001BB961 TMC
    ROMTbl[0][8]: E0044000, CID: B105F00D, PID: 001BB101 TSG
    Found 1 JTAG device, Total IRLen = 4:
    #0 Id: 0x5BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
    Cortex-M4 identified.



    Thks in advance

    The post was edited 1 time, last by imahgin ().

  • Hi,


    thanks for your inquiry.
    I could reproduce a issue with standalone programming of R7FS7G27G devices.
    We will investigate this issue and update this thread later this week.

    Best regards,
    Niklas
    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,


    Sorry for the delay in response.
    During debugging of the error, I accidentally (permanently) locked the device.
    Currently waiting for a new one to arrive.

    Best regards,
    Niklas
    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.
  • Quick update:
    We determined the root cause of the behavior and fixed it internally. A new version including this fix is scheduled for sometime next week.


    Best regards
    Erik
    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 Forum,


    Update:
    This issue if fixed in current version of the J-Link software & documentation pack.


    Best regards,
    Niklas
    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.