A ARM64 version?

[Th.Menard]

Hi there,

I wish to use the hobbyust tools into a RPI5 with an architecture arm64 instead of armhf. Is it possible to find the source, or a way to do that?

[rolfk]

Depends what you want to do. The Linx Makerhub Toolkit supports two modes.

The first is through a shared library that acts as a remote server. You can then use the Linx VIs to communicate over serial port or TCP/IP to do things on the remote target. The source for that shared library is in C++ and part of the Makerhub Github repository. You could get that repository and recompile the shared library for your target architecture 

The second mode is by treating it as a LabVIEW remote target, similar to how LabVIEW real time targets are accessed. Here you have no source code. This is performed by downloading a full LabVIEW runtime and extra driver libraries to the RPi or BBB. These runtimes are repacked binary products used for the NI ARM based real time targets that use a Zync 7000 FPGA ARM core. This is a Cortex A7 core which can only run 32-bit ARM code. In addition it uses soft FPU. Expecting NI to recompile the LabVIEW runtime and according drivers to a platform that delivers zero $ in income in software or hardware is of course naive. Getting the LabVIEW source code to do that yourself is even more unlikely. 

[Th.Menard]

Hi there,

Thanks you for the quick answer.

I wish to use hobbyist tools with this kind of device ( https://revolutionpi.com/en/products/revpi-connect ). This is based on the RPI5 compute module, but the producers add many interressing drivers. Unfortunatly it only work with a debian 64.

I try to add the armhf architecture via dpkg. I didn't succeed.

[rolfk]

You most likely can’t. The way NI does it is by installing a custom Debian image compiled as armeabi softfpu and install that in a chroot as a separate virtual machine. This has however a number of limitations.

1) That chroot environment has no access to the display. Your LabVIEW program runs literally in the dark!

2) Direct hardware access from inside that chroot is cumbersome and often impossible. This usually means that you can’t directly access custom hardware from your LabVIEW program.

3) Last but not least, those RevolutionPi hardware boxes are in terms of pricing not exactly low cost hobby hardware. If you intend to use the Community Edition you may however not use the end product in any commercial setting. This includes setting up a test solution for the production line of a friend, even if it is your best friend forever.

[Th.Menard]

Thanks again for the answer.

This differents points are not really a problem.

1) I don't need IHM.

2) I can have a codesys in the same device for the specific hardware access.

3) I use a proffessional edition of Labview.

Is it a solution?

[AndyLB]

Hi, 

I think it may be possible to get the LINX schroot working on a Rpi 5 running the 64 bit version of PI OS.  

I've tried a few tests and hope to have a beta version working next week.

The Rpi 5 running 32 bit PI OS  is currently supported in the LabVIEW 2024 and 2025 versions of the LINX Hobbyist toolkit. 

It supports the GPiO, I2C, UART and SPI signals on the Rpi 5  40 way connector. 

[Th.Menard]

It will be very great.

Can I help you?

[IlluminatedG]

By editing some of the package files you can get it to run on just about any debian based arm system, got it running on Banana Pi and Rock Pi a few years ago https://forums.ni.com/t5/Hobbyist-Toolkit/Successfully-running-LabVIEW-on-a-RockPi-S-512MB/td-p/4063...

[AndyLB]

Hi,

Good news, 

The 32 bit LINX schroot works on a Rpi 5 running the 64 bit PI OS.

The method I used was based on Derrick's excellent post. 

It needs the LabVIEW 2024 or LabVIEW 2025 versions of the lvrt .deb files.

I have a few more tests to run and will then post the commands I used.

GPIO, I2C and VISA USB serial devices are working. I was able to deploy a startup application.

Cheers,

Andy (LabVIEW Hobbyist)

[AndyLB]

Hi,
The 32 bit LINX schroot works on a Rpi 5 and a Compute Module 5 development kit running the 64 bit PI OS.

I ran tests on the GPIO, I2C, SPI (loopback) and Arduino / PICO USB serial devices. I was able to deploy start-up applications. 

The method I used required a change to the control file in the  lvrt24-schroot_24.1.0-3.deb and lvrt25-schroot_25.1.0-1.deb files

Architecture: armhf  was changed to  Architecture: arm64

I have attached text files showing the commands I used to install lvrt24-schroot and lvrt25-schroot. The commands can be pasted into a SSH session on the Rpi or the file can be copied to the Rpi and run as a script file.

e.g.

pi@pitest:~ $ chmod u+x install_lvrt24-schroot_on_64_bit_pi_os.txt
pi@pitest:~ $ ./install_lvrt24-schroot_on_64_bit_pi_os.txt

