Search Results

Search results 1-20 of 32.

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

  • Hi Segger, I am using RTTClient to do firmware upgrades, and I noticed there is a big delay again on transmitting TCP packet on port 19021. This has been discussed before: [SOLVED] RTT slow not usable anymore I can confirm that: * JLinkExe V6.32a was FAST (~10ms delay on TCP transmit from port 19021) * JLinkExe V6.46c is SLOW (~300ms delay on TCP transmit from port 19021) * JLinkExe V6.44c fixed the issue again, and is FAST again (also documented in the thread mentioned above) * JLinkExe V6.46e:…

  • Hi Nino, Thanks for the reply! Absolutely, the power state of the MCU makes a big different if it's debuggable or not. I was just referring to the 1.9V since your said: "The target voltage is suspiciously low". Whereas this is our normal operating voltage. The CPU is in deep sleep, which means it's not debuggable. However, I put it to wake on the SWD pins, to the CPU is waking up on SWD activity. I understand your point about unlocking the MCU when it's detected to be in a locked state. However,…

  • Hi Nino, The target voltage is just fine. We are working @ 1v9. The MCU is spec'ed 1.7 - 3.6V. Also, no popups were to be seen, ever. I am using JLinkExe on Linux, and it has never given me a popup. (Probably no GUI support, since I also get no device selection GUI) So I suppose this means JLink just proceeds to mass erase the device without asking, because there is no GUI? Maybe a command-line YES/NO can be a good alternative? Certainly mass-erasing without asking is not a good solution. Also, …

  • Hi Segger, I have a situation where the BlueNRG2 goes to sleep. JLinkExe then tries to connect to this board, but only succeeds half-ways. It then reports that no flash memory words could be read, and so it decides to mass-erase my device. This is scary. I have not asked to erase my device, just to connect to it. Command used: JLinkExe -device BLUENRG2 -if swd -speed 1000 -AutoConnect 1 See the log: SEGGER J-Link Commander V6.32b (Compiled May 8 2018 18:28:28) DLL version V6.32b, compiled May 8 …

  • Yes, our board is working a 1v8. I will try and monitor the supply while flashing with the oscilloscope. BR, Maxime

  • Hi Nino, This is indeed on a custom board, using a BlueNRG-248. Here's the full output: % JLinkExe -device BLUENRG2 -if swd -speed 1000 -AutoConnect 1 SEGGER J-Link Commander V6.32a (Compiled Apr 30 2018 15:46:56) DLL version V6.32a, compiled Apr 30 2018 15:46:51 Connecting to J-Link via USB...O.K. Firmware: J-Link V10 compiled Apr 20 2018 16:47:09 Hardware version: V10.10 S/N: 50104725 License(s): GDB VTref=1.896V Device "BLUENRG2" selected. Connecting to target via SWD Found SW-DP with ID 0x0B…

  • Hi Segger, When using the BlueNRG2 with certain applications, the JLinkExe seems unable to reliably reflash the device. What I get is this: Cortex-M0 identified. Downloading file [build/blescan.hex]... ****** Error: Verification of RAMCode failed @ address 0x200000C0. Write: 0x599D5991 D10442A9 Read: 0x01E80048 D10442A9 Failed to prepare for programming. Failed to download RAMCode! Unspecified error -1 After many tries, it eventually succeeds (sometimes after 2 or 3 times, sometimes after > 10 t…

  • I noticed in JLink command (or wherever under Windows you get a GUI prompt to select the CPU/MCU) the BlueNRG-2 is indicated as having 12 kB of RAM, whereas it actually has 24 kB of RAM. No idea if this affects any of the uses of the BlueNRG 2, but I thought I'd report it.

  • Ok, definitely didn't see that one coming. Thanks for the update.

  • When using JLinkExe or JLinkGDBServer, it opens a telnet server on port 19021 for RTT channel 0. However, is there a way to have it listen to a different RTT channel (at the same time) on a different port? In my application I want: RTT channel 0: serial debug console RTT channel 1: binary interface for interacting with the device How can this be done? P.S.: If not possible using the default JLink toolset, I would be happy to code something on top of the JLink SDK myself, but I cannot find any do…

  • It says here segger.com/products/debug-prob…gy/j-link-sdk/#tab-3357-7 that I should be able to build my own applications on using the JLink SDK. There should be example applications for Linux, too. However, I am not able to find these... E.g. where are the "Sample Projects and Test Applications" ? Ultimately, I just want to be able to read an arbitrary RTT channel...

  • The reason that works is because the ARM core's map the flash origin to 0x0 (because interrupt vector table is always at 0x0 when booting a cortex-m) I'll look for a .bin...

  • Flashing seems to work fine. However, I cannot reset to the "Reset_Handler" or put a breakpoint there, or on main. JLink GDB will just run past it. Only way to start from the beginning for me is set the PC to the reset handler manually: $> set $pc = *0x4 And step from there. "mon reset" or any variants don't work using JLinks's GDB server. However, using openocd, "mon reset halt" works fine, and puts me in the Reset_Handler()! So I am pretty sure this is a JLink issue.

  • Ok great, let me check that tomorrow!

  • Hi, I am working on a BlueNRG2 devboard (STEVAL-IDB008V1), which is now available from ST and distributors. Is there support planned for this device? I am currently using the BlueNRG1 device config, but I am having some issues: * Device cannot always be halted (it seems worse since V6.16c "DLL: ST BlueNRG1: Added AfterReset() functionality which makes sure that the bootloader is executed after reset.", but I did not test before/after many times to be sure about this) * Flashing does not always w…

  • Hey Nino, I have tried editting the .user file: After me setting it to my liking, it was: OpenWindow="Functions", DockArea=LEFT, x=0, y=0, w=470, h=326, FilterBarShown=1 OpenWindow="Call Stack", DockArea=LEFT, x=0, y=1, w=470, h=475, FilterBarShown After re-opening Ozone, the window was smaller. When quitting the application, the file was modified to: OpenWindow="Functions", DockArea=LEFT, x=0, y=0, w=214, h=326, FilterBarShown=1 OpenWindow="Call Stack", DockArea=LEFT, x=0, y=1, w=214, h=475, Fi…

  • Hi Nino, I created a new project from scratch, to be sure. I can confirm the windows I selected are still shown after re-opening, however, their size is still wrong after re-opening...

  • Thanks for the clarification! I am looking forward to possible future improvements on the reset behavior for BlueNRG1/2!

  • Hi, Thanks for the explanation. It works in JLinkExe (e.g. for flashing a new image) when holding the reset button, indeed. So, I should make sure my application does not go to sleep too soon, such that I can halt and debug in time, after resetting or powering on the device?

  • Ok, thanks. I might stick to GDB in that case, however.I'll try Embedded Studio for sure! BR, Maxime