Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronic Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

REQ:AT*MEL's @Web TCP/IP Stack Library for Ke*il

Status
Not open for further replies.

ZeRoN

Advanced Member level 4
Joined
Jun 28, 2001
Messages
104
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,298
Activity points
1,184
keil c51 ip ppp

8O I really need it to evaluated PPP connection.
Does anyone have it? PLZ.
Regards,

PS. I've ordered the kit, but it take long time to arrived.
it would be great if I get it for evaluate early.
 

guv

Newbie level 1
Joined
Feb 11, 2003
Messages
1
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
10
an2120 motorola

Dear Silvio,

Can you send also to me missed tcpip.lib from ATMEL WEB?
I have some tcpip implementations but without ppp, so I can't test my ideeas ....

Please help me!!!!

My eail address is guv@rol.ro

GUVRILA :(
 

silvio

Advanced Member level 3
Joined
Dec 31, 2001
Messages
716
Helped
105
Reputation
210
Reaction score
16
Trophy points
1,298
Location
Romania
Activity points
11,497
http req from microcontroller

I don't mind to share, though is very annoying to spent $50 just to send the money for the kit (swift and bank's comission).
See my other post, too. http://www.elektroda.pl/eboard/viewtopic.php?t=34101&highlight=tcp+ip

I even replaced the files deleted by a bored man who thinks is a superman :evil: if he found some holes in the server security.

However, it would be wiser to mention here the license as follows:

This License Agreement is a legal agreement between you ("Licensee") and Atmel Corporation ("Atmel")
for the Atmel @Web TCP/IP Evaluation Kit software product, which includes computer programs,
libraries, source code examples, printed materials, electronic documentation and verification suite for
these programs ("Licensed Software"). The Licensed Software also includes any updates and
supplements to the original Licensed Software provided by Atmel.
By installing copying, downloading, accessing, or otherwise using the Licensed Software the Licensee
agree to be bound by the terms of this License Agreement. If you do not agree to the terms of this
License Agreement, do not install or use this License Software, the Licensed Software may be returned
to a Atmel sales office or Atmel distributor for a full refund.


My question: :cry: It's someone willing to share this product: http://www.ceibo.com/pdf/tcpip-51.pdf

TCP/IP Stack works with 8051 Microprocessors
Dials, sends and receives emails
Libraries for Keil, IAR and Tasking
ANSI C source code available
Compact code size: 15K
TCP, SMTP, PPP and POP3
RTOS independent
Royalty free
User configurable


My answer is NO. The owner of the kit is definitely a company, because you can't afford spending on such expensive kits.
Would you risk your job as employer in such company, revealing the source ? The answer is definitely NO. As a matter of fact I'm doubtful that such employer is member of this forum.
Thus, keep dreaming to 15K compact size code, though it would be nice to see the ceibo development team worth-while effort.

Regards,
Silvio

I shall upload the CD in two parts.
 

micro_tools

Junior Member level 1
Joined
May 17, 2001
Messages
18
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
72
keil c51 tcp/ip

Hi,

I need this AT*MEL's @Web TCP/IP Stack Library for Ke*il but I dont have enough points

* Could somebody upload it to MCU Fileman
or sent it me to streamload (My streamload id is : micro_tools)


Thanks,
micro_tools
 

ZeRoN

Advanced Member level 4
Joined
Jun 28, 2001
Messages
104
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,298
Activity points
1,184
@web tcp/ip stack library for keil download

Dear silvio,

You said corrected.
but I would like to share for evaluation purpose really.
at now, I have not received the kit yet.

Thankyou very much for your sharing.

Regards,
ZeRoN
 

dacadc

Full Member level 2
Joined
Apr 22, 2001
Messages
146
Helped
2
Reputation
4
Reaction score
2
Trophy points
1,298
Location
Ukraine
Activity points
1,101
Files

Did you tested product from Atmel?
 

ZeRoN

Advanced Member level 4
Joined
Jun 28, 2001
Messages
104
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,298
Activity points
1,184
ucIP require porting to KE*IL C51.
but the uploaded ATWeb tcpip library designed for KE*IL C51.

I've tested by rebuild all demo projects
by KE*IL C51 v7.04, all OK. :)

Now, I can study the stack and simulate while waiting for the ATWeb kit hardware.

Thankyou again to Silvio.
Regards,
ZeRoN
 

usbman

