rtos

问题 I have a requirement which need to repeatedly allocate and deallocate memory. Currently trying it on Integrity ARM simulator. I have created two tasks : First task(encoder): receives video data from a socket and encodes it and send it to second task. Second task(decoder): receives data from encoder and decodes it. In this decoding process it dynamically allocates memory and after decoding deallocates memory. After some time decoder task is suspended and cannot read protected memory error

问题 I am an RTOS newbie and I am creating a simple real time system for automotive I am wondering if it possible to create a task inside another task. I tried to do this by the following method but it doesn't work. void vTask1 { *pvParameters){ unsigned portBASE_TYPE taskPriority; taskPriority=uxTaskPriorityGet( NULL ); char x; while (1){ x= 5 ; if (x==5) xTaskCreate( vTask2 , "task2", 1000, "task2 is running", taskPriority+5 , NULL ); } when I debug that code it hangs at xTaskCreate without

问题 A little intro, I am currently writing a small (read tiny) RTOS kernel, well it's supposed to be monolithic with most stuff in the kernel. However I can't find much information on a few things listed below, It would be a lot helpful and besides this, it isn't actually some kind of university project but something I'm doing at my own will. A better alternative to answering all the questions would be if you could refer to me a freely available RTOS (or even a free book) for arm preferably which

问题 I am currently in the process of developing the OS for a consumer electronics product my company is developing. I have settled on freeRTOS as the backbone for our OS, and am working diligently to implement hardware functionality within the OS. However, I have run into an issue concerning running 3rd-party applications from within freeRTOS. Originally I considered a task to be an application, where basically you had "myapplication.c" and "myapplication.h" containing all your applications

问题 I am currently in the process of developing the OS for a consumer electronics product my company is developing. I have settled on freeRTOS as the backbone for our OS, and am working diligently to implement hardware functionality within the OS. However, I have run into an issue concerning running 3rd-party applications from within freeRTOS. Originally I considered a task to be an application, where basically you had "myapplication.c" and "myapplication.h" containing all your applications

问题 I read two different definition for 'interrupt latency' in RTOS. "In computing, interrupt latency is the time that elapses from when an interrupt is generated to when the source of the interrupt is serviced" (source: https://en.wikipedia.org/wiki/Interrupt_latency ) "The ability to guarantee a maximum latency between an external interrupt and the start of the interrupt handler." (source: What makes a kernel/OS real-time? ) Now, my question is what is the correct definition of 'interrupt

问题 I was studying uC/OS and read this article: Because different microprocessors have different word length , the port of μC/OS-II includes a series of type definitions that ensures portability Specifically, μC/OS-II’s code never makes use of C’s short, int and, long data types because they are inherently non-portable. Instead, I defined integer data types that are both portable and intuitive as shown in listing 1.1. Also, for convenience, I have included floating-point data types even though μC

问题 Can anyone help me on design patterns commonly used for RTOS? In VXworks, which pattern is more preferable? 回答1: Can we ignore the second sentence in your question? It is meaningless, and perhaps points to a misunderstanding of design patterns. The first part is interesting however. That said, I would generalise it to cover real-time systems rather than RTOS. Many of the most familiar patterns are mechanistic, but in real-time systems higher-level architectural patterns are also important.

问题 If I have a non-RTOS single core system, can one task, say taskA interrupt another task, say taskB, where neither taskA or taskB are interrupt routines? Or is interruption of one task by another only possible through ISR(interrupt service routines) on non-RTOS systems? 回答1: For your system to have more than one non-ISR thread implies that there is some sort of multi-tasking - and multi-tasking is not exclusive to an RTOS. One task "interrupting" another is known as preemption . Preemption

问题 We are using the μC/OS-III RTOS of Micrium with a RX62N of Renesas. We built a system where we have to dynamicly alloc and free data. We found out the functions malloc() and free() are not working well with the RTOS. However the RTOS has a custom function for this; the Mem_HeapAlloc() function. This function allocates some memory of the RTOS' made 'heap' . Problem is that it does not have a free function, probably because everything goes into a heap pool . In the RTOS it is also possible to