GDBServer SWD 4.41h (beta) does no longer recognize S3FN41F

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

  • GDBServer SWD 4.41h (beta) does no longer recognize S3FN41F

    There is a regression from 4.40 to 4.41h (beta)
    in this latest beta version the same target (S3FN41F) cannot get connected using the GDB Server SWD.
    J-Link says: [connected], power level is ~5V but Target says [not connected

    using the latest 4.40d it work as expected (but shows the ID as 0x000000)
  • I run J-Link Commander to see more... and I see my device, but finally "No device found on SWD"

    SEGGER J-Link Commander V4.41h ('?' for help)
    Compiled Jan 31 2012 21:41:04
    DLL version V4.41h, compiled Jan 31 2012 21:40:48
    Firmware: J-Link ARM V6 compiled Feb 1 2011 14:28:14
    Hardware: V6.00
    S/N:
    Feature(s): FlashBP, FlashDL, GDB
    VTarget = 5.034V
    Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    No devices found on JTAG chain. Trying to find device on SWD.
    Info: Found SWD-DP with ID 0x0BB11477
    Info: FPUnit: 0 code (BP) slots and 0 literal slots
    No device found on SWD.
    Did not find any core.
    Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    No devices found on JTAG chain. Trying to find device on SWD.
    No device found on SWD.
    Did not find any core.
    J-Link>
  • Hi,

    I am a bit confused. In another thread you write that in V4.42 the GDBServer does not recognize the device while J-Link Commander still works.
    Here it seems that even J-Link Commander is unable to find the device.
    What is correct? Does it work from J-Link Commander and only not via GDBServer or does it not work at all?

    Could you please concentrate on one thread? Otherwise it is difficult to follow things here.


    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.
  • You can close this thread.

    The problem was that the device had a bad protection configuration that disabled SWD/JTAG due to writing a wrong value at flash address 0x0000C0 .. C8.

    That means the J-Link finds some device but cannot regonize its ID
  • Hi,

    the J-Link flash algorithm should make sure that Bit 0 at 0xC5 is never cleared which would enable the SWD protection.
    All other bits should not inhibit J-Link connection to the device in general.
    Moreover, if the SWD interface was disabled, I am wondering a bit how J-Link was then able to
    read the SW-DP ID of the device:
    No devices found on JTAG chain. Trying to find device on SWD.
    Info: Found SWD-DP with ID 0x0BB11477
    Info: FPUnit: 0 code (BP) slots and 0 literal slots


    How did you recover the device? Erasing it in serial programming 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.
  • But after that
    Info: Found SWD-DP with ID 0x0BB11477

    Info: FPUnit: 0 code (BP) slots and 0 literal slots

    No device found on SWD.

    Did not find any core.

    Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000

    Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000

    No devices found on JTAG chain. Trying to find device on SWD.

    No device found on SWD.

    Did not find any core.