Hi,
I'm new to the forum, thanks for your great work.
So I've got a new 2072A and I am currently trying to dump the beast,
I soldered a cable for my USB Blaster and started Dumping according to
post #2433, the Bfin is recognized nicely.
Dumping seems to work, but when it's finished, gdb spits out
dump binary memory ~/sdram.bin 0x00000000 0x07FFFFFF
Ignoring packet error, continuing...
Reply contains invalid hex digit 116
and even as the process takes hours and I can see gdbproxy's debug out
to iterate over the address space, no file is written.
I've already increased gdb's remotetimeout without any change.
As the BF-Toolchain was not available for Mac and did not compile on first try,
I used a current Ubuntu on my old Atom Netbook to do the dump.
Update:
Now also tried with same '116' problem on my MacBook Pro in a Ubuntu 14.04 VirtualBox.
I've even tried several toolchains and gdbproxy/gdb combinations
Update 2 (solved using workaround):
I managed to extract a dump and generate Keys using this workaround:
in gdb, I used
set debug remote 1
and
set remotelogfile /tmp/log
Then I started a new dump, which failed at the end with the stated '116' error, but all responses from the Blackfin were logged as ascii hexdump in the logfile.
I then awk'd the logfile to include only lines starting with +r $ and then removed this string using vi (:%s/^r\ +$//g)
Now I used xxd -p -r to convert the hexdump to binary and ran rigup on it, which worked fine.
Greetings,
- pit