Difference between revisions of "DsPIC30F 5011 Development Board"

From OpenCircuits
Jump to navigation Jump to search
Line 343: Line 343:
 
#Use [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en019469&part=SW007002 MPLAB IDE] to burn hex code (*.hex) to devices.
 
#Use [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en019469&part=SW007002 MPLAB IDE] to burn hex code (*.hex) to devices.
  
−
==Using ICD 2 Programmer==
+
==Programming Tips==
  
−
===MPLAB IDE===
+
===Memory Map for 5011===
−
*Install IDE and USB Driver
+
+-------------------------------------+ 0x000000 to 0x00AFFE<br>
−
# Do '''NOT''' connect ICD 2 (via USB) to PC.
+
|..............Flash.................|<br>
−
# Install MPLAB IDE.
+
|.........(22K x16 bits)..........|<br>
−
# Install USB driver by following the instruction in (C:\Program Files\Microchip\MPLAB IDE\ICD2\Drivers\Ddicd2.htm)
+
+-------------------------------------+ 0x00B000 to 0x7FFBFE<br>
 +
|............Reserved..............|<br>
 +
+-------------------------------------+ 0x7FFC00 to 0x7FFFFE<br>
 +
|.............EEPROM............|<br>
 +
|...........(1K x 8 bits)..........|<br>
 +
+-------------------------------------+ 0x800000 to 0x8005BE<br>
 +
|................PE..................|<br>
 +
+-------------------------------------+ 0x8005C0 to 0x8005FE<br>
 +
|..............Unit ID...............|<br>
 +
+-------------------------------------+ 0x800600 to 0xF7FFFE<br>
 +
|............Reserved..............|<br>
 +
+-------------------------------------+ 0xF80000 to 0xF8000E<br>
 +
|........Config Registers.......|<br>
 +
+-------------------------------------+ 0xF80010 to 0xFEFFFE<br>
 +
|............Reserved..............|<br>
 +
+-------------------------------------+ 0xFF0000 to 0xFF0002<br>
 +
|..............Device ID...........|_______________________'''0x0080'''<br>
 +
+-------------------------------------+ 0xFF0002 to 0xFF0004<br>
 +
|............Reserved..............|<br>
 +
+-------------------------------------+ 0xFFFFFE<br>
  
