S63 plugin on ARM devices

[jongough]

I have been using OpenCPN on Intel chips, Windows and Linux, with the S63 plugin to allow use of encrypted charts, the only official charts available in Australia, for quite some time. I have just compiled the S63 plugin from git for the ARM processor as well as OpenCPN. OpenCPN works well, but the S63 OCPNsenc executable is currently only available in the git for intel/AMD chips used in PC's.

When will a version that runs on ARM chipped devices be available? I would like to try out the S63 plugin on an ARM processor machine.

Thanks
Jon

[bcn]

Jon,

this is on our S-63 "discussion" list for a while.

The main problem is to find a reliable and generally working way to identify the individual systems.
If somebody has insights in this direction please email us as we can't discuss these aspects here at the forum for obvious reasons.

Beyond this "detail" there is no reason why a cross compiled S-63 version should not work on ARMhf systems.

Hubert

[jongough]

Hubert,
I have compiled and installed OCPN and S63 plugin on a Raspberry Pi and I get a message that OCPNsenc cannot be executed. That is probably because it has not been compiled for ARM, a RISC architecture. From what I can see the plugin itself will work OK.

Jon

[bcn]

This is correct, you would need a cross compiled version of the plug-in.

And there is no technical hurdle but the issue I mentioned above: how to identify the great variety of possible candidates reliably.
DRM/TPM for ARMhf boards.
It's not trivial for the basic Linux system neither but the ARM systems we were able to test are a bigger challenge.

For suggestions and proposals please drop us a mail.
If we find a feasible method we will be happy to implement it.

Hubert

[seandepagnier]

bcn,

Why don't you just provide an armv7 (or even armv6) binary of OCPNsenc?

[bcn]

Sean,

cause the parameters we use on x86/desktop architectures are not (always) present on the small ARM devices, so we have to "invent" or find something additional to identify those individually.
The PI a binary/closed code already for all architectures. We are oblidged to so.

Hubert

[seandepagnier]

so it needs some kind of unique identifier based on the processor?

[jongough]

The closest you can get is the CPU serial number. It is supposed to be unique amongst all Pi's. Would this do as a starter?