Exact match. Not showing close matches.
PICList
Thread
'[PIC]: where we are going to?'
2003\02\16@181315
by
Igor Pokorny
|
> Does anyone know of any robots (non commercial)
> programmed with the salvo rtos? Especially ones with
> code?
Sorry, all the ones I know of were programmed without code.
> Either that or a great tutorial on using it?
Um, the obvious answer would be to ask the Salvo people.
You should also step back and ask yourself why you think you want an RTOS
on a PIC, and if so, what limited set of RTOS-like features you really
want. Despite the hype from Salvo and their habit of belittleing any code
that doesn't use an RTOS, it is still doubtful these are of any real
advantage on small processors like PICs. I haven't seen anything yet that
hasn't been handled quite nicely by a simple foreground event loop
architecture. The closest I've gotten to RTOS-like features is creating a
psuedo-thread for handling an input stream such as from a host via the
UART. If that's all you need, you can get it for free. See the
HOS_CMD.ASPIC module of the HOS PIC project at
http://www.embedinc.com/pic/hos.htm. That same project also has an
example of a simple event loop in the HOS_MAIN.ASPIC module.
Hello Olin,
I would like to notice only you are incredible patient answering question
like this one. Where your intern power is going from?
To be frank, I enjoy to use 18F series because I consider to do everything
during interrupt is more clear than to check flags in a main loop. Hope the
next version will have RTOS integrated in hardware as well as using FSR two
bytes long addressing any RAM, indexing RAM by W or any other byte etc....
Watching the development for 30 more years in this area I have to say, that
there is not anything new except the speed. Intel continues his wrong way
based on 8080 instruction repertoir, others starting by RISC get slowly to
very complicated systems...No one asks programmers what would be best ....
Regards
Igor
--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
2003\02\17@104227
by
Olin Lathrop
From: "Igor Pokorny" <spam_OUTigorpTakeThisOuT
APPLET.CZ>
> To be frank, I enjoy to use 18F series because I consider to do
everything
> during interrupt is more clear than to check flags in a main loop. Hope
the
> next version will have RTOS integrated in hardware
I certainly hope not! Above all, PICs are optimized for low cost. I
wouldn't want to see Microchip drive up the cost for something that would
be rarely used. There are plenty of larger processors to chose from if
you want a more general purpose computing environment.
> as well as using FSR two
> bytes long addressing any RAM,
Um, they have that. RTFM.
> indexing RAM by W or any other byte etc....
They have that too, at least from W. Indexing for another byte is only a
cycle away. You really do need to read the manual, especially before
complaining about the thing it describes.
> ...No one asks programmers what would be best ....
Actually they do. Programmers, compiler writers, hardware designers, etc.
I know this because I was one of those asked about the dsPIC architecture
a few years ago when it was in its early stages of design. Probably a few
other people on this list were too, and couldn't say anything either
because we all signed non-disclosure agreements.
*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com
--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics
More... (looser matching)
- Last day of these posts
- In 2003
, 2004 only
- Today
- New search...