−
*Establish Conncetion with ICD 2
+
===Data Location===
−
# Connect ICD 2 to PC. Do '''NOT''' connect target (via 6-pin cable) to ICD 2.
+
{| border="1" cellspacing="0" cellpadding="5"
−
# Run MPLAB IDE on PC.
+
|+ Table 7.1 Data Location
−
# Open an existing project (Project>Open)
+
! Type !! Description !! Example
−
# Select MPLAB ICD 2 as the current programmer (Programmer>Select Programmer>MPLAB ICD 2)
+
|-valign="top"
−
# Configure the USB Interface (Programmer>Settings, Communications Tab)
+
| _XBSS(N) <sup>[1]</sup>
−
# Establish connection with ICD 2 (Programmer>Connect)<br>You should see "Connecting to MPLAB ICD 2...Connected."<br>You should also see Warnings regarding downloading OS to device, invalid device IDs, and/or running self tests. Ignore these warnings since the target board has not been connected yet.
+
| RAM Data in X-memory, aligned at N, no initilization
−
 
+
| int _XBSS(32) xbuf[16];
−
*Establish Connection with Target
+
|-valign="top"
−
# Uncheck the option “Power target circuit from MPLAB ICD” (Programmer>Settings, Power Tab). '''Place''' Jumper on target board. Power the Target.
+
| _XDATA(N) <sup>[1]</sup>
−
# Establish connection with target through ICD 2 (Programmer>Connect).
+
| RAM Data in X-memory, aligned at N, with initilization
−
# See results of self test (Programmer>Settings, Status Tab).
+
| int _XDATA(32) xbuf[] = {1, 2, 3, 4, 5};
−
 
+
|-valign="top"
−
*Program the Device
+
| _YBSS(N) <sup>[1]</sup>
−
# Programmer>Program
+
| RAM Data in Y-memory, aligned at N, no initilization
−
 
+
| int _YBSS(32) ybuf[16];
−
===PikLab===
+
|-valign="top"
−
*Under construction
+
| _YDATA(N) <sup>[1]</sup>
−
 
+
| RAM Data in Y-memory, aligned at N, with initilization
−
===dspicprg===
+
| int _YDATA(32) ybuf[16] = {1, 2, 3, 4, 5};
−
*Under construction
+
|-valign="top"
 +
| __attribute__((space(const)))
 +
| Flash ROM data, constant, accessed by normal C statements, but 32K max.
 +
| int i __attribute__((space(const))) = 10;
 +
|-valign="top"
 +
| __attribute__((space(prog)))
 +
| Flash ROM data, read/write by program space visibility window (psv)
 +
| int i __attribute__((space(prog)));
 +
|-valign="top"
 +
| __attribute__((space(auto_psv)))
 +
| Flash ROM data, read by normal C statements, write by accessing psv
 +
| int i __attribute__((space(auto_psv)));
 +
|-valign="top"
 +
| __attribute__((space(psv)))
 +
| Flash ROM data, read/write by (psv)
 +
| int i __attribute__((space(psv)));
 +
|-valign="top"
 +
| _EEDATA(N) <sup>[1]</sup>
 +
| ROM Data in EEPROM, aligned at N, read/write with psv
 +
| int _EEDATA(2) table[]={0, 1, 1, 2, 3, 5, 8};<br>
 +
  void main(){<br>
 +
    PSVPAG = __builtin_psvpage(&table);<br>
 +
    CORCONbits.PSV = 1;<br>
 +
    ...<br>
 +
    if(table[2]){<br>
 +
        ...<br>
 +
    }<br>
 +
  }
 +
|-valign="top"
 +
| _PERSISTENT
 +
| RAM Data, data remain after reset
 +
| int _PERSISTENT var1, var2;
 +
|-valign="top"
 +
| _NEAR
 +
| RAM Data at near section
 +
| int _NEAR var1, var2;
 +
|-valign="top"
 +
| _ISR
 +
| Interrupt service rountine
 +
| void _ISR _INT0Interrupt(void);
 +
|-valign="top"
 +
| _ISRFAST
 +
| Fast interrupt service rountine
 +
| void _ISRFAST _T0Interrupt(void);
 +
|-
 +
|}
 +
#N must be a power of two, with a minimum value of 2.
  
 +
===Driver Development===
 +
{| border="1" cellspacing="0" cellpadding="5"
 +
|+ Table 7.2 Driver Development
 +
! Item !! Description !! Start Date !! Completion Date !! Test Date
 +
|-valign="top"
 +
| DI/DO and 10ms Timer interrupt
 +
| Simple switching of LEDs
 +
| 07 Nov 2006 || 08 Nov 2006 || 15 Nov 2006
 +
|-valign="top"
 +
| UART
 +
| RS232 and RS485
 +
| 08 Nov 2006 || 10 Nov 2006 || 16 Nov 2006
 +
|-valign="top"
 +
| I<sup>2</sup>C
 +
| DAC
 +
| 13 Nov 2006 || 13 Nov 2006 || Pending
 +
|-valign="top"
 +
| Analog I/O
 +
| Sampling analog signal
 +
| || ||
 +
|-valign="top"
 +
| Usage of Standard C-libraries
 +
| 1. math.h<br>2. stdlib.h
 +
| 08 Nov 2006 || 08 Nov 2006 || 21 Nov 2006
 +
|-valign="top"
 +
| Usage of DSP libraries
 +
| 1. Vector<br>2. Matrix<br> 3. DFT
 +
| || ||
 +
|-valign="top"
 +
| Usage of Buildin libraries
 +
| 1. __builtin_add<br>2. __builtin_divud<br> 3. __builtin_clr
 +
| || ||
 +
|-
 +
|}
  
 
==Programming==
 
