Bmbed connects different boards/ microcontrollers and Windows PCs to a network. With the Bmbed High-Level-Protocol you can communicate from node to node (peer to peer).
Every network node represent a physical computing unit (e.g. PC, microcontroller, evaluation board, etc.). The node itself can own additionally logical sub-nodes. All these nodes also own a unique address which is valid in the entire network.
Example:
Node A sends a message to sub-node C2 to switch on the LED.
The protocol implementation is respondsible to execute the wanted action like blinking LEDs or to get an acknwoledge message. Bmbed gives you the framework. The customer can adapt it, change it, expand it.
The Bmbed High-Level-Prorocol is very simple. It is easy to use it and to adapt it. The protocol is valid for the entire Bmbed network. You can also use the Bmbed protocol for internal software communication.
Receiver
This is the reveiver node address of the message (who is getting the message). Bmbed pre-defines addresses e.g. 0x0010 for a TI F28069.
Sender
This is the sender node address of the message (who is sending the message). Sender and receiver address are type-identical.
Command
This 16 bits define the command of the message (What kind of message). Bmbed pre-defines about 60 commands for different jobs e.g. information message 0x0004.
Aux
Auxilliary data. This data can be bounded with the message or it can be user defined.
Data
This is the payload of the message. Always 48 bytes. The message definition determines the used number of bytes.
Comment
The Bmbed High-Level-Protocol doesn't own a length field. The transfer data length is always 56 bytes. If all 48 payload bytes are used or not. This has to be considered with a new message define.
This 56 bytes can be expanded in the low-level handling. It depends on the interface. e.g. a UART interface adds 2 bytes for a CRC. But these two bytes are just valid within the interface.