[New] Side project: ChibiToolchain

[Giovanni]

Hi,

It is correct, I am curious to know why it does not work when launched from Eclipse, are you able to find out? I don't have a 64bit OS to test on. Is it possible you have to set some compatibility attribute to ChibiStudio to make it work?

Giovanni

[fgomes]

Hi Giovanni, is there any 'verbose' or enhanced log that can be activated to try to debug this openocd issue on 64 bit windows? I've tried to change the compatibility settings in some binaries but the result was the same (openocd both 32 and 64 bit version, eclipse). What is the openocd version that eclipse should try to use, 32 or 64 bit? If it is possible to make some debug please let me know, I'm willing to try it, but I'm no eclipse plugin expert

I also noticed that when starting openocd manually the debug session (sort of) works, both starting the 32 or 64 bit openocd binary. I notice that really trying to debug the program, things don't work so well, the "step over" and "step into" functions seems to step 'erractically' through the code. So there might be some other issues on the communication with the openocd server.

Fernando

[Giovanni]

Hi,

Add "-d3" to the openocd command line for an extended log. The 32bits version should work even in 64bits systems.

About the debug, it is because optimizations, use -O0 in the Makefile instead of -O2 if you want to debug.

Giovanni

[fgomes]

Hi, just to update about some stupid errors I made for others to avoid.

The main problem of having to run manually the openocd server is that I was expecting that the server was automatically started by the debug command, now I know that I have to run it using the external tools button

Second error I was making, since I wasn't able to use the "Flash and Run" option (error on the openocd server, perhaps due to the stlink firmware version), I was using "Run Only", but it seems to me that with this option it doesn't load any code to the target, am I right? After compiling with no optimization (-o0) the code debug still seems to be executing randomly, and since the stlink firmware update enabled the Flash programming I tried the "Flash and Run" option and now everything is running well.

I hope this information might be useful to avoid others to make the same errors

Fernando

[Giovanni]

Correct, "Flash and Run", loads the code in flash then executes it, "Run" just quickly restarts a previous session without touching the flash memory, it is useful if you want to restart a debug session.

Giovanni

[Abhishek]

I'm trying to use OpenOCD in ChibiStudio but I'm getting the following errors:

Code: Select all

Open On-Chip Debugger 0.6.0 (2012-09-07-10:48)
Licensed under GNU GPL v2
For bug reports, read
   http://openocd.sourceforge.net/doc/doxygen/bugs.html
adapter speed: 1000 kHz
Info : clock speed 1000 kHz
libusbx: warning [windows_get_device_list] '\\.\USB#VID_0461&PID_4DFA#5&540BBBE&0&1' was only detected in late pass (newly connected device?) - ignoring
libusbx: warning [windows_get_device_list] '\\.\USB#VID_0483&PID_3748#5&540BBBE&0&3' was only detected in late pass (newly connected device?) - ignoring
Error: open failed
in procedure 'transport'
in procedure 'init'

It occurs in both 32-bit and 64-bit versions. Even replacing the driver is of no use.

Any clues what's going on?

Best Regards
Abhishek

I'm using a Dell Laptop (i7 Ivy Bridge, HM77 express chipset with all USB ports USB 3.0) with preloaded 64-bit version of Windows 7 Home Premium.

[Giovanni]

Do you have ST-Link drivers installed? if so, you may try to run the 64bit openocd executable and see if it makes any difference.

Giovanni

[Abhishek]

I've tried with the 32-bit version and 64-bit versions of OpenOCD, but getting the same error in both.

Interestingly enough, the ST-LINK device comes in the warnings, but then isn't detected officially.

I first installed the default STLINK drivers. Then I replaced it with libusb drivers in the hope it might work, but then, the same output. No clue what's going on.

[Giovanni]

I am using it with the standard STLink drivers, OpenOCD uses already those passthrough drivers. Not sure why it is not working for you, probably you could ask in the OpenOCD forum about this.

Giovanni

[jcbarlow]

you could ask in the OpenOCD forum about this.

The OpenOCD forum on the Sparkfun site seems to have many unanswered questions these days. A better resource IMHO are the email lists that are now hosted on sourceforge.net

See <https://lists.sourceforge.net/lists/listinfo/openocd-user> and <https://lists.sourceforge.net/lists/listinfo/openocd-devel>