Hello Dharam, Good day to you. Do you have a rough estimate if you could share on the memory requirements is it more than 1MB?
On Wednesday, August 21, 2019 at 3:52:48 PM UTC+5:30 Dharam Kumar wrote: > Hello Jaehong, > I've been able to put grpc framework on wiced rtos APIs > <https://www.cypress.com/products/wiced-software>. Basically, Wiced SDK > from Cypress provides abstracted RTOS/Networking APIs which is underneath > implemented by different rtos/network stacks. For example - > Expresslogic's ThreadX/NetX, FreeRTOS/lwip etc. I was able to get threads > running, start grpc core service, create grpc endpoints(tcp) etc... > > Please note that grpc library does not support embedded TLS stacks like > mbed-tls(from ARM). Also, default grpc transports module(chttp2?)might be > too heavy for your embedded platform. So, you may have to work on these > aspect. So be remindful of how "embedded" you can go. For example - it > probably won't work on a board/platform with 256KB of RAM. > > In nutshell, putting grpc framework is totally possible. > @Nicolas Noble - I'm not sure about the grpc being intertwined with posix > part - as i recollect there are pretty good grpc abstractions for different > platforms(windows, unix, posix etc.) - i just built on that and was able to > get the grpc core up and running. > > Br, > Dharam > > ------------------------------ > *From:* [email protected] <[email protected]> on behalf of > Nicolas Noble <[email protected]> > *Sent:* Wednesday, August 21, 2019 12:31 AM > *To:* jaehong park <[email protected]> > *Cc:* grpc.io <[email protected]> > *Subject:* Re: [grpc-io] Re: gRPC for embedded systems( for example - > RTOS like ThreadX, FreeRTOS etc. ) > > We have no plans for that, and the current codebase is way too intertwined > with posix to ever work on FreeRTOS / lwip. A full third party > implementation of grpc would be needed for that at this point. > > On Tue, Aug 20, 2019 at 10:23 AM jaehong park <[email protected]> wrote: > > Hello Dharam, > > I'm having a similar project like below question. > (III.Any effort in community in bringing gRPC for embedded devices(for > RTOSes) ? ) > Do you have any progress this issue? > > Could you let me know where I can find the answer for this? > > Thanks, > Jaehong > > > > On Tuesday, January 23, 2018 at 9:39:07 PM UTC-8, [email protected] > wrote: > > > Hello folks, > I'm working on a project where we are planning to create a Google > Assistant service instance on embedded/deeply embedded devices( non-linux, > ARM processors running RTOS like ThreadX, FreeRTOS etc. ) > Our system has support for building executables for c/c++ etc. but it is > not same as linux( for example - no posix availability ). > Of course, like RTOSes these days, we have wrappers for providing > OS/Networking functionality for applications/libraries to use. > > My questions are: > > i. How fit gRPC is for embedded devices? I can see abstraction for > different platforms in "port_platform.h" file used to build grpc-core with > options given in the file. > My first thought is it should be doable if I adapt port_platform.h > and build grpc-core with the capabilities provided by our system. > > ii. How deep gRPC's love is for posix? If any platform/devices does not > provide any posix-like high level APIs, will gRPC still work as expected? > How straight-forward such a task is going to be? > > iii. Any effort in community in bringing gRPC for embedded devices(for > RTOSes) ? Would not it be great to have a tiny(and limited) gRPC library > which can be > easily integrated to embedded devices ? And such a thing supported by > gRPC community/authors ? > > I understand that I can get most of the answers from reading the code > itself(which I'm doing btw). > But it would be nice to know insights/perspective of gRPC authors and > community folks who understands gRPC better than me. > > Open for suggestions/feedback. > > Best regards, > Dharam > > -- > You received this message because you are subscribed to the Google Groups " > grpc.io" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/grpc-io/5a72e682-031f-415b-830f-7818810f434f%40googlegroups.com > > <https://groups.google.com/d/msgid/grpc-io/5a72e682-031f-415b-830f-7818810f434f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to a topic in the > Google Groups "grpc.io" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/grpc-io/A0PlDMi2an8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/grpc-io/CAEvr0PEr7TM5m3JUtP04Jgc3tZj6zSx%2BmfRdGJNh5hwsB0HH6Q%40mail.gmail.com > > <https://groups.google.com/d/msgid/grpc-io/CAEvr0PEr7TM5m3JUtP04Jgc3tZj6zSx%2BmfRdGJNh5hwsB0HH6Q%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > > This message and any attachments may contain confidential information from > Cypress or its subsidiaries. If it has been received in error, please > advise the sender and immediately delete this message. > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/grpc-io/fc1b3260-0ce8-49f6-acb0-f7df4c8f8d16n%40googlegroups.com.
