Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| projects:oxford [2017/02/06 14:36] – [Credits and Thanks] darron | projects:oxford [2017/02/24 16:31] (current) – [Devices] darron | ||
|---|---|---|---|
| Line 12: | Line 12: | ||
| For the UART interface any of a number of serial interfaces may | For the UART interface any of a number of serial interfaces may | ||
| be used which includes bluetooth devices such as the [[interfaces: | be used which includes bluetooth devices such as the [[interfaces: | ||
| + | |||
| + | === Devices === | ||
| + | |||
| + | At this time 489 devices are thought to be supported and here is a list | ||
| + | of devices which have been tested during the production of this boot loader. | ||
| + | |||
| + | <columns 50% 50% -> | ||
| + | |||
| + | < | ||
| + | dsPIC30F1010 | ||
| + | dsPIC33EP128GP502 | ||
| + | dsPIC33EV256GM002 | ||
| + | dsPIC33EV256GM102 | ||
| + | dsPIC33FJ06GS101A | ||
| + | dsPIC33FJ128GP802 | ||
| + | dsPIC33FJ16GS502 | ||
| + | dsPIC33FJ32MC102 | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | |||
| + | < | ||
| + | |||
| + | PIC24F04KA201 | ||
| + | PIC24F16KL402 | ||
| + | PIC24FJ128GA202 | ||
| + | PIC24FJ16MC101 | ||
| + | PIC24FJ256GA702 | ||
| + | PIC24FJ64GA002 | ||
| + | PIC24FV08KM101 | ||
| + | PIC24FV32KA302 | ||
| + | PIC24HJ128GP502 | ||
| + | |||
| + | </ | ||
| + | |||
| + | </ | ||
| === Licence === | === Licence === | ||
| Line 19: | Line 55: | ||
| === Credits and Thanks === | === Credits and Thanks === | ||
| - | Oxford Boot Loader is developed by Darron M Broad with contributions from Gerhard Bertelsmann. | + | Oxford Boot Loader |
| I am grateful to Chiculita Claudiu for Tiny PIC Bootloader as Oxford Boot Loader uses a protocol derived from Tiny PIC bootloader. | I am grateful to Chiculita Claudiu for Tiny PIC Bootloader as Oxford Boot Loader uses a protocol derived from Tiny PIC bootloader. | ||
| + | === Checkout === | ||
| + | |||
| + | Oxford boot loader is obtained using mercurial. | ||
| + | |||
| + | < | ||
| + | hg clone http:// | ||
| + | cd oxford | ||
| + | </ | ||
| + | |||
| + | === Configure === | ||
| + | |||
| + | Configuring Oxford is a simple case of copying two template files for | ||
| + | the target device and editing it to suit the target application. | ||
| + | |||
| + | The first file is the assembly code for the loader and the second file | ||
| + | a GNU make file for building the loader. | ||
| + | |||
| + | < | ||
| + | cd boot | ||
| + | cp template.mk mk/ | ||
| + | cp template.s myproject.s | ||
| + | vi myproject.s | ||
| + | vi mk/ | ||
| + | </ | ||
| + | |||
| + | Follow the guide given in the template files to create the correct boot loader | ||
| + | firmware for your target then build the boot loader. [[: | ||
| + | be installed to perform this operation. | ||
| + | |||
| + | < | ||
| + | make | ||
| + | </ | ||
| + | |||
| + | === Program === | ||
| + | |||
| + | Now you must program the boot loader onto the target device. This will depend | ||
| + | on the programming tool you have available and in this example we use | ||
| + | [[: | ||
| + | |||
| + | < | ||
| + | p24 select dsPIC33EP128GP502 lvp program myproject.hex | ||
| + | </ | ||
| + | |||
| + | Once the boot loader hex file is on the target it may be reset whereupon | ||
| + | it will listen for a connection from `easy-loader' | ||
| + | the host platform. | ||
| + | |||
| + | === Upload === | ||
| + | |||
| + | In this final step you now take the application for your target device | ||
| + | and upload it to the boot loader which will store it in flash memory. | ||
| + | |||
| + | This process is documented on the [[: | ||
