Search Results

Search results 1-20 of 293.

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

  • 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…

  • Freut mich das es jetzt funktioniert. Melde dich einfach wenn du noch Hilfe brauchst. Viele Grüße, Til

  • Korrekt, der embOS Timer wird in der OS_InitHW() in der RTOSInit.c initialisiert. Dazu passend müssen dann einige Sachen in der RTOSInit.c angepasst werden damit alle embOS Timing Funktionen über den neuen Timer informiert sind. Das ist aber fast selbsterklärend (z.B. OS_TIMER_FREQ auf die richtige Frequenz des genutzten Timers setzen). Ich würde aber empfehlen den anderen Weg zu versuchen. Das ist eigentlich einfacher. Im Zweifelsfall kannst du uns auch dein Projekt schicken und wir schauen mal…

  • Hallo Philipp, wenn ich das richtig im Kopf habe wird der SysTick in der STM32F10x_StdPeriph_Driver nur für Timeouts benutzt. D.h. dort wird wahrscheinlich nur irgendein Zähler inkrementiert. Das einfachste wäre also den SysTick in der STM32F10x_StdPeriph_Driver nicht zu initialisieren und das Inkrementieren in unserem SysTick Interrupt Handler auszuführen. Alternativ könnte man natürlich auch für das embOS einfach einen anderen Hardware Timer benutzen. embOS ist nicht auf den SysTick angewiesen…

  • Hi Marco, no need to apologize. That's what I assumed since I did the same mistake in the past . Please let us know if we can be of any further help. Best regards, Til

  • Dear Mr. Seitter, most likely the "Printf Integer Support = Long Long" option is not set correctly in your project. Could you please double check that? You could also contact the embOS support directly via our support email address (which you can find in the embOS manual in chapter "Support"). If you like you can send us your project and we'll check it. Best regards, Til

  • Hello, thanks for your inquiry. Quote from bar: “1. Where can I found information about the OS_Init() function? ” Please have a look in the embOS manual which comes with your embOS shipment. It is also available online at: segger.com/downloads/embos/UM01001 Quote from bar: “2. Can I take the embOS example as init structure only use for the RTOS, so Is it right to use all the clock setting and power by the serial example as is or I need to understand what HW setting the embOS example all ready do…

  • Dear Audrey, in my understanding you are using the embOS RX CCRX sources with the IAR EWRX compiler and implement the necessary changes by yourself instead of licensing embOS RX IAR, right? Most likely there is no bug in embOS but in your implementation. What you are currently using is no embOS provided and tested by SEGGER! embOS RX IAR is used in a lot of products without any issues. > This bug appears when two interrupts (nested or with different priorities) run at same time (one interrupts t…

  • [SOLVED] Critical region

    SEGGER - Til - - embOS related

    Post

    Hi Ran, OS_TASK_EnterRegion()/OS_TASK_LeaveRegion() disables preemptive task switches. Whether this has any effect on the BLE stack depends on your application and the BLE stack itself with which I am not that familiar with. Is the BLE communication handled in a task or in interrupts? Best regards, Til

  • Dear Ran, __stack_start_ and __stack_end_ are linker symbols which are used by embOS. Which linker file are you using? With Embedded Studio the GCC linker file is generated from the flash_placement.xml and nRF52840_xxAA_MemoryMap.xml when you build the project. You might want to copy the Start_nRF52840.ld from the \Output folder to e.g. the \Setup folder and use it from there. Does that solve your issue? Best regards, Til

  • The web page is wrong but the embOS manual is correct. We will fix that on the web page now. Thanks for the hint! Best regards, Til

  • [SOLVED] Error in OSKern

    SEGGER - Til - - embOS related

    Post

    Thanks for the additional information. I'll contact you per email for further steps. Best regards, Til

  • [SOLVED] Error in OSKern

    SEGGER - Til - - embOS related

    Post

    Which problem? I can see in your screenshot that you are calling OS_PutMail() from an ISR which is not allowed. Please use OS_PutMailCond() instead. Does that solve your problem?

  • [SOLVED] Error in OSKern

    SEGGER - Til - - embOS related

    Post

    Hello Alex, please understand that it will be hard to help you with this little information. To help us and other forum members to understand your issue you should include at least the following information in your post: 1. Which embOS do you use? (CPU, compiler). 2. The embOS version. 3. A detailed description of the problem. Btw. since your are still in support please feel free to contact us directly by email. Best regards, Til

  • Ok, in that case you'll need to modify the MMU table accordingly since this memory region will most likely be missing. In case of doubt please contact us directly by our support email address. Best regards, Til

  • Hello Arul, it should not be necessary to change the selected target. Did you update the MMU table according to your device/hardware? Are you using one of our BSPs or did you create it on your own? embOS ARM IAR comes with board support packages for various SAMA4D3x boards. Best regards, Til

  • The IAR device definition file uses addresses at 0x3FEFA000: C Source Code (15 lines)This memory region is not mapped per default in our MMU table. But you can easily add an according entry to it: OS_ARM_MMU_AddTTEntries(_TranslationTable, OS_ARM_CACHEMODE_NC_NB, 0x3FE, 0x3FE, 0x001); // IO Area Please note you have to reduce the previous section size accordingly: OS_ARM_MMU_AddTTEntries(_TranslationTable, OS_ARM_CACHEMODE_ILLEGAL, 0x214, 0x214, 0x1EA); // Reserved area In case of doubt I can al…

  • Thanks, we'll have a look into it. Best regards, Til