Jie,
At 10:17 09/08/15, Jie Zhang wrote:
Atomu Hidaka wrote:
- version of software (toolchain/gdbproxy/gdb/etc...)
gdbproxy/jtag: revision 3524(svn) and all before
toolchain/gdb: blackfin-toolchain-08r1.5-14.i386.tar.bz2 and all before
host: Fedora 8, ubunts, CentOS5.x
How did you start gdbproxy?
I cannot tell you all options, because I tried very various and
numerous options like followings.
# gdbproxy bfin --board=bf533-stamp --connect="cable OOCDLink-s
ftdi-mpsse 0403:baf8"
# gdbproxy bfin --board=bf533-stamp --connect="cable jtagkey
ftdi-mpsse 0403:6010"
# gdbproxy bfin --wait-emuready --board=bf533-stamp --connect="cable
OOCDLink-s ftdi-mpsse 0403:baf8"
# gdbproxy bfin --wait-emuready --board=bf533-stamp --connect="cable
jtagkey ftdi-mpsse 0403:6010"
--frequency=8000000.... --loop-wait=50000....
I analyzed the USB packet by CATC, too.
Currently, I know those options are not related for our problems.
The loading image size is also not related.
The problem occurs when the image is loading continuously
from 0x3FFFFC to 0x400000 by following memory_write() loop.
for (; size >= 4; size -= 4)
{
uint32_t data;
data = *buf++;
data |= (*buf++) << 8;
data |= (*buf++) << 16;
data |= (*buf++) << 24;
core_emudat_set (core, data, RUNTEST);
}
Sorry, I described incorrect position of for-loop in memory_write()
for this problem before.
- Blackfin hardware (cpu/board/memory/etc...)
cpu: bf533/600MHz
board: our original (close to bf533-stamp)
/w 64MB SDRAM 4MB, NAND Flash ROM
http://www.devdrv.co.jp/products/boards/E!Kit-BF533/BF533-50.jpg
Did you find this error on other boards?
Not yet now. But I have a plan to try that.
Atomu Hidaka
_______________________________________________
Toolchain-devel mailing list
[email protected]
https://blackfin.uclinux.org/mailman/listinfo/toolchain-devel
