Search Results

Hi, In general there shouldn't be a problem in using parallel connections to J-Link on macOS anymore. Do you get an error message in SystemView or the debugger when you connect both? This might be related to your target device, which needs special handling to be able to connect to it and then might break the debugger connection. Best regards Johannes

Hi, What changes did you do to FreeRTOS 9? Did you make sure that SEGGER_SYSVIEW_LOCK is configured correctly? Invalid packets can in general only occur when recording a packet is interrupted by another packet, i.e. when interrupts are not disabled. Best regards Johannes

Hi, Yes, _cbSendSystemDesc is the right place to insert SEGGER_SYSVIEW_NameResource(). Which version of SystemView do you use? Which function event does not show the semaphore name? Best regards Johannes

Hi, Thanks for your feedback. Of course our goal is to provide a working solution, so this is always welcome. Regarding Wrong Define: Sure, this will be changed in the next update. Regarding Reading recorded data releases CPU from halt: SystemView does not explicitly let the target run after reading the data, but on some devices the target state is changed when J-Link connects or disconnects. When there is a second connection, the target should usually stay halted, but I'll check if this applies…

Hi, The only peripheral which is simulated is the SysTick. Everything else can only be used on hardware. Regards Johannes

Hi, When you point the project option Debugging -> Debugger -> Register definition file to your .svd file it will work as with the Embedded Studio .xml files. I do not see a problem with the MK26F18.svd Regards Johannes

Hi, The sample you provided runs in the simulator, which does not simulate the DWT. But when I change it to run on actual hardware (Change Target Connection and Target Device Option) it works fine. Regards Johannes

Hi, The status bar shows the value as read from the cycle counter. When it does not go to 0 after writing to DWT_CYCCNT, there must be something wrong with your application. I tried the same in Embedded Studio. The status bar showed 0 and increased and the printf worked accordingly. Regards Johannes

Hi, Your code looks correct. Usually the cycle counter is already enabled after start, but it does not hurt to re-enable it. In the status bar of Embedded Studio you can see the cycle counter, too (as xxx,xxx Cycles). You could check if it is running there. When you step through your code, you should see that it goes to 0 after *DWT_CYCCNT = 0; and continues running from there. Regards Johannes

Hi, We do tests on various versions of Linux. I just ran the installer on a fresh installation of Ubuntu 16.04 and everything works as expected. After you copied the extracted files to your Arch Linux machine, Embedded Studio runs and the GUI is correctly shown? Regards Johannes

Hi, Use -fno-signed-char instead of /J Regards Johannes

Hi, Not entirely sure what a window manager with no desktop environment is, but as Embedded Studio is a GUI application, it might need the desktop environment. Regards Johannes

Hi, With emSecure you cannot do the pure encryption of data, it may only be used to generate digital signatures. We are coming up with a new product which allows you to use more advanced and low-level crypto functions which might fit your needs. It will for example include functions for PBKDF2. Best regards Johannes

Hi, Does it crash on each call in the SysTick Handler? Might it be possible that you do not have enough system stack? As described in the documentation, incoming packets can be handled when creating events, which may require more stack to be available at any time a SystemView event could be generated. Regards Johannes

Ozone V2.22o, which includes the new J-Link V2.12i, is available now. Regards Johannes

J-Link V6.12h includes just one important fix, but not the fix for the crash. A release which includes the fix for the crash (Ozone V2.22o and J-Link V6.12i) is planned for tomorrow. Regards Johannes

Hi, Okay, now I get your question. What you can do in Embedded Studio is, you can move any file to any dock, which will open it there for editing. In this case, the Label like "Project Explorer" is replaced with the files opened in the editor of this dock. If no files are in a dock (which is the standard) it will display this information on click on the label. We might remove this one to not cause further confusion. Regards Johannes

Hi, We found an issue regarding additional J-Link licenses, which could cause the crash on macOS and Linux. Since J-Link PLUS already includes the license for Ozone, this combination does not crash. The fix will be part of the upcoming release of the J-Link software. Best regards Johannes

Hi, To enable display of peripheral registers in the registers window, you can set the project option Register Definition File at Debugger -> Debugging. This can be in either the embedded Studio XML format or an SVD file. Could you provide more details on the "No Editor" pop-up? When does it show up? Where does it show up? Regards Johannes

Hi, Embedded Studio does not take the include directories from the project folders. Instead, as with most toolchains, you need to specify them in the project options. To do this, in the project options go to C/C++ -> Preprocessor and add CException, or the directory CException.h is located in, to the User Include Directories. Adding CException.h to your Embedded Studio project will do nothing but showing it there. To add a library, you can either have a solution with your application project and…