Do you still have problems with OpenOCD and STLINKv1/2 ?
It seems that a new release candidate is out and they claim that it supports STLink, actually there is a .cfg specially for the discovery board.
[New] Side project: ChibiToolchain
- Giovanni
- Site Admin
- Posts: 14892
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: [New] Side project: ChibiToolchain
Hi,
I am using the RC1 too on Linux without problems, very fast and stable with both ST-Link V1 and V2 (even if you have to configure USB stuff and this is a bit complex, probably I should add a specific guide about this).
I still have to try it on Windows using that pass-through driver, if it works I will assemble a new ChibiStudio with the latest components.
Giovanni
I am using the RC1 too on Linux without problems, very fast and stable with both ST-Link V1 and V2 (even if you have to configure USB stuff and this is a bit complex, probably I should add a specific guide about this).
I still have to try it on Windows using that pass-through driver, if it works I will assemble a new ChibiStudio with the latest components.
Giovanni
Re: [New] Side project: ChibiToolchain
http://openocd.sourceforge.net/
0.6 is now officially released and supports STlink1/2
The list of changes is on the website.
0.6 is now officially released and supports STlink1/2
The list of changes is on the website.
- Giovanni
- Site Admin
- Posts: 14892
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: [New] Side project: ChibiToolchain
I am using ST-Link v1 and v2 under both Windows and Linux using 0.6.0, no problems so far. The setup under Linux is a bit complicated because permissions etc, probably I should add a guide.
Giovanni
Giovanni
Re: [New] Side project: ChibiToolchain
Hi Giovanni, very nice work! I have been 'struggling' for months to start something with my STM32F4 discovery board due to the needed setup for the tools (and not enough free time to do it also), and in a few minutes I have a working system using ChibiStudio. I had it working already with CooCox but it was much easier to make it work with the ChibiStudio 
One thing I didn't find in the forum or documentation was how to create a new project, what should be the best aproach for example to create a new project for the STM32F4 discovery board? Can you give me some clue of how to do it?
Fernando
One thing I didn't find in the forum or documentation was how to create a new project, what should be the best aproach for example to create a new project for the STM32F4 discovery board? Can you give me some clue of how to do it?
Fernando
- Giovanni
- Site Admin
- Posts: 14892
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: [New] Side project: ChibiToolchain
Hi,
The current way is to clone an existing project, remove in .project and .cproject files, then import it using the procedure described here: http://www.chibios.org/dokuwiki/doku.ph ... to_eclipse
I am working on an Eclipse plugin that will allow to create easily new projects, it will go in future ChibiStudio versions.
Giovanni
The current way is to clone an existing project, remove in .project and .cproject files, then import it using the procedure described here: http://www.chibios.org/dokuwiki/doku.ph ... to_eclipse
I am working on an Eclipse plugin that will allow to create easily new projects, it will go in future ChibiStudio versions.
Giovanni
Re: [New] Side project: ChibiToolchain
Thanks for your super fast reply. After importing the project it didn't apear on the project explorer, but if I try to import it again it says it already exists (overlaps the location of another project), do you know what did I make wrong? Thanks!
- Giovanni
- Site Admin
- Posts: 14892
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: [New] Side project: ChibiToolchain
The project is imported but you have to associate it to a working set, select "Properties" on one of the working sets you see in the left panel or create your own working set.
Giovanni
Giovanni
Re: [New] Side project: ChibiToolchain
Hi giovanni, thanks again for your help, it worked. Now I'm having a problem using the STM32F4 Discovery board, I can use it in this windows 7 64 bits PC with the ST tools and with CooCox but it was not working with ChibiStudio. After some atemps to try to solve this issue I found that if I run the openocd binary manually then I can use the debugger in ChibiStudio. I'm running it like that, in a console:
C:\ChibiStudio\tools\openocd>bin\openocd-0.6.0-rc2.exe -f interface/stlink-v2.cfg -f target/stm32f4x_stlink.cfg
Open On-Chip Debugger 0.6.0-rc2 (2012-08-29-09:22)
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
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection from 3333
Info : stm32f4x errata detected - fixing incorrect MCU_IDCODE
Info : device id = 0x10006413
Info : flash size = 1024kbytes
Warn : acknowledgment received, but no packet pending
undefined debug reason 6 - target needs reset
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08003364 msp: 0x20004e0c
Is this the correct way of doing it (starting manually openocd in a console), or am I doing something wrong?
Fernando
C:\ChibiStudio\tools\openocd>bin\openocd-0.6.0-rc2.exe -f interface/stlink-v2.cfg -f target/stm32f4x_stlink.cfg
Open On-Chip Debugger 0.6.0-rc2 (2012-08-29-09:22)
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
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection from 3333
Info : stm32f4x errata detected - fixing incorrect MCU_IDCODE
Info : device id = 0x10006413
Info : flash size = 1024kbytes
Warn : acknowledgment received, but no packet pending
undefined debug reason 6 - target needs reset
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08003364 msp: 0x20004e0c
Is this the correct way of doing it (starting manually openocd in a console), or am I doing something wrong?
Fernando