writing a dailer in c for a 8051 based system

[Sohail]

Hi all,
i am now to group this might be out of topic, if it is then please
tell me where i should ask this question...

At the time i am working on a project based on 8051, The project is so
get data from a system attached to telephone line, my system should
call the PC connected to phone line and retrive a file, and
disconnect. i can get a file from one Pc to an other PC via a
ftp-socket connection. That portion is finished but i am now i
trouble of making a call, i dont know what the dailers work. Please if
some one knows where i can get the information i will be greatful. i
have googled but all i find is how to get rid of dailers that get
installed by visiting a page or some thing like that.

any information will be helpfull,
thanks in advance
Sohail

 

[Malcolm]

i am now to group this might be out of topic, if it is then please
tell me where i should ask this question...

We only deal with C language issues here (clc), and ANSI C doesn't have any
support for networking, modems, or similar peripherals.

At the time i am working on a project based on 8051, The project > is so

get data from a system attached to telephone line,What's an 8051? Is there an ng devoted to it?

 

[Jack Klein]

Hi all,
i am now to group this might be out of topic, if it is then please
tell me where i should ask this question...

This is most certainly off-topic in both of the newsgroups you posted
it to. Do you actually think that there is a version of UNIX that
runs on an 8051 microcontroller?

At the time i am working on a project based on 8051, The project is so
get data from a system attached to telephone line, my system should
call the PC connected to phone line and retrive a file, and
disconnect. i can get a file from one Pc to an other PC via a
ftp-socket connection. That portion is finished but i am now i
trouble of making a call, i dont know what the dailers work. Please if
some one knows where i can get the information i will be greatful. i
have googled but all i find is how to get rid of dailers that get
installed by visiting a page or some thing like that.

any information will be helpfull,
thanks in advance
Sohail

The newsgroup that you want is

 

[Neil Kurzman]

Hi all,
i am now to group this might be out of topic, if it is then please
tell me where i should ask this question...

At the time i am working on a project based on 8051, The project is so
get data from a system attached to telephone line, my system should
call the PC connected to phone line and retrive a file, and
disconnect. i can get a file from one Pc to an other PC via a
ftp-socket connection. That portion is finished but i am now i
trouble of making a call, i dont know what the dailers work. Please if
some one knows where i can get the information i will be greatful. i
have googled but all i find is how to get rid of dailers that get
installed by visiting a page or some thing like that.

any information will be helpfull,
thanks in advance
Sohail

Of course there is C for the 8051 (8 bit micro)
try
comp.arch.embedded
www.keil.com
www.8052.com
Your request is unclear. are you going to use a modem. write the code to
be a modem?
fitting FTP can be done, but it is big.

Good luck

 

[August Derleth]

What's an 8051? Is there an ng devoted to it?

It's a microcontroller[1] made by Intel. It is (or was) widely used in
things like keyboards and modems and microwaves and so on and so forth.

The best place to discuss 8051-related stuff is probably
comp.arch.embedded.

[1]A microchip designed to be used in an environment other than a PC,
server, router, or other obviously-computer environment. They typically
have a place to hardcode instructions (that is, onboard ROM space) and
might support odd word sizes to interface with specialty hardware. Low
power consumption and extremely low cost-per-chip often counts for more
than clock speed.

 

[Dan Pop]

What's an 8051? Is there an ng devoted to it?

It's a microcontroller[1] made by Intel. It is (or was) widely used in
things like keyboards and modems and microwaves and so on and so forth.

The best place to discuss 8051-related stuff is probably
comp.arch.embedded.

[1]A microchip designed to be used in an environment other than a PC,
server, router, or other obviously-computer environment.

Many older hard disks found in PC's used an 8051 chip, so your definition
is rather shaky. Furthermore, Intel had an 8052 chip with an embedded
BASIC interpreter, that could be used as the core of a small computer.

They typically
have a place to hardcode instructions (that is, onboard ROM space) and
might support odd word sizes to interface with specialty hardware.

