http://wiki.mcselec.com/bavr/index.php?action=history&feed=atom&title=CONFIG_FT800CONFIG FT800 - Revision history2026-05-06T11:37:52ZRevision history for this page on the wikiMediaWiki 1.18.6http://wiki.mcselec.com/bavr/index.php?title=CONFIG_FT800&diff=5410&oldid=prevAdmin at 18:08, 17 January 20172017-01-17T18:08:40Z<p></p>
<a href="http://wiki.mcselec.com/bavr/index.php?title=CONFIG_FT800&diff=5410&oldid=5242">Show changes</a>Adminhttp://wiki.mcselec.com/bavr/index.php?title=CONFIG_FT800&diff=5242&oldid=prevAdmin at 21:17, 15 June 20152015-06-15T21:17:18Z<p></p>
<a href="http://wiki.mcselec.com/bavr/index.php?title=CONFIG_FT800&diff=5242&oldid=5241">Show changes</a>Adminhttp://wiki.mcselec.com/bavr/index.php?title=CONFIG_FT800&diff=5241&oldid=prevAdmin at 21:16, 15 June 20152015-06-15T21:16:28Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr valign='top'>
<td colspan='2' style="background-color: white; color:black;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black;">Revision as of 21:16, 15 June 2015</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 9:</td>
<td colspan="2" class="diff-lineno">Line 9:</td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>= <span class="f_Header">Syntax</span> =</div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div>= <span class="f_Header">Syntax</span> =</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="background: #ffa; color:black; font-size: smaller;"><div><span style="font-weight: bold; color: rgb(0, 0, 128);">CONFIG FT800 =&nbsp;</span>spi [, FTSAVE=ftsave , FTDEBUG=ftdebug] , FTCS=ftcs [, FTPD = ftpd]</div></td><td class='diff-marker'>+</td><td style="background: #cfc; color:black; font-size: smaller;"><div><span style="<ins class="diffchange diffchange-inline">font-size: 13.3333330154419px; </ins>font-weight: bold; color: rgb(0, 0, 128);">CONFIG FT800 =&nbsp;</span<ins class="diffchange diffchange-inline">><span style="font-size: 13.3333330154419px;"</ins>>spi [, FTSAVE=ftsave , FTDEBUG=ftdebug] , FTCS=ftcs [, FTPD = ftpd] <ins class="diffchange diffchange-inline">[,FTCHIP=800|801] [,PLATFORM=platform] [,LCD_SCREEN-lcdscr] [,LCD_ROTATE=lcdrotate] [,LCD_CALIBRATION=calib]</span></ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span style="font-family: Arial;">&nbsp;</span></div></td><td class='diff-marker'> </td><td style="background: #eee; color:black; font-size: smaller;"><div><span style="font-family: Arial;">&nbsp;</span></div></td></tr>
</table>Adminhttp://wiki.mcselec.com/bavr/index.php?title=CONFIG_FT800&diff=4961&oldid=prevAdmin: Created page with "= <span class="f_Header">Action</span> = This compiler option is required to setup the FT800 SPI interface. <span style="font-family: Arial;"> </span> <span style="fon..."2014-12-12T21:37:46Z<p>Created page with "= <span class="f_Header">Action</span> = This compiler option is required to setup the FT800 SPI interface. <span style="font-family: Arial;"> </span> <span style="fon..."</p>
<p><b>New page</b></p><div>= <span class="f_Header">Action</span> =<br />
<br />
This compiler option is required to setup the FT800 SPI interface.<br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
= <span class="f_Header">Syntax</span> =<br />
<br />
<span style="font-weight: bold; color: rgb(0, 0, 128);">CONFIG FT800 =&nbsp;</span>spi [, FTSAVE=ftsave , FTDEBUG=ftdebug] , FTCS=ftcs [, FTPD = ftpd]<br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
= <span class="f_Header">Remarks</span> =<br />
<br />
&nbsp;<br />
<div style="padding: 0px; margin: 0px 0px 0px 4px;"><br />
{| width="631" cellspacing="0" cellpadding="1" border="1" style="border: 2px solid rgb(0, 0, 0); border-spacing: 0px; border-collapse: collapse;"<br />
|- style="vertical-align: top;"<br />
| valign="top" width="16%" style="width: 97px; border: 1px solid rgb(0, 0, 0);" | <br />
spi<br />
<br />
| valign="top" width="100%" style="width: 525px; border: 1px solid rgb(0, 0, 0);" | <br />
The SPI interface used for the FT800 processor. This may be&nbsp;:<br />
<br />
- SPI, for normal AVR processors<br />
<br />
- SPIC, SPID, SPIE, SPIF, for XMEGA processors.<br />
<br />
|- style="vertical-align: top;"<br />
| valign="top" width="16%" style="width: 97px; border: 1px solid rgb(0, 0, 0);" | <br />
ftsave<br />
<br />
| valign="top" width="100%" style="width: 525px; border: 1px solid rgb(0, 0, 0);" | <br />
This is an optional parameter with a default of 0. The possible values are 0 and 1. With this option enabled, the parameters passed to the various FT800 routines are limited in range. For example when a parameter is expected in the range from 0-31 it would not matter if you pass 32. But limiting the range increases code. It is best to make sure yourself that you pass the proper values.<br />
<br />
|- style="vertical-align: top;"<br />
| valign="top" width="16%" style="width: 97px; border: 1px solid rgb(0, 0, 0);" | <br />
ftdebug<br />
<br />
| valign="top" width="100%" style="width: 525px; border: 1px solid rgb(0, 0, 0);" | <br />
This is an optional parameter with a default of 0. The possible values are 0 and 1. With this option enabled, the SPI communication can be monitored. A label named&nbsp;<span style="font-weight: bold;">_FTDBG</span>&nbsp;is called in your code. So when using this option you need to insert this label into your code. You also need to DIM a byte named<span style="font-weight: bold;">ftdebug</span>. This byte will be filled with the parameter sent to the SPI.<br />
<br />
Make sure you put a RETURN after the label and save registers you use:<br />
<br />
&nbsp;<br />
<br />
_FTDBG<br />
<br />
Pushall<br />
<br />
print hex(ftdebug)<br />
<br />
Popall<br />
<br />
RETURN<br />
<br />
|- style="vertical-align: top;"<br />
| valign="top" width="16%" style="width: 97px; border: 1px solid rgb(0, 0, 0);" | <br />
FTCS<br />
<br />
| valign="top" width="100%" style="width: 525px; border: 1px solid rgb(0, 0, 0);" | <br />
The name of the SPI port pin connected to the CS pin of the FT800. This would be SS in most cases. This pin is set to output and to logic level 1.<br />
<br />
|- style="vertical-align: top;"<br />
| valign="top" width="16%" style="width: 97px; border: 1px solid rgb(0, 0, 0);" | <br />
FTPD<br />
<br />
| valign="top" width="100%" style="width: 525px; border: 1px solid rgb(0, 0, 0);" | <br />
The name of the port pin connected to the PD pin of the FT800. This is an optional pin, it depends on your hardware. Gameduino2 does not require it. EVE demo boards do require this pin.<br />
<br />
|}<br />
</div><br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
<span style="font-family: Arial;">The CONFIG FT800 statement will inform the compiler to use the FT800.LIB. It will also create an ALIAS for the CS and PD pins you specify.</span><br />
<br />
<span style="font-family: Arial;">The FT800 is controlled by the SPI interface. This means that you need to configure the SPI the usual way.</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
<span style="font-family: Arial;">BASCOM FT800 support is implemented in the following way:</span><br />
<br />
<span style="font-family: Arial;">- a low level communication library FT800.LIB</span><br />
<br />
<span style="font-family: Arial;">- ASM include macros which are located in the FT800.LIB. Unlike sub routines, the code is included and not called.</span><br />
<br />
<span style="font-family: Arial;">- BASCOM high level commands such as CMD32, RD8(), RD16(), etc.</span><br />
<br />
<span style="font-family: Arial;">- FT800 include files&nbsp;: an include file with the declarations (FT800.INC) and an include file with the actual code (FT800_FUNCTIONS.INC).</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
<span style="font-family: Arial;">You may modify the code from the include files. The code will reveal some new options. It is important to understand these new options.</span><br />
<br />
<span style="font-family: Arial;">- Passing values using&nbsp;[[BYREG]]</span><br />
<br />
<span style="font-family: Arial;">- Passing values using&nbsp;[[BYSTACK]]</span><br />
<br />
<span style="font-family: Arial;">-&nbsp;[[CMDFTSTACK]]</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
= <span class="f_Header">See also</span> =<br />
<br />
<span style="font-family: Arial;">&nbsp;,&nbsp;[[CMDFTSTACK]]&nbsp;,&nbsp;[[CMD32]]&nbsp;,&nbsp;[[RD8]],&nbsp;[[RD16]],&nbsp;[[RD32]]&nbsp;,&nbsp;[[WR32]]</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
<span style="font-family: Arial;">&nbsp;</span><br />
<br />
= <span class="f_Header">Partial Example</span> =<br />
<br />
<source lang="bascomavr"><br />
' FT800 Gauges Application demonstrating interactive Gauges using Lines & Custom Font<br />
' FT800 platform.<br />
' Original code from http://www.ftdichip.com/Support/SoftwareExamples/EVE/FT_App_Gauges.zip<br />
' Requires Bascom 2.0.7.8 or greater<br />
<br />
$Regfile = "M328pdef.dat"<br />
$Crystal = 8000000<br />
$Baud = 19200<br />
$HwStack = 90<br />
$SwStack = 90<br />
$FrameSize = 300<br />
$NOTYPECHECK<br />
<br />
Config ft800=spi , ftsave=0, ftdebug=0 , ftcs=portb.2, ftpd=portb.1<br />
<br />
Config Base = 0<br />
Config Submode = New<br />
Config Spi = Hard , Interrupt = Off , Data_Order = Msb , Master = Yes , Polarity = Low , Phase = 0 , Clockrate = 4, Noss = 1<br />
SPSR = 1 ' Makes SPI run at 8Mhz instead of 4Mhz<br />
<br />
<br />
' Swaps Scales<br />
' 1 = Resitive - Random<br />
' 0 = Random - Resistive<br />
Const Resistive = 0<br />
<br />
#If Resistive = 0<br />
Const First = 1<br />
Const Second = 0<br />
#Else<br />
Const First = 0<br />
Const Second = 1<br />
#EndIf<br />
<br />
$Include "FT800.inc"<br />
$Include "FT800_Functions.inc"<br />
<br />
Declare Sub cs(Byval i As Byte)<br />
Declare Function da (Byval i As Long) As Word<br />
Declare Sub Polar(byval R As Long , Byval Th As Word)<br />
Declare Sub Polarxy(byval R As Long , Byval Th As Word , Byref X As Long , Byref Y As Long)<br />
Declare Sub IntroFTDI<br />
Declare Sub Gauges<br />
Declare Function Read_Keys() As Byte<br />
<br />
' General Program Variables and Declarations<br />
Dim temp_tag As Byte<br />
Dim ox As Long<br />
<br />
<br />
Spiinit<br />
<br />
if FT800_Init()=1 then end ' Initialise the FT800<br />
<br />
Gauges<br />
<br />
Do<br />
<br />
Loop<br />
</source><br />
<br />
<span class="f_Header">Remark</span><br />
<br />
In the samples,&nbsp;<span style="font-weight: bold;">Noss = 1</span>&nbsp;is used for CONFIG SPI. This means that the SS pin must be set by the user. In case of CONFIG FT800, the compiler always set the specified pin for FTCS to output and to logic 1. When possible you should use NOSS=0 and use the dedicated SPI SS pin. But for multiple SPI devices on the bus that is not possible since you will have multiple CS pins, and in these cases you should use NOSS=1, so you can control the SS logic level.<br />
<br />
<br/>{{Languages}}<br />
<br />
[[Category:BASCOM Language Reference]]</div>Admin