Advanced Member level 4
Joined
Sep 22, 2002
Messages
118
Helped
2
Reputation
4
Reaction score
1
Trophy points
1,298
Location
Germany
Activity points
1,019
silvio said:
Sorry for new thread but "Attachment cannot be added, since the max. number of 5 Attachments in this post was achieved"

The last rar file:
silvio,
thanks for sharing.
I have checked the package but could not compile any of the projects
because TCPIP.lib in directory \tcp_lib is missing..
Also I have not found any source for this lib so I could not create it. :(

Is this lib file on your cd ??

cheers usbman
 

silvio

Advanced Member level 3
Joined
Dec 31, 2001
Messages
716
Helped
105
Reputation
210
Reaction score
16
Trophy points
1,298
Location
Romania
Activity points
11,497
I can't help myself to say that.
You're a smart guy ZeRoN. But I'm glad you figure out.
I didn't want to cheat someone. If you feel offended, I apologize.

My first impulse, due to the license, was do not post the all CD contents.
That's why I makeup a little the welcome html file, then remove the most important part. Obvious, later as per your request (or someone else who really need it) I should sent by email the deleted part.
usbman is one among others who download the files but at least gives a try to compile and not only to store on HDD. This way he shows his immediately interest and obviously deserving and the missing file sent by email. I don't want these files to be spreaded around the internet rather than elektroda forum for peoples really interested. As a matter of fact could someone PM to me an URL (even chinese) where I could download the kit. Bear in mind his release date (middle of last year), long enough until now for someone to post somewhere, if really wants to share.

But I forgot empties the recycle. That's life. Worst thing is that doing so, I increased the rar file and counterpart the elektroda bandwidth, but not to increase my point rate.

Silvio
 

cdcll

Full Member level 3
Joined
Feb 15, 2002
Messages
163
Helped
8
Reputation
16
Reaction score
1
Trophy points
1,298
Activity points
1,199
Does the stack include DHCP?
 

silvio

Advanced Member level 3
Joined
Dec 31, 2001
Messages
716
Helped
105
Reputation
210
Reaction score
16
Trophy points
1,298
Location
Romania
Activity points
11,497
Hi Cdcll,

As far as I know DHCP (described in RFC 2131), the Dynamic Host Configuration Protocol, allows a device attached to the network (DHCP Clients) to automatically learn some or all of its network configuration, including its IP (Internet) address dynamically obtained from the DHCP Server.

The Atmel kit it's mainly concerned to point to point links protocol.
DHCP doesn't make sense over PPP anyway because PPP has its own options for doing everything DHCP does.

Besides this, the DHCP uses UDP as its transport protocol, which hasn't been implemented in the kit. The client sends messages to the server on port (67). The server sends messages to the client on port (68 ).

Maybe you're more interested in PPPoE which is another story not cover by the stack provided by Atmel in the kit.
Point to Point Protocol over Ethernet is a proposal specifying how a host personal computer (PC) interacts with a broadband modem (i.e. xDSL, cable, wireless, etc) to achieve access to the growing number of Highspeed data networks.


Regards,
Silvio
 

M!k

Advanced Member level 2
Joined
Apr 22, 2002
Messages
682
Helped
109
Reputation
218
Reaction score
35
Trophy points
1,308
Activity points
4,822
usbman said:
silvio,
thanks for sharing.
I have checked the package but could not compile any of the projects
because TCPIP.lib in directory \tcp_lib is missing..
Also I have not found any source for this lib so I could not create it. :(

Is this lib file on your cd ??

cheers usbman

Can somebody please upload the missing file TCPIP.lib. There was nothing to find @ Atmel.com.


Thanks - Mik
 

ZeRoN

Advanced Member level 4
Joined
Jun 28, 2001
Messages
104
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,298
Activity points
1,184
Dear All,

I've failed to use ATWeb's PPP to connect with direct cable connection
to WinXP host.

The ATWeb's PPP was reject all WinXP host's LCP requests,
also Authenticate protocol (MSCHAP in this case).
This caused WinXP host to terminate the connection immediately.

By normally, PPP/LCP nigotitation shouldn't reject Auth. protocol,
but PPP/LCP will NAK to change from other Auth. protocol to PAP.
(I have success with Microchip's AN724 before)

if anyone has experienced with ATWeb, please advise me.
How to config ATWeb PPP nigotation?

for more details about PPP/LCP nigotiation packets of my connection,
please see below.

Any advise welcome.
Thankyou in advance.

Regards,
ZeRoN

Code:
//Packet captured by HHD's Serial Port Monitor v2.16
//Packet analysed by My own analyser
//
//Answer is coming from 51 hardware to WinXP host
//Request is going out from WinXP host to 51 hardware

Port closed

Port opened by process "svchost.exe" (PID: 732)

Answer: 02/17/2003 21:28:23.457209664

 43 4C 49 45 4E 54 43 4C 49 45 4E 54               CLIENTCLIENT

Request: 02/17/2003 21:28:24.578822464 (+0.1101584000 seconds)

 43 4C 49 45 4E 54 53 45 52 56 45 52               CLIENTSERVER

Answer: 02/17/2003 21:28:24.969384064 (+0.3905616000 seconds)

 7E FF 7D 23 C0 21 7D 21 7D 20 7D 20 7D 2E 7D 22   ~ÿ}#À!}!} } }.}"
 7D 26 7D 20 7D 20 7D 20 7D 20 7D 23 7D 24 C0 23   }&} } } } }#}$À#
 7D 29 A1 7E                                       })¡~

