Changes

Jump to navigation Jump to search
no edit summary
Line 39: Line 39:     
Currently (Feb 2017), you can get the required software from:
 
Currently (Feb 2017), you can get the required software from:
http://www.microchip.com/development-tools/downloads-archive
+
:http://www.microchip.com/development-tools/downloads-archive
    
Download MPLAB IDE 32-bit Windows v8.66:
 
Download MPLAB IDE 32-bit Windows v8.66:
http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB_IDE_v8_66.zip
+
:http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB_IDE_v8_66.zip
http://dvswitch.org/files/AllStarLink/Voter/MPLAB_IDE_v8_66.zip
+
:http://dvswitch.org/files/AllStarLink/Voter/MPLAB_IDE_v8_66.zip
    
Download MPLAB C Compiler for PIC24 and dsPIC DSCs v3.31 '''NOT v.3.25''':
 
Download MPLAB C Compiler for PIC24 and dsPIC DSCs v3.31 '''NOT v.3.25''':
http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc30-v3_31-windows-installer.exe
+
:http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc30-v3_31-windows-installer.exe
http://dvswitch.org/files/AllStarLink/Voter/mplabc30-v3_31-windows-installer.exe
+
:http://dvswitch.org/files/AllStarLink/Voter/mplabc30-v3_31-windows-installer.exe
    
Optionally, install Windows Virtual PC and XP Mode. This is getting to be pretty old software, so running it under XP Mode may be a good idea, so we can keep it isolated (install it in a virtual machine). It does run fine in Windows 7.
 
Optionally, install Windows Virtual PC and XP Mode. This is getting to be pretty old software, so running it under XP Mode may be a good idea, so we can keep it isolated (install it in a virtual machine). It does run fine in Windows 7.
   −
Run the MPLAB IDE installer. You don't need to install the HI-TECH C Compiler at the end (click no).
+
To setup the compile/build environment, follow these steps:
 
+
*Run the MPLAB IDE installer. You don't need to install the HI-TECH C Compiler at the end (click no)
Run the MPLAB C Compiler installer.
+
*Run the MPLAB C Compiler installer
 
+
*Select Legacy Directory Name
Select Legacy Directory Name.
+
*'''Select Lite Compiler'''
 
+
*Go to: https://github.com/AllStarLink
'''Select Lite Compiler'''
+
*Follow the links to: voter --> Clone or Download --> Download Zip. That will get you voter-master.zip which is a download of the whole VOTER tree from GitHub.
 
+
*Extract it somewhere (ie. in the XP Mode Virtual PC)
Go to: https://github.com/AllStarLink
+
*Launch the MPLAB IDE
 
+
*Go to Configure --> Settings --> Projects and de-select one-to-one project mode.
Follow the links to: voter --> Clone or Download --> Download Zip
  −
 
  −
That will get you voter-master.zip which is a download of the whole VOTER tree from GitHub.
  −
 
  −
Extract it somewhere (ie. in the XP Mode Virtual PC).
  −
 
  −
Launch the MPLAB IDE.
  −
 
  −
Go to Configure --> Settings --> Projects and de-select one-to-one project mode.
         
==Bootloader==
 
==Bootloader==
   −
If you need to load the bootloader in to a fresh board, you will need to follow these steps.
+
If you need to load the bootloader in to a fresh board, you will need to follow these steps:
 
+
*Go to Project --> Open --> voter-bootloader.mcp --> Open (it is in the voter-bootloader folder of the GitHub source)
Go to Project --> Open --> voter-bootloader.mcp --> Open (it is in the voter-bootloader folder of the GitHub source)
+
*Go to File --> Import --> voter-bootloader --> ENC_C30.cof --> Open '''This step is missing from the original procedure.'''
 +
*Remove JP7 on the VOTER Board. This is necessary to allow programming by the PICKit2/PICKit3 device.
 +
*Attach the PICKIT2/PICKit3 device to J1 on the VOTER board. Note that Pin 1 is closest to the power supply modules (as indicated on the board).
 +
*If you have not already selected a programming device, go to Programmer --> Select Device and choose PICKit3 (or PICKit2, depending on what you are using).
 +
*Go to Programmer --> Program. This will program the bootloader firmware into the PIC device on the board.
   −
Go to File --> Import --> voter-bootloader --> ENC_C30.cof --> Open '''This step is missing from the original procedure.'''
+
If you want to change the default IP address from 192.168.1.11 in the bootloader:
 