==Programming==

Revision as of 18:33, 22 November 2006

Introduction

Web Page

  • Microchip
    • dsPIC 16-bit Embedded Control Solutions Brochure
    • dsPIC30F Family Overview

Forum

  • PICList: Discussion on older PIC systems (not dsPIC)
  • PicKit: Discussion on PICkit/PICkit 2 programmers

References

Features of dsPIC

  • Advantages
    • 2.5 to 5V
    • High current/sink source I/O pins: 25mA
    • with DSP Instruction Set
    • Dual programming techniques: ICSP and RTSP
    • UART: up to 2 modules
    • I2C: up to 1Mbps
    • 10-bit A/D, 1.1 Msps
    • 12-bit A/D, 500 ksps
    • around 64K flash, 4K RAM, 1K eeprom
  • Disadvantages
    • No DAC

Selected Chip

  • dsPIC30F, dsPIC30F5011


Programming Methods

  • There are 2 programming methods: In-Circuit Serial Programming (ICSP) and Run-Time Self-Programming (RTSP)
  • ICSP allows the devices to be programmed after being placed in a circuit board.
  • RTSP allows the devices to be programmed when an embedded program is already in operation.

ICSP

  • Two types of ICSP are available: ICSP and Enhanced ICSP. Both of them require setting ^MCLR to VIHH (9V – 13.25V).
  • Standard ICSP
    • Use external programmer (e.g. MPLAB® ICD 2, MPLAB® PM3 or PRO MATE® II) only.
    • Required low-level programming to erase, program and verify the chip.
    • Slower, because codes are serially executed.
    • Refer to Section 11 for programming in ICSP.
    • Program memory can be erased using Normal-Voltage (4.5 – 5.5V) or Low-Voltage (2.5V – 4.5V).
  • Enhanced ICSP
    • Use external programmer and Programming Executive (PE).
    • PE is stored in the on-chip memory.
    • PE allows faster programming.
    • PE can be downloaded to the chip by external programmer using the standard ICSP method.
    • PE contains a small command set to erase, program and verify the chip, avoiding the need of low-level programming.
    • Refer to Section 8 for programming the PE.
  • Hardware Interface
Table 3.1 Pin Used by ICSP
Pin Label Function Pin Number
^MCLR Programming Enable 7
VDD Power Supply 10, 26, 38, 57
VSS Ground 9, 25, 41, 56
PGC Serial Clock 17
PGD Serial Data 18


Table 3.2 Available Programmers in the Market
Product Name Interface with PC Interface with Device Price (US) Postage (US) Total (US)
MPLAB® ICD 2 USB/RS232 6-PIN RJ-12 connector $159.99 - -
PRESTO PIC Programmer Plus USB ? $200.16 $15.00 $215.16
Full Speed USB Microchip ICD2
Debugger and Programmer 		USB 6-PIN ICSP connector
6-PIN RJ-12 connector 		$72.00 $12.00 $84.00
Mini Microchip Compatible ICD2
Debugger and Programmer 		RS232 6-PIN ICSP connector
6-PIN RJ-12 connector 		$45.00 $10.00 $55.00
ICDX30 RS232 6-pin RJ-11 $51.00 $47.46 $98.46
Clone Microchip ICD2 RS232 6-pin flat cables $30.00 $12.00 $42.00


Table 3.3 DIY ICD 2 Programmer Circuit
Source Schematic PIC16F877A Bootloader
Patrick Touzet Yes HEX
Nebadje Yes Zip
  • Software Interface
    • The program can be written and compiled in an Integrated Development Environment (IDE) using either Assembly or C. The complied codes are then loaded to the device through the external programmer.