This is not the case of the general purpose ones, like the 8051, which
are best described as single chip computers, containing a CPU, ROM, RAM
and various external interfaces on a single chip. The word sizes are
the vanilla ones, so that adding external ROM or RAM can be done using
cheap, off the shelf, components (no point in having a cheap
microcontroller if it needs expensive external chips).

Low
power consumption and extremely low cost-per-chip often counts for more
than clock speed.

Low power consumption is often not an issue (no point in using a < 1 mW
controller in a microwave oven) but low cost per chip is an overriding
concern, otherwise the designer would opt for a traditional microprocessor
+ ROM + RAM + I/O intefaces approach, which is often more comfortable to
program on (the typical CPU in a microcontroller is less capable than an
usual microprocessor, the program and the data often reside in different
address spaces, and, for machine code compactness reasons, the program
memory is often paged).

Dan

 

[David Schwartz]

In <[email protected]> August Derleth <[email protected]>
writes:

[1]A microchip designed to be used in an environment other than a PC,
server, router, or other obviously-computer environment.

Many older hard disks found in PC's used an 8051 chip, so your definition
is rather shaky. Furthermore, Intel had an 8052 chip with an embedded
BASIC interpreter, that could be used as the core of a small computer.

He's saying it's "*designed* to be used in an environment other than a
PC". The 8051 was designed to be embedded in a wide variety of devices, and
not primarily as the central processor of a general-purpose computer.

This is not the case of the general purpose ones, like the 8051, which
are best described as single chip computers, containing a CPU, ROM, RAM
and various external interfaces on a single chip.

Huh? He said it had unboard ROM space and you said it contained "ROM ...
on a single chip". So how is it not the case?

The word sizes are
the vanilla ones, so that adding external ROM or RAM can be done using
cheap, off the shelf, components (no point in having a cheap
microcontroller if it needs expensive external chips).

You may not be familiar with the 8051, but it's addressing modes were
quite unusual. (If you only programmed it in C, you might not have realized
just how odd it is.) As an example, how many bits do you think you need for
a general purpose pointer in an 8051? (Keep in mind it has code and data in
distinct address spaces.) And what about the external MOV instructions that
take an 8-bit address? Do you know where the other 8 bits of the address
comes from? (It's truly bizarre.)

Low power consumption is often not an issue (no point in using a < 1 mW
controller in a microwave oven)

His claim was "often". And he didn't say it was the most important
thing, he said it counted more than clock speed. You aren't seriously going
to argue that clock speed is important in a microwave oven.

So he said A is often more important than B and you came up with a case
where neither is particularly important. How do you think this refutes what
he said?

but low cost per chip is an overriding
concern, otherwise the designer would opt for a traditional microprocessor
+ ROM + RAM + I/O intefaces approach, which is often more comfortable to
program on (the typical CPU in a microcontroller is less capable than an
usual microprocessor, the program and the data often reside in different
address spaces, and, for machine code compactness reasons, the program
memory is often paged).

Well that's the first thing you've said that's correct. Low cost is
quite often the most critical factor in a microcontroller. Though it's not
so much the per chip cost as the cost to implement an entire system. This is
why, for example, a microcontroller is more likely to contain an on-chip
clock generator than a general-purpose CPU is.

DS

 

[Malcolm]

Furthermore, Intel had an 8052 chip with an embedded
BASIC interpreter, that could be used as the core of a small
computer.

This sounds rather cute. Were these chips used for anything?

 

[CBFalconer]

This sounds rather cute. Were these chips used for anything?

No. They ground up millions of them in a wood chipper, and fed
them to the cattle. The results were eventually sold to
McDonalds. Thus mad cows were programmed in Basic.

 

[Dan Pop]

This sounds rather cute. Were these chips used for anything?

Dunno, I've only seen the specs in an Intel catalog.

Dan

 

[Alan Balmer]

This sounds rather cute. Were these chips used for anything?

Yes. They were and are used for millions of things. That's why Intel
makes so many ;-)

 

[Dan Pop]

In <[email protected]> August Derleth <[email protected]>
writes:

