Search Results

Quote from SEGGER - Martin: “ We expect to release an updated version of embOS for Cortex-M and KEIL MDK within the next week, which will provide full support for the most recent version of SystemView. Please kindly excuse the inconvenience. Best regards, Martin” Hello Martin, I can't see an update for the embOS object Code on Cortex-M and KEIL MDK until now. The actuall version is 4.12 with NO SystemView support. When will the update be available for Cortex-M and KEIL? Some other embOS Sources …

I have the same problem with OS_TRACE_API size mismatch using embOS V4.12 (that's the newest version for Cortex-M for Keil) and SystemView V2.20. The OS_TRACE_API definition in RTOS.h missmatches with it's using in SEGGER_SYSVIEW_embOS.c. The SystemView documentation says that it will work with embOS since V4.12 but that seams to be wrong. Do I need a newer version of embOS (which is not released for Keil at the moment!).

Hello Til, the project is copyright protected and to big to post it here. But I will explain my task handling: At startup the 3 tasks are suspended by calling "OS_Suspend(&Name); " (called for every task) before "OS_Start();". Now after initialization the Interrupt occurs natural with calling "OS_EnterInterrupt();" at the beginning of the IRQ-Handler and "OS_Leaventerrupt();" at the end. The IRQ makes some checks an if everything is ok, it is called "OS_Resume(&Task1);". When task1 is started he…

Hello Segger Team, I have an application where 3 Task starts in cooperative multitasking after an interrupt. Every task starts just one time per interrupt. In embOSView the run count of the first task increase faster then the other ones, but if I count the runs with a normal variable and view this over the debugger all 3 task a called in equal frequency. It seams to be an error in embOSView. I use embOSView v3.82p is there a known mistake with the run count? Greetings Martin

Hallo Til, thank you for your fast answer but now it works. I have just done a complete chip erase and cleaned the project before recompiling the files and now it works fine. Although I don’t know why. Sorry for disturbing! It’s almost embarrassing.

Hello Segger Team, I have problems with the task stack size. I use: „EXTERN OS_STACKPTR int StackTask[XXX]; and create tasks with: S_CREATETASK(&TTask, "The Task", Task, 100, StackTask); Now I can enter any value for XXX in the upper statement and the embOSView – Tool shows always a stack size of 512. What’s there wrong? At the moment I using the Demo library from embOS because the ordering is still in progress. But now I need more than 512 Byte. What’s my mistake? Greetings Martin

I use jLink EDU with Flashbreakpoints and Keil and it works fine. I think the Keil MDK is completely supported. But you need an unbrended jLink. The one from IAR is locked for the IAR Workbench (like cellular phones).

Hallo Segger Team, I have solved this problem for my own. I have copied the Files: "JLink.exe", "JLinkARM.dll" and the USBDriver Folder from "C:\Programme\SEGGER\JLinkARM_V424c" to the Segger directory in the Keil installation at "C:\Keil\ARM\Segger\". I suggest to put this information into your JLink Manual, I have nothing find there about this or you could modify your Install progress to Copy the actually files in an installed Keil Version automatically. Greetings Martin

Hello Segger team, I bought a jLink EDU and use it together with Keil µVision. Now I get always (often 3 times in a row) a Popup with the "jLink EDU Terms of Use" I have to accept. That’s very annoying! While debugging this popup arrives all few seconds, while downloading I have to accept, while Setup the debugger or the flash tool in µVision I have to accept 3 times in a row...) Is it possible to put this of? Or do I something wrong? So labor is not fun! I use latest jLink installpack (download…

Hello Til, you are right, just a blunder in C. I used the task routines from your example and they are all "static" defined. With static that can't work in another C-File. Thank you for Help and Information Martin

Hallo, I am student and compare different RTOS for a Cortex-M3 (LPC1768 from NXP) and Keil compiler. At the moment I'm checking the Segger embOS. To measure the context-switch-time I used the scope example comes with the evalversion of the embOS. My results are 4,66 µs with 72 MHz Core-Clock and 3,2 µs with 100 MHz Core-Clock. If I calculate correctly, they are round 320 CPU-Cycles. Is this a realistic time? What was the Core-Clock by your test for Cortex-M3 shown here? Furthermore, I want every…