[SOLVED/OR] "PC has unexpected value after checking target RAM" - EFM32 Zero Gecko - J-Link V5.41a

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

  • [SOLVED/OR] "PC has unexpected value after checking target RAM" - EFM32 Zero Gecko - J-Link V5.41a

    Is there anyone who can please explain

    a) the reason for
    "Error: PC of target system has unexpected value after checking target RAM."

    b) how to resolve/avoid it

    We are trying to program an EFM32ZG110F16 using J-Link Commander 5.41a - all under 64-bit Linux.

    We have seen this error crop up elsewhere in old posts in the forum, where the solution has been a new version of J-Link! So is this a J-Link error? Or can we get round it somehow?

    Thanks in advance
    Files

    The post was edited 2 times, last by sunnyBeach ().

  • Hi,

    usually this is means that sth. has interrupted the J-Link RAMCode during the RAMcheck, e.g. a Watchdog reset or a non-maskable interrupt occurred.
    Could you check the Watchdog / Interrupt status after this error occurs?

    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.

  • Our original commands to "J-Link Commander" V5.41a were:

    device efm32zg110f16
    si 1
    connect
    loadbin test.bin, 0

    This sequence failed as originally reported. We then changed the commands to:

    si 1
    device efm32zg110f16
    speed 4000
    loadbin test.bin, 0

    and this sequence worked for a while. But now (after many successful reprogram and debugging cycles) we are back to where we started.

    We appear to be able to read memory (eg with 'mem 0, 200') and this indicates that the flash is blank. So, how can any of our code be running? Isn't the debug interface (via JLink) supposed to disable/halt the code?

    Out of interest, does the RAMCode disable the watchdog? If we have power cycled the device (without any code in flash) then surely the Watchdog can't be running any more?

    The post was edited 2 times, last by sunnyBeach ().