Open trns1997 opened 7 months ago
@leducp @Rdk-T i would like your input regarding how to efficiently integrate KickCat. Let us take the arduino due with the lan92 shield. If we follow the nuttx driver convention, then the lan92 driver should be in nuttx, which means that slave stack would communicate with the shield via /dev/lan92
file probably. But in the case of our POC in KickCat we have the driver integrated here which uses the spi driver from nuttx. Both approaches work but i was wondering if KickCat should be the one responsible to provide drivers? From what i see:
lan92-ethercat-example
ethercat-example
/dev/ethercat
/dev/ethercat
file and use that as the driver to do it's ethercat stuffEach case has it's pros and cons. I have a hard time figuring out which approach it better, in case 1 we will have to pass a variable to Kickcat to tell it what driver to use or we end up with different apps based on the driver/board we choose. In case 2 we can have a single example which exploits the nuttx driver provided called something generic like /dev/ethercat
and what ever board we choose as long as we provided the driver with the right name it will work ideally. Let me know what you guys think.
I prefer to handle the case 1: the KickCAT codebase is more generic this way. Note that it can be useful to have the case 2, but it is more work since it means:
I think we just don't have the manpower to handle this (case 2).
Create a simple nuttx ethercat app using kickcats slave stack.