SEGGER - Nino Administrator

  • Member since Jan 2nd 2017
Last Activity

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

  • SEGGER - Nino -

    Replied to the thread std::mutex support.

    Post
    Hello, Thank you for your inquiry. Quote from CheMax: “again, without an RTOS I can't use the mutex from the standard library? ” That is correct. Same with other OS specific library functions. The standard library only defines what certain…
  • SEGGER - Nino -

    Replied to the thread [SOLVED] Custom Package Creation.

    Post
    Hello, Thank you for your inquiry. A general documentation how packages can be created can be found here: studio.segger.com/mkpkg.htm However, we also have tooling ready that can simply this further, but that is only available on request. If you are…
  • SEGGER - Nino -

    Replied to the thread startup code SEGGER_ARM_startup.s file.

    Post
    Hello, Thank you for your inquiry. i) The code is commented very detailed. It should already explain what it does. As you can see from the comments in invokes the linker generated init table for your system. This contains the heap init, constructor init…
  • SEGGER - Nino -

    Replied to the thread [SOLVED] Debugging code for all three cores (A7_0,A7_1,M4).

    Post
    Hello, we received this inquiry via our support system in parallel. Here is the answer we provided via mail so if someone stumbles across this inquiry they can read the answer as well: Embedded Studio itself does not have extensive support for…
  • SEGGER - Nino -

    Replied to the thread Static code analyzer ignores "v8M Has CMSE" option.

    Post
    Hello, Thank you for your inquiry. The reported behaviour is reproducible. Indeed only some preprocessor options are passed to the analyzer. You can see the CL call in the output window if you enable "Echo Build Command Lines". I will check with the…
  • SEGGER - Nino -

    Replied to the thread Unknown task.

    Post
    Hello, Thank you for your inquiry. FreeRTOS will create some tasks on its own. So you simply need to increase the value of SYSVIEW_FREERTOS_MAX_NOF_TASKS until all task names can be resolved. Just make sure to do a rebuild after changing the value and…
  • SEGGER - Nino -

    Replied to the thread [SOLVED] SEGGER_RTT_ASM_ARMv7M.S assembler error: bad instruction.

    Post
    Hello, Thank you for your inquiry. Your analysis is correct. That is why we ship the file with the .S ending, so the file runs first through a preprocessor so it is compatible to different assembler syntaxes from different tool chains. Case…
  • SEGGER - Nino -

    Replied to the thread [SOLVED] Package version control CMSIS 5.

    Post
    Hello, We received your inquiry in parallel via our support system where your question was answered. Please do not use multiple communication channels for the same inquiry with us as this can cause lost information between channels and increases our…
  • Hello, OK. Great to hear that you are up and running again. We will consider this thread as solved now. Best regards, Nino
  • Hello, Thank you for providing the example project. With it the issue is reproducible. It appears that the target device does not support background memory access for the memory area where the variable is located at. It reports that the memory read…
  • Hello, Thank you for your inquiry. From the behaviour it appears that the variable is placed in stack which is probably not what you are aiming for. So instead try declaring the variable as static. Do you still see the issue then? If yes, could you…
  • SEGGER - Nino -

    Replied to the thread Ozone 3.28 + JTrace PRO, trace not working after hitting breakpoint.

    Post
    Hello Florent, Thank you for your inquiry. What is the S/N of the J-Trace Pro you are using? For trace to work and later not to work there is usually one of the following reasons: * The trace interface between target device and J-Trace Pro is unstable…
  • SEGGER - Nino -

    Replied to the thread [SOLVED]Ozone warnings and unexpected code jumps..

    Post
    Hello, Quote from Akito: “When i link the application at address 0x0, the unused functions are marked as executable code in Ozone and i have the warning mentionned earlier on them. It is as if Ozone is confused on the possible location of these unused…
  • SEGGER - Nino -

    Replied to the thread [SOLVED] Support for Zfinx ISA spec.

    Post
    Hello, Thank you for your inquiry. Currently no plans for official support. But you can always use an external gcc that supports the extension and call it with Embedded Studio: wiki.segger.com/Use_an_externa…hain_with_Embedded_Studio You can also…
  • SEGGER - Nino -

    Replied to the thread [SOLVED] warning: relocation R_RISCV_CALL.

    Post
    Hello, Thank you for your inquiry. The warnings mean that the assembly code from the FreeRTOS RISC-V port is faulty. Each function must be declared as one as follows: C Source Code (1 line) Best regards, Nino
  • SEGGER - Nino -

    Replied to the thread SES link command syntax error (maybe ?).

    Post
    Hello, Thank you for your inquiry. Quote from jmarcialis: “The -T option is not separated from the file path, hence the syntax error on the new project. Is this normal ? ” Yes that is fine. Quote from jmarcialis: “If not, how can I possibly…
  • SEGGER - Nino -

    Replied to the thread [SOLVED] how to code profile a Zephyr application on the RP Pico?.

    Post
    Hello, Thank you for your inquiry. SWO profiling is currently not supported by Ozone. It is on our feature wishlist. You can only do printf via SWO in Ozone. If you are looking to do SWO profiling with J-Link our IDE Embedded Studio can be used:
  • SEGGER - Nino -

    Replied to the thread [SOLVED]Ozone warnings and unexpected code jumps..

    Post
    Hello, Thank you for your inquiry. As the poster before me mentioned one reason is typically a optimized build being debugged. Make sure you have code optimization off and debug symbols active in your toolchain. Another hint is the warning sign in your…