G40

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 19 total)
  • Author
    Posts
  • in reply to: insmod errors … #6464

    G40
    Participant

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

    in reply to: insmod errors … #6441

    G40
    Participant

    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++

    in reply to: Problems with eject (W7x64USP1) #6156

    G40
    Participant

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

     

    Great stuff. thanks you.

    in reply to: Debugging failed … ‘object reference not set’ #3382

    G40
    Participant

    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.

    in reply to: Atmel SAMA5 support? #3036

    G40
    Participant

    Thanks Bazis I will put this on my todo list

    in reply to: Atmel SAMA5 support? #3035

    G40
    Participant

    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.

    in reply to: Debugging failed … ‘object reference not set’ #3380

    G40
    Participant

    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 …

    in reply to: Atmel SAMA5 support? #3038

    G40
    Participant

    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

    in reply to: Minor feature request #3072

    G40
    Participant

    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 😀

    in reply to: ST-Link v2 device not found #3312

    G40
    Participant

    @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.

    in reply to: ST-Link v2 device not found #3311

    G40
    Participant

    Hello Chaps,

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

    in reply to: STM32 Discovery/STLinkV2/OpenOCD problems #3113

    G40
    Participant

    Hello Bazis

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

    in reply to: STM32 Discovery/STLinkV2/OpenOCD problems #3111

    G40
    Participant

    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:

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

    in reply to: STM32 Discovery/STLinkV2/OpenOCD problems #3110

    G40
    Participant

    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

    Then from a shell run telnet localhost 3333

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

    Connect via GDB

    OpenCOD shell shows:

    GDB:

    OpenOCD:

    in reply to: Linker Error on sprintf #3104

    G40
    Participant
Viewing 15 posts - 1 through 15 (of 19 total)