Table 3.4 Summary of IDE
Product Name Features OS Price (US$)
MPLAB® IDE Assembler Only Windows Free
MPLAB® C30 Assembler and C-Compiler Windows $895.00 (Free student version1)
Piklab 0.12.0 Assembler and C-Compiler Linux Free2
  1. Full-featured for the first 60 days. After 60 days only optimization level 1 can be enabled in the compiler. The compiler will continue to function after 60 days, but code size may increase.
  2. The current version supports external programmer ICD 2, but not yet tested.

RTSP

  • RTSP works in normal voltage (^MCLR no need to raise to VIHH).
  • No literature has mentioned the incorporation of Programming Executive (PE). Presumably, since Enhanced ICSP needs to set ^MCLR to VIHH, RTSP cannot use PE.
  • Refer to bootloader section.


Circuit Design and PCB

IC Requirements

Table 4.1 IC Requirements
Part No. Description Min Temp Max Temp Min Volt Max Volt Typ Cur Max Cur
dsPIC30F5011-30I/PT uP -40oC 85oC 2.5V [1] 5.5V 250mA
MAX3232ESE RS232 driver -40oC 85oC 3.0V 5.5V 0.3mA 1.0mA
ADM483E ANZ RS485 driver -40oC 85oC 4.5V 5.5V 0.036mA
DAC6574DGS 10-bit Quad-DAC I2C -40oC 105oC 2.7V 5.5V 0.6mA 0.9mA
74HC14D Quad-Schmitt Trigger -40oC 125oC 2.0V 6.0V 50mA
Overall -40oC 85oC 4.5V 5.5V <310mA [2]
  1. Minimum voltage measured is 3.3V (with 2 LEDs blinking) running at 30MHz.
  2. Measured current at 5V is 180mA (with 2 LEDs blinking only)

Module Board

  • Functions
    • Primary communication with other module boards via RS232 over short distance.
    • Secondary communication with benchtop via RS458 over longer distance.
    • Digital control I/O for 1 laser (e.g. on/off, detect temp overheat, current alarm)
    • Analog input for data acquisation on power, current and temperature
    • Analog output for power and current control
Table 4.2 Module
Digital Input Digital Output Analog Input Analog Output
1. ICSP 1. LED
2. Bi-color LED
3. RS232
4. RS458
5. Case temp overheat
6. Laser on/off 1,2
7. Interlock
8. Digital ctrl
9. Current 0,1 alarm
 1. Case temp
2. pow 0,1
3. cur0
4. temp0 		1. 10-bit DAC

Benchtop

  • Functions
    • Primary communciation with module boards via RS485
    • Secondary communication with other benchtops via RS232
    • Digital I/O control for 2 lasers
    • Analog inputs on power, current and temperature
    • Analog outputs for power and current control
    • LCD display and rotary key for user input
Table 4.3 Base Benchtop
Digital Input Digital Output Analog Input Analog Output
1. ICSP
2. Rotary Key
3. Push Buttons 		1. LED
2. RS232
3. RS458
4.LCD display
5. Buzzer
6. Digital Ctrl 0,1 		1. Case temp
2. CurrentDetect 0,1
3. PowerDetect 0,1,2,3
4. TempDetect 		1. 10-bit DAC (PowerCurrentCtrl 0,1)

Development Environment

Windows

PIC setup win.JPG

  • C-Compiler, Assembler and Linker are under GNU license.
    • MPLAB C30 C Compiler (*.c -> *.s)
    • MPLAB ASM30 Assembler (*.s -> *.o)
    • MPLAB LINK30 Linker (*.o -> *.exe)
  • PA optimizer, simulator, runtime libraries, header files, include files, and linker scripts are not covered by GNU. Reference is here.
  • Microchip has integrated ASM30, LINK30, assembly header files, linker scripts in MPLAB IDE, which is free for download.
  • MPLAB C30 costs US$895. A 60-day free student version is also available. After 60-days, the optimizer is automatically disabled, while other tools can still function properly. Refer to Table 3.4.


