Frank 26080115
These are the examples provided for [[/users/frank26080115/libraries/LPC1700CMSIS_Lib/]] Note, the entire "program" is not compilable!
CAN/CAN_test_two_kit/abstract.h@0:bf7b9fba3924, 2011-03-20 (annotated)
- Committer:
- frank26080115
- Date:
- Sun Mar 20 05:38:56 2011 +0000
- Revision:
- 0:bf7b9fba3924
Who changed what in which revision?
| User | Revision | Line number | New contents of line |
|---|---|---|---|
| frank26080115 | 0:bf7b9fba3924 | 1 | ******************** (C) COPYRIGHT 2010 NXPSemiconductors ******************* |
| frank26080115 | 0:bf7b9fba3924 | 2 | * @file CAN\CAN_test_two_kit\abstract.txt |
| frank26080115 | 0:bf7b9fba3924 | 3 | * @author NXP MCU SW Application Team |
| frank26080115 | 0:bf7b9fba3924 | 4 | * @version 2.0 |
| frank26080115 | 0:bf7b9fba3924 | 5 | * @date |
| frank26080115 | 0:bf7b9fba3924 | 6 | * @brief Description of the CAN test two kit example. |
| frank26080115 | 0:bf7b9fba3924 | 7 | ****************************************************************************** |
| frank26080115 | 0:bf7b9fba3924 | 8 | * Software that is described herein is for illustrative purposes only |
| frank26080115 | 0:bf7b9fba3924 | 9 | * which provides customers with programming information regarding the |
| frank26080115 | 0:bf7b9fba3924 | 10 | * products. This software is supplied "AS IS" without any warranties. |
| frank26080115 | 0:bf7b9fba3924 | 11 | * NXP Semiconductors assumes no responsibility or liability for the |
| frank26080115 | 0:bf7b9fba3924 | 12 | * use of the software, conveys no license or title under any patent, |
| frank26080115 | 0:bf7b9fba3924 | 13 | * copyright, or mask work right to the product. NXP Semiconductors |
| frank26080115 | 0:bf7b9fba3924 | 14 | * reserves the right to make changes in the software without |
| frank26080115 | 0:bf7b9fba3924 | 15 | * notification. NXP Semiconductors also make no representation or |
| frank26080115 | 0:bf7b9fba3924 | 16 | * warranty that such application will be suitable for the specified |
| frank26080115 | 0:bf7b9fba3924 | 17 | * use without further testing or modification. |
| frank26080115 | 0:bf7b9fba3924 | 18 | ****************************************************************************** |
| frank26080115 | 0:bf7b9fba3924 | 19 | |
| frank26080115 | 0:bf7b9fba3924 | 20 | @Example description: |
| frank26080115 | 0:bf7b9fba3924 | 21 | Purpose: |
| frank26080115 | 0:bf7b9fba3924 | 22 | This example describes how to configure CAN operation in two boards seperately |
| frank26080115 | 0:bf7b9fba3924 | 23 | Process: |
| frank26080115 | 0:bf7b9fba3924 | 24 | Using 2 CAN1 peripheral on two boards to test. |
| frank26080115 | 0:bf7b9fba3924 | 25 | This example just supports explicit standard/extended ID format. |
| frank26080115 | 0:bf7b9fba3924 | 26 | Both CAN1 peripherals are set baudrate at 125KHz |
| frank26080115 | 0:bf7b9fba3924 | 27 | |
| frank26080115 | 0:bf7b9fba3924 | 28 | CAN transmit: |
| frank26080115 | 0:bf7b9fba3924 | 29 | Initialize 4 CAN messages: |
| frank26080115 | 0:bf7b9fba3924 | 30 | - 1st message with 11-bit ID which exit in AF Look-up Table |
| frank26080115 | 0:bf7b9fba3924 | 31 | - 2nd message with 11-bit ID which not exit in AF Look-up Table |
| frank26080115 | 0:bf7b9fba3924 | 32 | - 3th Message with 29-bit ID which exit in AF Look-up Table |
| frank26080115 | 0:bf7b9fba3924 | 33 | - 4th Message with 29-bit ID which exit in AF Look-up Table |
| frank26080115 | 0:bf7b9fba3924 | 34 | These messages will be send to CAN peripheral in another board |
| frank26080115 | 0:bf7b9fba3924 | 35 | CAN receive: |
| frank26080115 | 0:bf7b9fba3924 | 36 | Setup a simple AFLUT. It just has two sections: |
| frank26080115 | 0:bf7b9fba3924 | 37 | - Explicit Standard Frame Format Identifier Section |
| frank26080115 | 0:bf7b9fba3924 | 38 | - Explicit Extended Frame Format Identifier Section |
| frank26080115 | 0:bf7b9fba3924 | 39 | Receive message from another board. Whenever CAN1 receive message that has ID exit |
| frank26080115 | 0:bf7b9fba3924 | 40 | in its AFLUT, receive interrupt occurs, CAN service routine will be invoked to receive |
| frank26080115 | 0:bf7b9fba3924 | 41 | message and save its data in array "AFRxMsg[]" and print to serial display via UART0 port. |
| frank26080115 | 0:bf7b9fba3924 | 42 | In this case, messages 1,3 will be received. |
| frank26080115 | 0:bf7b9fba3924 | 43 | |
| frank26080115 | 0:bf7b9fba3924 | 44 | Open serial display to observe CAN transfer processing. |
| frank26080115 | 0:bf7b9fba3924 | 45 | |
| frank26080115 | 0:bf7b9fba3924 | 46 | @Directory contents: |
| frank26080115 | 0:bf7b9fba3924 | 47 | \EWARM: includes EWARM (IAR) project and configuration files |
| frank26080115 | 0:bf7b9fba3924 | 48 | \Keil: includes RVMDK (Keil)project and configuration files |
| frank26080115 | 0:bf7b9fba3924 | 49 | |
| frank26080115 | 0:bf7b9fba3924 | 50 | lpc17xx_libcfg.h: Library configuration file - include needed driver library for this example |
| frank26080115 | 0:bf7b9fba3924 | 51 | makefile: Example's makefile (to build with GNU toolchain) |
| frank26080115 | 0:bf7b9fba3924 | 52 | can_test_two_kit.c: Main program |
| frank26080115 | 0:bf7b9fba3924 | 53 | |
| frank26080115 | 0:bf7b9fba3924 | 54 | @How to run: |
| frank26080115 | 0:bf7b9fba3924 | 55 | Hardware configuration: |
| frank26080115 | 0:bf7b9fba3924 | 56 | This example was tested on two board: |
| frank26080115 | 0:bf7b9fba3924 | 57 | Keil MCB1700 with LPC1768 vers.1 |
| frank26080115 | 0:bf7b9fba3924 | 58 | These jumpers must be configured as following: |
| frank26080115 | 0:bf7b9fba3924 | 59 | - VDDIO: ON |
| frank26080115 | 0:bf7b9fba3924 | 60 | - VDDREGS: ON |
| frank26080115 | 0:bf7b9fba3924 | 61 | - VBUS: ON |
| frank26080115 | 0:bf7b9fba3924 | 62 | - Remain jumpers: OFF |
| frank26080115 | 0:bf7b9fba3924 | 63 | |
| frank26080115 | 0:bf7b9fba3924 | 64 | CAN connection: |
| frank26080115 | 0:bf7b9fba3924 | 65 | - Two pins CAN-Pin2 (CAN-L) must be connected between two board |
| frank26080115 | 0:bf7b9fba3924 | 66 | - Two pins CAN-Pin7 (CAN-H) must be connected between two board |
| frank26080115 | 0:bf7b9fba3924 | 67 | (Common ground must be connected together between two board) |
| frank26080115 | 0:bf7b9fba3924 | 68 | |
| frank26080115 | 0:bf7b9fba3924 | 69 | Serial display configuration: (e.g: TeraTerm, Hyperterminal, Flash Magic...) |
| frank26080115 | 0:bf7b9fba3924 | 70 | 115200bps |
| frank26080115 | 0:bf7b9fba3924 | 71 | 8 data bit |
| frank26080115 | 0:bf7b9fba3924 | 72 | No parity |
| frank26080115 | 0:bf7b9fba3924 | 73 | 1 stop bit |
| frank26080115 | 0:bf7b9fba3924 | 74 | No flow control |
| frank26080115 | 0:bf7b9fba3924 | 75 | |
| frank26080115 | 0:bf7b9fba3924 | 76 | Running mode: |
| frank26080115 | 0:bf7b9fba3924 | 77 | This example can run on RAM/ROM mode. |
| frank26080115 | 0:bf7b9fba3924 | 78 | |
| frank26080115 | 0:bf7b9fba3924 | 79 | Note: If want to burn hex file to board by using Flash Magic, these jumpers need |
| frank26080115 | 0:bf7b9fba3924 | 80 | to be connected: |
| frank26080115 | 0:bf7b9fba3924 | 81 | - MCB1700 with LPC1768 ver.1: |
| frank26080115 | 0:bf7b9fba3924 | 82 | + RST: ON |
| frank26080115 | 0:bf7b9fba3924 | 83 | + ISP: ON |
| frank26080115 | 0:bf7b9fba3924 | 84 | - IAR LPC1768 KickStart vers.A: |
| frank26080115 | 0:bf7b9fba3924 | 85 | + RST_E: ON |
| frank26080115 | 0:bf7b9fba3924 | 86 | + ISP_E: ON |
| frank26080115 | 0:bf7b9fba3924 | 87 | |
| frank26080115 | 0:bf7b9fba3924 | 88 | (Please reference "LPC1000 Software Development Toolchain" - chapter 4 "Creating and working with |
| frank26080115 | 0:bf7b9fba3924 | 89 | LPC1000CMSIS project" for more information) |
| frank26080115 | 0:bf7b9fba3924 | 90 | |
| frank26080115 | 0:bf7b9fba3924 | 91 | Step to run: |
| frank26080115 | 0:bf7b9fba3924 | 92 | - Step 1: Setting "CAN_TRANSMIT = 1" (in main.c file) -> build and burn hex file in the board transmitter |
| frank26080115 | 0:bf7b9fba3924 | 93 | - Step 2: Setting "CAN_TRANSMIT = 0" (in main.c file) -> build and burn hex file in the board receiver |
| frank26080115 | 0:bf7b9fba3924 | 94 | Note that: receive program also can run in RAM mode. In this case, not burn hex file but run it with debugger. |
| frank26080115 | 0:bf7b9fba3924 | 95 | - Step 3: Connect UART0 on board receiver to COM port on your computer |
| frank26080115 | 0:bf7b9fba3924 | 96 | - Step 4: Configure hardware and serial display as above instruction |
| frank26080115 | 0:bf7b9fba3924 | 97 | - Step 5: Run example: |
| frank26080115 | 0:bf7b9fba3924 | 98 | - Re-set board receiver. |
| frank26080115 | 0:bf7b9fba3924 | 99 | - Re-set board transmitter. |
| frank26080115 | 0:bf7b9fba3924 | 100 | |
| frank26080115 | 0:bf7b9fba3924 | 101 | (Pls see "LPC17xx Example Description" document - chapter "Examples > CAN > CAN_test_two_kit" |
| frank26080115 | 0:bf7b9fba3924 | 102 | for more details) |
| frank26080115 | 0:bf7b9fba3924 | 103 | |
| frank26080115 | 0:bf7b9fba3924 | 104 | @Tip: |
| frank26080115 | 0:bf7b9fba3924 | 105 | - Open \EWARM\*.eww project file to run example on IAR |
| frank26080115 | 0:bf7b9fba3924 | 106 | - Open \RVMDK\*.uvproj project file to run example on Keil |
| frank26080115 | 0:bf7b9fba3924 | 107 |