Hello, On Tue, Mar 23, 2010 at 12:26 PM, Szabo, Gabor (GE Healthcare) <[email protected]> wrote: > Hello, > > Sorry that was my fault. I set wrong channel ID (1) yesterday and mentioned a > good one (11) in my mail. I think a little bit confusing to use different > channel numbers in python scripts and the userspace tools but I learnt the > lesson. Sorry again.
Ah, then it's fine. Python script (and current serial proto) uses channel numbers inherited from mc13193 chip. Hopefully our next gen protocol/firmware/etc. will use 802.15.4 channel specification. > Today morning I checked the code and saw the channel number problem. After I > changed it worked well. > > In my Zigbee system the end device is sending Beacon Request to the > coordinator to initiate the join. I tried to connect my linux box to the > coordinator and I saw it sent Association Request. Is this way missing now? > Where can I start to implement it? Unfortunately we (mac802154) are currently a bit diverged from the standard: 802.15.4 mandates that the device uses two requests for association (AssocReq + DataReq). As we currently don't have "indirect" MPDU queues, we've made the assoc just wait for the assoc response project. If you'd like to do a quick step towards standard compatibility, you can extend the association procedure by adding DataReq command after a calculated timeout. > > Thank You! > > Gabor > > -----Original Message----- > From: Dmitry Eremin-Solenikov [mailto:[email protected]] > Sent: 2010.03.23. 9:59 > To: Szabo, Gabor (GE Healthcare) > Cc: [email protected] > Subject: Re: [Linux-zigbee-devel] Problem in serial.c > > Hello, > > On Mon, Mar 22, 2010 at 5:18 PM, Szabo, Gabor (GE Healthcare) > <[email protected]> wrote: >> Hi! >> >> I tried the latest linux802154-serialdev firmware with the zigbee stack. >> With the python test scripts the communication worked correctly. But >> after I started the stack and the izcoordinatior I get an exception in >> serial.c:555 after I started a zigbee device. I downloaded the kernel >> and tool sources at 1st of March. Is it a known bug or I missed >> something? The low level serial communication seems to me worked >> correctly because the Beacon request received from the device. > > I've looked into your problem. That's really strange. The BUG_ON happens as > somebody is asking to set up the channel 1 and that's really strange. > > Could you please do several things to help us to debug the problem: > 1) comment two BUG_ONs in drivers/ieee802154/serial.c (on lines 555 and the > next one) > 2) insert a WARN_ON(1) in ieee802154_dev_set_channel (in net/mac802154/mib.c) > 3) send us an updated log. > > Thank you. > > -- > With best wishes > Dmitry > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Linux-zigbee-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel > -- With best wishes Dmitry ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Linux-zigbee-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
