2022/07/30 CHIP git hash code 67b4746ad8 What is it I would like to consider Exchange Context(EC) as a "channel" in each seassion. Every device/controller would hold a peer's session if they are connected. However, there are many different types of messages would be sent between controller/device, so we need a specified channel to handle each type of message. In addition, these ECs have been running in a session, so they could use all the resource of the session. That is, EC is not like session which has extreme complicated establishment process. A lot of time, CHIP stack would create a new EC just for one message. Thus, EC is also kind of a temporary channel.
Jul 30, 20222022/06/05 CHIP git hash code 67b4746ad8 How message goes Following the calling stack of sending/receiving message word by word shows a very basic idea of how the message being handled. However, we will have a better understanding of this project if we take a look from structure point of view. So, I would like to put down some note about these two classes: Seesion and ExchangeContext(next post).
Jun 12, 20222022/05/14 CHIP git hash code 67b4746ad8 Setup Python controller running on MAC Lock-app running on thunderboard sense 2 OpenThread board router on Raspberry pi 2B The lock-app example
May 14, 20222022/04/23 CHIP git hash code 67b4746ad8 I would like to follow the calling stack to understand how CHIP stack receives message. Bascially, it's like a reverse calling stack of "Send Message." Just give you a heads-up, there is an engine to handle CHIP-over-Bluetooth Low Energy (CHIPoBLE) message and I skipped this module because I think it would be easier to understand this kind of code if we got the specification first. Setup Python controller running on MAC
May 7, 2022or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up