The code for µC/Modbus is found in the following directories.
...
| Table of Contents |
|---|
Target Independent Source Code
\Micrium\Software\uC-Modbus\Source
...
mb.c Master/Slave independent code mb.h mb_def.h Modbus Definitions mb_util.c ASCII convertions utilities mbs_core.c Slave specific code mbm_core.c Master specific code
...
RTOS Interface
\Micrium\Software\uC-Modbus\OS\uCOS-II
...
These directories contains the code to interface to the µC/OS-II and µC/OS-III RTOSs and contains the following file:
mb_os.c (See Section 7.00See RTOS Interface)
If you interface µC/Modbus to different RTOSs, you would place an mb_os.c file in a separate directory. In other words, all RTOS interface files should be called mb_os.c but the specifics of the actual RTOS you use would be placed in a different directory. When you build your product, you obviously need to select only one RTOS interface – the one specific to your RTOS.
...
This directory contains the code to use µC/Modbus-S in a single threaded environment witouth without the need of an RTOS.
mb_os.c (See Section 8.00 No-OS Interface)
mb_os.h (See Section 8.00See No-OS Interface)
...
Product Specific Files
???\Product
This directory contains your application code. You need to provide the following files:
mb_cfg.h (See Section 4.00 Configuring µC/Modbus)
mb_data.c (See Section 5.00 µC/Modbus-S, Accessing Application Data)
mb_bsp.c (See Section 6.00)
...
(See Board Support Package (BSP))
CPU and Compiler Specific Files
\Micrium\Software\uC-CPU\<CPU-type>\<compiler>
...