Tomas Vanek writes: > Hi Augusto, > > see my comments in your message. > > On 15.03.2018 14:12, Augusto Fraga Giachero wrote: >> I've tried posting (twice) this message to the openocd-devel mailling >> list, but it didn't showed up in the archives. Anyway, this list seems >> more apropriate. > The mail archives are probably influenced by recent malfunctions of > sourceforge. > I did read both. And both openocd-user and -devel lists are appropriate. >
Ok, sorry for the noise! >> >> I've experiencing problems with recent versions of arm-none-eabi-gdb >> (8.0 and above) and openocd when connecting via pipe as suggested by the >> OpenOCD manual: >> >> (gdb) target remote | openocd -c "gdb_port pipe; log_output openocd.log" >> -f openocd.cfg > Probably not a widely used scenario. I've never tried it. > It might be the reason that nobody replied. > I connect via pipe because I didn't find a nicer way to start both, gdb and openocd, in the same terminal in a OS independent way without having problems with interrupt signals propagating to openocd. >> And I get: >> >> Remote replied unexpectedly to 'vMustReplyEmpty': >> PacketSize=3fff;qXfer:memory-map:read+;qXfer:features:read+;qXfer:threads:read+;QStartNoAckMode+ > Something is broken in gdb remote protocol as gdb reads the reply send > by OpenOCD to qSupported > command, which is send just before vMustReplyEmpty command. > You may want get more detailed logs: add -d3 to openocd command and > 'set debug remote 1' in gdb before > 'target remote' is issued. > Ok, I'll try this when I get my hands on the hardware again. >> But if I try to connect through TCP everything works fine. >> >> I'm debugging STM32Fx microcontrollers and connecting over pipe worked >> great until 3 weeks ago. I've been searching for similar problems on >> forums and mailling lists, but couldn't find relevant info. > Can you trace what changed in this 3 weeks? > Did you upgraded arm-none-eabi-gdb to 8.x? > Do you use OpenOCD 0.10.0 release or some newer git snapshot compiled > from sources? > I've tried some older gdb releases (down to 7.x) that I've on my pacman's pkg cache and the problem still showing up, so I'm not completely sure if this problem was introduced by gdb. But I haven't upgraded openocd since the 0.10.0 released version and it was working perfectly one month ago. I've experienced this problem with other machines running Ubuntu and the gnu toolchain provided by Arm (https://developer.arm.com/open-source/gnu-toolchain/gnu-rm). First I thought this was specific to their binaries but soon I experienced the same problem on my machine. I'll try to put my development environment in the same state it was before this problem started to happen. Thanks, Augusto Fraga Giachero ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
