Hope you are able to debug it now.
For using openOCD, select your project from the left hand side project window. It should work.
ChibiStudio preview
Re: ChibiStudio preview
Abhishek and all,
Got it working with OpenOCD. Took a while to figure out what config
file I had to select.
Turns out it is
in case anyone else is struggling with this...
Thanks everyone for your help!!
-John
Got it working with OpenOCD. Took a while to figure out what config
file I had to select.
Turns out it is
C:\ChibiStudio\tools\openocd\scripts\board\stm32f4discovery.cfg
in case anyone else is struggling with this...
Thanks everyone for your help!!
-John
Re: ChibiStudio preview
Ok, looks like I have gotten things working thanks to all the help here...
Now for my next request... ( you knew that was coming, right? )
In order to deal with version control and backups, I would like to move
my development
What I would like is something like this...
From what I have read, it seems I should be able to create a new workspace in the STM32 directories
( such as c:\projects\client1\projectname\stm32 ). What I can't figure out is how to convince ChibiStudio
to work with this setup...
Thanks
-John
Now for my next request... ( you knew that was coming, right? )
In order to deal with version control and backups, I would like to move
my development
What I would like is something like this...
c:\projects
-------------/client1
----------------------/projectname
--------------------------------/stm32
--------------------------------/avr
-------------/client2
----------------------/projectname2
--------------------------------/stm32
--------------------------------/avr
-------------/client3
----------------------/projectname3
--------------------------------/stm32
--------------------------------/avr
From what I have read, it seems I should be able to create a new workspace in the STM32 directories
( such as c:\projects\client1\projectname\stm32 ). What I can't figure out is how to convince ChibiStudio
to work with this setup...
Thanks
-John
- 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,
You can put projects everywhere on the file system not necessarily under the workspace, you can use the existing workspace and just import the projects.
You could then create a "working set" for each client in order to have them visually well organized in Eclipse.
Giovanni
You can put projects everywhere on the file system not necessarily under the workspace, you can use the existing workspace and just import the projects.
You could then create a "working set" for each client in order to have them visually well organized in Eclipse.
Giovanni
Re: ChibiStudio preview
What would be involved in adding the size command to the tail end of the build process?
It would be nice to know how big the project is for those times I do something really dumb and
allocate way too much memory...
-John
It would be nice to know how big the project is for those times I do something really dumb and
allocate way too much memory...
-John
- Giovanni
- Site Admin
- Posts: 14892
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: ChibiStudio preview
You have to modify rules.mk and add the command there. you can copy it into the project and then refer the copy from the Makefile.
Giovanni
Giovanni
Re: ChibiStudio preview
Hi,
I have difficulties setting up Segger J-Link to work with eclipse (STM32-E407 demo and chibistudio). Can someone help me ?
Thanks,
Todor
I have difficulties setting up Segger J-Link to work with eclipse (STM32-E407 demo and chibistudio). Can someone help me ?
Thanks,
Todor
Re: ChibiStudio preview
I was thinking, if next release of ChibiStudio onwards, could the bundled chibios folder may please be provided as a cloned git repository from the github upstream, so that it is as easy as a command to get the latest version, and also to switch release tags? I guess it would really be helpful and convenient for developers as well as users to get the latest stable / development version of the OS as they like. @Giovanni, what do you think?
Also, OpenOCD 0.6.1 bug fix release is coming soon. I think with that release, maybe we could apply mabl's patch for ChibiOS debugging (which should hopefully be ready soon) to it and provide our own customized version with the ChibiStudio bundle? I guess it would be the perfect time for the next release of ChibiStudio.
Best Regards
Abhishek
Also, OpenOCD 0.6.1 bug fix release is coming soon. I think with that release, maybe we could apply mabl's patch for ChibiOS debugging (which should hopefully be ready soon) to it and provide our own customized version with the ChibiStudio bundle? I guess it would be the perfect time for the next release of ChibiStudio.
Best Regards
Abhishek
- 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 just uploaded version 3 of ChibiStudio, it includes updated compiler, OCD 0.7.0dev (supporting ChibiOS) and ChibiOS 2.5.1. Support for Atollic GDB server removed.
Giovanni
I just uploaded version 3 of ChibiStudio, it includes updated compiler, OCD 0.7.0dev (supporting ChibiOS) and ChibiOS 2.5.1. Support for Atollic GDB server removed.
Giovanni
Re: ChibiStudio preview
Giovanni,
I upgraded to version 3 of the chibios studio and got the following error...
make: *** No rule to make target `C:\ChibiStudio\chibios/os/hal/platforms/STM32/spi_lld.c', needed by `build/obj/spi_lld.o'.
I don't see anything in my project that may cause this and it works fine in V2. I saw this in the changelog:
- FIX: Fixed wrong SPI path in platform_f105_f107.mk (bug 3598151).
I wonder if it need fixing in the stm32f4 version also????
Also, is there somewhere that you document the different versions of drivers? Such as SPIv1 and SPIv2
If not, maybe a txt file in the different versions that specify the differences in the different drivers.
Thanks
-John
I upgraded to version 3 of the chibios studio and got the following error...
make: *** No rule to make target `C:\ChibiStudio\chibios/os/hal/platforms/STM32/spi_lld.c', needed by `build/obj/spi_lld.o'.
I don't see anything in my project that may cause this and it works fine in V2. I saw this in the changelog:
- FIX: Fixed wrong SPI path in platform_f105_f107.mk (bug 3598151).
I wonder if it need fixing in the stm32f4 version also????
Also, is there somewhere that you document the different versions of drivers? Such as SPIv1 and SPIv2
If not, maybe a txt file in the different versions that specify the differences in the different drivers.
Thanks
-John