文件列表:

lin_master\lin_master\DefaultSession.hsf (3865, 2007-08-23)
lin_master\lin_master\E8.hsf (36192, 2007-08-27)
lin_master\lin_master\E8.ini (154, 2007-08-14)
lin_master\lin_master\lin_dev.c (19447, 2007-08-14)
lin_master\lin_master\lin_dev.h (14639, 2007-08-27)
lin_master\lin_master\lin_master.hwp (14935, 2007-08-27)
lin_master\lin_master\local.lnt (1249, 2007-08-14)
lin_master\lin_master\main_lin_master.c (12642, 2007-08-14)
lin_master\lin_master\Master.nav (9487, 2007-08-27)
lin_master\lin_master\Master.tps (980, 2007-08-27)
lin_master\lin_master\Program_RSK.hsf (10312, 2007-08-23)
lin_master\lin_master\Program_RSK.ini (154, 2007-01-29)
lin_master\lin_master\release\Master.map (28075, 2007-08-14)
lin_master\lin_master\release\Master.mot (14508, 2007-08-14)
lin_master\lin_master\release\Master.x30 (402286, 2007-08-14)
lin_master\lin_master\sect30.inc (7924, 2006-09-08)
lin_master\lin_master.ARF (351, 2006-12-05)
lin_master\lin_master.BKW (946, 2006-12-05)
lin_master\lin_master.Hbp (24, 2006-07-23)
lin_master\lin_master.hws (946, 2006-11-07)
lin_master\lin_master.tws (712, 2006-12-01)
lin_master\lin_master\debug (0, 2008-12-17)
lin_master\lin_master\release (0, 2008-12-17)
lin_master\lin_master (0, 2008-12-17)
lin_master (0, 2008-12-17)

I have divided the API code into 4 pairs of “.c” and “.h” files. lin_api.c & .h has all of the API function calls. I have tried to make this pair MCU independent, but that was not fully possible. The R8C has the LIN hardware block that requires different handling – especially for LIN Break detection – and the R8C and M16C have a different byte order from the H8/Tiny. So this code does have a few differences. lin_low_level.c & .h are the low-level driver routines that support the API. Again I have tried to make these MCU independent, but there are a few differences that could not be avoided. Bottom line, the LIN API code is at least 90% common among all of our processors, and the source files are written in a parallel structure, to simplify code maintenance as much as possible. To set up a LIN project, the user has to select the proper set of API and low level source files for the MCU he is using (no edits required or allowed), configure the processor dependent files to fit the chosen MCU and his application hardware and then configure the LIN device files to realize the functionality of his LIN devices. lin_dev.c & .h have all of the LIN specific (LIN device specific, actually) code and has nothing that is processor or hardware dependent. The user can use these same files for any of our processors. lin_hw.c & .h is completely processor dependent and has all of the configuration items, such as UART and timer selections, that might vary according to the processor used and the application hardware. Basically this means setting up the message frames and signals to define the data to be transferred. I have an extensive document that describes exactly how to do this, line by line. "LIN API User's Guide V1_1.doc". So far, GE has been quite successful in getting their projects to run using this code and the documentation provided. One of my MBO’s for this period is to write a Windows application to make the LIN config- uration menu driven. I am buried so deep in other things that I don’t know if I will ever be able to get to it.

近期下载者：

相关文件：

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

收藏者：