Does linux care the PCI IRQ tables created by LinuxBios? I thought it only look at the MP-table.
gin
On Tue, 11 Jan 2005, Gin wrote:
Does linux care the PCI IRQ tables created by LinuxBios? I thought it only look at the MP-table.
if it is not SMP, Linux will use the irq table. It is a good idea to have a working irq table available.
ron
On Tue, 11 Jan 2005, Ronald G. Minnich wrote:
if it is not SMP, Linux will use the irq table. It is a good idea to have a working irq table available.
Oh yeah, warning to all Geode users: Linux has not properly parsed a Geode IRQ table since 2.4.18 ... it's a problem.
ron
Need some way to test if linuxbios is booting correctly. I am debugging and I have reason to believe that my problem is the super io... Does any one know how to get the pc speaker to beep in X second intervals, or some thing that simple, power LED blink... I would like to set up a "speaker beeper" as my payload.
I would also like to try to get the new VGA bios running... The graphics card is built on to the board, just to make life more of a pain. If any one is willing to give me a "How To" that would be of great help. Thx -Adam
I need to start looking at moving the 440bx stuff to V2. The part I'm most concerned about is re-writing the ram init code.
Is it possible to use the V2 structure but graft in the assembly output from V1? Then as time permits I can go back and re-write those routines.
Tell me again which is the reference board for V2 for a simple embedded case.
===== Richard A. Smith Bitworks, Inc.
__________________________________ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250
Richard Smith smithbone69@yahoo.com writes:
I need to start looking at moving the 440bx stuff to V2. The part I'm most concerned about is re-writing the ram init code.
Is it possible to use the V2 structure but graft in the assembly output from V1? Then as time permits I can go back and re-write those routines.
Yes. You will need to copy a few of the assembly helper routines as well, since I think we finally removed those from V2.
Tell me again which is the reference board for V2 for a simple embedded case.
Something like the via epia, q-emu should be ok. I don't really know as I have not looked at the simple embedded case lately. In the last round of cleanups I'm pretty certain we managed to purge the worst of the bad examples from the tree in the last round of cleanups.
Eric
--- "Eric W. Biederman" ebiederman@lnxi.com wrote:
Something like the via epia, q-emu should be ok. I don't really know as I have not looked at the simple embedded case lately. In the last round of cleanups I'm pretty certain we managed to purge the worst of the bad examples from the tree in the last round of cleanups.
Ok. I'll re-look at it. Last time I looked I seemed to remember getting lost pretty quick.
IIRC the q-emu wasn't really complete enough for my purposes. I'll start with epia and go from there.
===== Richard A. Smith Bitworks, Inc.
__________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250
On Wed, 12 Jan 2005, Richard Smith wrote:
IIRC the q-emu wasn't really complete enough for my purposes. I'll start with epia and go from there.
sorry, richard, I misunderstood your question. Yeah, try the epia.
ron
I don't understand the cpu naming scheme in the cpu/intel dirctory.
Our board uses a PIII Celeron in a PGA socket 370 @ 400 Mhz
should I just call the directory socket_PGA370 or do I need to add speed info? What about the Celeron, non-celeron difference?
===== Richard A. Smith Bitworks, Inc.
__________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo
Richard Smith smithbone69@yahoo.com writes:
I don't understand the cpu naming scheme in the cpu/intel dirctory.
Our board uses a PIII Celeron in a PGA socket 370 @ 400 Mhz
should I just call the directory socket_PGA370 or do I need to add speed info? What about the Celeron, non-celeron difference?
The idea is to filter the processors by which processors will fit into a socket. With recent Xeons Intel has reused the same socket with a different pin-out. The only name associated with the pin out change is the processor front side bus frequency. You can look up the appropriate Intel data sheets to figure out what is socket compatible with what else.
If we fully supported it we would have a lot of potential cpus and non-intel cpus that could plug into it. So we would need to include a bunch of directories.
Socket 370 is the first socket that Intel denied the clone manufacturers from using I believe. So the choice in cpus should be fairly small.
After that I break the functionality by the information returned by cpuid. If the processors are significantly different I have different directories for initializing them. If the processors are similar I have the same directory and look at the values cpuid returns for the changes.
The idea is to differentiate things how it makes sense from a code perspective, rather than how it makes sense from a vendor marketing perspective.
As I recall the only real difference with Celerons is their reduction in cache so we may get a fair amount of code sharing with other processors. I don't think the clock cycle changes at that point caused a different socket pin out to be used.
And of course a lot of functionality is buried in cpu/x86/.... for code that is independent of a given processor model.
It is not a huge leap forward from where we used to be but it is better, and the code has the very nice property that when we encounter a new model of cpu (which for Intel almost always requires a different microcode update) we have to explicitly allow it to boot. So the developers get a chance to verify the code is going to work with the new cpu model.
Eric
--- "Eric W. Biederman" ebiederman@lnxi.com wrote:
Socket 370 is the first socket that Intel denied the clone manufacturers from using I believe. So the choice in cpus should be fairly small.
There are not any pin changes for the various speeds of PIII. Well at least as far as 733Mhz. Our data sheet dosen't list any speeds higher than that.
Dooing some googleing I see that up to 1.3Ghz the 370 was still in use and looks like nothing changed. 1.4Ghz and up added the mPGA478. I found 1.4s in both footprints but anything faster though seems to be mPGA.
So I'm taking that to mean that socket_PGA370 is ok as my cpu directory?
===== Richard A. Smith Bitworks, Inc.
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Wed, 12 Jan 2005, Richard Smith wrote:
Is it possible to use the V2 structure but graft in the assembly output from V1? Then as time permits I can go back and re-write those routines.
bite the bullet. Just write the C. I've tried both ways and the C is just plain easier.
I would go for the advanced digital logic p3.
ron
--- "Ronald G. Minnich" rminnich@lanl.gov wrote:
bite the bullet. Just write the C. I've tried both ways and the C is just plain easier.
The problem with that is that it requires me to actually go _understand_ the code. *grin* I fixed a few bugs in the origial asm code but most of it remains unchanged and untouched. I don't claim to understand all the steps for proper SDRAM init.
I would go for the advanced digital logic p3.
Dose either this one or the epia read the SPD eproms and set the registers accordingly?
===== Richard A. Smith Bitworks, Inc.
__________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250
On Wed, 12 Jan 2005, Richard Smith wrote:
Dose either this one or the epia read the SPD eproms and set the registers accordingly?
you mean does the EPIA read the SPD? Yes it does, and somebody recently fixed a bunch of bugs so it does a better job that it used to.
ron
On Tue, 11 Jan 2005, Adam Talbot wrote:
Need some way to test if linuxbios is booting correctly. I am debugging and I have reason to believe that my problem is the super io... Does any one know how to get the pc speaker to beep in X second intervals, or some thing that simple, power LED blink... I would like to set up a "speaker beeper" as my payload.
you don't have a post card do you? that is always the 'gold standard' to debug.
I would also like to try to get the new VGA bios running... The graphics card is built on to the board, just to make life more of a pain. If any one is willing to give me a "How To" that would be of great help.
let's get you booting first.
ron
"Adam Talbot" talbotx@comcast.net writes:
Need some way to test if linuxbios is booting correctly. I am debugging and I have reason to believe that my problem is the super io... Does any one know how to get the pc speaker to beep in X second intervals, or some thing that simple, power LED blink... I would like to set up a "speaker beeper" as my payload.
I would also like to try to get the new VGA bios running... The graphics card is built on to the board, just to make life more of a pain. If any one is willing to give me a "How To" that would be of great help.
I would aim at the PC speaker if I could. Usually the PIT (programmable interval timer) which drives that speaker is on the south-bridge, so it should make a very good target for getting output if you are not certain about the super-IO. The keyboard LED is a lot more work, so I would not worry about that. And I would suggest that a payload is much later than you want that debugging to happen.
Unfortunately I don't believe we have an pc-speaker output coded for the LinuxBIOS case. I keep play with the idea of morse code console, using the pc-speaker :) You would not want full debugging on but it might be useful for your kind of scenario.
Eric
On Wed, 12 Jan 2005, Eric W. Biederman wrote:
Unfortunately I don't believe we have an pc-speaker output coded for the LinuxBIOS case. I keep play with the idea of morse code console, using the pc-speaker :) You would not want full debugging on but it might be useful for your kind of scenario.
now that's a cool idea, Eric, I didn't know you knew morse code!
How about for the failure case: ... --- ...
ron
"Ronald G. Minnich" rminnich@lanl.gov writes:
On Wed, 12 Jan 2005, Eric W. Biederman wrote:
Unfortunately I don't believe we have an pc-speaker output coded for the LinuxBIOS case. I keep play with the idea of morse code console, using the pc-speaker :) You would not want full debugging on but it might be useful for your kind of scenario.
now that's a cool idea, Eric, I didn't know you knew morse code!
Not very well. The idea originally came from Alan Cox with respect to the kernel. I have simply been mulling it over for a while. With the realization a couple of days ago that the PIT is easily accessible makes it that much more attractive.
I think morse code would actually tie in better with the post code infrastructure than general console traffic. That would keep the volume of data low enough so as to be meaningful. Even if you did not know morse code.
How about for the failure case: ... --- ...
:)
Except that usually the failure case does not print a message.
But a boot sequence that when like ----- .---- ..--- ...-- ....- ..... -..... --... ---.. But never got to ----.
Could be pretty telling.
Eric
Eric W. Biederman wrote:
I think morse code would actually tie in better with the post code infrastructure than general console traffic. That would keep the volume of data low enough so as to be meaningful. Even if you did not know morse code.
Then maybe you could use one of these instead of a POST card: http://www.universal-radio.com/catalog/morse/2070.html
:) -Bari
A morse code decoder for decoding "Audio console". Wow, our geek is hanging out! :-) if some one have that much spair time... But for now, one or two simple beeps would make me VERY happy. As far a POST card, I do not have one... Yet. What POST card have your guys had good luck with (PCI)? -Adam
----- Original Message ----- From: "Bari Ari" bari@onelabs.com To: "Eric W. Biederman" ebiederman@lnxi.com Cc: "Ronald G. Minnich" rminnich@lanl.gov; "Adam Talbot" talbotx@comcast.net; Linuxbios@clustermatic.org Sent: Wednesday, January 12, 2005 10:43 AM Subject: Re: speaker beeper
Eric W. Biederman wrote:
I think morse code would actually tie in better with the post code infrastructure than general console traffic. That would keep the volume of data low enough so as to be meaningful. Even if you did not know morse code.
Then maybe you could use one of these instead of a POST card: http://www.universal-radio.com/catalog/morse/2070.html
:) -Bari
On Wed, 12 Jan 2005, Adam Talbot wrote:
As far a POST card, I do not have one... Yet. What POST card have your guys had good luck with (PCI)?
For 5V PCI bus the company I used to buy from no longer sells it, oops (I just checked)
anybody?
ron
Check put this post card. What do you think. http://www.compgeeks.com/details.asp?invtid=SY-TECHAID http://www.soyogroup.com/dl/manuals/peripherals/techaid_manual_v10.pdf -Adam ----- Original Message ----- From: "Ronald G. Minnich" rminnich@lanl.gov To: "Adam Talbot" talbotx@comcast.net Cc: "Bari Ari" bari@onelabs.com; Linuxbios@clustermatic.org Sent: Wednesday, January 12, 2005 12:16 PM Subject: Re: speaker beeper
On Wed, 12 Jan 2005, Adam Talbot wrote:
As far a POST card, I do not have one... Yet. What POST card have your
guys
had good luck with (PCI)?
For 5V PCI bus the company I used to buy from no longer sells it, oops (I just checked)
anybody?
ron
Adam Talbot wrote:
Check put this post card. What do you think. http://www.compgeeks.com/details.asp?invtid=SY-TECHAID http://www.soyogroup.com/dl/manuals/peripherals/techaid_manual_v10.pdf -Adam
For only $28.75 it looks great.
-Bari
"Adam Talbot" talbotx@comcast.net writes:
A morse code decoder for decoding "Audio console". Wow, our geek is hanging out! :-) if some one have that much spair time... But for now, one or two simple beeps would make me VERY happy. As far a POST card, I do not have one... Yet. What POST card have your guys had good luck with (PCI)?
I keep having problems with not having a 5V 32bit PCI slot or an ISA slot... But in any case the llshell.inc should do the trick just include it and call it very early on. And the first thing it does when called is beep.
From romcc the calling convention would look something like:
asm( "movl $1f, %esp\n\t" "jmp low_level_shell\n\t" "1:\n\t" );
Of course you won't come back unless you have your serial console working...
Eric
-Eric Console... Well "running" is a big word :-). I get garbage to the screen, so I no that "some" of Linux bios is loading. I know that the console connection is good, added console support to GRUB, that works great. Currently I am looking over freebios2/src/northbridge/intel/i855pm/raminit.c. Found that the CAS is hard set to 2.0 !@#$ that will kill my board REAL quick like, my ram is 2.5 CAS, fixing that, and hoping that will fix my garbage out put problem. I would like to add beep code's to different parts of my boot. So 3 beeps means that RAM failed to load, 2 the Northbridge failed, and so on. Just a good debug to get my console up and running. I am very happy to see the code for the speaker, but that code is way beyond my skills of C. I need to be able to just copy and paste the speaker code, or a function calling the speaker and put that into key parts of the code. I have no clue if this is easy or hard to do. I will keep you up to date if the raminit.c fix cleans up my console. -Adam
----- Original Message ----- From: "Eric W. Biederman" ebiederman@lnxi.com To: "Adam Talbot" talbotx@comcast.net Cc: "Bari Ari" bari@onelabs.com; Linuxbios@clustermatic.org Sent: Wednesday, January 12, 2005 8:11 PM Subject: Re: speaker beeper
"Adam Talbot" talbotx@comcast.net writes:
A morse code decoder for decoding "Audio console". Wow, our geek is hanging out! :-) if some one have that much spair time... But for now,
one
or two simple beeps would make me VERY happy. As far a POST card, I do not have one... Yet. What POST card have your
guys
had good luck with (PCI)?
I keep having problems with not having a 5V 32bit PCI slot or an ISA
slot...
But in any case the llshell.inc should do the trick just include it and call it very early on. And the first thing it does when called is beep.
From romcc the calling convention would look something like: asm( "movl $1f, %esp\n\t" "jmp low_level_shell\n\t" "1:\n\t" );
Of course you won't come back unless you have your serial console
working...
Eric
On Wed, 12 Jan 2005, Adam Talbot wrote:
Console... Well "running" is a big word :-). I get garbage to the screen, so I no that "some" of Linux bios is loading. I know that the console connection is good, added console support to GRUB, that works great.
you want to send your output to me again? Also, to the'screen' do you mean vga or serial?
ron
-Ron Sorry about that, have not even looked at vga; yes, screen=console. As far as the output i see in minicom... ".. ....... .. .. TÜ .¿.Ü.ü. . .. . .. ... Tü. .. .. . . ...û. . . .. .. .. ." Hope that means something to you. Thank you -Adam Talbot
----- Original Message ----- From: "Ronald G. Minnich" rminnich@lanl.gov To: "Adam Talbot" talbotx@comcast.net Cc: "Eric W. Biederman" ebiederman@lnxi.com; Linuxbios@clustermatic.org Sent: Thursday, January 13, 2005 7:01 AM Subject: Re: speaker beeper
On Wed, 12 Jan 2005, Adam Talbot wrote:
Console... Well "running" is a big word :-). I get garbage to the
screen,
so I no that "some" of Linux bios is loading. I know that the console connection is good, added console support to GRUB, that works great.
you want to send your output to me again? Also, to the'screen' do you mean vga or serial?
ron
On Thu, 13 Jan 2005, Adam Talbot wrote:
As far as the output i see in minicom... ".. ....... .. .. TÜ .¿.Ü.ü. . .. . .. ... Tü. .. .. . . ...û. . . .. .. .. ."
yeah, it means your baud rate is wrong or there is some other problem with your serial port setup.
You have to fix this before you do anything else.
ron
* Adam Talbot talbotx@comcast.net [050113 17:32]:
-Ron Sorry about that, have not even looked at vga; yes, screen=console. As far as the output i see in minicom... ".. ....... .. .. TÜ .¿.Ü.ü. . .. . .. ... Tü. .. .. . . ...û. . . .. .. .. ." Hope that means something to you.
Have you tried setting it to half or double baud rate?
Stefan
-Stefan Can i set my baud rate in the config, or do i need to go change it in the code? -Adam ----- Original Message ----- From: "Stefan Reinauer" stepan@openbios.org To: "Adam Talbot" talbotx@comcast.net Cc: "Ronald G. Minnich" rminnich@lanl.gov; Linuxbios@clustermatic.org Sent: Thursday, January 13, 2005 10:42 AM Subject: Re: speaker beeper
- Adam Talbot talbotx@comcast.net [050113 17:32]:
-Ron Sorry about that, have not even looked at vga; yes, screen=console. As far as the output i see in minicom... ".. ....... .. .. TÜ .¿.Ü.ü. . .. . .. ... Tü. .. .. . . ...û. . .
..
.. .. ." Hope that means something to you.
Have you tried setting it to half or double baud rate?
Stefan
* Adam Talbot talbotx@comcast.net [050113 20:39]:
-Stefan Can i set my baud rate in the config, or do i need to go change it in the code?
You should be able to set it in the config ## Select the serial console baud rate default TTYS0_BAUD=115200 #default TTYS0_BAUD=57600 #default TTYS0_BAUD=38400 #default TTYS0_BAUD=19200 #default TTYS0_BAUD=9600 #default TTYS0_BAUD=4800 #default TTYS0_BAUD=2400 #default TTYS0_BAUD=1200
but I actually meant playing with your terminal program. A very common problem is that some i2c programming is missing and that makes the serial console come out with 57600 instead of the configured 115200 baud..
Stefan
-Stefan I had to add in the Options.ld used TTYS0_BAUD. I when with default TTYS0_BAUD=9600 as I have had allot of luck with that speed.
.r2öTü.b.3.Z..¬ö.4..W.öut¶t.6.T4.4u.....4wWIóu.î¼7UT 1¶.ts1.Q..N4u«W.QQÑ.¢QQQIRQQyQYÑ
Any other ideas of what to look at? Tried both hardware and softwareware flow control, I have defaulted back to no flow control. -Adam
----- Original Message ----- From: "Stefan Reinauer" stepan@openbios.org To: "Adam Talbot" talbotx@comcast.net Cc: Linuxbios@clustermatic.org Sent: Thursday, January 13, 2005 11:45 AM Subject: Re: speaker beeper
- Adam Talbot talbotx@comcast.net [050113 20:39]:
-Stefan Can i set my baud rate in the config, or do i need to go change it in
the
code?
You should be able to set it in the config ## Select the serial console baud rate default TTYS0_BAUD=115200 #default TTYS0_BAUD=57600 #default TTYS0_BAUD=38400 #default TTYS0_BAUD=19200 #default TTYS0_BAUD=9600 #default TTYS0_BAUD=4800 #default TTYS0_BAUD=2400 #default TTYS0_BAUD=1200
but I actually meant playing with your terminal program. A very common problem is that some i2c programming is missing and that makes the serial console come out with 57600 instead of the configured 115200 baud..
Stefan
On Thu, 13 Jan 2005, Adam Talbot wrote:
-Stefan Can i set my baud rate in the config, or do i need to go change it in the code?
change it in minicom first. Try setting minicom up and down 2x and 1/2x and see if you get real characters.
ron
On Wed, Jan 12, 2005 at 09:11:32PM -0700, Eric W. Biederman wrote:
I keep having problems with not having a 5V 32bit PCI slot or an ISA slot...
What are good features for a POST card besides being a Universal board? (dual voltage) I will probably be designing one for a customer later this spring, and while they have a few feature demands I think this list can offer good ideas as well. :)
I've seen memory on POST cards, giving scrollback of the last 32 seen codes, but I'm not sure how useful that is..
//Peter
On Thu, 13 Jan 2005, Peter Stuge wrote:
What are good features for a POST card besides being a Universal board? (dual voltage)
you have to make sure that it won't keep a machine from turning on. I have 5V post cards that when put in some mainboards won't allow them to power up.
I've seen memory on POST cards, giving scrollback of the last 32 seen codes, but I'm not sure how useful that is..
very useful to me anyway.
ron
actually, a very handy thing would be a post card with a serial port ...
ron
Ronald G. Minnich wrote:
actually, a very handy thing would be a post card with a serial port ...
With a serial port for output?
-Bari
On Thu, Jan 13, 2005 at 08:07:00AM -0700, Ronald G. Minnich wrote:
On Thu, 13 Jan 2005, Peter Stuge wrote:
What are good features for a POST card besides being a Universal board? (dual voltage)
you have to make sure that it won't keep a machine from turning on. I have 5V post cards that when put in some mainboards won't allow them to power up.
Ouch! Does anyone know what the problem is?
Also, do you recall which models any of those mainboards were?
I've seen memory on POST cards, giving scrollback of the last 32 seen codes, but I'm not sure how useful that is..
very useful to me anyway.
Right, for bringing up a board/BIOS I agree it's useful. :) I just thought about the hw store I'm making it for, they only need them for their tech people handling returns.
I figure why not add a few neat features to it as well, since they were considering making large batches and offering them for sale to anyone else.
On Thu, Jan 13, 2005 at 08:07:15AM -0700, Ronald G. Minnich wrote:
actually, a very handy thing would be a post card with a serial port ...
That's a good idea!
On Thu, Jan 13, 2005 at 09:55:41AM -0700, Ronald G. Minnich wrote:
On Thu, 13 Jan 2005, Bari Ari wrote:
With a serial port for output?
yeah. A BASIC Stamp ought to be able to do the deed.
I'll probably just put a PIC there for the serial port and any other peripheral stuff.
Thanks for the ideas!
//Peter
On Fri, 14 Jan 2005, Peter Stuge wrote:
Ouch! Does anyone know what the problem is?
No
Also, do you recall which models any of those mainboards were?
every model I've had with a 3V pci bus.
I figure why not add a few neat features to it as well, since they were considering making large batches and offering them for sale to anyone else.
I still think a POST card with a Basic Stamp on it might be the best bet.
ron
On Fri, Jan 14, 2005 at 09:53:15AM -0700, Ronald G. Minnich wrote:
On Fri, 14 Jan 2005, Peter Stuge wrote:
Ouch! Does anyone know what the problem is?
No
Also, do you recall which models any of those mainboards were?
every model I've had with a 3V pci bus.
Aha, a 5V PCI card will likely cause problems if plugged into a 3V bus, although that's not supposed to be possible thanks to the differently keyed connectors. Of course a bad POST card can key as a Universal board even if it only runs off 5V, but that's not all there is to it. To be at least a little future proof (who knows how long PCI will live) I fully intend to make it a real Universal board that works equally well in 5V and 3V systems, without any configuration required. This is possible within the PCI specification.
I still think a POST card with a Basic Stamp on it might be the best bet.
Any particular reason to specifically choose a BASIC Stamp rather than e.g. a PIC?
Has all email to/from the list been coming through correctly the last 12 hours? I'm not sure if I got some duplicates and delayed messages?
//Peter
On Fri, 2005-01-14 at 10:56, Peter Stuge wrote:
I still think a POST card with a Basic Stamp on it might be the best bet.
Any particular reason to specifically choose a BASIC Stamp rather than e.g. a PIC?
What is BASIC Stamp and what is PIC ?
Ollie
Has all email to/from the list been coming through correctly the last 12 hours? I'm not sure if I got some duplicates and delayed messages?
//Peter
On Fri, 14 Jan 2005, Li-Ta Lo wrote:
What is BASIC Stamp and what is PIC ?
very nice small devices that are a full CPU with I/Os, and in the case of basic stamp, a basic interpreter built in.
Basic Stamp is popular for many home robotics apps.
ron
On Fri, Jan 14, 2005 at 11:08:04AM -0700, Ronald G. Minnich wrote:
On Fri, 14 Jan 2005, Li-Ta Lo wrote:
What is BASIC Stamp and what is PIC ?
very nice small devices that are a full CPU with I/Os, and in the case of basic stamp, a basic interpreter built in.
Specifically the PIC devices are the "PICmicro Microcontroller" products from Microchip, not to be confused with the AMD PIC mentioned in another thread. One of the newer PICmicro devices that I like in the smallest-but-still-quite-useful range is the PIC16F688; http://microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1335&...
35 instructions, couple of thousand instructions program memory, 5 MIPS, 256 bytes RAM, 256 bytes EEPROM, up to 12 IO pins multiplexed with serial TX/RX and interrupt pin, timers, internal tuned 8MHz oscillator, low power modes, etc. etc.
They come in lots of shapes and sizes but the entire 16F family is the same core architecture, if you know one you pretty much know them all. They also have the 18F family, which is optimized for C compilers. I tend to only do assembler on the 16F's.
Fun to toy with and easy to use. :) Program (burner can be built for just a few $) it, connect a power source, and away it goes.
//Peter
On Fri, 14 Jan 2005, Peter Stuge wrote:
On Fri, Jan 14, 2005 at 09:53:15AM -0700, Ronald G. Minnich wrote:
On Fri, 14 Jan 2005, Peter Stuge wrote:
Ouch! Does anyone know what the problem is?
No
Also, do you recall which models any of those mainboards were?
every model I've had with a 3V pci bus.
Aha, a 5V PCI card will likely cause problems if plugged into a 3V bus, although that's not supposed to be possible thanks to the differently keyed connectors.
yeah, but even a plan ol' pci 32 bits slot @ 33 mhz on the supermicro boards we have won't tolerate a post card. I haven't look enough to know what's up here. Serial POST was my fix -- I like that better anyway.
To be at least a little future proof (who knows how long PCI will live) I fully intend to make it a real Universal board that works equally well in 5V and 3V systems, without any configuration required. This is possible within the PCI specification.
good plan.
Any particular reason to specifically choose a BASIC Stamp rather than e.g. a PIC?
PIC is fine. Something you can program would be cool
Has all email to/from the list been coming through correctly the last 12 hours? I'm not sure if I got some duplicates and delayed messages?
things seem ok here.
ron
* Bari Ari bari@onelabs.com [050112 19:43]:
Eric W. Biederman wrote:
I think morse code would actually tie in better with the post code infrastructure than general console traffic. That would keep the volume of data low enough so as to be meaningful. Even if you did not know morse code.
Then maybe you could use one of these instead of a POST card: http://www.universal-radio.com/catalog/morse/2070.html
If you don't want an extra device these might work as well, they capture morse code with a sound card:
http://he.fi/archive/linux-hams/200407/0035.html http://bellota.ele.uva.es/~jesus/rtty/
The windows programmers usually take a pretium doloris for their code: http://www.dxsoft.com/en/products/cwget/ http://www.polar-electric.com/Morse/MRP40-EN/index.html
Stefan
this has got to be the most amusing thread I have read in a while.
For the key, on the morse console, do I need special hardware, or can I just use a mouse button?
On 12 Jan 2005 11:19:01 -0700, Eric W. Biederman ebiederman@lnxi.com wrote:
"Ronald G. Minnich" rminnich@lanl.gov writes:
On Wed, 12 Jan 2005, Eric W. Biederman wrote: I keep play with the idea of morse code console, using
the pc-speaker :)
On Mon, 14 Feb 2005, David Nicol wrote:
For the key, on the morse console, do I need special hardware, or can I just use a mouse button?
sure, if you don't mind frying your tendon ... you can use up one finger at a time :-)
ron
If you compilie in llshell, it will beep the speaker whenever called (this can be at any stage). Also, type beep at the command prompt, assuming you have serial.
(2nd try, apologies if you get this twice)
-
Adam Talbot -
Bari Ari -
Bryan E. Chafy -
David Nicol -
ebiederman＠lnxi.com -
Gin -
Li-Ta Lo -
Peter Stuge -
Richard Smith -
Ronald G. Minnich -
Stefan Reinauer