Thread: [RTnet-developers] RTnet port for Tricore?
Brought to you by:
bet-frogger,
kiszka
Menu
▾
▴
rtnet-developers
|
From: Karl R. <Kar...@gm...> - 2007-03-28 12:18:14
|
Hello all, is there any work done porting RTnet on tricore from Infineon? What do you think, how much work would it be, writing an ethernet driver for RTnet for triboard 1130 NIC? I'm talking about a direct implementation, so no RTLinux like Xenomai/RTAI underneath. Thanks in advance for your help. Karl -- von Karl Reichert "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: http://www.gmx.net/de/go/promail |
|
From: Jan K. <jan...@we...> - 2007-03-29 08:35:47
Attachments:
signature.asc
|
Karl Reichert wrote: > Hello all, >=20 > is there any work done porting RTnet on tricore from Infineon? >=20 > What do you think, how much work would it be, writing an ethernet drive= r for RTnet for triboard 1130 NIC? I'm talking about a direct implementat= ion, so no RTLinux like Xenomai/RTAI underneath. On bare metal? No OS at all? Feasible, for sure. It's much like hacking RTmac/TDMA (I suppose that is your goal) into Etherboot, see the old patches. The basic TDMA support was fairly small code, just suffering a bit from our lacking standardised format for transmitting the TDMA configuration to the slaves (you will see the shell script parser in the patch...). Additionally, I had to add high resolution timer support to Etherboot. The advantage of bare-metal RTnet clearly is that you can achieve very low jitters for frame timing and time stamp synchronisation. Basically, you should get into the region which Ethernet Powerlink reaches as well by dedicating separate controllers on their protocol handling. I would be very interested to hear about your experiences! Jan |
|
From: Karl R. <Kar...@gm...> - 2007-03-29 08:55:58
|
-------- Original-Nachricht -------- Datum: Thu, 29 Mar 2007 10:34:31 +0200 Von: Jan Kiszka <jan...@we...> An: Karl Reichert <Kar...@gm...> CC: rtn...@li... Betreff: Re: [RTnet-developers] RTnet port for Tricore? > Karl Reichert wrote: > > Hello all, > > > > is there any work done porting RTnet on tricore from Infineon? > > > > What do you think, how much work would it be, writing an ethernet driver > for RTnet for triboard 1130 NIC? I'm talking about a direct > implementation, so no RTLinux like Xenomai/RTAI underneath. > > On bare metal? No OS at all? Feasible, for sure. It's much like hacking > RTmac/TDMA (I suppose that is your goal) into Etherboot, see the old > patches. The basic TDMA support was fairly small code, just suffering a > bit from our lacking standardised format for transmitting the TDMA > configuration to the slaves (you will see the shell script parser in the > patch...). Additionally, I had to add high resolution timer support to > Etherboot. > > The advantage of bare-metal RTnet clearly is that you can achieve very > low jitters for frame timing and time stamp synchronisation. Basically, > you should get into the region which Ethernet Powerlink reaches as well > by dedicating separate controllers on their protocol handling. I would > be very interested to hear about your experiences! > > Jan > Well, I'm still reading lots of papers to evaluate things, but as far as I understood until now, there are two possible ways how to do: a) As there is no port of etherboot to the tricore architecture, I first have to port it to this and then using the old patches and hacking them into etherboot. b) Implementing the RTnet spec directly on the tricore itself, which means, without using etherboot. Would you agree with that or do you have any other ideas? What would you consider to be less work, if you can tell? Thanks Karl -- von Karl Reichert "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: http://www.gmx.net/de/go/promail |
|
From: Jan K. <jan...@we...> - 2007-03-30 00:39:08
Attachments:
signature.asc
|
Karl Reichert wrote: > -------- Original-Nachricht -------- > Datum: Thu, 29 Mar 2007 10:34:31 +0200 > Von: Jan Kiszka <jan...@we...> > An: Karl Reichert <Kar...@gm...> > CC: rtn...@li... > Betreff: Re: [RTnet-developers] RTnet port for Tricore? >=20 >> Karl Reichert wrote: >>> Hello all, >>> >>> is there any work done porting RTnet on tricore from Infineon? >>> >>> What do you think, how much work would it be, writing an ethernet dri= ver >> for RTnet for triboard 1130 NIC? I'm talking about a direct >> implementation, so no RTLinux like Xenomai/RTAI underneath. >> >> On bare metal? No OS at all? Feasible, for sure. It's much like hackin= g >> RTmac/TDMA (I suppose that is your goal) into Etherboot, see the old >> patches. The basic TDMA support was fairly small code, just suffering = a >> bit from our lacking standardised format for transmitting the TDMA >> configuration to the slaves (you will see the shell script parser in t= he >> patch...). Additionally, I had to add high resolution timer support to= >> Etherboot. >> >> The advantage of bare-metal RTnet clearly is that you can achieve very= >> low jitters for frame timing and time stamp synchronisation. Basically= , >> you should get into the region which Ethernet Powerlink reaches as wel= l >> by dedicating separate controllers on their protocol handling. I would= >> be very interested to hear about your experiences! >> >> Jan >> >=20 > Well, I'm still reading lots of papers to evaluate things, but as far a= s I understood until now, there are two possible ways how to do: > a) As there is no port of etherboot to the tricore architecture, I firs= t have to port it to this and then using the old patches and hacking them= into etherboot. > b) Implementing the RTnet spec directly on the tricore itself, which me= ans, without using etherboot. >=20 > Would you agree with that or do you have any other ideas? >=20 > What would you consider to be less work, if you can tell? Go for b), unless you want features of Etherboot as well (boot image download...). I gave the reference just to study the TDMA patch, not the whole Etherboot design. What will be the application of that port? Means: what control structure will your code on tricore have, what communication will take place (periodic data reception or delivery, interactive traffic)? Or do you plan to write an RTnet library, ie. something totally generic? That's relevant when considering possible designs of the RTnet state machines. Jan |
|
From: Karl R. <Kar...@gm...> - 2007-03-30 07:57:56
|
> Karl Reichert wrote: > > -------- Original-Nachricht -------- > > Datum: Thu, 29 Mar 2007 10:34:31 +0200 > > Von: Jan Kiszka <jan...@we...> > > An: Karl Reichert <Kar...@gm...> > > CC: rtn...@li... > > Betreff: Re: [RTnet-developers] RTnet port for Tricore? > > > >> Karl Reichert wrote: > >>> Hello all, > >>> > >>> is there any work done porting RTnet on tricore from Infineon? > >>> > >>> What do you think, how much work would it be, writing an ethernet > driver > >> for RTnet for triboard 1130 NIC? I'm talking about a direct > >> implementation, so no RTLinux like Xenomai/RTAI underneath. > >> > >> On bare metal? No OS at all? Feasible, for sure. It's much like hacking > >> RTmac/TDMA (I suppose that is your goal) into Etherboot, see the old > >> patches. The basic TDMA support was fairly small code, just suffering a > >> bit from our lacking standardised format for transmitting the TDMA > >> configuration to the slaves (you will see the shell script parser in > the > >> patch...). Additionally, I had to add high resolution timer support to > >> Etherboot. > >> > >> The advantage of bare-metal RTnet clearly is that you can achieve very > >> low jitters for frame timing and time stamp synchronisation. Basically, > >> you should get into the region which Ethernet Powerlink reaches as well > >> by dedicating separate controllers on their protocol handling. I would > >> be very interested to hear about your experiences! > >> > >> Jan > >> > > > > Well, I'm still reading lots of papers to evaluate things, but as far as > I understood until now, there are two possible ways how to do: > > a) As there is no port of etherboot to the tricore architecture, I first > have to port it to this and then using the old patches and hacking them > into etherboot. > > b) Implementing the RTnet spec directly on the tricore itself, which > means, without using etherboot. > > > > Would you agree with that or do you have any other ideas? > > > > What would you consider to be less work, if you can tell? > > Go for b), unless you want features of Etherboot as well (boot image > download...). I gave the reference just to study the TDMA patch, not the > whole Etherboot design. > > What will be the application of that port? Means: what control structure > will your code on tricore have, what communication will take place > (periodic data reception or delivery, interactive traffic)? Or do you > plan to write an RTnet library, ie. something totally generic? That's > relevant when considering possible designs of the RTnet state machines. > > Jan > Thanks for the helping answer :) The plan is not to write a generic lib, although this would be very fine. I'm writing my diploma at university of applied sience Berlin from beginning of may for three months. This work consists of much more than a RTnet implementation. I also have to first evaluate the requirements of the whole system, communication ... So, what I can say to the requirements is, that I need a realtime ethernet communication, but with much less features RTnet is offering. I need for example no backup masters, no protection against failing slaves ... I just need a very simple, basic realtime ethernet, cause we are dealing with some testing systems here and if sth like failing stations occure, we will just stop whole tests, so no need for that. We are dealing with only few use cases here, which are communication from master to slave(uni/multicast) with or without answers, callbacks and communication between slaves. The whole communication is totally async. But of course writing a generic lib could be an option for me afterwards, or maybe for master thesis next summer. So why I am asking these questions is, because I'm at the moment thinking about differnet possibilities how to solve this problem. One of those - and at the moment my most prefered one, cause there is already a ready implementation for the PC (master) - is RTnet, but what I'm trying to find out is, how much work this would be, porting this (not completely, but basic features we need) to tricore 1130. So, don't really know what to ask at the moment. Maybe you could give me some hints/suggestions, if you consider RTnet to be right for this, if you see any major problems ... Thanks a lot Karl -- von Karl Reichert "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail |
|
From: Jan K. <jan...@we...> - 2007-04-05 17:30:43
Attachments:
signature.asc
|
Karl Reichert wrote: > Thanks for the helping answer :) >=20 > The plan is not to write a generic lib, although this would be very fin= e. I'm writing my diploma at university of applied sience Berlin from beg= inning of may for three months. This work consists of much more than a RT= net implementation. I also have to first evaluate the requirements of the= whole system, communication ... >=20 > So, what I can say to the requirements is, that I need a realtime ether= net communication, but with much less features RTnet is offering. I need = for example no backup masters, no protection against failing slaves ... = I just need a very simple, basic realtime ethernet, cause we are dealing = with some testing systems here and if sth like failing stations occure, w= e will just stop whole tests, so no need for that. We are dealing with on= ly few use cases here, which are communication from master to slave(uni/m= ulticast) with or without answers, callbacks and communication between sl= aves. The whole communication is totally async.=20 >=20 > But of course writing a generic lib could be an option for me afterward= s, or maybe for master thesis next summer. >=20 > So why I am asking these questions is, because I'm at the moment thinki= ng about differnet possibilities how to solve this problem. One of those = - and at the moment my most prefered one, cause there is already a ready = implementation for the PC (master) - is RTnet, but what I'm trying to fin= d out is, how much work this would be, porting this (not completely, but = basic features we need) to tricore 1130. >=20 > So, don't really know what to ask at the moment. Maybe you could give m= e some hints/suggestions, if you consider RTnet to be right for this, if = you see any major problems ... Sounds feasible. Did I already asked this: Do you have a working "bare-metal" Ethernet NIC driver for the TriCore? That would be the base to build all RTnet timing and protocol stuff around. And, finally, you could then add the application code on top of it. Try to find a clean separation (can already be a simple function call) between RTnet services and your control application on top. Makes it easier to cope with potentially changing requirements of the control application. Jan |
Thanks for helping keep SourceForge clean.
X