Hi Claes,

It has been a while since I last experimented with the Raspberry Pi. I am now trying to experiment with it again, but this time, I'm using the more recent Proview V5.9
On the development station (Ubuntu 20.04), I made sure to follow what is written in the "man_rpi" documentation but while I'm trying to build associated to the Raspberry Pi on bus Prd1 (Operating system: CustomBuild, ARM on Linux...), I get the following errors:

%GSX-F-CCERROR, Error from c compiler or linker /usr/lib/gcc-cross/arm-linux-gnueabihf/9/../../../../arm-linux-gnueabihf/bin/ldÂ: /usr/local/pwrp/(myproject)/bld/arm_linux/obj/plc_raspberrypi_0001_plc.o: in function "plc_p1_init":
plc_raspberrypi_0001_plc.gc:(.text+0x0): undefined reference to "M000_001_001_015_00000022_init"

/usr/lib/gcc-cross/arm-linux-gnueabihf/9/../../../../arm-linux-gnueabihf/bin/ldÂ: /usr/local/pwrp/(myproject)/bld/arm_linux/obj/plc_raspberrypi_0001_plc.o: in function "plc_p1_exec":
plc_raspberrypi_0001_plc.gc:(.text+0x6): undefined reference to "M000_001_001_015_00000022_exec"

collect2: error: ld returned 1 exit status

And when I try to run the "custom_build.sh" script, I get such outputs:

./custom_build.sh: line 8: /pwra_env.sh: No such file or directory
mkdir: cannot create directory «/bld/arm_linux»: No such file or directory
mkdir: cannot create directory «/bld/arm_linux/obj»: No such file or directory
mkdir: cannot create directory «/bld/arm_linux/lib»: No such file or directory
mkdir: cannot create directory «/bld/arm_linux/lis»: No such file or directory
mkdir: cannot create directory «/bld/arm_linux/exe»: No such file or directory
./custom_build.sh: line 34: /os_linux/hw_arm/exp/exe/wb_gcg.sh: No such file or directory

So what could be wrong?

/Maverick

Hi Maverick,

There is some PlcPgm that is not compiled with CustomBuild. Check that you have set OperatingSystem to CustomBuild in File/VolumeAttributes in the root volume. Compile with Force to make sure everything is compiled.

/Claes

Hi Claes,

Thank you for your help. It works. But one more thing, after successfully distributing to the Raspberry Pi, I encounter such error when running the command systemctl enable pwr on the Raspberry Pi:

Synchronizing state of pwr.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable pwr
update-rc.d: error: no runlevel symlinks to modify, aborting!

and whenever I attempt to run the command pwr start, I have:

Job for pwr.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status pwr.service" and "journalctl -xe" for details.

/Maverick