On 31.07.19 10:55, danwe via Xenomai wrote:
> I have found that my modules are loading via "modprobe".
> You wrote:
> "Ah, you are on legacy, out-of-tree RTnet! I forgot that RTnet only moved
> into
> Xenomai for version 3.0. For 2.x, you are with the old repo that wasn't
> touched
> since 2013. In this particular case, the script fails early because of
> "insmod
> <existing-module>", rather than using "modprobe" like in Xenomai upstream".
>
> So in my S51rtnet it loads modules like this:
> for i in rtnet rt_smsc rt_davinci_mdio rt_ticpsw rtpacket rtipv4 rtmac
> rtcfg tdma
> do
> echo -n"$i "
> modprobe ${i}
> sleep 1
> done
>
> As you write "rather than using "modprobe" like in Xenomai upstream"...
> should tdma work on Xenomai 2 / RTnet here or is it just a problem because
> of ouf-of-tree RTnet?
The problem is you have two scripts now working against each other. The legacy
start script from legacy RTnet would do the heavy-lifting for RTmac/TDMA & Co.
but stumbles over insmod for an already loaded module. And your own start script
uses the right insmod but only does that, nothing for the full configuration.
Remove the latter, and you may get further - unless legacy RTnet has more
surprises.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