=FF 03 C0 21 01 00 00 0E 02 06 00 00 00 00 03 04   ÿ.À!............
=C0 23 09 A1                                       À#.¡
=PPP:LCP:Link Control Protocol (0xFF03C021)
=Code:01,Request, RFC1661
=ID:00
=Option:02(00000000),Async Control Character Map, RFC1662
=Option:03(C023),Authentication Protocol, RFC1661

Request: 02/17/2003 21:28:25.019456064 (+0.0500720000 seconds)

 7E FF 7D 23 C0 21 7D 21 7D 20 7D 20 3B 7D 22 7D   ~ÿ}#À!}!} } ;}"}
 26 7D 20 7D 20 7D 20 7D 20 7D 23 7D 25 C2 23 81   &} } } } }#}%Â#
 7D 25 7D 26 44 D1 78 6C 7D 27 7D 22 7D 28 7D 22   }%}&DÑxl}'}"}(}"
 7D 2D 7D 23 7D 26 7D 31 7D 24 7D 26 4E 7D 33 7D   }-}#}&}1}$}&N}3}
 37 7D 21 C8 C5 CD DC CD 45 43 FD 82 E9 F6 E6 72   7}!ÈÅÍÜÍECý‚éöær
 88 B0 3B 7D 20 7D 20 7D 20 7D 20 7D 37 7D 24 7D   ˆ°;} } } } }7}$}
 20 7D 20 7F 78 7E                                  } x~

=FF 03 C0 21 01 00 00 3B 02 06 00 00 00 00 03 05   ÿ.À!...;........
=C2 23 81 05 06 44 D1 78 6C 07 02 08 02 0D 03 06   Â#..DÑxl.......
=11 04 06 4E 13 17 01 C8 C5 CD DC CD 45 43 FD 82   ...N...ÈÅÍÜÍECý‚
=E9 F6 E6 72 88 B0 3B 00 00 00 00 17 04 00 00 7F   éöærˆ°;........
=78                                                x
=PPP:LCP:Link Control Protocol (0xFF03C021)
=Code:01,Request, RFC1661
=ID:00
=Option:02(00000000),Async Control Character Map, RFC1662
=Option:03(C22381),Authentication Protocol, RFC1661
=Option:05(44D1786C),Magic Number, RFC1661
=Option:07,Protocol Field Compression, RFC1661
=Option:08,Address and Control Field Compression, RFC1661
=Option:13(06),Callback, RFC1570
=Option:17(064E),Multi Link MRRU, RFC1990
=Option:19(01C8C5CDDCCD4543FD82E9F6E67288B03B00000000),ML Endpoint Discriminator, RFC1990
=Option:23(0000),Link Discriminator for BACP, RFC2125

Request: 02/17/2003 21:28:25.029470464 (+0.0000000000 seconds)

 7E FF 7D 23 C0 21 7D 22 7D 20 7D 20 7D 2E 7D 22   ~ÿ}#À!}"} } }.}"
 7D 26 7D 20 7D 20 7D 20 7D 20 7D 23 7D 24 C0 23   }&} } } } }#}$À#
 37 22 7E                                          7"~

