Unterstützung #82
Von Maximilian Seesslen vor mehr als 2 Jahren aktualisiert
The bringup software should be able to easily test periphery.
CANIO already has some test routines. They should be available in general.
Move them to a tests.cpp. No Arena stuff.
Having an test-class could help to make some overall information.
testSpiFlash( pPlatform->m_spi );
testSpiLoopback( pPlatform->m_spi );
testI2cEeprom( pPlatform->m_i2c, bottom=true );
testInternFlash( );
testCan( ECanSpeed, ECanTest::ExternLoopback/ECanTest::Mirror );
The test routines should not be in the biwak periphery clases. There will be some assumptions or depencies.
Just use functions or a seperate test class.
Those tests will also provide units-tests for biwak itself.
The fosh commands for i2c and sf are waste of space for regular use.
CANIO already has some test routines. They should be available in general.
Move them to a tests.cpp. No Arena stuff.
Having an test-class could help to make some overall information.
testSpiFlash( pPlatform->m_spi );
testSpiLoopback( pPlatform->m_spi );
testI2cEeprom( pPlatform->m_i2c, bottom=true );
testInternFlash( );
testCan( ECanSpeed, ECanTest::ExternLoopback/ECanTest::Mirror );
The test routines should not be in the biwak periphery clases. There will be some assumptions or depencies.
Just use functions or a seperate test class.
Those tests will also provide units-tests for biwak itself.
The fosh commands for i2c and sf are waste of space for regular use.