DIY_EFI Digest Wednesday, August 18 1999 Volume 04 : Number 476 In this issue: Re: DIY_EFI Digest V4 #475 Re: DIY_EFI Digest V4 #475 Re: DIY_EFI Digest V4 #474 Re: real time OS See the end of the digest for information on subscribing to the DIY_EFI or DIY_EFI-Digest mailing lists. ---------------------------------------------------------------------- Date: Wed, 18 Aug 1999 09:28:09 +0600 From: Kihurani Gakuu Subject: Re: DIY_EFI Digest V4 #475 >Date: Tue, 17 Aug 1999 14:50:24 -0700 (MST) >From: d houlton x0710 >Subject: MCU recomendation? > >Can someone who knows a bit more than I do about MCUs reccomend one and a >development board to use? > >I'm new to this and I'm finding it near impossible to decide what chip/board >I should be looking at. I'm learning as I go, but I don't even know enough >where to start. > >I definitely want one that I can get a C compiler for. I think the Hitachi >might be good as their dev. kits come with one (or two). Cost of course is >an issue. The Hitachi boards start around $150 complete with C compiler, >power supply, board, etc.. I figure I can afford up to $250. Maybe $300 >if there's a strong case for that particular set-up. Check out this site: http://rigelcorp.com/home.htm. You can get an evaluation board for the SIEMENS C-166 for less than $150(US). It comes with an evaluation copy of RIGEL's proprietary C Compiler, READS166. The full version of the compiler costs $300, but memory is limited to 64k. Find out if this is what you need to get started. Kih ------------------------------ Date: Wed, 18 Aug 1999 09:18:39 -0400 From: "Gary Derian" Subject: Re: DIY_EFI Digest V4 #475 How about this? http://el.www.media.mit.edu/projects/handy-board There are others, also. Gary Derian > Subject: MCU recomendation? > > Can someone who knows a bit more than I do about MCUs reccomend one and a > development board to use? > > I'm new to this and I'm finding it near impossible to decide what chip/board > I should be looking at. I'm learning as I go, but I don't even know enough > where to start. ------------------------------ Date: Wed, 18 Aug 1999 12:17:46 EDT From: Fisystems@xxx.com Subject: Re: DIY_EFI Digest V4 #474 In a message dated 8/17/99 12:23:00 PM Pacific Daylight Time, DIY_EFI-Digest-Owner@xxx.edu writes: << V4 >> Looking for bin file (1993,94) Vette LT1. Thanks Ken Murillo fisystems@xxx.com ------------------------------ Date: Wed, 18 Aug 1999 11:46:43 PDT From: "Douglas Wright" Subject: Re: real time OS > >No chance. Windows cannot do this. Linux probably can if you are >comfortable with programming for real time applications, but you would >probably be safest with a genuine real-time OS, which of course is a very >specialized skill and probably expensive for the software. > >You kind of reach a point of diminishing returns with PC hardware. The >CPUs today are designed for computationally intensive applications which >engine management is certainly not. Your real bottleneck is the I/O, >most PC systems are very poor at this and it's the most important part of >engine management. > Hello, We have designed BeOS to be able to handle digital audio processing with very low latency. We can have audio buffers as small as 1.3 msec without experiencing any dropouts or glitches. And an incoming midi note can get from the port to a user appliction in under 100 microsecs. As you said, PC hardware can do this, but some OSes can't. We have fully multi-threaded environment, but with a twist. Threads with priorities from 1-99 are on a round robin schedule with threads with a higher priority getting to run more often. Threads with priority 100-120 are "real-time" threads. They get to run as long as they want AND there isn't a higher priority thread running. I would be happy to help anyone that would like to try using BeOS for doing FI management. I would do it myself, but I've got plenty of work to do already;-) thanks, dug Audio Software Engineer Be, Inc. http://www.be.com ------------------------------ End of DIY_EFI Digest V4 #476 ***************************** To subscribe to DIY_EFI-Digest, send the command: subscribe diy_efi-digest in the body of a message to "Majordomo@xxx. A non-digest (direct mail) version of this list is also available; to subscribe to that instead, replace "diy_efi-digest" in the command above with "diy_efi".