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 CFLAGS="-g
-O2 -L/usr/local/lib"
make
Then, when I run src/openocd -f tcl/board/crossbow_tech_imote2.cfg -f
interface/jtagkey-tiny.cfg
I get the following output:
Open On-Chip Debugger 0.4.0-dev-00659-g2653b80 (2009-11-26-12:31)
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
jtag_nsrst_delay: 260
jtag_ntrst_delay: 250
jtag_nsrst_delay: 800
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Error: type 'xscale' is missing write_phys_memory
Error: type 'xscale' is missing read_phys_memory
Info : clock speed 6000 kHz
Info : JTAG tap: imote2.cpu tap/device found: 0x79265013 (mfg: 0x009,
part: 0x9265, ver: 0x7)
I am confused about these "write_phys_memory" and "read_phys_memory"
errors. I found the place in the code where the checking is performed
but have no idea how to fix the errors. The problem is that afterwards I
get errors with flashing my imote2 and I thought that the following
errors might relate to "write_phys_memory" and "read_phys_memory"
errors. Although I have a valid blob-im2 in place, what I get with
flashing is:
flash write_image blob-im2
couldn't open blob-im2
Runtime error, file "command.c", line 580:
couldn't open blob-im2
Could you please give me some hints how to solve this, or refer me to
some other openocd versions that could work?
In fact, I have tried also openocd-0.2.0.tar.bz2 and
openocd-0.3.1.tar.bz2 but flashing was unsuccessful, too:
> flash write_image blob-im2
couldn't open blob-im2
called at file "command.c", line 473
called at file "embedded:startup.tcl", line 89
called at file "embedded:startup.tcl", line 91
called at file "embedded:startup.tcl", line 93
I am looking forward to your help. Thanks in advance.
Andrei
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
