Re: [Openocd-development] [PATCH 3/3] ft2232: Add casts to avoid warnings

On Fri, Jun 24, 2011 at 1:03 PM, Øyvind Harboe wrote: > The patch fails. > > Could you rebase and repost? > I think the whole idea is fail. This patch adds more problems than it fixes. What size of unsigned long is on amd64 or ppc64? PRIx macros are for fixed-width types, like int32_t. Unsigned lo

Re: [Openocd-development] [PATCH 3/3] ft2232: Add casts to avoid warnings

On Thu, Jun 23, 2011 at 4:39 PM, Laurent Gauch wrote: >> >/ On Thu, Jun 23, 2011 at 1:03 PM, Steve Bennett > > workware.net.au >> > > wrote: >> />>/ On 23/06/2011, at 8:59 PM, Øyvind Harboe wrote: >> />>/ />>>/ I don't think this is su

Re: [Openocd-development] bitbanging ft2232 dongle port from TCL is TOO DANGEROUS : PLEASE COMMENT

On Mon, Jun 20, 2011 at 4:44 PM, Laurent Gauch wrote: >>  only one transport option; autoselect 'jtag' >>  > interface_signal list >>  interface_signal list >>      Interface Signal Name      |    Mask    |   Value >>  -- >>  > interface_sign

Re: [Openocd-development] [PATCH] Change "kb/s" to "KB/s" in messages refering to kibibytes

> > kilograms is Kg not kg That's wrong - kilogram is kg. IIRC data rate units are special category. Also openocd target audience will never have problems with kilobyte/kibibyte mess, so familiar KBps or KB/s should be used, IMHO. ___ Openocd-development

Re: [Openocd-development] Common TFTP support

On Wed, Dec 2, 2009 at 5:57 PM, Øyvind Harboe wrote: > This one? > > http://lufs.sourceforge.net/ I think you meant fuse http://fuse.sourceforge.net/ but I don't really know if that supports tftp or not. We use plain tftp and NFS for production. ___ Ope

Re: [Openocd-development] What's git's equivalent to svn version #?

Hi! On Wed, Oct 14, 2009 at 6:11 PM, Øyvind Harboe wrote: > What's the most reasonable way to refer to a git version > for human beings? > > In svn it's a small integer("only" in the thousands). > > I was thinking about something like "0.2 + N versions". Most git-using people are happy with commi

[Openocd-development] PXA issues, GDB debugging on slow clocks

Hi, all! First, I need to report that PXA debugging works with current trunk, with a few minor issues (like ones in TODO list). So I debug some prototype device, which is quite buggy itself, I have managed to set up more or less stable configuration, was able to flash file, etc. But what I can't

[Openocd-development] xscale debug_handler.bin

Hi, all! TODO does have the following entry: - regression: xscale does not place debug_handler.bin into the right spot. workaround: use -s option on command line to place xscale/debug_handler.bin in search path. And, really, ${prefix}/lib/openocd/xscale is not within scripts search path. We ca

[Openocd-development] PXA270 problems

Sorry, forgot to Cc list -- Forwarded message -- From: Sergey Lapin Date: Wed, Sep 9, 2009 at 12:00 PM Subject: Re: [Openocd-development] PXA270 problems To: Øyvind Harboe On Wed, Sep 9, 2009 at 11:45 AM, Øyvind Harboe wrote: > On Wed, Sep 9, 2009 at 9:39 AM, Mich

Re: [Openocd-development] PXA270 problems

