Forum Replies Created
[Solved] Don’t try and use a USB NIC. My test netbook had the onboard NIC disabled and was attempting to use the USB ethernet adaptor that was also plugged into the machine …
dmesg shows this:
netpoll: kgdboe: eth0 does not support polling. aborting.
currently running mint with the 188.8.131.52 kernel if that helps.
wonder if this is the reason: http://askubuntu.com/questions/139314/netconsole-error-eth0-doesnt-support-polling
Please ignore this. I loaded up the Portable 3.4 version which works just fine.
Great stuff. thanks you.
If possible, yes. I am away from the machine in question, though I think this can be reproduced quite easily using advanced/manual CPU settings.
Thanks Bazis I will put this on my todo list
Hello Bazis. Any update on this would be most useful. I am hoping that there is some tooling for generating register and IP block definitions (from .h files perhaps?) Or is there an ARM standard for doping this?
Here is the %&**(&(*()* bug. If you configure a project by hand the vgdbsettings file contains an invalid XML attribute (!). See example below on how to correct. This now works. Praise the gods the configurations are not proprietary binary formats …C++123456789<keyvalue><br /><key>com.sysprogs.jlink.targetdevice</key><br /><!--<br /><value>$$SYS:MCU_ID$$</value><br />--><br /><value>VF6xx_A5</value><br /></keyvalue><br />
I am doing some work with Freescale Vybrid VF50/VF60 boards. it would be great if there was some basic support for these in the Freescale device lists.
More generally, is there any documentation on adding a new Wizard configuration? The ‘developing for legacy ARM devices’ tutorial is useful but it would be good to have a really consistent, repeatable, way of setting up a project.
Merged with another topic about making custom BSPs
My broadband connection can be terrible, and it is slightly annoying to have to wait for VS to become available for use … no biggie. I’ve other things in mind that I’d prefer to see first 😀
right Vendor ID but has a Device ID of 374B
Is this one of the ST Nucleo boards with mbed support etc? If so try ditching the ST drivers etc. completely and use Zadig to install a WinUSB driver for the board.
OpenOCD 0.8 does support STLink V2.1. Not sure if this has yet made it into the VGDB builds?
Thanks. I will check this out when I get a moment.
Possible solution: Ensure all STLink software is removed and Zadig used to install a WinUSB driver. I am now able to debug from VS2012 as expected.
1 question arising:
What does this mean ? KARL – should read back as 0x03, not 60 02 00 00
VisualGDB program output console shows:C++1234567892014-08-03T15:25:22 INFO src/stlink-common.c: Loading device parameters....2014-08-03T15:25:22 INFO src/stlink-common.c: Device connected is: F42x and F43x device, id 0x100364192014-08-03T15:25:22 INFO src/stlink-common.c: SRAM size: 0x30000 bytes (192 KiB), Flash: 0x200000 bytes (2048 KiB) in pages of 16384 bytesChip ID is 00000419, Core ID is 2ba01477.Target voltage is 2859 mV.Listening at *:4242...KARL - should read back as 0x03, not 60 02 00 00GDB connected.cannot recv: -2
Some more background on this problem.
I have installed OpenOCD 0.8 for Windows (using the Chopin package).
I have uninstalled the STLink drivers.
Zadig to install up a WinUSB driver for the 429 Discovery board.
In a nutshell, then connection between the various tools when running from shells on Windows appears to connect and respond correctly.
Question for Sysprogs: Are you using the same version of OpenOCD or have you got some custom build?
N.B. openocd-x184.108.40.206.exe renamed openocd.exe for simplicity!
R:appsopenocd>openocd -f ./scripts/board/stm32f429discovery.cfg ./scripts/interface/stlink-v2.cfgC++12345678910Open On-Chip Debugger 0.8.0 (2014-04-28-08:42)Licensed under GNU GPL v2For bug reports, readhttp://openocd.sourceforge.net/doc/doxygen/bugs.htmlsrst_only separate srst_nogate srst_open_drain connect_deassert_srstInfo : This adapter doesn't support configurable speedInfo : STLINK v2 JTAG v19 API v2 SWIM v0 VID 0x0483 PID 0x3748Info : using stlink api v2Info : Target voltage: 2.862077Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
Then from a shell run telnet localhost 3333C++12Info : accepting 'gdb' connection from 3333Error: attempted 'gdb' connection rejected
Then run arm-eabi-gdb from the sysprogs installation folder:C++1234567GNU gdb (GDB) 7.6.1Copyright (C) 2013 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later <http: //gnu.org/licenses/gpl.html><br />This is free software: you are free to change and redistribute it.<br />There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />and "show warranty" for details.<br />This GDB was configured as "--host=i686-pc-mingw32 --target=arm-eabi".</http:>
Connect via GDBC++1234gdb) target remote localhost:3333Remote debugging using localhost:33330x00000000 in ?? ()(gdb)
OpenCOD shell shows:C++12345Info : accepting 'gdb' connection from 3333Info : device id = 0x10036419Warn : STM32 flash size failed, probe inaccurate - assuming 2048k flashInfo : flash size = 2048kbytesundefined debug reason 7 - target needs reset
GDB:C++12345gdb) monitor reset inittarget state: haltedtarget halted due to debug-request, current mode: ThreadxPSR: 0x01000000 pc: 0x080eccd0 msp: 0x2002e8a0(gdb)
OpenOCD:C++1234target state: haltedtarget halted due to debug-request, current mode: ThreadxPSR: 0x01000000 pc: 0x080eccd0 msp: 0x2002e8a0
I suspect this article will help: