| Installing WAGO-PFC-BSP-2018.2.1 [message #1787447] |
Fri, 25 May 2018 10:37  |
Eclipse User |
|
|
|
Hello 4DIAC Team,
I am using virtual machine with Ubuntu 16.04 version to install and cross compile forte for Wago PFC 200 by following the tutorial "Installation/Forte for WagoPFCs".
I am having some errors during installation of WAGO-PFC-BSP-2018.2.1.
According to tutorial step this;
2.4) Let the package manager list available toolchains for the cortexa8 (just to see if repository is working correctly).
>apt-cache search cortexa8-linux-gnueabihf
I am supposed to see the repository working but it doesn´t show anything after the command entered "apt-cache search cortexa8-linux-gnueabihf" and after step 2.5,
2.5) Install "oselas.toolchain-2012.12.1-arm-cortexa8-linux-gnueabihf-...
>sudo apt-get install oselas.toolchain-2012.12.1-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized
------------------------------------------------------------------------------
Repository will install the cross toolchain into folder:
/opt/OSELAS.Toolchain-2012.12.1/arm-cortexa8-linux-gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/bin/
------------------------------------------------------------------------------
I am facing some errors which are shown in screenshot I shared. Please have a look and help me out.
Thanks a lot for your support
Best Regards
Obaid Khan
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Installing WAGO-PFC-BSP-2018.2.1 [message #1807904 is a reply to message #1807876] |
Wed, 12 June 2019 02:54  |
| Eclipse User |
|
|
|
Hi,
First of all thanks to the video which you created, I think this will make life easier for many 4diac- Wago enthusiasts. One thing in advance, the Eclipse based build and debugging is required only when you require remote dubugging of your 4diac project on Wago PFC target device. For the initial testing of your compiled forte (4diac run time env) on wago, succeeding the step ptxdist targetinstall forte_wago
Coming to your eclipse use case, the problem is that the behavior of the remote system plugin may vary from version to version. I think you you have everything ready in your case. You are already connected to the wago. In your last step(3-3) at 16.27-17:27, you have a terminal window where you can execute all embedded linux commands and expand the root node of the remote system device, you may get the same root tree as shown in the help file.
I would be happy to know if it helps and see a full video.
|
|
|
|
| Re: Installing WAGO-PFC-BSP-2018.2.1 [message #1808077 is a reply to message #1808059] |
Mon, 17 June 2019 03:59 |
| Eclipse User |
|
|
|
Hi,
Once again thank you for the videos. I know "ptxdist targetinstall forte_wago" is a confusing command, one might expect that it should install the executable directly on the target. Yes it does, but this happens in the target system linux tree generated in your local host Ubuntu machine. These files are not transferred automatically to the actual remote Wago hardware. Our help files assumes that you create a bootable SD card as mentioned in the wago help file. This means you transfer your whole embedded linux tree on to your bootable SD card, and then boot with this SD card. You do not need to manually transfer the files in this case.
Subsequently you might need to connect to your remote hardware (Wago_PFC), where some tools like Putty, filezilla, Eclipse remote system explorer, etc., may be handy. We recommended Eclipse remote system explorer because it offers a more user-friendly experience for standard ssh and ftp connection offered by FileZilla and Putty. In addition, Eclipse remote system explorer offers remote debugging functionality, which will be really helpful, once we start playing with "forte" on remote hardware (Wago_PFC) . With any of the tools mentioned above, you may use the standard credentials from wago to establish an SSH connection.
Then comes the second case. If you do not want to create a bootable image and want to use the wago image on the shipped device OR do not want to disturb the bootable image already created, then you have to manually transfer the executable files generated in .../ptxproj-2.2.20/platform-wago-pfc200/buid-target/forte_wago-1.6.2-build/src to the target remote hardware (Wago_PFC). Here you may once again use any of the tools mentioned above. With filezilla or Eclipse remote system explorer, you get a tree view of the local file system (Host device) and remote system (target Wago_PFC) separately. You can use drag and drop functionality to execute a file transfer. It is recommended that a generated binary is copied on to /usr/bin directory of remote hardware (Wago_PFC).
Coming back your questions,
(1) Any of the command with prefix "ptxdist" works on only in the ptxdist build system project environment, ie for example ~wago/ptxproj-2.2.xx on the host machine
(2)You have already set up a Eclispe remote system explorer connection to the target wago PFC. So if you have used a bootable SD card, then your forte_wago might be there in the /usr/bin directory of the Wago_PFC. Otherwise you might have to drag and drop forte_wago binary from .../ptxproj-2.2.20/platform-wago-pfc200/buid-target/forte_wago-1.6.2-build/src directory of the host machine to /usr/bin directory of the target device
(3) The file sizes may not be an issue. As mentioned in the documentation, the help file, was created based on WAGO-PFC-BSP-2014.10.3, wago may have optimized their BSP in between.
Once you get an executable on the remote hardware(Wago_PFC), you may run any standard commands on the remote hardware(Wago_PFC) shell. For example
|
|
|
Home
