Search Results

Search results 1-20 of 217.

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

  • Hello Fabian, This excellently does what I want. Thank you! About piece of information: Please understand, I did not want to open a thread / start a new post on Segger forum asking about a TI CCS question. Asking about Segger's GUI / Segger config options made more sense (which in the end it is : JLink script file is not CCS, it's Segger specific init /config file) (Or , more polite way around , rather than asking straight how to setup my CCS ..) Thanks again.

  • Hi Fabian, No, not quite. Yes, it is over IP. But, I do not believe its GDB, it's whatever debugger TI's CCS is using. CCS invokes JLink through dll/ so library, and I cannot pass anything to JLink through CCS interface, which then results in Segger's GUI popping up when it cannot find a USB device connected, asking for ID or IP of the JLink (wow, this is first time I'm actually glad that that Segger's GUI window exists, else I prob wouldn't be able to use JLink over IP at all. I usually always …

  • There is a GUI which pops up on start-up / connect attempt, when JLink cannot open the probe, it's asking for probe id , or IP address , or serial etc.. When invoking JLinkExe you sort of can disable GUI, and you can pass on command line where you want to connect, which probe. But if JLink gets invoked through dll/ so, by an IDE, is it possible to pre-configure / save JLink params somewhere, like local init file? I need to insert an IP address of the probe, so I do not have to insert it every ti…

  • Thank you I will check this updated file. Im on Linux Fedora, and so using RPM. I used RPM for at least N years. (note: this is the test bed for corporate RH, so I really think it's a good distro to support) I do try to update Segger packages about say every 6 months or more often if something looks broken, directly downloading from your site. On this Linux image, i see from package log install JLink_Linux_V682 | 2020-07-25 11:18 | Upgrade . So that probably , should have your update mentioned. …

  • ANSWER : Segger needs to add this line to their 99-link.rules in the installation package: ATTR{idProduct}=="1020", ATTR{idVendor}=="1366", MODE="666"' This then solves it.

  • Bizarre issue : JLink soft doens't allow me to access J-Trace as normal user, but allows to access J-Link. Source Code (37 lines)So why ? . Means , rest of my Apps like IDE's cannot access J-Trace. Why would "DLL" be accessible for J-Link , but not J-Trace .. ? Presumably , it's same DLL / shared object file, so is there something in USB connect : do I need special udev rules, 99-link.rules ? Shouldn't this be already handled by the Segger's J-Link installer ?

  • Hi Fabian, It would be great to first receive any update on similar issue I've reported I think year ago, and, which I waited on, but you never got back to me. The issue is, as I'm aware, still open, and I haven't received any update from you on. (I was also exchanging messages directly with you, but you havent' replied). See here free rtos can't continue after svc on a ti mcu .. (you know, a bit frustrating there was no update from you on it ..) For that board/setup, I have fully described it, …

  • JLink TI 14-pin to ARM 20-pin adapter

    v01d - - General

    Post

    I see, well I could use jumpers for now, may be buy dedicated adapter later. Could you recommend supplier that does stock these, I tried local Mouser and they do have stock, and don't plan to unless someone orders, Which means I would wait > month or so .

  • JLink TI 14-pin to ARM 20-pin adapter

    v01d - - General

    Post

    Need this adapter for a TI target, segger.com/products/debug-prob…apters/14-pin-ti-adapter/ But I'm wondering why is it so expensive - EUR 49 before shipping & tax - and locally it's not stocked either. What is so special , what is on it , beyond routing the right line to right pin on target connector? Are there any other components mounted that I cannot see? So happens I already have this connector form Segger : segger.com/products/debug-prob…mil-10-pin-patch-adapter/ Can I just use this, and j…

  • Yea I can't pretty much like camel case either, but Segger been using those names for a long while. May be, if you provide a post-install script that Segger could include into their packages, which basically symlinks to their default file names, that would make others happy .

  • Currently, connected to same target / same code using J-Trace , over Ethernet, and I do not observe the same behavior.

  • Could you recommend USB isolator that will fully work with J-Trace PRO Cortex? I know one Segger makes is not compatible (I think its USB 3 issue). Would this be fully sufficient ? usd.saleae.com/products/usb-3-0-superspeed-isolator Do you have any other recommendation?

  • I'm debugging RTOS based code , on Cortex R4F. Every time there is an SVC call - and here are multiple handles based on SVC value - my Segger J-Link breaks / stops execution. I do not have any breakpoints in these handlers / places, and I also tried removing all of other breakpoints - this did not help. I further , disable all "Semihosting" (requires bkp in SVC_xxx), and I do not have CIO enabled. What else can I do ..? I do not understand why it stops by itself in places. ( A bit reminds me of …

  • When trying to install latest Segger tools including SystemView the OS package manager does not see this new SystemView as an upgrade of existing / installed SystemView already. This is most likely , because Segger's latest RPM is not correctly formed / not upgrading/updating existing install. dnf install JLink_Linux_V680d_x86_64.rpm Ozone_Linux_V320b_x86_64.rpm systemview-3.12.x86_64.rpm Installing: SystemView x86_64 3.120-1 @commandline 6.2 M Upgrading: jlink x86_64 6.804-1 @commandline 37 M o…

  • Quote from SEGGER - Fabian: “I will send you a link with a preliminary version for testing purposes via PM. ” I tried it, and the problem now was the Accept License terms dialog / message box. Firmware update window suppression worked.

  • Quote from SEGGER - Fabian: “The only thing that changed is that we added GUI support for Linux, ... b) We will add a "-nogui" command in our next release. ” But this sounds excellent. Thank you So as to set a reminder to upgrade : which release number / version will be next ? (Btw, Linux is what all embedded sw dev work must be on ^__^ )

  • Hey Erik Quote from SEGGER - Erik: “Basically there are two possibilities: ” This is great stuff, thank you. Yes I was thinking along the route of setting hardware address watchpoint at address X. One obvious non-nicety is too much knowledge at the connect/reset script stage (sits below all code & debugging). I understand your easiest solution, and I see how it can work. (Just that you would need to modify all your early startup code). I may, however, ask you to check something else I'm using, h…

  • Hello, Now I have sent you an archive containing the setup exactly as I use to create this problem / trace (there is nothing more to it beyond it, its complete). I described exactly how I start it in the README, and the logs are from it essentially ( I didn't repeat them, but they the same).

  • Hey Erik Quote from SEGGER - Erik: “....... If the core is hold in reset after triggering the reset, the ResetTarget() has to release the core and halt it. It does not make any sense to return from ResetTarget() if the core is not accessible through the debug interface. ............. Even if the DLL does not check the debug registers after resettarget, what should the DLL do? It still cannot access the core so a debug session or whatever will simply crash. ” Thanks for quick response on technica…