ChibiStudio Problems

[fribo]

Hi,

I've developed some projects with Atmel 8bit processors, so far.
I'm feeling, it is time to change to ARM, now.

So, I've bought "STM32F051-Discovery" and also "STM32F4i-Discovery".
For first test the STM32F0 was selected.

I've tested the CooCox IDE, and it runs successfully, without problems under Win7.
But I think, to change to "ChiBios" instead, because of the Graphic support,
when I'm changing to my STM32F4... later.

So, I tried "ChiBiStudio".
But, I'm disappointed, because it seems to be just a "Hacker-Tool".

When I'm only trying to use the pre-configured projects for my board "STM32F051-Discovery", I could build it without failures.
But, when I'm trying to debug, all runs into hell.
I've installed the driver for USB from STM.
Anyway, all this doesn't work here as installed.

I would expect an IDE for ChiBios+Graphics that runs flawlessly for the delivered Example Projects, including all ST stuff.
I'm not very interested to find out the deep details of ChiBiosStudio or Eclipse.
I just want to use it for my projects...

The IDE should simply work after installation (see CooCox IDE) !

Is there any good documentation for this?
I googled around, but didn't find any good...

No, install this and that is not the solution.
How about a batch file, that makes all running?
(for example for the ST-Dicovery-Boards)

BR, fribo

[jscott]

...all runs into hell

... is not a very technical description ....

Can you provide some more detailed information....

... say a error message?

... or better yet a screen print would help provide us an idea just what is going on.

otherwise perhaps someone can recommend a good exorcist....

Most development tools will require you to learn quite a bit about them to
get the best use out of them. I have been using ChibiStudio since version 1,
and have not had much trouble with it.

Give us some details and someone is very likely to be able to help you figure
out what is wrong.

-John Scott

[enly1]

Yeah - let us know what doens't work and i'm sure there will be help forthcoming - Chibistudio is pretty good (if not perfect) if your're using chibios... The biggest issues I have with it are EClipse issues and not ChibiStudio related.

Debug was the biggest challenge I had (any ide), but working perfectly in the ChibioSudio s6 preview without any fiddling...

Give this a try ... (asuming you're using the onboard debugger on the discovery board)

ChibioStudio 6,
open project,
build,
run openocd stlink2 (External Tools), when prompted for filename - give it C:\ChibiStudio\tools\openocd\scripts\target\stm32f0x_stlink.cfg (assuming you're debugging on discovery board stlink).
Launch Debug Config : ARMCM0-STM32F051-DISCOVERY (OpenOCD, Flash and Run) (from debug dropdown next to play symbol)- or run|debug configurations, select that config and click debug.
Keep Fingers crossed you should program board and pop up with a breakpoint in main.

The F0 uses the F1 debug configs, which is what i'm using,so the logic above should be pretty close, but I don't have one of those boards, so can't check.

[fribo]

Hi jscott and enly1,

Thanks a lot for your reply.

I must admit, that I was desperate about ChibiStudio when I've written that post.
Especially in debugging nothing works as I like.

Meanwhile, I've tested the TEXANE gdb server (27.12.2012) with ChibiStudio succesfully.
It flashes the board and I can see the green and blue LEDs blinking.
Unfortunately, it works only once. And I don't know why.

When I tried this again, I've got error messages like
- Binary not found (ch.elf) // What binary? No detailed error. The "ch.elf" is in place.
- Application doesn't run

These error messages doesn't help much. What binary, what application?

Another question is, how to deal with the "ST-Link Utility" by STM.
I can always connect to the board using this.
And I think this must be started once and "connect target", then leave the prog in order to keep ChiboStudio work.

I would really appreciate your help.

BR, fribo

[enly1]

For me and openOCD, stlink utility must not be started - because it connects to taregt fine if you launch ST-LINK but it locks the stlink,so openocd cannot control it.

So my workflow was as I wrote above.

I'm using stlink + Chibistudio unchanged ...