So as already mentioned, the trick would be to stick to the object files that implement only the _katcl functions - that shouldn't require some basics (malloc, strcmp, etc) but not the full unix io API. That might mean building individual object files (parse.c, line.c etc) rather than the full library.
regards marc On Mon, Feb 2, 2015 at 6:22 AM, Jason Manley <[email protected]> wrote: > Hi Pablo > > I'm hoping Marc will chime-in here, as the author of the package. My > suspicion is that these are expected standard libraries that should be > supplied with your dev environment. If PIC don't supply them, then perhaps > you can compile without those features, or rewrite those few functions > yourself? > > Jason Manley > CBF Manager > SKA-SA > > Cell: +27 82 662 7726 > Work: +27 21 506 7300 > > On 30 Jan 2015, at 16:34, Pablo Vasquez <[email protected]> wrote: > > > Hi Jason, > > > > Thanks for the reply. The problem that I have when trying to implement > this library on the PIC32 is that on the compiler that I use there is no > <sys/select.h> file. Also there are some functions defined inside this .h > files that are missing. > > > > Do you know where can I get these special .h files that were used with > this lightweight processors? > > > > Best regards. > > > > > > On Mon, Jan 26, 2015 at 11:35 AM, Jason Manley <[email protected]> > wrote: > > There is a C-based KATCP library that has been used successfully on > lightweight (8-bit) processors in the past. It might make your life a > little easier, as the parsing and everything's already taken care of. Try > this: https://github.com/ska-sa/katcp_devel > > > > Jason Manley > > CBF Manager > > SKA-SA > > > > Cell: +27 82 662 7726 > > Work: +27 21 506 7300 > > > > On 26 Jan 2015, at 15:50, Pablo Vasquez <[email protected]> wrote: > > > > > Hi, > > > > > > I'm trying to get a 32 bits PIC controller to work with a ROACH. I'm > establishing communication through a standard TCP connection and getting > data from a socket opened between the PIC and the ROACH. About this I have > two questions: > > > > > > 1.- What is the package size, also know as maximum segment size, that > the ROACH/KATCP uses for transmission over the LAN port? > > > I need to know this so I can work with the same segment size on both > platforms and get proper data flow synchronization. > > > > > > > > > 2.- Do you know where can I find more info about the way struct.pack > works? > > > I need to "unpack" the data coming in the string from the ROACH, but > since I have no python libraries on the PIC I need to handle the unpacking > myself. Looking directly at the data I seem to recognize some patterns > (i.e. "/0" at the end of each integer per channel) but this patterns are > not behaving the same through the whole string. > > > > > > Any hints will help. > > > > > > Best regards. > > > > > > -- > > > Pablo Vasquez > > > Ingeniero Eléctrico > > > DAS Universidad de Chile > > > (+562)29771119 > > > > > > > > > > -- > > Pablo Vasquez > > Ingeniero Eléctrico > > DAS Universidad de Chile > > (+562)29771119 > > >
