gs_usb: CAN - USB Adapter

[KozhinovAlexander]

Dear Zephyr RTOS community,

I was able to (re-)implement gs_usb CAN-Bus to USB adapter Firmware based in Zephyr RTOS, which (still in development) can be found here: https://github.com/KozhinovAlexander/zephyr/tree/gs_usb use following command to build:

west build -p auto -d <ZEPHYR_DIR>/samples/drivers/can/gs_usb/build -b nucleo_h745zi_q/stm32h745xx/m7 <ZEPHYR_DIR>/samples/drivers/can/gs_usb  -DDTC_OVERLAY_FILE=<ZEPHYR_DIR>/samples/drivers/can/gs_usb/nucleo_h745zi_q.overlay

GS_USB is a OpenMoko Geschwister Schneider CAN adapter system including Linux CAN-USB driver. It has also VID and PID from it.

The great thing about it, there is a pretty a lot of SW sub-projects doing:

1. Python support here
2. Linux SocketCAN driver support here
3. CandleLight bare metall FW here

and there are also a lot of STM32 based HW available:

1. candleLight from Linux Automation here
2. MKS Canable v2.0 here, can be found for a nice price on Ali-Express here

With my FW Zephyr RTOS based clone I have already all the funbctionality (except, find-my-device and generic support of multiple CAN-Endpoints).

What I plan to do? I need your advice and/or support in following questions:

1. How to handle licensing? Since Linux-Kernel driver is GPL-2.0 only, is it legitime for me to release my FW clone under Apache 2.0 within Zephyr RTOS?
2. Since my GS_USB is a FW clone implmenting a USB-Class, shall it be added to USB class sub -folder of Zephyr RTOS project or putted as a sample?

From my point of view the right persons to answer this questions may be @jfischer-no @henrikbrixandersen @martinjaeger @alexanderwachter If I putted falsily your name here, please let me know, I will remove it.

I will also be happy to get in touch if necessary and/or to discuss additions. Basically with some minor clean-ups I shall be ready release this work soon.

I appreciate your help. Thanks a lot.

[henrikbrixandersen]

I wish you had reached out before embarking on this. I have a fully functional, multi-endpoint gs_can implementation ready to be submitted after the current feature freeze ends.

[KozhinovAlexander]

I wish you had reached out before embarking on this. I have a fully functional, multi-endpoint gs_can implementation ready to be submitted after the current feature freeze ends.

Very good point. Well, I have no problem, you submit it and stay maintainer. I've gathered a lot of experience implementing my code and can support you and/or do a review, if you okay with it.
Would you like to submit your code s.t. we can join our forces?
I have already x2 MKS Canable v2.0 with stm32g4 from AliExpress and can create bsp for them too and of course test them. Nice thing about them - they're open hardware.

[henrikbrixandersen]

Awesome. I would really like to have your experienced eyes reviewing the implementation. I'll brush off the last documentation bits and pieces and ping you.

[KozhinovAlexander]

Awesome. I would really like to have your experienced eyes reviewing the implementation. I'll brush off the last documentation bits and pieces and ping you.

Great. I am happy to see it soon.
BTW: My implementation does not have twister tests at the moment. Does your's have it?

[henrikbrixandersen]

BTW: My implementation does not have twister tests at the moment. Does your's have it?

Only a basic console-based test scenario. The USB device class itself is better verified using the stress testing tools from Linux can-utils.

[KozhinovAlexander]

BTW: My implementation does not have twister tests at the moment. Does your's have it?

Only a basic console-based test scenario. The USB device class itself is better verified using the stress testing tools from Linux can-utils.

Sounds plausible. In my branch above you can also find a bash script for cyclic can message sending with can-utils, fyi.