Well... count me as an enthusiastic.
Read through the web page (which I thought was well written at the right detail
level). Seems like an excellent approach. I'm surprised there's not more
chatter about the announcement on this group.
Very, very happy to see Python support.
When is 7370 targeted? What can I do to make to happen faster?
A question. Are the canctl, dioctl, and spictl protocols/apis you mention
proprietary technology systems protocols/apis? or are they some industry
standard? Are they existing now or futures?
What's the license and source availability?
Only concern might be speed on some hi bandwidth requirements. I'm sure it
will be fine for many applications. I would suspect that many applications
would need to bypass at least the IP layer and/or server side "locking".
To that end I suggest that the server side api to the hardware be "clean" so a
user program could talk directly to that api to the hardware (bypassing IP
layer). Maybe incorporate a mechanism in protocol to tell tsctl that it can't
use subsystem xyz because user is talking to it directly. The design philosophy
looks like you might have addressed this.
I couldn't tell in a quick read whether you were doing UDP or TCP. I'd support
both. The UDP for speed when it's from process to process inside the cpu. The
TCP for reliability when it's off chip. Like from the laptop in my office over
a satellite link to 7370 in the middle of the ocean. If I had to choose which
to do first, I'll probably pick UDP, but I would make sure there is an upgrade
path in the API to TCP (or maybe some of the unix internal queues/shared memory
for more maybe more speed) which would allow you to implement other transport
mechanisms in future without breaking UDP code in the field.
Looking forward to seeing the code and trying it. Will you make announcements
to this group at signficant release points?
--- In Michael Schmidt <> wrote:
>
> Hello All,
>
> I have posted documentation for the tsctl project, which will be
> released soon.
>
> http://oz.embeddedarm.com/~michael/tsctl/
>
> Currently this document is updated daily to reflect updates to the
> project. The "revision log" section documents changes to the document
> itself.
>
> tsctl was created as a way to ease software development, allow programs
> developed for one board to be easily re-used on other boards, and
> provide a way to control boards from any language and operating system
> that supports TCP/IP.
>
> tsctl has a consistent client API accessible from shell script, Python,
> C, and the tsctl protocol itself. tsctl is object oriented, and
> currently defines classes for Bus, CAN, DIO, Pin, Time (timekeeping),
> TWI, and SPI hardware, with future classes based on new hardware and
> customer demand.
>
> tsctl runs as a single server instance on each board. Each platform has
> a tsctl binary compiled specifically for that platform, and
> configuration files are kept to a minimum. tsctl will run under
> fastboot or full Debian boot and has a minimum of extra library
> dependencies (currently pthreads, which is statically linked)
>
> tsctl implements the canctl, dioctl, and spictl protocols on top of
> these objects, replaces those binaries, and supports their command-line
> parameters when invoked as them (through a symlink to tsctl).
>
> Initial support is in development for the TS-4500 (and other Cavium
> based boards), TS-4200, TS-4700, and TS-4800 with future board support
> to cover newly developed boards and older boards by customer request.
>
> I welcome all feedback, suggestions, and other comments.
>
> ______ Best Regards,
> |__ __/ Michael Schmidt
> || Software Engineer
> ||echnologic Systems (EmbeddedARM.com)
> || (480) 16525 East Laser Drive
> |/ 837-5200 Fountain Hills, AZ 85268
> http://oz.embeddedarm.com/~michael
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|