Skip to main content
al2757
al2757
Associate
September 8, 2009
Question

GDB issue on STM32

  • September 8, 2009
  • 1 reply
  • 596 views
Posted on September 08, 2009 at 11:21

GDB issue on STM32

    This topic has been closed for replies.

    1 reply

    al2757
    al2757Author
    Associate
    May 17, 2011
    Posted on May 17, 2011 at 13:23

    Hello everybody,

    I am working on a STM3210E-EVAL board for 2 weeks now and there are some odd things happening when I use the GDB provided with WinARM(gdb version 6.4.50.20060226-cvs).

    I use Eclipse as a IDE, everything seems to be working fine until I reach some instructions that need to work with register R7('mov.w r7,0' or 'mov.w r7,r7,#12', also an add.w r7 creates the same outcome), I took a look on the packages sent by gdb and this is what it sends:

    Sending packet: $m2000037e,2#8c...Ack

    Packet received: 80bc

    Sending packet: $m20000380,2#58...Ack

    Packet received: 7047

    Sending packet: $Hc0#db...Ack

    Packet received:

    Sending packet: $s#73...Ack

    Packet received: O7461726765742073746174653a2068616c7465640a

    Packet received: O7461726765742068616c74656420696e205468756d622073746174652064756520

    746f2073696e676c6520737465702c2063757272656e74206d6f64653a205468726561

    64200a785053523a20307830313030303030302070633a20307832303030303332320a

    target state: halted

    target halted in Thumb state due to single step, current mode: Thread

    xPSR: 0x01000000 pc: 0x20000322

    Packet received: T05

    Sending packet: $g#67...Ack

    Packet received: 0000000000000080e04f0020020000003600000037000000ffffbff700000000

    ffffffffffffbff73d0000006dddfe4810000000bc4f00204d26002023030020000000000

    0000000000000000000000000000000000000000000000000000000000000000000000000

    0000000000000000000000000000000000000000000000000000000000000000000000000

    00000000000000000000000000000000000000000000000000001

    Sending packet: $m20000322,4#56...Ack

    Packet received: 07f10c07

    Sending packet: $m3c,4#63...Ack

    Packet received: E0E

    The bolded message is what actually this error is about, normally that package should not exist and it happens only when I try ''mov.w r7,0'', if I try ''mov.w r1,0'' this packet doesn't get sended.

    Everything works fine(single stepping,watches,and so on) except for this problem.

    Any ideas?

    Thank you in advance!

    LC

    [ This message was edited by: al2757 on 08-09-2009 14:52 ]

    Terms & ConditionsAccessibility statement