[1]A microchip designed to be used in an environment other than a PC,
server, router, or other obviously-computer environment.

Many older hard disks found in PC's used an 8051 chip, so your definition
is rather shaky. Furthermore, Intel had an 8052 chip with an embedded ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
BASIC interpreter, that could be used as the core of a small computer.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

He's saying it's "*designed* to be used in an environment other than a
PC".

So are plenty of high performance RISC processors, designed to be used in
workstations and servers...

The 8051 was designed to be embedded in a wide variety of devices, and
not primarily as the central processor of a general-purpose computer.

See the counterexample mentioned above...

Huh? He said it had unboard ROM space and you said it contained "ROM ...
on a single chip". So how is it not the case?

I was commenting the whole of his statement, not the on-board ROM bit.
See the rest of the paragraph for full enlightenment.

You may not be familiar with the 8051, but it's addressing modes were
quite unusual.

Having programmed in 8051 assembly, I am reasonably familiar with it and
its addressing modes. I wouldn't say that a word size of 8 bits is
particularly odd...

(If you only programmed it in C, you might not have realized
just how odd it is.) As an example, how many bits do you think you need for
a general purpose pointer in an 8051? (Keep in mind it has code and data in
distinct address spaces.) And what about the external MOV instructions that
take an 8-bit address? Do you know where the other 8 bits of the address
comes from? (It's truly bizarre.)

I'm failing to see the connection between these questions and the size of
the 8051 word. In your humble opinion, why is it called an 8-bit
microcontroller?

His claim was "often". And he didn't say it was the most important
thing, he said it counted more than clock speed. You aren't seriously going
to argue that clock speed is important in a microwave oven.

If it's not important, then try to control one using a 1 Hz clock...
But my point was that low power is not that often an overriding concern,
while low cost per chip *is*.

If you'd read my sentences and paragraphs in their entirety instead
of interrupting the process at arbitrary points, you might even be
able to see my points by yourself...

So he said A is often more important than B and you came up with a case
where neither is particularly important. How do you think this refutes what
he said?


Well that's the first thing you've said that's correct.

Everything I said in my previous post was factually correct. Learn to
read and you may eventually realise it.

Dan

 

[Old Wolf]

Yes. They were and are used for millions of things. That's why Intel
makes so many ;-)

I heard that Intel sold the 8051 rights to Philips back when the 8086
was the latest greatest thing and it was inconceivable to Intel that
anyone would want an 8051 any more. Of course, Philips then used them
in all their appliances and now on, and sales are higher than ever,
but Intel doesn't see a cent of it.
Is there any truth in that?

 

[LeTubs]

No. They ground up millions of them in a wood chipper, and fed
them to the cattle. The results were eventually sold to
McDonalds. Thus mad cows were programmed in Basic.

10 PRINT "moo"
20 GOSUB chew_cud
30 GOSUB standing_around_in_a_field_all_day
40 GOSUB produce_large_amounts_of_manure_and_methane
50 GOTO 10

Sorry but had to do it

Later
David

 

[Richard Bos]

I heard that Intel sold the 8051 rights to Philips back when the 8086
was the latest greatest thing and it was inconceivable to Intel that
anyone would want an 8051 any more. Of course, Philips then used them
in all their appliances and now on, and sales are higher than ever,
but Intel doesn't see a cent of it.
Is there any truth in that?

It sounds atypical for Philips, who tend to be technically quite
inventive, but more or less inadept at getting a commercial one-over on
the competition.

Richard

 

[Dan Pop]

I heard that Intel sold the 8051 rights to Philips back when the 8086
was the latest greatest thing and it was inconceivable to Intel that
anyone would want an 8051 any more. Of course, Philips then used them
in all their appliances and now on, and sales are higher than ever,
but Intel doesn't see a cent of it.
Is there any truth in that?

Nope. Intel may have licensed the architecture to other companies (dunno
if they actually did or not), but not sold it.

See http://support.intel.com/design/mcs51/

Dan

 

[Neil Kurzman]

Either way Intel no longer makes any 8051 variants anymore.