Wolfgang, I have reproduced the problem.
That said - get_rtapi_config() was meant to be internal use to rtapi, and not from RT components. Also, since it uses file operations it would be usable only for userland components, and only in rtapi_app_main and rtapi_app_exit. Moreover, since the path handling does not have a very good general solution right now, I'm hesitant to export that for general use in an ad-hoc way, because that means that API is frozen as it stands and must be supported. proposal: just use a string parameter passed when loading the component - you are free to use ini/hal file macro substitution to do any pathname massage. See the mesanet .hal files which work that way. - Michael Am 12.02.2014 um 18:41 schrieb W. Martinjak <[email protected]>: > Charles, > > On 2014-02-02 03:01, Charles Steinkuehler wrote: >> >> Well, a quick check shows the get_rtapi_config function is defined in >> the xenomai flavor used with MachineKit. Michael or John might have >> more insight, but you might want to run "make V=1" to get a full dump of >> what's happening. That might help expose the problem, and is likely the >> first thing you'd be asked to provide unless Michael or John are aware >> of the problem already. > http://emc.mah.priv.at/irc/%23linuxcnc-devel/2014-02-02.html#17:14:45 > IMHO its still a issue. And I need a solution for accessing the fpga-firmware. > (see below) > >> I did the user-mode hostmot2 PCI driver for the x86 Xenomai flavor, but >> AFAIK no one has built pluto drivers for Xenomai (x86 or ARM), or *ANY* >> FPGA drivers for the BeagleBone. There could easily be a problem with >> the make files or defines. Using the verbose flag with make and posting >> the actual make results and not just a snippet with a truncated single >> error message are probably the best bet for identifying the problem. >> >> Is your code somewhere that's publicly visible (github or similar)? >> > Maybe I'm "no one" but I'm doing it. > https://github.com/tinkercnc/spi-fpga-driver > I know, there are some issues with the code but basically it works. (ie: > hardcoded firmware path. see above) > The raspi version better than the BBB version due to the mentioned spi-driver > issues (last PM). > Apropos spi-driver. > do you know something about the mcspi-driver? (activating in DT etc.) > > -- > "In der Wissenschaft siegt nie eine neue Theorie, > nur ihre Gegner sterben nach und nach" > > Max Planck > > > ------------------------------------------------------------------------------ > Android apps run on BlackBerry 10 > Introducing the new BlackBerry 10.2.1 Runtime for Android apps. > Now with support for Jelly Bean, Bluetooth, Mapview and more. > Get your Android app in front of a whole new audience. Start now. > http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
