Search Results

Hello, you are right, there was a mistake, I fixed the uart routines. I am sorry for any inconvenience caused by this. Regards, Til

Hello, this is not a smart workaround since you only have disabled the embOS debug tests, which means, that the problem could still exist. We can support IAR PowerPac customers when they buy a new Segger support agreement. If not please contact your IAR support. Best regards, Til

Hello, please let me know if your using embOS ARM IAR trial version from our webpage or which embOS version you are using. We have no BSP for TMPA900 in embOS ARM IAR so far, but it should be similar to BSP for TMPA910. With embOS ARM IAR you don't have to call OS_EnterInerrupt()/OS_LeaveInterrupt() becasuse it is already called in OS_irq_handler(). Please contact us directly (support@segger.com), I am sure that I can help you to solve your problem in short time. Best regards, Til

Hello, there are no technical difference, you are right, it is the same code. There are differences in the licensing models and prices. If you buy from us you get of course the support also directly from us. Please contact us directly for more details. Best regards, Til

Hello, please have a look in the embOS cpu/compiler specific manuals, I believe that most of your question are answered there. Quote: “In a project targeting the RX platform, and using the GNU RX toolchain, where is ram_start defined?” This label is set in the linker section settings. Quote: “L2310 (E) Undefined external symbol "_OS_CreateTaskEx_R" referenced in "C:\Code\MyProject_HEWRX\Debug\debugtask.obj" L2310 (E) Undefined external symbol "_OS_CreateTaskEx_R" referenced in "C:\Code\MyProject…

Hello, it seems that IAR did not include the embOS libraries for an unknown reason. Please download our latest embOS Cortex M IAR trial version at segger.com/cms/download_embos-arm-cortex-m3-iar.html. Best regards, Til

Hello Arne, Quote: “Is TimerRoutine1 called and as soon as it is finished the OS-Scheduler calls TimerRoutine2? ” Yes, it is like this. The scheduler runs all callback functions where the software timer is expired. Quote: “Do they use the stack of the thread they just interrupted or the stack of main()?” The software timer callback functions run like the scheduler on the C-stack. The C-stack is the stack which is used in main() before the call of OS_Start(). Best regards, Til

Hello, we do not have a MSP430FG4619 BSP for embOS MSP430 TICC so far, but we can create it for you. Please contact us directly per email at support@segger.com. Regards, Til

Hello, we will check if we add a test for this parameter in OS_CreateTask()/OS_CreateTaskEx(). Regards, Til

Hello, you cannot use OS_CONFIG() with a higher timer interrupt frequency, you can use it only with lower timer interrupt frequency. Why do you want to change the timer interrupt period to 0.2 msec? I suggest to use another hardware timer for the embOS system tick interrupt if you need this 0.2 msec period. Regards, Til

Yes, depending on the string functions like printf() and sprintf() uses a lot of stack. Please ensure that your task stack size is big enough.

Hello, we are not aware of any problems with sprintf() and embOS. I tried to reproduce the problem with IAR simulator and our embOS start project but I cannot see any problem here. My task looks like this: C Source Code (8 lines) What exactly happens when you talk about a crash? Did you try to call sprintf() without embOS? Is the character array as first paramter for sprintf() bigh enough? Regards, TIl

Hello Kam, I just tried it and it works without any problem. Could you please try it again? J-Link Software If you have no success please write us an email and I will send it to you per email or upload it to another server. Regards, Til

Hello, yes, you can of course use JTAG insetad of SWD, I guess your JTAG/SWD option is disabled because Semihosted is enabled. Please have a look in the build settings in "General options" -> "Library Configuration" and set the "Library low-level interface implementation" to "None". Regards, Til

Hello, the linker message reports that the embOS library is missing in your project. Since I guess you use one of our start projects th embOS library is already included in the project. Could you please let me know which embOS do you use? I guess it is embOS CM3 IAR? (Just tell me the filename of the downloaded file). Which IAR compiler version do you use? If you like you can contact us directly (support@segger.com). I am sure that I can help you with the first steps with embOS and IAR. Regards,…

Hello, you can use embOS of course with C++, you don't need the source code version, the object version is enough. If you like you can download the embOS RX HEW trial version from our website. It has no functional limitation, so you could test by yourself that it works with C++. If you have any further question you are invited to contact us directly. Regards, Til

Hi Dominik, I guess you use the trial version of Atollic TrueStudio? In this version you can select only the ST Link as debugger, this is a limitation of the the free trial version. Why do you want to use Atollic TrueStudio? There exists some toolchains which are easier to use. for example Rowley Crossworks (rowley.co.uk) or IAR Embedded Workbench (iar.com). You can use J-Link with these toolchains also in their trial versions. Regards, Til

Hello, If you want to evluate embOS for R8C you could make the BSP on your own, there should be no major differences between R8C/23 and R8C/2B. Please contact our sales team per email (info@segger.com), I am pretty sure that we can help you to find a solution to evaluate embOS. Regards, Til

Hello, please be aware that microcontroller tracing with J-trace and tracing embOS API calls with embOSView are two different things. If you want to to trace only embOS API calls you can use embOSView with serial connection or for some microcontroller with J-Link (ARM7, ARM9, CortexM3, ...). You can use there different filters. If you want to use microcontroller trace you need J-Trace and a software like IAR Embedded Workbench. You can't use for this embOSView. Regards, Til

Hello, could you please explain your question? I am afraid that we do not understand it. Which box do you mean? Regards, Til