On Wed, Sep 9, 2009 at 12:25 AM, Øyvind Harboe wrote: > On Tue, Sep 8, 2009 at 8:50 PM, Sergey Lapin wrote: >> Hi, all! >> >> When working with PXA270 I see the following messages on reset. >> >> JTAG tap: pxa270.cpu tap/device found: 0x49265013 (mfg: 0x009, pa

[Openocd-development] PXA270 problems

Hi, all! When working with PXA270 I see the following messages on reset. JTAG tap: pxa270.cpu tap/device found: 0x49265013 (mfg: 0x009, part: 0x9265, ver: 0x4) value captured during scan didn't pass the requested check: captured: 0x00 check_value: 0x02 check_mask: 0x07 JTAG error while writing DC

Re: [Openocd-development] OpenOCD + beagle

On Mon, Jul 6, 2009 at 7:43 PM, Magnus Lundin wrote: > Wookey skrev: >> +++ Sergey Lapin [2009-07-06 19:02 +0400]: >> >>> Hi, all! >>> >>> Is there any news regarding support of BeagleBoard in OpenOCD? >>> Last time I checked, there was none

[Openocd-development] OpenOCD + beagle

Hi, all! Is there any news regarding support of BeagleBoard in OpenOCD? Last time I checked, there was none, I'm interested to help, so I want to know the status and what can I do. Thanks a lot, S. ___ Openocd-development mailing list Openocd-developmen

Re: [Openocd-development] RFC: uint32_t vrs u32 - et al

Hi, all! Well, I think I need to add something to discussion. We actually have 3 problems here. 1. Type defintions problem. 2. As [1] is decided, there is transition needed. 3. Whatever is done, it does not add to functionality, only maintainability. As it is generally considered, when release pr

[Openocd-development] nand support

Hi, all! Do I miss something or OpenOCD do definitely have NAND support? For which processorts it exists? How hard it is po port that to at91sam9260? Thanks a lot, S. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://list

Re: [Openocd-development] RFC: bug/patch/testing tracking

> Hi all, > > I would like to define a modest feature set with a list of use-cases. > Here would be my various criteria, were I to implement one from scratch: > > General Requirements: > - KISS: simple to use, simple to change, simple to love. I did not have anything simpler and more usable than b

Re: [Openocd-development] JLink + MC1322x

On Wed, Mar 18, 2009 at 8:16 PM, Jeff Williams wrote: > Hi Alan, > > First, thanks for your assistance. > > At the top of jlink.c and jtag.h are some switches to turn on state > machine debugging. Could you turn those on with and without the patch > and then send me the output? The state machine

Re: [Openocd-development] JLink + MC1322x

Dear Jeff, Duane and All! What are news, if any, regarding Jeff's patch for OpenOCD? I just want to know a little bit of details, and I'd like to help, if I can. All the best, S. ___ Openocd-development mailing list Openocd-development@lists.berlios.de

Re: [Openocd-development] JLink + MC1322x

On Mon, Mar 9, 2009 at 6:05 AM, Jeff Williams wrote: > Hi, > > I've made some changes to OpenOCD to support the Segger JLink for the > Freescale MC1322x. > > I'm working with someone who says that my changes seem more stable for > JLink overall, but he also says there might be some issues with ARM

Re: [Openocd-development] Reset, Halt, and Init Problems with AT91SAM9G20

On Tue, Mar 3, 2009 at 10:09 AM, Rob Emanuele wrote: > Greetings, > > I've been using OpenOCD for a few years now. I've had great success > using it with the STM32 family of processors. I've just moved to a > new platform with the AT91SAM9G20 processor from Atmel. > > I'm having a bit of trouble

[Openocd-development] PXA270

Hi, all! Since I'm really interested in support for pxa270 in OpenOCD for my OpenSurce - related projects, I'd like to know what could I do for a project. I'm pretty good with C and hopefully have enough of knowledge about various ARM/PXA devices, I have very little knowledge about JTAG/EICE. But

Re: [Openocd-development] several PXA270 issues.

Hi, Øyvind! On Mon, Feb 23, 2009 at 12:09 AM, Øyvind Harboe wrote: > On Sun, Feb 22, 2009 at 10:03 PM, Sergey Lapin wrote: >> On Sun, Feb 22, 2009 at 8:04 PM, Øyvind Harboe >> wrote: >>> Please post the patch as an attachment. It didn't apply cleanly. Please see

[Openocd-development] PXA270: conclusion

Hi, all! Reading through mail list archives and by trial-and-error, I found that: 1. Latest SVN revision which works with PXA270 is 825. 2. jlink won't work with this version, but olimex arm-usb-ocd will (probably any with ft2232) with closed source driver. libftdi tries to work, but fails with ch

Re: [Openocd-development] several PXA270 issues.

Hi, all! As I see, latest reported working with pxa270 version of OpenOCD is r825. But I was unable to make it work with jlink at all. All versions with working jlink provide the same errors I posted earlier. Is ther any chance for me to make PXA270 work with jlink, or should I use another tool?

Re: [Openocd-development] PXA270: can read/write the core registers, but can't read memory and registers of the devices on chip

I have the same kind of problem on Colibri PXA270 module, with different b/l so I'll add a bit. On Thu, Dec 4, 2008 at 2:53 AM, Duane Ellis wrote: > dswei wrote> [pxa270 - I can change cpu regs, not memory, target is in > USER mode] > > > Question #2 - Maybe UBOOT is turning the CPU cache on and

[Openocd-development] several PXA270 issues.

Hi, all! First of all, pxa270.cfg in current trunk doesn't work, because it has bad line in file. The following patch fixes this problem: Index: src/target/target/pxa270.cfg === --- src/target/target/pxa270.cfg(revision 1377

[Openocd-development] PXA270

Hi, all! Do anybody have proper pxa270 config to play with? I try to use colibri board. btw, target/pxa270.cfg soesn't work. All the best, S. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/list

[Openocd-development] defintions of peripherals in tcl configs

Hi, all! while working with mc13224 and looking in scripts for other devices, I see a lot of various peripheral defintions. How could I use them/implement them? I'm mostly interested in flash and spi. is there some documentation available regarding this? Thanks a lot, S. _

Re: [Openocd-development] support for freescale mc13224

On Wed, Jan 21, 2009 at 8:56 PM, Sergey Lapin wrote: > On Wed, Jan 21, 2009 at 8:26 PM, Alan Carvalho de Assis > wrote: >> Hi Sergey, >> >> On Wed, Jan 21, 2009 at 4:30 PM, Sergey Lapin wrote: >>> Hi, all! >>> >>> I write support fo

Re: [Openocd-development] support for freescale mc13224

On Wed, Jan 21, 2009 at 8:26 PM, Alan Carvalho de Assis wrote: > Hi Sergey, > > On Wed, Jan 21, 2009 at 4:30 PM, Sergey Lapin wrote: >> Hi, all! >> >> I write support for mc13224 - arm7tdmi-based ieee8021.15.4 -compliant >> communication chip. Chip is quite new

[Openocd-development] support for freescale mc13224

Hi, all! I write support for mc13224 - arm7tdmi-based ieee8021.15.4 -compliant communication chip. Chip is quite new, documentation is in weird state and is not full, but core and basic peripherals like SPI are documented normally. I already managed to make core work, but I can't manage it to rese

Re: [Openocd-development] at91sam9260

On Mon, Dec 8, 2008 at 2:23 PM, Duane Ellis <[EMAIL PROTECTED]> wrote: > Sergey> With my custom config of > Sergey> > Sergey> source [find interface/jlink.cfg] > Sergey> telnet_port > Sergey> gdb_port > Sergey> source [find target/at91rm9200.cfg] > Sergey> > > Hmm, above seems *wrong* - i

[Openocd-development] at91sam9260

Hi, all! A config for this device is not properly working. With my custom config of source [find interface/jlink.cfg] telnet_port gdb_port source [find target/at91rm9200.cfg] In target/at91sam9260minimal.cfg I have changed TAP ID to a proper one set _CPUTAPID 0x0792603f and then OpenO

[Openocd-development] atmel SPI dataflash at91 scripts for openocd

Hi, all! I have a small problem in not so far future, which requires bootstrapping several hundreds of in-house at91sam9260 boards. They come empty, so it was decided to bootstrap them by hand. Only thing which works on them is jtag, so the questions are: 1. Did anybody used OpenOCD to flash lots

Re: [Openocd-development] mips target

On Sat, Jul 26, 2008 at 2:33 PM, Spen <[EMAIL PROTECTED]> wrote: > Hi, > > I have merged the mips target into trunk - it is still work in progress. Could there be some announcement about features? Because I'm very interested (mostly regarding rtl865xb CPU). _

[Openocd-development] NAND

Hi, all! Is there some documentation around on making NAND flash work for OpenOCD on some particular board? S. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

[Openocd-development] Fwd: Implementing OpenOCD in Lua & C

Sorrym forgot to Cc list. -- Forwarded message -- From: Sergey Lapin <[EMAIL PROTECTED]> Date: Wed, Jun 25, 2008 at 6:39 PM Subject: Re: [Openocd-development] Implementing OpenOCD in Lua & C To: Øyvind Harboe <[EMAIL PROTECTED]> On Wed, Jun 25, 2008 at 5:55 P

Re: [Openocd-development] Adding Jim Tcl support to OpenOCD

On Wed, Jun 25, 2008 at 1:42 PM, Øyvind Harboe <[EMAIL PROTECTED]> wrote: > Jim Tcl is embedded friendly, which for me is a killer feature + > it is used by VHDL developers via e.g. ModelSim. > > Lua is nice as well. I'm surprised to see it rated that high. Never seen > in real life usage. Could be

[Openocd-development] jlink and at91sam9260 - success story

Hi, As feedback I'd like to announce that I have tested OpenOCD trunk and found that jlink works with my at91sam9260-based board. I was unable to halt board immediately. Allowing it to run for some time works though: openocd.cfg: #daemon configuration telnet_port gdb_port #interface i