Search Results

Search results 1-20 of 310.

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

  • Hello, yes, these are called in embOS "task events". segger.com/doc/UM01001_embOS.html#Task_Events Please also have a look here Migration from FreeRTOS to embOS. Best regards, Til

  • Thanks for the feedback. Good to know it's working now. Please let me know if I can be of any further help. Best regards, Til

  • Hello Liorsze, I just tested the nRF52840 DK BSB in Start\BoardSupport\NordicSemi\nRF52840_nRF52840_DK\ and I can build it successfully with Embedded Studio V5.42b. 1. Which Embedded Studio version do you use? 2. Did you make any changes to the project? Best regards, Til

  • Hello Michael, I am sorry, there was an issue with the manual, please download the latest revision from here segger.com/downloads/embos/UM01014_embOS_CortexM_IAR.pdf Best regards, Til

  • Hello Michael, unfortunately IAR changed the thread safety support in different IAR EWARM version. What needs to be done for different IAR version in described in chapter "4.2 Thread-safe system libraries" and "4.2.2 IAR compiler V8.10 and newer". From the linker error message I guess you did not add the xmtx.c, xmtx2.c and xmtx3.c. Please find these files in the \Setup folder of your board support package. Does that solve your issue? In case of doubt please don't hesitate to contact our embOS s…

  • Hello Broddo, thanks for the additional information. Just to keep you up to date, we are still working on it. It's a little bit more complicated to install/use the latest NIOS II tools. Best regards, Til

  • Hello Broddo, thanks for the detailed description. Maybe an issue with your linker file and stack symbols. We will have a look into this today and get back to you asap. Best regards, Til

  • Hello Vadym, Quote from vadymsodolevsky: “As I understand the porting should not depend on IDE. Am I right? ” Yes, correct, the embOS Cortex-M GCC libraries are core/compiler but not IDE specific. Quote from vadymsodolevsky: “Can I use the library and include for the STM32CubeIDE Cortex M4 V7 project? ” Basically yes, but I recommend to use the embOS library from embOS Cortex-M GCC since it's based on a more recent embOS version. In any case please don't mix embOS libraries and RTOS.h from diffe…

  • Hello Vadym, Sounds like you did not add the embOS library to your project. Yes, we have support for STMCubeMX. Please have a look here: wiki.segger.com/Using_embOS_with_STM32CubeMX No, we don't have a STM32WB55 BSP with embOS Cortex-M GCC so far (which is the correct embOS port for STM32CubeIDE): segger.com/products/rtos/embos…tex-m/embos-cortex-m-gcc/ But that can easily be created for your evaluation. Please feel free to contact us directly via our ticket system or support email address: segg…

  • Please be aware this is not a technical question only but also a license/sales decision. I can't share any details about that now (since it's simply not yet decided) but I am pretty sure we'll find a solution which will work for you. Best regards, Til

  • Hello Jim, yes, you can use embOS spinlocks to synchronize data messaging between two or more cores. If you have an embOS instances running on each core you usually have a shared memory in which you can pass data from one core to the other. This shared memory must be secured with a spinlock. That's a generic way which works with every core. But most devices have device specific mechanism to communicate between the cores like triggering an interrupt on the other core. It depends on you applicatio…

  • Quote from westloser86: “This is correct, BLE is time sensitive and modifying the priorities of the ISR might cause instability in connections, advertisements, etc. I would not recommend to change this priorities. ” With Cortex-M the absolute interrupt priority value is not crucial but the comparison of two priorities. For example it makes no difference whether the interrupt priority is 0x00 or 0x80 if this is the only interrupt. Let's say the BLE stack initializes a BLE interrupt at priority 0x…

  • I guess the interrupt is initialized in the BLE library and you don't have the source code, correct? Anyway you can change the interrupt priority at any time later before your application starts. You just need to know which interrupt is used (I think it's the RTCC interrupt) and change the according interrupt priority. But I cannot know whether the interrupt priority has an influence on the BLE stack. Best regards, Til

  • Quote: “As far as I understand, this means that I cannot call the OS_EVENT_SetMask function because my program is in an ISR with higher priority. I have no clue how I can resolve this issue. ” That's correct. embOS API must be called only from embOS interrupts with an according interrupt priority. That means you have to change the interrupt priority to a valid value. Please have a look here and in the embOS manuals: wiki.segger.com/Interrupt_prioritization Best regards, Til

  • Dear Giacomo, Quote from j000: “Since in the method interrupt_handler() I make some calls to OS functions (like OS_PutMail used for mailboxes) If I'm not mistaken I have to tell the OS that I'm within an interrupt, with the methods OS_EnterInterrupt() and OS_LeaveInterrupt(). ” Yes, that's correct. Which error code do you get? Most likely you are using an invalid interrupt priority. The iMXRT1062 has four interrupt priority bits implemented, thus NVIC_SetPriority() expects values from 0 to 15 an…

  • Hi Thomas, that's more a question for IAR. Please have a look in the IAR EWRX compiler/linker manual on how to suppress warnings. Basically you can do it in the source code and in the project options. Best regards, Til

  • Hello Alexander, IAR changes the runtime model from time to time. This messages says that the embOS libraries were built with an older runtime model. Unfortunately there is no easy fix. The embOS libraries needs to be rebuilt with your IAR version. And we must check whether there is something we need to modify in our code. Please contact us directly per email or our ticket system and we'll help you with the evaluation. You can also give me a call to discuss further details. Best regards, Til

  • Hello, is it possible to share your complete project with us? With the project it should be possible to solve your issue within a few minutes. If not could you please show how StackFS and StackNOR are defined? What else did you change in the project? Regarding hard fault, please have a look here in the application note: Analyzing HardFaults on Cortex-M CPUs (AN00016) Best regards, Til

  • Wenn du das embOS Cortex-M ES V5.06 schon hast schaue doch bitte mal in die BSP_UART.c in Start\BoardSupport\ST\STM32F103_STM3210B_Eval\Setup\. Evtl. kannst du einfach bei uns abschauen oder das Modul direkt nutzen. Viele Grüße, Til

  • Hallo Philipp, üblicherweise passiert das wenn das Interrupt Pending Flag nicht gelöscht wurde. Du müsstest mal schauen, ob es das bei deinem Device gibt und es dann in der Interrupt Routine als erstes löschen. Ansonsten sieht der Interrupt Controller das ein Pending Flag gesetzt ist und führt die ISR sofort wieder aus. Das sollte aber ohne embOS genauso passieren. Löst das dein Problem? Btw. Ein OS_INT_Call() brauchst du nicht. Das wird nur bei manchen speziellen CPUs gebraucht. Eine embOS Inte…