|
Support for Open Supervised Device Protocol (OSDP) in Zephyr
Hi Thea, Thanks for helping me out; have you had a chance to look into this? Sid. ---- On Sun, 14 Apr 2019 01:24:31 +0530 Thea Aldrich <aldrich.thea@...> wrote ----
Hi Thea, Thanks for helping me out; have you had a chance to look into this? Sid. ---- On Sun, 14 Apr 2019 01:24:31 +0530 Thea Aldrich <aldrich.thea@...> wrote ----
|
By
...
· #5933
·
|
|
Support for Open Supervised Device Protocol (OSDP) in Zephyr
Hi, Can anyone comment on this? It'd be helpful to know such information earlier on. Sid. ---- On Sun, 07 Apr 2019 00:39:04 +0530 Siddharth Chandrasekaran <siddharth@...> wrote ----
Hi, Can anyone comment on this? It'd be helpful to know such information earlier on. Sid. ---- On Sun, 07 Apr 2019 00:39:04 +0530 Siddharth Chandrasekaran <siddharth@...> wrote ----
|
By
...
· #5920
·
|
|
Support for Open Supervised Device Protocol (OSDP) in Zephyr
Hello, I'm working on an project that involves Open Supervised Device Protocol (OSDP) [1], an access control communication protocol used in the security industry. I'm working on this as an application
Hello, I'm working on an project that involves Open Supervised Device Protocol (OSDP) [1], an access control communication protocol used in the security industry. I'm working on this as an application
|
By
...
· #5894
·
|
|
Shell add 'exit' command to leave current module
Hello Anas, Thanks, already raised PR #320. Siddharth.
Hello Anas, Thanks, already raised PR #320. Siddharth.
|
By
...
· #600
·
|
|
Shell add 'exit' command to leave current module
Hello, In shell, to select a module, we use 'select <module_name>'. When inside a module, there is no indication on how one has to leave the module. Would it be better to have an 'exit' ? I know (afte
Hello, In shell, to select a module, we use 'select <module_name>'. When inside a module, there is no indication on how one has to leave the module. Would it be better to have an 'exit' ? I know (afte
|
By
...
· #598
·
|
|
Porting Zephyr to STM32F103C8T6 Minimum System Development Board
Thanks Erwan, now I understand why the switch was not created. That still leaves us with how and where we have to create those switches to enable the right hearers. Is there any _nice_ way to achieve
Thanks Erwan, now I understand why the switch was not created. That still leaves us with how and where we have to create those switches to enable the right hearers. Is there any _nice_ way to achieve
|
By
...
· #559
·
|
|
Porting Zephyr to STM32F103C8T6 Minimum System Development Board
Hi Erwan, Thanks, I did notice that. Infact that's the reason I ORed it to existing headder. But was unsure since none of the existing includes had a anything ORed with them. Perhaps, we should OR all
Hi Erwan, Thanks, I did notice that. Infact that's the reason I ORed it to existing headder. But was unsure since none of the existing includes had a anything ORed with them. Perhaps, we should OR all
|
By
...
· #553
·
|
|
Porting Zephyr to STM32F103C8T6 Minimum System Development Board
Hi Erwan, Thanks for your speedy response, that was very helpful. After adding the pin mux settings, I was able to get the UART to work. I added a new CONFIG value for STM32F103X8 and had to do a bunc
Hi Erwan, Thanks for your speedy response, that was very helpful. After adding the pin mux settings, I was able to get the UART to work. I added a new CONFIG value for STM32F103X8 and had to do a bunc
|
By
...
· #549
·
|
|
Porting Zephyr to STM32F103C8T6 Minimum System Development Board
Hello, I am trying to port Zephyr into one of the cheap, breadboard friendly, "STM32F103C8T6 Minimum System Development Boards" (link not attached due to overwhelming results in Google) and I am facin
Hello, I am trying to port Zephyr into one of the cheap, breadboard friendly, "STM32F103C8T6 Minimum System Development Boards" (link not attached due to overwhelming results in Google) and I am facin
|
By
...
· #539
·
|