Search Results

Search results 1-20 of 54.

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

  • Hi Audrey, Quote from AudreyD: “Don't you think there could be a problem with the region counter ? ” From your description and screenshots, I'm afraid I cannot see how this would be related to the region counter. Also, as til had mentioned previously, embOS RX IAR is used in a lot of products without any issues. Still, we'd of course ike to be able to reproduce the observed problem for a better understanding of what actually happens with your application. A screenshot of the call stack once insi…

  • Hi Audrey, I've quickly tried to reproduce the observed issue, but to no avail. Does your application utilize ISP or USP when the SystemView init function is called? This is for the reason that, generally speaking, OS_ERR_ILLEGAL_IN_ISR will only be issued when an embOS API function that mustn't be called from an ISR was called from an ISR. However, main() will initially utilize the interrupt stack as well, which may have resulted in a false-positive detection if any embOS API function was calle…

  • Hi Audrey, Okay, so it's not embOSView but SystemView that fails to start. This, however, is somewhat expected: Auto-detection of the RTT control block will typically search through internal memory only, since J-Link cannot know the exact layout of your external memory. Hence, if the control block is located in external memory, its adress needs to be explicitly specified in the connection dialog, e.g.: forum.segger.com/index.php/Att…e40462579c21a2ecf328f67f9 If you don't know the adress of the R…

  • Hi Audrey, Generally, no additional configuration is required even when part of the code is stored in external memory. Can you tell in more detail which problems do occur? Are you using J-Link as communications interface between target and host, or are you e.g. using UART instead? Does the embOSView log ("View" -> "Log" from the menu) show any error conditions? Best regards, Martin

  • Hi bar, Sorry for the delay in reply, unfrotunately I haven't been in office for a few days. If "Edit section placement" is not shown in the context menu, that typcially indicates no valid placement file was found or, alternatively, no placement file was specified at all. Therefore, could you please check if the path and file name in "Project options -> Code -> Linker -> Section Placement File" do specify a valid placement file? Best regards, Martin

  • Hi bar, If all source files, librararies and include paths from the Nordic project are added to your project, there should be no unresolved references to Nordic API functions. In addition, you'd need to merge the flash_placement.xml and possibly the nRF52840_xxAA_MemoryMap.xml. To do so, please right-click on the project and select "Edit section placement" or "Edit Memory Map", respectively, and manually edit the files: forum.segger.com/index.php/Att…e40462579c21a2ecf328f67f9 nrf52840_Registers.…

  • Hi bar, __start_nrf_section should be defined in the flash_placement.xml of the original Nordic project. Apparently, you're not using that in your combined project (i.e. did not merge the placement files from both projects). The same applies to other symbols, e.g. __end_nrf_sections_run, __stop_log_const_data, __start_log_const_data, __start_log_dynamic_data, or __start_pwr_mgmt_data: they, too, are defined in Nordic's placement file. Other undefined references include functions like ble_nus_dat…

  • Hi bar, The embOS for Cortex-M and IAR project you're referring to probably is the generic CMSIS project. Such generic project, of course, is available with embOS for Cortex-M and ES, too. Please find it at $ROOT$/Start/BoardSupport/CMSIS/Generic/Start_CMSIS_Generic.emProject within our most recent embOS for Cortex-M and ES trial and/or regular shipment. However, it's also possible to sort out the multiple definition problems by merely excluding the files contained in the folder DeviceSupport of…

  • Hi Audrey, Please understand we can't give support on a customized embOS. However, we do offer an official embOS port for RX and IAR compiler as well. Please refer to our website for further information. If you're interested in obtaining that port, please let me know and I will ask my sales colleagues to provide you with an official quote. Best regards, Martin

  • Hi Audrey, Thanks for providing further information. Quote from AudreyD: “The device we use is R5F563NE in OS_LIBMODE_DP. The compiler we use is IAR C/C++ Compiler for RX v1.09, in IAR Embedded Workbench IDE - RX 3.10.6. ” Could you please confirm that it's actually IAR? I'm afraid I can't find a license for your company for embOS for RX and IAR in our database, but for embOS for RX and CCRX only. Or, are you currently using the CCRX port with IAR? Best regards, Martin

  • Hello Audrey, Thanks for your inquiry. While we're not aware of any issues with embOS V4.02a for RX and CCRX, we of course would like to assist you in finding the root cause for the observed problem. Quote from AudreyD: “In which cases the region counter could be equal to zero, since before OS_ChangeTask() is called, the counter is either incremented, either set to 1. What could be the "other internal error" ? ” With embOS V4.02a, OS_ERR_INTERNAL is issued exclusively when the region counter is …

  • Hello bar, Quote from bar: “1.In my embOS I fond this file RTOSInit_nRF5x.c Is this is the right one? ” Yes, that's the right one. Quote from bar: “2. for the _WFI I found this function void OS_Idle(void) { // Idle loop: No task is ready to execute while (1) { // Nothing to do ... wait for interrupt #if ((OS_VIEW_IFSELECT != OS_VIEW_IF_JLINK) && (OS_DEBUG == 0)) //__WFI(); // Switch CPU into sleep mode #endif } } _WFI all ready close. Is this the right function? ” Yes, that's the right one as we…

  • Hello bar, and thanks for your inquiry, Unfortunately, there's no automated way to merge the projects: You'd have to manually add the files to your project tree and subsequently add the include paths as well. Once done, you'd also need to perform 3 minor modifications to the board support package that was shipped with embOS to work with the BLE. That is, first, the embOS BSP file RTOSInit.c will typically include a line to set the Vector table offset register. This can't be done when utilizing B…

  • Hi Ran, Quote from wrani: “Note that I see those symbols in ses_startup_nrd52840.s :"_vectors: .word __stack_end__" but not in ses_startup_nrd52840.s which is used when building from "armgcc" ” This is correct. With the armcc startup code, __initial_sp is used instead of __stack_end__. Hence, you will find a line like Source Code (1 line) in the armcc startup. Yet, both __initial_sp and __stack_end__ are linker created symbols, respectively. Since embOS for Cortex-M and Embedded Studio does rely…

  • Dear Vakaras, I'm glad to announce that the requested functionality will be included with upcoming versions of embOS. That is, V5.06 and later will include a OS_DEBUG_RemoveObjName() function, which may then be used in combination with e.g. OS_free(MailboxName). Best regards, Martin

  • Dear ptiguitardenver, Thanks for your inquiry. With embOS, users may choose between two distinct approaches: mailboxes and queues. While mailboxes work on fixed size messages only, a queue with embOS does in fact accept messages of variable size and will handle those dynamically. That, however, does not mean one single message may wrap around the ring buffer: Instead, if no sufficient space for the particular message is available at the end of the buffer, embOS will try to store the entire messa…

  • Hello Christian, Thank you for your inquiry. We do in fact provide appropriate layers for both the CMSIS-RTOS v1.0.2 and CMSIS-RTOS v2.1.0 API, but also, as you already noticed, do not recommend to use them in a product for several reasons (limited number of features, decreased performance, etc). If their usage in a product is mandatory, however, as it seems in your case, there is no restriction on mixing the CMSIS-RTOS API with native embOS API. Therefore, it's perfectly possible to use CMSIS-R…

  • Dear Vakaras, Thank you for your inquiry. Calling free() on MailboxName is not possible at this particular time. It may, however, be reassigned for any other object by calling OS_DEBUG_SetObjName() on MailboxName again. Please let me know if I can be of any further help. Best regards, Martin

  • Hi PTepe, Thanks for your feedback, we'll consider this case solved then. Quote from PTepe: “In my EmbOS version I don't have OS_TIME_Getus64() but I do the substraction and now I'm also sure what the return range of OS_GetTime32() is. ” This function was called OS_GetTime_us64() with previous versions of embOS. Since V5.00, it's called OS_TIME_Getus64(). Best regards, Martin

  • Dear shal, It seems the hardfault was caused by an unaligned memory access. Does your application use the STM32F7's external SDRAM? If so, the hardfault is probably related to the hardware's memory specifications. This is for the reason that the STM32F7's SDRAM is mapped to 0xC0000000 - 0xC03FFFFF. That area, however, is specified as device memory type according to the ARMv7-M architecture. This means that all accesses to this area must be naturally aligned, whereas any unaligned access will cau…