[SOLVED] Failed to measure CPU clock frequency

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

  • [SOLVED] Failed to measure CPU clock frequency

    Dear,

    I've recently had a problem using ozone with PLC2387 and LPC 2148. Previously everything worked fine. But now I received following error message from Ozone

    Device "LPC2387" selected.
    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4F1F0F0F, IRLen: 04, ARM7TDMI-S Core
    Connected to target device.
    Elf.GetEntryPointPC(); // returns 0x8000
    Target.SetReg ("PC", 0x8000);

    Failed to measure CPU clock frequency
    Read memory error @ address 0x40000000, 16 bytes: Communication timeout.
    000, 16 bytes: Communication timeout.
    Failed to halt CPU for clock frequency detection!
    Target voltage too low (1 Volt is required, Measured: 0.0 Volt).
    Download failed: J-Link reports an unspecified download error

    Connection to target device lost.
    Disconnected from target device.
    Elf.GetEntryPointPC(); // returns 0x8000
    Target.SetReg ("PC", 0x8000);
    Target.SetReg ("PC", 0x8000): Not connected.

    The problem for device LMP2148 is equal. I can download program to flash using JFlash. But if I use J-Link, I will receive equal error message.

    I use Ozone 2.70a (x64), SEGGER J-Link Commander V6.54 (Compiled Oct 28 2019 10:35:28) and SEGGER J-Link ARM V10.10 with firmware 22 Oct 2019. But, I periodically received following message in J-Link

    Connecting to J-Link via USB...Updating firmware: J-Link V10 compiled Oct 22 2019 16:28:15
    Replacing firmware: J-Link V10 compiled Jun 3 2015 BTL
    Waiting for new firmware to boot
    FAILED: Communication timed out: Requested 4 bytes, received 0 bytes !
    Could not read J-Link capabilities.
    Cannot connect to J-Link
    J-Link>con
    J-Link connection not established yet but required for command.
    Connecting to J-Link via USB...

    And J-Link is unavailable until rebooted. Help me, please

    BR,
    Andy

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

  • Hello Andy,
    sorry for the delay in response.
    The last days were very busy.

    Such an issue is not known to us.

    Did the Problem appear when you updated Ozone or did it work with the Ozone version you are currently using before?
    Could you check if the voltage really drops below 1V?

    Best Regards,
    Fabian
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.
  • Hello Andy,

    Could you tell me what is different to the last time it worked with these chips?
    Did you update the J-Link Software and Documentation Pack?

    Best regards,
    Fabian
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.
  • Fabian, I don't see any difference environment (debugger, scheme, chips and software SEGGER for debugger) between last successful experience and bad experience (when appeared problem). I updated J-Link software up to latest version, but it had fixed problem. Also, I tested my J-link PLUS with new PC with latest Ozone and J-Link software - result is equal (problem saved). I don't know, that I can do it.

    I'm embarrassed by the error message Replacing firmware: J-Link V10 compiled Jun 3 2015 BTL. Early (when Ozone and J-Link PLUS worked) this message didn't appeared.

    BR,
    Andy
  • Hi Andy,

    Could you please answer the following questions?:
    1) Does this replacing firmware error also appear when you are using J-Link Commander (jlink.exe)?
    2) Could you send us a picture of the whole Commander output?
    3) Is the J-Link connected to the PC directly, or via an USB-Hub?
    4) Could you send us a picture of your debug setup?

    Best regards,
    Fabian Federschmidt
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.
  • Fabian, answers is below

    1) Does this replacing firmware error also appear when you are using J-Link Commander (jlink.exe)?

    Message about replacing firmware does not always appears and Yes, this message also appear when I using J-Link Commander.

    2) Could you send us a picture of the whole Commander output?

    Picture is in attachement

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link V10 compiled Oct 22 2019 16:28:15
    Hardware version: V10.10
    S/N: 600112975
    License(s): RDI, FlashBP, FlashDL, JFlash, GDB
    VTref=3.303V


    Type "connect" to establish a target connection, '?' for help
    J-Link>con
    Please specify device / core. <Default>: LPC2387
    Type '?' for selection dialog
    Device>
    Please specify target interface:
    J) JTAG (Default)
    TIF>
    Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
    JTAGConf>
    Specify target interface speed [kHz]. <Default>: 4000 kHz
    Speed>500
    Device "LPC2387" selected.


    Connecting to target via JTAG
    TotalIRLen = 4, IRPrint = 0x01
    JTAG chain detection found 1 devices:
    #0 Id: 0x4F1F0F0F, IRLen: 04, ARM7TDMI-S Core
    ARM7 identified.
    ETM V1.2: 1 pairs addr.comp, 0 data comp, 4 MM decs, 1 counters
    J-Link>r
    Reset delay: 0 ms
    Reset type NORMAL: Using RESET pin, halting CPU after Reset
    J-Link>loadfile c:\WORKS\EM133_12.9.28.24_24D1_test.hex
    Downloading file [c:\WORKS\EM133_12.9.28.24_24D1_test.hex]...

    ****** Error: Failed to measure CPU clock frequency
    Communication timed out: Requested 4 bytes, received 0 bytes !Read memory error @ address 0x40000000, 16 bytes: Communication timeout.
    Failed to halt CPU for clock frequency detection!
    Target voltage too low (1 Volt is required, Measured: 0.0 Volt).
    Unspecified error -1
    J-Link>

    3) Is the J-Link connected to the PC directly, or via an USB-Hub?

    I tried both variants - connect j-link to PC directly and via USB-Hub. Results are equal - problem has saved.

    4) Could you send us a picture of your debug setup?

    My debug setup from Ozone is in file "debug setup.pdf".
    Images
    • Commander output.jpg

      186.15 kB, 1,920×1,040, viewed 34 times
    Files
    • debug setup.pdf

      (202.46 kB, downloaded 25 times, last: )
  • Hello,

    Please note that this is no support forum so replies from our engineers may be delayed.
    For more information see my signature.

    Regarding your J-Link, it appears that this one is defective. I have created a ticket with our sales department and they will answer you via e-mail shortly.

    To avoid communication over multiple channels this thread will be closed now.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.