[Openocd-development] write_phys_memory and read_phys_memory

Hi, I am sorry if this the wrong place for this kind of help request. I am using Openocd (latest version from git) to program my imote2 sensor via an Amontec JTAG-tiny. To configure and build openocd I use the following commands: ./configure --prefix=/usr/local/lib/ --enable-ft2232_libftdi

Re: [Openocd-development] write_phys_memory and read_phys_memory

Hi Andrey, Error: type 'xscale' is missing write_phys_memory Error: type 'xscale' is missing read_phys_memory Ignore these errors. They are only reminders to the developers to add this support to the xscale target. Try writing up a fresh bug report using these guidelines:

Re: [Openocd-development] write_phys_memory and read_phys_memory

Hi Øyvind, Thanks for your previous message. Do you have any idea about the nature of the following runtime error (I get it when I try to protect a memory part for blob)? reset halt JTAG tap: imote2.cpu tap/device found: 0x79265013 (mfg: 0x009, part: 0x9265, ver: 0x7) target state: halted

Re: [Openocd-development] write_phys_memory and read_phys_memory

Have you tried: https://lists.berlios.de/pipermail/openocd-development/2009-November/012907.html -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer

Re: [Openocd-development] write_phys_memory and read_phys_memory

Thank you for referring to this. It solved the problem. Regarding the previous problem couldn't open blob-im2 I also solved it: I needed to run both 'openocd' and 'telnet localhost ' from the same directory (my mistake). Cheers, Andrey Øyvind Harboe wrote: Have you tried:

Re: [Openocd-development] write_phys_memory and read_phys_memory

On Thu, 2009-11-26 at 14:05 +0100, Øyvind Harboe wrote: Hi Andrey, Error: type 'xscale' is missing write_phys_memory Error: type 'xscale' is missing read_phys_memory Ignore these errors. They are only reminders to the developers to add this support to the xscale target. I saw these two

Re: [Openocd-development] write_phys_memory and read_phys_memory

On Thursday 26 November 2009, Zach Welch wrote: On Thu, 2009-11-26 at 14:05 +0100, Øyvind Harboe wrote: Hi Andrey, Error: type 'xscale' is missing write_phys_memory Error: type 'xscale' is missing read_phys_memory Ignore these errors. They are only reminders to the developers to

Re: [Openocd-development] write_phys_memory and read_phys_memory

Error: type 'xscale' is missing write_phys_memory Error: type 'xscale' is missing read_phys_memory In this case a minimal correct implementation of those two methods would be to return ERROR_FAIL.  Obviously, something that does the relevant hard work would be better. Committed that