I hear you but no supply of these boards is available and I suspect it will be long forgotten when the rpi2 is still supported with a very large community. It is already obsolete and replaced with the pre-order XU-4 for twice the price
I get that there are a multitude of single
board Arm7+ boards out there and this market moves at light speed...
The rpi2 is a great spec machine and yes I also get that the lack of a Broadcom native driver is a problem for all of us that want to use it in earnest with grown up applications like OpenCPN
etc. It is also cheap
to have another redundant unit on standby in the event of an issue and will have availability for a long time. Anyone having a C1 that needed to replace it will be faced with recompiling for the samsung processor etc.
I live in hope that the brainpower of the community will overcome these issues. Otherwise as you say it may be necessary to go another direction and start the process of learning
all og the shortcomings of that platform!
I also wanted to report an issue. Maybe others have already seen it before. If I enable the dashboard plugin and enable the clock applet it crashes opencpn
and leaves nothing sensible in the logs
. It spammed syslog with endless of these:
Jul 23 06:33:00 pi org.mate.panel.applet.ClockAppletFactory: (clock-applet:764): GLib-GObject-CRITICAL **: g_param_spec_get_redirect_target: assertion 'G_IS_PARAM_SPEC (pspec)' failed
Maybe I am on the wrong track with these errors but could find nothing else in error.
I could not restart OpenCPN without a reboot.
I have disabled the clock applet and am running an extended 24 hour test to see if it is stable. Version was compiled last night and all went well no errors. So far all seems well no log spam etc. The system was not connected to a gps
during the failed test. And is not connected to a gps
now just the lan.
I can provide more info if you can point me in the direction of what might be useful.