Script output
deb [trusted=yes] http://feeds.labviewmakerhub.com/debian/ binary/
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Ign:5 http://feeds.labviewmakerhub.com/debian binary/ InRelease
Ign:6 http://feeds.labviewmakerhub.com/debian binary/ Release
Ign:7 http://feeds.labviewmakerhub.com/debian binary/ Packages
Ign:8 http://feeds.labviewmakerhub.com/debian binary/ Translation-en_GB
Ign:9 http://feeds.labviewmakerhub.com/debian binary/ Translation-en
Ign:7 http://feeds.labviewmakerhub.com/debian binary/ Packages
Ign:8 http://feeds.labviewmakerhub.com/debian binary/ Translation-en_GB
Ign:9 http://feeds.labviewmakerhub.com/debian binary/ Translation-en
Ign:7 http://feeds.labviewmakerhub.com/debian binary/ Packages
Ign:8 http://feeds.labviewmakerhub.com/debian binary/ Translation-en_GB
Ign:9 http://feeds.labviewmakerhub.com/debian binary/ Translation-en
Hit:7 http://feeds.labviewmakerhub.com/debian binary/ Packages
Ign:8 http://feeds.labviewmakerhub.com/debian binary/ Translation-en_GB
Ign:9 http://feeds.labviewmakerhub.com/debian binary/ Translation-en
Ign:8 http://feeds.labviewmakerhub.com/debian binary/ Translation-en_GB
Ign:9 http://feeds.labviewmakerhub.com/debian binary/ Translation-en
Ign:8 http://feeds.labviewmakerhub.com/debian binary/ Translation-en_GB
Ign:9 http://feeds.labviewmakerhub.com/debian binary/ Translation-en
Ign:8 http://feeds.labviewmakerhub.com/debian binary/ Translation-en_GB
Ign:9 http://feeds.labviewmakerhub.com/debian binary/ Translation-en
Reading package lists... Done
Get:1 http://feeds.labviewmakerhub.com/debian binary/ lvrt24-schroot 24.1.0-3 [17.8 MB]
Fetched 17.8 MB in 2s (9,827 kB/s)
lvrt24-schroot_24.1.0-3_armhf.deb
Package: lvrt24-schroot
Version: 24.1.0-3
Section: base
Priority: optional
Provides: lvrt24-schroot
Replaces: lvrt24-schroot, lvrt19-schroot, lvrt20-schroot, lvrt21-schroot, lvrt22-schroot, lvrt23-schroot
Conflicts: lvrt24-schroot, lvrt19-schroot, lvrt20-schroot, lvrt21-schroot, lvrt22-schroot, lvrt23-schroot
Architecture: armhf
Depends: schroot, python3, avahi-daemon
Maintainer: LabVIEWMakerHub Administrator <admin@labviewmakerhub.com>
Description: LabVIEW run-time schroot
A schroot environment to allow the softfp LabVIEW run-time to run on a hardfp
Debian distro.

Package: lvrt24-schroot
Version: 24.1.0-3
Section: base
Priority: optional
Provides: lvrt24-schroot
Replaces: lvrt24-schroot, lvrt19-schroot, lvrt20-schroot, lvrt21-schroot, lvrt22-schroot, lvrt23-schroot
Conflicts: lvrt24-schroot, lvrt19-schroot, lvrt20-schroot, lvrt21-schroot, lvrt22-schroot, lvrt23-schroot
Architecture: arm64
Depends: schroot, python3, avahi-daemon
Maintainer: LabVIEWMakerHub Administrator <admin@labviewmakerhub.com>
Description: LabVIEW run-time schroot
A schroot environment to allow the softfp LabVIEW run-time to run on a hardfp
Debian distro.

postinst
postrm
preinst
prerm
control
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
schroot is already the newest version (1.6.13-3+b2).
debhelper is already the newest version (13.11.4).
The following packages were automatically installed and are no longer required:
libcamera0.3 libwlroots12 lxplug-network
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Selecting previously unselected package lvrt24-schroot.
(Reading database ... 150405 files and directories currently installed.)
Preparing to unpack lvrt24-schroot_24.1.0-3_arm64.deb ...
Unpacking lvrt24-schroot (24.1.0-3) ...
Setting up lvrt24-schroot (24.1.0-3) ...
Processing triggers for man-db (2.11.2-2) ...
pi@pitest:~ $

To remove previous lvrt-schroot installs before running the scripts you can use the command

sudo apt-get remove lvrt*-schroot

Hope this works on your system,
Andy.