Difference between revisions of "ME333 Unofficial Sample Code"

From Mech
Jump to navigationJump to search
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
'''OBSOLETE. THIS PAGE REFERS TO A PRE-RELEASE VERSION OF THE NU32 PIC32 DEVELOPMENT BOARD. FOR INFORMATION, SAMPLE CODE, AND VIDEOS RELATED TO THE PRODUCTION VERSION (2016 AND LATER), AND TO THE CORRESPONDING BOOK "EMBEDDED COMPUTING AND MECHATRONICS WITH THE PIC32 MICROCONTROLLER," VISIT [[NU32|THE NU32 PAGE]].'''
'''DO NOT USE SAMPLE CODE ON THIS PAGE! IT IS STILL IN TESTING MODE. USE [[ME333_Sample_Code|THIS PAGE]] INSTEAD.'''



Code for ME333 instructors to test before it goes live.
Code for ME333 instructors to test before it goes live.
Line 67: Line 68:


'''Using the UART'''
'''Using the UART'''
* Simple RS232 communication: one UART to another on the same PIC
* '''TESTED 2/6/2013''' [[Media:Uart_loop.c|Uart_loop.c]]: Simple RS232 communication: one UART to another on the same PIC
* [[Media:Uart_pic2pic.c|Uart_pic2pic.c]]: Simple RS232 communication: PIC to PIC
* '''TESTED 2/7/2013''' [[Media:Uart_pic2pic.c|Uart_pic2pic.c]]: Simple RS232 communication: PIC to PIC
* [[Media:Uart_hfc.c|Uart_hfc.c]]: RS232 with hardware flow control
* '''TESTED 2/7/2013''' [[Media:Uart_hfc.c|Uart_hfc.c]]: RS232 with hardware flow control
* Talking to a PC with an FTDI cable
* '''TESTED 2/10/2013''' [[Media:Uart_ftdi.c|Uart_ftdi.c]]: Talking to a PC with an FTDI cable


'''Using I2C'''
'''Using I2C'''
* '''TESTED 2/20/2013''' [[Media:NU32_I2C.c|NU32_I2C.c]], [[Media:NU32_I2C.h|NU32_I2C.h]]: Library files.
* I2C1 to I2C2 on one PIC
* I2C1 to I2C2 on one PIC
* PIC to PIC
* PIC to PIC
* MAX518 8bit I2C DAC
* '''TESTED 2/20/2013''' [[Media:I2C_DAC.c|I2C_DAC.c]]: MAX518 8bit I2C DAC
* NAU7802 24bit I2C ADC
* '''TESTED 2/20/2013''' [[Media:I2C_ADC.c|I2C_ADC.c]]: NAU7802 24bit I2C ADC
* PCF8570 2kbit I2C SRAM
* '''TESTED 2/20/2013''' [[Media:I2C_RAM.c|I2C_RAM.c]]: PCF8570 2kbit I2C SRAM


'''Using SPI'''
'''Using SPI'''
Line 114: Line 116:


'''USB'''
'''USB'''
* '''TESTED 2/17/2013''' [[Media:USBHost-MassStorage.zip|USBHost-MassStorage.zip]]: Writes the voltage on an analog pin to a ADC.csv file on an external USB stick approx. 5 times per second. Writing starts when the USB is inserted and stops when the USER button is pressed. Remember to press the USER button to stop writing data before removing the USB stick. View the README.txt file to build
* HID to Processing on a PC
* HID to Processing on a PC
* CDC to PC
* CDC to PC

Latest revision as of 05:50, 16 January 2016

OBSOLETE. THIS PAGE REFERS TO A PRE-RELEASE VERSION OF THE NU32 PIC32 DEVELOPMENT BOARD. FOR INFORMATION, SAMPLE CODE, AND VIDEOS RELATED TO THE PRODUCTION VERSION (2016 AND LATER), AND TO THE CORRESPONDING BOOK "EMBEDDED COMPUTING AND MECHATRONICS WITH THE PIC32 MICROCONTROLLER," VISIT THE NU32 PAGE.


Code for ME333 instructors to test before it goes live.

Code with TESTED has been tested and is ready to go live.

Code with EDITS has been updated but not fully test.

Code without any marking has not been looked at yet.


PIC32 Code

Bootloader Project

  • 1/30/2013 NU32_bootloader.zip: (Updated 1/30 to make it jump to the noncacheable virtual address, not cacheable, just for conceptual clarity.) All files in one folder. Kevin's version building on Nick's. Jumps to application at new jump location that doesn't waste flash. Also sets config bits for Shadow Register Set.
  • 1/20/2013 Nick's bootloader app as of Jan 20, that doesn't compile

Simple PIC

  • TESTED 1/16/2013 simplePIC.c: Flashes LEDs on the NU32 unless the USER button is pressed.
  • TESTED 1/16/2013 simplePIC_standalone.c: Standalone version of simplePIC.c.


