@Gerhard-Bertelsmann Thanks for your answer ! Do I understand it correctly that this board is like a dock for the Omega2+ and through a serial communication lib will read/write the CAN BUS ?
yes, that's right. It's using the SLCAN API which could be used in conjunction with SocketCAN. The firmware was mainly developed by Darron Broad
The PIC firmware is highly optimized so that there are lots of free cycles even under heavy load on the CAN-Bus.
Can you share more details of it and is it possible to buy it ?
With the /overlay having almost the same size as /rom, I would guess something in the update/reset process has duplicated most of the firmware into the overlay, for some reason, instead of completely emptying it.
I would have a look into /overlay, that's where you can see the files which occupy those 7.3M.
After all that - I spotted the Breadboard Dock as one of the options at ABRA Electronics (Canadian Distributor). Bought it and had it in my hands two days later. So finally answered my own question too ;-)
Note that this thread is about Omega, not Omega 2.
Omega 2 is rather picky, consumes more power, and has the habit of demanding high instantaneous current at times when voltage cannot drop below a lower voltage threshold known as brown-out Vcc.
i'm successfully using OpenVPN client with Omega2+ using AES-128 encryption without any cpu overhead problem. I'm using the LEDE project distribution re-built after re-configuring it through the 'make menuconfig'. A short steps list follows:
Download from github (git clone) the latest LEDE project source repository
'make menuconfig' and add OpenVPN plus SSL and Crypto libraries (and some other useful stuff you need)
'make', then copy the created firmware file (.bin) found in the bin/<target> directory to a USB key root
rename the firmware bin file to 'omega2.bin'
insert the USB key into the USB interface of the Omega 2 Dock, keep pressed the reset button and then power-on the board. - from the menu choose the command '2', then wait for the firmware file being flashed. lede distribution then will boot.
edit /etc/config/openvpn with your openvpn configuration (see openvpn manuals) and copy all certificates to /etc/openvpn directory
/etc/init.d/openvpn restart and you shoud be able to use openvpn as a client.
I agree, I had already typed my reply and then deleted the draft.
Douglas, you just didn't carefully read what he wrote :-)
I could see along the lines that he'd referred to the conclusions / breaking point of existing threads on this. Besides, the question was if there is any PLAN NOW to get things sorted, which is independent of any prior unanswered (and also different) threads.
Plus, not continuing to ask is the one way that can't have an effect.
I sense the guys have been quite busy considering they already got a 300+page book written, and I also can see on here that the Onion team is recovering or busy on something since 4weeks+.
In any case, like he wrote, it's a deprecated standard. It should be resolved, and likely can, and likely will. Knowing if it someone has set aside some time for this in, say August, or during Winter time, would allow for a rough plan and mean people can decide what they can build based on the hardware, and what not.