Revision: 1658
Author: [email protected]
Date: Wed Feb 10 21:26:16 2010
Log: Added image of my new programmer (PicKit2 Clone) to getting started
page. Updated image in SPI tutorial + minor changes. topublish.
http://code.google.com/p/jallib/source/detail?r=1658
Added:
/trunk/doc/dita/tutorials/images/getting_started_pic_kit2_clone.jpg
Modified:
/trunk/doc/dita/TOPUBLISH
/trunk/doc/dita/tutorials/images/spi_intro_data_transfer.jpg
/trunk/doc/dita/tutorials/tutorial_getting_started.xml
/trunk/doc/dita/tutorials/tutorial_spi_introduction.xml
=======================================
--- /dev/null
+++ /trunk/doc/dita/tutorials/images/getting_started_pic_kit2_clone.jpg Wed
Feb 10 21:26:16 2010
Binary file, no diff available.
=======================================
--- /trunk/doc/dita/TOPUBLISH Fri Jan 29 09:56:54 2010
+++ /trunk/doc/dita/TOPUBLISH Wed Feb 10 21:26:16 2010
@@ -26,7 +26,7 @@
tutorials/tutorial_blink_a_led.xml japp_config.py
2010012901
tutorials/tutorial_changelog.xml japp_config.py
2010012701
tutorials/tutorial_externals.xml japp_config.py
2010012501
-tutorials/tutorial_getting_started.xml japp_config.py
2010012501
+tutorials/tutorial_getting_started.xml japp_config.py
2010021101
tutorials/tutorial_gp2d02.xml japp_config.py
2010012501
tutorials/tutorial_i2c1.xml japp_config.py
2010012701
tutorials/tutorial_i2c2.xml japp_config.py
2010012701
@@ -42,5 +42,5 @@
tutorials/tutorial_sd_card.xml japp_config.py
2010012501
tutorials/tutorial_serial_communication.xml japp_config.py
2010012501
tutorials/tutorial_serial_port_board.xml japp_config.py
2010012501
-tutorials/tutorial_spi_introduction.xml japp_config.py
2010012801
+tutorials/tutorial_spi_introduction.xml japp_config.py
2010021101
tutorials/tutorial_spi_sram_23k256.xml japp_config.py
2010012801
=======================================
--- /trunk/doc/dita/tutorials/images/spi_intro_data_transfer.jpg Sun Jan 24
12:51:04 2010
+++ /trunk/doc/dita/tutorials/images/spi_intro_data_transfer.jpg Wed Feb 10
21:26:16 2010
Binary file, no diff available.
=======================================
--- /trunk/doc/dita/tutorials/tutorial_getting_started.xml Fri Jan 22
12:53:57 2010
+++ /trunk/doc/dita/tutorials/tutorial_getting_started.xml Wed Feb 10
21:26:16 2010
@@ -112,6 +112,7 @@
<p>Any pic programmer will do. The only suggestions I have is to
make sure it can program a wide variety of PIC’s such as the ones listed
above, and make sure it has a ICSP port for future use. ICSP is for
in-circuit programming.</p>
<p>Here are some images of programmers we use:</p>
<p><image href="images/getting_started_serial_programmer.jpg"
width="265" otherprops="clickable"/><image
href="images/getting_started_a-wisp648.jpg" width="217"
otherprops="clickable"/></p>
+ <p><image href="images/getting_started_pic_kit2_clone.jpg"
otherprops="clickable" width="300"/></p>
</section>
<section>
<title>What editor should I use?</title>
=======================================
--- /trunk/doc/dita/tutorials/tutorial_spi_introduction.xml Wed Jan 27
10:31:11 2010
+++ /trunk/doc/dita/tutorials/tutorial_spi_introduction.xml Wed Feb 10
21:26:16 2010
@@ -64,6 +64,7 @@
</tgroup>
</table>
<p>As you can see SPI sends the least bit's per data byte
transfer byte and does not need to send a device address before
transmission. This makes SPI the fastest out of the three we compared.</p>
+ <p>Although SPI allows "unlimited" devices, and I2C allows
for 1024 devices, the number of devices that can be connected to each of
these protocol's are still limited by your hardware setup. This
tutorial does not go into detail about connecting a large number of devices
on the same bus. When connecting more devices, unrevealed problems may
appear.</p>
</section>
<section>
<title>How does SPI work?</title>
@@ -76,9 +77,11 @@
</section>
<section>
<title>SPI Modes</title>
- <p>If you are using a device that does not yet have a Jallib
library, you will need to get the devices SPI mode. SPI devices can be set
to run in 4 different modes depending on the clock polarity & data
sample rising or falling edge.</p>
+ <p>If you are using a device that does not yet have a Jallib
library, you will need to get the devices SPI mode. Some device datasheets
tell you the SPI mode, and some don't. Your device should tell you the
clock idle state and sample edge, with this information, you can find the
SPI mode. SPI devices can be set to run in 4 different modes depending on
the clock's idle state polarity & data sample rising or falling
edge.</p>
+ <p>The image above is SPI mode 1,1. See if you can understand
why.</p>
<p><b>Clock Polarity (CKP)</b> - Determines if the clock is normally
high or normally low during it's idle state.</p>
- <p>If CKP is set to 1, the clock line will be high during idle.
With CKP=0 the clock will be low during idle.</p>
+ <p>If CKP = 1 - the clock line will be high during idle. </p>
+ <p>If CKP = 0 - the clock will be low during idle.</p>
<p><b>Data Clock Edge (CKE)</b> - The edge that the data is sampled
on (rising edge or falling edge)</p>
<p>If CKP = 0, CKE = 0 - Data is read on the clocks rising edge
(idle to active clock state)</p>
<p>If CKP = 0, CKE = 1 - Data is read on the clocks falling edge
(active to idle clock state)</p>
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
