Code Monkey home page Code Monkey logo

rpipic's Introduction

#/****************************************************************************/
#/* RPiPIC                                                                   */
#/* ------------------------------------------------------------------------ */
#/* V1.00 - 2017-05-13 - Jason Birch                                         */
#/* V1.01 - 2017-12-30 - Added support for PIC18F device programming.        */
#/* V1.02 - 2019-05-10 - Calibrate clock pulse, device specific clock period.*/
#/*                      Device ID lookup and verify.                        */
#/*                      Read specified data range. Only read and verify upto*/
#/*                      highest programmed or specified address.            */
#/*                      Added devices: 12F508,12F1822,16F505,16F688,16F716  */
#/* ------------------------------------------------------------------------ */
#/* Python PIC Microcontroller Programmer.                                   */
#/*                                                                          */
#/*                                                                          */
#/* Try to read unknown device ID:                                           */
#/*                                                                          */
#/* 16F_1W_DEV_ID   16F_2W_DEV_ID   18F_DEV_ID                               */
#/*                                                                          */
#/*                                                                          */
#/* Currently supported devices:                                             */
#/*                                                                          */
#/* 12F508          12F629          12F675          12F683          12F1822  */
#/*                                                                          */
#/* 16F88           16F505          16F627          16F628A         16F630   */
#/* 16F684          16F688          16F690          16F716          16F876A  */
#/* 16F877A         16F886          16F887          16F18313        16F18323 */
#/* 16F18324        16F18325        16F18326        16F18344        16F18345 */
#/* 16F18346                                                                 */
#/*                                                                          */
#/* 18F2420         18F2455         18F2520         18F2550         18F4420  */
#/* 18F4455         18F4520         18F4550                                  */
#/*                                                                          */
#/* Additional devices can be added in the PIC_DEVICES.py file.              */
#/****************************************************************************/



NOTE: From Version 1.0.3 updates to the electronic circuit have been made,
see file RPiPicProgrammer.pdf for details.



Linux Packages For PIC Microchip Development
============================================
apt-get install gpsim
apt-get install gputils
apt-get install sdcc



Tools From Linux Packages For PIC Microchip Development
=======================================================
Cross compile a PIC Microchip assembly text file.
gpasm -w 1 -c [FILE_NAME].asm

Link a PIC Microchip object file and produce a Intel HEX formatted object file.
gplink -o [FILE_NAME].hex [FILE_NAME].o

Simulate a compiled PIC Microchip code file for debugging.
gpsim -s [FILE_NAME].cod

PIC Microchip disassembler.
gpdasm

Discard symbols from a PIC Microchip object file.
gpstrip

PIC Microchip object file viewer.
gpvo

PIC Microchip cod file viewer.
gpvc

PIC Microchip object library manager.
gplib



PIC Microchip Hardware Requirements
===================================
VPP 13V 100 mA
Varies from device to device, see device specifications.

VDD >=2.0V <=6.5V += 0.25V 40 mA
Officially Microchip specifies to verify the device is programmed by verifying
at each voltage between 2V and 6.5V in steps of 0.25V. When not verified in
this way the device is considered programmed for development purposes.

While programming a device it maybe required to pull a pin named PGM low using
a high value resistor, to prevent it floating and interfering with the
programming process.


Raspberry Pi GPIO Requirements
-----------------------------
OUTPUT      VDD Switch
OUTPUT      PRG Switch
OUTPUT      Data Out
INPUT       Data In
OUTPUT      Clock



RPiPIC PIC Microchip Programmer Commands
========================================
./RPiPIC.py -P
Power on current device. Used for test button, test program testing.

./RPiPIC.py -O
Power off current device. Used for test button, test program testing.

./RPiPIC.py -L
List currently supported PIC devices.

./RPiPIC.py -C [PIC_DEVICE]
Display device memory checksum.

./RPiPIC.py -D [PIC_DEVICE] <MEMORY_AREA> <START_ADDRESS> <END_ADDRESS>
Read memory from device and display. If no options are provided, display all memory.
<MEMORY_AREA>   - See -LM option for memory area options.
<START_ADDRESS> - Address to start displaying data.
<END_ADDRESS>   - Address to stop displaying data.

./RPiPIC.py -B [PIC_DEVICE]
Blank check device.
Check if memory areas are erase and blank, ready for programming.

./RPiPIC.py -E [PIC_DEVICE] <NO_STORE>
Erase all device memory.
<NO_STORE>      - Factory data and program memory is not retained.

./RPiPIC.py -EC [PIC_DEVICE]
Erase all device config.

./RPiPIC.py -R [PIC_DEVICE] [FILE_NAME]
Read memory from device and save to .hex file.

./RPiPIC.py -W [PIC_DEVICE] [FILE_NAME]
Read .hex file and write to device memory.

./RPiPIC.py -V [PIC_DEVICE] [FILE_NAME]
Read memory from device and read .hex file, then verify data is identical.

