We are using openocd with no problems with a ADuc7020 and ADuc7021
(different boards) but when we try to flash a board with the 7022 we run
into problems.

 

The debugger uses an RDI probe and we can program with it fine, we can also
verify the image (ihex) with openocd.

 

When we try to erase and reprogram it we get:

 

S:\>openocd -f file.txt

Open On-Chip Debugger 0.4.0 (2010-02-22-19:05)

Licensed under GNU GPL v2

For bug reports, read

        http://openocd.berlios.de/doc/doxygen/bugs.html

jtag_nsrst_delay: 200

jtag_ntrst_delay: 200

Info : clock speed 6000 kHz

Info : JTAG tap: aduc702x.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787,
part: 0xf0f0, ver: 0x3)

Info : Embedded ICE version 1

Info : aduc702x.cpu: hardware has 2 breakpoint/watchpoint units

target state: halted

target halted in ARM state due to debug-request, current mode: System

cpsr: 0x400000df pc: 0x000007b0

erased sectors 0 through 123 on flash bank 0 in 6.453125s

Info : Padding image section 0 with 28 bytes

Info : Padding image section 1 with 28 bytes

Warn : memory write caused data abort (address: 0x00010040, size: 0x4,
count: 0x

5ad)

Error: error writing to flash at address 0x00080000 at offset 0x00000000
(-307)

Command handler execution failed

 

 

Here is my burn script

 

#####################################################

#

 

telnet_port 4444

tcl_port 6666

gdb_port 3333

 

sleep 500

#jtag_khz 100

 

source [find interface/olimex-jtag-tiny.cfg]

source [find target/aduc702x.cfg]

 

init

halt

 

# Write to MEMMAP to enable access to flash below first 64 bytes

mwh 0xfffff804 0x8

 

#setup POWCON register to obtain the default 5.22MHz (RC osc) clock.

#  POWKEY1 = 0x01;

mwh 0xffff0404 0x01

#  POWCON = 0x0;

mwh 0xffff0408 0x0

#  POWKEY2 = 0xF4;

mwh 0xffff040c 0xf4

 

sleep 100

 

flash erase_sector 0 0 123

flash write_image file.hex 0x80000 ihex

verify_image      file.hex 0x80000 ihex

exit

 

The Verify script is the same with the Erase and Flash Write commented out

 

Any ideas? Anyone work with the 7022 before?

 

Tom

 

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to