Search Results

Search results 1-20 of 434.

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

  • Hi, Thank you for your inquiry. We are sorry for the delay in response. We have been very busy with pressing projects for the last weeks. Good to hear that the issue has been resolved. Quote from Hardwariano: “Although I sent a ticket explaining the issue, I didn't get any response ” This should not have happened. Could you please tell me the inquiry number of the ticket you opened? Best regards, Fabian

  • Hi, Thank you for your inquiry. We are sorry for the delay in response. We have been very busy for the last weeks. We currently only provide debug support for Cortex-A53 devices. This is because 64 bit cores are not our main business, as > 90% of the users debug with a Linux on these devices and not bare-metal. We will add support at some point, but we cannot give a fixed timeline for it. What we can say is that this will not happen this year. Best regards, Fabian

  • Hi Dave, Thank you for your inquiry. There is no such issue known to us. Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Do you use custom hardware or an evaluation board? In the latter case which one? If custom hardware, do you experience the same problem on an evaluation board? Best regards, Fabian

  • Hi, Good to hear that you are up and running again. As this issue does not persist anymore, we will close this thread now. For completion: VTref is the reference voltage, provided by the device, not the J-Link. The J-Link is using it as reference voltage for the communication with the device. Best regards, Fabian

  • Hi, Thank you for your inquiry. Did you make sure that the eval board's ST Link is the only ST Link plugged into your PC? Best regards, Fabian

  • Hi, Just to make sure that I understand you correctly: The issue does not appear on the eval boards "STM32F407 and STM32F429 disco", but only on your custom hardware? When power-cycling the device I assume you end the debug session beforehand and start a new debug session afterwards? As already requested: Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Best regards, Fabian

  • Hi Brian, Thank you for your inquiry. Could you tell us where exactly you found this information? I am asking because we would like to correct the related section. Our limits as of now are: Max number of devices in chain: 32 Total IR length: 255 Max DR length: 64 (Max. DRLen of the device we talk to in bits) Best regards, Fabian

  • Hi, Thank you for your inquiry. Each core is supposed to be added as a separate device. For example: Device_M4, Device_M0 Does this answer your question? Best regards, Fabian

  • Hi, As you did not answer to our questions/answers in any channel, we will close this thread. Best regards, Fabian

  • Hi, Thank you for your inquiry. We are sorry for the delay in response. The last weeks have been very busy. From what you say, this issue might be connected to KEIL. Does debugging via SEGGER Ozone work as expected? segger.com/downloads/jlink#Ozone Best regards, Fabian

  • TI C2000 Support

    SEGGER - Fabian - - J-Link/Flasher related

    Post

    Hi Torsten, Thank you for your inquiry. Sorry for the delay in response. We have been very busy for the last couple of weeks. TMS320F support is not currently planned as for the low demand and the considerable effort to add support. Would you require flash or debug support? Best regards, Fabian

  • Hi, Thank you for your inquiry. There is no issues known to us related to RA6M devices. Do you use custom hardware or an evaluation board? In the latter case which one? If custom hardware, do you experience the same problem on an evaluation board? Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File What OS are you running this VM on and which VM program do you use for it? Best regards, Fabian

  • Hi, As you contacted us via Support Ticket system, and your question was already answered, we will close this thread. For the future: Please try to keep flow of information to one channel, as this is considerably lessening our work load and handling times. Also please refrain from opening several inquiries for the same question. Best regards, Fabian

  • Hi Bram, Thank you for your inquiry. We are sorry for the delay in response. The last weeks were very busy on our side. IAR implemented SWO themselves, and controls the J-Link directly, so we do not have any influence on how they enable it. You would have to contact IAR regarding this. Best regards, Fabian

  • Hi, Thank you for your inquiry. From your post, it Looks like there is a power issue. Could you please make sure that - the J-Link is directly connected to the PC, and not to a USB-Hub - the Device is correctly powered externally. Are you using the J-Link you registered with? The S/N of that J-Link is from a unit from 2012 which is out of support and maintenance. We recommend to make use of our trade-in program: segger.com/purchase/trade-in-program/ Best regards, Fabian Federschmidt

  • Hi, Thank you for your inquiry. We are sorry for the delay in response. We have been very busy with some pressing projects for the last weeks. There is no issue known to us regarding J-Link GDB Server and the S32K device family. Could you please send us J-Link log files of both sessions? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Do you use custom hardware or an evaluation board? In the latter case which one? If custom hardware, do you experience the same problem on an eval…

  • Hi, Thank you for your inquiry. We are sorry for the delay in response. We have been very busy with some pressing projects the last couple of weeks. Such an issue is not known to us and we are not able to reproduce it: forum.segger.com/index.php/Att…9d96b023545f8ccf9d64ab473 Setup: - Ubuntu 20.04 - Ozone V3.20e - J-Trace PRO Cortex-M V2 Could you please try the following: - Open the J-Link Commander (JLinkExe) - Connect to the device - Send the command "erase" (without quotations). Does this wor…

  • Hi Thomas, Sorry for the delay in response. We are currently very busy. We only had a MB997B in house and everything worked fine on it: forum.segger.com/index.php/Att…9d96b023545f8ccf9d64ab473 We ordered a new board, which should have the latest revision, and will give it a try as soon as it arrives. Best regards, Fabian

  • Hi, Thank you for your inquiry. Does selecting a log file path work? It should then be created at the logfile path specified. Otherwise, you can activate it like this: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Does this answer your question? Best regards, Fabian

  • Hi, The version is now available. Could you please come back to us if this fixed the issue for you? Best regards, Fabian