./RPiPIC.py -LM [PIC_DEVICE]
List device memory areas.

./RPiPIC.py -LD [PIC_DEVICE] [MEMORY_AREA] [DATA]
Load data into a device memory area.
EXAMPLES:
./RPiPIC.py -LD 16F684 CONFIG:BOR_CAL 23F8
./RPiPIC.py -LD 16F684 CONFIG:CAL 3FFF
./RPiPIC.py -LD 16F684 CONFIG:ID 0005000100020001



Project Files
-------------
A full write up for this project can be found at the web site:
http://www.newsdownload.co.uk/

├── GNU-GeneralPublicLicense.txt
├── README.txt           - This file.
├── RPiPicProgrammer.pdf - Programmer circuit diagram.
├── RPiPIC.py            - PIC Microchip programmer application.
├── PIC_DEVICES.py       - Definitions of supported PIC Microchip devices.
├── HEX_File.py          - Intel HEX file format handler.
├── PIC_API.py           - API level PIC Microchip device control.
├── PIC.py               - Low level PIC Microchip device control.
└── TEST_ASM             - Example projects for supported PIC Microchip devices.
    ├── INCLUDE          - PIC Microchip device asm include files.
    │   ├── P12F1822.INC
    │   ├── P12F508.INC
    │   ├── P12F629.INC
    │   ├── P12F675.INC
    │   ├── P12F683.INC
    │   ├── P16F18326.INC
    │   ├── P16F18346.INC
    │   ├── P16F505.INC
    │   ├── P16F627.INC
    │   ├── P16F628A.INC
    │   ├── P16F630.INC
    │   ├── P16F684.INC
    │   ├── P16F688.INC
    │   ├── P16F690.INC
    │   ├── P16F716.INC
    │   ├── P16F876A.INC
    │   ├── P16F877a.INC
    │   ├── P16F886.INC
    │   ├── P16F887.INC
    │   ├── P16F88.INC
    │   ├── P18F2420.INC
    │   ├── P18F2455.INC
    │   ├── P18F2520.INC
    │   ├── P18F4520.INC
    │   └── P18F4550.INC
    ├── PIC12F1822      - Program for PIC12F1822 using test button and LED.
    │   ├── Build.sh
    │   └── PIC12F1822.asm
    ├── PIC12F508       - Program for PIC12F508 using test button and LED.
    │   ├── Build.sh
    │   └── PIC12F508.asm
    ├── PIC12F629       - Program for PIC12F629 using test button and LED.
    │   ├── Build.sh
    │   └── PIC12F629.asm
    ├── PIC12F675       - Program for PIC12F675 using test button and LED.
    │   ├── Build.sh
    │   └── PIC12F675.asm
    ├── PIC12F683       - Program for PIC12F683 using test button and LED.
    │   ├── Build.sh
    │   └── PIC12F683.asm
    ├── PIC16F18326     - Program for PIC16F18326 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F18326.asm
    ├── PIC16F18346     - Program for PIC16F18346 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F18346.asm
    ├── PIC16F505       - Program for PIC16F505 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F505.asm
    ├── PIC16F627       - Program for PIC16F627 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F627.asm
    ├── PIC16F628A      - Program for PIC16F628A using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F628A.asm
    ├── PIC16F630       - Program for PIC16F630 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F630.asm
    ├── PIC16F684       - Program for PIC16F684 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F684.asm
    ├── PIC16F688       - Program for PIC16F688 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F688.asm
    ├── PIC16F690       - Program for PIC16F690 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F690.asm
    ├── PIC16F716       - Program for PIC16F716 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F716.asm
    ├── PIC16F876A      - Program for PIC16F876A using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F876A.asm
    ├── PIC16F877A      - Program for PIC16F877A using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F877A.asm
    ├── PIC16F88        - Program for PIC16F88 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F88.asm
    ├── PIC16F886       - Program for PIC16F886 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F886.asm
    ├── PIC16F887       - Program for PIC16F887 using test button and LED.
    │   ├── Build.sh
    │   └── PIC16F887.asm
    ├── PIC18F2420      - Program for PIC18F2420 using test button and LED.
    │   ├── Build.sh
    │   └── PIC18F2420.asm
    ├── PIC18F2455      - Program for PIC18F2455 using test button and LED.
    │   ├── Build.sh
    │   └── PIC18F2455.asm
    ├── PIC18F2520      - Program for PIC18F2520 using test button and LED.
    │   ├── Build.sh
    │   └── PIC18F2520.asm
    ├── PIC18F4520      - Program for PIC18F4520 using test button and LED.
    │   ├── Build.sh
    │   └── PIC18F4520.asm
    └── PIC18F4550      - Program for PIC18F4550 using test button and LED.
        ├── Build.sh
        └── PIC18F4550.asm



Configuration
-------------
The only configuration required is to edit the GPIO pin allocation in the
PIC.py project file to the GPIO allocation used, if different pins to the ones
specified on the circuit diagram are used.



