http://www.paradroid.net/ip65

I think that is the best solution available currently. However I think what you want is a binary library that simply sits in RAM, like a network kernel. I think Six (not Sixx/F4CG) is working on such a library. However, last time I checked the web link was broken.

Schema should know more about it as he's been using it for his Artillery Duel network game.

Um. So because you don't feel like writing one yourself, you expect someone else to do it for you?

Sure. It makes more sense for someone to do it, who has already implemented it for himself and is knowledgeable in the subject. Don't you agree?

For the same reason I wanted someone to do a FAT-library for MMC64. I really expected the BIOS to provide this already and was hugely disappointed ...

I believe strongly in the age-old hacker ethic that calls for contributors to share their efforts for the good of the community!

_________________
Commodore 128 Programmer
City of Kouvola, Finland

http://mydarkgothvampiricplace.endofthe ... Commodore/

Yeah, Six took down his netlib64 network lib page - not sure what that means.

However, it's included in my Artillery Duel source releases - with Six's permission. Hopefully it's not too hard to separate it out

http://home.ica.net/~leifb/commodore/du ... 28-006.zip

Note that it is an older version of the netlib though.

Greetings from some sort of a newbie when it comes do actually *do* something with the RRNet device. I've just begun to read here and try out all the little code snippets around. Eventually, uip-0.9 and the unmodified version of the cs8900a driver from Contiki 1.2 work out fine on my setup, the httpd server application does do the trick (at least on the internal network, won't work with NAT / port forwarding and dyndns on the router though). I'm pretty excited, since this stuff actually *works*. I've been playing around with Doc Bacardi's examples for quite some time, but I'm less assembler and more into C. So finally I ended up with using uIP and the cs8900a driver. As I said, I'm sort of new to this but it is fun! Hope I can contribute to this forum later on. Thanks for all the good hints and examples!

_________________
LOAD ":*",8,1
READY.
RUN

Greetings and welcome to the forum! It's great that you got uIP and the cs8900 driver up and running already. As you might know already, this is the solution i'm using for GuruTerm and it's been working perfectly so far. Looking forward to your questions and contributions

Thank you.

I do have one question regarding the latest release of uIP: has anyone here ever been able to compile version 1.0? I've tried all the tricks I used to build uip-0.9 (e.g. I didn't fix the Makefiles but compiled each source file manually, linking them together in the end). But the final linking fails, with cc65 then complaining about an unresolved symbol "_main" in (callmain.s). Shouldn't that symbol be found in the c64.lib of cc65 anyway?

Building uip-0.9 doesn't cause any problems though. I would really appreciate any hints on how to successfully compile uip-1.0.

_________________
LOAD ":*",8,1
READY.
RUN

I've never bothered with 1.0 simply because 0.9 is working great and from what I know 1.0 doesn't bring any significant advantage. It would interesting to try it out though.

I don't know about the linking problem.. Does the main() function reside in callmain.c or what does it do? cl65 seems to be a bit dodgy about the command line ordering. Try reordering the input files. I think I made a post about that recently..

Well, I've come to the same conclusion. 1.0 makes use of some time.h struct that isn't implemented in cc65 (yet). And since this tiny, little webserver runs pretty well under 0.9 I'll stick to that. But I seem to have problems running uip-0.9 through my firewall router (CheckPoint VPN-1 Edge).

Anyway, I've done some adaptions, mainly typecasts, from 1.0 to the original 0.9 code so now the uip_sethosaddr() and other macros defined in uip.h work properly and compile with the current cc65 snapshot release.

Also, I've done some simple routine in C that takes an IP address in a string (eg. "192.168.0.1") and returns the four octets as u16_t values (I guess the assembler guys just shift around some bits in the memory to accomplish the same ). It's not fool-proof, but it works. So if there's any interest in having a closer look at these modifications, I'd be honored to put the modified uip-0.9 sources along with my build.sh script to the uploads section. If you don't mind, that is?!

_________________
LOAD ":*",8,1
READY.
RUN

Indeed we do

http://codebase64.org/doku.php?id=base:ip_address_input

Please do! I'd like to take a look at it. Might as well use it in the next version of GuruTerm

Done, see upload section.

_________________
LOAD ":*",8,1
READY.
RUN

Hi,

First of all a happy new year to everybody.

I know that the uIP users have the great tradition of being afraid of Contiki but nevertheless I'd like to mention that Contiki 2.x is READY-TO-GO ported to, tested with and maintained on the cc65 tool chain.

Beside that the Contiki 2.1 snapshot contains a much more recent uIP codebase than the uIP 1.0 snapshot.

Additionally Contiki 2.1 comes with with new dynamically loaded NIC drivers allowing to work with RRNet, TFE and ETH64 by just changing the runtime configuration.

And if you check out the latest CVS sources instead of using the 2.1 snapshot you'll additionally get convenient "high-level" config macros like:

MTU_SIZE: Reduce the MTU size from the 1500 default
WITH_BOOST: Support the delayed ACK workaround
WITH_DNS: Support UDP and DNS
WITH_CLIENT: Support "connect()"
WITH_LOGGING: Support Logging to the CRT
WITH_GUI: Support the CTK UI (doesn't work well together with logging)
WITH_MOUSE: Support the 1351 mouse (works only with GUI)

But if you say "I just don't want the whole Contiki thing, I'm only looking for uIP" you should know:

- uIP is a library that you call when you want to. Although it's a strange library in that most of your program logic lives inside callbacks from the library.

- Contiki is a framework that you plug your program logic into. Frameworks typically come with their own main() and so does Contiki. But in Contiki the main() isn't "hidden" from the user. Just check out

http://contiki.cvs.sourceforge.net/contiki/contiki-2.x/platform/c64/contiki-main.c?revision=1.16&view=markup

If you remove everything from main() and put in what you know from uIP you don't have any type of Contiki runtime overhead at all !

The only thing to know is how to use the generic NIC driver:

- ethernet_poll() and ethernet_send() work as expected and known from the traditional drivers.

- ethernet_init() however takes one argument that you can simply create like this:
static struct ethernet_config config = {0xDE08, "cs8900a.eth"};

Just my two cents, Oliver

Good to know and I'm really curious to check it out on my C64, but where do I find accurate instructions on how to successfully build Contiki 2.x for the c64 using the lastest snapshot of cc65?



What about the "struct timeval" missing in time.h of the latest cc65 snapshot? uIP 1.0 makes use of that struct in the clock-arch.c file. I'm always running into things like that with Contiki sources > 1.2-devel1.



Well, IMHO the plain uIP stack and its demo applications are quite a good point to start with, if you're new to all this stuff. Of course, Contiki offers a lot more features and I'm sure that I'll have a closer look at it sometime.



That sounds great and as I said: tell me how to get it to compile with cc65 and I'll join the Contiki party!

EDIT: um ... must have been me . I've checked out the latest CVS release and - surprise, surprise - the hello-world example compiled. I'll try out all the other stuff tonight and see what it's all about. Forget my complaints, that was definetely a case of "user error".

_________________
LOAD ":*",8,1
READY.
RUN