Search Results

Hi, The "monitor flash device = ..." command is used to select a device. This allows the DLL to get information about the flash (size, page size, algorithm etc...) which are required to program the internal flash. In general, we recommend to use the command line option "device = <DeviceName>" instead of using the "monitor flash device = ..." command via GDB init file. The reason for this is simple: For some devices J-Link needs to perform special handling on connect. This has to be done BEFORE t…

Hi, The issue has been already fixed but it is not official yet. We plan a Linux release version of the J-Link software which fixes this problem today or tomorrow. Best regards Erik

Hi, Thank you for pointing this out. You are right it is a mistake. We will correct it in further versions of the manual. Best regards Erik

Hello, Quote: “1) Question - What is the purpose of this driver? What hardware or software requires this driver to be installed? Why should I install it or NOT install it???” Some J-Link OBs (J-Link on-board) come with CDC functionality. Until now the users of those OB's had to download the CDC driver from our website manually. We decided to add this CDC driver to our default software package installer as optional driver. Best regards Erik

Hi, You have to click the download link as shown in the screenshot below, in order to be forwarded to the page Alex referred to on the last post. forum.segger.com/index.php/Att…0136d256bdfba771f2a1c133d It does not matter, whether you click on this link on the beta or release download page. The Link you will be forwarded to, is still the same. Best regards Erik

Hi, It's me again with another question. Do you use Windows Vista x64 or x86? Maybe the windows installer package is corrupted in general? Can you confirm this? Best regards Erik

Hi Vince, We were able to reproduce the problem here with an old version of the "JL2CM3.dll" (2.73.0.0). After replacing the old JL2CM3.dll with the new one from the web (2.74.0.0) the problem is solved and everything works just fine. Could you please verify that you are using the latest fixed version of the JL2CM3.dll (2.74.0.0)? Best regards Erik

Hi, We are not aware of such a problem. Nevertheless, we will take a look at this short term and come back to you. Best regards Erik

Hi, We are not able to reproduce the problem here. Would it be able to strip down the project to a simpler one, so we can easily exclude application errors? Moreover, according to your last post, this problem is not reliably reproducible, even on your side: Quote: “I'm still not sure but you can try to reproduce the issue with these steps (you may need a lot of patience to catch it): ” Please understand that there is not much we can do in this situation because without being able to reproduce a …

Hi, Could you please give us some information about your setup? - Which device (manufacturer + device name) do you use? - What SW version do you use? Please note that the Flasher firmware that comes with SW V4.42 or later must be used in order to guarantee proper function of the start application command in stand alone mode. Please also note that the reset pin (nRESET) of the CPU also needs to be connected to the JTAG/SWD connector so the Flasher can toggle this pin. Best regards, Erik

Hi, We are not able to reproduce this here. Find our setup listed below: - HW: J-Link V8.00 - SW: V4.46d - Device: MC13224V (ARM7TDMI) We performed a quick test with J-Link commander and everything works fine: forum.segger.com/index.php/Att…0136d256bdfba771f2a1c133d Do you have a second hardware (e.g. Evalboard) with an equal device on it? If yes: Does this one work correctly with J-Link? If yes, could you please check for hardware differences between both hardware units? Best regards, Erik

Hi, There are no known problems with this device. Are you working with custom hardware or an evalboard? In case of custom hardware, could you please try out if the problem is reproducible on an evalboard, too? Best regards, Erik

Hi, Please download the current version of the J-Link software and documentation package (4.46a). It supports the STM32F207. Download-Link: segger.com/jlink-software.html Best regards, Erik

Hi,Quote: “Is there a way to limit GDB server to a maximum of 1 connection to make me aware of the problem? ” No, not yet. We will discuss internally if this will be implemented. We will get back to you as soon as we have any results. Best regards, Erik

Hi Jitesh, We have tried to reproduce this here with the following setup: - J-Link GDB Server - GNU GDB 7.3.1 - J-Link EDU - i.MX535 QuickStart Board with a PCIMX535DVV1B on it (Cortex-A8) We do not see any problem here, see attached pictures. Best regards Erik

Hi Rafael, Sorry for the late reply. Could you please start J-Link Commander (JLink.exe) and try to establish a connection to the target via J-Link? Does it works? Does you get any error? Furthermore we need some additional information: - What firmware do you use? - What hardware version of J-Link do you use? Best regards, Erik

Hi, I am wondering that you have to enable flash download by setting monitor flash download = 1 because selecting device should be enough since you use the latest version 4.40. We will have a look into this. Best regards Erik