Tuesday, January 8, 2013

Can't find 0x210 words (0x210 withtotal) for psect "swtext1" in segment "CONST"

Have you ever seen something like this:

Error [1347] ; 0. can't find 0x210 words (0x210 withtotal) for psect "swtext1" in segment "CONST" (largest unused contiguous range 0x100)

Well, I crashed my head over the table the whole morning playing with buffers sizes, defines, deleting functions etc... The linker kept giving me the above error. Then I searched and fount this thread. One cool thing about this thread is that it contains a pretty cool step-by-step on how to trace to the root of the problem:

Monday, January 7, 2013

One more XBee tools-related bug

This time in (unofficial, unsupported etc) API Frame Maker tool from Digi.

This is, by the way, a very handy tool when it gets to understanding +XBee API operation. In seconds you can tailor a packet for all your needs and send it using X-CTU software (which feature-wise is exhostive, but usability-wise is a pain). Well, this API Frame Maker tools saves a lot of time.

But the bug took me a few hours of debugging (as usual, yes). It incorrectly calculates length for at least one API frame id - '0x90 Receive Packet'.

So be warned!

Sunday, January 6, 2013

The 0x97 bug is fixed in python-xbee!

I raised the issue described in Make a note: how an XBee replies to 'IS' command post on the package author's development group here. Paul replied, that the issue has been fixed for a while in the latest source code.

If you face the same issue (get 0x97 packet insted of 0x92 and the package fails to parse samples), here's what Paul advises:

As it happens, this bug has already been reported and fixed; a much more recent codebase which includes this fix is available at our Google Code source control: http://code.google.com/p/python-xbee/source/browse/. If you click the 'Download zip' link, in the approximate middle of the navigation bar, you will get the very latest version of the code.
I have not gotten around to updating the python-xbee distribution and documentation in quite some time; I apologize for this. 
Thanks again for this great package, Paul!