Difference between revisions of "DsPIC30F 5011 Development Board"

Latest revision as of 07:30, 16 October 2012

This project aims to provide the development tools for building a multi-purpose MCU board. Description is based on Microchip dsPic33FJ256GP506 (was dsPic30F5011), but information provided in this wiki may give useful directions for developing similar embedded systems with different platforms.

Introduction

Features of dsPic33FJ256GP506

3.0 to 3.3 V
Up to 40 MIPs
Maximum current sink/source for I/O pins: 4 mA
16-bit arithmetics
DSP Instruction Set
Dual programming techniques: ICSP and RTSP
Memory
- 256 KB flash (86K instructions)
- 16 KB RAM (incl. 2 KB DMA RAM)
- No EEPROM
Communications ports
- UART
- I²C: up to 1 Mbit/s
- SPI
ADC
10-bit A/D, 1.1 Msps
12-bit A/D, 500 ksps
No DAC (PWMs only)
Pin-to-pin compatible with other dsPICs

Comparison between different dsPICs
dsPic	*Price US$	MIPs	Flash (kB)	RAM (kB)	I/O	ADC 12-bit	IC	OC	Motor Ctrl	Timers	QEI	UART	SPI	I2C	CAN	Codec
33FJ256GP506	6.11	40	256	16	53	18	8	8	0	9x16bit 4x32bit	0	2	2	2	1	1
33FJ128GP206	4.62	40	128	8	53	18	8	8	0	9x16bit 4x32bit	0	2	2	1	0	1
33FJ128GP306	4.81	40	128	16	53	18	8	8	0	9x16bit 4x32bit	0	2	2	2	0	1
33FJ128GP706	5.49	40	128	16	53	18	8	8	0	9x16bit 4x32bit	0	2	2	2	2	1
33FJ128MC506	4.97	40	128	8	53	16	8	8	8	9x16bit 4x32bit	1	2	2	2	1	0
33FJ128MC706	5.38	40	128	16	53	16	8	8	8	9x16bit 4x32bit	1	2	2	2	1	0

*For reference only, subject to change

Forums

Microchip: Official forum by Microchip
- See MPLAB ICD 2, MPLAB IDE, MPLAB C30 Compiler, ASM30, Link30 forum, dsPIC30F Topics, dsPic33 topics
HI-TECH Software Forum: Discussion on dsPICC, a C compiler developed by HI-TECH
FreeRTOS Real Time Kernel: Open Discussion and Support on FreeRTOS
Nabble: MicroControllers - GNUPIC

References

dsPIC33F
ICD2 Programmer
- ICD2 User's Guide
MPLAB
- MPLAB IDE User's Guide
C30 Compiler
- MPLAB C30 C Compiler User's Guide: Contains commands for using pic30-elf-gcc
- 16-bit Language Tools Libraries: Contains summaries and examples of using DSP libraries, standard C libraries and device libraries
- MPLAB ASM30, MPLAB LINK30 and Utilities User's Guide

Code Examples

Microchip Example Codes for dsPic

Related Development

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: External Programmer (ICD2)

Two types of ICSP are available: ICSP and Enhanced ICSP. Both of them require setting MCLR# to V_IHH (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.

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.

Hardware Interface

Pin Used by ICSP
Pin Label	Function	Pin Number
MCLR#	Programming Enable	7
V_DD	Power Supply	10, 26, 38, 57
V_SS	Ground	9, 25, 41, 56
PGC	Serial Clock	17
PGD	Serial Data	18

Available Programmers in the Market
Product Name	Interface with PC	Interface with Device	*Price (US)	Remarks
MPLAB^® ICD 2	USB or RS232	6-PIN RJ-12 connector	$159.99	-
Clone Microchip ICD2 (Now Using)	USB	6-pin flat cables	$52.35	Do not work with new MPLAB versions (works for 7.50), communication to MPLAB may sometime hang (see manual)

*For reference only (exclude shipping), subject to change

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.

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 version¹)
Piklab	Assembler and C-Compiler	Linux	Free

Full-featured for the first 60 days. After 60 days, some code optimization functions are disabled. The compiler will continue to function after 60 days, but code size may increase.

RTSP: COM Port (Bootloader)

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

Development Environment

Windows

C-Compiler, Assembler and Linker are under GNU license.
- MPLAB C30 C Compiler (*.c -> *.s)
- MPLAB ASM30 Assembler (*.s -> *.o)
- MPLAB LINK30 Linker (*.o -> *.bin)

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.

C-libraries contained in C30 includes (Refer to 16-Bit Language Tools Libraries from Microchip).

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	\lib \src\peripheral \support\h	ADC12, IOPort, UART, I²C, 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

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
Important Note: Only the compiler is free. The header files and library are owned by Microchip.