=FF 03 C0 21 02 00 00 0E 02 06 00 00 00 00 03 04   ÿ.À!............
=C0 23 37 22                                       À#7"
=PPP:LCP:Link Control Protocol (0xFF03C021)
=Code:02,Ack, RFC1661
=ID:00
=Option:02(00000000),Async Control Character Map, RFC1662
=Option:03(C023),Authentication Protocol, RFC1661

Answer: 02/17/2003 21:28:25.049499264 (+0.0200288000 seconds)

 7E FF 7D 23 C0 21 7D 24                           ~ÿ}#À!}$
 7D 20 7D 20 35 7D 23 7D 25 C2 23 81 7D 25 7D 26   } } 5}#}%Â#}%}&
 44 D1 78 6C 7D 27 7D 22 7D 28 7D 22 7D 2D 7D 23   DÑxl}'}"}(}"}-}#
 7D 26 7D 31 7D 24 7D 26 4E 7D 33 7D 37 7D 21 C8   }&}1}$}&N}3}7}!È
 C5 CD DC CD 45 43 FD 82 E9 F6 E6 72 88 B0 3B 7D   ÅÍÜÍECý‚éöærˆ°;}
 20 7D 20 7D 20 7D 20 7D 37 7D 24 7D 20 7D 20 BA    } } } }7}$} } º
 AA 7E                                             ª~

=FF 03 C0 21 04 00 00 35 03 05 C2 23 81 05 06 44   ÿ.À!...5..Â#..D
=D1 78 6C 07 02 08 02 0D 03 06 11 04 06 4E 13 17   Ñxl..........N..
=01 C8 C5 CD DC CD 45 43 FD 82 E9 F6 E6 72 88 B0   .ÈÅÍÜÍECý‚éöærˆ°
=3B 00 00 00 00 17 04 00 00 BA AA                  ;........ºª
=PPP:LCP:Link Control Protocol (0xFF03C021)
=Code:04,Reject, RFC1661
=ID:00
=Option:03(C22381),Authentication Protocol, RFC1661
=Option:05(44D1786C),Magic Number, RFC1661
=Option:07,Protocol Field Compression, RFC1661
=Option:08,Address and Control Field Compression, RFC1661
=Option:13(06),Callback, RFC1570
=Option:17(064E),Multi Link MRRU, RFC1990
=Option:19(01C8C5CDDCCD4543FD82E9F6E67288B03B00000000),ML Endpoint Discriminator, RFC1990
=Option:23(0000),Link Discriminator for BACP, RFC2125

Request: 02/17/2003 21:28:25.049499264 (+0.0000000000 seconds)

 7E FF 7D 23 C0 21 7D 25 7D 21 7D 20 7D 30 44 D1   ~ÿ}#À!}%}!} }0DÑ
 78 6C 7D 20 3C CD 74 7D 20 7D 20 7D 23 97 38 FE   xl} <Ít} } }#—8þ
 7E                                                ~

=FF 03 C0 21 05 01 00 10 44 D1 78 6C 00 3C CD 74   ÿ.À!....DÑxl.<Ít
=00 00 03 97 38 FE                                 ...—8þ
=PPP:LCP:Link Control Protocol (0xFF03C021)
=Code:05,Terminate Request, RFC1661
=ID:01

Answer: 02/17/2003 21:28:25.059513664 (+0.0100144000 seconds)

 7E FF 7D 23 C0 21 7D 26 7D 21 7D 20 7D 30 44 D1   ~ÿ}#À!}&}!} }0DÑ
 78 6C 7D 20 3C CD 74 7D 20 7D 20 7D 23 97 7D 39   xl} <Ít} } }#—}9
 64 7E                                             ¡~

=FF 03 C0 21 06 01 00 10 44 D1 78 6C 00 3C CD 74   ÿ.À!....DÑxl.<Ít
=00 00 03 97 19 64                                 ...—.d
=PPP:LCP:Link Control Protocol (0xFF03C021)
=Code:06,Terminate Ack, RFC1661
=ID:01
 

silvio

Advanced Member level 3
Joined
Dec 31, 2001
Messages
716
Helped
105
Reputation
210
Reaction score
16
Trophy points
1,298
Location
Romania
Activity points
11,497
Hi ZeRoN,

