Search Results
Search results 1-12 of 12.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Dear Community, I've downgraded the JLink driver version to V6.50b - the result is the same. Can somebody confirm if this procedure works for recent JLink on Ubuntu/Debian? Thanks in advance.
-
Dear community, I'm trying to restore the original FW on embOS/IP switch board. OS: Debian 10.3 / Windows 10 PCB: V2.0A I'm following instructions from ReadMe.txt (segger.com/downloads/eval/Segg…rd_CortexM_EmbeddedStudio) Segger-embOS-SW/Prebuild$ /opt/SEGGER/JLink_V670/JLinkExe -device MK66FN2M0XXX18 -speed 4000 -CommanderScript CommandFile.jlink SEGGER J-Link Commander V6.70 (Compiled Mar 27 2020 14:37:00) DLL version V6.70, compiled Mar 27 2020 14:36:47 J-Link Command File read successfully. …
-
[SOLVED] How to adjust reset sequence in J-Link (Low level JTAG scan chain configuration) (i.MX6Q)
PostHi Alex, I do have a working setup which is now using 100 us as delays when generating those signals. I was wondering if I can achieve the same results with J-Link PRO.
-
[SOLVED] How to adjust reset sequence in J-Link (Low level JTAG scan chain configuration) (i.MX6Q)
PostMy point was as follows: - Power cycle the board - Stop it in U-Boot prompt - Attach with GDB (target remote localhost:2331) - execute (gdb) mo reset Then I've checked: What is the output of the serial console ? What is the output of (gdb) i r pc ? In my case it was to late (when compared to other tool which I do use) as stated in the first message. That is what I had from the J-Link out of the box with default settings. Then I've pointed out that with some other tool I can set/clear TRST and !R…
-
[SOLVED] How to adjust reset sequence in J-Link (Low level JTAG scan chain configuration) (i.MX6Q)
PostHi, Please don't get me wrong, but I think that we are going off topic a bit here. The original question was about the possibility to emulate/generate with Segger setup the TRST and !RESET signals with micro seconds resolution.
-
Thanks for the hint. I was just curious - how one can load re-located U-Boot symbols (or shared library for example). In my use case - 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.
-
[SOLVED] How to adjust reset sequence in J-Link (Low level JTAG scan chain configuration) (i.MX6Q)
PostHi, Thank you for your response. My approach (I think that it is what your suggested above): Power cycle the board Go to the U-Boot prompt > Start GDB server: ./JLinkGDBServerExe -select USB -device MCIMX6Q7 -endian little -if JTAG -speed auto -noir -noLocalhostOnly arm-linux-gnueabihf-gdb (gdb) target remote localhost:2331 (gdb) hb *0x908000 Hardware assisted breakpoint 1 at 0x908000 (gdb) i b Num Type Disp Enb Address What 1 hw breakpoint keep y 0x00908000 (gdb) mo reset Resetting target (gdb)…
-
Dear Community, Please find the reproduction steps (i.MX6Q): Power cycle the board Stop at U-Boot prompt ./JLinkGDBServerExe -select IP=192.168.2.72 -device MCIMX6Q6 -endian little -if JTAG -speed auto -noir -noLocalhostOnly (gdb) target remote localhost:2331 (gdb) hb *0x17800000 (gdb) c Boot Linux GDB halts on the address: Breakpoint 1, 0x17800000 in ?? () At this point I do want to start the other instance of GDB Server (for Core #1): ./JLinkGDBServerExe -select IP=192.168.2.72 -device MCIMX6Q…
-
[SOLVED] How to adjust reset sequence in J-Link (Low level JTAG scan chain configuration) (i.MX6Q)
PostDear Community, I need to tune the default reset sequence (executed thereafter with 'mo reset'). The problem: ------------------- Stop SoC (i.MX6Q) just after powering it up (in the early SRAM - 0x908000 address in this case). This is necessary for debugging early bootloader code (U-Boot SPL to be precise). I've tried to pass adjusted SetResetTime (it provides only ms resolution) and SetResetType=0 to ./JLinkGDBServerExe. Unfortunately, the result is not acceptable - I still see SPL welcome prom…
-
Dear community, I would like to ask about using Ozone SW (ver. 2.70.3 - 64 bit Debian) with debugging U-Boot. U-Boot itself work with two sets of "locations". One matches the address set of u-boot elf binary just after starting it from SPL (or loading it via GDB - e.g. 0x17800000). However, after successful startup the U-Boot relocates itself to the area being near the top of available SDRAM. Hence my question - is it possible to relocate symbols in Ozone GUI for easy debugging? I mean to have s…