Adding Devices
--------------
The file PIC_DEVICES.py contains definitions of the memory map for each
supported PIC device. PIC devices can be added by creating an additional memory
map for the device. There are a few reasons why a particular PIC device may not
work with the current release of this software.

1. The process of adding a device is to define the memory map of the device in
   the application. It is possible that the current data definitions in the
   application may not be sufficient to properly define a memory map for a
   specific device.

2. Currently specific processes are selected in the code rather than the device
   definition.

An example memory map would be:

PIC_DEVICE.append([
"16F630",
   [
      [PICMEM_RW|PICMEM_EEPROM|PICMEM_DATA,
                                             0x0000, 0x0080, 0x4200, [0x00FF]],
      [PICMEM_RW|PICMEM_EEPROM|PICMEM_PROG,
                                             0x0000, 0x03FF, 0x0000, [0x3FFF]],
      [PICMEM_RW|PICMEM_EEPROM|PICMEM_PROG|PICMEM_ST|PICMEM_RE|PICMEM_OSC_CAL,
                                             0x03FF, 0x0001, 0x03FF, [0x3FFF]],
      [PICMEM_WO|PICMEM_EEPROM|PICMEM_CONF|PICMEM_ID,                
                                             0x0000, 0x0004, 0x4000, [0x3FFF]],
      [PICMEM_RO|PICMEM_EEPROM|PICMEM_CONF|PICMEM_ID,
                                             0x2000, 0x0004, 0x4000, [0x3FFF]],
      [PICMEM_RO|PICMEM_EEPROM|PICMEM_CONF|PICMEM_DEV_ID,
                                             0x2006, 0x0001, 0x4006, [0x0000]],
      [PICMEM_WO|PICMEM_EEPROM|PICMEM_CONF|PICMEM_CONFIG,
                                             0x0007, 0x0001, 0x400E, [0x31FF]],
      [PICMEM_RO|PICMEM_EEPROM|PICMEM_CONF|PICMEM_CONFIG,
                                             0x2007, 0x0001, 0x400E, [0x31FF]],
   ]
])


The device name is specified first, then within that definition is the
definition for the devices memory map. Each line of the definition defines an
area of the memory.

First if the memory is read only PICMEM_RO, write only PICMEM_RO or read/write
PICMEM_RW.

Next the physical type of memory, currently only PICMEM_EEPROM supported.

Next the memory region type, PICMEM_DATA data memory read and writable
by a program. PICMEM_PROG program memory. PICMEM_CONF device configuration
memory.

Next the memory region segment name, e.g. PICMEM_OSC_CAL oscillator calibration
word. If PICMEM_ST is specified, this application will read the value of the
memory before erasing, and where PICMEM_RE is specified the value will be
restored here after erasing.

The final four words of data for a memory region are:

Device memory address. The address of the memory on the physical device.

Device memory size. The number of words in of memory available in this region.

Assembly memory address. For data and program memory the device address
typically starts at 0x0000 for both. So in the assembly program a directive
ORG 0x4000 can be used for example to define data memory content. The
programming specification of the device can define this value, so if it is
defined in the specification, that value must be used.

The last value is the configuration mask, used to prevent verification errors
where configuration bits are unsettable, and always read as a 0 or 1.
This can be a single word applied to all data, or a list of mask values.



RELEASE TEST PROCEDURE
======================
Perform the following procedure on each supported device to verify operation
before checking in to source control.

./RPiPIC.py -E 16F877A
./RPiPIC.py -B 16F877A
./RPiPIC.py -W 16F877A TEST_ASM/PIC16F877A/PIC16F877A.hex
./RPiPIC.py -B 16F877A
./RPiPIC.py -V 16F877A TEST_ASM/PIC16F877A/PIC16F877A.hex
./RPiPIC.py -D 16F877A
./RPiPIC.py -P
Press test button to check the test application flashes the LED three times.
./RPiPIC.py -O

rpipic's People

Contributors

birchjd avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

rpipic's Issues

Adding support for PIC16F1828

hello,

can you please add support for PIC16F1828 ? I am quite new into pic devices and would be happy if you can show some pointer for this.
thanks

Adding a PIC clarifications

Trying to understand how to add a PIC to the devices list:

What I am not getting is the Obj Address; how is that identified through documentation?

Mostly for other readers:
I noticed this part in PIC_DEVICES:
#/* PIC Device Name, /
#/
[ /
#/
Memory Type, PIC Memory Area, Start Address, Length, Obj Address, /
#/
Store/Restore Mask, /
#/
... /
#/
], */

Where I think Memory Type and PIC Memory Area should be grouped together to avoid confusion.
Something like maybe: (Memory Type, PIC Memory Area), Start Address, ...

Took a bit to figure out.
Also like to clear up that Start Address for writes is based off of what the Load Configuration command sets the PC to

Working with a 16F18346 btw
Load Config sets PC to 0x8000

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.