Search Results

Hello, could you please provide us your ELF file? You can email it to https://www.segger.com/support/technical-support/ using "JScope beta 611k crashing" as subject. Regards Arne

Hello Johan, an RTOS in general might leave registers untouched when switching to another task, so having access to CPU registers is a good idea. We will add functions for reading/writing CPU registers to the GDB_API structure in the GDB server and then update the SDK. Regards Arne

Hi, the RTOS Plugin is loaded when the GDB client starts serving symbols ('qSymbol' packet). Best regards Arne

Hi, using RTT the channels are reset to default values on every start of a sampling session. I tried using HSS, which behaves different and keeps the scaling values for future sessions. I will put this on the feature request list, currently there is no way to keep the scaling values for RTT sessions. Best regards, Arne

Hello Bruno, the reason for this behavior is the GDB client, which immediately starts the target over and over again. Can you provide us a project for reproduction on an FRDM-K82F eval board? Best regards Arne

Hi, I did not see this behavior during my tests, the Y-Offset should never be set automatically. Autoscaling should also be turned off, when you change scaling manually for the first time. Could you please send me your project file? Best regards Arne

Hi, did you try the latest version? I just tested it with the 5.10d and 6.11j, the settings (Y Resolution and Offset) are saved and restored correctly with the project. The values are named YOffset="..." and YResolution="..." in the project file. Best regards, Arne

Hello, the channel names for RTT are currently limited to 32 bytes in the J-Link API (max. 31 characters with zero termination). Therefore, the last 4 characters of your 35 characters string are cut and only 12 variables are parsed instead of 14. We have added the option to use longer channel names to our feature requests. We cannot give you an exact schedule about the implementation. But as soon as this is possible, J-Scope will be updated to use it. Best regards Arne PS: Please try the new J-S…

Hi, FreeRTOS has the ability to use "port optimized task selection". This setting causes the internal priority variable to become unpredictable. Could you please try to define configUSE_PORT_OPTIMISED_TASK_SELECTION to 0 in your FreeRTOS configuration? Best regards Arne

Hello Makineci, see J-Scope user manual (UM08028) Chapter 11: RTT: Instrumenting an application to use it with J-Scope There is also an embedded studio sample project using RTT mode in the J-Scope installation directory. Best regards Arne

Hello Makineci, on PC side no additional tools are required. RTT needs to be implemented into the target application and to be configured for J-Scope. "Sample\Example Code RTT" in the J-Scope installation directory contains a sample project. The documentation on how to use RTT with J-Scope is located in the J-Scope manual (UM08028): "Chapter 11 - RTT: Instrumenting an application to use it with J-Scope" Best regards Arne

Hello Makineci, for higher sampling rates via HSS, a J-Link Ultra+ or J-Link Pro is required. However, due to limitations of the debug interface and debug logic, the upper limit (depends on the used MCU and the number of memory locations to sample) is at about 20kHz. Alternatively, you can use the RTT interface to send the data to J-Scope. This will give you a higher bandwidth in total, but it requires some resources on the MCU. Best regards Arne PS: Please try our latest J-Scope beta.

Hello, could you please enable the GDB server's log file? wiki.segger.com/Enable_J-Link_log_file#J-Link_GDB_Server In case of an error, the GDB server should always report back a single task (thread) with the current register values. Best regards Arne

If stack size is a problem, maybe some of the FreeRTOS control structures are already damaged. This will lead to the effect you are experiencing, because the plugin reads pointers and then tries to read memory from this location. Of course the plugin has no chance to display any reasonable results if any of the control structures are damaged. But I can only guess here...

Hi, you wrote, you have 10% success rate. Is this related to exactly the same binary or to 10% of the builds? Best regards Arne

Hello Karlheinz, could you please create a J-Link and a GDB server logfile? wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File The CPU must have been stopped, otherwise the plugin will never try to read memory. Maybe the CPU was immediately restarted. Regards Arne

Hello Karlheinz, the RTOS plugin only gets active, if the CPU stops. There is no kind of "background monitoring" while the CPU is running. So, if there is no breakpoint at "pxCurrentTCB = pxNewTCB;", why does the CPU halt? Are you single stepping in this function? Does it also stop on this line, if the RTOS plugin is not loaded? Regards Arne

Hi, please try setting "configUSE_PORT_OPTIMISED_TASK_SELECTION" to 0. I still could not reproduce a GDB server crash in case of this error (Error reading stack frame from FreeRTOS task.) But this error will result in an incorrect packet sent to the GDB client, which should not be the case. This will be fixed in the next software release (6.18b). Regards Arne

Hello Dave, the "Task List" in your screen shot has nothing to do with our task awareness feature. Our feature only helps the Eclipse IDE to build up its pretty tree view of tasks. The task list results from a different plugin. Probably this plugin gets confused if the structure of the task control block, which depends on various configuration settings, is different from what it expects. Best regards Arne

Hello, you can write the plugin by yourself, we offer a SDK for that purpose. J-Link GDB Server RTOS plug-in SDK I had a quick look at the port for Cortex-R. As it uses a different method to save the task context, the plugin for Cortex-M will not work. Best regards, Arne