I have a sam7-p256 rev e board and the Olimex ARM USB OCD. I have both Test and BDS jumpers open. I’m having trouble getting this LED blinking stuff to work, I’m using the example code in the CD. I installed the software in from the included CD which included,
ARM-USB-OCD drivers: FTDI drivers from 2008-03-13
Eclipse: Version: 3.4.1 (Ganymede)
Zylin Eclipse plugin: Version 4.5.1
OpenOCD: Revision 717 from 2008-06-18
OpenOCD for STM32: Revision 555 from 2008-04-09
Yagarto: binutils: 2.18
gcc: 4.2.2
newlib: 1.16.0
gdb: 6.8.50-20080308-cvs
(08.04.2008, mifi)
Java Runtime: Version 6 update 7
When I try and run the OpenOCD tool I get
Open On-Chip Debugger 1.0 (2008-10-04-10:00) svn:exported
$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
Info: options.c:50 configuration_output_handler(): jtag_speed: 10, 10
Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger 1.0 (2008-10-04-10:00) svn:exported
Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)
Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)
Info: target.c:237 target_init_handler(): executing reset script 'sam7flash.script'
Info: options.c:50 configuration_output_handler(): dcc downloads are enabled
Info: options.c:50 configuration_output_handler(): core state: ARM
Info: options.c:50 configuration_output_handler(): flash 'at91sam7' found at 0x00100000
Info: options.c:50 configuration_output_handler(): #0: at91sam7 at 0x00100000, size 0x00040000, buswidth 4, chipwidth 0
Info: options.c:50 configuration_output_handler(): #0: 0x00000000 (0x40000 256kB) protection state unknown
Info: options.c:50 configuration_output_handler():
at91sam7 information: Chip is AT91SAM7S256
cidr: 0x270d0940, arch: 0x0070, eproc: ARM7TDMI, version:0x000, flashsize: 0x00040000
master clock(estimated): 51047kHz
pagesize: 256, lockbits: 16 0x0000, pages in lock region: 64
securitybit: 0, nvmbits(2): 0x0
Info: options.c:50 configuration_output_handler(): cleared protection for sectors 0 through 15 on flash bank 0
Info: options.c:50 configuration_output_handler(): gpnvm bit '#2' is out of bounds for target AT91SAM7S256
Info: options.c:50 configuration_output_handler(): erased sectors 0 through 0 on flash bank 0 in 0.046874s
Error: fileio.c:79 fileio_open_local(): couldn't open main.bin
Error: ft2232.c:174 ft2232_write(): FT_Write returned: 4
Error: ft2232.c:404 ft2232_send_and_recv(): couldn't write MPSSE commands to FT2232
Here is the config file
#
# Flash AT91SAM7S memory using openocd
# and a FTDI FT2232-based JTAG-interface
#
# created by Martin Thomas
# based on information from Dominic Rath
#
#daemon configuration
telnet_port 4444
gdb_port 3333
#interface
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG A"
ft2232_layout "olimex-jtag"
ft2232_vid_pid 0x15BA 0x0003
jtag_speed 2
jtag_nsrst_delay 200
jtag_ntrst_delay 200
#use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst
#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0xe
#target configuration
daemon_startup reset
#target <type> <startup mode>
#target arm7tdmi <reset mode> <chainpos> <endianness> <variant>
target arm7tdmi little run_and_init 0 arm7tdmi_r4
run_and_halt_time 0 30
# flash-options AT91
target_script 0 reset sam7flash.script
working_area 0 0x00200000 0x4000 nobackup
flash bank at91sam7 0 0 0 0 0
# Information:
# erase command (telnet-interface) for complete flash:
# flash erase <num> 0 numlockbits-1 (can be seen from output of flash info 0)
# SAM7S64 with 16 lockbits and bank 0: flash erase 0 0 15
# set/clear NVM-Bits:
# at91sam7 gpnvm <num> <bit> <set|clear>
# disable locking from SAM-BA
# flash protect 0 0 1 off
# For more information about the configuration files, take a look at:
# http://openfacts.berlios.de/index-en.phtml?title=Open+On-Chip+Debugger
Any one have an idea of how to fix it? Because I’m a bit lost at this point.