From: Dirk B. <dir...@go...> - 2009-09-30 21:27:52
|
Magnus Lundin wrote: > We can, and sometimes we want to, write to memory while the CortexA8 > core is running, > but for gbd to load a program and the i-caches to be cleared to core > must be halted. Yes, thanks! Attachment now gives me: -- cut -- > arm-none-linux-gnueabi-gdb GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi". *** Executing .gdbint to set up the environment for debugging gdb: 0x8200003c in ?? () The target may not be able to correctly handle a memory-write-packet-size of 1024 bytes. Change the packet size? (y or n) [answered Y; input not from terminal] TargetName Type Endian TapName State -- ------------------ ---------- ------ ------------------ ------------ 0* omap3.cpu cortex_a8 little omap3530.dap halted *** Environment ready, now load and start executeable: Loading section .text, size 0xe0 lma 0x82000000 Start address 0x82000000, load size 224 Transfer rate: 4 KB/sec, 224 bytes/write. Current language: auto; currently asm Breakpoint 1 at 0x8200003c: file LEDblink.c, line 22. Breakpoint 1, main () at LEDblink.c:22 22 LEDbrightness++; Current language: auto; currently c (gdb) -- cut -- already at first start up :) Thanks Dirk |