| QX block - "FB Not Initialized" [message #1805818] |
Wed, 24 April 2019 16:09  |
 Felipe Molina
Messages: 1
Registered: April 2019 |
Junior Member |
|
|
Hello everybody,
We are using a custom board based on the SAMA53D. We have compiled FORTE and now are trying to run the simple blinking example (adding the QX block)(pic 1), this board has a linux system with SysFs on it.
The issue that we are facing, is that the QX fails to initialize (pic 2). The example was run on the raspberry pi, so we know the blocks are correct.
We have checked the GPIO folder (/sys/class/gpio) and the pin seems to be initialized (pioA19 is the equivalent to OUTPUT 19, which is the parameter defined on the QX block)(pic3). Neither the FORTE console (pic 4) or the deployment console indicates an error. IX blocks also shows the same behavior, as others GPIO pins on the board. This was tested on Ubuntu 18.10, Debian 9 and with a custom YOCTO build.
The block was also tested without the E_SR.EQ > QX.REQ connection (as was suggested on another post), but it didn't seem to have an effect on the connection.
Any input on how to debug this or where we could check for errors would be kindly appreciated,
Attachment: pic1.png
(Size: 102.65KB, Downloaded 112 times)-
Attachment: pic2.png
(Size: 107.25KB, Downloaded 96 times) -
Attachment: pic3.png
(Size: 10.21KB, Downloaded 93 times) -
Attachment: pic4.png
(Size: 25.09KB, Downloaded 98 times)
|
|
|
| Re: QX block - "FB Not Initialized" [message #1806340 is a reply to message #1805818] |
Tue, 07 May 2019 22:08  |
|
|
I would say that the problem is that the sysfs IO implementation assumes that the gpio is accessible as "/sys/class/gpio/gpio" + std::string(PARAMS().getValue()) + "/value". That means that the value you give to your QX FB has in your case to be set to chip128 in order to access the gpiochip128 pin that you have shown in your list. However to pioA19 is somehow special. With the current implementation this would not be possible. So you may need to develop your own process interface. Or find out why it is different and not a gpio. Could it be that there is an error in your gpio config?
|
|
|
|
Powered by
FUDForum. Page generated in 0.03433 seconds
] 
Search
Help
Register
Login
Home