+
*Select View --> Program Memory (from the top menu bar)
Select View --> Program Memory (from the top menu bar).
+
*Hit Control-F (to "find") and search for the digits "00A8C0".
 
+
*These should be found at memory address "03018".
If you want to change the default IP address from 192.168.1.11:
  −
 
  −
Hit Control-F (to "find") and search for the digits "00A8C0".
  −
 
  −
These should be found at memory address "03018".
      
The "A8C0" at 03018 represents the hex digits C0 (192) and A8 (168) which are the first two octets of the IP address. The six digits to enter are 00 then the SECOND octet of the IP address in hex then the FIRST octet of the IP address in hex.
 
The "A8C0" at 03018 represents the hex digits C0 (192) and A8 (168) which are the first two octets of the IP address. The six digits to enter are 00 then the SECOND octet of the IP address in hex then the FIRST octet of the IP address in hex.
Line 92: Line 82:  
The "0B01" at 0301A represents the hex digits 0B (11) and 01 (1) which are the second two octets of the IP address. The six digits to enter are 00 then the FOURTH octet of the IP address in hex then the THIRD octet of the IP address in hex.
 
The "0B01" at 0301A represents the hex digits 0B (11) and 01 (1) which are the second two octets of the IP address. The six digits to enter are 00 then the FOURTH octet of the IP address in hex then the THIRD octet of the IP address in hex.
   −
Otherwise, if you just want to load the bootloader...
+
Once you have modified the address to your desired IP, follow the programming procedure (above).
 
  −
Remove JP7 on the VOTER Board. This is necessary to allow programming by the PICKit2/PICKit3 device.
  −
 
  −
Attach the PICKIT2/PICKit3 device to J1 on the VOTER board. Note that Pin 1 is closest to the power supply modules (as indicated on the board).
  −
 
  −
If you have not already selected a programming device, go to Programmer --> Select Device and choose PICKit3 (or PICKit2, depending on what you are using).
  −
 
  −
Then go to Programmer --> Program. This will program the bootloder firmware into the PIC device on the board.
         
==Firmware==
 
==Firmware==
   −
To compile the firmware (if you want to make custom changes)...
+
To compile the firmware (if you want to make custom changes):
 
+
*Go to Project --> Open --> navigate to board-firmware and open the .mcp file for the flavor of firmware you want to compile. They are in the board-firmware folder of the GitHub source.
Go to Project --> Open --> navigate to board-firmware and open the .mcp file for the flavor of firmware you want to compile. They are in the board-firmware folder of the GitHub source.
+
*'''NOTE''': the .mcp files with the "smt" suffix are for the RTCM (built with SMT parts). The non-smt files are for the ORIGINAL through-hole VOTER boards. The difference is that the VOTER uses a dsPIC33FJ128GP802 and the RTCM uses a dsPIC33FJ128GP804.
 
+
*Go to Project --> Build Configuration and select "Release". This may not be necessary (I don't believe that option is used in the firmware), but it removes the compiler option of __DEBUG being passed, so theoretically it would build "normal" firmware.
'''NOTE''': the .mcp files with the "smt" suffix are for the RTCM (built with SMT parts). The non-smt files are for the ORIGINAL through-hole VOTER boards. The difference is that the VOTER uses a dsPIC33FJ128GP802 and the RTCM uses a dsPIC33FJ128GP804.
+
*Go to Configure --> Select Device and choose the appropriate device for your board from the Device list. If you don't select the right one, the board will not boot. Select dsPIC33FJ128GP802 for the VOTER, and dsPIC33FJ128GP804 for the RTCM.
 
+
*Now, if you go to Project --> Build All it should compile everything and show you "Build Succeeded".
Go to Project --> Build Configuration and select "Release". This may not be necessary (I don't believe that option is used in the firmware), but it removes the compiler option of __DEBUG being passed, so theoretically it would build "normal" firmware.
  −
 
  −
Go to Configure --> Select Device and choose the appropriate device for your board from the Device list. If you don't select the right one, the board will not boot. Select dsPIC33FJ128GP802 for the VOTER, and dsPIC33FJ128GP804 for the RTCM.
  −
 
  −
Now, if you go to Project --> Build All it should compile everything and show you "Build Succeeded".
      
A .cry file should be in the board-firmware folder. You can load this with the ENC Loader.
 
A .cry file should be in the board-firmware folder. You can load this with the ENC Loader.
36

edits

Navigation menu