Hi Tony,

I haven't changed the baud rate (so it's 115200), and my pings are
certainly not 400ms, so I'm not seeing that issue (whatever it is/was).

Another quick question... When you do a wireshark of something with
6lowpan fragmentation, are you getting malformed packet errors for the
first packet? I'm trying to decide whether this is something that could
hold me up, or whether it's a wireshark issue with 6lowpan. I uploaded a
capture file[1] from my embedded board. :1 is the PC with econotag and
:2 is the embedded board with mrf24j40. As you can see, not all the
packets are making it through. I'll do some testing with the rftest tools.

This example capture [2] shows an HC1 header (for example, packet 4)
that we don't have, but my quick look at the 6lowpan RFC hasn't been
able to convince me that it's required in any way. Like I said, it could
be a Wireshark issue.

Alan.

[1] http://www.signal11.us/~alan/cap.pcap.gz
[2]
http://wiki.wireshark.org/SampleCaptures?action=AttachFile&do=view&target=6LoWPAN.pcap.gz

On 08/02/2012 04:43 PM, Tony Cheneau wrote:
> Hi all,
>
> (Just answering to that last mail quickly, and I'll come back to the
> other ones when I'll have more time.)
>
> I found out that the baudrate is very important when experimenting
> with the Econotag (I wrote about that on the zigbee list a few months
> ago). A ping6 (on a heavily patched kernel) would initially take me
> around 400ms at 115200 bps. At 926000, it takes me around 20ms
> (agreed, there might have been something else wrong before).
>
> As a side note, when doing a lot of exchanges between devices running
> at 926000, one has to be careful about having the rftest-rx firmware
> used for sniffing being built at 926000 bps too, or else some packets
> won't get through and the packet capture will not reflect what is
> actually sent. However, the rftestrx2pcap.py throw an exception pretty
> quickly at this speed (I'll need to find out why exactly and fix it).
>
> Regards,
> Tony
>
> Le 02.08.2012 22:04, David Kopf a écrit :
>> Is there any difference between 115200 and 921600 baud? If using flow
>> control, does it hang in interrupt when the output buffer is full?
>> The econotag can send packets very rapidly if the tx queue is used,
>> not leaving enough time for the receiver to unload the fifo. The
>> standard for long interframe spacing is 640 usec; accumulate the
>> minimum difference between tx's using the mac clock and subtract the
>> RF time to see what is the LIFS.
>>
>>
>> -----Original Message----- From: Alan Ott
>> Sent: Thursday, August 02, 2012 3:22 PM
>> To: Mariano Alvira ; Tony Cheneau
>> Cc: mc13...@devl.org ; Alexander Smirnov ;
>> linux-zigbee-devel@lists.sourceforge.net
>> Subject: [mc1322x] Econotag Linux 802.15.4 issues
>>
>> Hello,
>>
>> I have an Econotag that I'm running with the linux802154-serialdev[1]
>> firmware and using the serial.c driver from the linux-zigbee[2] project.
>> I'm running the latest kernel (linux-next, with serial.c manually ported
>> over). I've also run with the 3.3-rc5[2] kernel (+patches) which is
>> hosted at the linux-zigbee[2] project.
>>
>> I'm currently able to talk between two systems, one system with the
>> Econotag and serial.c, and the other system with an MRF24J40 and a
>> driver I wrote[3] and am trying to test. I can ping6 between the two
>> systems with high reliability, but there seems to be trouble when
>> packets are sent too quickly from the Econotag. For example, if I change
>> the ping interval (-i) to 0.1, most of the packets get lost. An interval
>> of 0.2 works fine though. This issue also seems to present itself when
>> sending real 6lowpan traffic, such as using ssh. I am completely unable
>> to ssh between the two systems, and wireshark of wpan0 on the Econotag
>> PC shows a lot of retransmission-related packets.
>>
>> I put in some printk()'s and found that sometimes the
>> ieee802154_serial_xmit() function returns -110 (-ETIMEDOUT). It doesn't
>> seem like that happens as often as packets are lost though. I need to
>> investigate further to find out which command is failing and when.
>>
>> The above is all with the linux-next kernel using the instructions at
>> [4]. However, I also noticed some dropping of packets when using the
>> linux-zigbee kernel[2] and izchat[5] if I typed and hit enter really
>> quickly a few times from the Econotag PC.
>>
>> My question is, have any of you done any stress testing with the
>> Econotag, the linux802154-serialdev firmware, and serial.c using a
>> protocol analyzer or other method? Do any of you have 6lowpan working
>> with the Econotag in this configuration (with linux802154-serialdev)?
>>
>> I'm not trying to point fingers. I'm just in a situation where I have
>> too many unknowns, and I'm trying to make sense of it. The issue could
>> very well be on my side. I do however have some things which could
>> possibly to point to Econotag firmware/driver issues, and I'd like to
>> know what experiences others have had with this configuration.
>>
>> Thanks,
>>
>> Alan.
>>
>> [1] http://mc1322x.devl.org/linux802154-serialdev.html
>> [2]
>>
>> http://linux-zigbee.git.sourceforge.net/git/gitweb.cgi?p=linux-zigbee/kernel;a=summary
>>
>> [3] http://permalink.gmane.org/gmane.linux.network.zigbee.devel/1135
>> [4] http://code.google.com/p/linux-wsn/wiki/Mainline
>> [5]
>> http://sourceforge.net/apps/trac/linux-zigbee/wiki/GettingStarted-0.2
>>
>>
>> _______________________________________________
>> mc1322x mailing list
>> mc13...@devl.org
>> http://devl.org/cgi-bin/mailman/listinfo/mc1322x
>


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel

Reply via email to