Pic30 C-Compiler Toolchain Templates for Conversion to Debian-based systems
Toolchain Source	Instruction	Remarks
v2.00	Download pic30-gcc-2.00-1.i386.rpm and pic30-binutils-2.00-1.i386.rpm. Convert to deb files.	Stable Now using
v2.05	Reference to example below, but use 2.05 files	Can compile Stable but not heavily tested
v3.01	Follow example below	Can compile Unstable (sometime produce segmentation fault)
v3.10	Reference to example below, but use 3.10 files	Cannot compile yet (segmentation fault)

Conversion Example

Pre-install these packages: dpkg-dev, debhelper, bison, flex, sysutils, gcc-3.3, fakeroot
- cmd: sudo apt-get install dpkg-dev debhelper bison flex sysutils gcc-3.3 fakeroot
Download and unzip template: pic30-3.01.tar.bz2
Download assembler: mplabalc30v3_01_A.tar.gz. Save under /pic30-3.01/pic30-binutils-3.01/upstream/
Download c-compiler: mplabc30v3_01_A.tgz. Save under /pic30-3.01/pic30-gcc-3.01/upstream/
Install MPLAB_C30_v3_01-StudentEdition under Windows
Copy directories /include, /lib, /support, and /bin/c30_device.info to pic30-3.01/pic30-support-3.01/upstream/
Pack pic30-binutils into deb file
- goto /pic30-3.01/pic30-binutils-3.01/
- type cmd: dpkg-buildpackage -rfakeroot -b
Install pic30-binutils_3.01-1_i386.deb
- type cmd: sudo dpkg -i pic30-binutils_3.01-1_i386.deb
Pack pic30-gcc-3.01 into deb file
- goto /pic30-3.01/pic30-gcc-3.01/
- type cmd: dpkg-buildpackage -rfakeroot -b
Install pic30-gcc_3.01-1_i386.deb
- type cmd: sudo dpkg -i pic30-gcc_3.01-1_i386.deb
Pack support files into deb file
- goto /pic30-3.01/pic30-support-3.01/
- type cmd: dpkg-buildpackage -rfakeroot -b
Install pic30-support_3.01-1_all.deb
- type cmd: sudo dpkg -i pic30-support_3.01-1_all.deb
After installation, locations of
- C-Header (*.h): /usr/pic30-elf/include
- Libraries (*.a): /usr/pic30-elf/lib
- Assembly header (*.inc): /usr/share/pic30-support/inc
- Linkerscript (*.gld): /usr/share/pic30-support/gld

Burning Program Codes to Target Board

Use 'dspicprg and dspicdmp' utilities developed by Homer Reid to burn hex code (*.hex) to devices. See Reference here. Through serial port only?
Use Piklab IDE. Details on file format not known.
Use MPLAB IDE to burn hex code (*.hex) to devices.

Code Optimization

Below is a comparsion between different optimization levels for the project including drivers for 2 projects.

Comparison between differnt optimization levels
Optimization	Description	Project 1 Code Size (byte)	Project 1 Data Usage (byte)	Project 2 Code Size (byte)	Project 2 Data Usage (byte)
O0	No optimization Fastest Compilation	6222 (9%)	178 (4%)	26,037 (38%)	710 (17%)
O1	Optimize Tries to reduce code size and execution time.	4473 (6%)	178 (4%)	22,290 (32%)	710 (17%)
O2	Optimize even more Performs nearly all supported optimizations that do not involve a space-speed trade-off. Increases both compilation time and the performance of the generated code.	4422 (6%)	178 (4%)	21,993 (32%)	710 (17%)
O3	Optimize yet more. O3 turns on all optimizations specified by O2 and also turns on the inline-functions option.	4485 (6%)	178 (4%)	22,176 (32%)	710 (17%)
Os	Optimize for size. Os enables all O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.	4356 (6%)	178 (4%)	21,885 (32%)	710 (17%)

Driver Development

Description on developing drivers with POSIX API

Bootloader Development

Description on concepts and development on bootloader
Description on dsPicProgrammer to download firmware via bootloader

Programming the Device

Description on how to use dsPicProgrammer to download firmware to dspic

Difference between revisions of "DsPIC30F 5011 Development Board"

Latest revision as of 07:30, 16 October 2012

Contents

Introduction

Features of dsPic33FJ256GP506

Forums

References

Code Examples

Related Development

Programming Methods

ICSP: External Programmer (ICD2)

Hardware Interface

Software Interface

RTSP: COM Port (Bootloader)

Development Environment

Windows

Linux

Conversion Example

Burning Program Codes to Target Board

Code Optimization

Driver Development

Bootloader Development

Programming the Device

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Tools

