|
|
| |
Patch 10: This works for me under Cygwin with a USB tower, but some of the
files such as rcx_comm.c have a bit of platform-specific code.
Patch 11: I've noticed that the linker command file is a little different in
Bibo than it was in BrickOS. If _motor_controller is 0x00 in bibo.ld and
dm_mask is set to 0x00 in dmotor.c dm_init(), there is "regular" motor
output; if _motor_controller is the BrickOS value of 0x80, DCC motor output
functions as expected.
|
|
| |
> Revised version [BrickOS patches] at
> http://sourceforge.net/tracker/?func=detail&aid=2722649&group_id=58151&atid=486699
> Now for Bibo.... I have merged these patch rollup collections with Bibo
> (where appropriate) and have posted the resulting diff files to
> http://sourceforge.net/tracker/?func=detail&aid=2773502&group_id=58151&atid=486699
I have found two problems with the patches. I narrowed down the problems to
specific patches from the Bibo set. However the symptoms are identical under
BrickOS so I assume they would be linked to the same patches there.
Patch 10: Under Ubuntu with the usb tower, this causes firmdl3 to exit with
error "read: resource temporarily available". However the light does light up on
the tower for a small moment.
Patch 11: This seems to do something funny with the motors. Power does not seem
to be supplied to the motors. when running the motor, the arrows appear on the
lcd however there is no power being outputted.
|
|
| |
> A very useful site is the cs university page here:
> http://www.cs.brown.edu/courses/cs148/old/2004fall/brickos.shtml
Agreed. There is also a set of pages from the following school year at
http://cs.brown.edu/courses/csci1480/old/2005/brickOS/quickstart.html .
Unfortunately (at least from a code merge perspective), their "version 1.2"
is based on BrickOS 0.2.5. The lnp_printf functionality has been adapted
and included in the recently-posted rollup patches, but incorporating other
modifications, such as "Reliable LNP," is more involved due to the
difference in BrickOS versions.
> A page of patches: http://carl.troein.com/
[@Carl]: Please correct me if I'm wrong, but I believe these patches are
already included in the rollup posted to SourceForge?
If the SourceForge project wiki for BrickOS could be enabled....
I've noticed another thing that is disappearing is the custom sensors and
multiplexor boards that were created for the RCX....
Thanks,
Matthew
|
|
| |
Now for Bibo.... I have merged these patch rollup collections with Bibo
(where appropriate) and have posted the resulting diff files to
http://sourceforge.net/tracker/?func=detail&aid=2773502&group_id=58151&atid=486699
Most of this follows the pattern of the previous patch rollup collection for
BrickOS, with the following notes:
* 00 - Update configuration and make slight makefile modifications to work
with Cygwin
* 10 - As Carl noted, there are similarities between rcxtty.c and
rcx_comm.c. I updated this patch to add code to rcx_comm.c that previously
was only in rcxtty.c. There are still some differences (such as in return
types, use of exit(), and FileDescriptor handling), but this should reduce
the gap.
* 13 - I originally added LegOShrink as lnp_shrink (due to the OS naming
issue) but have added it here as lnpmsg.
* 16 - [@Carl]: I have not included the edgecount patch. Most of the
edgecount code appeared to be fairly straightfoward to incorporate into
Bibo; however, the assembly code in ds_interrupt in dsensor.c is a little
different, which could impact the edgecount patch. If you have the time to
take a look at it, that would be great, as it would be nice to have it
included.
Thanks,
Matthew
|
|
| |
> A list of all the current versions and patches, along with links and
> perhaps backups would be very useful.
Nice to see a few of us share the interest. :-) The best I can offer for a
list of patches is what I listed in the post here [
http://news.lugnet.com/robotics/rcx/legos/?n=4032&t=i&v=a ], along with
Carl's follow-up post. That list was culled from links I've collected over
the years. As was noted, there are different patches out there for
different versions of BrickOS, and those two posts are an effort to merge
together appropriate patches against the latest SourceForge version of
BrickOS. From Carl's post, the link to download the latest version of this
collection of patches is
http://sourceforge.net/tracker/?func=detail&aid=2722649&group_id=58151&atid=486699 .
The patches are numbered and are intended to be applied in numerical order.
As was also noted, patches yet to be merged deal with "reliable LNP," task
prioritization, task scheduling, memory allocation, real-time sensors, etc.
To the tools versions--
* binutils: 2.16.1 - h8300 COFF support was dropped from subsequent
releases, so unless BrickOS is updated to h8300 ELF, we will have to stick
with this version
* gcc: 3.4.6 - this is the version that I use; I think Carl has had some
success with some releases in the version 4 series
Dr. Jochen Hoenicke's Bibo is also worth considering as a "next version" of
BrickOS. I have started going through that list of patches to carry over
any relevant changes to Bibo. If I can get them ported over to Bibo, I
expect I will base any of my future "legOS" development on Bibo.
For some 404 pages, http://www.archive.org/ might be your friend; no
guarantees, though.
Hope this helps,
Matthew
|
|
| |
After surfing through many sites, and (sadly) even more 404s I have been
unable to find a definitive list of gcc, binutils, BrickOS etc. versions and
patches that I should and could be using.
Presumably everybody here has up to date versions of all the necessary programs
working with BrickOS.
What would be very useful would be to have a solid list of patches, version
numbers, problems as of now.
I spotted the patch list on the first post of "BrickOS Patches and Development"
and found it very handy.
The main problem in getting everything together is that every site I visit seems
to have been left unattended for many years, and are all recommending old and
outdated versions of compilers and patches.
A list of all the current versions and patches, along with links and perhaps
backups would be very useful.
|
|
| |
Hi all
Lately I've noticed a lot of old-school Lego Mindstorm resources are
starting to disappear from teh webz. I've blagged about wanting to
preserve this stuff here: http://rubyredbricks.com/2009/4/12/back-to-
the-brick
If anyone knows of any resources you think should be maintained
please let me know. I'm going to do my utmost to make sure stuff
doesn't just "blow away". TIA
Cheers
Tom
|
|
| |
Hi,
> > 1 - 5. Dr. Hoenicke's patches (
> > http://hoenicke.ath.cx/rcx/brickOS.html ),
> > including gcc33, highmem, performance, Makefile, and tcpcomm
> The second, "experimental" version of the performance patch (which adds
> CONF_DSENSOR_FAST) also works well with the following patches.
I had worked to assimilate those patches prior to the second version of the
performance patch being posted, so I'm glad to hear that it also works well.
> > That reminds me that there's some fairly trivial code duplication between
> > dll and firmdl. It's not very important, but I'll try to do something
> > about it soon.
When I went back through to add TCP support to other things, that "similar
but different code" made things a little more difficult. There are more
things that could use the addition of TCP support, including xsLisp. I
think a nice enhancement to the TCP ir-server would be to give it the same
"--tty" interface options as dll and firmdl--i.e., directly with a serial
tower, USB tower, or another TCP ir-server. This, for example, would enable
a "real" brick and a BrickEmu instance to communicate with each other.
Anyway, the short of it is that, yes, I think a merged communication library
would be very useful.
By the way, I don't know if you monitor the NQC newsgroup, but I submitted a
patch to add TCP support to NQC....
- RE: BrickOS and Bibo
Personally, my feeling is that Bibo improves upon BrickOS and will provide a
better foundation moving forward, and I say that as one who has spent some
time incorporating a number of patches into the latest BrickOS. I'm not
sure yet how much effort will be involved in working back through them to
apply them to Bibo (I'm thinking in particular of patches 7 - 16), but I
think it would ultimately be worth the effort. Of course, a few of the
patches to BrickOS may not even be relevant in Bibo, but I would at least be
interested in having the LDCC, LNP printf, and LNP communication utility
functionality in Bibo.
Thanks,
Matthew
|
|
|
