Search Results
Search results 101-120 of 245.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
This is weird .. I'm testing now, and, if I switch the board to SWD (using on-board SOP jumpers configuration from JTAG (which I prefer still) to SWD), then , based on test I did now, J-Link does not have that SVC 0 issue anymore .. Could Segger look at it please .. ? I obviously don't know how that relates, and why on-board XDS emulator has no such issue, but re-tried couple of times, it doesn't have same issue when in SWD. It feels quite sluggish though, when hitting breakpoint. ( I don't thin…
-
Hi Nino, That is what I have tried originally. It doesnt' seem to work with this unit - JLink EDU. I have the more expensive J-Trace, and I can see it is 'smart' enough to sense accurately when the board is powered (I observe it reacts with the led very quick every time i turn on/off the board). My J-Trace is too good for this board though ...
-
bump ... Some news would be good.
-
Quote from SEGGER - Nino: “Hello, Could you provide a J-Link log of a failing session? wiki.segger.com/Enable_J-Link_log_file ” Please see the JLinkLog , with app binary, attached. The log ends when it (debugging) stucks on svc 0
-
Is there a way to pre-set / force JLink to never power or try power the board? I don't know if this make sense though, tbh .. Basically, if my board is powered externally or from another USB source, I wouldn't want JLink to power it. What I see is, if I unplug power , say to reset whole system, JLink is supplying some power, and I have to unplug it to fully power down the board. But I'm not sure if it's expected behaviour - is it sensing no power and then supplying it .. ? I have tried to set po…
-
Hello Nino, Quote from SEGGER - Nino: “Hello, Nonetheless if you can provide us with a reproducer that works out-of-the-box on an eval board we could take a look. ” I should be able to. The board is the eval CC3220SF-LAUNCHPAD ( easy to get for you), and the code is all standard from TI's example base. Quote from SEGGER - Nino: “Does the issue appear when using Ozone instead? segger.com/products/development-tools/ozone-j-link-debugger/ ” Could you Please explain why Ozone , vs me already have re…
-
Quote from SEGGER - Nino: “So programming should work. If debugging works in Flash depends on the target specifics. ” Hello Nino, I saw from output of JLinkExe/GDBServer it's programming flash, at least from (very useful) output traces it says it's writing flash, and the addresses from linker script are the flash. What can be a little confusing is why the contents are lost, each time you reset the device. I think it's the specifics of the bootloader & the protective model, it restores the defaul…
-
The issue was also seems reported here , in 2018: forum.segger.com/index.php/Thr…rtFirstTask/?postID=20991 Abandoned, not sure there was solution ...
-
It is that SVC issue. Here is me trying to step in JLinkExe: J-Link>s 01004E98: 00 DF SVC #0 J-Link>s 01004E98: 00 DF SVC #0 J-Link>s 01004E98: 00 DF SVC #0 ............. Here is that call disassembly : C Source Code (11 lines)SVC is used by FreeRTOS, and it shouldn't cause J-Link to get stuck on this .. ?
-
On the CC3220SF launch board, I do a simple hello world uart sample, based on FreeRTOS. The code loads and starts, but, when FreeRTOS tries to start first task, the J-Link/GDBServer halts it seems in debug request on call to prvPortStartFirstTask. And it doesnt get out of it, code cannot resume. snippet of what SeggerGDBServer prints: Starting target CPU... ...Target halted (DBGRQ, PC = 0x01004EB2) --------------------------- snippet from GDB client: Program received signal SIGTRAP, Trace/breakp…
-
Quote from grantch: “v01d, According to the link here segger.com/products/debug-prob…pported-cpus-and-devices/ under the "List of Known Devices" it says CC3220SF * Cortex-M4 * Parallel CFI NOR flashProgram flash (Bank0) Program flash (Bank1) Hope this helps CG ” Hey grantch, Thank you. I hoped someone else already tried it and could advise on it (a bit lazy on my part , i know). So far tested running/debugging from RAM.
-
I was installing latest rpm - JLink_Linux_V648b_x86_64.rpm - which is jlink-6.482-1.x86_64 My previous one was version jlink-6.4611-1.x86_64 . On installing new version, package manager (dnf) said downgrade will be performed . Why, this should be version up. I think, your versioning scheme may be changed? ( 6.4611 seen as > 6.482.. ) Source Code (28 lines)
-
Quote from siermm: “Hi Nino, thank you for this answer. So i just copied: sudo cp ../ozone/2.62.7/Lib/libQtCore.so.4 /usr/lib/ sudo cp ../ozone/2.62.7/Lib/libQtGui.so.4 /usr/lib/ Now the libs are accessible, but i get a new error message: SystemView: symbol lookup error: SystemView: undefined symbol: _ZN12QApplication13setMainWidgetEP7QWidget Now, i have no idea how to solve this. Thank you. ” May be this can help (my old thread: ) forum.segger.com/index.php/Thr…-rpm-is-a-broken-install/
-
Still an issue. A guy from Linaro group, when I shared same logs as here, suggested in a chat that the server (J-Link's GDBServer) sends corrupt response. Could you check? (per logs included already)
-
It seems like I cannot reproduce this using gdb built from mainline / master as at date.
-
Got a problem with new'er GDB clients from GNU ARM toolchain dropping connection immediately after connecting to the Segger GDB Server. The last trace from GDB is 'cannot access memory .. ' which I thought, I would resolve by 'set mem inaccessible by default off' before the connect attempt, but this does not help. Working / without this behaviour GDB client : GNU gdb (GNU Tools for ARM Embedded Processors 6-2017-q2-update) 7.12.1.20170417-git With this behaviour / one not working for me : GNU gd…
-
Quote from SEGGER - Nino: “Hello, ... Keep in mind that all memory ready, breakpoints etc. .. We suggest getting in contact with the GDB Client support. .... Best regards, Nino ” Hi Nino, Please help me out : How many 'hardware' breakpoints are supported with JLink Plus for the target (iMX7) ? How many with JTrace Pro Cortex? Why do I get those Warnings : "WARNING: No more breakpoint resources left" ? Is this trace about un-available hardware breakpoints? All I had set through gdb was soft ones,…