Search Results

Hello "pizza", You were using the loadbin command incorrectly... As the name says, it was designed to work with *.bin files... It was *never* intended to work with other extensions, so this has been corrected. (Because there were a lot of users which passed hex files etc. to it, without knowing what they are doing) Pass a bin file to it (extension .bin) and it will work... *.img files are not really specified at all. They can contain binary data or some kind of structured data with headers etc. …

Thanks for the feedback. Does this mean everything is working now? - Alex

Hi, Quote: “This may need Segger's nRF51822 USB-dongle Linux driver source code. How can I get the same ? ” You won't. The J-Link software is not open-source (and this is good, since we also have to subsist on something...) Quote: “ If getting source is not possible, is there a way to access the device from the kernel space (from a kernel module) ?” Why do you see that you are needing this? So far, I do not see why you would. Could you please clarify? Best regards Alex

Hi Jared, Yes, you did. See VTarget reported by J-Link LITE. It says 2.3V J-Link LITE is specified for 3.3V targets only and the nRF Kits (which are delivered with J-Link LITE) are running at 3.3V. Anyhow, good to hear that you are up and running. - Alex

Hi Douglas, We possibly found the issue. Cannot guarantee it, but the behavior looks quite the same but under other circumstances. Note: It *only* shows up with the OB on the Energy Micro board (which is not directly maintained & supported by SEGGER). It does not show up with any "full" J-Link. We are planning to have a new version by the end of this week. Best regards Alex

Hi, Sorry, I had a look at the wrong chip, I was referring to the STR912FAW42... Anyhow, the core of my answer remains the same... STR912FAW47 Bank 0: 2048 KB Bank 1: 128 KB Bootbank 0 mode: Continuous memory from 0x0 - 0x21FFFF Bootbank 1 mode: Memory 0: 0x00000000 - 0x0001FFFF Memory 1: 0x00200000 - 0x003FFFFF (Starting at offset 2 MB!!!) So as I said: At 0x80000 (4 0's) there is *no* memory for J-Flash... J-Flash does not re-configure the STR912 again for bootbank 1 mode, so that the memory m…

Hi, It is just a guess since I do not know anything about your hardware, but this is what I assumes happens here: - You have manually wired the connection between J-Link & your target - You do not have connected pin 1 of J-Link to VCC of your target CPU Note: uLink-ME is only specified for 3.3V targets. J-Link is specified for 1.2 - 5V but for this, it needs to measure the target operating voltage to adapt the I/O voltage of the debug signals on the J-Link side accordingly. Measurement of the ta…

Hi, Quote: “ 2) I select device str912FAW47 Bootbank 1 in the J-link task bar (is there a way of making that sticky please as I seem to need to redo it for each time I run J-flash?)” What is your problem here? I do not understand the question... If you select the correct device in J-Flash at Options -> Project settings -> CPU -> Device you are fine and done. Quote: “5) read back entire chip (at this point the memory @ 0x80000 is shown as "--" in J-flash)” This is correct... Do you know what the …

Hi Volker, E-Mail address: segger.com/support/technical-support/ Please add a link to this thread to the e-mail. Strange... I do not see why the EDU should not work. Did you give J-Link Commander a quick try? It's a small command line utility that comes with the J-Link software package. Can you give it a quick try and post a screenshot of the output of the Commander? - Alex

Hi Sandeg, Sorry for the late reply. Basically this can be done via J-Link + the SDK since you can output any JTAG sequences using the SDK, so you can of course do things like that but there is no "out-of-the-box solution" available. Best regards Alex

Hi, Quote: “What can i try?” Providing some more information: Are you using an eval board or custom hardware? Which version of the Keil MDK / uVision are you using? Can you send us the project, so we can have a quick look at it to check if there is anything odd in the MDKJ-Link settings? - Alex

Release is still "under development". For now, please find a fixed beta version available for download, on our website: segger.com/jlink-software-beta-version.html - Alex

Release date has been moved a bit, so for now, please find a beta version (V4.83a) for download on our website, which fixes the problem: segger.com/jlink-software-beta-version.html - Alex

Hi, You are using the command correctly. It is related to this problem: No XMC4500 flash programming possible on Linux JLink 4.82 (works again after downgrade to 4.80e) We have already identified and fixed it. A new version comes later this week. Background info: There has been some internal re-structuring regarding the loadbin and unfortunately, there has been introduced a problem in the Linux & Mac version (does not show up under Windows) which causes the loadbin command in J-Link Commander to…

Hi, Status update: New version has been delayed for this week due to some other things we are currently working on and that should make it into this version. Will update this thread as soon as the new version is available. - Alex

Hi, Sorry, but we do not understand your question... What do you mean with?: Quote: “What i really meant is there some way to tell J-Link where in flash to set breakpoints?” How do you expect them to work? For the debugger there is *no* difference in how flash breakpoints work apart from hardware breakpoints. The debugger tells the DLL: "Set a breakpoint at address xxx" and that's it. The DLL will then do everything necessary, internally: Save the original instruction at address xxx Replace it b…

Hi, Problem is reproducible and will be fixed in the next version, planned for later today. - Alex

Hi, Looks like you have an application running on the target which has powered down the debug logic of the core and the power up request made by J-Link is rejected by the device. There is not much J-Link can do here if the power-up request (to be able to access the debug logic of the core again) is rejected by the device. We do not see this behavior on the AM3359 devices we have here. Best regards Alex

Hi, Alright, we will try to reproduce here. Quote: “Description of the command line options in UM08001 §3.11.1.1 is inconsistent (-CommandFile vs -CommanderScript) ” Thanks for pointing this out. There have been some naming changes in the past (old commands are still accepted), so maybe some parts of the documentation have not been updated properly. - Alex

Hi, Quote: “ Something odd on both versions has to do with scripting (I just was curious, so I tried):” There is nothing odd with scripting you are just using an incompatible file as J-Link Commander "command file". Basically there are two types of script files which are completely different and not compatible to each other: 1) J-Link script files (see UM08001 for more info) which are C-like-syntax scripts for customizing connect sequences, resets etc. for devices which need this. 2) J-Link comm…