On 2010-04-20 09:46, Andreas Fritiofson wrote:
Freddie, have you checked if the patch resolves your problem?
I managed to check that today (sorry for delay). Current master (with
the merged patch) fixes the first gdb load issue completely for me.
Everything else regarding the stm32 chip
BTW - I've posted the compiled version on my website
(www.freddiechopin.info) for ppl to test.
Cheers!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Merged.
I would still like to see a more robust general solution to this problem,
but identifying it is a very good start...
--
Meet Zylin at ESC 2010 San Jose
April 26 - 30. 2010
http://www.zylin.com/events_esc2010.html
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63
I've updated the documentation on the gdb-attach event to
provide an alternate way to solve this issue.
--
Meet Zylin at ESC 2010 San Jose
April 26 - 30. 2010
http://www.zylin.com/events_esc2010.html
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
On Tue, Apr 20, 2010 at 9:08 AM, Øyvind Harboe oyvind.har...@zylin.com wrote:
I've updated the documentation on the gdb-attach event to
provide an alternate way to solve this issue.
Great! And there's the target event list that I was briefly searching
for. Good to know there is one.
Freddie,
You have found an interesting case here indeed.
As a principle it should be possible to connect via GDB regardless
of the target state.
Since that state, in general, can include a case where the target's
flash is not probable and we need the flash layout upon connection,
I think we need a more
On 2010-04-17 09:40, Øyvind Harboe wrote:
I would like a robust and simple solution. This is not a common problem,
it is the first time that it has been spotted.
I believe that the problem spotted here is the reason for this bug
reported by me a while ago:
On Sat, Apr 17, 2010 at 9:40 AM, Øyvind Harboe oyvind.har...@zylin.com wrote:
You have found an interesting case here indeed.
As a principle it should be possible to connect via GDB regardless
of the target state.
Since that state, in general, can include a case where the target's
flash is
I think you make some good points specifically for this target.
I'll let this patch cool off + await for feedback on this discussion before
considering merging.
--
Meet Zylin at ESC 2010 San Jose
April 26 - 30. 2010
http://www.zylin.com/events_esc2010.html
Øyvind Harboe
US toll free
If the flash has not yet been probed and GDB connects while the target is
running, the flash probe triggered by GDB's memory map read will fail. In
that case the returned memory map will be empty, causing a subsequent load
from within GDB to fail. There's not much you can do from GDB to recover,
10 matches
Mail list logo
