Search Results

Hi Kenny, Bricked J-Link: Has already been solved with SEGGER support. ADuCM320: We will check tomorrow. We are not aware of any problems with this device, regarding flash programming. - Alex

Hi Thorsten, Thanks for the feedback. So we can consider this as solved / closed. - Alex

Hi, Quote: “I checked the documentation but it has commandline option for starting gdb server in localhost only mode, not the otherwise.” Then you should read it again. forum.segger.com/index.php/Att…3c0fc29784573dc8cfb6e5720 - Alex

Hi, Sorry for the delay. Busy days... For RDDI (like for RDI) a higher end model is needed. This may be J-Link PLUS J-Link ULTRA+ J-Link PRO - Alex

Thanks for clarifying. Good to hear that it is working now. - Alex

Hi, You are using the loadbin command which is (as the name indicates) for binary files. The file you are loading is an ELF file. ELF is not bin. ELF file support is planned for a future version, but I cannot give you a schedule yet. For now, you need to convert your ELF file into a bin file for using this command or converting it into a hex/mot/ etc. file in order to use the "loadfile" command. Please note that J-Link always expects proper file extensions. - Alex

Info for all: We have been contacted by Rich via regular support in parallel. Current status: Quote: “Hi Rich, Thanks for your inquiry. In the J-Flash logfile I see that even initial connection to the device fails. I also see: "RESET (pin 15) high, but should be low. Please check target hardware." when J-Flash is performing a reset. With the software package J-Flash comes with, there is also a small command line utility called "J-Link Commander". This utility also works for Flasher ARM. Could yo…

Hi Ryan, This is not a J-Link / SAM-ICE related question but a Atmel Studio related one, since the breakpoint management (Code <-> Source Line assignment of breakpoints) in Atmel Studio is done by Atmel Studio. J-Link does not have any influence on this. So you should get in touch with the people from Atmel Studio regarding this. Quote: “Is this due to an optimization configuration” Yes, pretty likely, but as I wrote: The guys from Atmel Studio are the correct ones to address here. - Alex

Hi, Thanks for the feedback, so I will close this threads for now. - Alex

Hi, Quote: “Is this because it is newer (609300411) or because its a PLUS?” Because its newer (V9 hardware). Quote: “Is there way to update our old ones (158009579 and 58010952)? ” Yes, by making use of the trade-in program: segger.com/trade-in-program.html - Alex

Hi, Can you please post the serial number of your J-Link? My guess: The J-Link you are using is an old one for which no firmware update with such an improvement is available. Best regards Alex

Hi, Sorry for the delay. Busy days... V4.88 has been released which comes with support for the L0 series devices. Download-Link: segger.com/jlink-software.html - Alex

Hi, Sorry for the delay. Busy days... V4.88 has been released. It comes with the fix for J-Links with VCOM support, mentioned earlier. Download-Link: segger.com/jlink-software.html - Alex

Hi, Sorry for the delay. Busy days... V4.88 has been released. It comes with the fix for J-Links with VCOM support, mentioned earlier. Download-Link: segger.com/jlink-software.html - Alex

Hi, Alright, unfortunately, 2-wire ICSP is not usable for debugging and the MX795 does not support 2-wire JTAG debugging. What ICD3 does: Downloading a special handler into flash which communicates via a proprietary protocol, causing the target application to stop immediately in case no debugger is connected, making it impossible to perform post-mortem debugging of release versions. Best regards Alex

Hi, Quote: “ - Download speed is very low compare to ICD3” We are currently working on a new version of the DLL in which the download speed has been improved (see PIC32 info page which already shows the new values) J-Link is more than 2 times faster than the ICD3, on the PIC32MX... Just to be sure: You are debugging via the 14-pin header, correct? Since the RJ11 connector is for 2-wire JTAG (different pins) which is not supported by the PIC32MX795. See PIC32 info page for more information. Quote…

Hi Simon, Sure, feel free to do that. If any mistakes regarding the hardware version etc. happen, please to not hesitate to get in touch with our sales department. I am confident that we will find a solution then. Best regards Alex

Hi, Currently, the ELF format is not supported in J-Flash. You need to convert it into a mot/hex etc. file first. We are working on ELF file support and plan to have this by the end of this month. Best regards Alex

Hi, We have already fixed this internally but are working on some other things, before the new release with this fix is going to be public. Initially, we planned a new release for Friday last week, but some "interrupts" came in, so it will probably be end of this week. - Alex

Hi, Sorry for the confusion. Min hardware requirements: J-Link BASE / EDU V9 or later J-Link ULTRA+ / PRO V4 or later We will also add this to the PIC32 info page. - Alex