at91sam7s64 olimex debug=ok flash=no

Development Boards MicroMod
1

Hello together,

the problem:

  1. It is possible to flash the prg. No errors in the console.

  2. After reset the prg. don’t run. :?:

  3. If I change to the debugmode, start openocd and then the prg., the prg. works fine. :?

here my configuration:

Hardware:

board: at91sam7s64 olimex

Jtag: Olimex Tiny

Software:

Openocd, yagarto, eclipse

nik

2

Where are you locating the program when you flash it? The startup code has to be located at 0x00 (I think). The debugger may be able to start the program because it forces the CPU to jump to the flashed location and run.

3

Where are you locating the program when you flash it?

in the consolewindow I got the following messages during flashing: 
Flash Programming with OpenOCD...
d:/Programme/openocd-2007re204/bin/openocd-ftd2xx.exe -f d:/Programme/openocd-2007re204/bin/at91sam7s64-armusbocd.cfg            # program the onchip FLASH here
Info:    openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00 CEST)
Warning: arm7_9_common.c:734 arm7_9_assert_reset(): srst resets test logic, too
Info:    target.c:232 target_init_handler(): executing reset script 'script.ocd'
Info:    configuration.c:50 configuration_output_handler(): waiting for target halted...
Info:    configuration.c:50 configuration_output_handler(): target halted
Info:    configuration.c:50 configuration_output_handler(): core state: ARM
Info:    configuration.c:50 configuration_output_handler(): waiting for target halted...
Info:    configuration.c:50 configuration_output_handler(): target halted
Info:    configuration.c:50 configuration_output_handler(): waiting for target halted...
Info:    configuration.c:50 configuration_output_handler(): target halted
Info:    configuration.c:50 configuration_output_handler(): waiting for target halted...
Info:    configuration.c:50 configuration_output_handler(): target halted
Info:    configuration.c:50 configuration_output_handler(): waiting for target halted...
Info:    configuration.c:50 configuration_output_handler(): target halted
Info:    configuration.c:50 configuration_output_handler(): flash 'at91sam7' found at 0x00100000
Info:    configuration.c:50 configuration_output_handler(): wrote  2676 byte from file main.bin to flash bank 0 at offset 0x00000000 in 0s 531250us (4.919118 kb/s)
Info:    configuration.c:50 configuration_output_handler(): waiting for target halted...
Info:    configuration.c:50 configuration_output_handler(): target halted
Info:    configuration.c:50 configuration_output_handler(): core state: ARM
Info:    configuration.c:50 configuration_output_handler(): target state: halted
Info:    configuration.c:50 configuration_output_handler(): target halted in ARM state due to debug request, current mode: Abort
Info:    configuration.c:50 configuration_output_handler(): cpsr: 0x20000097 pc: 0x000007c8
Warning: arm7_9_common.c:734 arm7_9_assert_reset(): srst resets test logic, too
Flash Programming Finished.

The startup code has to be located at 0x00

I think, it's been written on the right place, ``` Info: configuration.c:50 configuration_output_handler(): wrote 2676 byte from file main.bin to flash bank 0 at offset 0x00000000 in 0s 531250us (4.919118 kb/s) ``` if the window show me the truth.

regards

nik

4

The problem is solved!

the problem was the frequency of the uC. - The frequency was to high.

So that in the flash-mode was to fast. → Prg. don’t runs.

In the debug-mode, had to be transported a lot of variables and dates.

The rate of transmission goes down. → the prg works.

regards

nik