[GitHub] [nuttx] acassis commented on issue #8017: Create a Software Qualification Testing for Release new versions

[GitBox <gi...@apache.org>]

acassis commented on issue #8017:
URL: https://github.com/apache/nuttx/issues/8017#issuecomment-1369745316

   Hi @btashton very nice! I think we could create a listing of features to test for each peripheral to guarantee the driver is working. Recently I discovered that SSD1306 wasn't working on ESP32 because the I2C driver doesn't support NOSTOP feature. My idea is something like this:
   
   Qualification Test
   ==============
   
   1) GPIO
   - Check if GPIO pins can work as Output, Input
   - Check if GPIO Input can generate interrupts
   - Check if GPIO can work in Open Drain mode 
   2) UART
   - Check if the NSH console can start on selected UART (case MCU has 2 or more UARTs, test on others too)
   - Check if UART can exchange data with other boards/devices, to exercise higher throughput, different baudrates and parity modes, etc
   - Check if RS485 (Modbus) works on that UART ports
   3) I2C
   - Check if I2C can send a byte (to some I2C DAC that receives only a byte by time)
   - Check if I2C can send block of bytes (to some I2C Display like SSD1306)
   - Check if I2C can receive a byte per transaction (some sensor)
   - Check if I2C can receive a block of bytes
   ...
   
   It is not easy to automate these tests, maybe a FPGA board that use some standard connector pinout (i.e. like Raspberry Pi pinout) should be necessary to do it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org