Hi,
The internal IPs evolve over time SPIv2 is for F0 and F3 devices, F4 has still SPIv1. Probably you are right about paths, more need fixing, I will do that tomorrow (1 minute to fix, 2 hours to open tickets, test and stuff...).
You just have to replace the chibios folder with a checkout from trunk.
Giovanni
ChibiStudio preview
-
Giovanni
- Site Admin
- Posts: 14892
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
-
Giovanni
- Site Admin
- Posts: 14892
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: ChibiStudio preview
Hi,
I am unable to reproduce the problem, the paths are correct and the demo compiles here. Try unzipping ChibiStudio again.
Giovanni
I am unable to reproduce the problem, the paths are correct and the demo compiles here. Try unzipping ChibiStudio again.
Giovanni
Re: ChibiStudio preview
OK, I think I figured this out....
I have a project that I am working on using ver2..
renamed version 2 of ...studio to get it out of the way...
unzipped version 3. into c:\
loaded up project into Working Set and tried to compile..
make: *** No rule to make target `C:\ChibiStudio\chibios/os/hal/platforms/STM32/spi_lld.c', needed by `build/obj/spi_lld.o'.
After Giovanni could not reproduce the problem, I looked a lot closer to see what I missed.
After several hours of searching I discovered an odd line in the .dep directory in my project directory.
It seems that this file contained a cached build file of some sort.
I finally deleted the contents of the .dep directory, and EVERYTHING WORK FINE!!! YIPPEE!!
I also found that if you delete the LST and OBJ directories in the BUILD directory of the project,
things will not go well.... Eclipse and yagarto will not create these directories for you.
If you do a 'clean project', it will delete the BUILD directory, then rebuild them for you. This has not
always been the case.
--John Scott
I have a project that I am working on using ver2..
renamed version 2 of ...studio to get it out of the way...
unzipped version 3. into c:\
loaded up project into Working Set and tried to compile..
make: *** No rule to make target `C:\ChibiStudio\chibios/os/hal/platforms/STM32/spi_lld.c', needed by `build/obj/spi_lld.o'.
After Giovanni could not reproduce the problem, I looked a lot closer to see what I missed.
After several hours of searching I discovered an odd line in the .dep directory in my project directory.
It seems that this file contained a cached build file of some sort.
I finally deleted the contents of the .dep directory, and EVERYTHING WORK FINE!!! YIPPEE!!
I also found that if you delete the LST and OBJ directories in the BUILD directory of the project,
things will not go well.... Eclipse and yagarto will not create these directories for you.
If you do a 'clean project', it will delete the BUILD directory, then rebuild them for you. This has not
always been the case.
--John Scott
Re: ChibiStudio preview
I got exact the same error trying to debug with ST-Link GDB Server 1.7.3.
As the client tries to connect, the server stops and I get an error in Eclipse.
Can someone zip me the version 1.5.6 and upload it somewere that I can try if it is the only problem that ST applied a lock?
Maby someone has some version inbetween that works.
Would be nice if someone helps me tracking this down.
Best regards
Stomper
As the client tries to connect, the server stops and I get an error in Eclipse.
Abhishek wrote:I'm using Atollic GDB Server 1.5.6 and it works fine.
Is it the case that latest Atollic GDB servers contain a lock-in to Atollic TrueStudio IDE?...
Can someone zip me the version 1.5.6 and upload it somewere that I can try if it is the only problem that ST applied a lock?
Maby someone has some version inbetween that works.
Would be nice if someone helps me tracking this down.
Best regards
Stomper
-
Giovanni
- Site Admin
- Posts: 14892
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: ChibiStudio preview
Hi,
What is the need to do that? OpenOCD now works well with ST-Link and supports all STM32s. The latest working Atollic server does not support F3 devices.
Giovanni
What is the need to do that? OpenOCD now works well with ST-Link and supports all STM32s. The latest working Atollic server does not support F3 devices.
Giovanni
Re: ChibiStudio preview
Mmm,
maby there is no need, but I am interested in finding out what the problem is/was.
If you think like this you also can ask: What is the need of an Porsche 911
if a Skoda also gets you from A to B...
but there are a lot of people who want the Porsche for personal reasons.
So I am just interested in getting it to work.
Best regards
Stomper
maby there is no need, but I am interested in finding out what the problem is/was.
If you think like this you also can ask: What is the need of an Porsche 911
if a Skoda also gets you from A to B...
but there are a lot of people who want the Porsche for personal reasons.
So I am just interested in getting it to work.
Best regards
Stomper
Re: ChibiStudio preview
Wanted to get OpenOCD 0.7.0 to work on Windows 7 x64 but I cant get it to run.
I tried to use zadig v2.0.1.160 to change the driver from the ST-Link of the VL Discovery Board, but as I click on "List all Devices" zadig crashes with an ntdll.dll error.
I tried for about an hour to get it to work, but without success.
So if someone would be so kind to upload a working ST-Link GDB Server, that would be nice.
Best regards
Stomper
I tried to use zadig v2.0.1.160 to change the driver from the ST-Link of the VL Discovery Board, but as I click on "List all Devices" zadig crashes with an ntdll.dll error.
I tried for about an hour to get it to work, but without success.
So if someone would be so kind to upload a working ST-Link GDB Server, that would be nice.
Best regards
Stomper
Re: ChibiStudio preview
I just downloaded ChibiStudio. Any reason why there's no STM32F1xx Board Configuration template in the new configuration wizard?
Also, there aren't any options for "Target Platform" in the New Application Project Wizard.
Should I still import an example to have a fully working project?
And finally, is there any better, graphical way to select peripherals? An idea would be to have something like CooCox's CoSmart (screenshot: http://www.coocox.org/images/CoSmart/CoSmart_Screenshot.png) to easily detect peripheral/pin conflicts.
Also, there aren't any options for "Target Platform" in the New Application Project Wizard.
Should I still import an example to have a fully working project?
And finally, is there any better, graphical way to select peripherals? An idea would be to have something like CooCox's CoSmart (screenshot: http://www.coocox.org/images/CoSmart/CoSmart_Screenshot.png) to easily detect peripheral/pin conflicts.
Re: ChibiStudio preview
I just downloaded ChibiStudio. Any reason why there's no STM32F1xx Board Configuration template in the new configuration wizard?
Also, there aren't any options for "Target Platform" in the New Application Project Wizard. Should it be like that?
Should I still import an example to have a fully working project?
And finally, is there any better, graphical way to select peripherals? An idea would be to have something like CooCox's CoSmart (screenshot: http://www.coocox.org/images/CoSmart/CoSmart_Screenshot.png) to easily detect peripheral/pin conflicts.
Also, there aren't any options for "Target Platform" in the New Application Project Wizard. Should it be like that?
Should I still import an example to have a fully working project?
And finally, is there any better, graphical way to select peripherals? An idea would be to have something like CooCox's CoSmart (screenshot: http://www.coocox.org/images/CoSmart/CoSmart_Screenshot.png) to easily detect peripheral/pin conflicts.