2020-02-06 06:36 AM
Hi,
I tried to follow the given instructions for building the STUHFL demo for linux but I encountered multiple issues:
1) Header files were not found when building the solution.
2) The directory structure of the copied files on the Raspberry Pi was quite different to the one expected by the build commands in visual studio. So, there were errors of the libSTUHFL.so and the STUHFL_demo.out not being found.
3) Finally it ran:
4) The demo version on windows gives some options for interaction but it takes a considerable amount of time for it to respond.
Solved! Go to Solution.
2020-02-14 08:41 AM
Hello MStri.1,
ad 1: As the Linux demo is rather new we have currently only the VS2017 project as a working reference. Maybe the conversation to VS2019 made some problem here. We will check this.
----------------
ad 2: What RPi and distro do you use ?
----------------
ad 3: Your screen shows that the STUHFL_demo.out and libSTUHFL.so are compiled correct and run remote on your target.
The message "Welcome to the ST-UHF-L demo V1.9.0.0" comes from the libSTUHFL.so and is called in the STUHFL_demo from the function STUHFL_F_GetLibVersion() in the first statement in main.
But the board SW and HW version is wrong, it must be for SW: V1.9.0 and for HW: V1.0.0. This is when no valid UART communication is established between the Host (RPi) and the Reader (EVAL board)
This could have several reasons
*) Is the FTDI UART converter (is part of the EVAL board) detected by your RPi ?
*) Is the FTDI driver running and to which device is it mapped ? In the STUHFL_demo the default port is /dev/ttyUSB0. You could change this in main.c with the COM_PORT define
*) Do you use the FW V1.9.0 on your board ? The V1.8.6, which works with the GUI works not with the STUHFL_demo. To run the STUHFL_demo you need to flash the v1.9.0 FW from the package. You could use KEIL or TrueStudio to build, flash and debug the FW.
----------------
ad 4) For the windows STUHFL_demo its the same. Are you able to connect to the port and got correct version information ? If you are able to read with the GUI (v1.8.6) and did not flash the v1.9.0 FW the above mentioned point is the problem.
Please try again with FW v1.9.0 to run the STUHFL_demo (Windows or Linux)
We will soon release a V2.0.0 of the FW, GUI and STUHFL_demo were all components are compatible to solve this problem.
BR
Nick
2020-02-14 08:41 AM
Hello MStri.1,
ad 1: As the Linux demo is rather new we have currently only the VS2017 project as a working reference. Maybe the conversation to VS2019 made some problem here. We will check this.
----------------
ad 2: What RPi and distro do you use ?
----------------
ad 3: Your screen shows that the STUHFL_demo.out and libSTUHFL.so are compiled correct and run remote on your target.
The message "Welcome to the ST-UHF-L demo V1.9.0.0" comes from the libSTUHFL.so and is called in the STUHFL_demo from the function STUHFL_F_GetLibVersion() in the first statement in main.
But the board SW and HW version is wrong, it must be for SW: V1.9.0 and for HW: V1.0.0. This is when no valid UART communication is established between the Host (RPi) and the Reader (EVAL board)
This could have several reasons
*) Is the FTDI UART converter (is part of the EVAL board) detected by your RPi ?
*) Is the FTDI driver running and to which device is it mapped ? In the STUHFL_demo the default port is /dev/ttyUSB0. You could change this in main.c with the COM_PORT define
*) Do you use the FW V1.9.0 on your board ? The V1.8.6, which works with the GUI works not with the STUHFL_demo. To run the STUHFL_demo you need to flash the v1.9.0 FW from the package. You could use KEIL or TrueStudio to build, flash and debug the FW.
----------------
ad 4) For the windows STUHFL_demo its the same. Are you able to connect to the port and got correct version information ? If you are able to read with the GUI (v1.8.6) and did not flash the v1.9.0 FW the above mentioned point is the problem.
Please try again with FW v1.9.0 to run the STUHFL_demo (Windows or Linux)
We will soon release a V2.0.0 of the FW, GUI and STUHFL_demo were all components are compatible to solve this problem.
BR
Nick