NU32 library, header file, procdefs, and terminal comm test

  • 1/17/2013 talkingPIC.c: echoes strings sent from keyboard back to computer screen
  • 1/21/2013 NU32bootloaded.ld: Use this linker script when creating executables to be bootloaded on NU32 (not app.ld). Kevin's version which puts the program starting at 0x9D000000, allowing access to full amount of flash.
  • 1/20/2013 NU32.c: NU32 board library.
  • 1/28/2013 NU32.h: NU32 header file, updated to have config bits for Shadow Register Set and to include <plib.h>.
  • NU32_serial_comm.c: Serial communication test with the terminal.
  • NU32_serial_plot.c: Plot data with serial communication in NU32_Utility.

LCD code (to be moved into NU32.c)

Serial Sample code for Invest.c

Communication Examples

  • Serial to a terminal
  • Serial to MATLAB
  • Serial to Processing
  • Output to the LCD

Digital I/O

  • DIGIO_sfrs.c: Digital I/O and change notification using SFR manipulation.
  • DIGIO_plib.c: Digital I/O and change notification using the peripheral library.

Counter/timer

Interrupts

  • INT_core_timer.c: Interrupt on core timer period match.
  • INT_ext_int.c: Interrupt on rising edge of external interrupt line INT0.
  • Peripheral timer interrupt.

Output compare (PWM)

  • OC_PWM_nolib.c: Set up PWM by setting SFRs.
  • OC_PWM_lib.c: Set up PWM using peripheral library functions.
  • OC_square_wave.c: Alternate between two different PWM duty cycles at 1 Hz. PWM is at 100 kHz and can be low-pass filtered to get a square wave analog output.

Analog to digital

  • ADC_Read2.c: Reads two analog inputs repetitively and prints the results to the user's terminal.
  • ADC_Read2_LCD.c Reads two analog inputs repetitively and prints the results to the LCD.
  • Something else, scanning mode, asynchronous results check on the buffer, and/or interrupt generated when some results are ready.

Using the UART

  • TESTED 2/6/2013 Uart_loop.c: Simple RS232 communication: one UART to another on the same PIC
  • TESTED 2/7/2013 Uart_pic2pic.c: Simple RS232 communication: PIC to PIC
  • TESTED 2/7/2013 Uart_hfc.c: RS232 with hardware flow control
  • TESTED 2/10/2013 Uart_ftdi.c: Talking to a PC with an FTDI cable

Using I2C

  • TESTED 2/20/2013 NU32_I2C.c, NU32_I2C.h: Library files.
  • I2C1 to I2C2 on one PIC
  • PIC to PIC
  • TESTED 2/20/2013 I2C_DAC.c: MAX518 8bit I2C DAC
  • TESTED 2/20/2013 I2C_ADC.c: NAU7802 24bit I2C ADC
  • TESTED 2/20/2013 I2C_RAM.c: PCF8570 2kbit I2C SRAM

Using SPI

  • TESTED 2/7/2013 SPILoopback.c: SPI4 to SPI1 on one PIC
  • PIC to PIC
  • MCP4922 12bit SPI DAC
  • MCP3008 10bit SPI ADC
  • Microchip 23k256 256kbit SPI SRAM

Comparator

  • TESTED 2/7/2013 Comparator.c‎: Toggle an LED based on the relative state of two pins
  • TESTED 2/7/2013 ComparatorOutput.c‎: Output analogue ref voltage based on the difference between source pins
  • turn a light on or off based on potentiometer reading

Input Capture

  • TESTED 2/7/2013 Input_capture.c: Create a PWM signal (duty cycle controlled by a potentiometer) and read in to an input capture, display the pulse width or duty cycle

Applications

DSP and FFT

Reading a quadrature encoder with the dsPIC33FJ12MC201 breakout board

Controlling a stepper motor with the TB6612

Controlling an RC servo motor


Extra PIC32 Code

USB

  • TESTED 2/17/2013 USBHost-MassStorage.zip: Writes the voltage on an analog pin to a ADC.csv file on an external USB stick approx. 5 times per second. Writing starts when the USB is inserted and stops when the USER button is pressed. Remember to press the USER button to stop writing data before removing the USB stick. View the README.txt file to build
  • HID to Processing on a PC
  • CDC to PC

Watchdog Timer

  • TESTED 2/7/2013 WatchdogTimer.c: User button turns on LED the LED turns off again when PIC restarts due to watchdog timer
  • Press a button every so often or watch the PIC reset itself (and perhaps a light stays off until you manually reset it or something)

Using the RTCC

  • Keeping time: set time from a PC, display current time on same PC
  • alarm clock demo?

Programming the onboard flash

  • Flash self programming: displays saved data at power on, allows user to enter new data (button presses, whatever), displays the new data, and when you power cycle, PIC displays the most recent data on startup

Sleep, Idle, Freeze

  • config bits?
  • demonstrate little current usage in sleep mode; wake up at predefined intervals or on certain signals and do something (and see the spike in current usage?)

Using CAN

  • Three PICs establishing a CAN bus: each PIC has a button and the state of the LEDs on each NU32 changes depending on which buttons are pressed (confirm communication between PICs)
  • PC to PIC (Peak card?)
  • some CAN chip? sensor?

DIP PIC32 with reconfigurable pins (1/2xx) (11/21)

  • Reconfiguring the pins.

Data logging on a uSD card

  • Using the Microchip FAT32 library, AN1045