ChibiStudio preview 6

[Giovanni]

You can already use 3.0, just create another workspace and import the demos, make the variable CHIBIOS point to the 3.0 directory.

Anyway, it will be included in preview 7.

Giovanni

[Korken]

I mean in the debug mode, currently it says that no ChibiOS was detected.

[Giovanni]

There is a specific viewer for ChibiOS 3.0, you have to open it.

Giovanni

[Korken]

Ahhh! Thank you!

[enly1]

Just wanted to say a quick thankyou for this release.....

I've setup Chibios and Eclipse in the past and used Chibistudio Preview 5 after that (with large amounts of sucess,although never got debugging working properly), but with this release everything is working absolutely perfectly (well 99.9%).

Chibios Rocks !!!

Simon

[enly1]

Giovanni,

We appear to have a slight issue with the preview release in relation to the make functionality.

I'm running the latest release and depending on my choice of start.bat or start2.bat the ability to make clean works or doesn't.

Using start2 it creates the directory structure for the build - i.e. obj/map and compiles. If launched from start.bat it removes the directories as part of clean, but doesn't recreate them so the compile fails.

My makefile was ported from an earlier demo makefile and was used with the previous preview fine ( and obviously works with one of the toolchains )

Happy to supply it if it will help, but expect it will be easy to reproduce.

Thanks

Simon

[Giovanni]

Thanks, probably there is a wrong path in start2.bat.

Giovanni

[enly1]

Hi - don't think its the paths.

I have a suspicion it was simply that I had a process holding open the build directory when I did the clean. If it can't remove the build folder, but can remove the sub folders, next time through the build fails as it didn't recreate the map/obj folders. Deleting the build directory and new build worked.

Probably released the directory between instance swaps ?

I would forget about it unless someone else shouts....

[protobit]

I ran a quick benchmark with the default toolchain vs Bleeding Edge toolchain. Attached are the results.

Setup:
I cleaned/compiled a couple demo projects in Chibistudio with various compiler settings:
ARMCM4-STM32F407-DISCOVERY
ARMCM4-STM32F407-DISCOVERY-G++
ARMCM4-STM32F407-DISCOVERY-MEMS

Rig:
AMD Phenom II P650 Dual-core 2.60GHz
Samsung 830 SSD

Conclusion:
Compile time and program size probably decreases while using Bleeding Edge toolchain. I can't speak of performance however.

[Giovanni]

Good work. you could easily see the performance too, just run the test suite, the last test cases in the report are all benchmarks and quite accurate.

Giovanni