Roland Tollenaar wrote: > Hi, > > All closing & shutting down has been perfected. There are no more errors > on closing my application. > > Yet the problem persists very explicitly. Rtcan and EML can run > separately and never throw up any errors. As soon as they are used in > combination then in 50% of the cases the framebuilding in EML gets > messed up (as per the error message) > > There is definitely something between the two that is not right. >
In 9 of 10 cases (if not more): timing. Running both alone doesn't expose some timing issue (race) or transient overload. I can't help with EML complaints, maybe the FMTC guys have an idea what can trigger this and how to debug it. > >>>>> RTnet:rtskb allocation from real-time cache failed. > > Could I get some tips as to what I can do about this? I seem to get it > even when I do not have rtcan activity running in my application and > (because I am clueless) I would like to prevent this message which may > signify the root of the problem. You have created the socket for some/all EML activity from primary mode of some Xenomai thread, thus network buffer allocation is ought to run against the real-time rtskb pool - which is by default empty :p. See README.pools from the RTnet documentation on this. I don't have the EML design at hand, but you might be able to avoid this by initialising before creating the shadow task or by explicitly switching to secondary mode before initialising. [Sorry for this issue, it's at least partly due to some outdated RTnet design.] Jan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
