Knowledge Base
The SPice10206 is no longer on sale for new designs. Please contact us if you have an existing design that uses this product.

Programming the SPice10206 and SitePlayer requires mainly an understanding of the SPLat Tiny Serial Peripheral (TSP) instructions and of how SiteObjects in the SitePlayer work and correspond to certain addresses. Your first port of call should be the SitePlayer documentation. We strongly recommend that you buy a SitePlayer developer kit, connect it to your PC and become thoroughly familiar with using and programming it via the PC.

There is also a Yahoo discussion group for SitePlayer which is a forum where you can exchange ideas with other SitePlayer users, and sometimes get help.

Once you have mastered the SitePlayer itself you will find that extending what you have learned to the SPLat and the TSP instructions is quite straightforward.

The TSP instructions allow you to write bits, bytes, words, long data (“Doubles” in SitePlayer parlance) and strings of up to 16 bytes to the SitePlayer. You can also interrogate the SitePlayer for the same data types. Data transfers go via the U register in SPLat.

The only real complication is that when you request a data item from the SitePlayer, it is not available instantly. For this reason we have a TSPBranch instruction that allows you to test if the requested data is yet available from the SitePlayer. You may find our multitasking tutorial useful to discover ways of making your application continue doing other things while a response is pending from the SitePlayer.

In the SitePlayer software manual you will find definitions of SitePlayer serial commands. These are the messages the SitePlayer can receive through its serial port (RS232 on the SitePlayer developer kit) and respond to. SitePlayer serial commands are mapped to SPLat TSP instructions according to the following table:

TSPSPComments
TSPGetBitReadBit 
TSPPutBitWriteBit 
TSPGet$ReadXFew TSP devises are likely to have more than 32K of memory, so normally you will be using the “L” version.
TSPPut$WriteX
TSPGetStatusStatus 
TSPSendUV Depends entirely on what you send. Typically used to generate a UDPSend