Table 5.1 C Libraries in MPLAB C30
Library Directory
(\\Microchip\MPLAB C30)		 Major functions
DSP Library
(e.g. libdsp-coff.a) 		\lib
\src\dsp
\support\h 		Vector, Matrix, Filter, etc.
16-Bit Peripheral Libraries
(e.g. libp30F5011-coff.a) 		\lib
\src\peripheral
\support\h 		ADC12, IOPort, UART, I2C, etc.
Standard C Libraries
(e.g. libc-coff.a, libm-coff.a, libpic-coff.a) 		\lib
\src\libm
\include 		stdio.h, time.h, float.h, math.h,
MPLAB C30 Built-in Functions none _buildin_addab, _buildin_add, _buildinmpy, etc

Linux

PIC setup linux.JPG

  • C Compiler, Assembler and Linker are under GNU license.
    • The code can be downloaded from Microchip at here.
    • Current MPLAB ASM30 Assembler: v2.04
    • Current MPLAB C30 Compiler: v2.04
  • John Steele Scott has made templates that can be readily used by Debian-based systems. Someone at http://noel.feld.cvut.cz/dspic/ has done the necessary conversion to *.deb already.
    • Download pic30-1.32-debian.tar.bz2 for Template v1.32. (For v2.01, please goto pic30-debian-2.01.tar.bz2).
    • Download pic30-binutils_1.32-1_i386.deb for the assember.
    • Download pic30-gcc_1.32-1_i386.deb for the compiler.
  • Important Note: Only the compiler is free. The header files and library is owned by Microchip.
    • Thomas Sailer suggested to download the Student version of C30 compiler and then build the libraries without source code. A package template for Fedora system is available here.
    • Instructions for filling the upstream direction is available here.
    • Alteratively, Stephan Walter has started a project to develop C Runtime Library for dsPIC.
      • Current libraries in version 0.1.1 include: assert.h, cdefs.h, ctype.h, errno.h, inttypes.h, stdint.h, stdio.h, stdlib.h, string.h
  • Burning Program Codes to Target Board
  1. Use 'dspicprg and dspicdmp' utilities developed by Homer Reid to burn hex code (*.hex) to devices. See Reference here. Through serial port only?
  2. Use Piklab IDE. Details on file format not known.
  3. Use MPLAB IDE to burn hex code (*.hex) to devices.

Programming Tips

Memory Map for 5011

+-------------------------------------+ 0x000000 to 0x00AFFE
|..............Flash.................|
|.........(22K x16 bits)..........|
+-------------------------------------+ 0x00B000 to 0x7FFBFE
|............Reserved..............|
+-------------------------------------+ 0x7FFC00 to 0x7FFFFE
|.............EEPROM............|
|...........(1K x 8 bits)..........|
+-------------------------------------+ 0x800000 to 0x8005BE
|................PE..................|
+-------------------------------------+ 0x8005C0 to 0x8005FE
|..............Unit ID...............|
+-------------------------------------+ 0x800600 to 0xF7FFFE
|............Reserved..............|
+-------------------------------------+ 0xF80000 to 0xF8000E
|........Config Registers.......|
+-------------------------------------+ 0xF80010 to 0xFEFFFE
|............Reserved..............|
+-------------------------------------+ 0xFF0000 to 0xFF0002
|..............Device ID...........|_______________________0x0080
+-------------------------------------+ 0xFF0002 to 0xFF0004
|............Reserved..............|
+-------------------------------------+ 0xFFFFFE

Data Location

