Re: [PATCH]: 753c706011 Drop parallel port adapters

On 26.08.24 17:31, Marc Schink wrote: Thanks for the hardware recommendations! I have a working parallel port setup and I have a few questions ;) - Why is the "wiggler" cable selected in "parport.cfg"? I would expect basic configuration in "parport.cfg" and a "wiggler.cfg", as there is a "parp

Re: [PATCH]: 753c706011 Drop parallel port adapters

On 17.08.24 10:47, Marc Schink wrote: I would imagine many embedded developers have a PCI or PCIe serial+parallel card laying around. You never know when it might be useful. I personally have like 3. Can you provide me the names of your parallel port interface cards? What mode (i.e SPP, ECP,

Re: [PATCH]: 753c706011 Drop parallel port adapters

On 20.06.24 00:40, Marc Schink wrote: To be host I'm suprised that there are still parallel port users out there. Although the main reason is probably more nostalgia than anything else ;) Partly. Although I have switched mostly to USB, I also the parallel port adapter from time to time - the p

Re: Olimex ARM-USB-OCD-H Driver Issue

On 14.07.23 15:55, Abe Lapped wrote: Good morning, Thank you for this. I just checked the pin configuration and retried on another board. The board is definitely powered on (the status lights come on) and the cable orientation is correct, but I'm still getting the same error... could it be so

Re: semihosting unexpected breakpoint not acknowledged

On 13.07.23 20:30, Liviu Ionescu wrote: On 13 Jul 2023, at 19:12, Liviu Ionescu wrote: ... change OpenOCD to resume it when running with semihosting enabled but standalone (i.e. not in a debug session). Question: what do you think should be a correct behaviour for OpenOCD when an explicit

Re: Add zlib dependency to OpenOCD?

(Sorry, my mailserver rejected the reply, so I have to pull this from the archive and respond with broken references) On 24.06.23, Antonio Borneo wrote: >> What is the benefit of including zlib and code to manage decompression >> versus just loading the data from a file? > >Valid question! >But

Re: Add zlib dependency to OpenOCD?

On 23.06.23 14:12, Antonio Borneo wrote: Hi, I would like to have your feedback on this topic. Today a binary package of OpenOCD should include: - the binary openocd[.exe] - the TCL scripts from tcl folder - the file contrib/60-openocd.rules (for Linux only) - documentation - license files To

Re: [PATCH]: d5e2eb8057 jtag/drivers/ftdi: add support for using FTDI D2XX driver on Windows

On 10.04.23 10:52, ger...@openocd.org wrote: commit d5e2eb80571ae23b0de68fd40a5f79c1c9632011 Author: Weijie Gao Date: Mon Apr 10 15:13:01 2023 +0800 jtag/drivers/ftdi: add support for using FTDI D2XX driver on Windows This patch adds FTDI D2XX support on Windows platform.

Re: TI CC Debugger with OpenOCD?

On 20.12.22 05:42, Stuart Longland VK4MSL wrote: Hi all, So, on Friday I had a whoopsie moment with the Olimex XDS100v3 clone JTAG probe I was using -- and managed to blow it up (let's say, the FPGA it uses is not 24V-tolerant on its GPIO pins), and needed to quickly replace it with something.

Re: Time for OpenOCD v0.12.0-rc1?

On 03.11.21 18:32, Antonio Borneo wrote: > Which patches already in gerrit would be valuable to review and/or > merge before the code freeze? I would like to get the GD32 patches either merged, or a decision to abandon that course: https://review.openocd.org/c/openocd/+/6543 cu Michael

Re: Porting the P&E Multilink Universal adapter

On 11.10.21 11:49, David Brown wrote: > The licencing for OpenOCD, and how strictly it is applied, is entirely > up to the people who write the software.  So your two cents are worth > a great deal more than my two cents here. > > However, you should be aware that while this is clearly not a mere >

Re: Porting the P&E Multilink Universal adapter

On 06.10.21 12:15, cw...@thedigitaledge.co.uk wrote: > All, > > I'm currently trying to port P&E Multilink Universal[1,2]. This is > currently supported by pyocd-pemicro[3] using external dll[4]. What license applies to these DLLs? https://github.com/NXPmicro/pypemicro specifies "bsd 3-clause", do

Re: [openocd:tickets] Re: #313 Website Compromised

On Tue, Aug 03, 2021 at 06:53:30AM -, Paul Fertser wrote: > On Tue, Aug 03, 2021 at 12:40:00AM -, sbru...@users.sourceforge.net wrote: > > just opened ticket #313, looks like someone managed to compromise the > > openocd.org website > > Thank you for reporting. I wonder if it's SF.net comp

Re: [OpenOCD-devel] GigaDevice GD32E230 support

On 10.03.21 23:03, Antonio Borneo wrote: > Could you post the whole dump of the GD32E230's ROM table? > You can use CMSIS-DAP with openocd command 'dap info' Sure: > dap info AP ID register 0x04770025     Type is MEM-AP AHB5 MEM-AP BASE 0xe00ff003     Valid ROM table present         Component bas

Re: [OpenOCD-devel] GigaDevice GD32E230 support

On 09.03.21 14:00, Andreas Bolsch wrote: > On 2021-03-09 12:34, Michael Schwingen wrote: >> Is there a documented way to get a *manufacturer* ID in some common >> register that can be accessed without prior knowledge about the part? If >> not, I would prefer to shift

Re: [OpenOCD-devel] GigaDevice GD32E230 support

On 09.03.21 15:14, Uwe Bonnes wrote: > Andreas Bolsch writes: >> On 2021-03-09 12:34, Michael Schwingen wrote: >>> Is there a documented way to get a *manufacturer* ID in some common >>> register that can be accessed without prior knowledge about the part? >>>

Re: [OpenOCD-devel] GigaDevice GD32E230 support

On 08.03.21 20:46, Tommy Murphy wrote: > Is this of relevance to your query? > > https://www.mail-archive.com/openocd-devel@lists.sourceforge.net/msg12475.html > Thanks, seems I missed that. Patch #2 looks quite simila

[OpenOCD-devel] GigaDevice GD32E230 support

(re-send from correct mail address) Hi, I am currently starting to work on a project that uses a GD32E230 CPU (due to ST's inability to ship parts in the required volume for the next year or so :-(). The older GD32 parts were basically 1:1 ST-compatible clones. However, the GD32E230 deviates fro

Re: [OpenOCD-devel] Offer for website

On 24.10.20 15:28, Paul Fertser wrote: > My colleague Johan designed a simple, elegant javascript-css skeleton >> that we based our website on: >> [1]https://embeetle.com > I'm attaching a screenshot and that fully expresses my personal > opinion about this idea. Full ACK from me - it looks the sa

Re: [OpenOCD-devel] [openocd:tickets] #242 STM32L0x too high SWD clock

On 04.07.19 18:30, Patrik Bachan via OpenOCD-devel wrote: > > > *[tickets:#242] > STM32L0x too high SWD clock* > > Hi, > when calling |reset init| on STM32L0x target, function >

Re: [OpenOCD-devel] [PATCH]: 8d73f14 target/cortex_a: fix cache coherency with AHB read/write

On Wed, 01 Aug 2018 22:25:18 +0200 Matthias Welwarsky wrote: > Hi, > > I'm very much wondering if this feature is worth maintaining. Is it > so useful that it's worth the considerable additional complexity for > keeping the caches coherent? Flushing the caches is a very invasive > action by a de

Re: [OpenOCD-devel] [External] Re: Fwd: Image Dump Query

On 11.07.2018 10:54, N K, Athira wrote: Hello Tommy, Thank you for the quick response. Actually I could get an example command *dump_image empty.bin 0x8D000 185* But I get a response *Ignoring read of non readable area - Request address: 0x8D000, Request size 184. Bytes successfully read:

Re: [OpenOCD-devel] openocd newbie flashing questions

On Wed, 28 Mar 2018 22:38:20 -0500 John Griessen wrote: > On 03/28/2018 08:16 PM, John Griessen wrote: > > What is the meaning of Vref in the SWD config > > (interface/ftdi/swd-resistor-hack.cfg) > > > > > > " Vref of the adapter should be supplied with a voltage equal > > to the target's (pref

Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

On 24.02.2018 15:06, jaymayn...@gmail.com wrote: > The Olimex ARM-JTAG-SWD has a 27 ohm resistor in series with the SRST > line. I’m using about a 3-inch ribbon cable between it and the board; > the SWD adapter is plugged directly into the JTAG-TINY, as they recommend. That sounds good. Anyway, TR

Re: [OpenOCD-devel] Atmel ATSAME70 examination incomplete at startup

On Sat, 24 Feb 2018 00:52:44 +0100 Tomas Vanek via OpenOCD-devel wrote: > On 24.02.2018 0:04, Jay Maynard wrote: > More important is a small series resistor (33 ohm) on SWD - ringing > prevention. Again not necessary if the cable to adapter is short. However, "short" may mean "really short" - I

Re: [OpenOCD-devel] Telnet interface is not protected against cross protocol scripting

On 15.01.2018 03:26, Christopher Head wrote: > On January 14, 2018 12:37:53 PM PST, Michael Schwingen > wrote: >> How about a safe mode that disallows "dangerous" commands (eg. those >> that call external programs)? This would be a bit like "-dSAFER" on &

Re: [OpenOCD-devel] Telnet interface is not protected against cross protocol scripting

On 14.01.2018 20:38, Tomas Vanek via OpenOCD-devel wrote: > On 14.01.2018 20:06, Tomas Vanek via OpenOCD-devel wrote: >> On 14.01.2018 18:01, Christopher Head wrote: >>> none of the above attacks would work if you had to, say, type a >>> password before OpenOCD would accept your Telnet (or GDB, or

Re: [OpenOCD-devel] Telnet interface is not protected against cross protocol scripting

On 14.01.2018 20:06, Tomas Vanek via OpenOCD-devel wrote: > On 14.01.2018 18:01, Christopher Head wrote: >> none of the above attacks would work if you had to, say, type a >> password before OpenOCD would accept your Telnet (or GDB, or TCL, or >> …) session. > If OpenOCD would require a password it

Re: [OpenOCD-devel] Follow-up: DAP handling for Cortex-A

On Mon, 23 Nov 2015 07:38:15 +0100 Albert ARIBAUD wrote: > > just after i sent mail yesterday, i got similar idea: > > > > return code should be uint32_t, and like idcode or midr, pidr... > > registers, assembled by following: [31:24] - target return code > > [23:16] - ap ret. code > > [15:8] -

Re: [OpenOCD-devel] RoadMap Part 2

On 04.05.2015 16:19, De Cesaris, Ivan wrote: > Hi All, > jumping on the topic of "the future of OpenOCD", one thing I'd like the core > group to consider is the license. > > Maybe this is not obvious to everyone but the code, being GPL, precludes some > usages. > I'm not a lawyer but I can't rele

Re: [OpenOCD-devel] problem connecting to LPC812 with FT2232 (busblaster/ktlink) - solved!

On 29.03.2015 22:01, Paul Fertser wrote: > Thank you for this report, I hope the future users will be grateful > for that! For the record, what is the BB version you have, is it v3 or > v4? It's V2.5. Looking at the different schematics, it seems V2.6 (and newer) have series resistors on board. c

Re: [OpenOCD-devel] problem connecting to LPC812 with FT2232 (busblaster/ktlink) - solved!

On 27.03.2015 05:02, Tomas Vanek wrote: > Do not be so focused to a reset signal on target connecting. > Reset is not pulsed just because OpenOCD init command fails before > script reads a reset command. > Origin of the problem is bad read from DP. Recheck cabling and > compatibility of cfg and bus

Re: [OpenOCD-devel] problem connecting to LPC812 with FT2232 (busblaster/ktlink)

On 26.03.2015 08:21, Tomas Vanek wrote: > Michael, > > If srst wiring of your LPC812 board is correct, there might be another > reason that srst > is not pulsed: OpenOCD checks if target was examined and if not reset > is not issued > (this is IMHO wrong) > Please try http://openocd.zylin.com/2606

Re: [OpenOCD-devel] problem connecting to LPC812 with FT2232 (busblaster/ktlink)

On 26.03.2015 08:17, frank wrote: > Besides the suggestion to check correct wiring of reset, the reset pin > can also be configured for other purposes with the switchmatrix. > If it is no longer is a reset function, it will not work anyways. It is configured as reset - when I pull the pin low, the

Re: [OpenOCD-devel] problem connecting to LPC812 with FT2232 (busblaster/ktlink)

On 26.03.2015 00:07, Andreas Fritiofson wrote: > > > On Wed, Mar 25, 2015 at 11:26 PM, Michael Schwingen > mailto:mich...@schwingen.org>> wrote: > > The results are: > - Busblaster/KTLink works fine with a STM32F103 target, both with > "reset_

Re: [OpenOCD-devel] problem connecting to LPC812 with FT2232 (busblaster/ktlink)

On 22.03.2015 23:36, Michael Schwingen wrote: > (re-sending from correct account) > > Hi, > > I started working with an LPC812. Using a ST-Link V2 as SWD interface, > this seems to work, but I can't get reset working - it seems the reset > output is always active, so I

Re: [OpenOCD-devel] problem connecting to LPC812 with FT2232 (busblaster/ktlink)

On Mon, Mar 23, 2015 at 11:05:57AM +0300, Paul Fertser wrote: > On Sun, Mar 22, 2015 at 11:36:53PM +0100, Michael Schwingen wrote: > > I started working with an LPC812. Using a ST-Link V2 as SWD interface, > > this seems to work, but I can't get reset working - it seems the

[OpenOCD-devel] problem connecting to LPC812 with FT2232 (busblaster/ktlink)

(re-sending from correct account) Hi, I started working with an LPC812. Using a ST-Link V2 as SWD interface, this seems to work, but I can't get reset working - it seems the reset output is always active, so I decided to pull out my bus blaster. I flashed the KT-Link CPLD configuration into the

Re: [OpenOCD-devel] Windows binaries from freddiechopin.info falsely flagged as infected by some virus scanners

On 05.02.2015 21:59, Freddie Chopin wrote: > On 02/05/2015 08:49 PM, Michael Schwingen wrote: >> For this to be true, the checksums would have to come from a different >> source. If someone can modify the binary on your webserver, he could >> also modify the md5sum files.

Re: [OpenOCD-devel] Windows binaries from freddiechopin.info falsely flagged as infected by some virus scanners

On 05.02.2015 10:00, Freddie Chopin wrote: > If the md5 checksum of the package matches the info from the download > section, then the packages were NOT tampered with. For this to be true, the checksums would have to come from a different source. If someone can modify the binary on your webserver

Re: [OpenOCD-devel] [PATCH]: 410b19b checkpatch.pl: check for the FSF mailing address

On 10.10.2014 06:40, ger...@openocd.zylin.com wrote: > + if ($rawline =~ /\bwrite to the Free/i || > + $rawline =~ /\b59\s+Temple\s+Pl/i || > + $rawline =~ /\b51\s+Franklin\s+St/i) { > + my $herevet = "$here\n" . cat_vet($rawline) . "\

Re: [OpenOCD-devel] Micrel openocd flash programming issue

On 16.07.2014 19:02, Sujith K R wrote: > > I am trying to program Micrel KSZ9692 processor based board. I am > getting error > > "timed out while waiting for target halted > target not halted > error writing to flash at address" > > I used the command > > "flash write_image u-boot.bin 0x1c00"

Re: [OpenOCD-devel] Fast polling function

On 04.06.2014 16:13, Franck Jullien wrote: > 2014-06-04 15:08 GMT+02:00 Franck Jullien : >> Hi, >> >> I'm implementing support for an UART over JTAG module present in the >> OpenRISC debug interface. It's a device which looks like an UART on >> the SoC Wishbone bus but which transfers data via JTAG

Re: [OpenOCD-devel] [PATCH]: fd89352 tcl/target/fm3.cfg: use a CHIPNAME known by the flash driver

On Wed, Jun 04, 2014 at 07:58:44AM +, ger...@openocd.zylin.com wrote: > This is an automated email from Gerrit. > > Paul Fertser (fercer...@gmail.com) just uploaded a new patch set to Gerrit, > which you can find at http://openocd.zylin.com/2160 > > -- gerrit > > commit fd89352b6bff479854f2

[OpenOCD-devel] Problem compiling openocd master

Hi, when trying to compile master, I get compile errors in src/jtag/drivers/usb_blaster/usb_blaster.c (sorry, no logs saved - working on a different problem right now) - which is a bit strange because I disabled that adapter during configure: ./configure --prefix=/opt/openocd-test --enable-parpor

Re: [OpenOCD-devel] Cortex-M3 - Issue: BKPT_TYPE_BY_ADDRESS()

On 03.05.2014 17:42, Paul Fertser wrote: > On Sat, May 03, 2014 at 07:03:18AM -0700, Duane Ellis wrote: >> I do - need to attach to a dead/crashed system without reset, aka: “a >> soft attach” - no reset. Because you need to figure out why things >> have crashed, various bus clocks may be disabled

Re: [OpenOCD-devel] OpenOCD + RaspberryPi

On 02.05.2014 11:25, st...@nixia.no wrote: >> 3) The BCM2835 SPI controller appears to be flexible enough to use as >> a JTAG master. The current SPI driver couldn’t accommodate JTAG. >> If I go about writing a new driver on the Pi, how should the >> interface >> look to the application (OOCD spe

Re: [OpenOCD-devel] Build of Openocd 0.8.0-rc1 in Cygwin env

On Wed, Apr 16, 2014 at 11:54:16AM +0400, Paul Fertser wrote: > > Just wondering what is the official stand from the OpenOCD project > > with regard to MinGW.org toolchain support. > > My personal opinion: screw environments that are not C99-conforming. I fully agree. Now if MinGW falls in that

Re: [OpenOCD-devel] IPv6 support considerations

On 01.02.2014 08:00, Paul Fertser wrote: > On Fri, Jan 31, 2014 at 10:50:05PM +0100, Michael Schwingen wrote: >> I don't think this would be a good idea. Even with IPv6 gaining >> popularity, I see IPv4 in LAN installations for a long time. > It's really hard to fin

Re: [OpenOCD-devel] IPv6 support considerations

On 31.01.2014 18:30, Paul Fertser wrote: > Hi, > > Currently OpenOCD listens for telnet, GDB and RPC only on IPv4. Of > course, that's uncool to say the least. > > The easiest way would be to use AF_INET6 and that would allow both > IPv6 and IPv4 connections transparently on all common systems exce

Re: [OpenOCD-devel] Gerrit/OpenID login?

On Mon, Jan 27, 2014 at 11:50:42PM +0100, Andreas Fritiofson wrote: > Instead of logging in with another OpenID, essentially creating a new user, > log in with your "real" (MyOpenID) account. Click your name in top right > corner, settings, identity, link another identity. You should be able to > a

[OpenOCD-devel] Gerrit/OpenID login?

Hi, I am a bit frustrated with the gerrit login procedure. I created an account with MyOpenID back when gerrit was introduced. However, that service is due to be turned of in february, so I looked for alternatives. I tried creating a yahoo account, but on their site, not even logging in with fir

Re: [OpenOCD-devel] Adding adapter commands?

On 10/30/2013 11:48 PM, Alain Mouette wrote: Em 30-10-2013 19:04, Andreas Fritiofson escreveu: So I'm excited the code is getting cleaned up. However, I've got a bit of a problem. I have a unique JTAG dongle that allows me to select the target voltage. IIRC Turtelizer dos that: http://www.e

Re: [OpenOCD-devel] Support for low-cost development boards as JTAG adapters

On 10/20/2013 11:18 PM, Paul Sokolovsky wrote: > It is the same with a serial port: no such implementation exists now. > The detour may be a bit shorter, but not by much. > Well, I have that covered, I really didn't want to start > completely theoretical discussion. But I just didn't want to overlo

Re: [OpenOCD-devel] Support for low-cost development boards as JTAG adapters

On 10/20/2013 07:44 PM, Paul Sokolovsky wrote: > Hello, > > On Sun, 20 Oct 2013 16:28:59 +0200 > Michael Schwingen wrote: > >> On 10/20/2013 02:57 PM, Paul Fertser wrote: >>> Doesn't remote_bitbang that's already mainline fit all your >>> requi

Re: [OpenOCD-devel] Support for low-cost development boards as JTAG adapters

On 10/20/2013 04:55 PM, Paul Fertser wrote: > On Sun, Oct 20, 2013 at 04:28:59PM +0200, Michael Schwingen wrote: >> I wonder if one of the existing HLA protocols might be useable. > They're even higher level, about the Gdb serial protocol, so no, > unlikely. In that case, if

Re: [OpenOCD-devel] Support for low-cost development boards as JTAG adapters

On 10/20/2013 02:57 PM, Paul Fertser wrote: > Doesn't remote_bitbang that's already mainline fit all your > requirements? Just use socat to redirect a unix or tcp socket to your > serial port and you should be good to go. See tools/remote_bitbang/ > for an example client. HTH If this really takes

Re: [OpenOCD-devel] high output drive capability in raspberry pi

On 09/24/2013 03:30 PM, Paul Fertser wrote: >> If you have signal integrity issues, increasing the drive strength of the >> outputs may actually make the problem worse due to increased ringing. > So true. Do you probably have any suggestions on how to use > raspberrypi without additional buffers? W

Re: [OpenOCD-devel] high output drive capability in raspberry pi

On Tue, Sep 24, 2013 at 02:49:17PM +0400, Paul Fertser wrote: > I've seen blackmagicprobe failing to connect until I attached another > ground line. And someone on IRC reported he used 3 ground lines until > it started to work. Sounds reasonable - JTAG can be quite fast (in terms of rise/falltime,

Re: [OpenOCD-devel] [PATCH]: 51054c4 aice: fix FTBFS on ARM

On Sat, Jul 06, 2013 at 01:23:00PM +0400, Paul Fertser wrote: > > I would consider this to be a requirement for *any* new code to be merged, > > specially new code, no matter where it comes from. > > I've tried to find some reasonably accessible way to run BE code in an > emulated environment but

Re: [OpenOCD-devel] [PATCH]: 51054c4 aice: fix FTBFS on ARM

On Sat, Jul 06, 2013 at 07:23:47AM +, ger...@openocd.zylin.com wrote: > Paul Fertser (fercer...@gmail.com) just uploaded a new patch set to Gerrit, > which you can find at http://openocd.zylin.com/1477 > Also, the aice code I've seen so far seems to be assuming it runs on a > little-e

Re: [OpenOCD-devel] Instructions on doing (semi-)manual JTAG boundary scan with OpenOCD

On 06/21/2013 03:51 PM, Paul Fertser wrote: > Hi, > > It wasn't the first time I tried and failed to find any guides on > using JTAG for its original purpose, so I felt like trying it on my > own. It's still unclear how to communicate with several different > devices on a chain at the same time as

Re: [OpenOCD-devel] LPC4330 Xplorer

On Fri, Feb 22, 2013 at 02:11:32PM +0100, Laurent Gauch wrote: > > Right. However: are you sure *all* dongles out there do it right? > The Amontec JTAGkey and JTAGkey-2 was designed for hot-plugging , > without any glitch on power on etc ... That does not answer my question. > But we know some o

Re: [OpenOCD-devel] LPC4330 Xplorer

On Thu, Feb 21, 2013 at 06:51:13PM +0100, Laurent Gauch wrote: > > I think we should leave the signals in a defined, dongle/layout-specific > > state at disconnect, which may be different from what is present at power > > up. > > > If it is different from power on, it is not a good dongle concept.

Re: [OpenOCD-devel] LPC4330 Xplorer

On Thu, Feb 21, 2013 at 05:44:39PM +0100, Laurent Gauch wrote: > This will put the io in tristate ! > This will work with the Amontec JTAGkey JTAGkey-2 ... since we have > on-board strong pull-up and use OE_N to control the buffers . > This could be not enough for other dongle / layout without str

Re: [OpenOCD-devel] LPC4330 Xplorer

On Thu, Feb 21, 2013 at 10:11:02AM +0100, Laurent Gauch wrote: > Yes true, both ft2232.c and ftdi.c should tristate the JTAG port at > openocd quit. If openocd drive the pin it must tristate it at the end. > But how you tristate the port could be specific to the layout used. I > just say ft2232.c

Re: [OpenOCD-devel] OpenOCD with PPC architecture

On Thu, Jan 24, 2013 at 12:07:01PM +0100, Tomek CEDRO wrote: > Hey Michael. This may be the good starting point to obtain the > documentation as the project claims to be Open Source and there is some > community around it. Thats it, just a hint. You can give it a try, maybe > some nice Open Source

Re: [OpenOCD-devel] OpenOCD with PPC architecture

On Thu, Jan 24, 2013 at 10:11:01AM +0100, Tomek CEDRO wrote: > I am not really interested in these devices, but the Power Project claims > to be open source, so if there is no debug documentation yet available > maybe it is a good idea to request one :-) So you are just throwing us an unspecific U

Re: [OpenOCD-devel] OpenOCD with PPC architecture

On Thu, Jan 24, 2013 at 10:21:15AM +0100, Lino - Andrea wrote: > On Wed, Jan 23, 2013 at 03:14:59PM +0100, Øyvind Harboe wrote: > >I would like to work on e300/e500 cores, but the debug interface > >seems to be > >non-documented for practical purposes. > > I am interested to work on ST SPC560B and

Re: [OpenOCD-devel] OpenOCD with PPC architecture

On Wed, Jan 23, 2013 at 04:00:24PM +0100, CeDeROM wrote: > > If so, then PowerPC debug support isn't suitable for being supported > > by the opensource community. > > How about this one https://www.power.org/ ? :-) Where is the JTAG debug documentation on that site? cu Michael -

Re: [OpenOCD-devel] OpenOCD with PPC architecture

On Wed, Jan 23, 2013 at 03:14:59PM +0100, Øyvind Harboe wrote: > The PowerPC CPU doesn't really support an open documented standard for > communicating with it's debug hardware does it? No, AFAIK not. There was free documentation for the Motorola MPC860 - at a former employer, we implemented our o

Re: [OpenOCD-devel] Internals reorganization

On Tue, Jan 22, 2013 at 04:02:10PM +0100, CeDeROM wrote: > On Tue, Jan 22, 2013 at 3:17 PM, Peter Stuge wrote: > > The use case for such a prefix is when creating a library with a > > public API, which OpenOCD is not, and will not be in foreseeable > > time. > > If I am supposed to do the work, I

Re: [OpenOCD-devel] Internals reorganization

On Tue, Jan 22, 2013 at 03:02:54PM +0100, Tomek CEDRO wrote: > I propose to introduce and use superfluous variable names: > > 1. Prefix all variables and function names with "oocd_". This will > help to identify which code comes from OpenOCD in case we also use it > in conjuction with other progra

Re: [OpenOCD-devel] how to modify openocd source codes ?

Am 09/13/2012 04:28 AM, schrieb Nuwan Jayasekara: > Hi All, > i want to define new target type for openocd. i feel for that i have > to download source code and modify the code with IDE and compile and > run the program. can anyone help me to find a tutorial or forum thread > on this topic.Thank yo

Re: [OpenOCD-devel] openocd installation,

On 08/29/2012 08:21 PM, Javier Ortiz wrote: after that I looked again for openocd, but it's nowhere. during "make install" there were some errors make[3]: Leaving directory `/home/joc/Imote2/openocd/src' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/home/joc/Imote2/openo

Re: [OpenOCD-devel] OpenOCD-BOX

On 06/05/2012 07:25 AM, Peter Stuge wrote: > Austin, Alex wrote: >> As long as the DHCP response doesn't include a default route, it >> shouldn't interfere with an existing network connection. > If the DHCP server in the device has the same IP as the default > gateway then things stop working. > Al

Re: [OpenOCD-devel] OpenOCD-BOX

On 05/22/2012 03:57 AM, David Riley wrote: > > That's good to know; I imagine uClinux has a lot to do with > that. Most of the time I've had to play with embedded Linux > it's been with particularly boneheaded implementations that > take that long even on an 800 MHz PowerPC (I was not the > implem

Re: [OpenOCD-devel] Microchip Explorer 16 kit flash command

On 05/11/2012 02:51 AM, Bazzynga wrote: > Hi, > > I am using open-ocd to talk to Microchip Explorer 16 with Plug in module > PIC32MX. > > I tried to flash a word (0x0). But I can't restore it back. > > I ran a command like this > > > mdw 0x9d00 > 0x9d00: 0f400038 > > >flash fillw 0x9d0

Re: [OpenOCD-devel] GDB vs. Cortex-m3

On Tue, May 08, 2012 at 06:36:36PM -0700, Luke wrote: > To do this properly, it seems like openocd would have to be aware of > which version of gdb was going to be used with it, and conditionally > compile this file appropriately. Alternatively, a future release of > OpenOCD could simply require g

Re: [OpenOCD-devel] [PATCH]: f4b03f6 smartfusion_a2f200: reference code for flash writing

On 04/17/2012 12:50 AM, ger...@openocd.zylin.com wrote: > This is an automated email from Gerrit. > > Helen Fornazier (helen.fornaz...@gmail.com) just uploaded a new patch set to > Gerrit, which you can find at http://openocd.zylin.com/569 > > -- gerrit > > commit f4b03f660d1f381ae28f6d2721be6b8d2

Re: [OpenOCD-devel] Can BIOS prevent JTAG from ...

On 04/03/2012 08:23 AM, jana1...@centrum.cz wrote: Hi, In my a Linux based device there are CPU( yes, it is MIPS) and BIOS and SDRAM modules. If I have BIOS chip in that device, I can easily write to SDRAM and I read the same value I wrote. But if I remove BIOS I can not read the same values t

Re: [OpenOCD-devel] [RFC]: Spansion S29NS512P: Fix reading of number of sectors.

On Wed, Mar 28, 2012 at 04:54:00PM +0200, Javier Martin wrote: > According to p.82 of the datasheet, the erase region information > for the S29NS512P is configured as follows (16 bit addresses): > > Address Data Description > 2Dh 0x01FFh Number of sectors (lower byte) > 2Eh

Re: [OpenOCD-devel] MIPS ejtag DMA support

On Mon, Mar 26, 2012 at 02:26:07PM +0200, Jeroen Peelaerts wrote: > > Thanks for your reply. I'm sure that the flash is not empty, it contains > the original firmware of the device which boots up correctly. OK. Then the next step should be to get a dump of the correct memory area to display the

Re: [OpenOCD-devel] MIPS ejtag DMA support

On Fri, Mar 23, 2012 at 10:13:19AM +0100, Jeroen Peelaerts wrote: > But when probing for the flash memory, I get the following output (filtered > the output a bit) > > Debug: 9935 163572 command.c:145 script_debug(): command - ocd_command > ocd_command type ocd_flash probe 0 > Debug: 9936 16357

Re: [OpenOCD-devel] STM32W

On 01/26/2012 02:15 AM, Luke wrote: > >> Auto-probing the parameters from the device would be great it it can be >> done, but specifying them in the config file would also be OK (and >> probably easier to implement). > > From what I can tell, these devices don't make use of the ARM Private > Periph

Re: [OpenOCD-devel] STM32W

Am 01/25/2012 07:10 AM, schrieb Luke: > Also if i remember correctly the flash controller is not exactly the > same as the stm32f1x, may be worth checking the em357 driver. > The em35x family are the same device as the stm32w. > I'm trying to get started on the stm32w version and I was

Re: [OpenOCD-devel] Need small review

On 01/25/2012 06:54 PM, Freddie Chopin wrote: > W dniu 2012-01-24 22:36, Andreas Fritiofson pisze: >> It's fairly simple to replace the few instructions in stm32f1x.S that >> are unavailable on the M0, with their equivalent multi-instruction >> sequence. In fact I just did this, will try flashing t

Re: [OpenOCD-devel] How to start

Am 01/17/2012 12:59 PM, schrieb jana1...@centrum.cz: > So I found out TCK,TMS,TDO,TDI and RST signals on the JTAG connector > on my PCB. > The datasheet for the BCM7401 says the values for these are 3.3V. > But I can not find Vcc/Vref on JTAG. > Where should lead that Vcc/Vref from that JTAG conne