-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi,
well, I repost my question with some further information. I tried to find out what happens, when I call start() on the SplitControl (which is the only thing that gets called in our SerialInit.init()). The SplitControl turns out to be wired to a StdControl in our SerialProtoP. This again is wired to our PlatformSerialC, that says StdControl = TelosSerialP, so TelosSerialP implements the start() method. But the TelosSerialP StdControl.start() implementation only calls Resource.immediateRequest(). As far as i understood the TEP 108 this only tries to get the resource without queueing the request and returns if it is possible for that single point in time. Deep down in the ArbiterP where the Resource seems to be wired to (I cannot tell for sure as my brain had several severe breakdowns while following the dataflow through about 20 open vims) the immediateRequest() calls ResourceConfigure.configure[resId]() if the resId is the id of the type the immediateRequest is called with. But then as I looked into the implementation of ResourceConfigure.configure() I saw it was "only" a default implementation which is empty. If I got it right, default means that this implementation is used if not already declared elsewhere. And for me it does not have been declared elsewhere, since Msp430UsartShare0P creates a new FcfsArbiterC(MSP430_HPLUSART0_RESOURCE) as ArbiterC and then Resource = ArbiterC and ResourceConfigure = ArbiterC. Now the FcfsArbiterC creates a new ArbiterP(uniqueCount(resourceName)) as ArbiterP, where the resourceName is MSP430_HPLUSART0_RESOURCE. Then it states Resource = ArbiterP and ResourceConfigure = ArbiterP. This seems to me, that the default implementation of ArbiterP is used, so it does nothing. Which again leads me to the question if there is somewhere in the TinyOS system an initialization of the serial port taking place? Greetz, chriz Christopher Schwardt wrote: > Hi there, > > we are having a problem developing an application that communicates with > a smart card reader attached to our telosb mote. > The communication works between the pc and the mote and the pc and the > reader, but not if the mote and the reader are connected with each other > over the uart0 device. > We presume that there is some initialization between a connected DTE > (Data Terminal Equipment) and the DCE (Data Communications Equipment), > that gets triggered by the DTE. We guess, that both devices, the mote > and the reader, act like DCEs and therefore no initialization takes > place, resulting in no communication at all. > > This leads us to two questions. > First: Is there such initialization between the DTE and DCE? > Second: If there is, what is the easiest way to trigger it on the mote? > > Greetz, > Chriz _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFILVR8CMaHFbmprfoRCL6jAJ99xqDlpjH/TTF8TmeFEHGh099X3ACgxlr+ 90GGC15p1PjHG6Ky+q4YNkU= =zvvk -----END PGP SIGNATURE----- _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
