Search Results

Search results 1-11 of 11.

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

  • Waste of $700...

    henry10210 - - J-Link/Flasher related

    Post

    I do Nino; supporting a hobby platform like RPi will be a low priority for any company. It would have been nicer if Niklas had told me up front that SEGGER will not support Raspberry Pi even on J-Link Ultra+; could have saved $700...

  • Hello, I was looking for a better side-by-side (C-and-assembly) view of the code than what gdb give you, so I am trying out ozone (other people apparently got it to work as you can see here). But after loading up my u-boot ELF file, ozone does NOT show me the assembly (only the machine code) as you can see in the attached picture. I would guess this is because ozone doesn't know where my cross-tool chain is--even though I have an environment variable called CROSS_COMPILE. How can I tell Ozone to…

  • Hi Nino, I get exactly the same output when I use JLinkExe. Strangely, the Reset proc is not called at all. I didn't realize that initializing a Cortex A's debug would be so complicated. I am struggling to understand why some of your examples even use the internal DAP ADDR write followed by DAP DATA write (which makes sense at a low level) vs. memory mapped write. At this point it's hard to see which one I can get working first--OpenOCD + J-Link route, or JLinkExe + J-Link route. At least OpenOC…

  • Hi Nino/Niklas, I have written a JLinkScript for Raspberry Pi 2, but it doesn't quite work yet. Here is the latest output fro JLinkGDBServer using this custom device I created: ------Target related settings------ Target device: BCM2836_A7_0 ... Firmware: J-Link V9 compiled Sep 26 2017 17:01:02 Hardware: V9.30 S/N: 609302643 Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB Checking target voltage... Target voltage: 3.30 V Listening on TCP/IP port 2331 Connecting to target... *** J-Link V6.21a Inter…

  • Thanks for the clarification Nino, I now think that my confusion was caused by people using RPi as a debug probe or debug host--which is not what I want to do. I think the closes JLinkScript example for initializing a Cortex-A7 target(s) is the NXP_iMX7D_Connect_CortexA7_0.JLinkScript shipped with J-Link SW. But in it, I see SetupTarget() in addition to ResetTarget() and InitTarget(). The latter 2 are described briefly in the J-Link user manual section 5.11.1, but not SetupTarget(). Can you plea…

  • Thanks for the tip, Nino. Can you please help me with my confusion. Naklas and you both say you don't support the BCM2835,2836,2837 SoCs for the RPi. I thought I understood that, but then I found forum posts (just search for "raspberry") where people report success, and Niklas says it worked for him just last month. It seems that JLinkExe was used to connect to the target. Given that I am trying to do the same thing (connect to the target with JLinkExe or JLinkGDBServer) why would Niklas say it'…

  • The RPi2 I had ordered arrived, and I got a J-Link+ v9.3. Still doesn't work. I also attached the Saleae logic capture data. TDO and TDI are hopping, and you can apparently talk to the chip. But still no connection. Can you please suggest what I should try? Thank you. $ JLinkExe SEGGER J-Link Commander V6.21a (Compiled Sep 29 2017 16:47:39) DLL version V6.21a, compiled Sep 29 2017 16:47:34 Connecting to J-Link via USB...O.K. Firmware: J-Link V9 compiled Sep 26 2017 17:01:02 Hardware version: V9.…

  • I ordered J-Link Ultra+ v4 yesterday. Meanwhile, I'll try to connect my J-Link+ v9 to Raspberry Pi (original).

  • Have not found an information so far what would happen if I tried to specify Cortex-A7 to JLinkExe against Cortex-A53 chip (like the BCM2837 on RPi3) using JLink+ v9. Do I have to know the internals of J-Link to figure this out, or is there some ARM document that will answer this question? Thanks for reading.

  • Thank you Niklas, I should have read through the whole manual... How can I check if what the distributor is selling is Ultra+ v1 or v4?

  • Hello, I have been following a help page on sysprog s website to try JTAGging into my RPi3 (B+) for the last week. I am trying to find whether J-Link+ even supports cortex-a7 (a53 would be even better, but I'll settle for working). I documented my steps and the problem on my blog entry , but here's where I am stuck (recap). When using JLinkGDBServer (on Ubuntu 16.04 running in Parallels Desktop): just connection failure. When using JLinkExe, and choosing CORTEX-A7, JTAG, 4000 KHz: Source Code (2…