I must admit that I purchased the kit in order to be able to send by email some informations from the field.
The Atmel kit was a good choise for my needs after some disappointing hardware trial for such kind of application.
Thus, I didn't felt the need to get into much details of implementation, as long as I succesfully succeed to send information through my ISP.
That's it, I use the modem fitted on the board and not shift the serial communication (through two micro switches provided by Atmel design) to outside world.
Since you're still waiting the evaluation board, I believe you use some 51 hardware to simulate the communication as I can do by-passing the modem on development Atmel board.

From your post I understand you try to connect the 51 hardware to WinXP host through direct cable connection.
It's a very bad behaviour for 51 harware to reject the Authorization request instead of NAK it, even for PAP proposal, which is the minimum that Atmel kit will accept. CHAP was not implemented and it's clearly stated by Atmel.

Looking at the time stamp for either request or answer, why are two running request with same ID, but no answer from 51 hardware between them:

Request: 02/17/2003 21:28:25.019456064 (+0.0500720000 seconds)
Code:01, ID:00
Request: 02/17/2003 21:28:25.029470464 (+0.0000000000 seconds)
Code:02, ID:00


What's the 51 hardware doing meanwhile ?

Because the Request: 02/17/2003 21:28:25.02947046 has the code 02, it acknowledge as server, the request from 51 hardware.
Bear in mind that if all options are acceptable, the peer then responds with Configure-ACK with exactly the same option list as given in the Configuration_Request to indicate that all of the enclosed options were acceptable and that all are now enabled.
Thus, how the request from 51 harware looks like ? If the server respond with ACK option 03, that means the 51 hardware, request that option prior to response from server.

On the other hand we are still in LCP negotion, we didn't succeed to pass to Auth. phase, since it's not clear for peer which authentification protocol should be used.
Another hint is that an implementation in which a peer cannot identify itself using any of the protocol it has (which happens if the user has not configured the right secrets or password) should send LCP Configure_reject to ask to remain anonymous.
I'm in doubt that's happens in our system, but did you check if the user and password fields are filled inside 51 code. Silly question !
On the other hand since I don't have the source code for ppp.c, only object code, I don't know how the 51 micro behaves. The problem could be solved in debugger and tracking the code near the point when reject is sent, synchronized with the time stamp delivered by HHD software.

Because I feel that something is missing from the listing generated by serial monitor program can you PM to me the all log file.
I understand the layout of the log file (nice feature of removing the escape character) but shame for me I don't understand the two rows:
43 4C 49 45 4E 54 43 4C 49 45 4E 54 CLIENTCLIENT
43 4C 49 45 4E 54 53 45 52 56 45 52 CLIENTSERVER


Maybe when you'll receive the development kit and doing all the job online through ISP, the play will have much fun.
That's the purpose, the development kit was made for. To simulate only if you have trouble on real live.

If you look at post http://www.elektroda.pl/eboard/viewtopic.php?t=34101&highlight=tcp+ip and parsing the code you will see some "if define" conditional for debugger at each step of ending phase.
You can do the same thing sending codes through second 51 UART in order to know what exactly where you are. Obvious if you're not doing in K_e_i_l simulator.

Regards,
Silviu
 

ZeRoN

Advanced Member level 4
Joined
Jun 28, 2001
Messages
104
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,298
Activity points
1,184
Dear Silvio,

silvio said:
Looking at the time stamp for either request or answer, why are two running request with same ID, but no answer from 51 hardware between them:

Request: 02/17/2003 21:28:25.019456064 (+0.0500720000 seconds)
Code:01, ID:00
Request: 02/17/2003 21:28:25.029470464 (+0.0000000000 seconds)
Code:02, ID:00
both server and client are start their own LCP. nigotation.

Request: 02/17/2003 21:28:25.029470464 (+0.0000000000 seconds)
is answer to 51, for client side started LCP nigotation at
Answer: 02/17/2003 21:28:24.969384064 (+0.3905616000 seconds)
(ID:00 is from 51)
and
Request: 02/17/2003 21:28:25.019456064 (+0.0500720000 seconds)
is server side start LCP nigotation from winxp host to 51, and 51 reject
Answer: 02/17/2003 21:28:25.049499264 (+0.0200288000 seconds)
(ID:00 is from WinXP host)

NOTE:
Request:... is mean WinXP host send data to 51, not PPP/LCP request.
Answer:... is mean WinXP host receive data from 51.

After 51 rejected host request LCP Auth. protocol option,
host terminate connection immediately!
the LOG file from Serial Monitor is completed.

