Recent Activities

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

  • Hello. I use Programmer firmware: J-Link V11. Program SEGGER J-Link Registration V8.10. MCU SPC560B50L5 in LQFP144 case on the board, connection via JTAG. When trying to connect, I have an error: “Unable to enable OnCE 10-bit TAP controller Failed…
  • Maketych -

    Replied to the thread J-Scope failed to parse elf file.

    Post
    Ok, thanks! Will be waiting for fix with impatience ))
  • binford -

    Posted the thread Nordic+VSCode+Ozone monitor mode debugging?.

    Thread
    Hi, I'm developing for the nRF52840 and building with the Nordic toolchain in VSCode. Is it possible to debug that build in monitor mode with Ozone? Using J-Link Ultra+. Thank you
  • kdarwish96 -

    Posted the thread Flashing Segger JLink Plus Compact using Windows Command Prompt.

    Thread
    Hello, I am new to using Segger, I have the J-Link Plus Compact and I was able to use its software (configurator, comnmander, etc...) to talk to and flash a microprocessor chip on a board. Now I need to do this with Windows Command Window (CMD) without…
  • SEGGER - Simon -

    Replied to the thread J-Scope failed to parse elf file.

    Post
    Hello, We are aware of this issue and are actively working on a fix. Since it impacts the core handling of symbols, the resolution is more complex and may take some time. However, we are aiming to have the fix ready within the next few weeks. Best…
  • Maketych -

    Posted the thread J-Scope failed to parse elf file.

    Thread
    J-Scope failed to parse elf file. Since the J-Scope v7.92o release till v7.98i, when opening elf file, first it stuck parsing for a while on few places, then parsing completed, but in the following Select Symbols window, typing anything in the Filter…
  • SEGGER - AlexD -

    Replied to the thread [SOLVED] Issue Attaching to Running Program.

    Post
    Hi Hi Charles_1, good to see you are up and running again. We will consider this thread as closed now. Thanks for sharing this with us and best regards -- AlexD
  • Charles_1 -

    Replied to the thread [SOLVED] Issue Attaching to Running Program.

    Post
    Yes I can attach now, and the solution was to override the SetupTarget function in JlinkScript in the Ozone project file function: BeforeTargetConnect()
  • mutlukosemen -

    Posted the thread JLINK and FLASHER programming/verification error..

    Thread
    Hello; I try to program renesas R7FA2L1AB via Flasher Compact.While programming stage ; if i get "****** Error: Verification of RAMCode failed @ address 0x20000344." error , i get the verification error at the end of programming If this happens once,…
  • Andy_AN2 -

    Posted the thread Header_CreateEX() causes HardFault due to unaligned access.

    Thread
    Dear Sirs, we use emWin 6.32.3 from KEIL. For memory management purposes we need to configure our external memory on our STM32F767 cpu to be of strongly ordered type. Doing this, 32bit accesses have to be on 32bit boundaries, 16bit accesses on 16bit…
  • gustavolaureano -

    Replied to the thread Please improve SystemView export possibilities.

    Post
    By the way, I believe that either the User Guide is wrong or the software has a bug, as, according to the User Guide, "the contents of the Terminal Window can be exported from the context menu and Export..." but, as already described, when using the…
  • Tomas_Skredenas -

    Posted the thread DeviceProvisioner_Choose_Emulator.

    Thread
    Hello, I am using Device Provisioner software on Raspberry Pi with several connected Jlink Probes. Can someone explain how to choose Jlink emulator from code side ? If I using terminal windows pop-up windows let you choose which emulator will be used. It…
  • gustavolaureano -

    Posted the thread Please improve SystemView export possibilities.

    Thread
    Hi, I am now using SystemView to measure the average time of a mark in our firmware, but, to my surprise, I am not able to only export the filtered entries shown when selecting "Show only markers", as SystemView will instead always export the entire…
  • jonestn -

    Replied to the thread Programmatic reset of ARM Cortex-M4 through J-Link Plus.

    Post
    I've confirmed that I can work around the issue using Pylink's open(), connect(), read(), close() operations each time I need to use the J-Link API. In hindsight, the lack of a J-Link disconnect() operation should have been a red flag as well as the…
  • SEGGER - Yan -

    Replied to the thread emNet Berkeley (BSD) socket compatibility.

    Post
    Hi Hendrik, you could use gethostbyname() or if you already have the host as an IP use the IP directly. There is a utility function to help you with that - IP_IPV4_ParseIPv4Addr()
  • rechrtb -

    Replied to the thread Trouble with instrumenting a module.

    Post
    One more thing, the initial pop-up window also says 0 modules.
  • SEGGER - AlexD -

    Replied to the thread [SOLVED] live tracing - timeline.

    Post
    Hi fraengers, we were able to reproduce the issues from bullet point #1 and #2. We will provide fixes in a future release of Ozone. Best regards -- AlexD
  • SEGGER - AlexD -

    Replied to the thread [SOLVED] Issue Attaching to Running Program.

    Post
    Hi Charles_1 your inquiry is no longer Ozone specific. You are facing general connection issues, which cannot be handled by Ozone team but need to be handled by the J-Link team. If my understanding is correct, you are now able to attach to your device.…
  • jonestn -

    Replied to the thread Programmatic reset of ARM Cortex-M4 through J-Link Plus.

    Post
    Running with J-Link v7.98g software and a J-Link Plus USB probe S/N 601006986 and nrfjprog 10.24.0 Test 1; 1) Connect J-Link Plus to target device (with a Laird BL652) 2) Start J-Flash, open nRF52832_xxAA device, SWD speed 4000 3) Erase chip, program &…
  • Charles_1 -

    Replied to the thread [SOLVED] Issue Attaching to Running Program.

    Post
    Ok, so I've been able to attach by using the SetupTarget function: int SetupTarget() { // // We leave ths function empty here to skip the ECC RAM init for SystemView. // Otherwise the RTT buffer would be overwritten and SystemView will not…