Re: can4linux for the BananaPi

Gentlemen,

It seems the discussion on Beagle Board & Co. is getting more interesting.

There are but a couple of questions to answer first.

I would appreciate if experienced can list users answer those to help me
understand the idea behind such boards.

What are the benefits of developing of a fully capable CAN/CANopen board
that works as an extention to a Beagle Board (as a cape) and its future
development as well as being capable to work as a stand alone CAN/CANopen
board?

Who is interested in that. A privat lab or rather an R&D of a company?

Will the board (as a cape) be able to support sophisticated CANopen
profiles such as motion control (CiA 402) or lift control (CiA 417)?

What are the maximal and minimal requirements to the micro-controller (cpu
and memory), CAN controller (how many controllers) for an advanced CANopen
design including CANopen protocol stack, object dictionary, application,
e.g. for 20 TPDOs and RPDOs, 5 SDO channels, 5000 CANopen objects. NMT
manager, SDO manager, Network redundancy capability?

Is the cape or a standalone board be capable to fulfill those requirements?

Should the board (as a cape or a standalone version)  be a development
(designed for a particular application) and/or an evaluation board
(designed for various applications, supporting future versions of a
micro-controller, CAN controller, CAN transceiver which are surface mounted
using BGA package)?

Does it make sense to have also a kind of adapter boards for connecting
raspberry pi  and shields from arduino?

Much appreciated.

Regards.


Kent