[SOLVED]Crash to desktop when flashing with JFlash on a Win7 platform

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

  • [SOLVED]Crash to desktop when flashing with JFlash on a Win7 platform

    Flashing a Freescale MC9328MXS with ST 28F320C3BD70-32M Flash.

    Developed on a Mac w/VMware and a J-link Ultra. Tested on an XP64 machine and a Flasher ARM, flashes with either.

    Deployed to production on Windows 7 Pro(32) machines. Crashes to desktop while unlocking flash(see logs). Duplicated on 2 different machines both crash, compatibility modes don't have any affect.



    Jflash Log:

    Opening data file [C:\HH flash program\HH41_407_mfg.srec] ...
    - Data file opened successfully (2461411 bytes, 430 ranges, CRC = 0x0F1C2383)
    Connecting ...
    - Connecting via USB to J-Link device 0
    - J-Link firmware: V1.20 (J-Link ARM / Flasher ARM V3 compiled Sep 12 2011 19:54:02)
    - JTAG speed: 5 kHz (Fixed)
    - Initializing CPU core (Init sequence) ...
    - Executing Reset (0, 0 ms)
    - Executing Write 32bit (0x00221000, 0x91090300)
    - Executing Read 32bit (0x08000000)
    - Executing Write 32bit (0x00221000, 0xA1090300)
    - Executing Read 32bit (0x08000000)
    - Executing Read 32bit (0x08000000)
    - Executing Read 32bit (0x08000000)
    - Executing Read 32bit (0x08000000)
    - Executing Read 32bit (0x08000000)
    - Executing Read 32bit (0x08000000)
    - Executing Read 32bit (0x08000000)
    - Executing Read 32bit (0x08000000)
    - Executing Write 32bit (0x00221000, 0xB1090300)
    - Executing Write 32bit (0x08119800, 0xFFFFFFFF)
    - Executing Write 32bit (0x00221000, 0x81098300)
    - Executing Write 32bit (0x0021B808, 0x00000001)
    - Executing Write 32bit (0x00220004, 0x00000C01)
    - Executing Write 32bit (0x00220018, 0x00000F00)
    - Executing Write 32bit (0x0022001C, 0x03030D01)
    - Initialized successfully
    - JTAG speed: 12000 kHz (Fixed)
    - J-Link found 1 JTAG device. Core ID: 0x1092001D (ARM9)
    - Reading CFI info ...
    - Found CFI compliant flash device
    - 2 block regions
    - 8 sectors with 8 KB
    - 63 sectors with 64 KB
    - Flash ID (Chip 0) = 0x2088BB
    - Matching flash chip found: "ST M28W320FCB"
    - CFI info read successfully
    - Connected successfully
    Programming and verifying target (2461411 bytes, 430 ranges) ...
    - RAM tested O.K.
    - Soft unlocking affected sectors ...
    - 50 of 71 sectors affected to unlock, 6 ranges
    - Affected sectors 0 to 15 (0x10000000 - 0x1008FFFF)
    - Affected sectors 17 to 18 (0x100A0000 - 0x100BFFFF)
    - Affected sectors 20 to 28 (0x100D0000 - 0x1015FFFF)
    - Affected sectors 36 to 56 (0x101D0000 - 0x1031FFFF)
    - Affected sector 68 (0x103D0000 - 0x103DFFFF)
    - Affected sector 70 (0x103F0000 - 0x103FFFFF)



    Windows Log:

    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: JFlashARM.exe
    Application Version: 0.0.0.0
    Application Timestamp: 4ea074ba
    Fault Module Name: JFlashARM.exe
    Fault Module Version: 0.0.0.0
    Fault Module Timestamp: 4ea074ba
    Exception Code: c0000005
    Exception Offset: 00037bee
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 1033
    Additional Information 1: 0a9e
    Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
    Additional Information 3: 0a9e
    Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

  • Hi,

    We are not aware of such problems.
    Nevertheless, we will give it a try and check if we can reproduce the behavior you are describing.


    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,

    The problem has been located and fixed.
    There will be a patched release version (V4.36i) within the next days.

    Everyone who wants to get informed automatically when the new version becomes available
    can subscribe to the J-Link newsletter:
    segger.com/notification/subscribe.php?prodid=7


    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 all,

    Porblem has been fixed in V4.36i.

    Download-Link: segger.com/download_jlink.html


    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.