This PR adds minimal HW test projects using the embot environment for the ems , the mc4plus and the amc boards.
The projects can be used as template / demonstrators for developing / testing new HW device drivers.
Description
The most recent boards use the embot environment and new code will be strongly preferred to be in C++ and to run in this environment.
So, it is normal that the HW test project for instance of the amc uses the embot environment. But is useful that also the ems and the mc4plus can use the embot features.
So, this PR adds some simple test programs for the ems and mc4plus that run the embot environment. The embot::hw layer runs on top of the legacy hal2.ems4rd.ethdbg.lib and hal2.mc4plus.ethdbg.lib hardware abstraction layer libraries. And then, the embot::os layer runs as usual.
As a result, the test projects on the three boards all share a common environment to explore some topics that may be of interest.
They all launch a periodic thread called tTEST that can init some HW module and then tick it regularly. The details of what each board does are in the following.
The mc4plus test project uses the HAL motor driver to impose a PWM to a motor and to read back the generated current. That can be the starting point for a beginner to understand how the TIM peripherals work to impose PWM and to retrieve ADC readings (such as the induced motor current) that are synchronized w/ the PWM.
The ems test project demonstrates CAN communication using the HAL driver in a manner similar to what happens in the control loop. The CAN frames are received in the background and are parsed all together periodically at each tick. After that, the outgoing CAN frames are sent to the channel.
The amc test project demonstrates CAN communication using the embot::hw::can driver and also how to configure the object embot::app::eth::theErrorManager to redirect its messages onto the CAN channel. That can be the starting point for instance to implement / test HW embot drivers for new high resolution SPI encoders.
Tests
All the projects have been tested using an ULINK Pro and an STlink. They work fine. I just attach a simple printscreen.
Figure. The tTEST thread flushes 8 CAN frames to the channel and we can see the 8 execution of the CAN IRQHandler FDCAN1_IT0.
Mergeability
This PR does not change any feature, it just adapts the mandatory embot::hw drivers so that they can work on top of hal2. So, it can be safely merged.
This PR adds minimal HW test projects using the
embotenvironment for theems, themc4plusand theamcboards. The projects can be used as template / demonstrators for developing / testing new HW device drivers.Description
The most recent boards use the
embotenvironment and new code will be strongly preferred to be in C++ and to run in this environment.So, it is normal that the HW test project for instance of the
amcuses theembotenvironment. But is useful that also theemsand themc4pluscan use theembotfeatures.So, this PR adds some simple test programs for the
emsandmc4plusthat run theembotenvironment. Theembot::hwlayer runs on top of the legacyhal2.ems4rd.ethdbg.libandhal2.mc4plus.ethdbg.libhardware abstraction layer libraries. And then, theembot::oslayer runs as usual.As a result, the test projects on the three boards all share a common environment to explore some topics that may be of interest.
They all launch a periodic thread called
tTESTthat can init some HW module and then tick it regularly. The details of what each board does are in the following.mc4plustest project uses the HAL motor driver to impose a PWM to a motor and to read back the generated current. That can be the starting point for a beginner to understand how the TIM peripherals work to impose PWM and to retrieve ADC readings (such as the induced motor current) that are synchronized w/ the PWM.emstest project demonstrates CAN communication using the HAL driver in a manner similar to what happens in the control loop. The CAN frames are received in the background and are parsed all together periodically at each tick. After that, the outgoing CAN frames are sent to the channel.amctest project demonstrates CAN communication using theembot::hw::candriver and also how to configure the objectembot::app::eth::theErrorManagerto redirect its messages onto the CAN channel. That can be the starting point for instance to implement / test HWembotdrivers for new high resolution SPI encoders.Tests
All the projects have been tested using an
ULINK Proand anSTlink. They work fine. I just attach a simple printscreen.tTESTthread flushes 8 CAN frames to the channel and we can see the 8 execution of the CAN IRQHandlerFDCAN1_IT0.Mergeability
This PR does not change any feature, it just adapts the mandatory
embot::hwdrivers so that they can work on top ofhal2. So, it can be safely merged.