Search Results

Hi Austin, Thank you for the provided project. We are able to reproduce this issue and will be looking into it as soon as possible. I will keep you posted. Best regards, Fabian

Hi, Good to hear that you are up and running again. We will close this thread now. Best regards, Fabian

Hi, Thank you for your inquiry. The issue is caused by a different bug that was recently fixed. Could you please update to the latest version and try again? segger.com/downloads/jlink#J-L…twareAndDocumentationPack Best regards, Fabian

Hi, Thank you for your inquiry. I just gave this a quick try and on my and everything is working as expected (auto search and search range). Setup: - STM32F746G-DISCO - J-Link Plus V10 - J-Link Software V6.94a - The sample (hex file): download.segger.com/Fabian/STM32F7_RTT_Sample.hex It is a small printf() loop sample, linking the the SEGGER RTT CB to 0x2004ef78. Could you please tell us if the RTT sample above works on your side, too? Could you please provide us with a small example project or …

Hi, Thank you for your inquiry. There is no issue known to us connected to the STM32F4 devices. I noticed that you do not use the latest version of the J-Link Software, apparently. Could you please download the latest version and try again? You can find it here: segger.com/downloads/jlink#J-L…twareAndDocumentationPack If the issue persists after updating: 1) Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File 2) Could you please send us th…

Hi, Thank you for your inquiry. I moved this thread to the correct sub-forum. To answer your questions: The SDK is not required for RTT. You can probably find all required information here: wiki.segger.com/RTT Best regards, Fabian

Hi, We would need access tomorrow, for the whole day. That way we can make sure that we have enough time to make this work. I will send you a DM with further instructions. Best regards, Fabian

Hi, Update: We added support for this and updated the Cortex-M template accordingly: wiki.segger.com/Open_Flashload…ortex-M_template_projects Best regards, Fabian

Hi Pengfei, There are no issues known to us related to this device. I just gave this a quick try on an evaluation board () and everything works fine on our side: forum.segger.com/index.php/Att…dc1df683b6af6edc2d8ff7b53 If the shared signal wires are in issue here depends on what the FT230 does. If the FT230 sends any signals over the shared lanes, yes this would be an issue. Just to exclude this as a possible source of trouble: Does it also fail when you select JTAG as interface? Best regards, F…

Hi, Thank you for your inquiry. If the device is compatible to the other C8051FXXX devices we can add support for it short term. Unfortunately, we do not have any evaluation board for this chip in house and as far as I can tell there also is none available. Three options: Could you either 1) point us to an evaluation board for this device or 2) send us the board/hardware you are using or 3) provide us with remote access to the hardware so we can add and test the device support? Best regards, Fab…

Hi, Good to hear that you are up and running again. We will close this thread now. Best regards, Fabian

Hi, Okay. Unfortunately, there is not much we can do in this case. Best regards, Fabian

Hi, Thank you for your inquiry. Such an issue was not yet known to us. I agree that if other people complained about similar issues, the root cause would most likely be related to the Surface and not to the J-Link. Especially since this issue does not seem to appear on other Computers/Laptops. When RTT is active, the J-Link rapidly reads the RTT Control block on the target side. The result of these reads is passed to the host system (in your case the Surface) which results in very frequent USB t…

Hi, Thank you for your inquiry. IAR implements device support themselves and does not use the J-Link device connection sequence implemented by SEGGER. You would have to contact IAR support regarding this. Best regards, Fabian

Update: The root of this problem was that Keil was not launched with Admin rights. When launched with Admin rights the J-link debugger was selectable and the SETTINGS menu could be opened. Best regards, Fabian

Hi, Thank you for your inquiry. The template is designed to only implement what is necessary for the RAM code to work. Usually it is only supposed to write registers and such.Integrating the libc would make the RAM code unnecessarily big. The idea of a RAM code is to be as bare metal and small as possible. That way a better performance with less size is achieved. To integrate a library into the RAM code, you would have to make sure that it is linked correctly. As this is not intended, please und…

Hi, Good to hear that you are up and running again. As the issue is solved, we will close this thread now. Best regards, Fabian

Hi, Okay. As this seems to be an issue with the KEIL installation process, we will close this thread now. Best regards, Fabian

Hi, Thank you for your inquiry. Such an issue is not known to us. The JL2CM3.dll is shipped by KEIL. Is the JL2CM3.dll is not present in that directory? If not, it was probably deleted somehow. You could try to reinstall the IDE. If this does not help, we would suggest to contact KEIL regarding this. Please understand that there is not much we can do here as this is a KEIL related issue. Best regards, Fabian

Hi, Good to hear that you are up and running again. We will close this thread now. Best regards, Fabian