[G40]

[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 …

[G40]

dmesg shows this:

netpoll: kgdboe: eth0 does not support polling. aborting.

currently running mint with the 3.16.0.34 kernel if that helps.

wonder if this is the reason: http://askubuntu.com/questions/139314/netconsole-error-eth0-doesnt-support-polling

Thx++

[G40]

Please ignore this. I loaded up the Portable 3.4 version which works just fine.

 

Great stuff. thanks you.

[G40]

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.

[G40]

Thanks Bazis I will put this on my todo list

[G40]

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?

Many thanks.

[G40]

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 …

com.sysprogs.jlink.targetdevice



VF6xx_A5

[G40]

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.

Thanks again.

Merged with another topic about making custom BSPs

[G40]

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 😀

[G40]

@rraab wrote:

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.

Good luck.

[G40]

Hello Chaps,

OpenOCD 0.8 does support STLink V2.1. Not sure if this has yet made it into the VGDB builds?

[G40]

Hello Bazis

Thanks. I will check this out when I get a moment.

[G40]

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:

2014-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 0x10036419
2014-08-03T15:25:22 INFO src/stlink-common.c: SRAM size: 0x30000 bytes (192 KiB), Flash: 0x200000 bytes (2048 KiB) in pages of 16384 bytes
Chip 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 00
GDB connected.
cannot recv: -2

Zadig: http://zadig.akeo.ie/

[G40]

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-x64.0.8.0.exe renamed openocd.exe for simplicity!

R:appsopenocd>openocd -f ./scripts/board/stm32f429discovery.cfg ./scripts/interface/stlink-v2.cfg

Open On-Chip Debugger 0.8.0 (2014-04-28-08:42)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : This adapter doesn't support configurable speed
Info : STLINK v2 JTAG v19 API v2 SWIM v0 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 2.862077
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints

Then from a shell run telnet localhost 3333

Info : accepting 'gdb' connection from 3333
Error: attempted 'gdb' connection rejected

Then run arm-eabi-gdb from the sysprogs installation folder:

GNU gdb (GDB) 7.6.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.  Type "show copying"

and "show warranty" for details.

This GDB was configured as "--host=i686-pc-mingw32 --target=arm-eabi".

Connect via GDB

gdb) target remote localhost:3333
Remote debugging using localhost:3333
0x00000000 in ?? ()
(gdb)

OpenCOD shell shows:

Info : accepting 'gdb' connection from 3333
Info : device id = 0x10036419
Warn : STM32 flash size failed, probe inaccurate - assuming 2048k flash
Info : flash size = 2048kbytes
undefined debug reason 7 - target needs reset

GDB:

gdb) monitor reset init
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x080eccd0 msp: 0x2002e8a0
(gdb)

OpenOCD:

target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x080eccd0 msp: 0x2002e8a0

[G40]

I suspect this article will help:

http://stm32discovery.nano-age.co.uk/open-source-development-with-the-stm32-discovery/getting-newlib-to-work-with-stm32-and-code-sourcery-lite-eabi

BR.

Jerry

[Author]

Posts