Search Results

Hello Benjamin, Thank you for the additional details. A buck converter is usually famous for ripple/noise due to its switching design. So an LDO is generally recommended instead for embedded designs where applicable. Here is a nice article I found in this topic: resources.altium.com/p/using-l…tching-regulator-your-pcb But before you go and redesign your board I recommend to hook up an oscilloscope and see how the signal looks in circuit. Do you see the same pattern there as well? I recommend to …

Hello Pawel, That is strange indeed. Do you see the same behaviour with the latest V3.50a release of SystemView? If yes, do you have another Linux VM or PC to test against? Do you see the same behaviour there? Which Linux are you using exactly? Best regards, Nino

Hello, Thank you for your inquiry. Generally SystemView should be able to record as long as you like. If that is not the case this is usually caused by a setup issue. Could you first try using the latest SystemView version V3.50a and update the target sources as well? Does it work now? If not, did you follow the following guide from our Wiki? (assuming you are using FreeRTOS here like in your other thread) wiki.segger.com/FreeRTOS_with_SystemView Best regards, Nino

Hello, Thank you for your inquiry. It appears that either SystemView is receiving an incorrect package or the debug interface is being disabled by your application. Are you using any low power/sleep modes? Could you try the latest SystemView version V3.50a and update the SystemView target sources accordingly in your project? If it still shows this issue could you provide a J-Link log file of the failing session? You can enable it in the SystemView recorder settings. Does your application work st…

Hello, Thank you for your inquiry. This does not sound like the right approach to tackle the issue you are seeing. Currently it sounds more like a project setup issue. The toolchain should provide all necessary libc symbols out of the box. Could you provide a small example project that shows the "undefined reference to `__libc_init_array'" error? On another note. Is there a specific reason you are using the gnu linker instead of the SEGGER linker? Is there some feature missing or did something n…

Hi Sharon, Quote from sharon: “but I have no idea that my post was deleted? ” As said before. Thread bumping is not allowed. J-Link team will answer when they have time. If you require a guaranteed and fast response we recommend to use our official support channels. Best regards, Nino

Hello, Thank you for your inquiry. Such an issue is not known to us. Could you provide your J-Link serial number for reference? You can find it at the bottom starting with with S/N. Are you powering your board/chip only via the debug interface or are you also powering via some external power source? Best regards, Nino

Hello, yes, no thread bumping. Please understand that this is not a support forum. If you qualify for support please use our support channels as explained in my signature. There is no guarantee that you will receive an answer via this forum. Best regards, Nino

Hello, Thank you for your inquiry. Quote from fraengers: “Is the only thing Ozone can do with with the SWO-pin print text to terminal? ” Correct. SWO tracing is on the wishlist with low priority. If you need SWO tracing now with J-Link Embedded Studio can be used: wiki.segger.com/Configure_SWO_in_Embedded_Studio Best regards, Nino

Hello, #if blocks are indeed not supported yet. We have added this to our wishlist for a future Embedded Studio version. To get automatically notified when new versions of Embedded Studio launch you can subscribe here: segger.com/notification/subscribe.php?prodid=196 Best regards, Nino

Hello, Thank you for your inquiry. That version of Embedded Studio does not support code folding. It was added with version V6.32. So any version newer than that should have that feature. Best regards, Nino

Hello Lothar, You have to supply the memory information to your Embedded Studio project so the debugger knows there is valid memory there and it may access it during debugging. On many target devices there are memory sections e.g. ROM Bootloader (RP2040 has this as well) where they could jump to during run time and depending on the chip it might then crash or even get bricked. So as a precaution the debugger will only disassemble known memory areas. To supply such area you can either use a memor…

Hello, Thank you for your inquiry. As _frank_ correctly stated dynamic libaries on bare metal embedded systems is highly atypical. Usually you link only statically on embedded systems (.a files + their respective headers). For dynamic linked libraries you essentially need a fully fledged OS like Linux running or at least an RTOS, Filesystem and most likely an MMU. Also your dll would need to be build for your target system architecture. If I had to guess none of these prerequisites fit your setu…

Hello, Please note that discussing J-Link SDK documentation and API in the public is a license violation. For support please use our dedicated support channels as explained in my signature. This thread will be closed now. Best regards, Nino

Hello, Thank you for your inquiry. Please understand that we do not provide support for such old Embedded Studio versions as they are out of maintenance and thus support. Is the issue reproducible with the latest Embedded Studio version V7.12 as well? If yes could you provide an example project for reproduction with reproduction steps? Best regards, Nino

Hello, Thank you for your inquiry. No there is no way around the MAC address if you plan on using the free Nordic license. But you can of course generate as many licenses as you want. If you have a build system that e.g. does not have a fixed MAC address we recommend to purchase a so called "Automated Environment License". segger.com/purchase/licensing/license-cul/ For a quote feel free to contact our sales: segger.com/purchase/request-quote/ Best regards, Nino

Hello, Thank you for your inquiry. Could you try using the latest SystemView sources and SystemView version? You see to have a version mismatch there. Additionally here is a Wiki article describing how SystemView should be used on FreeRTOS: wiki.segger.com/FreeRTOS_with_SystemView For more details about troubleshooting see the SystemView reference manual. Best regards, Nino

Hello Matthias, is this matter resolved? Because in your other thread you wrote that you were able to instrument your application as documented. Best regards, Nino

Hello Matthias, Thank you for your inquiry. Generally when using SystemView J-Link will not reset the device on record start. Only if necessary. There are sometimes chips or even architectures that do not support attach mode so this might be one of them. How did you determine that the device is reset? What kind of reset is issued? Reset Pin toggle or Software Reset? Are you using FINE or JTAG as debug interface? Could you provide a J-Link log of the SystemView session? wiki.segger.com/Enable_J-L…

Hello, Thank you for your inquiry. Please note that this is a community forum. For support please see the links below in my signature. We recommend to open your inquiry via our support channels. Best regards, Nino