The nigotation above didn't passed LCP. to Auth. Protocol.
because ATWeb was reject Auth. protocol.

The problem is Server side (WinXP) request LCP with MSCHAP (0xC22381)
The correct step is Client side (51 ATWeb) must NAK Auth. protocol with PAP (0xC023),
then Server Request LCP again with Auth. protocol PAP (0xC023)
but ATWeb doesn't NAK, Its reject!

silvio said:
I understand the layout of the log file (nice feature of removing the escape character) but shame for me I don't understand the two rows:
43 4C 49 45 4E 54 43 4C 49 45 4E 54 CLIENTCLIENT
43 4C 49 45 4E 54 53 45 52 56 45 52 CLIENTSERVER


Maybe when you'll receive the development kit and doing all the job online through ISP, the play will have much fun.
That's the purpose, the development kit was made for. To simulate only if you have trouble on real live.
"CLIENTCLIENT" is Client side request to WinXP host to start connection.
"CLIENTSERVER" is Server side answer to client.
It's like modem dial by "ATDT...." and modem response "CONNECT ....."

I must use this Auth. protocol NAK feature, because I didn't use modem dial-up to ISP. (always use PAP)
I connect to GSM/GPRS ISP., that request with MD5CHAP (0xC22305) Auth. protocol.

please see another full & success PPP nigotation, attached RAR files.
(use PPP by porting C source from Microchip's AN724 to 51)
http://www.elektroda.pl/eboard/viewtopic.php?t=34492&highlight=ppp

Thankyou so much.
Regards,
ZeRoN
 

usbman

Advanced Member level 4
Joined
Sep 22, 2002
Messages
118
Helped
2
Reputation
4
Reaction score
1
Trophy points
1,298
Location
Germany
Activity points
1,019
ZeRon,

which Processor do you use. Hopefully its a ATMEL CC01 or AC2.

I found some strange code in the lib while debugging.
There is a function _IP_CHECK which works only on Atmel.

usbman
 

dacadc

Full Member level 2
Joined
Apr 22, 2001
Messages
146
Helped
2
Reputation
4
Reaction score
2
Trophy points
1,298
Location
Ukraine
Activity points
1,101
PPP

Did you analyzed code of this function?
 

ZeRoN

Advanced Member level 4
Joined
Jun 28, 2001
Messages
104
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,298
Activity points
1,184
Dear usbman,

I haven't use ATMEL processor yet. I'm waiting for ATWeb_EVK01.

I'm using Phillips P89C51RD2 on my exists 51 system, to evaluate
ATWeb tcp/ip stack before EVK01 arrived.

but for now, the PPP connection still can't established.
PPP steps are...
1.LCP. (Link Control Protocol)
2.AP. (Authenticate Protocol, I must use PAP:password Auth. Protocol)
3.IPCP. (IP Config Protocol)
4.IP(ICMP,UDP,TCP)

IP config is in 3rd. step.
now ATWeb don't pass 1st. step.

Is there more details of ATWeb TCP/IP stack library?
I would like to know...
How to config PPP nigotation?
or
How to disable it?

(to put my own PPP connection, then use only their TCP/IP stack)

Thankyou for your information.
Regards,
 

usbman

Advanced Member level 4
Joined
Sep 22, 2002
Messages
118
Helped
2
Reputation
4
Reaction score
1
Trophy points
1,298
Location
Germany
Activity points
1,019
dacadc said:
Did you analyzed code of this function?
yes I did but I realy dit not unterstand the implications.
Its definately something which will work only at Atmel

here is the code
Code:
_IP_CHECK:				;_34EA:
	CLR	A			;
	MOV	DPH, A			;DPTR=0030h
	MOV	DPL, #30h		;mayby reading the Vendor id
	CLR	EA			;EA=0
	MOV	FCON, #2h		;FCON=_FMOD0;
	MOVC	A, @A+DPTR		;
	ADD	A, DPL			;
	SUBB	A, #88h			;
	MOV	FCON, A			;
	SETB	EA			;
	JZ	OK			;
NOK:
	MOV	DPH, R1			;R1/R2 is undefined in most cases
	MOV	DPL, R2			;
	JMP	@A+DPTR			;
OK:
	MOVC	A, @A+DPTR		;
	ADD	A, DPL			;
	SUBB	A, #88h			;
	JZ	NOK			;
	RET				;
 

Status
Not open for further replies.
Toggle Sidebar

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Top