buggy firmware upgrade by 3.96d version of GDB server?

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

  • buggy firmware upgrade by 3.96d version of GDB server?

    We use the Atmel AT91SAM-ICE JTAG emulator version of the J-Link ARM to load a program into the RAM of an Atmel AT91FR40162SB device (ARM 7 CPU and embedded flash), which we use in a hand device, as part of our flash programming process.

    I had been using my AT91SAM-ICE JTAG emulator successfully with version 3.74i of the Segger J-Link GDB Server for some time.

    I recently tried upgrading to version 3.96d of the Segger J-Link GDB Server. I now find that the AT91FR40162SB device is no longer recognized. I have returned to version 3.74i, but it is still no longer recognized.

    When I start the J-Link Commander program, I get this line:

    Firmware: J-Link compiled Jul 30 2008 11:24:37 ARM Rev.5

    This date is only four months ago, even though I have had my AT91SAM-ICE well over a year.

    Also, the same line for another AT91SAM-ICE device that still works is:

    Firmware: J-Link ARM V6 compiled Oct 10 2007 19:39:24

    So I conclude that version 3.96d of the Segger software has reflashed my SAM-ICE with buggy firmware.

    Is this a known problem? Perhaps it affects other J-Link ARM devices too? Is there some way to restore the original firmware?

    Is this the correct forum to ask this? Can anyone suggest a more appropriate place?

  • Hello cmacdonnell,

    there should be no problems when using SAM-ICE + J-Link GDB Server with your target device.
    Could you please post a more detailed description of your problem?
    Posting the complete output of J-Link commander (when using the SAM-ICE which does not work)
    would also be useful in order to investigate this.

    How to downdate the firmware:
    Described in UM08001 (J-Link / J-Trace User Guide), chapter "9.7.2 Invalidating the firmware".
    Download UM08001

    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.

  • Here is the full output from J-Link Commander for the SAM-ICE that fails:

    SEGGER J-Link Commander V3.74i ('?' for help)
    Compiled Sep 11 2007 14:43:12
    DLL version V3.74i, compiled Sep 11 2007 14:43:07
    Firmware: J-Link compiled Jul 30 2008 11:24:37 ARM Rev.5
    Hardware: V5.40
    S/N : 20004833
    OEM : SAM-ICE
    Feature(s) : RDI
    VTarget = 0.000V

    ****** Error: Supply voltage too low (1 Volt is required, Measured: 0.0 Volt).
    Please check target power.
    JTAG speed: 30 kHz
    J-Link>

    Here is the full output from J-Link Commander for the SAM-ICE that still works:

    SEGGER J-Link Commander V3.74i ('?' for help)
    Compiled Sep 11 2007 14:43:12
    DLL version V3.74i, compiled Sep 11 2007 14:43:07
    Firmware: J-Link ARM V6 compiled Oct 10 2007 19:39:24
    Hardware: V6.00
    S/N : 26004027
    OEM : SAM-ICE
    Feature(s) : RDI
    VTarget = 0.000V

    ****** Error: Supply voltage too low (1 Volt is required, Measured: 0.0
    Volt).
    Please check target power.
    JTAG speed: 30 kHz
    J-Link>

    I see that the hardware version is different.

    =====

    Thanks for the link to the newer manual. I could not find information about downdating firmware in the manuals for V3.74i. I hesitate to use the procedure described there for the moment, due to these cautions that appear in the manual:

    Note: Downdating J-Link / J-Trace is not recommended, you do it at your own risk!

    Note: Note also the firmware embedded in older versions of JLinkARM.dll might not execute properly with newer hardware versions.

    It is possible, I suppose, that the firmware that used to be in my SAM-ICE was newer than the firmware in V3.74i, and so I could run afoul of the second caution. Could you advise me on this please? Is the firmware in V3.74i safe to use with my hardware version V5.40 SAM-ICE?

  • Hello cmacdonnell,

    J-Link commander output:
    sorry for the confusion, what I meant is that it would be useful to see if the communication with the target
    in general works with the SAM-ICE containing the newer J-Link firmware. So the output when a target is connected would be useful.

    GDB Server problem:
    What exactly happens when you are trying to use the SAM-ICE with the newer firmware version?

    Downdating the firmware:
    There should be no problem by downdating the fimrware to 3.74i.

    Bets 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 wrote:
    > J-Link commander output:
    > sorry for the confusion, what I meant is that it would be useful to see if the communication with the
    > target in general works with the SAM-ICE containing the newer J-Link firmware. So the output when
    > a target is connected would be useful.

    From J-Link Commander V3.74i:

    SEGGER J-Link Commander V3.74i ('?' for help)
    Compiled Sep 11 2007 14:43:12
    DLL version V3.74i, compiled Sep 11 2007 14:43:07
    Firmware: J-Link compiled Jun 28 2007 10:45:08 ARM Rev.5
    Hardware: V5.40
    S/N : 20004833
    OEM : SAM-ICE
    Feature(s) : RDI
    VTarget = 1.132V
    JTAG speed: 30 kHz

    ****** Error: Target VCC failure. Please check target voltage.
    Could not find supported CPU core on JTAG chain
    Trying to connect with 5 kHz !

    J-Link>

    J-Link Commander V3.96d output:

    SEGGER J-Link Commander V3.96d ('?' for help)
    Compiled Nov 21 2008 19:00:17
    DLL version V3.96d, compiled Nov 21 2008 18:59:52
    Firmware: J-Link compiled Jul 30 2008 11:24:37 ARM Rev.5
    Hardware: V5.40
    S/N : 20004833
    OEM : SAM-ICE
    Feature(s) : RDI
    VTarget = 1.138V
    Info: TotalIRLen = ?, IRPrint = 0x..00000000000000000000000000000000

    WARNING: No matching core found. Selecting default core (ARM7).

    ****** Error: Target VCC failure. Please check target voltage.
    JTAG speed: 5 kHz
    J-Link>

    J-Link GDB Server V3.96d GUI window:

    GDB Waiting for connection Initial JTAG speed Auto
    J-Link Connected Current JTAG speed Auto
    Target Not connected 1.13V

    Log output

    SEGGER J-Link GDB Server V3.96d

    JLinkARM.dll V3.96d (DLL compiled Nov 21 2008 18:59:52)

    Listening on TCP/IP port 2331

    J-Link connected
    Firmware: J-Link compiled Jul 30 2008 11:24:37 ARM Rev.5
    Hardware: V5.40
    S/N: 20004833
    OEM: SAM-ICE
    Feature(s): RDI

    > GDB Server problem:
    > What exactly happens when you are trying to use the SAM-ICE with the newer firmware version?

    As the facsimile of the J-Link GDB Server GUI window above shows, "Target" remains "Not connected".

    As one would then expect, running GDB fails.

    > Downdating the firmware:
    > There should be no problem by downdating the fimrware to 3.74i.

    I tried the firmware from V3.74i. But no joy. Although I did momentarily see "Target" in the GDB Server GUI window momentarily change to "ARM ...", or something like that. This was just for an instant. So I do not know what the rest of the text was. It did not stay long enough to try using GDB to load a program to RAM.

    J-Link Commander V3.74i output using V3.74i firmware:

    SEGGER J-Link Commander V3.74i ('?' for help)
    Compiled Sep 11 2007 14:43:12
    DLL version V3.74i, compiled Sep 11 2007 14:43:07
    Firmware: J-Link compiled Jun 28 2007 10:45:08 ARM Rev.5
    Hardware: V5.40
    S/N : 20004833
    OEM : SAM-ICE
    Feature(s) : RDI
    VTarget = 1.132V
    JTAG speed: 30 kHz

    ****** Error: Target VCC failure. Please check target voltage.
    Could not find supported CPU core on JTAG chain
    Trying to connect with 5 kHz !

    J-Link>

    ===

    I do not recall using J-Link Commander until I had the problem after upgrading to V3.96d. J-Link GDB Server always worked for me (I never bothered showing the "Log output" either). I only tried J-Link Commander to try to troubleshoot the problem. So I do not know if the "Target VCC failure" message has always been there. I will ask my colleague with the working SAM-ICE to see what he gets. But there have been know changes to the hardware I am using (unless I have damaged the JTAG port or connector strap or something, which I doubt).

  • It appears that I must have damaged the JTAG plug I am using at the same time I happened to upgrade my firmware. Where my colleague does the same test he gets a "VTarget" over 3 volts:

    SEGGER J-Link Commander V3.74i ('?' for help)
    Compiled Sep 11 2007 14:43:12
    DLL version V3.74i, compiled Sep 11 2007 14:43:07
    Firmware: J-Link ARM V6 compiled Oct 10 2007 19:39:24
    Hardware: V6.00
    S/N : 26004027
    OEM : SAM-ICE
    Feature(s) : RDI
    VTarget = 3.125V
    JTAG speed: 30 kHz
    Found 1 JTAG device, Total IRLen = 4:
    Id of device #0: 0x1F0F0F0F
    Found ARM with core Id 0x1F0F0F0F (ARM7)
    J-Link>

    I only get a "VTarget" of 1.1 volts.

    Sorry for the fuss. Thanks for your help.