On 15/06/16 15:49, Bastian wrote:


Whilst we are waiting for the BBB gurus, I notice that parallel-cape2.bbio still includes the hdmi cape overlay you say is disabled

I assume that cape uses the pin you chose, are you actually sure it is disabled?
Try commenting out the overlay line?

Yes, I tired and got some errors. I think the statement is correct. If my understanding is correct, the overlay actually enables the usage of the pins which are normally used by hmdi as gpio pins.

In file 'base_bbb.hal' I added 846 to the input_pins.



Have you tried NOT exporting the pin and writing to it via fd  calls in /sys/class/gpio


I tried to not export the Pins (commented the lines in rc.local). While starting AXIS, I got 4 warnings that the pins are not exported and direction/value cannot be set. HAL Meter shows still the wrong value.
What are fd calls?

My terminology may be incorrect, file descriptor - using read and write operations to psuedo files to address memory locations

 

The other suggestion is to set DEBUG = to a high number ( at least 5) run and then look at /var/log/linuxcnc.log

The hal_bb_gpio driver has numerous debug error prints  - you may catch something there


I changed the value for DEBUG to 0x7FFFFFFF and looked into the log file. There is a memory allocation problem right at the beginning, because maximum memory allocation is set to 64 KiB.

You can increase that within /etc/security/limits.d/machinekit.conf

Try inserting something like the attached file

Beside this I cannot identify anything unusual. I attached the log if you are interested in it.

Looks like the pin is created OK
```
Mar 16 08:38:38 sandybox msgd:0: hal_lib:6488:rt hal_pin_new:121 HAL: creating pin 'bb_gpio.p8.in-46'
Mar 16 08:38:38 sandybox msgd:0: hal_lib:6488:rt hal_pin_new:121 HAL: creating pin 'bb_gpio.p8.in-46.invert'
Mar 16 08:38:38 sandybox msgd:0: hal_lib:6488:rt pin 46 maps to pin 2-7, mode 85
```

I don't use BBB, so have nothing I can test further with, have to leave you to the 'experts'

regards


regards

--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
# /etc/security/limits.conf.d/machinekit.conf
#
#<domain>        <type>  <item>  <value>
# Default 64 not big enough for Machinekit
*                -       memlock         32768
root             -       memlock         32768

# Taken from RedHat's rt-setup package
*                soft    cpu             unlimited
*                -       rtprio          99
*                -       nice            -20

# End of file

Reply via email to