@@ Line 1: / Line 1: @@
+This project aims to provide the development tools for building a [[Multi-purpose_Embedded_System | multi-purpose MCU board]]. Description is based on Microchip dsPic33FJ256GP506 (was dsPic30F5011), but information provided in this wiki may give useful directions for developing similar embedded systems with different platforms.
 ==Introduction==
-===Web Page===
+===Features of dsPic33FJ256GP506===
-*[http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=2529&param=en024856 Microchip]
+*3.0 to 3.3&nbsp;V
-**dsPIC 16-bit Embedded Control Solutions Brochure
+*Up to 40&nbsp;MIPs
-**dsPIC30F Family Overview
+*Maximum current sink/source for I/O pins: 4&nbsp;mA
+*16-bit arithmetics
-===Forum===
+*DSP Instruction Set
-*[http://direct.forum.microchip.com/default.aspx Microchip]: Official forum by Microchip
+*Dual programming techniques: ICSP and RTSP
-**[http://direct.forum.microchip.com/tt.aspx?forumid=49 MPLAB ICD 2]: Subforum on ICD 2 programmer
+*Memory
-**[http://direct.forum.microchip.com/tt.aspx?forumid=57 MPLAB IDE]: Subforum on IDE
+**256&nbsp;KB flash (86K instructions)
-**[http://direct.forum.microchip.com/tt.aspx?forumid=101 MPLAB C30 Compiler, ASM30, Link30 forum]: Subforum on C compiler. Refer to [http://ww1.microchip.com/downloads/en/DeviceDoc/C30_Users_Guide_51284e.pdf MPLAB C30 C Compiler User's Guide] Chapter 3
+**16&nbsp;KB RAM (incl. 2&nbsp;KB DMA RAM)
-**[http://direct.forum.microchip.com/tt.aspx?forumid=153 dsPIC30F Topics]: Subformum on dsPIC30F
+**No EEPROM
+*Communications ports
-*[http://www.gnupic.org/ GNUPIC]: Discussion on PIC in Linux Systems
+**UART
-**[http://www.linuxhacker.org/cgi-bin/ezmlm-cgi?1:dds:5443#b Debian]
+**I<sup>2</sup>C: up to 1&nbsp;Mbit/s
+**SPI
+*ADC
+*10-bit A/D, 1.1 Msps
+*12-bit A/D, 500 ksps
+*No DAC (PWMs only)
+*Pin-to-pin compatible with other dsPICs
+{| border="1" cellspacing="0" cellpadding="5"
+|+ Comparison between different dsPICs
+! dsPic !! *Price<br>US$ !! MIPs
+! Flash<br>(kB)!! RAM<br>(kB) !! EEPROM<br>(kB)
+! I/O !! ADC<br>12-bit !! IC !! OC !! Motor<br>Ctrl !! Timers
+! QEI !! UART !! SPI !! I2C !! CAN !! Codec
+|-
+| 33FJ256GP506 || 6.11 || 40
+| 256 || 16 || 0
+| 53 || 18 || 8 || 8 || 0 || 9x16bit<br>4x32bit
+| 0 || 2 || 2 || 2 || 1 || 1
+|-
+| 33FJ128GP206 || 4.62 || 40
+| 128 || 8 || 0
+| 53 || 18 || 8 || 8 || 0 || 9x16bit<br>4x32bit
+| 0 || 2 || 2 || 1 || 0 || 1
+|-
+| 33FJ128GP306 || 4.81 || 40
+| 128 || 16 || 0
+| 53 || 18 || 8 || 8 || 0 || 9x16bit<br>4x32bit
+| 0 || 2 || 2 || 2 || 0 || 1
+|-
+| 33FJ128GP706 || 5.49 || 40
+| 128 || 16 || 0
+| 53 || 18 || 8 || 8 || 0 || 9x16bit<br>4x32bit
+| 0 || 2 || 2 || 2 || 2 || 1
+|-
+| 33FJ128MC506 || 4.97 || 40
+| 128 || 8 || 0
+| 53 || 16 || 8 || 8 || 8 || 9x16bit<br>4x32bit
+| 1 || 2 || 2 || 2 || 1 || 0
+|-
+| 33FJ128MC706 || 5.38 || 40
+| 128 || 16 || 0
+| 53 || 16 || 8 || 8 || 8 || 9x16bit<br>4x32bit
+| 1 || 2 || 2 || 2 || 1 || 0
+|-
+|}
+<nowiki>*</nowiki>For reference only, subject to change
+===Forums===
+*[http://forum.microchip.com/ Microchip]: Official forum by Microchip
+**See MPLAB ICD 2, MPLAB IDE, MPLAB C30 Compiler, ASM30, Link30 forum, dsPIC30F Topics, dsPic33 topics
 *[http://www.htsoft.com/forum/all/ubbthreads.php/Cat/0/C/6 HI-TECH Software Forum]: Discussion on dsPICC, a C compiler developed by HI-TECH
+*[http://sourceforge.net/forum/forum.php?forum_id=382005 FreeRTOS Real Time Kernel]: Open Discussion and Support on FreeRTOS
-*[http://piclist.com/techref/piclist/index.htm PICList]: Discussion on older PIC systems (not dsPIC)
+*[http://www.nabble.com/MicroControllers---GNUPIC-f2057.html Nabble]: MicroControllers - GNUPIC
-*[http://groups.google.com/group/pickit-devel PicKit]: Discussion on PICkit/PICkit 2 programmers
 ===References===
-*dsPIC30F
+*dsPIC33F
-**[http://ww1.microchip.com/downloads/en/DeviceDoc/70043F.pdf Family Overview]
+**[http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=2573 dsPIC33F Family Reference Manual Sections]
-**[http://ww1.microchip.com/downloads/en/DeviceDoc/70046E.pdf Family Reference Manual]
+**[http://ww1.microchip.com/downloads/en/DeviceDoc/70286C.pdf dsPIC33FJXXXGPX06/X08/X10 Data Sheet]
-**[http://ww1.microchip.com/downloads/en/DeviceDoc/70116F.pdf 5011 Data Sheet]
+**[http://ww1.microchip.com/downloads/en/DeviceDoc/80306E.pdf dsPIC33FJXXXGPX06/X08/X10 Rev. A2/A3/A4 Silicon Errata]
-**[http://ww1.microchip.com/downloads/en/DeviceDoc/70102G.pdf Flash Programming Specification]
+**[http://ww1.microchip.com/downloads/en/DeviceDoc/70152G.pdf Flash Programming Specification]
-**[http://ww1.microchip.com/downloads/en/DeviceDoc/70157B.pdf Programmer Reference Manual]
 *ICD2 Programmer
-**[http://ww1.microchip.com/downloads/en/DeviceDoc/51331B.pdf ICD2 User's Guide]
+**[http://ww1.microchip.com/downloads/en/DeviceDoc/51331C.pdf ICD2 User's Guide]
 *MPLAB
 **[http://ww1.microchip.com/downloads/en/DeviceDoc/51519B.pdf MPLAB IDE User's Guide]
 *C30 Compiler
-**[http://ww1.microchip.com/downloads/en/DeviceDoc/C30_Users_Guide_51284e.pdf MPLAB C30 C Compiler User's Guide]
+**[http://ww1.microchip.com/downloads/en/DeviceDoc/C30_Users_Guide_51284e.pdf MPLAB C30 C Compiler User's Guide]: Contains commands for using pic30-elf-gcc
-**[http://ww1.microchip.com/downloads/en/DeviceDoc/16bit_Language_Tool_Libraries_51456c.pdf 16-bit Language Tools Libraries]
+**[http://ww1.microchip.com/downloads/en/DeviceDoc/16bit_Language_Tool_Libraries_51456c.pdf 16-bit Language Tools Libraries]: Contains summaries and examples of using DSP libraries, standard C libraries and device libraries
+**[http://ww1.microchip.com/downloads/en/DeviceDoc/Asm30_Link_Util_51317e.pdf MPLAB ASM30, MPLAB LINK30 and Utilities User's Guide]
-===Features of dsPIC===
+===Code Examples===
-*Advantages
+*[http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1408 Microchip Example Codes for dsPic]
-**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
-**I<sup>2</sup>C: 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===
+===Related Development===
-*dsPIC30F, dsPIC30F5011
+*[[Ethernet Module]]
+*[[Modulation Plugin]]
 ==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===
+===ICSP: External Programmer (ICD2)===
-*Two types of ICSP are available: '''ICSP''' and '''Enhanced ICSP'''. Both of them require setting ^MCLR to V<sub>IHH</sub> (9V – 13.25V).
+*Two types of ICSP are available: '''ICSP''' and '''Enhanced ICSP'''. Both of them require setting MCLR# to V<sub>IHH</sub> (9V – 13.25V).
 *Standard ICSP
 **Use external programmer (e.g. MPLAB<sup>®</sup> ICD 2, MPLAB<sup>®</sup> PM3 or PRO MATE<sup>®</sup> 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
@@ Line 76: / Line 111: @@
 **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
+====Hardware Interface====
 {| border="1" cellspacing="0" cellpadding="5"
-|+ Table 3.1 Pin Used by ICSP
+|+ Pin Used by ICSP
 ! Pin Label !! Function !! Pin Number
 |-
-| ^MCLR || Programming Enable|| 7
+| MCLR# || Programming Enable|| 7
 |-
 | V<sub>DD</sub> || Power Supply || 10, 26, 38, 57
@@ Line 97: / Line 131: @@
 {| border="1" cellspacing="0" cellpadding="5"
-|+ Table 3.2 Available Programmers in the Market
+|+ Available Programmers in the Market
 ! Product Name
 ! Interface with PC
 ! Interface with Device
-! Price (US)
+! *Price (US)
-! Postage (US)
+! Remarks
-! Total (US)
 |-
 | [http://direct.www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010046&part=DV164005 MPLAB<sup>®</sup> ICD 2]
-| USB/RS232
+| USB or RS232
 | [http://www.microchip.com/Microchip.WWW.SecureSoftwareList/secsoftwaredownload.aspx?device=en010046&lang=en&ReturnURL=http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010046&part=DV164005# 6-PIN RJ-12 connector]
 | $159.99
 | -
-| -
-|-
-| [http://www.kanda.com/index.php3?cs=1&bc=direct&bw=%2Fbrowse.php3%3Fnode%3D114%26semisupport%3D PRESTO PIC Programmer Plus]
-| USB
-| ?
-| $200.16
-| $15.00
-| $215.16
 |-
-| [http://www.etekronics.com/product_info.php?cPath=24&products_id=48  Full Speed USB Microchip ICD2<br> Debugger and Programmer]
+| [http://www.sureelectronics.net Clone Microchip ICD2] (Now Using)
 | USB
-| 6-PIN ICSP connector<br>6-PIN RJ-12 connector
-| $72.00
-| $12.00
-| $84.00
-|-
-| [http://www.etekronics.com/product_info.php?cPath=24&products_id=47 Mini Microchip Compatible ICD2<br> Debugger and Programmer]
-| RS232
-| 6-PIN ICSP connector<br>6-PIN RJ-12 connector
-| $45.00
-| $10.00
-| $55.00
-|-
-| [http://www.inexglobal.com/microcontroller.php ICDX30]
-| RS232
-| 6-pin RJ-11
-| $51.00
-| $47.46
-| $98.46
-|-
-| [http://www.sure-electronics.net/englishsite/icd2/icd2.htm Clone Microchip ICD2]
-| RS232
 | 6-pin flat cables
-| $30.00
+| $52.35
-| $12.00
+| Do not work with new MPLAB versions (works for 7.50), communication to MPLAB may sometime hang (see [http://www.sureelectronics.net/pdfs/DB-DP003.pdf manual])
-| $42.00
 |-
 |}
+<nowiki>*</nowiki>For reference only (exclude shipping), subject to change
 {| border="1" cellspacing="0" cellpadding="5"
-|+ Table 3.3 DIY ICD 2 Programmer Circuit
+|+ DIY ICD 2 Programmer Circuit
 ! Source !! Schematic !! PIC16F877A Bootloader
 |-
@@ Line 164: / Line 168: @@
 |}
-*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.
+====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.
 {| border="1" cellspacing="0" cellpadding="5"
-|+ Table 3.4 Summary of IDE
+|+ Summary of IDE
 ! Product Name !! Features !! OS !! Price (US$)
 |-
@@ Line 182: / Line 186: @@
 | $895.00 (Free student version<sup>1</sup>)
 |-
-| [http://linux.softpedia.com/get/Science-and-Engineering/Electronic-Design-Automation-EDA-/Piklab-8099.shtml Piklab 0.12.0]
+| [http://piklab.sourceforge.net/ Piklab]
 | Assembler and C-Compiler
 | Linux
-| Free<sup>2</sup>
+| Free
 |}
-# 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.
+# Full-featured for the first 60 days. After 60 days, some code optimization functions are disabled. The compiler will continue to function after 60 days, but code size may increase.
-# The current version supports external programmer ICD 2, but not yet tested.
-===RTSP===
+===RTSP: COM Port (Bootloader)===
-*RTSP works in normal voltage (^MCLR no need to raise to V<sub>IHH</sub>).
+*RTSP works in normal voltage (MCLR# no need to raise to V<sub>IHH</sub>).
-*No literature has mentioned the incorporation of Programming Executive (PE). Presumably, since Enhanced ICSP needs to set ^MCLR to V<sub>IHH</sub>, RTSP cannot use PE.
+*No literature has mentioned the incorporation of Programming Executive (PE). Presumably, since Enhanced ICSP needs to set MCLR# to V<sub>IHH</sub>, RTSP cannot use PE.
-*Refer to bootloader section.
+*Refer to [[DsPIC30F_5011_Development_Board#Bootloader_Development | bootloader section]].
-==Design Circuit and PCB==
-===IC Requirements===
-{|border="1" cellspacing="0" cellpadding="5" align="center"
-|+ Table 4.1 IC Requirements
-! Part No. !! Description
-! Min Temp !! Max Temp !! Min Volt !! Max Volt !! Typ Cur !! Max Cur
-|-valign="top"
-| [http://ww1.microchip.com/downloads/en/DeviceDoc/70116F.pdf dsPIC30F5011-30I/PT] || uP
-| -40<sup>o</sup>C || 85<sup>o</sup>C
-| 2.5V <sup>[1]</sup>|| 5.5V
-|     || 250mA
-|-
-| [http://datasheets.maxim-ic.com/en/ds/MAX3222-MAX3241.pdf MAX3232ESE] || RS232 driver
-| -40<sup>o</sup>C || 85<sup>o</sup>C
-| 3.0V || 5.5V
-| 0.3mA || 1.0mA
-|-
-| [http://www.analog.com/UploadedFiles/Data_Sheets/ADM483E.pdf ADM483E ANZ] || RS485 driver
-| -40<sup>o</sup>C || 85<sup>o</sup>C
-| 4.5V || 5.5V
-| 0.036mA ||
-|-
-| [http://focus.ti.com/lit/ds/symlink/dac6574.pdf DAC6574DGS] || 10-bit Quad-DAC I<sup>2</sup>C
-| -40<sup>o</sup>C || 105<sup>o</sup>C
-| 2.7V || 5.5V
-| 0.6mA || 0.9mA
-|-
-| [http://www.semiconductors.philips.com/acrobat/datasheets/74HC_HCT14_3.pdf 74HC14D] || Quad-Schmitt Trigger
-| -40<sup>o</sup>C || 125<sup>o</sup>C
-| 2.0V || 6.0V
-| || 50mA
-|-
-| Overall ||
-| -40<sup>o</sup>C || 85<sup>o</sup>C
-| 4.5V || 5.5V
-| || <310mA <sup>[2]</sup>
-|-
-|}
-#Minimum voltage measured is 3.3V (with 2 LEDs blinking) running at 30MHz.
-#Measured current at 5V is 180mA (with 2 LEDs blinking only)
-===Module===
-{|border="1" cellspacing="0" cellpadding="5" align="center"
-|+ Table 4.2 Module
-! Digital Input !! Digital Output !! Analog Input !! Analog Output
-|-valign="top"
-| 1. ICSP
-| 1. LED<br> 2. Bi-color LED<br> 3. RS232<br> 4. RS458<br> 5. Case temp overheat<br> 6. Laser on/off 1,2<br> 7. Interlock<br> 8. Digital ctrl<br> 9. Current 0,1 alarm<br>
-| 1. Case temp<br> 2. pow 0,1<br> 3. cur0<br> 4. temp0
-| 1. 10-bit DAC
-|-
-|}
-===Benchtop===
-{|border="1" cellspacing="0" cellpadding="5" align="center"
-|+ Table 4.3 Base Benchtop
-! Digital Input !! Digital Output !! Analog Input !! Analog Output
-|-valign="top"
-| 1. ICSP<br> 2. Rotary Key<br> 3. Push Buttons
-| 1. LED<br> 2. RS232<br> 3. RS458<br> 4.LCD display<br> 5. Buzzer<br> 6. Digital Ctrl 0,1
-| 1. Case temp<br> 2. CurrentDetect 0,1<br> 3. PowerDetect 0,1,2,3<br> 4. TempDetect
-| 1. 10-bit DAC (PowerCurrentCtrl 0,1)
-|-
-|}
@@ Line 271: / Line 208: @@
 **MPLAB C30 C Compiler (*.c -> *.s)
 **MPLAB ASM30 Assembler (*.s -> *.o)
-**MPLAB LINK30 Linker (*.o -> *.exe)
+**MPLAB LINK30 Linker (*.o -> *.bin)
 *PA optimizer, simulator, runtime libraries, header files, include files, and linker scripts are not covered by GNU. Reference is [http://direct.forum.microchip.com/tm.aspx?m=107208 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 2.4.
+*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.
 *C-libraries contained in C30 includes (Refer to [http://ww1.microchip.com/downloads/en/DeviceDoc/16bit_Language_Tool_Libraries_51456c.pdf 16-Bit Language Tools Libraries] from Microchip).
-{|border="1" cellspacing="0" cellpadding="5" align="center"
+{|border="1" cellspacing="0" cellpadding="5"
-|+ Table 4.1 C Libraries in MPLAB C30
+|+ C Libraries in MPLAB C30
 ! Library !! Directory <br>(\\Microchip\MPLAB C30) !! Major functions
 |-valign="top"
@@ Line 289: / Line 226: @@
 | Vector, Matrix, Filter, etc.
 |-valign="top"
-| 16-Bit Peripheral Libraries <br>(e.g. libp30F5011-coff.a)
+| 16-Bit Peripheral Libraries
 | \lib <br> \src\peripheral <br> \support\h
 | ADC12, IOPort, UART, I<sup>2</sup>C, etc.
@@ Line 311: / Line 248: @@
 **Current MPLAB ASM30 Assembler: v2.04
 **Current MPLAB C30 Compiler: v2.04
+*'''Important Note''': Only the compiler is free. The header files and library are owned by Microchip.
-*[http://gcc.gnu.org/ml/gcc/2005-02/msg01144.html 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.
+{|border="1" cellspacing="0" cellpadding="5"
-**Download '''pic30-1.32-debian.tar.bz2''' for Template v1.32. (For v2.01, please goto [http://thread.gmane.org/gmane.comp.hardware.microcontrollers.gnupic/3768/focus=3768  pic30-debian-2.01.tar.bz2]).
+|+ Pic30 C-Compiler Toolchain Templates for Conversion to Debian-based systems
-**Download '''pic30-binutils_1.32-1_i386.deb''' for the assember.
+! Toolchain Source !! Instruction !! Remarks
-**Download '''pic30-gcc_1.32-1_i386.deb''' for the compiler.
+|-valign="top"
+| [http://www.baycom.org/~tom/dspic/ v2.00]
-*'''Important Note''': Only the compiler is free. The header files and library is owned by Microchip.
+| Download pic30-gcc-2.00-1.i386.rpm and pic30-binutils-2.00-1.i386.rpm.<br>Convert to deb files.
-**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 [http://www.baycom.org/~tom/dspic/ here].
+| Stable<br>Now using
-**Instructions for filling the upstream direction is available [http://forum.microchip.com/printable.aspx?m=139360 here].
+|-valign="top"
-**Alteratively, [https://gna.org/projects/pic30-libc/ Stephan Walter] has started a project to develop C Runtime Library for dsPIC.
+| [http://www.nabble.com/Debian-templates-for-dsPIC-build-toolchain-2.05-td7886279.html v2.05]
-***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
+| Reference to example below, but use 2.05 files
+| Can compile<br>Stable but not heavily tested
+|-valign="top"
+| [http://www.nabble.com/Debian-templates-for-dsPIC-build-toolchain-3.01-tf4308624.html v3.01]
+| Follow example below
+| Can compile<br>Unstable (sometime produce segmentation fault)
+|-valign="top"
+| [http://www.nabble.com/Debian-Template-Patches-for-C30-v3.10-i386-td17534084.html v3.10]
+| Reference to example below, but use 3.10 files
+| Cannot compile yet (segmentation fault)
+|-
+|}
+====Conversion Example====
+*Pre-install these packages: dpkg-dev, debhelper, bison, flex, sysutils, gcc-3.3, fakeroot
+**cmd: '''sudo apt-get install dpkg-dev debhelper bison flex sysutils gcc-3.3 fakeroot'''
+*Download and unzip template: '''pic30-3.01.tar.bz2'''
+*Download assembler: '''mplabalc30v3_01_A.tar.gz'''. Save under /pic30-3.01/pic30-binutils-3.01/upstream/
+*Download c-compiler: '''mplabc30v3_01_A.tgz'''. Save under /pic30-3.01/pic30-gcc-3.01/upstream/
+*Install MPLAB_C30_v3_01-StudentEdition under Windows
+*Copy directories /include, /lib, /support, and /bin/c30_device.info to pic30-3.01/pic30-support-3.01/upstream/
+*Pack pic30-binutils into deb file
+**goto /pic30-3.01/pic30-binutils-3.01/
+**type cmd: '''dpkg-buildpackage -rfakeroot -b'''
+*Install pic30-binutils_3.01-1_i386.deb
+**type cmd: '''sudo dpkg -i pic30-binutils_3.01-1_i386.deb'''
+*Pack pic30-gcc-3.01 into deb file
+**goto /pic30-3.01/pic30-gcc-3.01/
+**type cmd: '''dpkg-buildpackage -rfakeroot -b'''
+*Install pic30-gcc_3.01-1_i386.deb
+**type cmd: '''sudo dpkg -i pic30-gcc_3.01-1_i386.deb'''
+*Pack support files into deb file
+**goto /pic30-3.01/pic30-support-3.01/
+**type cmd: '''dpkg-buildpackage -rfakeroot -b'''
+*Install pic30-support_3.01-1_all.deb
+**type cmd: '''sudo dpkg -i pic30-support_3.01-1_all.deb'''
+*After installation, locations of
+**C-Header (*.h): /usr/pic30-elf/include
+**Libraries (*.a): /usr/pic30-elf/lib
+**Assembly header (*.inc): /usr/share/pic30-support/inc
+**Linkerscript (*.gld): /usr/share/pic30-support/gld
-*Burning Program Codes to Target Board
+===Burning Program Codes to Target Board===
 #Use 'dspicprg and dspicdmp' utilities developed by [http://homerreid.ath.cx/misc/dspicprg/ Homer Reid] to burn hex code (*.hex) to devices. See Reference [http://forum.microchip.com/tm.aspx?m=94243 here]. Through serial port only?
 #Use [http://piklab.sourceforge.net/ Piklab IDE]. Details on file format not known.
 #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==
+===Code Optimization===
+*Below is a comparsion between different optimization levels for the project including drivers for 2 projects.
-===MPLAB IDE===
+{|border="1" cellspacing="0" cellpadding="5"
-*Install IDE and USB Driver
+|+ Comparison between differnt optimization levels
-# Do '''NOT''' connect ICD 2 (via USB) to PC.
+! Optimization !! Description !! Project 1<br>Code Size<br>(byte) !! Project 1<br>Data Usage<br>(byte) !! Project 2<br>Code Size<br>(byte) !! Project 2<br>Data Usage<br>(byte)
-# Install MPLAB IDE.
+|-valign="top"
-# Install USB driver by following the instruction in (C:\Program Files\Microchip\MPLAB IDE\ICD2\Drivers\Ddicd2.htm)
+| O0
+| No optimization<br>Fastest Compilation
+| 6222 (9%) || 178 (4%) || 26,037 (38%) || 710 (17%)
+|-valign="top"
+| O1
+| Optimize<br> Tries to reduce code size and execution time.
+| 4473 (6%) || 178 (4%) || 22,290 (32%) || 710 (17%)
+|-valign="top"
+| O2
+| Optimize even more<br> Performs nearly all supported optimizations <br>that do not involve a space-speed trade-off. <br>Increases both compilation time and the <br>performance of the generated code.
+| 4422 (6%) || 178 (4%) || 21,993 (32%) || 710 (17%)
+|-valign="top"
+| O3
+| Optimize yet more. <br>O3 turns on all optimizations specified by O2 <br>and also turns on the inline-functions option.
+| 4485 (6%) || 178 (4%) || 22,176 (32%) || 710 (17%)
+|-valign="top"
+| Os
+| Optimize for size. <br>Os enables all O2 optimizations that do not <br>typically increase code size. It also performs <br>further optimizations designed to reduce code <br>size.
+| 4356 (6%) || 178 (4%) || 21,885 (32%) || 710 (17%)
+|-
+|}
-*Establish Conncetion with ICD 2
-# Connect ICD 2 to PC. Do '''NOT''' connect target (via 6-pin cable) to ICD 2.
-# Run MPLAB IDE on PC.
-# Open an existing project (Project>Open)
-# Select MPLAB ICD 2 as the current programmer (Programmer>Select Programmer>MPLAB ICD 2)
-# Configure the USB Interface (Programmer>Settings, Communications Tab)
-# 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.
-*Establish Connection with Target
+==[[freertos_posix Development | Driver Development]]==
-# Uncheck the option “Power target circuit from MPLAB ICD” (Programmer>Settings, Power Tab). '''Place''' Jumper on target board. Power the Target.
+*Description on developing drivers with POSIX API
-# Establish connection with target through ICD 2 (Programmer>Connect).
-# See results of self test (Programmer>Settings, Status Tab).
-*Program the Device
-# Programmer>Program
-===PikLab===
+==[[Bootloader Development]]==
-*Under construction
+*Description on concepts and development on bootloader
+*Description on dsPicProgrammer to download firmware via bootloader
-===dspicprg===
-*Under construction
+==[[Programming the Device]]==
+*Description on how to use dsPicProgrammer to download firmware to dspic
-==Programming==
-===Data Location===
+[[category:projects]]
-{| border="1" cellspacing="0" cellpadding="5" align="center"
-|+ Table 7.1 Data Location
-! Type !! Description !! Example
-|-valign="top"
-| _XBSS(N) <sup>[1]</sup>
-| RAM Data in X-memory, aligned at N, no initilization
-| int _XBSS(32) xbuf[16];
-|-valign="top"
-| _XDATA(N) <sup>[1]</sup>
-| RAM Data in X-memory, aligned at N, with initilization
-| int _XDATA(32) xbuf[] = {1, 2, 3, 4, 5};
-|-valign="top"
-| _YBSS(N) <sup>[1]</sup>
-| RAM Data in Y-memory, aligned at N, no initilization
-| int _YBSS(32) ybuf[16];
-|-valign="top"
-| _YDATA(N) <sup>[1]</sup>
-| RAM Data in Y-memory, aligned at N, with initilization
-| int _YDATA(32) ybuf[16] = {1, 2, 3, 4, 5};
-|-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)
-| 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.