Search Results
Search results 961-980 of 1,000. There are more results available, please enhance your search parameters.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi, Quote: “(I've smudged out all J-Link serial numbers) ” Why? There was a problem in the Configurator that under special circumstances messed up the IP settings stored in the config area of the J-Link. This problem has been fixed in V4.84b: segger.com/jlink-software.html But this should never ever inhibit a connection via USB because even if the USB settings are messed up, it will go back to the default settings for USB enumeration... Did you make sure that you only have 1 J-Link device connec…
-
J-Link embedded in a Energy Micro STK-3600 on OSX loses communications whenever new code is flashed
PostHi Douglas, We need a reproduction scenario which allows us to reproduce the problem here in house on an eval board. So far, we are not aware of *any* problems with the current release. - Alex
-
Hi, The LPC-Link-2 must not be used with J-Flash. J-Flash is a production programming software and using the LPC-Link-2 J-Link firmware for production programming is prohibited... For the LPC4337 currently only programming of the internal flash is supported. Programming of SPIFI flash is currently supported for LPC18xx and LPC43xx flashless devices only. This is going to be changed in a future version of the software but requires big internal changes of the J-Link software. - Alex
-
Hi Ronny, Yes, it is. For example J-Flash supports programming of SPIFI flash connected to an LPC4330: forum.segger.com/index.php/Att…e00b2241be19f49186071e601 PS: Please refrain from using such unspecific descriptions like "to an external flash". The flash type is *always* important (NAND, serial NOR, parallel NOR, serial NOR that is memory-mapped accessible, EEPROM, ...) - Alex
-
Hi, Quote: “I believe it supports SWD and I was going to give the J-Link EDU a try since I've read so many great review on this JTAG emulator probe that I had to get myself one.” Welcome to the side of light In case you see a regression in a new version, please let us know. Downdating is the wrong way! First, you need to differ between: Software version and Firmware version Of course you can always go back to a previous software version... new firmwares are kept compatible to old software versio…
-
Hi, I checked the source and it is impossible that this error message comes up in case a Cortex-M4 has been properly identified. You are using CoIDE + J-Link GDBServer + J-Link to connect to the device, correct? Can you please send us a logfile of the GDBServer when the session is started and this error appears? A GDBServer logfile can be created by checking the "Generate logfile" checkbox in J-Link GDBServer. The logfile is placed in the same directory where the executable of the GDBServer is p…
-
Hi Peter, For J-Flash: Will be corrected. Thanks for letting us know. Keil/IDE in general: More something for the IDE vendor to fix/change. But in general, for flash programming itself, you will not gain much from a higher communication speed. J-Link usually reaches the max. flash programming speed (limited by the flash speed itself) at 4-8 MHz. For debugging speed, higher communication speed makes sense of course. Best regards Alex
-
J-Link embedded in a Energy Micro STK-3600 on OSX loses communications whenever new code is flashed
PostHi Douglas, Should be fixed in V4.84a: segger.com/jlink-software.html Best regards Alex
-
Hi, I get your point but unfortunately, currently this is not possible. Anyhow these delays should not be really a problem regarding loss of data. a) J-Link implements a buffer on the firmware side for read/write VCOM data b) The J-Link OBs on the nRF51 kits make use of hardware flow control, so no data should be lost even in case the buffers on the J-Link side get full due to delayed flush requests from the PC. Best regards Alex
-
Hi, What Kinetis device (exact device name) do you use? In general programming of the data flash region is supported and much easier to achieve than you are trying to do it. Best regards Alex
-
Hi "pizza", Quote: “ So if I am correctly interpreting what you wrote, in order to get JLinkExe to continue to act as it did prior to v4.82, I will need to *rename* the file to have a .bin extension?” Correct. Prior versions, by accident, did not check the file extension. Best regards Alex
-
Hi, The reset pin toggles because J-Link is trying its best to get any chance to gain control over the device which also includes resetting it, if a regular connect does not work. No doubt that there *is* a difference between your board and the one from Glyn... Can you send/post your schematics? Feel free to send them to segger.com/support/technical-support/ (referring to this thread) if they are confidential. - Alex