On 6/15/2016 9:49 AM, Bastian wrote: > > 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. Beside this I cannot identify anything unusual. > I > attached the log if you are interested in it.
That's likely the physically locked memory used by HAL and the real-time system. You definitely want to track down why you can't lock more than 64K. I've seen this when connecting via ssh, which by default tends to be more restrictive than the system configured defaults. To fix this for ssh, you need to put "UsePAM yes" in your /etc/ssh/sshd_config file (typically there's a comment about this at the bottom of the default Debian sshd_config file). Then, of course, your PAM settings need to allow locking more than 64K memory. As for why you aren't seeing the value change on HAL meter, I'm not sure. It looks like you've done everything necessary to get things working. The two things I can think of to check are: 1) You didn't do anything to control the pin muxing, but by default it should be set to GPIO. You can try using the config-pin utility if the device-tree you're using supports the universal overlay (I'm not sure what's on the current SandyBox image). But if you can properly see the signal changing value via "halcmd show", this isn't your problem. 2) There may be some problem with the HAL meter application. I haven't used it much (and never on a BBB), but it ought to work. You might want to try using halscope instead (I know that works), and make sure you're adding the monitor process to the proper HAL thread (there is typically no base thread on BBB configurations). -- Charles Steinkuehler [email protected] -- 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.
