Search Results

Search results 1-11 of 11.

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

  • Hi, on my side the path is $(StudioDir)/samples/SEGGER_Flash.icf Regards Jluc

  • Hello, same here. My original project was created with release 4.12 by importing a CubeMX project in MDK format. So, we've a to go in the Options/Build/Memory segments and replace FLASH and RAM by FLASH1 and RAM1 ? For every project updated from V4.xx to V4.18 ? Regards JLuc

  • Hi, in release 4.18, the linker complains about redefinition of FLASH in SEGGER_Flash.icf. Brainfuck Source Code (5 lines)It works with Source Code (5 lines) Could you check that ? Regards Jluc

  • Dear Til, thanks a lot for these interesting answers. If I'm correct, my watchdog in Idle loop is efficient for: -> trapped in OS_Error(), -> infinite loops without OS_Delay() consuming all the resource, but not the task timing. Gone to upgrade to 4.38... Jluc

  • Hardware watchdog

    JLuc - - embOS related

    Post

    Dear Til, I don't understand your answer : "If you would trigger the hardware watchdog in one task only all other tasks are not checked and you don't know if they are still running." Why Hardware watchdog reload in the idle loop is not possible ? Please explain . In my mind, if any task is blocked, the idle loop is not reached anymore and the hardware watchdog is triggered. What do you think about kicking the watchdog in the lowest priority task ? Regards Jluc

  • Dear Martin, Quote: “ For a Cortex-M3 using SWO, both the IAR C-SPY debugger and SEGGER SystemView should be able to run in parallel. Did you experience an error message telling "Second debugger connection to the same J-Link detected"? ” It doesn't work, even with the correct address, no message. Quote: “ Your configuration seems fine except for "Unspecified": When no debug session is running in parallel, you'd need to specify the target device inside SystemViewer, e.g. STM32F101VG.” In fact, I …

  • Dear Martin, finally it works ! The problem is in the RTT connection. When in AUTO mode, RTT can't find the buffers, even in range mode. I've to fill the address manually, in address mode. You can find it in the map file, look for _SEGGER_RTT, something like 0x20000D5C. By the way, the tip (help) for this field doesn't appear if the connection fails. Waiting for the V2.30.... Regards JLuc

  • Dear Martin, Quote: “ Did you call SEGGER_SYSVIEW_Conf() from within your application? ” Yes. My program is more or less a copy paste of the user manual example: C Source Code (11 lines) Quote: “ Furthermore, did you configure the appropiate device in SystemViewer? ” Let me know what should I configure. TODO: add a paragraph in the manual regarding JLink connection. Here's the parameters in the connection to JLink window: Connection to JLINK : USB Target Device: Unspecified Target Interface & Sp…

  • Hello Martin, I've downloaded and compiled 2.20 release: SEGGER_SYSVIEW.c Error[Pe018]: expected a ")" C:\Projets EWARM 7.20\EmbOs V4.12a STLib V3.50 - System Viewer 2.20\System Viewer 2.20\TargetSrc\Config\SEGGER_SYSVIEW_Conf.h 75 Remark[Pe193]: zero used for undefined preprocessing identifier "SEGGER_SYSVIEW_CORE_M3" C:\Projets EWARM 7.20\EmbOs V4.12a STLib V3.50 - System Viewer 2.20\System Viewer 2.20\TargetSrc\Config\SEGGER_SYSVIEW_Conf.h 101 Remark[Pe193]: zero used for undefined preprocess…

  • Hi All, I'm trying to implement SystemView V2.10 with EmbOS V4.12a libraries. IDE is IAR's EWARM 7.20. Target CORTEX M3 STM32F101 Project based on EmbOS 'Start' blinking 2 leds in 2 tasks, running fluently w/o System View. When compiling with System View files, i get this error: Updating build tree... SEGGER_SYSVIEW_embOS.c Error[Pe146]: too many initializer values C:\...\System Viewer 2.10\TargetSrc\Sample\OS\SEGGER_SYSVIEW_embOS.c 139 Error while running C/C++ Compiler It's due to the structur…

  • Dear all, I'm using PowerPac 3.80g / Ewarm 5.40 on STM32F101 Cortex M3 target. I want to find where the processor enters the hardfault handler. I wrote a small code to display on LCD: R0 0X12345678 Hard R1 0X12345678 Fault! R2 0X12345678 R3 0X12345678 R12 0X12345678 LR 0X12345678 PC 0X12345678 SR 0X12345678 everything is OK, the values are the same as in the debugger window. That's fine, because the problem arises on EMC perturbations on the field and I can't use the debugger. Question: When ent…