[regression] J-Link software 4.42 does not find the S3FN41F anymore

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

  • [regression] J-Link software 4.42 does not find the S3FN41F anymore

    After installing the latest J-Link software 4.42 I see that this new version can no longer detect the S3FN41F on my eval board using GDBServer SWD!
    By contrast the J-Link commander finds the correct device

    -->
    SEGGER J-Link GDB Server V4.42 LogFile
    Logging started @ 2012-02-08 09:49
    03-00-00000000-001E: SEGGER J-Link GDB Server V4.42
    03-00-00000000-0036: JLinkARM.dll V4.42 (DLL compiled Feb 7 2012 21:44:38)
    03-00-00000004-0020: Waiting for J-Link connection...
    02-00-00000012-0035: Firmware: J-Link ARM V6 compiled Feb 1 2011 14:28:14
    02-00-00000012-000F: Hardware: V6.00
    02-00-00000012-000D: S/N: 5600xxxx
    02-00-00000129-0046: Feature(s): FlashBP, FlashDL, GDB returns O.K. (0125ms, 0000ms total)
    03-00-00000129-0014: J-Link is connected.
    02-00-00000131-0068: T13C4 000:130 JLINK_ExecCommand("SetFlashRewriteBehavior = 1", ...) returns 0x00 (0000ms, 0125ms total)
    02-00-00000132-0041: T13C4 000:132 JLINK_GetFirmwareString(...) (0000ms, 0125ms total)
    03-00-00000132-0035: Firmware: J-Link ARM V6 compiled Feb 1 2011 14:28:14
    02-00-00000133-004F: T13C4 000:133 JLINK_GetHardwareVersion() returns 0xEA60 (0000ms, 0125ms total)
    03-00-00000133-000F: Hardware: V6.00
    03-00-00000134-000D: S/N: 5600xxxx
    03-00-00000134-0021: Feature(s): FlashBP, FlashDL, GDB
    02-00-00000134-0049: T13C4 000:134 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0125ms total)
    02-00-00000135-003C: T13C4 000:135 JLINK_EnableSoftBPs(ON) (0000ms, 0126ms total)
    03-00-00000135-001D: Listening on TCP/IP port 2331
    03-00-00000135-001D: Waiting for GDB connection...
    02-00-00000204-0049: T14E4 000:204 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00000404-0049: T14E4 000:404 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00000604-0049: T14E4 000:604 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00000804-0049: T14E4 000:804 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00001005-0049: T14E4 001:005 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00001205-0049: T14E4 001:205 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00001405-0049: T14E4 001:405 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00001605-0049: T14E4 001:605 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00001805-0049: T14E4 001:805 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00002006-0049: T14E4 002:006 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00002206-0049: T14E4 002:206 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00002406-0049: T14E4 002:406 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00002606-0049: T14E4 002:606 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00002806-0049: T14E4 002:806 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00003007-0049: T14E4 003:007 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00003207-0049: T14E4 003:207 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    02-00-00003407-0049: T14E4 003:407 JLINK_GetHWStatus(...) returns 0x00 (0000ms, 0126ms total)
    03-00-00003455-0019: Closing GDB connection...
    03-00-00003456-0037: Restoring target state and closing J-Link connection...
    02-00-00003456-0041: T13C4 003:456 JLINK_IsOpen() returns 0x01 (0000ms, 0126ms total)
    02-00-00003456-0056: T13C4 003:456 JLINK_ExecCommand("ClrAllBPs", ...) returns 0x00 (0000ms, 0126ms total)
    03-00-00003510-0010: Shutting down...
    <--
    Veikko

  • Hi,

    Did you check your startup settings for the GDBServer?
    They should look similar to the ones in the attached screenshot.

    In general, there was a bug in V4.42 when performing a target reset while using SWD.
    This has been fixed in V4.42a.

    Currently, we do not have a S3FN41F device here, so we can not reproduce the problem here.


    Best regards
    Alex
    Images

    • GDBServerStartup.gif

      12.14 kB, 550×875, viewed 686 times
    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.

  • Sorry, I am not able to get a dialog after clicking the [Downlaod] so I cannot sholw you the screenshot.
    But actually it looks like yours - and is not showing a device at all.

    So I will ty 4.42a.

    BTW: Can you confirm that anyone has ever successfully worked with the J-Link and the S3FN41F?