文件列表:

1基站多标签V3.6\decadriver\deca_device.c (116291, 2018-03-21)
1基站多标签V3.6\decadriver\deca_device_api.h (62414, 2015-11-30)
1基站多标签V3.6\decadriver\deca_params_init.c (3952, 2015-12-03)
1基站多标签V3.6\decadriver\deca_param_types.h (1754, 2015-12-03)
1基站多标签V3.6\decadriver\deca_range_tables.c (14481, 2015-11-27)
1基站多标签V3.6\decadriver\deca_regs.h (76888, 2015-12-03)
1基站多标签V3.6\decadriver\deca_types.h (1124, 2015-11-13)
1基站多标签V3.6\decadriver\deca_version.h (1177, 2015-12-04)
1基站多标签V3.6\Libraries\CMSIS\CM3\CoreSupport\core_cm3.c (17273, 2010-06-07)
1基站多标签V3.6\Libraries\CMSIS\CM3\CoreSupport\core_cm3.h (85714, 2011-02-09)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\Release_Notes.html (26297, 2011-03-14)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\arm\startup_stm32f10x_cl.s (15766, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\arm\startup_stm32f10x_hd.s (15503, 2011-10-06)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\arm\startup_stm32f10x_hd_vl.s (15692, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\arm\startup_stm32f10x_ld.s (12376, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\arm\startup_stm32f10x_ld_vl.s (13656, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\arm\startup_stm32f10x_md.s (12765, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\arm\startup_stm32f10x_md_vl.s (14073, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\arm\startup_stm32f10x_xl.s (15955, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\gcc_ride7\startup_stm32f10x_cl.s (13072, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\gcc_ride7\startup_stm32f10x_hd.s (13160, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\gcc_ride7\startup_stm32f10x_hd_vl.s (12482, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\gcc_ride7\startup_stm32f10x_ld.s (9814, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\gcc_ride7\startup_stm32f10x_ld_vl.s (10562, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\gcc_ride7\startup_stm32f10x_md.s (10269, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\gcc_ride7\startup_stm32f10x_md_vl.s (11058, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\gcc_ride7\startup_stm32f10x_xl.s (13261, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\iar\startup_stm32f10x_cl.s (16626, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\iar\startup_stm32f10x_hd.s (16229, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\iar\startup_stm32f10x_hd_vl.s (15675, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\iar\startup_stm32f10x_ld.s (12650, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\iar\startup_stm32f10x_ld_vl.s (12950, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\iar\startup_stm32f10x_md.s (12912, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\iar\startup_stm32f10x_md_vl.s (13601, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\iar\startup_stm32f10x_xl.s (16628, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\TrueSTUDIO\startup_stm32f10x_cl.s (12604, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\TrueSTUDIO\startup_stm32f10x_hd.s (12592, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\TrueSTUDIO\startup_stm32f10x_hd_vl.s (12239, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\TrueSTUDIO\startup_stm32f10x_ld.s (9826, 2011-03-10)
1基站多标签V3.6\Libraries\CMSIS\CM3\DeviceSupport\ST\STM32F10x\startup\TrueSTUDIO\startup_stm32f10x_ld_vl.s (10275, 2011-03-10)
... ...

/** @page CAN_Networking CAN Networking example @verbatim ******************** (C) COPYRIGHT 2011 STMicroelectronics ******************* * @file CAN/Networking/readme.txt * @author MCD Application Team * @version V3.5.0 * @date 08-April-2011 * @brief Description of the CAN Networking example. ****************************************************************************** * THE PRESENT FIRMWARE WHICH IS FOR GUIDANCE ONLY AIMS AT PROVIDING CUSTOMERS * WITH CODING INFORMATION REGARDING THEIR PRODUCTS IN ORDER FOR THEM TO SAVE * TIME. AS A RESULT, STMICROELECTRONICS SHALL NOT BE HELD LIABLE FOR ANY * DIRECT, INDIRECT OR CONSEQUENTIAL DAMAGES WITH RESPECT TO ANY CLAIMS ARISING * FROM THE CONTENT OF SUCH FIRMWARE AND/OR THE USE MADE BY CUSTOMERS OF THE * CODING INFORMATION CONTAINED HEREIN IN CONNECTION WITH THEIR PRODUCTS. ****************************************************************************** @endverbatim @par Example Description This example shows how to configure the CAN peripheral to send and receive CAN frames in normal mode. The sent frames are used to control Leds by pressing key push button. The CAN serial communication link is a bus to which a number of units may be connected. This number has no theoretical limit. Practically the total number of units will be limited by delay times and/or electrical loads on the bus line. This program behaves as follows: - After reset LED1 is ON - By Pressing on KEY Button : LED2 turns ON and all other Leds are OFF, on the N eval boards connected to the bus. - Press on KEY Button again to send CAN Frame to command LEDn+1 ON, all other Leds are OFF on the N eval boards. @note This example is tested with a bus of 3 units. The same program example is loaded in all units to send and receive frames. @note Any unit in the CAN bus may play the role of sender (by pressing KEY button) or receiver. The CAN is configured as follow: - Bit Rate = 1 Mbit/s - CAN Clock = external clock (HSE) - ID Filter = All identifiers are allowed - RTR = Data - DLC = 1 byte - Data: Led number that should be turned ON User can select CAN1 or CAN2 cell using the private defines in main.c : @code #define __CAN1_USED__ /* #define __CAN2_USED__*/ @endcode @note When using CAN2, please check that you device is Connectivity line. @par Directory contents - CAN/Networking/platform_config.h Hardware configuration header file - CAN/Networking/stm32f10x_conf.h Library Configuration file - CAN/Networking/stm32f10x_it.c Interrupt handlers - CAN/Networking/stm32f10x_it.h Interrupt handlers header file - CAN/Networking/main.c Main program - CAN/Networking/system_stm32f10x.c STM32F10x system source file @par Hardware and Software environment - This example runs on STM32F10x Connectivity line, High-Density, Medium-Density, XL-Density and Low-Density Devices. - This example has been tested with STMicroelectronics STM3210C-EVAL (Connectivity line), STM3210E-EVAL (High-Density and XL-Density) and STM3210B-EVAL (Medium-Density) evaluation boards and can be easily tailored to any other supported device and development board. To select the STMicroelectronics evaluation board used to run the example, uncomment the corresponding line in CAN/Networking/platform_config.h or stm32_eval.h file - STM3210C-EVAL Set-up - Use LED1, LED2, LED3 and LED4 connected respectively to PD.07, PD.13, PF.03 and PD.04 pins - Use Key Push Button connected to PB9 - Connect a female/female CAN cable between at least 2 EVAL CAN connectors (on STM3210E-EVAL (CN2)/ STM3210C-EVAL (CN3 or CN4) boards) - Connector 1 DB9_PIN2 to Connector 2 DB9_PIN2 (CAN_L) - Connector 1 DB9_PIN5 to Connector 2 DB9_PIN5 ( GND ) - Connector 1 DB9_PIN7 to Connector 2 DB9_PIN7 (CAN_H) @note JP6 or JP5 must be fitted. - STM3210E-EVAL Set-up - Use LED1, LD2, LED3 and LED4 leds connected respectively to PF.06, PF0.7, PF.08 and PF.09 pins - Use Key Push Button connected to PG8 - Connect a female/female CAN cable between at least 2 EVAL CAN connectors (on STM3210B-EVAL (CN2)/ STM3210E-EVAL (CN4) boards) - Connector 1 DB9_PIN2 to Connector 2 DB9_PIN2 (CAN_L) - Connector 1 DB9_PIN5 to Connector 2 DB9_PIN5 ( GND ) - Connector 1 DB9_PIN7 to Connector 2 DB9_PIN7 (CAN_H) @note JP6 must be fitted. - STM3210B-EVAL Set-up - Use LED1, LED2, LED3 and LED4 leds connected respectively to PC.06, PC.07, PC.08 and PC.09 pins - Use Key Push Button connected to PB9 - Connect a female/female CAN cable between at least 2 EVAL CAN connectors (on STM3210B-EVAL (CN2)/ STM3210E-EVAL (CN4) boards) - Connector 1 DB9_PIN2 to Connector 2 DB9_PIN2 (CAN_L) - Connector 1 DB9_PIN5 to Connector 2 DB9_PIN5 ( GND ) - Connector 1 DB9_PIN7 to Connector 2 DB9_PIN7 (CAN_H) @note JP3 must be fitted. @note Any unit in the CAN bus may play the role of sender (by pressing on the key) or receiver. @par How to use it ? In order to make the program work, you must do the following : - Copy all source files from this example folder to the template folder under Project\STM32F10x_StdPeriph_Template - Open your preferred toolchain - Rebuild all files and load your image into target memory - Run the example - In the first time the all leds are OFF. - By Pressing on Key Button : LED1 turn ON and all other Leds are OFF, on the N eval-boards connected to the bus. - Press on Key Button again to send CAN Frame to command LEDn+1 ON, all other Leds are OFF on the N eval-boards. @note - Low-density Value line devices are STM32F100xx microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes. - Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes. - Medium-density Value line devices are STM32F100xx microcontrollers where the Flash memory density ranges between *** and 128 Kbytes. - Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx microcontrollers where the Flash memory density ranges between *** and 128 Kbytes. - High-density Value line devices are STM32F100xx microcontrollers where the Flash memory density ranges between 256 and 512 Kbytes. - High-density devices are STM32F101xx and STM32F103xx microcontrollers where the Flash memory density ranges between 256 and 512 Kbytes. - XL-density devices are STM32F101xx and STM32F103xx microcontrollers where the Flash memory density ranges between 512 and 1024 Kbytes. - Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers. *

© COPYRIGHT 2011 STMicroelectronics

*/

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：