You are here: start » projects » icspio

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
projects:icspio [2015/01/08 01:59] – darronprojects:icspio [2017/01/12 22:44] (current) – external edit 127.0.0.1
Line 3: Line 3:
 ICSP I/O is a protocol and group of functions designed ICSP I/O is a protocol and group of functions designed
 to quickly develop test code for the devices supported to quickly develop test code for the devices supported
-by the k8048 Microchip PIC programmer.+by [[:projects:pickle|Pickle Microchip PIC ICSP]].
  
 It uses the I/O lines used by the ICSP programming It uses the I/O lines used by the ICSP programming
Line 9: Line 9:
 the Velleman K8048. the Velleman K8048.
  
-ICSP I/O was not designed a replacement for more established+ICSP I/O was not designed as a replacement for more established
 and more reliable protocols but it can be used for prototyping. and more reliable protocols but it can be used for prototyping.
  
 === Licence === === Licence ===
  
-ICSP I/O is licensed under same terms as the k8048 Microchip PIC programmer which is the origin of this software project. The k8048 Microchip PIC programmer [[:projects:k8048:licence|LICENCE]] is found here. This licence details the rights and liabilities of using  the  application and it should be especially understood that I, the  author,  will not accept any responsibility for any side effects of  running it.  Do not download and use this firmware unless you are willing  to accept  the consequences of it failing for any reason.+ICSP I/O is licensed under same terms as [[:projects:pickle|Pickle Microchip PIC ICSP]] which is the origin of this software project. The Pickle [[:projects:pickle:licence|LICENCE]] is found here. This licence details the rights and liabilities of using  the  application and it should be especially understood that I, the  author,  will not accept any responsibility for any side effects of  running it.  Do not download and use this firmware unless you are willing  to accept  the consequences of it failing for any reason.
  
 === Install === === Install ===
Line 40: Line 40:
 the main source file to ensure that this address is both valid and that there is enough space for allocation. the main source file to ensure that this address is both valid and that there is enough space for allocation.
  
-The include files are located in /usr/local/share/pickles/include+The include files are located in /usr/local/share/pickle/include
  
 === Demo === === Demo ===
Line 46: Line 46:
 == Set LEDs and read switches in a loop == == Set LEDs and read switches in a loop ==
 <code> <code>
-ktest 5 ARG+ptest 5 ARG
 </code> </code>
  
 == Set LEDs and read switches from the command line == == Set LEDs and read switches from the command line ==
 <code> <code>
-kio CMD ARG +pio CMD ARG
-Src/etc/led.sh +
-Src/etc/switch.sh+
 </code> </code>
  
Line 81: Line 79:
 PGD is used for data I/O with even parity and PGC for clock synchronisation. PGD is used for data I/O with even parity and PGC for clock synchronisation.
 PGC is unidirectional and is only controlled by the master (host), this is the PGC is unidirectional and is only controlled by the master (host), this is the
-slave. The interface may or not be inverted but this is catered for by the +slave. The interface may or not be inverted but this is catered for by 
-k8048 Microchip PIC programmer BITRULES inversion logic.+[[:projects:pickle|Pickle Microchip PIC ICSP]] BITRULES inversion logic.
  
-Data is setup on the master prior to a clock low to high transition and setup+Data is set up on the master prior to a clock low to high transition and set up
 on the slave after a clock low to high transition. Data is read after a clock on the slave after a clock low to high transition. Data is read after a clock
 high to low transition on both master and slave. high to low transition on both master and slave.