Search Results

Search results 1-20 of 176.

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

  • Quote from SEGGER - Fabian: “.. We always get stuck in the boot loader at address 0x000029B8..... Best regards, Fabian Federschmidt ” Hi Fabian. I now got your case, and I have the steps for you to replicate the issue. Please start by examining the thread I created here - forum.segger.com/index.php/Thr…p-binary-for-TI-CC3220SF/ Change the how-to step 1 to use jtag (and check your board is set for 4-wire/jtag debug) Load & run the binary as per how-to. The app /binary should run normally under Se…

  • I saw that Segger support didn't know how to to load my provided binary/app built for TI CC3220SF MCU, so I thought I 'll write the steps for how to do it. Assume you have a CC3220SF with a blank-app image Development image (refer to the chip user manual) : i.e. you (or whoever) created the system image containing no app to be started by the application core; or lets say both the internal flash copy of and the external flash app image file (pre-programmed by manufacturing) got corrupted and boot…

  • Quote from SEGGER - Fabian: “ We always get stuck in the boot loader at address 0x000029B8. ” Can I ask you, how did you manage to get the bootloader/ROM code stuck at that address? I tried many things, changing jumper settings, etc.. I seems cannot get it purposefully stuck at that address, and the only time I had it myself, I cannot replicate it now. Could you share your exact board config - jumper settings / positions (not just SOP ones) , power supply options, etc. By observation, system beh…

  • Note: TI forum support confirmed the reported issue as per thread: thus they 've confirmed the issue independently. But I don't think they can do anything about it : as this is Segger specific.

  • Hello Fabian, Quote from SEGGER - Fabian: “We were using the TI CC3220 LaunchPad (wiki.segger.com/CC3220_LaunchPad). ” No, technically it is CC3220SF, not CC3220. I believe difference is external serial flash - please double check. Quote from SEGGER - Fabian: “Are you using the same board? Could you sent us an application, the issue you mentioned here is reproducible with on the TI CC3220 LaunchPad? ” I do not have non SF, only SF board . And I'm not even sure there is just CC3220. The applicati…

  • Quote from awneil: “Quote from simone: “does not connect ” note that Segger have a Wiki page on resolving connection issues: wiki.segger.com/J-Link_cannot_connect_to_the_CPU ” He did write that, connects initially & programs. Could you re-check his post?

  • I see that doing a 'r' / reset command in J-Link, causes a flash write traces, and , I do not understand why. Most importantly I guess to know if it's actually erasing/writing anything just because I wanted reset .. and why. I load/flash image just before reset, and don't want it to be erased. Source Code (12 lines)Sort of, did not expect reset to trigger re-flashing.

  • Quote from simone: “I have a problem with J-Link SWD isolator too, when using production programming but for STM32 devices. The first time I program a board it is programmed succesfully, then the second fails. So what I see is alternating exactly one succeed and one failure. v01d: is it the same issue? I got in touch with support, but they were not abe to replicate this issue ” Hello Simone, Issue is likely different : mine cannot connect at all, 0 / zero success on any attempt.

  • Quote from SEGGER - Alex: “... Not sure what board you use but is the board designed to also allow drawing current on the VTref pin? (pin 1) This is needed as the SWD isolator uses VTref to adjust its target buffers for the correct HIGH levels but also uses this pin to supply power to these buffers. Maybe that's the problem here: The SWD Isolator cannot draw current from the target board to power its own target side. ” Hey Alex, Could you help me out to check on it? The board is CC3220SF launcha…

  • Problem is I cannot connect to target when J-Link SWD Isolator is in between. I wanted to use the isolator to connect to the target TI CC32220SF board, in SWD mode. The SWD mode without isolator works. Why doesn't this work with the SWD isolator ... ? (Note: I do set "power on" to power the isolator itself first. in case you ask) Connection is: J-Link Edu <--> J-Link SWD Isolator <--> J-Link Cortex-M Adapter <--> Target The Segger products in this setup: segger.com/products/debug-probes/j-link/m…

  • Quote from SEGGER - Alex: “.... This will then allow multiple connections via IP (if all come from the same host PC) .... ” Nice to know Alex, thanks for update.

  • Quote from rdpoor: “I have a mildly complex JLink.exe script that gets launched from a .bat file via Source Code (1 line)... and I'd like to make it so others (including my future self) can understand what's going on in myscript.jlink. Is there a way to insert comments into a jlink script? ” Hey rdpoor, Have you checked the example pre-installed JLink connect scripts? From memory they have comments in them, at least the Segger copyright notice should be commented out.

  • Hey Fabian, Quote from SEGGER - Fabian: “For sanity reasons could you try the same Setup with your J-Trace Pro? ” If you see above - I did already, see post from Oct 31st 2019 on this thread. I will re-check. I will re-try with my J-Link EDU too, not mini, haven't had chance yet. Quote: “I can assure you, that we did not link the SN of any J-Link to any of our customers personal information at any openly accessible platform. ” Yea but your distributors , whom I buy most, may. In any event, I can…

  • Quote from lukma: “Hi, Just to test if I can "break" the execution of the code (in some random place) - see if symbols are correctly loaded (after relocation) and resume. ” Oh ok. When you halt the target CPU at a random place with the monitor (monitor halt..), on your client you update/add the symbols , as you were doing it. It's kinda Ok. Or you script it to autoload/update for you. without monitor halt

  • Quote from lukma: “ The original question was about the possibility to emulate/generate with Segger setup the TRST and !RESET signals with micro seconds resolution. ” It is true, apologies I still do not understand why you want /need it. For what you wrote : Quote: “ ... SoC state after going out of ROM bootloader. ” Quote: “Unfortunately, the result is not acceptable - I still see SPL welcome prompt "U-Boot SPL 2019.10-00343-" after "mo reset". This is too late for early debugging. ... ” Seems …

  • Quote from lukma: “Hi, Thank you for your response. My approach (I think that it is what your suggested above): ” Lukma, If you / your Co is willing / in -need, I can deliver a working debug setup on U-boot and Linux kernel, for your SoC/board, if we agree contractually (need some money for food , or to buy more J-Links ) I deliver in a virtual machine (prefer VBox), and done this before. Setup will be based on Segger J-Link + GDBServer; hardware wise any J-Link above EDU, I would say, and, I st…

  • Hey Lukma, Quote from lukma: “(gdb) target remote localhost:2331 (gdb) hb *0x908000 ........... ” Yes.. Quote from lukma: “However, I would like to know how early I can stop the i.MX6Q when I do generate the reset (with 'mo reset'). This may be helpful when debugging the SoC state after going out of ROM bootloader. ” You should set it up from the first U-boot instruction, i.e. after ROM code loaded it and starts to execute it. I don't think you want to debug the SoC ROM code. Also keeping in min…

  • Hi Nino, Quote: “..... The GDB Server plugin is not compatible to Ozone or ES as the GDB Server has to use another approach due to the limitations of the GDB Protocol. So you can only use the available plugins from us in third party IDEs if the IDE uses the same API which I doubt. For third party IDEs most likely other plugins must be created which is usually out of our reach. We recommend using SEGGER software tools when debugging for compatibility. .... ” If the tool in question already uses J…

  • Quote from lukma: “... I would like to do it without any breakpoints set (HW or SW). Just break the execution of the code (at some random place), load symbols with offset - inspect the code and just resume execution. ” This seems a little contradictory : no breakpoint, but break the execution .. resume execution..

  • See here: forum.segger.com/index.php/Thr…hout-uploading-to-target/