I'm Vincenzo from UninaCorse E-Team, a Formula Student team. We are developing an electric racing car, with in-wheel motors.
Today we decided to start developing using ChibiOS!
The decision was not easy, we evaluated many other solutions: mbedOS, FreeRTOS, Zephyr, CubeMX+HAL (without an RTOS). But ChibiOS looks like the smallest and fastest RTOS on the market. With its speed we can respect the safety requirements of the competition, and we can implement the algorithms to manage the 4 motors. The smallness is important because we are going to use only two Nucleo Board (STM32F446RE).
The developing of the firmware don't start today, we had developed a lot of demo (without an RTOS) to test the single systems of the car. But today we must put everything together, and what a better way than using ChibiOS?
We know that the firmware developing doesn't start from the code, but from its architecture. We are going to evaluate design tools like UML, and its derivatives SysUML and MARTE. Really, these 2 last tools are useful for describing a complete system (hardware + software), but the hardware part was quite ready and we don't want to lose time translating what we have done, so we want only to describe the behaviour of the firmware (software). Do you have any tips about this choice? MARTE and SysUML are useful for our needs?
Wish us good luck!
Cheers from all the UninaCorse E-Team members
This forum is about you. Feel free to discuss anything is related to embedded and electronics, your awesome projects, your ideas, your announcements, not necessarily related to ChibiOS but to embedded in general. This forum is NOT for support.
2 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest