# Problem with SPI

**URL:** <https://forums.digi.com/t/problem-with-spi/13755>\
**Category:** XBee Programamble (S2C & 900 HP)\
**Tags:** problem, spi, xbee\
**Created:** [October 16, 2014, 3:41am UTC](https://forums.digi.com/t/problem-with-spi/13755 "2014-10-16T03:41:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![warchild](https://avatars.discourse-cdn.com/v4/letter/w/b19c9b/32.png) [@warchild](https://forums.digi.com/u/warchild)\
**Post date:** [October 16, 2014, 3:41am UTC](https://forums.digi.com/t/problem-with-spi/13755/1 "2014-10-16T03:41:19Z")

</div>

Good day!

Nowadays we understand module 868LP and found the following problems:

1. firmware 8059.  
A module sometimes, when reading data from it via SPI, there is a watchdog timer reset is. Average - at five minutes at an intensity of 2 packets of data per second.  
The conditions under which it is observed:

- Worked through the SPI;
- Module receives broadcast packets;
- The module does not send.  
What it looked like:
- Exposes the module interrupt SPI\_ATTN (LOW).
- Exhibiting him SPI\_SSEL, begin reading data via the SPI
- Read normal package with submitted data, but after that - SPI\_ATTN not returned to HI.
- As SPI\_ATTN in LOW, continue reading data SPI. Fails to consider the order of 93630 bytes (plus / minus 10 bytes) - all zeros.
- Then returned to HI SPI\_ATTN
- After 250 microseconds ATTN switches back to LOW
- Read data from there and get the very first packet 0x7E, 0x00, 0x02, 0x8A, 0x01, 0x74. If you believe the documentation - 0x01 = Watchdog timer reset

1. firmware 8072  
Unable to run the module in operation SPI.  
Our software successfully works with firmware 8059, but after a firmware update to 8072 - SPI does not work.  
Prohibition outputs UART not given effect.

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [October 30, 2014, 9:57am UTC](https://forums.digi.com/t/problem-with-spi/13755/2 "2014-10-30T09:57:34Z")

</div>

Yes Digi is aware of this and is working on solving the issue.