Table 7.1 Data Location
Type Description Example
_XBSS(N) [1] RAM Data in X-memory, aligned at N, no initilization int _XBSS(32) xbuf[16];
_XDATA(N) [1] RAM Data in X-memory, aligned at N, with initilization int _XDATA(32) xbuf[] = {1, 2, 3, 4, 5};
_YBSS(N) [1] RAM Data in Y-memory, aligned at N, no initilization int _YBSS(32) ybuf[16];
_YDATA(N) [1] RAM Data in Y-memory, aligned at N, with initilization int _YDATA(32) ybuf[16] = {1, 2, 3, 4, 5};
__attribute__((space(const))) Flash ROM data, constant, accessed by normal C statements, but 32K max. int i __attribute__((space(const))) = 10;
__attribute__((space(prog))) Flash ROM data, read/write by program space visibility window (psv) int i __attribute__((space(prog)));
__attribute__((space(auto_psv))) Flash ROM data, read by normal C statements, write by accessing psv int i __attribute__((space(auto_psv)));
__attribute__((space(psv))) Flash ROM data, read/write by (psv) int i __attribute__((space(psv)));
_EEDATA(N) [1] ROM Data in EEPROM, aligned at N, read/write with psv int _EEDATA(2) table[]={0, 1, 1, 2, 3, 5, 8};
 void main(){

    PSVPAG = __builtin_psvpage(&table);

    CORCONbits.PSV = 1;

    ...

    if(table[2]){

       ...

    }

 }
_PERSISTENT RAM Data, data remain after reset int _PERSISTENT var1, var2;
_NEAR RAM Data at near section int _NEAR var1, var2;
_ISR Interrupt service rountine void _ISR _INT0Interrupt(void);
_ISRFAST Fast interrupt service rountine void _ISRFAST _T0Interrupt(void);
  1. N must be a power of two, with a minimum value of 2.

Driver Development

Table 7.2 Driver Development
Item Description Start Date Completion Date Test Date
DI/DO and 10ms Timer interrupt Simple switching of LEDs 07 Nov 2006 08 Nov 2006 15 Nov 2006
UART RS232 and RS485 08 Nov 2006 10 Nov 2006 16 Nov 2006
I2C DAC 13 Nov 2006 13 Nov 2006 Pending
Analog I/O Sampling analog signal
Usage of Standard C-libraries 1. math.h
2. stdlib.h 		08 Nov 2006 08 Nov 2006 21 Nov 2006
Usage of DSP libraries 1. Vector
2. Matrix
3. DFT
Usage of Buildin libraries 1. __builtin_add
2. __builtin_divud
3. __builtin_clr

Programming

Data Location

Table 7.1 Data Location
Type Description Example
_XBSS(N) [1] RAM Data in X-memory, aligned at N, no initilization int _XBSS(32) xbuf[16];
_XDATA(N) [1] RAM Data in X-memory, aligned at N, with initilization int _XDATA(32) xbuf[] = {1, 2, 3, 4, 5};
_YBSS(N) [1] RAM Data in Y-memory, aligned at N, no initilization int _YBSS(32) ybuf[16];
_YDATA(N) [1] RAM Data in Y-memory, aligned at N, with initilization int _YDATA(32) ybuf[16] = {1, 2, 3, 4, 5};
__attribute__((space(const))) Flash ROM data, constant, accessed by normal C statements, but 32K max. int i __attribute__((space(const))) = 10;
__attribute__((space(prog))) Flash ROM data, read/write by program space visibility window (psv) int i __attribute__((space(prog)));
__attribute__((space(auto_psv))) Flash ROM data, read by normal C statements, write by accessing psv int i __attribute__((space(auto_psv)));
__attribute__((space(psv))) Flash ROM data, read/write by (psv) int i __attribute__((space(psv)));
_EEDATA(N) ROM Data in EEPROM, aligned at N, read/write with psv int _EEDATA(2) table[]={0, 1, 1, 2, 3, 5, 8};
 void main(){

    PSVPAG = __builtin_psvpage(&table);

    CORCONbits.PSV = 1;

    ...

    if(table[2]){

       ...

    }

 }
_PERSISTENT RAM Data, data remain after reset int _PERSISTENT var1, var2;
_NEAR RAM Data at near section int _NEAR var1, var2;
_ISR Interrupt service rountine void _ISR _INT0Interrupt(void);
_ISRFAST Fast interrupt service rountine void _ISRFAST _T0Interrupt(void);
  1. N must be a power of two, with a minimum value of 2.
Retrieved from "http://www.opencircuits.com/index.php?title=DsPIC30F_5011_Development_Board&oldid=2238"